feat: fail-proof org first connection (guided install link, first-run fork, mismatch guard, verified handoff) - #2973
Merged
Merged
Conversation
…es; den-web: mint install links on active origen
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
Author
This was referenced Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.








What
Closes the loop on the org "first connection" handoff (web → download → installer → desktop → web) so an invited teammate can no longer silently end up on the wrong server (the Blue Yonder incident class). One link — the org install link — is now visible, copyable, and paste-recoverable at every step, every degraded path asks instead of guessing, and the org's own web page confirms the desktop actually connected.
Changes
den-web
den-api
POST /v1/auth/desktop-handoff/status— rate-limited, public, returnspending|consumed|unknown, never leaks tokens./v1/install/:platformserves mounted generic installers stamped (mac: zip sidecar; win: filename tag — was redirecting to the plain versioned desktop exe, a real bug found during Windows validation), falling back to the existing plain redirect + deep-link binding.desktop app
openwork://links, raw grants). No silent defaults; local-first escape hatch kept.meta.desktopBootstrap); no window where an org device believes it's on hosted cloud. Bootstrap now carriessource: file|default.installer
Validation (commands + results)
pnpm fraimz --flow first-connection --cdp-url http://127.0.0.1:9825): real den stack, two Chrome profiles, real installer binary, real Electron. Results:evals/results/2026-07-21T21-04-57-963Z/(fraimz comment below).evals/results/first-connection-windows-20260721/report.md: W1 stamped-exe → Acme bootstrap in%LOCALAPPDATA%✓, W2 renamed exe → paste fallback ✓, W3 expired link message ✓, W4 (app-on-Windows) skipped honestly (no toolchain in VM; read path covered by workspace-store unit tests).Post-merge note
release-generic-installer.ymlis workflow_dispatch — run it after merge so deployments can mount current generic installer builds; without mounted artifacts the route falls back to the plain installer + deep-link binding (now covered by the first-run fork).