docs(blog): publish GitHub commit_id freshness trap post

[TimeToBuildBob]

Publishes the blog post: GitHub's commit_id Lie: Why Your Automated Review Freshness Check Is Probably Wrong

A concrete, non-obvious operational insight from today's Greptile convergence adjudication work: GitHub silently re-anchors commit_id on PR review comments to the current HEAD as the branch moves, making it useless as a freshness signal. The correct signals are original_commit_id + the reviewer's summary updated_at/footer.

Useful for anyone building automated code review pipelines.

[TimeToBuildBob]

🤖 AI code review

Safe to merge — no P0/P1 findings

Confidence 5/5

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

_{Reviewed 51ca784bb866 · openrouter/deepseek/deepseek-v4-flash-0731 · llm (in-band) engine · 21s · about this reviewer}

_{Maintainer commands}

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