feat(runtime): bind coordinator recovery generations - #196
Open
briananderson1222 wants to merge 1 commit into
Open
feat(runtime): bind coordinator recovery generations#196briananderson1222 wants to merge 1 commit into
briananderson1222 wants to merge 1 commit into
Conversation
briananderson1222
force-pushed
the
feat/coordinator-bound-recovery-generation-195
branch
from
July 29, 2026 05:42
df08652 to
10fd1f4
Compare
briananderson1222
force-pushed
the
feat/coordinator-bound-recovery-generation-195
branch
from
July 29, 2026 05:54
10fd1f4 to
56f88fe
Compare
Contributor
Author
|
Local verification for exact head
The PR remains blocked only because the three protected GitHub Actions contexts are absent while hosted CI is intentionally skipped for the exhausted CI budget. No required context was synthesized and branch protection was not changed. |
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.
Closes #195.
Summary
writeRunRecoveryFence()behavior and its rejection of caller-supplied generationsBoundary
Flow remains provider-neutral and owns path safety, locking, atomic publication, inspection, and finalization. External coordinators remain responsible for authenticating and durably binding
expected_generationbefore delegation. The generation is identity, not bearer authority.Local verification
npm test(352 Node tests passed; 26 browser tests passed, 8 intentional skips)npm run typechecknpm run check:types:contractsnpm run docs:checknpm exec --yes --package=@kontourai/veritas@1.5.2 -- veritas readiness(0 failures, 2 pre-existing warnings)Hosted CI was intentionally skipped because the suite CI budget is exhausted.
npm audit --omit=devreports the two advisories already present onmain(brace-expansion,fast-uri); this PR changes no dependencies.