chore: retain milestone-2 audit follow-up as read-only source evidence - #81
chore: retain milestone-2 audit follow-up as read-only source evidence#81seonghobae wants to merge 38 commits into
Conversation
|
Important Review skippedToo many files! This PR contains 230 files, which is 130 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (5)
📒 Files selected for processing (230)
You can disable this status message by setting the 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 |
Superseded by the protected additive Milestone 2 delivery path
This branch is a direct descendant of the read-only
codex/milestone-2-direct-postgres-productsource branch: its first parent is the exact retained source head96116aa4c44d0fe5dd2515b2e348a75f8f025a48. It therefore reopens the same parallel repository replacement that PR #77 intentionally removed from the merge queue.The branch contains useful follow-up work for run audit fields and abstention-safe metric parsing, but the PR diff still replaces the protected LineageWeave product across 235 files. It brings a second web application, resets the migration/product lineage, duplicates current runtime and documentation surfaces, and includes a
compose/keyverse_oidc.pyKeyverse-shaped identity implementation with local credentials. Those changes cannot be merged into the post-PROV-O product architecture as one unit.Issue #79 is the canonical delivery contract. Preserve this branch read-only and port only bounded, reproduced slices after the protected #74 result:
The run-audit and abstention-safe parsing delta should be isolated as a small additive commit against that protected line, with failing regressions first and exact-head product, PostgreSQL, frontend, browser, security, and public-content gates.
Closing this PR prevents an unsafe replacement merge without deleting its branch or its reproducible implementation evidence.
Superseded by #79.