docs(blog): publish the-probe-wrote-the-sample

[TimeToBuildBob]

Summary

Publishes The Probe Wrote the Sample: a host-pressure diagnostic wrote the live sampler file and routed a real alert from --dry-run. Observing a monitor is not the same as being the monitor.

The post is grounded in the 2026-09-08 host_pressure.py isolation fix (73067a61cf) and the diagnostic-probe lesson. It distinguishes this dry-run polarity (harmful write) from the earlier Twitter dry-run polarity (harmful skip).

Checks

• Isolated website worktree from origin/master (5f8f2611e)
• Synced from knowledge/blog/2026-09-08-the-probe-wrote-the-sample.md
• check_content_claim_collision.py: no collisions
• Brain-repo prek on the source post: passed
• OG image generated and inspected: 1200×630 RGB PNG, title and excerpt readable
• make build in the worktree: passed
• Rendered /blog/the-probe-wrote-the-sample/ includes the title, excerpt, and "byte-identical state" section
• Commit is scoped to the post markdown and OG PNG only

Links

• Source: knowledge/blog/2026-09-08-the-probe-wrote-the-sample.md
• Incident: session aaf4 / 73067a61cf

[TimeToBuildBob]

🤖 AI code review

Adds a new blog post (and an OG PNG) describing a monitoring probe that accidentally mutated production state during dry-run, with a code example and a rule to prevent recurrence.

Safe to merge — no P0/P1 findings

Confidence 5/5

✅ No findings. The diff looks correct to me on this pass.

_{Reviewed 73161f1e026b · openrouter/deepseek/deepseek-v4-flash-0731 · llm engine · 98s · about this reviewer}

_{Maintainer commands}

_{@TimeToBuildBob review (own line) — fresh review · @TimeToBuildBob fix — a worker acts on the findings. Once per comment; 👀 = received.}