Explain preliminary metadata coverage separately from ZIP integrity #18
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/issue-6-metadata-coverage"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The analysis report presented filename matching as a health check, making intact exports look damaged and implying importer outcomes it cannot predict. This separates ZIP integrity from preliminary metadata coverage, explains entry/JSON counts and subset-only timeline/location summaries, and directs users to Immich-Go's own preview and retained diagnostics.
Validation passed locally on AMD64 Docker Desktop: backend tests/vet with the pinned importer; UI lint and production build; disposable browser/upload-recovery suite including real queued analysis, synthetic ambiguous/repeated/empty/legacy reports, 320/390px report layout, other-user/administrator isolation and support-report privacy; nine CI policy tests and source/documentation contracts; exact pinned-format comparison; source-only secret scan; source gosec/govulncheck and all three image advisory policies with existing baselines unchanged. Source scan: 32 production files, 29 reviewed findings, no suppressions.
Addresses #6; follows #14. Stacked on #15, with
codex/issues-10-11-diagnosticsas the base so this review contains only #6. Retarget to main after #15 merges. Commit:9980373bf6d7025f23560f47ede1c9ff74dce1e1.This is pushed for review, not merged, release-image-published or deployed. Native ARM64/full release CI and a real-library pilot are not claimed. A separate existing header extends 3px beyond 320px; the report fits and the established whole-page 390px check passes. Keep #6 open through review and the coordinated idle deployment/new owner preview; do not interrupt active uploads/tasks.