Repository navigation
v0.13.4
Sidecar file metadata inventory and Lode error path validation
Summary
Files written via storage.put() are now tracked in Lode snapshot metadata, enabling downstream consumers to enumerate sidecar files without prefix-scanning storage. Targeted integration tests provide evidence for Lode V1_READINESS §5 error path validation.
Highlights
- Sidecar file inventory:
storage.put()files tracked in snapshotMetadata["sidecar_files"]withpath,filename,content_type, andsizefields - Consumer-facing flush boundaries: file refs flush on event and metrics writes only — chunk writes do not drain pending refs
- Lode sentinel tests:
ErrPathExists(immutability on double-write) andErrNotFound(stale snapshot ID) validated from Quarry's actual code paths - End-to-end pipeline test: full
file_writeIPC frame →PutFile→ event flush →sidecar_filesin snapshot, with strict assertion that exactly one snapshot carries the metadata - Contract and docs:
CONTRACT_LODE.md§ Sidecar File Inventory,guides/lode.md, andPUBLIC_API.mdupdated
Upgrade Notes
- No breaking changes — sidecar file metadata is additive (new
Metadatakey on existing snapshots) - Downstream consumers can optionally read
snapshot.Manifest.Metadata["sidecar_files"]to discover files; existing prefix-scan workflows continue to work
Full Changelog: v0.13.3...v0.13.4