Skip to content

Re-vendor the Carried Rule Sections From the Current Hub - #89

Merged
ptr727 merged 1 commit into
developfrom
resync-the-instruction-set
Aug 10, 2026
Merged

Re-vendor the Carried Rule Sections From the Current Hub#89
ptr727 merged 1 commit into
developfrom
resync-the-instruction-set

Conversation

@ptr727

Copy link
Copy Markdown
Owner

Step 1 of a resync, per the hub's RESYNC.md section 3: the instruction set first, because it is the rules every later step is judged against.

Hub read at main = d9b5ffa. This is the first of several focused pull requests rather than one sprawling change, per that file's section 6.

What was stale

Thirteen verbatim units had fallen behind the hub canonical, and one had never arrived at all:

FileSections
AGENTS.mdFleet Bootstrap, Where the Rules Live
GOVERNANCE.mdBranching Model, Communicating with the User, Documentation Style Conventions, Operational Repositories, PR Review Etiquette, Release Model, Repository Boundaries and Write Safety, Repository Details, Verification Discipline, Workflow YAML Conventions
GOVERNANCE.mdHub-Hosted Tooling — absent, never carried
whole file.markdownlint-cli2.jsonc, matched a past hub revision

Hub-Hosted Tooling is inserted after Operational Repositories, which is its position in the hub's declared order once the hub-only Repository Onboarding and Conformance section is excluded. This repo correctly does not carry that one.

Two sections come from the corrected canonical deliberately

Repository Boundaries and Write Safety and Branching Model are taken from the hub revision that stops citing repo-config/configure.sh as a repo-local path. The previous canonical carried a dead relative link to a file this repo does not have, so re-vendoring from it would have required a second pass over the same two sections.

Verification

Every unit is checked by the audit engine's own content hash against origin/main, not by eye: 21 of 21 verbatim sections plus the whole-file unit match.

That mattered. An inserted section looked byte-identical in a diff and failed the hash on the blank line before the following heading, which splitlines() hides. Only the hash caught it.

Line endings are LF throughout, matching this repo's declared lineEndings rather than the hub's CRLF, verified byte-wise per file after writing.

Still to come, as separate pull requests

  • Delete repo-config/configure.sh, with the inbound-reference sweep the hub's RESYNC.md section 4 requires.
  • Carry host-tools.json, a baseline file the hub added, currently one LETTER on all 22 cataloged repos.
  • README structure: a retired section name, unsorted link groups, and four 3rd Party Tools description mismatches.

🤖 Generated with Claude Code

Thirteen verbatim sections had fallen behind the hub canonical and one had never
arrived. Fleet Bootstrap and Where the Rules Live in AGENTS.md, and eleven
sections in GOVERNANCE.md, are copied from the hub. Hub-Hosted Tooling was absent
and is inserted after Operational Repositories, which is its position in the
declared order once the hub-only Repository Onboarding and Conformance section is
excluded.
.markdownlint-cli2.jsonc is a whole-file verbatim unit that matched a past hub
revision, so it is replaced by the current canonical.
Two of the sections, Repository Boundaries and Write Safety and Branching Model,
are taken from the hub revision that stops citing repo-config/configure.sh as a
repo-local path. The earlier canonical carried a dead relative link to a file this
repo does not have, so re-vendoring from it would have needed a second pass.
All 21 verbatim sections and the whole-file unit are verified by the audit's own
content hash rather than by eye, which is what caught an inserted section that
looked identical and differed by the blank line before the next heading. Every
file is written LF to match this repo's declared line endings rather than the
hub's CRLF.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CopilotAI lite review requested due to automatic review settings August 10, 2026 21:51

CopilotAI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR re-vendors the carried governance/instruction-set content to match the current hub canonical, ensuring the repo’s agent-facing rules and lint configuration are up to date before subsequent resync steps.

Changes:

  • Updated carried sections in GOVERNANCE.md, including expanding “Repository Boundaries and Write Safety”, adding the previously-missing “Hub-Hosted Tooling” section, and refreshing multiple governance subsections.
  • Updated AGENTS.md to align the “Fleet Bootstrap” procedure and the “Where the Rules Live” section map with the hub.
  • Refreshed .markdownlint-cli2.jsonc comments to match the hub revision (no functional rule changes).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

FileDescription
GOVERNANCE.mdRe-vendors multiple governance sections; adds “Hub-Hosted Tooling” and updates operational/review/verification guidance.
AGENTS.mdAligns fleet bootstrap/resync procedure pointers and updates the governance section map.
.markdownlint-cli2.jsoncComment-only refresh consistent with the hub canonical.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@ptr727
ptr727 merged commit d6f0f10 into developAug 10, 2026
5 checks passed
@ptr727
ptr727 deleted the resync-the-instruction-set branch August 10, 2026 21:56
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ptr727