[Webtoon study] Epic: rebuild cartoon workflow around vertical webtoon grammar

[realproject7]

Context

A local study set under /Users/cho/Projects/z-others/webtoon-study contains five webtoon samples across modern fantasy, thriller, slice-of-life, and romance. The samples show that the current cartoon workflow in OWS is still too image-cut-centric and does not model the production grammar that makes vertical webtoons readable: opening hooks, beat pacing, speech balloon tone, silence, gutters, transition cards, UI inserts, and cliffhanger endings.

This issue is the parent epic for applying the study findings to PlotLink OWS. The implementation must use only abstract craft patterns from the samples. Do not copy, embed, upload, quote, or reproduce original screenshots, artwork, dialogue, character designs, or distinctive story scenes.

Study Findings To Carry Forward

• Webtoon openings usually establish genre promise in the first few scrolls, not after a long prose setup.
• One episode is not just a list of illustrated cuts; it is a rhythm of image panels, blank space, text-only panels, reaction shots, UI/object inserts, and timed reveals.
• Speech balloons carry semantic tone: normal speech, thought, narration, system/status, whisper, shock, shout, dread, hesitation, emphasis, and off-screen speech need different visual treatments.
• Scene transitions are first-class content. White gutters, black gutters, gradient fades, object inserts, phone/message UI, time cards, and isolated SFX often do more storytelling work than a literal connecting image.
• Endings vary by genre: modern fantasy closes on a repeatable power/reward loop, thriller closes on dread or unresolved threat, romance closes on relationship complication, slice-of-life closes on a compact gag/observation.

Child Work Areas

• Episode beat model + genre templates.
• Speech balloon taxonomy + overlay schema.
• Focused lettering editor controls for tone-specific bubbles.
• Transition/interstitial editor for gutters, time skips, text-only panels, and UI inserts.
• Storyboard rhythm map and cut-density QA.
• Agent skills/docs for webtoon opening, buildup, pacing, and endings.
• Clean-image prompt changes so generated art supports lettering and transitions.
• Full practical test harness using original OWS-created stories only.

Acceptance Criteria

• OWS can plan, edit, letter, QA, and publish a cartoon episode using webtoon-native concepts instead of prose/fiction leftovers.
• Users can explicitly create and edit speech balloons and scene transitions as first-class objects.
• Agents generate episode plans with hook, beat, transition, dialogue purpose, and ending metadata.
• QA can detect obvious webtoon pacing defects: overlong dialogue, missing transition, missing hook, missing ending turn, and unstyled speech tone.
• No copyrighted sample assets or copied dialogue appear in repo, tests, docs, issues, or generated fixtures.

Verification

• Implement child issues in small PRs.
• Run unit/type/lint tests for each PR.
• Create at least one new original test webtoon in OWS and verify preview/edit/export flows end to end.
• Review the completed workflow against the abstract study findings in this epic.