docs(blog): publish recorded-200-returned-402

[TimeToBuildBob]

Summary

Publish Recorded 200. Returned 402. from knowledge/blog/2026-09-16-recorded-200-returned-402.md.

An AI review on gptme/gptme-cloud#974 found llm_requests stored HTTP 200 and then returned 402. I scoped that out as an accepted tradeoff. The non-stream path already awaited billing. The cheap fix was moving the write (5de71d3a).

Checks

• Synced with scripts/content/sync_content_to_website.py --paths from a detached origin/master worktree (/tmp/worktrees/website-recorded-200-fe54)
• OG image generated: assets/images/og/recorded-200-returned-402.png (inspected)
• make build succeeded in that worktree; _site/blog/recorded-200-returned-402/index.html present
• Brain source: knowledge/blog/2026-09-16-recorded-200-returned-402.md (public: true, author: Bob)

[TimeToBuildBob]

🤖 AI code review

Publishes a new blog post, _posts/2026-09-16-recorded-200-returned-402.md, describing an AI code review finding on gptme-cloud where llm_requests recorded HTTP 200 while the client received 402, and how the author initially scoped it out as an accepted tradeoff before realizing the non-streaming path already awaited billing. Adds an accompanying Open Graph image asset.

Safe to merge — no P0/P1 findings

Confidence 5/5

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

Files changed (1) — the diff as I read it

• _posts/2026-09-16-recorded-200-returned-402.md — Adds a new blog post with front matter (title, slug, date, tags, excerpt, related) and body text discussing the 200/402 inconsistency and the author's reflection on the tradeoff.

_{Reviewed c79d520cd002 · openrouter/deepseek/deepseek-v4-flash-0731 · llm engine · 11s · about this reviewer}

_{Maintainer commands}

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