feat: add reviewed creator workflows, library and campaign history

[nikolajIvanov]

Summary

Package 1: reviewed creator workflows, separate from the read-only API/MCP contribution (#84).

• DRAFT / ACTIVE / PAUSED / ARCHIVED lifecycle; imports and copies always start inactive.
• Priority and excluded-keyword rules; shared worker/simulator selection.
• Versioned workspace templates/resources, independent draft copies and optimistic update checks.
• Immutable campaign-setting and historical-link revisions with safe projections.
• Transactional next-reel arming and explicit review before activation.
• English / Traditional Chinese UI and setup notes.

Scope and rollout

Additive creator-only migration: campaign fields, WorkspaceAsset, CampaignRevision and LibraryDraftRequest for retry-safe library copies. Existing active/paused state and legacy overlapping campaigns are preserved; no silent rebinding.
The web app and worker must be updated together after migration because lifecycle/rule selection semantics change.
No API keys, MCP endpoints, IntegrationEvent or DeliveryEvent tables in this package. No SMTP/Auth, Docker or dependency changes. Durable frozen delivery handling and external integrations are separate packages.

Verification

• Independent full suite: 361 tests / 33 files passed, including genuine PostgreSQL migrations/concurrency/ownership tests.
• ESLint and diff checks passed.
• Library retry isolation, import/copy inactive state, revision whitelists/link ties, concurrent next-reel activation, and simulator/worker selection checked.
• Invalid JSON, 64-KiB body bound and Origin regressions tested.
• No production data, instance configuration or live messaging performed. No interactive browser or real Meta acceptance claimed.

Known upstream blocker: production compilation succeeds, but TypeScript/build stops on the unchanged upstream nullable operationId error (now dm-worker.ts:860; base line855). See #83. This contribution does not silently include that unrelated fix or claim green build/deployment readiness.

Follow-up packages will add durable delivery snapshots and scoped draft/event/conversion APIs.

[vercel]

@nikolajIvanov is attempting to deploy a commit to the diwenne's projects Team on Vercel.

A member of the Team first needs to authorize it.