Refresh the Divergence Ledger and Clear Three Spent Backlog Claims - #641
Merged
Conversation
The ledger is a live pass over each repo's ground-truth branch, so the committed copy is only as current as its last run, which was 2026-08-06. Regenerating it moved three rows: AGENTS.md "Fleet Bootstrap" is now divergent at Blog and HomeAutomation-Config, and GOVERNANCE.md "Verification Discipline" and "Workflow YAML Conventions" widened from one repo to four. The reason TODO.md gave for regenerating did not survive the run. It said the committed copy still rendered repo-config/configure.sh under a re-vendor disposition, and that copy already carried retire, so the warning was true of the decision rather than of the file. The line now says why the file goes stale at all and records what this run actually moved. Two spent claims go with it. The "Verified Complete, Awaiting Close" entry for #578 is deleted, since #578 closed on 2026-08-08 and the part the fleet still owes is carried by the re-vendor entry, which names all three sections it touches. The README rework's State read backlog, which is not one of the four values this file defines, and it is now decision, on where Build Artifacts belongs, which is the only thing in that cluster a hub pull request settles. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Regenerates the fleet divergence ledger and updates TODO.md to reflect current backlog state by clarifying one cluster’s selection status, updating the divergence-regeneration rationale with current findings, and removing a now-closed “awaiting close” issue entry.
Changes:
- Update the README structure rework cluster in
TODO.mdtoState: decisionand clarify what is (and isn’t) hub-selectable work. - Refresh the “regenerate divergences ledger” note in
TODO.mdwith the actual results from the 2026-08-09 regeneration. - Regenerate
reports/divergences.mdto reflect current divergence counts/targets (including new/widened rows).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| TODO.md | Clarifies cluster state and selection semantics; updates the divergence-regeneration rationale; removes the now-closed #578 “awaiting close” entry while keeping remaining references intact. |
| reports/divergences.md | Updates the generated divergence ledger to current measured divergence rows and counts. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
ptr727
added a commit
that referenced
this pull request
Aug 9, 2026
… Gates (#643) Three commits, all backlog bookkeeping and local tooling. No rule changes meaning, and nothing here alters what CI gates. **#640, the tagline question.** #577 asked that the tagline be a distinct thing from the intro so a README may carry a second paragraph without the cap or the mirrors reaching it. That shipped in `c2ce145` (#632), so the issue is closed against it. Grepping the number before closing found `TODO.md` had also given #577 to a different entry, the README-to-About hop, which the issue's body never covers. That hop now carries #639 of its own. **#641, the divergence ledger.** `reports/divergences.md` is a live pass over each repo's ground-truth branch, so a committed copy is only as current as its last run. Regenerating moved three rows: `AGENTS.md` "Fleet Bootstrap" is now divergent at Blog and HomeAutomation-Config, and `GOVERNANCE.md` "Verification Discipline" and "Workflow YAML Conventions" widened from one repo to four. The reason `TODO.md` gave for regenerating did not survive the run and is corrected. Two spent backlog claims went with it. **#642, the pre-commit hook.** The chore was to reconsider whether the hook should run the doc gates now that they are diff-scoped. Measuring first found this repository had no hook at all, while `GOVERNANCE.md` and `scripts/README.md` both described what one runs. There is now a committed `.husky/pre-commit` running the prose gate diff-scoped and the line-ending check repo-wide, with the `.gitattributes` and `.editorconfig` pins that `GOVERNANCE.md` "Line Endings" makes mandatory for an extensionless hook. The formatting half the fleet convention names is deliberately absent, and that is the finding worth carrying: this repository declares `[tool.ruff]` in `pyproject.toml` and `spec/project-types.json` declares `python.ruff.config`, yet no workflow runs ruff and the tree does not pass it, at 13 of 57 files unformatted and 106 lint errors. A ruff step would have blocked every commit from the moment it landed. The `GOVERNANCE.md` bullet now states the condition rather than a tool list, that a repo adds each half once its tree passes that half, and the measurement is recorded as a `TODO.md` chore. ## Carried content in this promotion `GOVERNANCE.md` "Running the Linters Locally" changed, and that section is carried `verbatim`, so every downstream copy is byte-mismatched until the next fleet visit. It rides the re-vendor entry already tracked under `TODO.md` "Fleet Sweeps" rather than owing a sweep of its own. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.
Maintenance, in three parts, none of which changes a rule.
The ledger is regenerated
reports/divergences.mdis generated by a live pass over each repo's ground-truth branch, so a committed copy is only as current as its last run, which was3f91868on 2026-08-06. This run moves three rows:AGENTS.md"Fleet Bootstrap" is now divergent at Blog and HomeAutomation-Config, andGOVERNANCE.md"Verification Discipline" and "Workflow YAML Conventions" widen from one repo to four. The fleet re-vendor sweep reads this file as its work list, so it wanted regenerating before the sweep rather than during it.The reason
TODO.mdgave for regenerating did not survive the run, which is the more useful finding. It said the committed copy still renderedrepo-config/configure.shunder a re-vendor disposition that the retirement decision replaced. That copy already carriedretire, so the warning described the decision rather than the file, and a session acting on it would have gone looking for a row that was already correct. The line now states why the file goes stale at all and records what this run moved.Two spent claims are cleared
The "Verified Complete, Awaiting Close" entry for #578 is deleted, since #578 closed on 2026-08-08. Deleting it loses nothing the fleet still needs: the re-vendor entry under "Fleet Sweeps" already names all three
GOVERNANCE.mdsections the #578 widening touches, and it keeps the[issue-578]reference definition in use.The README rework cluster's
Statereadbacklog, which is not one of the four valuesTODO.mddefines at the top of the file, so a reader following the selection procedure had nothing to match it against. It is nowdecision, on where## Build Artifactsbelongs, which is the only thing in that cluster a hub pull request settles. The four conformance entries above it are named as landing on downstream visits, in the sense "Fleet Sweeps" gives that phrase.Verification
scripts/prose_lint.pyas CI invokes it (. --check charset --check semicolon ...) exits 0,scripts/repo_gate.pyreportseol,eol-coverageandsha-pinclean,editorconfig-checkerexits 0, andmarkdownlint-cli2reports 0 issues over both files. Both files are CRLF and stayed CRLF.One note for a future run, since it cost a confusing minute here: pointing
prose_lint.pyatreports/divergences.mdby path reports 12dashviolations, because naming a file explicitly bypasses theGENERATED_TREESexemption that holdsreports/out of the corpus. The generator's own phrasing is not an author's, which is what that exemption is for, and the CI invocation scans.and is unaffected.🤖 Generated with Claude Code