v5.8.2 — Demo ready: --assert-env flag + offline demo kit

[JosephOIbrahim]

Closes the last un-built demo item and ships the offline rehearsal kit. (Bundles the offline demo kit that was held on a brightline review — content clean, cleared to ship.)

Added

• agent diagnose --assert-env <hash> — protect a frozen demo box with its own tool ("we use the tool to protect the demo of the tool"). Record the fingerprint at Thursday rehearsal, assert it Friday morning: exit 0 unchanged, 3 drifted, 2 undeterminable. Reads a fresh worker fingerprint, falls back to the last report when the worker is unreachable. Keyless. This closes the un-built half of Demo Gate condition 6 (a DISPATCH KEEP-list item).
• Offline demo kit (demo/) — seed_diagnosis_demo.py reproduces the run-report store keyless (3 clean baselines + 1 OOM break; no ComfyUI, no API key); DIAGNOSIS_RUNBOOK.md is the five-beat runbook rewritten to rehearse fully offline, each beat tagged offline-reproducible vs server-gated, with real captured output.
• README — baseline-bootstrap line in the run-reports section.

Verified

• --assert-env live against the real box: match → 0, wrong hash → 3, --json clean.
• +6 tests; full suite 4821 passed, 2 skipped (zero regressions).

Demo Gate after this

Conditions 2–5 offline-certified; the beat-2 live timing table is demonstrable (bridge confirmed installed); condition 6's assertion is now one command. Only the genuinely frozen-box items remain: condition 1 (twice-through) and the backup video.

🤖 Generated with Claude Code

https://claude.ai/code/session_01T5Uf4eyeqC9K9eZSesVLrp

[coderabbitai]

Warning

Review limit reached

@JosephOIbrahim, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 42b74712-e21b-40e4-aa09-e7d075b21b82

📥 Commits

Reviewing files that changed from the base of the PR and between 3f6ceba and f54c57b.

📒 Files selected for processing (8)

• CHANGELOG.md
• README.md
• agent/__init__.py
• agent/cli.py
• agent/diagnosis/cli.py
• demo/DIAGNOSIS_RUNBOOK.md
• demo/seed_diagnosis_demo.py
• tests/diagnosis/test_assert_env.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/demo-readiness

---

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.}