Close the Tagline Question and Give the About Hop Its Own Number - #640
Merged
Conversation
#577 asked that the tagline be stated as a distinct thing from the intro, so that a README may carry a second paragraph without the cap or the mirrors reaching it. That shipped in c2ce145 (#632) across all three surfaces the issue named, so the issue is closed against it. Grepping the number before closing found it in a second place: "The Declared Repository Description" had given #577 to its README-to-About hop entry, work the issue's body never covers. That entry now carries #639 of its own, so a closed number stops standing in for open work. The "Recorded for the Maintainer" bullet that held #577 behind the declared description is deleted rather than rewritten, since the action it recorded is taken. Its reasoning did not survive the check: the extraction rule it feared writing already existed for the About and Docker Hub mirrors, so narrowing the HISTORY.md mirror to match it was one line rather than a new parser. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR performs backlog housekeeping in TODO.md by closing out the resolved tagline question (#577) and assigning the README-to-About mirror work its own dedicated tracking issue (#639), preventing a remaining TODO entry from pointing at a now-closed and out-of-scope issue.
Changes:
- Update the “Close the README-to-About hop” TODO entry to reference #639 instead of #577, with rationale for the split.
- Remove the “Recorded for the Maintainer” bullet that tied #577 to the declared-description sequencing.
- Add the
[issue-639]reference definition to the link list.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Uh oh!
There was an error while loading. Please reload this page.
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 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.
Backlog bookkeeping for a question that is settled, and for a number that was doing two jobs.
#577 asked that the tagline be stated as a distinct thing from the intro, so a README may carry a second paragraph without the 100-character cap or the mirrors reaching it. That is what shipped in
c2ce145(#632):spec/readme-structure.mditem 1 states that further paragraphs below the tagline are free prose read by no mirror,CODESTYLE.mditem 4 narrows theHISTORY.mdmirror to the tagline alone, andspec/audit.pyextracts the first line of the intro region under a self-test that names the two-paragraph case. #577 is closed against that evidence.Grepping the number before closing it found it in a second place. "The Declared Repository Description" had given #577 to its README-to-About hop entry, which is work the issue's body never covers, so closing the issue on its own correct evidence would have left that entry pointing at a closed number. The hop now carries #639 of its own and the entry cites it.
The "Recorded for the Maintainer" bullet that held #577 behind the declared description is deleted rather than rewritten, because the action it recorded is taken. Its reasoning did not survive the check either: the extraction rule it feared writing already existed for the About and Docker Hub mirrors, so narrowing the changelog mirror to match it was one line rather than a new parser, which is recorded on the closing comment so it is not re-derived.
Verification
scripts/prose_lint.py,scripts/repo_gate.py(eol,eol-coverage,sha-pin),editorconfig-checkerandmarkdownlint-cli2all pass on the working tree. The file is CRLF and stayed CRLF, whicheditorconfig-checkeris the gate that would have caught.Closes#577
🤖 Generated with Claude Code