Skip to content

fix(kpi): restack provenance integrity on current main - #250

Merged
seonghobae merged 4 commits into
mainfrom
fix/kpi-provenance-integrity-current-main-v2
Aug 13, 2026
Merged

fix(kpi): restack provenance integrity on current main#250
seonghobae merged 4 commits into
mainfrom
fix/kpi-provenance-integrity-current-main-v2

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Purpose

Restack the strict KPI provenance-integrity repair onto the current protected main without carrying the stale/diverged ancestry of #105.

Exact identities

  • protected base immediately before PR creation: c01a663485dc25d2d11f35318aa0a677c07e0320
  • predecessor fix(kpi): bind strict provenance to exact log bytes #105 exact source head: 43ed054432f0a5ad8533492d686ddb9c45b80410
  • successor exact head: e8ea51cac02bec499c2b80a9509cf8dc155201ea
  • ancestry: successor is 4 commits ahead / 0 behind protected base; merge base is exactly protected base

Preserved bounded slice

The successor preserves the exact source blobs from #105 for only these six paths:

  • docs/observability-kpi.mded83c44732f1ebcf5fa96da397602928841c4178
  • scripts/collect-kpi-logs.sh8a1848742cfa5191ef5de13248e519e799d8d5cd
  • scripts/kpi-gate.mjs5fa43b732d510311fd8a7691da933974fbb51de6
  • test/kpi-collect.test.tsedf027cceeaa0373dba16dd62a81e1d16a3761ca
  • test/kpi-gate.test.ts9235db82b77f19049b2692a40a8d080d5e0f0961
  • test/kpi-provenance-snapshot.test.ts18e6497eee094282dd947c20bd686ee7c2951227

No predecessor CHANGELOG or unrelated merged-main content is replayed.

Security / data-integrity behavior

The slice binds strict production KPI evidence to the exact retained log bytes that are scored, derives record count/digest/byte size coherently from the retained stream, scores a verified permission-restricted snapshot instead of a mutable original path, strips sensitive ambient authority from KPI child processes, validates HTTPS-only log URL handling, and fails closed when strict evidence persistence cannot retain its configured result.

Evidence boundary

Predecessor CI, reviewer, scanner, model-review and formal-review states do not transfer to this successor. This PR stays Draft until fresh checks execute against this exact head and live protected-base scanner semantics. Pending, absent, skipped, neutral, failed, cancelled, stale, predecessor-head, status-only, model-only, and rate-limited evidence remain non-passing.

This repair does not prove 30 days of real production operation, upstream Logpush/archive authenticity, deployment/release state, customer or revenue evidence, owner/legal/IP-transfer authority, or an outbound license decision.

Related: #3, #5, #27, #29, #104, #105

@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 20 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: 130a2dfb-eab9-48ef-a274-d566b6150218

📥 Commits

Reviewing files that changed from the base of the PR and between c01a663 and e8ea51c.

📒 Files selected for processing (6)
  • docs/observability-kpi.md
  • scripts/collect-kpi-logs.sh
  • scripts/kpi-gate.mjs
  • test/kpi-collect.test.ts
  • test/kpi-gate.test.ts
  • test/kpi-provenance-snapshot.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

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

@seonghobae
seonghobae marked this pull request as ready for review August 13, 2026 01:45
@seonghobae
seonghobae merged commit 82d884d into main Aug 13, 2026
16 checks passed
@seonghobae
seonghobae deleted the fix/kpi-provenance-integrity-current-main-v2 branch August 13, 2026 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant