Data Export, Portability & Reimport Readiness Review

The likely issue is a contract mismatch around data exports, portability packages, schema/version documentation, completeness, identifiers, timestamps, attachments, metadata, permissions, checksums, large-file handling, reimport feasibility, retention, and evidence. I would first define the invariant: A portability export is ready only when the user can trace what is included/excluded, validate integrity, understand identifiers/schema, and preserve the context needed for lawful transfer, archival use, or supported reimport. Then I would trace the smallest owning boundary, keep VERIFIED facts separate from LIKELY/UNKNOWN state, apply or propose the narrowest repair, and add deterministic normal, boundary, failure, retry/cancellation, and recovery tests. The workflow preserves authorization, privacy, security policy, public interfaces, user-visible behavior, and documented ownership. With repository/workspace access, findings can map to exact paths and focused local validation; with partial evidence, the result remains an explicit diagnosis/evidence map with no invented execution claims.