docs(kdo): authorize H2-R1 legacy test reconciliation

[TheHalfMoon]

Supplemental docs-only authorization for KDO-H2-R1 legacy test reconciliation.

Canonical base: 04cea3fef169411d267100fc510e7d5695bceb23
Related implementation PR: #45
Observed implementation head: 9b62f0c8bcb4e6027545ef69cbfabb5f5e48eed7

This PR changes exactly one documentation path and authorizes only three additional legacy test paths for later reconciliation in PR #45 after this authorization becomes canonical.

It does not modify PR #45, runtime code, tests, provider transports, K2, Done Gate, or evidence ledger state.

Do not merge automatically. Founder review and required governance/review gates are required.

---

Summary by cubic

Adds a docs-only supplemental authorization to reconcile three legacy tests with H2-R1 model-visible request semantics for related implementation PR #45. Old tests assumed no durable user prompt and no model.request.snapshot; H2-R1 requires a durable, lossless snapshot appended before provider execution. No production scope expands.

• Adds docs/planning/KODAC_KDO_H2_R1_LEGACY_TEST_RECONCILIATION_AUTHORIZATION_2026-08-14.md.
• Authorizes PR feat(kdo): implement H2-R1 model-visible request reconstruction #45 to change only:
  • packages/kodac-runtime/test/ask-cli.test.ts
  • packages/kodac-runtime/test/model-capabilities.test.ts
  • packages/kodac-runtime/test/model-turn.test.ts
• No runtime code, provider transports, registries, or ledger behavior changes beyond the existing H2-R1 allowlist.
• Reconciled tests must assert: model.request.snapshot is recorded before provider execution; the exact model-visible request is reconstructable; response/assistant evidence stays coarse (no raw assistant content); failure before snapshot does not persist private prompts.
• Keep PR feat(kdo): implement H2-R1 model-visible request reconstruction #45 in Draft; do not add the evidence ledger until the reconciled head is green across required gates; do not auto-merge this PR.

^{Written for commit 0442fca. Summary will update on new commits.}

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 5 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 Plus

Run ID: b6a647a8-773f-48f1-9edf-7e5518aeb2e2

📥 Commits

Reviewing files that changed from the base of the PR and between 04cea3f and 0442fca.

📒 Files selected for processing (1)

• docs/planning/KODAC_KDO_H2_R1_LEGACY_TEST_RECONCILIATION_AUTHORIZATION_2026-08-14.md

---

_{Comment @coderabbitai help to get the list of available commands.}