[Promote] NSFW/TOS media moderation: analysis pipeline, protected tags, blur shield, admin review (#308)

[lopugit]

Automated promotion of #308 from develop to main, opened by the Promote features to main workflow for release review.

Source

Source PR	#308 — NSFW/TOS media moderation: analysis pipeline, protected tags, blur shield, admin review
Author	@lopugit
Merged into develop	2026-08-21T03:12:22Z
Merge commit	14ee574541589797b9a85d93ddd675b5b00cbe05
Head branch	claude/nsfw-tos-media-moderation-58c301

How to review

• This PR re-applies the source PR's exact changes onto main
  (git cherry-pick -x; each commit message references the original SHA).
• Merge it normally to release the change to main —
  the Sync main into develop workflow keeps develop aligned afterwards.
• Close it (without merging) to keep the change out of main;
  the workflow never recreates a closed promotion (reopen it to change your mind).
• Prefer shipping everything at once? Merge the standing omnibus
  Promote develop to main PR instead — this PR's diff then becomes
  empty and the workflow closes it automatically.

Automatic conflict-resolution review

• The exact source patch conflicted with main, so the trusted AI
  promotion resolver produced this branch automatically instead of leaving manual commands.
• Its write scope was limited to non-Graphify paths already changed by the source PR;
  Graphify output was handled as derived data, and unresolved conflict markers were rejected.
• A github-actions[bot] comment on source PR NSFW/TOS media moderation: analysis pipeline, protected tags, blur shield, admin review #308 attests the exact
  base, source endpoints, reservation commit, final head, plan hash, and resolver run.
• Please review the resolved diff before merging; no manual branch repair is required.

---

🤖 Generated by the promote-features-to-main workflow.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
thingtime	Ready	Preview	Aug 21, 2026 4:09am

[github-actions]

🤖 Automatic promotion conflict resolution completed.

Source PR: #308 · plan: 822b4f3b3c822f1c048e0c7c664d575714804e604eab285072528ab7acf64f7e · workflow run

Base: main at 52c2d49938144988828e70ac36701600305ac824 · reservation: 29ac004474901999b401046065e5c993d77467ec · verified head: 76267907ad6817b7671187a277739fd2a53b2184.

Please manually review the paths the isolated AI resolved:

• remix/CHANGELOG.md
• remix/app/api/utils/attachments/attachmentCore.ts
• remix/app/api/utils/attachments/attachmentStore.ts
• remix/app/api/utils/messenger/messenger.ts
• remix/app/api/utils/things/things.ts
• remix/app/components/Attachments/PostAttachments.tsx
• remix/app/components/Attachments/attachmentTypes.ts
• remix/app/components/Attachments/attachmentUiCore.ts

Model waterfall: --model claude-opus-5 --fallback-model claude-fable-5,default · Graphify refresh: true (semantic: claude-cli).

[lopugit]

Manual conflict-resolution review completed for all eight AI-resolved paths.

• Independently reconstructed the exact NSFW/TOS media moderation: analysis pipeline, protected tags, blur shield, admin review #308 patch onto current main from source boundary 58f6f2e..14ee574.
• All non-Graphify code in head 7626790 matches the independent resolution byte-for-byte; only CHANGELOG placement/wrapping differs, with the same moderation entries and no unrelated entries.
• Confirmed the promotion excludes attachment ordering ([Promote][attachments #1] feat(attachments): drag/drop sort ordering for post media & files (create + edit) (#306) #311), detected-container/media UI (feat(attachments): play every browser-playable video container inline + label sniffed types #319/feat(media): masonry gallery, lightbox, media Thing pages + title/description (stacked on #306) #312), relationship migration (Security: data crystals can no longer squat the kind-blind unique key slots (followKey & friends) #320/Relationship uniqueness rides the server-only uniqueKeys namespace (phase 1: stamp + swap + backfill) #325), and unrelated product work.
• Validation on the scoped promotion tree: complete unit suite passed; moderation 52, attachments 110, messenger 3, schemas 53, collections 16, migrations 19; production Vercel build and output verifier passed.

The resolver workflow's terminal failure was an HTTP 502 from PR creation after the branch had already been safely published; PR #337 and its immutable review metadata exist.

[lopugit]

Additional exact-tree verification: started the isolated worktree stack on its deterministic 18880/18882 ports, confirmed one stable PM2 entry and listeners, then ran the canonical live API suite: 431/431 passed. The temporary PM2 entry was removed afterward and all three listeners are closed.