Provenance archive linkage, post reconciliation close-out, and the cleanup/admin DRY pass #127
Reference in New Issue
Block a user
Delete Branch "dev"
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?
Batch of work on
dev, all CI-green.Provenance: archive → image linkage (milestone #87)
068def2): scope the modal's Attachments to the originating post + scroll-cap the list, so a "High Resolution Files" bundle post stops ballooning the rail.5269cd0,af7f007): capture which archive an extracted image came from —ImageProvenance.from_attachment_id(migration 0055), stamped at import for new/superseded/deduped members, idempotent so re-extraction backfills.for_image()shows only the containing archive when known. Guard for sidecar-less archives.Post reconciliation close-out (milestone #73)
77d02f5):_repoint_post_linksnow carries a loser'sfrom_attachment_idonto the keeper before dropping the colliding provenance row.Cleanup/admin DRY pass (#753)
6281cb1):_run_dry_run_opconsolidates the 5 Tier-A dry-run/apply admin handlers.6599a07):_queuedconsolidates the 5 Celery-dispatch 202 responses (caught a self-recursion bug mid-edit).26589c3):_guard(all 13 admin-store actions) +_dryRunPost(the 6 maintenance ones).7c94d99):usePreviewCommitcanonicalizes the sync preview→commit maintenance-tile flow (6 hand-rolled flows across TagMaintenanceCard + PostMaintenanceCard).Post-deploy action
Run Settings → Maintenance → Re-extract Archives once to backfill
from_attachment_idacross the existing library.🤖 Generated with Claude Code