Layer gate: explicit token for pure application-layer integration merges - #381
Merged
Conversation
…gration merges The existing hatches (commercial paths, distribution authoring, test-only, forced cleanup) all assumed integration merges ride other work. A PURE application-layer integration — landing an application/* integration branch's accumulated verbs onto master — had no legal path: the head-name rule blocks application/* heads, and the kernel-first rule blocks application/ diffs without a hatch. Rather than gaming an existing hatch with a token commercial file, the path is made explicit and auditable: a PR body carrying [coordinated-integration] plus a written rationale is allowed through the kernel-first path rule, with a loud ::notice for reviewers. Mirrors the [skip-prod-style] body-token convention already established by the testing-strategy gate. The head-name rule stays strict — integration PRs use a properly named branch, not application/* directly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The existing hatches assumed integration merges always ride commercial work — a pure application-layer integration (the studio-cli verbs landing on master) had no legal path. This adds the auditable one: [coordinated-integration] in the PR body plus written rationale, with a loud ::notice for reviewers. Mirrors the [skip-prod-style] convention. The head-name rule stays strict.
Prepares the studio-cli → master integration merge that follows.
🤖 Generated with Claude Code