Problem
Static storage metric checks now exist, but device behavior still needs validation after real build, prune, rebuild, and container edit/copy-up flows. UI totals must not double-count shared layer data.
Scope
- Verify layer store, image-view, container-private, total, free-space, volume, and build-cache metrics on device.
- Confirm shared layer-pool accounting is nonnegative and not double-counted as image unique storage.
- Validate metric refresh after build, prune, rebuild, and container file edit/copy-up.
Non-goals
- Do not move file contents into SQLite/DB storage.
- Do not claim exact overlayfs inode semantics.
Acceptance checks
python3 scripts/verify-storage-metrics.py passes for fixture/static coverage.
- Device/manual or smoke evidence captures
/system/df, /images/json, and /containers/json?all=1&size=1 around build/prune/rebuild/edit flows.
- Docs/test artifact records the result and any remaining gap.
Current context
- Static lane:
scripts/verify-storage-metrics.py.
- Docs:
docs/test/STORAGE_METRICS.md, docs/design/COW_OVERLAY_STORAGE.md.
- TODO: Android storage metrics verification entry.
Problem
Static storage metric checks now exist, but device behavior still needs validation after real build, prune, rebuild, and container edit/copy-up flows. UI totals must not double-count shared layer data.
Scope
Non-goals
Acceptance checks
python3 scripts/verify-storage-metrics.pypasses for fixture/static coverage./system/df,/images/json, and/containers/json?all=1&size=1around build/prune/rebuild/edit flows.Current context
scripts/verify-storage-metrics.py.docs/test/STORAGE_METRICS.md,docs/design/COW_OVERLAY_STORAGE.md.