Skip to content

fix: isolate unfinished native launches by profile - #225

Merged
ecochran76 merged 1 commit into
mainfrom
fix/scoped-launch-custody
Oct 8, 2026
Merged

ecochran76 merged 1 commit into
mainfrom
fix/scoped-launch-custody

Conversation

@ecochran76

@ecochran76 ecochran76 commented Oct 8, 2026 •

Copy link
Copy Markdown

An unfinished native launch for one profile prevents ordinary commands and retained handoffs for every other profile from recovering after idle cleanup. Scope unresolved-claim admission to the launched or recovered profile, and retain cold-launch or uncertain claims during native runtime construction.

The real-host/SQLite regression first failed with remote_view_session_launch_readback_required in 0.09s and now passes in 0.14s, preserving the unrelated claim, logical identity and retained native handoff readiness. Same-profile retries and assignment-generation fences remain enforced.

Validation: 30 consumer tests, the complete Service Model suite, six SQLite custody tests, final handoff regression, format and strict workspace Clippy passed. The original authenticated PRF presentation reproduces on the old installation; production publication and original-link acceptance remain separate pending runtime checks. No runtime records were manually edited and no reboot occurred.

Closes #224. Related to #218; preserves PRs #191 and #184.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Scope unfinished native launch custody to the affected browser profile

1 participant