[Epic] Webtoon/cartoon mode inside plotlink-ows

[realproject7]

Goal

Add webtoon/cartoon production support directly to plotlink-ows while preserving the currently stable fiction workflow in plotlink-ows@1.0.33.

This is a pivot away from the standalone PlotToon app. The implementation should reuse the existing OWS foundations instead of rebuilding them:

• Claude terminal/session flow
• story folder model
• Preview/Edit split UI
• PlotLink image upload and publish flow
• current OWS wallet flow
• dashboard/settings pages

Full proposal reference for agents working on this batch:

~/z-docs/PROPOSAL-plotlink-ows-webtoon-pivot.md

Product Decisions

• Use PlotLink's existing contentType: fiction | cartoon contract.
• Do not invent a separate OWS-only category model.
• Webtoon UI appears only for stories with contentType === "cartoon".
• Speech bubble / lettering editor is MVP-required.
• Agent generates clean images without final dialogue text; user letters manually.
• plot-NN.cuts.json is canonical cartoon cut state.
• plot-NN.md remains publish-facing markdown, with generated cut blocks preserved/regenerated from cuts.json. Use ows:cartoon-cut generated markdown markers, not stale PlotToon-branded markers.
• First implementation batch must avoid refactoring stable OWS terminal, wallet, publish transaction, dashboard, and settings flows unless strictly necessary.
• AtlasCloud is postponed.
• Multi-wallet is post-MVP and is not part of this batch.

Rollback / Release Strategy

plotlink-ows@1.0.33 is the stable rollback point.

• Webtoon builds should be prerelease builds under a non-default npm dist-tag such as webtoon.
• Test webtoon builds with npx plotlink-ows@webtoon rather than replacing the global stable install.
• Rollback should remain as simple as npm install -g plotlink-ows@1.0.33.
• Do not perform destructive migrations of existing fiction stories, wallet data, dashboard data, terminal session metadata, or publish status files.
• Live in-memory PTY/Claude processes are not expected to survive restart, but stored session IDs and story folders must remain available for resume after rollback.

Batch Order

QuadWork agents should process the sub-tickets in this order. Operator gates are intentionally placed at the start and end so the implementation tickets can run as one mostly automated batch.

• Operator Gate: confirm webtoon rollout baseline and rollback policy #198 — Operator Gate: confirm webtoon rollout baseline and rollback policy
• Add PlotLink contentType metadata to OWS New Story flow #199 — Add PlotLink contentType metadata to OWS New Story flow
• Generate cartoon-aware agent instructions for OWS stories #200 — Generate cartoon-aware agent instructions for OWS stories
• Add cartoon cuts.json schema and file services #201 — Add cartoon cuts.json schema and file services
• Add cartoon preview routing without changing fiction preview #202 — Add cartoon preview routing without changing fiction preview
• Add cartoon clean image asset management and cut list UI #203 — Add cartoon clean image asset management and cut list UI
• Build SVG/HTML lettering editor foundation #204 — Build SVG/HTML lettering editor foundation
• Implement speech bubble, narration, and SFX overlay tools #205 — Implement speech bubble, narration, and SFX overlay tools
• Vendor approved lettering fonts and language fallbacks #206 — Vendor approved lettering fonts and language fallbacks
• Export lettered cartoon cuts under the 1MB image limit #207 — Export lettered cartoon cuts under the 1MB image limit
• Generate cartoon publish markdown from cuts.json while preserving manual prose #208 — Generate cartoon publish markdown from cuts.json while preserving manual prose
• Integrate cartoon upload and publish with existing PlotLink flow #209 — Integrate cartoon upload and publish with existing PlotLink flow
• Add webtoon MVP regression and readiness checks #210 — Add webtoon MVP regression and readiness checks
• Fix cartoon publish contentType propagation from StoriesPage #224 — Fix cartoon publish contentType propagation from StoriesPage
• Fix cartoon cut export/upload state and failure handling #225 — Fix cartoon cut export/upload state and failure handling
• Make webtoon lettering font loading deterministic for export #226 — Make webtoon lettering font loading deterministic for export
• Operator Gate: run real pilot and approve webtoon prerelease promotion #211 — Operator Gate: run real pilot and approve webtoon prerelease promotion

Review Follow-ups Before Pilot

Review of merged PRs #212-#223 found three pilot-blocking follow-ups: #224, #225, and #226. Complete those before running #211.

The first real #211 pilot also found schema/readiness issues that must be fixed before prerelease promotion:

• Fix cartoon agent instructions to emit app-compatible cuts.json #231 — Fix cartoon agent instructions to emit app-compatible cuts.json
• Show actionable errors for invalid cartoon cuts.json #232 — Show actionable errors for invalid cartoon cuts.json
• Prevent publish markdown placeholders for unuploaded cartoon cuts #233 — Prevent publish markdown placeholders for unuploaded cartoon cuts
• Wire cartoon readiness checks into publish blocking #237 — Wire cartoon readiness checks into publish blocking
• Verify cartoon markdown image URLs match uploaded cut URLs #239 — Verify cartoon markdown image URLs match uploaded cut URLs
• Fix cartoon planning-state UX and markdown generation discoverability #243 — Fix cartoon planning-state UX and markdown generation discoverability
• Sync package-lock after webtoon package version bump #245 — Sync package-lock after webtoon package version bump
• Normalize package-lock optional dependency churn after npm install #247 — Normalize package-lock optional dependency churn after npm install
• Fix terminal reconnect crash from server-side WebSocket.OPEN usage #249 — Fix terminal reconnect crash from server-side WebSocket.OPEN usage
• Clarify cartoon publish readiness after Generate MD awaiting-upload state #251 — Clarify cartoon publish readiness after Generate MD awaiting-upload state
• Clarify clean image generation handoff and prompt/import workflow #252 — Clarify clean image generation handoff and prompt/import workflow
• Add terminal agent provider abstraction for Claude and Codex #253 — Add terminal agent provider abstraction for Claude and Codex
• Add New Story agent provider selection and force Codex for cartoon #254 — Add New Story agent provider selection and force Codex for cartoon
• Add Codex image-generation capability preflight and setup guidance #255 — Add Codex image-generation capability preflight and setup guidance
• Implement Codex cartoon clean-image generation and asset sync workflow #256 — Implement Codex cartoon clean-image generation and asset sync workflow

Not In This Batch

• Multi-wallet support. Existing issue Feature: support multiple OWS wallets and active wallet selection #196 remains separate and should not be mixed into this webtoon MVP batch.
• AtlasCloud app-managed integration.
• Major rewrites of terminal, wallet, dashboard, settings, or existing publish transaction code.

Acceptance Criteria

• Existing fiction story workflow still works.
• Npm package size remains reasonable after font additions, with large font choices documented.
• Existing Claude terminal behavior remains stable.
• Existing upload/publish flow remains stable for fiction.
• OWS can create a cartoon story using PlotLink contentType: "cartoon".
• Claude can follow cartoon-specific agent docs to plan cut-based episodes.
• User can manage cartoon cuts and clean images.
• User can place/edit speech bubbles, narration boxes, and SFX overlays.
• OWS can export final cut images under 1MB.
• OWS can generate publish markdown image sequences while preserving manual prose outside generated blocks.
• OWS can publish cartoon content through the existing PlotLink API contract.
• Final operator pilot validates the workflow with a real or representative story.

Public Safety

This is a public repo. Do not include secrets, API keys, wallet private keys, mnemonics, auth tokens, OWS vault internals, private story drafts, or sensitive local paths in issues, PRs, logs, docs, tests, or examples.