Repository navigation
Add owner board and release ancestry gates - #47
Merged
Merged
Conversation
sshlg
marked this pull request as ready for review
October 13, 2026 04:37
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.
The owner validator accepted duplicate board declarations and release workflows with a bypassed tag ancestry guard. Add member-local board validation and reuse the reviewed family release parser; preserve grouped historical identities, explicit hub references and the separate summary table. Correct the real even-backslash Markdown pipe found during migration.
Eight baseline plants reproduced the missing refusals. The candidate passes 16 actual-validator controls with residue accounting after independent review corrected orphan-row admission. Full local npm test passed at7aa4dd3; the later documentation-only head preserves the receipt. Hosted candidate checks are next. Wire the suite into local and hosted gates, and apply the standing nightly/explicit-candidate CI policy without per-push full runs.
Entry: docs/HANDOFF.md and docs/evidence/runs/2026-10-13-r30-owner-gates.md. No release or installed-payload claim.