Repository navigation
Document board readiness, holds and issue closure - #345
Merged
Merged
Conversation
This was referenced Nov 3, 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 this changes
Explains native blockers, explicit holds, issue/PR status tracking and complete-scope closing links in the contributor documentation. Replaces the retired workflow reference with the new board runbook.
Why
Part of #340. Companion to #344; merge #344 first so the workflow and runbook links resolve. Hosted automation acceptance stays open in #340.
Zone
docsonly.docs/ONBOARDING.md: replaces obsolete readiness limitations with the current blockers, hold and closure policy.docs/DEVELOPMENT.md: points the contributor PR workflow to the replacement automation and activation instructions.How to verify
Read the getting-work and PR-workflow sections against #344's runbook.
git diff --checkpassed, and link targets were checked against that companion change. The complete cleanup passedmake check; this PR changes only prose.Checklist
stagingand targetsstaging.Deployment notes
Merge after #344. No service deployment settings change.