Record the promotion, and retire a done item the file still lists as next

[ptr727]

State drifts silently, so this records where things stand after the 2026-08-09 promotion rather than adding work. Documentation only.

A done item was still listed as next

git restore-mtime has been in deploy-site-task.yml since #65, and TODO.md still carried it under Next, in dependency order as unstarted. Marked done, measurement kept, and the part that is genuinely still ahead named: the next production deploy is the first to exercise it, and therefore the first where a badly moded file can ride a hard link into every later release. The live media check landed before it deliberately, and is what watches for that.

What the promotion did

A Branches row in the State table: main carries every commit on develop, the content diff is empty, and nothing published — no run fired on main and 1.0.11 is still the newest release. That last part is recorded because a promotion that correctly publishes nothing looks identical to one that failed to.

The hub

"Owed to the hub" no longer reads "Nothing".ptr727/ProjectTemplate#633 is filed, and the offer to port checks/check-eol-pins.py into the hub's scripts/ is owed only if the hub wants that shape. Marked do not start, because the open design question changes the code rather than just delaying it: the dead-pattern direction cannot be lifted unmodified, since a carried baseline forward-declares pins for files its consumers will have and the template itself does not.

Added to the hub table with what it means here — that gate reported 0 issue(s) against the exact tree carrying both defects #69 fixed, and where a repo sets [*] end_of_line = lf, as this one does, it is vacuously satisfied by any pin at all.

Three traps

Each was hit this session and none is mechanically preventable, which is what qualifies them:

• A review that exists on the head is not a finished review.pr_review.py wait returned in one second, an independent poll agreed at zero unresolved, and Copilot posted a finding after both reads. Every query was correct and every query was early. A very short waited= is the tell.
• A rule naming a target that does not exist reads as coverage. Gated for this file now; the generalisation is gated nowhere.
• A gate is only as good as its matcher, and a wrong matcher fails quietly. Two defects in one function, both found by review rather than by the gate. Hence comparing against git check-attr rather than against the documentation.

One new item

checks/README.md has been the authority for its directory since #66 and names one of the three gates in it. Either a section naming the other two, or an explicit statement that the file is scoped to the URL contract. The present state reads as complete while not being.

Verification

markdownlint-cli2 clean, editorconfig-checker clean, and both checks/ gates pass. No non-documentation file is touched.

[Copilot]

Pull request overview

Documentation-only update to TODO.md to reflect the repo’s current state after the 2026-08-09 develop → main promotion, and to retire/clarify items that were still recorded as “next” despite already being completed or already filed upstream.

Changes:

• Update the State table with explicit CI gate inventory and a new Branches row capturing the 2026-08-09 promotion outcome (including “nothing published” context).
• Mark the git restore-mtime CI work as Done (linked to #65) and refine the “Owed to the hub” section to reflect the newly filed upstream issue (#633) and its conditional follow-up.
• Add/extend “Traps” entries and append missing PR/issue reference links.

---

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