blog: land codex reviewer fixes for OpenClaw first-week post

[amavashev]

Summary

Lands the codex/external-reviewer fixes from PR #564 into main. These were merged into the blog branch after #563 was already merged into main, so the published post still has the older claims.

What's in this PR

A second-round technical pass on blog/openclaw-budget-guard-first-week-dry-run-to-production.md. Six edits, all verified against the integration guide and blog/openclaw-plugin-lessons-learned.md:

1. Frontmatter description rewritten to align with in-post terminology (simulated dry-run, canary cutover decision).
2. Day-1 config example adds analyticsWebhookUrl so readers can copy-and-run a setup that actually delivers the full SessionSummary.
3. Day-1 enableEventLog bullet corrected — eventLog is a field inside SessionSummary, and the practical way to retrieve the full summary is via analyticsWebhookUrl or a wrapper reading ctx.metadata, not log scraping.
4. Day 2–3 opener tightened: "can POST" → "POSTs ... when configured".
5. Operational-readiness row — replaced BudgetExhaustedError/ToolBudgetDeniedError class names with the observable forms (model block, tool reservation denial, call-limit block, access-list block). Per Lesson 2 of the lessons-learned post, BudgetExhaustedError doesn't surface as such in OpenClaw logs — the plugin redirects to __cycles_budget_exhausted__ and the reader sees a provider "Unknown model" error.
6. Rollback signal Add new documentation pages to VitePress navigation #1 — important catch: high-budget plugin dry-run is a call-shape predictor, not a denial-rate baseline. With dryRunBudget: 1000000000, you're intentionally avoiding the wall. Original framing implied dry-run gives you a comparable denial rate; it doesn't.
7. Rollback signal Add comprehensive documentation for Cycles protocol and client #3 — same correction as Add comprehensive deployment guide and admin server documentation #5 propagated to the rollback list (__cycles_budget_exhausted__ model failure rather than BudgetExhaustedError).

Test plan

• Build the site locally (npm run dev) and confirm the post renders without VitePress errors.
• Confirm the new frontmatter description renders in /blog/ listings and OG metadata.
• Verify all internal links still resolve (no link content changed in this round, but worth a quick spot-check).
• Spot-check that the Day-1 JSON config is still valid JSON after the analyticsWebhookUrl addition.

Related

• Original PR (already merged): blog: OpenClaw budget guard first-week operator playbook #563
• Codex review PR (merged into the blog branch, not main): [codex] fix OpenClaw dry-run rollout guidance #564