Document the local verification loop for content and server changes

[ptr727]

CI proves the render half of the URL contract and cannot prove the other 917. A redirect is the web server's job, and the validation workflow has no server to point at, so a change to the Caddy config or a generated map is invisible to it. The workflow goes green while the redirect it broke stays broken until someone follows an old link.

OPERATIONS.md gains a "Local Verification Before a Pull Request" section naming which paths require a local release and live check first, and why each one does:

Path	Why
deploy/Caddyfile	Rule order is load-bearing, and an over-matching regex is silent
deploy/maps/	A regenerated map can lose entries and still parse
content/, static/	A moved page turns a redirect destination into a 404 the build gate does not follow
hugo.yaml, layouts/	Permalink changes move URLs underneath the redirects pointing at them

The loop was run, not written from memory. Against the current build it reports PASS - 1245 URLs honored, which is the output quoted in the new section.

That also settles a residual delta in the audit, which recorded the redirect half as asserted rather than proven. It is now proven against a running server, though only the local mirror and only by hand. CI still cannot enforce it, and that stays true until staging exists, so the report says so rather than claiming the gap is closed.

[Copilot]

🟡 Not ready to approve

There are a couple of documentation statements in the changed hunks that are currently inaccurate/unclear about which script performs the release step and about “needing an argument,” which could mislead the local verification procedure.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Pull request overview

This PR updates the operational and audit documentation to explicitly describe the required local verification loop for changes that can silently break redirects or URL mappings, clarifying why CI alone can’t validate those behaviors.

Changes:

• Adds a new “Local Verification Before a Pull Request” section to document when to run a local release + live URL check.
• Updates the audit report to reflect that the redirect half is verified locally against a running server (but remains non-automatable in CI without staging).

File summaries

File	Description
reports/Blog/audit.md	Updates the URL-contract audit narrative to reflect local live redirect verification and its limits.
OPERATIONS.md	Documents the pre-PR local verification loop and the path categories that require it.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 2
• Review effort level: Lite

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

[Copilot]

🟡 Not ready to approve

The new OPERATIONS.md table contains an inaccurate hard-coded count (“11 redirect rules”) for deploy/Caddyfile, which should be corrected to keep the documentation factually accurate.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Review details

Suppressed comments (1)

OPERATIONS.md:40

• The table row claims deploy/Caddyfile has “11 redirect rules”, but the current deploy/Caddyfile contains 13 redir directives (e.g., redir @post_id ... through redir @mapped ...). This hard-coded count is inaccurate and likely to drift; consider removing the specific number (or updating it) so the doc stays correct.

| [`deploy/Caddyfile`](./deploy/Caddyfile) | The 11 redirect rules. Rule order is load-bearing, and a regex that matches too much is silent. |

• Files reviewed: 2/2 changed files
• Comments generated: 0 new
• Review effort level: Lite

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

[ptr727]

Answering the suppressed comment from the review on 6411634, since it carries no thread to reply in.

Accepted, the count was wrong. deploy/Caddyfile carries 13 redir directives, not 11:

38 redir @post_id      43 redir @post_child_feed   46 redir @post_child
49 redir @term_feed    53 redir @site_feed         56 redir @blogger_feed
61 redir @blogger_archive  64 redir @blogger_page  69 redir @date_archive
74 redir @author       77 redir @label            82 redir @uploads
84 redir @mapped

Fixed in b89540b by removing both counts rather than correcting them. That cell exists to say why the Caddyfile needs a running server, not to enumerate it, and a number in prose that has to track a config file drifts the moment either changes.

The same imprecision exists in deploy/README.md ("11 regex rules plus 5 map files"), which is not in this change. Recorded in TODO.md for a proper re-derivation rather than fixed by guess, because the R1 to R11 numbering does not map one-to-one onto the directives and deserves working out rather than a patched number.

Noting for the record that this finding sat in the collapsed review body with no review thread, so a loop polling only unresolved threads would have reported a clean pass while it stood. That is the case the merge gate's third precondition calls out explicitly.

[Copilot]

🟢 Ready to approve

The changes are documentation-only, consistent with the repo’s existing CI behavior, and accurately separate local proof from CI enforcement.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 0 new
• Review effort level: Lite

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.