Repository navigation
Fix: adopt published CAS recovery for attachment GC - #925
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
✨ Finishing Touches📝 Generate docstrings
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 |
|
Code Lawyer self-audit (P2 validation defect): the full Docker pre-push run fails |
|
Full independent feedback follows. Its blocking golden failure matches the self-finding already posted; verification and push gaps remain open until the fix passes the entire pipeline. The detailed adversarial Code Lawyer review plan and complete findings have been recorded in [ Key Findings Summary
Mandatory Verification Checklist Summary
Binding Verdict
Execution & Verification SummaryThe independent binding adversarial Code Lawyer review for All investigations adhered strictly to the read-only authorization fence: no repository files were modified, no host tests were executed, and no external merges or posts were performed. All tests were inspected from logged evidence or executed inside isolated, COPY-based Docker containers ( Core Verification & Audit Findings
Remediation Required for Merge Eligibility
Binding Review Verdict
|
|
Golden update verified, not blindly accepted: COPY-based Docker restored the v17 fixture under old and new published dependency versions. The payload remains36 bytes and its blob remains11aa40d0d62f960fe7348f7ba34eb201cf2f87be. New manifest formatVersion6.5.11 yields tree2b67e47826ccb797a7441019756abc3e697792d3. Replacing only formatVersion with6.5.10 and recomputing the derived manifestHash reconstructs old tree09e785fbd98adf5c00f250598d3a92b0e3e75a33 exactly. An initial inverse experiment omitted the derived hash and failed, as expected for inconsistent metadata; the complete reconstruction passes. Commit08bde047 updates the pinned golden and its version explanation. Eleven related migration tests plus ESLint pass in Docker. The full pre-push rerun and subsequent independent review remain required; no skipped shards are counted as passed. |
Release PreflightHead:
npm bundle analysis
Warnings begin at 85% of a limit; critical headroom begins at 95%. Exceeding a limit fails the existing payload gate.
Findings (0)No static inspection findings. Static reachability findings are deletion candidates, not proof that a file is safe to remove. Dependency checks cover imports and manifest declarations; they are not a vulnerability audit. Largest files (unpacked)
A release-branch merge still requires final preflight and the normal release workflow. |
|
Full independent current-head feedback follows, with these independently adjudicated corrections:
These corrections narrow evidence claims and do not alter source or the substantive approval. An independent binding adversarial Code Lawyer review of The implementation plan artifact has been recorded in [ Executive Review SummaryPR #925 adopts published npm releases The prior review finding at commit Audit by Mandatory Review Protocol1. Every Code Path
2. Merges Are Changes
3. No Trusted Claims
4. Constants Against Evidence
5. Every Number Audited
6. Errors and State Machines
7. Repository Standards
Review Findings
Mandatory Verification Checklist
VerdictThe code changes, upstream adoptions, error translations, merge conflict resolutions, and golden proof at commit
Verification & Execution SummaryExecution has progressed following plan approval. Both the [Implementation Plan](/pr_925_code_lawyer_review_plan.md) and [Walkthrough](/walkthrough.md) artifacts have been recorded in the session artifact directory. All actions strictly observed the read-only operational fence: no repository code was modified, no host tests were executed, no external posts or merges were triggered, and all tests and proofs were verified through isolated, COPY-based Docker evidence. Key Verification & Audit Findings
Final Binding Review Verdict
|
Activity Summary — Code LawyerReviewed head:
All hosted checks are green, including Node/Bun/Deno, coverage, preflight, performance and links. Local lint/type/policy gates passed. Local link checking was unavailable; hosted link checking passed. The exact-head independent agy APPROVE includes the full mandatory checklist. No inline review threads or active changes-requested reviews exist. Public Runtime/Lane attachment operations (#901), bounded streaming (#818), and public consumer proof (#902) remain separate. This PR repairs storage transport recovery; it does not complete those capabilities or authorize a git-warp release. The remaining host consumer-test isolation gap is tracked in #922. Release preflight reports tight package headroom (729,317/760,000 compressed bytes; 3,195,895/3,300,000 unpacked bytes). Limits pass; this warning remains explicit for future growth. MERGE GATE: OPEN. Existing user authorization covers normal merge after marking ready; no protection bypass. |
Outcome
Adopt published
@git-stunts/git-cas@6.5.11and@git-stunts/plumbing@3.3.2so closed mktree transport failures enter CAS's existing bounded retry. Match Deno dependency ranges and remove the temporary Plumbing patch. Retain six regressions for single/batch recovery, retry exhaustion, closed-input races, and producer/unrelated error identity.Fixes #923. Upstream Plumbing #20 and git-cas #132 are merged and published; this change consumes real npm artifacts. Public Runtime/Lane attachment methods (#901) and bounded streams (#818) remain separate.
Validation
08bde0479afa7974a758797fa7f509ad88aaa86b.formatVersion: 6.5.10and recomputedmanifestHash, reproducing the previous migration golden tree exactly with unchanged payload bytes. The pinned 6.5.11 golden is updated; eleven related migration checks pass.Mainline integrations include #915 and #914. The CHANGELOG conflict retained both hook-safety and attachment-recovery entries. No broad concurrent-GC interleaving proof, completed public attachment API, or git-warp publication is claimed.