Ambiguous Artifact ID

The artifact hash prefix 1f5e is ambiguous and might mean any of the following:

1. 1f5e773731c0388eba6f0e7c3b86489873ddafa4285ff36dd61562a88b990ef9 -

   • File src/artifact.zig — part of check-in [0ae7fb2622] at 2026-07-08 21:53:01 on branch trunk — Scaffold zit: Zig project + RFC references + module layout

     Fossil-in-Zig, ported from the four RFC drafts (docs/rfcs/). Layout mirrors the RFC layering: delta -> artifact -> repostate -> sync. delta int codec + checksum and artifact naming/Z-card implemented with RFC-derived test vectors; everything else stubbed against its section. Builds clean; zig build test green. See docs/HANDOFF.md. (user: dmestas, size: 4357) [annotate] [blame] [check-ins using]

2. 1f5ed9ab4668da9f8e027d1f6e7956953c21234bef3698afc48f16c891f5440a -

   • File src/e2e.zig — part of check-in [c0a116d458] at 2026-08-10 20:17:42 on branch sub-manifest — Delete the legacy reserved-name tier (consolidation Task 7)

     The policy is three names and a prefix: .zit, .zit-checkout, .zit-cache, .zit-tmp-*. Removed: the absorbed sibling reservations (.zit-managed/-undo/ -bisect), the pre-directory cache/vstat spellings and their read tolerance, the retired scratch spellings, and the import-provenance names (refs, .zit-import-map.jsonl).

     Behavior shift: in never-re-opened old checkouts these leftovers are now visible to extras and deletable by clean. The container's byte-1 fold stays, so a legacy authoritative sibling still migrates losslessly on first contact (e2e: every-leftover checkout converges to the clean root with membership intact). (user: dmestas, size: 883523) [annotate] [blame] [check-ins using]