feat(operability): add bounded control-plane SLI receipts

[seonghobae]

Purpose

Implement issue #903 as a read-only, finite-cardinality control-plane SLI receipt. The collector summarizes queue/defer age, transient retries, writer-collision avoidance, merge latency, protected-main acceptance debt, meta-intermediate continuation, exit-sweep discoveries, genuine run-budget handoffs, and premature-stop recovery outcomes without creating a new authority class or database.

Exact current identity

• base branch: main;
• PR creation base snapshot: 6eb06cdd08c79a06f7b390069d4ffa49e2eb7dba (historical provenance; merge decisions must resolve the live protected base independently);
• exact current head: 0e76ecab99be4f19ca2ac7f02760bf11bc1520d4;
• state: Draft until current source review, complete gates, independent approval, live-base compatibility, and branch protection are satisfied.

Bounded contract

• schema: cwl.control-plane-sli/v1;
• strict ContextualWisdomLab/<repo> and exact 40-hex source revision validation;
• finite reason/failure classes only;
• deterministic output independent of repository/lane ordering;
• rejection of future timestamps, backwards lifecycle transitions, duplicate repository/lane identity, unknown keys, non-finite/duplicate-key JSON, unbounded/user-controlled strings, and authority-conflating fields;
• no PR title, comment body, model output, credential, raw exception text, unrestricted URL/log, or PII in output labels;
• queue age, retry/exhaustion, writer-collision, gate-clean→merge, merge→acceptance, acceptance-debt, meta-continuation, first-exit-sweep discovery, and real run-budget handoff metrics;
• bounded user_redirection_incidents, user_redirection_multi_lane_recoveries, and user_redirection_non_documentation_recoveries, with recovery counts prohibited from exceeding incident count;
• additive backwards compatibility: existing v1 input producers may omit the three new recovery counters and receive canonical zero values, while unknown fields still fail closed;
• read-only local JSON CLI only; no merge/review/model credential and no persistence claim.

TDD evidence

The initial branch deliberately failed before production implementation existed. A later documentation→implementation reconciliation added a new RED contract for same-invocation premature-stop recovery metrics. At exact head 974381ed667ce4909faef5ace3798d8578c04ee9, the focused quality gate failed exactly because the production schema rejected the three new bounded recovery fields as unknown.

The minimum implementation then extended the finite schema and aggregation without adding unbounded labels or authority semantics, followed by negative tests for impossible recovery counts and non-integer counters.

Exact-head quality evidence

Control Plane SLI Receipt Quality CI run 31354848775 checked out exact current head 0e76ecab99be4f19ca2ac7f02760bf11bc1520d4 and completed successfully:

• focused receipt suite: 25 passed;
• production module: 196/196 statements and 68/68 branches at 100%;
• public docstrings: 100.0%;
• complete central suite: 1002 passed, 16 subtests passed;
• compilation and git diff --check: success.

At the most recent exact-head gate refresh, Control Plane SLI Receipt Quality CI, Scorecard PR, Secret Scan, SAST Semgrep, Security Scan, SBOM Generation, OSV-Scanner PR, and Python Security had completed successfully; CodeQL PR was still in progress. Pending evidence is not passing and blocks only this exact lane.

Authority boundary

This receipt is descriptive operability evidence only. It does not infer check success, formal approval, model verdict, merge authority, incident closure, or certification. It introduces no persistent database. Any durable cross-repository continuation/writer store still requires a separate data-model/privacy/tenancy/DR ADR.

Do not mark Ready or merge until every current-head required/security/supply-chain gate is complete and clean, current automated source review has no valid actionable finding, a qualifying independent non-author formal approval exists, the live base is revalidated, and branch protection authorizes the expected-head merge. Protected-main/consumer receipt canaries are required after integration before operational closure.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 28 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f37f4f22-61e4-49a8-85f3-40c0e8d63cd5

📥 Commits

Reviewing files that changed from the base of the PR and between 6eb06cd and 0e76eca.

📒 Files selected for processing (3)

• .github/workflows/control-plane-sli-receipt-quality-ci.yml
• scripts/ci/control_plane_sli_receipt.py
• tests/test_control_plane_sli_receipt.py

---

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

[seonghobae]

@coderabbitai full review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

---

Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 10 minutes.

[seonghobae]

@coderabbitai review

Please perform a fresh semantic source review of unchanged exact head 0e76ecab99be4f19ca2ac7f02760bf11bc1520d4 against live protected base 6eb06cdd08c79a06f7b390069d4ffa49e2eb7dba. All nine exact-head workflows are terminal-success, the branch is zero commits behind, and no review or unresolved thread currently exists. Keep Draft; this request is source-review evidence only and is not merge approval or protected-main acceptance.

[coderabbitai]

@seonghobae I will perform a fresh semantic source review of the requested head against the stated base. I will keep the PR as Draft. This review does not approve, merge, or accept the PR into protected main.

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.