Repository navigation
Files Changed: page receipts and preserve legacy external diffs #1090
Description
Important
Problem — Existing external-diff persistence must remain readable while full-provenance receipt data needs stable root-scoped pagination.
Approach — Add a compatibility adapter and receipt-sequence pagination without upgrading legacy records into full-provenance ownership.
Scope — in: paged retrieval, immutable sequence cursors, legacy_external projection, expiry projection · out: mutation-route adoption and UI replacement.
Assumptions — Receipt storage and bounded evidence lifecycle slices are merged.
Acceptance Criteria
- Retrieval pages immutable receipts by creation sequence within one root without duplicate or skipped rows.
- Existing v1 external-diff data reads as a legacy_external compatibility record with no operation group, lineage ownership, or full-provenance claim.
- Missing or expired evidence produces an unavailable assessment and never a patch payload.
- Legacy consumers remain wire-compatible.
Testing Decisions
Extend external-diff lifecycle tests and storage tests with cursor boundaries, compatibility fixtures, evidence expiry, and legacy-payload assertions.
Key Decisions
Compatibility is read-only: it translates prior data but never synthesizes root ownership or operation history.
Constraints & Invariants
Full-provenance discovery remains separate from compatibility reads; no UI or serializer change is included.
Prior Art
#972 external-diff foundations, #1076 design record, and the preceding storage slices.
Source
Part of #1076 and #972. Blocked by the receipt-schema and evidence-budget slices.
Activity