fix(kpi): restack provenance JSON byte integrity on 4b45ca main

[seonghobae]

Purpose

Rebuild only PR #321's strict production-KPI provenance byte-integrity hardening onto current protected main after #316 and #322 advanced the base. No predecessor CI, review, scanner, coverage, production-KPI, release, deployment, legal-rights, or acquisition authority transfers.

Exact construction

• protected main immediately before publication: 4b45caae6a543759f54caafb959e2cffe653fe05;
• source PR fix(kpi): restack ambiguous provenance JSON bytes on current main #321 exact unchanged head at the pre-write refetch: 7f3519161d2b650cbccd8a4b8300fe53bbcbda4a;
• successor exact head: 5a200e80cbf77fbb0f6dbd33242f56e869008f88;
• ancestry: exactly 1 commit ahead / 0 behind protected main, merge base exactly protected main;
• net scope: exactly two paths: scripts/kpi-gate.mjs and test/kpi-provenance-json-integrity.test.ts.

Protected-main movement since #321's base changes workflow-registry and release-SBOM integrity paths, so this successor overlays #321's exact two head blobs without overwriting intervening protected bytes.

KPI provenance integrity contract

Strict provenance remains raw bytes until fatal UTF-8 decoding, then rejects escape-equivalent duplicate decoded JSON object names before JSON.parse or production-source identity, collection timestamp, record count, SHA-256/byte-size, verified snapshot, final identity, and least-authority KPI child-process decisions. Existing production-source/provenance binding remains unchanged. This does not synthesize or claim a real 30-day production KPI window.

Evidence boundary

Keep Draft until this unchanged exact head receives fresh terminal-success application ci, reviewer-ci, protected-base-eligible central Security Scan, exact configured 100% owned production statement/branch/function/line coverage with realistic tests, and zero valid unresolved findings. Pending, queued, skipped, absent, neutral, failed, cancelled, stale, predecessor, status-only, model-only, or rate-limited evidence is non-passing.

Immediately before Ready or merge, independently re-resolve protected main, exact head/base/ancestry, formal reviews/threads, checks and checkout SHAs, live rulesets, central Security Scan revision/triggers/base filters/thresholds, releases, and writer state.

Supersedes #321 only after fresh exact-head verification and protected integration. Related: #3.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 29 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: f4de573b-cb67-47ba-b7d8-70d98d5c9444

📥 Commits

Reviewing files that changed from the base of the PR and between 4b45caa and 5a200e8.

📒 Files selected for processing (2)

• scripts/kpi-gate.mjs
• test/kpi-provenance-json-integrity.test.ts

---

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