Re-vendor the eight verbatim carries the hub advanced past - #11
Merged
Conversation
The hub's first audit of this repo (ProjectTemplate#547) found eight verbatim units behind the canonical at hub main `3a7cc64`. Six are stale copies and two never arrived at all, and the distinction matters, because a stale copy still states the rule in an older form while an absent one states nothing. ## Absent, so this is the first time the rule lands here - `AGENTS.md > Fleet Bootstrap` says where the canonical rules live and routes by the state this repository is actually in. Without it, an agent starting here has nothing telling it the hub exists. - `GOVERNANCE.md > Representative Data in Agent-Authored Text` is the rule that agent-authored text illustrates with constructed data rather than with data observed in the maintainer's environment. ## Stale, so the rule was here in an older form - `AGENTS.md > Context and Delegation Discipline` gains the rule that a wait separates three outcomes and says which one it reached. - `AGENTS.md > Where the Rules Live` gains the row routing to the representative-data rule above. - `GOVERNANCE.md > Git and Commit Rules` gains "Commit means commit and push". - `GOVERNANCE.md > Verification Discipline` gains "A launched process is not a result, and a cause nobody observed is not a diagnosis". - `GOVERNANCE.md > PR Review Etiquette` gains the whole "Every Finding Ends in an Action" subsection, so the review loop arrives with the five outcomes that close a finding rather than without them. - `repo-config/configure.sh` takes the payload-driven check mode. The copy here compared the merge methods and the required-status-check contexts by name; the canonical compares every parameterized rule's whole parameters object in both directions, so a rule added live that no payload declares is now caught. TODO.md says not to hand-edit `configure.sh` or the ruleset payloads. Re-vendoring from the hub canonical is the sanctioned exception and the reason that rule exists. The two ruleset payloads are deliberately not touched: ProjectTemplate#545 changed them an hour ago on the hub's `develop`, and ground truth is the hub's `main`, so that one converges when it promotes. The intro line is adjusted from two things to four, because the file now holds the bootstrap as well. ## Verification - Every verbatim unit byte-matches the canonical after LF normalization: the three `AGENTS.md` sections, the eighteen `GOVERNANCE.md` sections, `configure.sh`, and `.markdownlint-cli2.jsonc`. The only two that differ are `Devcontainer` and `Repository Layout`, both intent fidelity. - `repo-config/configure.sh check ptr727/Blog release` exits 0 under the new stricter check mode, so the live rulesets and settings still conform, which is the check that would have caught a bad re-vendor. - markdownlint, editorconfig-checker, and the JSON and prose gates are clean, and all 20 rows of the rules map resolve to a carried section except the one the table itself marks hub-only. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR re-vendors previously stale/absent governance and configuration-carry units from the fleet hub canonical, and tightens the repository configuration audit logic so repo-config/configure.sh check detects previously-missed drift in ruleset definitions and settings verification.
Changes:
- Add the missing Fleet Bootstrap section to
AGENTS.mdand extend the “Where the Rules Live” map to include the new representative-data rule. - Add the missing “Representative Data in Agent-Authored Text” section to
GOVERNANCE.md, plus updates to several governance sections (commit semantics, verification discipline, review-loop closure rules). - Strengthen
repo-config/configure.sh checkto compare ruleset rule-types bidirectionally and compare full parameters objects (with normalization), and harden settings payload parsing to avoid false-clean runs.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| repo-config/configure.sh | Tightens drift detection in ruleset/settings check mode and makes the check logic more robust against silent no-op loops. |
| GOVERNANCE.md | Adds missing representative-data rule and updates review-loop / verification / commit semantics guidance to match the hub canonical. |
| AGENTS.md | Adds missing Fleet Bootstrap routing and updates the rules map to include the representative-data governance section. |
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Aug 3, 2026
The report named `6501479`, the ref the baseline was carried from. The re-vendor in this branch moves every verbatim unit to `3a7cc64`, so the line named a ref the tree no longer matched the moment the rest of this change landed. Co-Authored-By: Claude Opus 5 (1M context) <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 freeto 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.
The hub ran its first audit of this repo (ProjectTemplate#547) and found eight verbatim units behind the canonical at hub
main3a7cc64. This applies them. Six are stale copies and two never arrived at all, and the distinction matters: a stale copy still states the rule in an older form, while an absent one states nothing.Absent, so this is the first time the rule lands here
AGENTS.md > Fleet Bootstrapsays where the canonical rules live and routes by the state this repository is actually in. Without it, an agent starting here has nothing telling it the hub exists, which is exactly how this repo drifted eight units behind without anyone noticing.GOVERNANCE.md > Representative Data in Agent-Authored Textis the rule that agent-authored text illustrates with constructed data rather than with data observed in your environment.Stale, so the rule was here in an older form
AGENTS.md > Context and Delegation DisciplineAGENTS.md > Where the Rules LiveGOVERNANCE.md > Git and Commit RulesGOVERNANCE.md > Verification DisciplineGOVERNANCE.md > PR Review Etiquetterepo-config/configure.shThe
configure.shchange is the one with teeth. The copy here compared the merge methods and the required-status-check contexts by name. The canonical compares every parameterized rule's whole parameters object in both directions, so a rule added live that no payload declares is now caught, where before it passed clean.What is deliberately not in this PR
The two ruleset payloads. ProjectTemplate#545 took
bypass_actorsout of them an hour before this branch was cut, but that is on the hub'sdevelopand ground truth is the hub'smain. It converges when it promotes, and its live half is a settings change on a protected branch, so it is yours rather than mine.TODO.mdsays not to hand-editconfigure.shor the ruleset payloads. Re-vendoring from the hub canonical is the sanctioned exception and the reason that rule exists.Verification
AGENTS.mdsections, the eighteenGOVERNANCE.mdsections,configure.sh, and.markdownlint-cli2.jsonc. The only two that differ areDevcontainerandRepository Layout, both intent fidelity and legitimately ours.repo-config/configure.sh check ptr727/Blog releaseexits 0 under the new stricter check mode, so the live rulesets and settings still conform. That is the check that would have caught a bad re-vendor, and it is why it ran after the overwrite rather than before.🤖 Generated with Claude Code