4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 4.8	91b0145bc8	feat(tags): 'Reset content tagging' admin action ... Wipe every general + character tag so the operator can re-tag from scratch via the Camie auto-suggest, while PRESERVING fandoms, series (+ series_page order), and each image's stored tagger_predictions (so suggestions repopulate immediately). One set-based DELETE FROM tag WHERE kind IN ('general','character') — the five tag-referencing tables all cascade, so applications + aliases + allowlist + rejections + centroids clear automatically; series tags aren't deleted so series survive; Tag.fandom_id is SET NULL so fandoms are untouched. Reuses the established dry-run-preview -> confirm pattern: cleanup_service. reset_content_tagging() + POST /api/admin/tags/reset-content + TagMaintenanceCard section with a backup-first warning and a red confirm showing exact counts (tags by kind + image applications). Irreversible except via DB backup restore; the wipe only fires when the operator confirms. Tests: service dry-run counts + live delete preserves fandom/series/series_page while content tags + their image_tag cascade away; API dry-run wiring. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-04 16:47:36 -04:00
bvandeusen	bf8eb4468f	feat(tags): legacy-tag purge also catches source:* general tags ... Operator-confirmed 2026-05-28: the BlenderKnight:* tags are `archive` kind (caught by the kind purge), but the `source:patreon`-style tags are IR's old `source` kind that fell back to `general` during migration (FC's enum has no `source` kind) — so they can't be matched by kind. Broadened the purge to a two-rule match and renamed it for accuracy (all dev-only, unreleased): - cleanup_service.purge_tags_by_kind → purge_legacy_tags. Predicate is now `kind IN (archive, post, artist) OR name LIKE 'source:%'` (LEGACY_NAME_PREFIXES). Preview classifies each row into by_kind OR by_prefix (source:* counts once under the prefix bucket regardless of its general kind). - endpoint /tags/purge-retired-kinds → /tags/purge-legacy. dry-run returns by_kind + by_prefix + count + sample. - store purgeRetiredKindTags → purgeLegacyTags. - Tag Maintenance card copy + breakdown updated to show both buckets; button reads "Preview/Delete legacy tags". Tests updated + extended: dry-run reports by_kind {archive,post,artist} AND by_prefix {source:*}, plain general/character tags survive; commit deletes both the kind-matched and source:*-matched rows and leaves the rest.	2026-05-28 01:20:41 -04:00
bvandeusen	e1fc65bd1b	feat(provenance+tags): collapse provenance descriptions; purge retired-kind tags ... Operator-flagged 2026-05-28, two asks. **1. Provenance posts ate the panel.** Each post card rendered its full description (180px scroll box) inline, so a few posts pushed everything else off-screen. ProvenancePanel now collapses the description by default behind a per-post "Show description ▾ / Hide ▴" toggle (state keyed by provenance_id, reset when the viewed image changes). Cards stay compact — platform/date/title/meta/actions — and the operator expands only the descriptions they want. **2. Purge tags of retired/system kinds.** The IR migration left `archive`/`post`/`artist`-kind tags (e.g. `BlenderKnight:Hannah_BJ_Loops`) that FC no longer creates — the tag input only makes character/fandom/series/general, and provenance + artists are their own systems now. (meta/rating were already hard-deleted by alembic 0023.) - cleanup_service.purge_tags_by_kind(kinds=PURGEABLE_TAG_KINDS) — counts (dry_run) or deletes tags whose kind ∈ (archive, post, artist). CASCADE clears the image_tag / alias / allowlist / etc. rows. - POST /api/admin/tags/purge-retired-kinds (Tier-A, dry-run preview returns per-kind counts + sample names — the preview IS the verification of exactly what'll be deleted before committing). - Tag Maintenance card gets a second section: "Preview retired-kind tags" → per-kind breakdown + sample → "Delete N retired-kind tag(s)". Tests: dry-run counts by kind (general survives), commit deletes only the retired kinds (general + character survive, retired count → 0). NOTE: a dry-run preview will show exactly which kinds/counts are present. If the operator's noisy tags turn out to be `general` (e.g. an IR `source:patreon` that fell back to general during migration), they won't be caught by the kind purge — the preview makes that visible so we can decide on a name-based pass separately.	2026-05-28 01:12:20 -04:00
bvandeusenandClaude Opus 4.7	e41ab1cca5	fc3k(ui): Pinia admin store — six endpoints + task_run polling for Tier-C dispatched ops ... Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-25 00:47:09 -04:00