Repository navigation
fix(native): bind foreground ownership to stable boot sessions - #230
Merged
Merged
Conversation
added 30 commits
October 8, 2026 12:33
added 27 commits
October 8, 2026 16:30
…ive-authored-recovery-writer
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
1 participant
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.
Native recovery previously compared macOS boot timestamps whose fractional representation could differ during the same boot. New native publications use the kernel boot-session UUID, keeping live-owner checks and explicit dead-owner recovery tied to the actual host session. Older receipt families retain their separate compatibility and refusal rules.
Validation: independent review of the exact head
7d92ea81against currentnext73ef475f, all 12 required CI jobs passed, focused TypeScript/native controls and static checks passed, and unchanged owning-source correspondence preserves the recorded full Rust results. The producer6d82324eand its packaged artifacts retain their original provenance.A genuine M5 macOS trial passed authenticated sibling readiness, live-owner and wrong-hash refusal, ordinary recovery, private environment/frontend retirement, a fresh same-scope startup, exact history preservation and normal Ctrl-C shutdown. An independent read-only observer verified all three runs Removed with null resource observations and preserved the original provider/process/disk/boot baseline. The interrupted frontend settled at 137 with complete streams; the native process was observed absent, but its exit status remains unknown. Earlier observer-only failures remain recorded.
Release intent: runtime correctness fix. This qualifies the bounded boot-session recovery path; source-bearing recovery, persistent databases, routes, refreshed hooks, full corpus parity and performance comparisons remain separate work. No release, installed-channel or default-backend change is included.