Complete v19 Studio media administration

[lowestprime]

Summary

• Add a durable no-navigation Studio autosave shell with replay, optimistic conflicts, canonical reconciliation, and exact route/viewport/focus recovery.
• Add reviewed media-folder rules, transactional direct-public assignment, notification policies, project lifecycle administration, privacy-preserving visitor insights, and a redacted administrative audit workspace.
• Add schema 13 managed FTS5 search with Unicode/prefix tokenization, source-write synchronization, publication/private visibility, weighted BM25 snippets, integrity/rebuild controls, and bounded precomputed-vector reranking.
• Add protected inventory schema 3 with stable v19 Studio subviews, deep dialog/surface capture, and inventory-derived snapshot-lab mutation/write-count validation.
• Add R1-R13 traceability and an explicit Studio mutation classification that keeps R7/R8 parity gaps visible until implemented.

Why

The v19 administration work needs non-disruptive editing, safe media operations, controlled outbound messaging, privacy-preserving visitor insight, fast self-hosted search, and exact release evidence that cannot misclassify clone-only writes as production safety.

Files / areas touched

• Studio Piece, Media, Notifications, Visitors, Audit, Projects, and Search Index workspaces plus shared autosave/navigation behavior.
• Media rules, normalized piece-media persistence, notification delivery, project lifecycle, visitor privacy, audit redaction, FTS5 synchronization, bounded reranking, and additive schema migrations 8-13.
• Protected visual inventory, deterministic deep-state capture, snapshot-lab round trips, strict diagnostics, and disposable smoke validation.
• Focused migration, transaction, notification, project, visitor, media, search, Studio, visual-audit, and safe-build tests.
• README.md, admin.md, synology-nas-deploy.md, woodsmith_DeepWiki_Merged_03222026.md, PLANS.md, and docs/v19-requirements-traceability.md.

Validation

• npm run test - passed, 155/155 tests.
• npm run typecheck - passed.
• npm run lint - passed with 0 errors and 11 established no-img-element advisories.
• npm run build - passed on Next.js 16.3.0; standalone runtime-data gate passed.
• Visual-audit tests - passed, 84/84.
• Content-equivalent snapshot-lab smoke - passed with 445 captures across 48 routes, six required mutation states, exactly ten successful clone-only unsafe requests, zero unexpected diagnostics, zero residual drafts, unchanged source data/media, matching cloned media, and complete cleanup.
• Content-equivalent live-readonly smoke - passed with 366 captures across 36 routes, zero successful unsafe requests, 38 expected policy blocks, zero unexpected diagnostics, and complete cleanup.
• WP07 exact commit 0ff5d6863e66d1fd7c11cee3c0325a2109c8f4bf built as linux/amd64 image sha256:f2ef7bbe2b6c69397464200b67a5b19e9beb68369797da118ad67ce20f51576a; image inspection found no bundled database, environment, auth state, evidence, report, screenshot, archive, or production-media payload.

Caveats / follow-up

• This pull request remains draft. Settings, Process, People, commission types, categories, media metadata/rules, Orders, and Reviews still require complete R7/R8 autosave and destructive-dialog parity before final candidate freeze.
• The latest archive smokes used deliberately unstamped unknown-loopback-smoke images. They are local safety evidence, not final exact Tier 1, Tier 2, or Tier 3 evidence.
• Production-clone migration/restart/performance, paired backup and staging restore for the final identity, candidate deployment, persistence, rollback, Cloudflare differential, sidecar reachability, and Tier 3 live evidence remain pending.
• No production data or production media was mounted or mutated.
• SMTP, Stripe, EasyPost, and optional model integrations remain configuration-dependent and fail closed when unavailable.
• Local persistence uses node:sqlite, and current build logs show Node's experimental warning for that API; public deployment should move to Postgres, LibSQL, or another stable production database.