Operator Gate: run real pilot and approve webtoon prerelease promotion

[realproject7]

Parent: #197

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

Context

This final gate happens after automated implementation tickets are complete. It should validate the webtoon MVP with a real or representative story before promoting any webtoon build beyond the prerelease dist-tag.

Pilot Blockers

Pilot should wait for follow-up fixes #224, #225, and #226, created from review of merged PRs #212-#223.

Required Pilot

Operator should verify:

• before testing, record the current story slug/name and Claude resume session id/hash from ~/.plotlink-ows/data/terminal-sessions.json using sanitized notes only;

• install/run stable rollback path: npm install -g plotlink-ows@1.0.33 still works;

• after reverting from the webtoon build, existing story folders, publish statuses, local DB/config, and terminal session metadata still exist;

• compare the post-rollback terminal session metadata against the pre-test resume baseline and confirm OWS attempts resume for the expected story;

• confirm the operator understands live PTY/Claude processes are interrupted by restart, while stored Claude session IDs should allow OWS to attempt resume;

• test webtoon build with npx plotlink-ows@webtoon or local dev run;

• create a cartoon story with PlotLink contentType: "cartoon";

• create a cut plan with Claude using the generated cartoon agent docs;

• attach/import clean cut images;

• place bubbles/narration/SFX manually;

• export final images under 1MB;

• upload final images;

• generate publish markdown;

• publish or dry-run publish according to operator approval;

• confirm fiction stories still preview/edit/publish normally.

Acceptance Criteria

• Operator posts pilot result in this issue.
• Any blocking bugs are opened as follow-up issues before release promotion.
• Only after approval should webtoon builds move beyond the webtoon prerelease channel.

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.

[realproject7]

Pre-pilot local baseline recorded.

• Global stable install: plotlink-ows@1.0.33
• npm latest: 1.0.33
• ~/.plotlink-ows exists: yes
• stories directory exists: yes
• local.db exists: yes
• .env / config.json exist: yes
• terminal-sessions.json exists: yes

Story baseline:

• new-employee: present, publish status present, Claude resume id present
• paper-chair: present, publish status present, Claude resume id present
• seoul-slowly: present, publish status present, Claude resume id present

Full session IDs, env values, wallet/config contents, and private story text are not posted publicly.

[realproject7]

Pilot analysis found the flow is not ready for prerelease promotion yet.

The agent produced a good cartoon story concept and followed the high-level clean-image-first workflow, but it generated plot-01.cuts.json in a custom planning schema instead of the app-compatible OWS v1 schema from app/lib/cuts.ts. It also hand-wrote plot-01.md with pending/fake image references rather than relying on OWS generated ows:cartoon-cut marker blocks after upload.

Created follow-up blockers before this gate can pass:

• 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

Recommendation: keep #211 open until #231-#233 are completed and the pilot is rerun from a fresh cartoon story.

[realproject7]

Review of #231-#233 is complete.

Summary:

• Fix cartoon agent instructions to emit app-compatible cuts.json #231 looks correct: cartoon agent instructions now include a concrete app/lib/cuts.ts-compatible v1 cuts.json example and explicit warnings against the invalid pilot schema.
• Show actionable errors for invalid cartoon cuts.json #232 looks correct: invalid cuts.json now surfaces actionable OWS v1 schema guidance in the cartoon preview and cut list instead of silently looking like an empty state.
• Prevent publish markdown placeholders for unuploaded cartoon cuts #233 is partially correct but incomplete for the real publish path: checkMarkdownReadiness() was hardened and tested, but it is currently only used by tests. It is not wired into PreviewPanel, StoriesPage, or the /api/publish/file route, so a hand-written cartoon plot-NN.md with fake/pending image references can still be published if the user proceeds.

Created follow-up blocker before this gate can pass:

• Wire cartoon readiness checks into publish blocking #237 — Wire cartoon readiness checks into publish blocking

Recommendation: complete #237, then rerun the fresh cartoon pilot before closing #211.

[realproject7]

Review of #237 / PR #238 is complete.

What looks good:

• Cartoon publish readiness is now wired into both UI and the server publish route.
• Server-side guard derives cartoon status from .story.json, not from request body, so direct API callers cannot bypass by omitting/faking contentType.
• Missing/invalid cuts.json, pending placeholders, local paths, and missing marker blocks are blocked.
• The narration-only policy was clarified: every publishable cartoon cut must become a final uploaded image.
• Local review verification passed: npm run typecheck, targeted tests, and npm run app:build.

Remaining blocker found:

• checkMarkdownReadiness() does not verify that each markdown image URL matches the corresponding cut.uploadedUrl recorded in cuts.json. It currently accepts arbitrary https://... image refs, even if the cut was never uploaded through OWS.

Created follow-up blocker:

• Verify cartoon markdown image URLs match uploaded cut URLs #239 — Verify cartoon markdown image URLs match uploaded cut URLs

Recommendation: complete #239, then rerun the fresh cartoon pilot before closing #211.

[realproject7]

Review of #239 / PR #240 is complete.

What looks good:

• checkMarkdownReadiness() now requires every cut to have a recorded uploadedUrl.
• Each ows:cartoon-cut cut-XXX block must contain exactly one image reference.
• The image URL in that block must exactly match the corresponding cut.uploadedUrl from plot-NN.cuts.json.
• Arbitrary https://... image refs are rejected if they are not recorded uploaded cut URLs.
• Local/relative refs and bad local-path uploadedUrl values are still blocked.
• Server /api/publish/file uses the same readiness guard, so direct API calls are covered.

Local review verification passed:

• npm run typecheck
• targeted tests: app/lib/cartoon-readiness.test.ts, app/routes/publish.test.ts, app/web/components/cartoon-publish-block.test.tsx, app/lib/cartoon-markdown.test.ts — 61 tests passed
• npm run app:build

Residual non-blocking note: the checker allows a recorded uploaded URL to appear again outside its canonical cut block. That is not ideal for strict markdown canonicalization, but it does not reopen the original #239 issue because the URL is still tied to a recorded uploaded cut. It can be handled later if we want stricter generated-markdown-only enforcement.

Recommendation: #239 is acceptable. Proceed to rerun the fresh cartoon pilot under #211.