40.01: re-point the engagement after-clock at the rebuild SHA

[pftg]

Docs-only. Caught by a scheduled /okf:okf maintain tick.

The blog rebuild landed in three merges today — f80de8088 (index + tag
pages), f3f9353b6 (Phase 0 instrumentation + tooling), e1fa5409d (the post
template rebuild). 40.01's ship marker still named the first as the
after-clock trigger, so the 28-day engagement window would have started
measuring a blog that was still two-thirds old — precisely the error the
whole-blog measurement pivot was meant to avoid.

• After-clock re-pointed at e1fa5409d (last merge that changes the
  measured thing).
• Read date now derived from the actual deploy rather than pinned to a guessed
  2026-09-17 — a delayed deploy shifts the window, it doesn't shorten it.
• Title/scope updated from "the before for phases 2.1+2.2" to "for the
  whole-blog rebuild", matching the pivot.

Generalised in .okf/log.md: a ship marker written mid-sprint ages badly, and
the tell that it's stale is the doc still describing its own scope in
pre-pivot phase language.

bin/hugo-build green; OKF conformant under --strict.

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 97ad6a35-f272-45d4-b077-4e895db79f51

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}