feat: name the exact checks and reviews behind ci-changed/review-changed details

[diegomarino]

Resolves the two TODO(v0.2) notes in lib/cli.mjs detail rendering: ci-changed and review-changed details previously exposed only an opaque digest transition, forcing agents to re-query GitHub to learn what changed.

What changed

Persisted normalized summaries. The PR fingerprint now stores two compact, detail-only fields in the snapshot:

• ciChecks — sorted {name, status, conclusion} rows (normalizes both CheckRun and StatusContext rollup shapes)
• reviewSummary — sorted {author, state, submittedAt, commit} rows from latestReviews

Named detail breakdown. With --detail, ci-changed / review-changed (and the updated catch-all) keep their digest from/to and gain added / removed / changed arrays:

{
  "class": "ci-changed",
  "field": "ci",
  "from": "b6e7d0bc0ba1",
  "to": "632f7f45b0b2",
  "added": [{ "name": "lint", "status": "IN_PROGRESS", "conclusion": "" }],
  "removed": [{ "name": "docs", "status": "COMPLETED", "conclusion": "SUCCESS" }],
  "changed": [{ "name": "build", "from": { "status": "COMPLETED", "conclusion": "FAILURE" }, "to": { "status": "COMPLETED", "conclusion": "SUCCESS" } }]
}

opaque: true remains only as the fallback when the detail cannot name the change (a from side written before summaries existed, or a digest diff the summary does not explain).

Compatibility

• No phantom deltas on upgrade: comparableFingerprint drops the summaries, so a pre-summary snapshot compares equal to a current fetch of the same state; the first tick just persists the summaries.
• Stable delta ids: the summaries are excluded from deltaIdentity, so the same observed change yields the same content-addressed id from legacy and new snapshots (cross-monitor dedupe survives mixed versions). Verified end-to-end.
• Frozen digests: canonicalizeCiRollup now derives from summarizeCiRollup (digest and summary can never disagree) and a test freezes the digest values byte-identical to the pre-summary implementation.
• Additive contract: DELTA_DETAIL_FIELDS gains changed; no schemaVersion bump per the documented policy.

Docs

docs/contract.md (detail shapes, fingerprint table, API exports), --help-json description, and the agent-facing guides (RUNBOOK.md, docs/watch-loop-prompt.md, docs/usage.md) now describe the named breakdown and the opaque fallback. The README example fixtures are documented as exercising the pre-summary fallback path, so no SVG regeneration was needed.

Testing

• npm run check green: lint, prettier, 161 tests (6 new: summarizer normalization/sorting, frozen digests, comparable stripping, named CI/review details, legacy-snapshot upgrade without phantom deltas, id stability).
• Manual end-to-end with the real binary and a stubbed gh over two ticks: named diff output, legacy-snapshot upgrade (exit 0, zero deltas, summaries persisted), opaque fallback, and identical delta ids across snapshot versions.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PGgDzjgxoGajZU7sHJTp81

---

Generated by Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 10b172304b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".