docs(policy): move agent-fast / build gate from dev to unstable - #484
Merged
Conversation
Introduce unstable as the qualification branch in the promotion chain (dev -> unstable -> stable) and move the required agent-fast / build status check there. dev remains the topic-integration branch but no longer carries branch-rule status requirements.
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
2 participants
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.
Summary
Introduces
unstableas the qualification branch in the promotion chain and moves the requiredagent-fast / buildstatus check there.Promotion flow: topic branch →
dev→unstable→stableProtection changes:
unstablenow carries theagent-fast / buildrequirement formerly ondevstablestill requiresrelease_okdevremains the topic integration line but is no longer a protected branch with status-check requirementsChanges
agent-policy.jsonaddsqualification: unstableandpromotion_chaindocs/BRANCH_POLICY.md,docs/CI.md,docs/REPO_MAP.mdupdated with the new machine-readable declarations and proseunstable(ci.yml,codeql.yml,documentation.yml)scripts/ci/check_branch_policy.pyvalidates live protection onunstableinstead ofdev, and rejects status-check requirements left ondevscripts/agent/generate-adapters.py,scripts/generate-architecture-catalogs.py,scripts/agent/check-change.pyupdated to know about the qualification branchAGENTS.md,.claude/policy-brief.md,.cursor/agent-policy.md,docs/branch-policy.json) and the architecture catalog regeneratedscripts/hooks/pre-push.shprotects direct pushes tounstablescripts/agent/test_check_change.pyandscripts/ci/test_check_branch_policy.pyOperator follow-up
GitHub branch protection rules still need to be applied on the remote:
unstablebranch (if it does not exist yet)agent-fast / buildrequired status fromdevtounstabledevrelease_okonstableTest plan
python3 scripts/agent/check-change.py --base origin/dev— pass (changelog, source_integrity, architecture_catalog, policy_adapters)python3 -m unittest scripts.agent.test_check_change scripts.ci.test_check_branch_policy— 34 tests passpython3 scripts/ci/check_branch_policy.py— passGenerated by Claude Code