fix(kpi): restack provenance integrity on current main - #250
Conversation
|
Warning Review limit reached
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 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
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. Comment |
Purpose
Restack the strict KPI provenance-integrity repair onto the current protected
mainwithout carrying the stale/diverged ancestry of #105.Exact identities
c01a663485dc25d2d11f35318aa0a677c07e032043ed054432f0a5ad8533492d686ddb9c45b80410e8ea51cac02bec499c2b80a9509cf8dc155201eaPreserved bounded slice
The successor preserves the exact source blobs from #105 for only these six paths:
docs/observability-kpi.md—ed83c44732f1ebcf5fa96da397602928841c4178scripts/collect-kpi-logs.sh—8a1848742cfa5191ef5de13248e519e799d8d5cdscripts/kpi-gate.mjs—5fa43b732d510311fd8a7691da933974fbb51de6test/kpi-collect.test.ts—edf027cceeaa0373dba16dd62a81e1d16a3761catest/kpi-gate.test.ts—9235db82b77f19049b2692a40a8d080d5e0f0961test/kpi-provenance-snapshot.test.ts—18e6497eee094282dd947c20bd686ee7c2951227No 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