4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 4.8	5269cd0709	feat(provenance): capture which archive an extracted image came from (#87) ... Images pulled out of a .zip/.rar previously kept no record of WHICH archive they came from — the member->archive link was computed during extraction and discarded, leaving only image->post. So the provenance modal could only scope attachments to the whole post, showing every archive a 'High Resolution Files' bundle carried instead of the one a given file lives in. - ImageProvenance.from_attachment_id: nullable FK -> post_attachment.id (SET NULL), migration 0055. - importer: _import_archive stamps from_attachment_id on every member's provenance row for the post (new + superseded + deduped members), resolving the archive's own PostAttachment by (post, sha). Post-pass UPDATE, NULL-only and idempotent, so it doesn't touch the dedup/supersede branches and the backfill is safe to re-run. Nested members link to the outer stored archive. - provenance_service.for_image: when the originating post's provenance row records from_attachment_id, return ONLY that archive; else fall back to the primary-post scoping from 068def2. - ProvenancePanel: heading pluralizes ('Attachment' for a single file). - Backfill: re-running reextract_archive_attachments (ArchiveReextractCard) routes through _import_archive and stamps existing rows — no new code. Tests: capture stamps on fresh import, nested-archive attribution, per-post archive on dedup; for_image filters to the containing archive; reextract backfill stamps the link. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-21 22:22:03 -04:00
bvandeusenandClaude Opus 4.8	8dee2f9628	feat(import): recurse nested archives + precise "no images" reason (#718) ... Root cause (operator-confirmed via event metadata + lsar): a "High Resolution files" pack often wraps a per-chapter .rar/.zip INSIDE one outer archive (incase). _import_archive only extracted one level — a nested-archive member failed is_supported and was skipped, so the real pages were silently dropped and the post showed "archive but no images". The disk scan found this pattern recurring across the attachment store. - Recurse into nested archives via _collect_archive_members: a member that is itself an archive is bomb-probed and extracted too, depth-capped at _ARCHIVE_MAX_DEPTH=3. Nested members attribute to the OUTER archive's sidecar so they link to the right Post. Each level is wrapped so one bad nested archive can't abort the import. The shared path means external (mega/gdrive) archives recurse too. - Replace the catch-all "held no supported members" string with a per-outcome tally (media/deduped/unsupported/failed/nested/nested_rejected). The all-deduped case is now recognised as BENIGN — images already in the library, re-linked to this post via enrich-on-duplicate — and returns attached WITHOUT error, so it no longer false-flags in event metadata.unextracted_archives. Genuine failures carry the precise breakdown. Tests: nested zip-in-cbz imports both inner images + links them to the outer post; all-deduped archive returns attached with error=None and links images to both posts. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 21:18:02 -04:00
bvandeusenandClaude Opus 4.7	7dea165fae	fix(test): archive members need structured imgs+threshold0; provenance payload gained attachments key ... Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-19 11:22:17 -04:00
bvandeusenandClaude Opus 4.7	f97551e2f6	feat(attachments): importer dispatch — archive extract + non-media capture ... Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-19 11:13:36 -04:00