Record M7a as done, since production is serving a release

[ptr727]

TODO.md only.

Found by the review on #56, which caught the file contradicting the description of its own promotion. The State table and the dependency list both still said production served 0000-placeholder and that the first deploy was pending. It deployed on 2026-08-08 and serves 20260808-041050.

This is the staleness I flagged while rebasing #37 and chose not to bundle into a rebase. It should have been its own change immediately rather than a note, and this is that change.

Three places said it

• The State row now records the release, and that the host side verified it independently: 9/9 unauthenticated, with the built baseURL read from the deployed bytes rather than from this repo's config, across a 3,095-request gate run with no unexplained 404s.
• The production item leads with M7a done and reframes its sub-items as where this repo stands against M7b, two owed and one already answered, rather than as work standing before a first deploy that has since happened.
• The robots decision is now due before the cutover rather than before the first deploy, and its 404 is measured after that deploy rather than predicted before it.

Merge before #56

#56 promotes develop to main and its description states production serves 20260808-041050. Landing this first makes the file agree with it; landing #56 first promotes the contradiction.

Verification

markdownlint-cli2, editorconfig-checker and cspell clean on TODO.md. Documentation only, so the local mirror gate does not apply — and it was run on this tip anyway as part of #56: PASS - 1245 URLs honored.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Updates the repository’s running backlog (TODO.md) so it accurately reflects that production (M7a) has already been deployed and is serving a real release, aligning the state file with the current operational reality ahead of the develop -> main promotion work.

Changes:

• Update the State table to record that VPS production is serving release 20260808-041050 (M7a done 2026-08-08) and note the independent host-side verification.
• Reframe the “Deploy production once” dependency item to reflect that production deployment is complete and the remaining work is now M7b (.com cutover).
• Adjust the robots.txt decision text to be “before cutover” (measured post-deploy) rather than “before first production deploy”.

---

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