scriveno 2.0.5

package/commands/scr/spread-layout.md

@@ -0,0 +1,187 @@
+---
+description: Generate children's book page spread layouts with text and illustration zones.
+argument-hint: "<spread-number> [--text-ratio <percent>]"
+---
+
+# /scr:spread-layout -- Page Spread Layout
+
+Generate children's book / picture book page spread layouts with labeled zones for text placement, illustration direction, and bleed areas using ASCII grid visualization.
+
+## Usage
+```
+/scr:spread-layout <spread-number> [--text-ratio <percent>]
+```
+
+## Instruction
+
+You are generating a page spread layout for a children's book or picture book. Load:
+- `.manuscript/config.json` (to get `work_type` -- must be in visual group: childrens_book, picture_book, illustrated_book)
+- Scriveno's installed/shared `CONSTRAINTS.json` (global `~/.scriveno/data/CONSTRAINTS.json` or project `.scriveno/data/CONSTRAINTS.json`) (to check `commands.spread-layout.available` -- visual group only)
+- `.manuscript/illustrations/ART-DIRECTION.md` if it exists (for visual style consistency)
+- `.manuscript/OUTLINE.md` (to get spread content -- for picture books, each spread is an atomic unit)
+- Drafted spread content if it exists (the text and scene description for this spread)
+
+**Check availability:**
+
+Look up the current work type's group in CONSTRAINTS.json. If the group is in `commands.spread-layout.hidden` (prose, script, academic, poetry, interactive, speech_song, sacred), inform the writer:
+
+> Spread-layout is designed for children's books and picture books. Your [work_type] project uses different layout tools.
+
+Then **stop**.
+
+---
+
+### Spread Analysis
+
+<spread_analysis>
+  Read the content for spread `<spread-number>` from OUTLINE.md and any drafted content.
+
+  Determine:
+  - **Text content:** The actual text for this spread (or summary if not yet drafted)
+  - **Text length:** Word count to determine text zone size
+  - **Illustration subject:** What should be illustrated on this spread
+  - **Emotional tone:** How this spread should feel visually
+  - **Narrative function:** Is this a quiet moment, action beat, reveal, opening, climax, denouement?
+  - **Page turn impact:** What comes before and after -- is this a surprise reveal on page turn?
+</spread_analysis>
+
+---
+
+### Layout Generation (D-04 ASCII Grid)
+
+<layout_generation>
+  Generate the spread layout using ASCII grid per D-04, showing both pages of the two-page spread with labeled zones.
+
+  **Standard picture book dimensions:**
+  - Single page: 10" x 8" (landscape) or 8.5" x 11" (portrait)
+  - Full spread: 20" x 8" (landscape) or 17" x 11" (portrait)
+  - Use dimensions from config.json `trim_size` if set, otherwise default to 10" x 8" landscape
+
+  **Text-to-illustration ratio:**
+  - Default: 30% text / 70% illustration for picture books
+  - Override with `--text-ratio <percent>` (e.g., `--text-ratio 40` for 40% text / 60% illustration)
+  - Text-heavy spreads (> 50%) are unusual -- warn if requested
+
+  **Zone Labels:**
+  - `[TEXT]` -- Where text is placed, with actual text excerpt
+  - `[ILLUSTRATION]` -- Illustration zone with scene description
+  - `[BLEED]` -- Areas extending beyond trim for full-bleed printing
+  - `[GUTTER]` -- Center binding area (wider inner margin, typically 0.5"-0.75")
+  - `[SAFE]` -- Safe area for critical content (0.25" from trim)
+
+  **Output Format:**
+
+  ```markdown
+  # Spread [N] Layout
+
+  **Title/Caption:** "[spread title or key text excerpt]"
+  **Text ratio:** [N]% text / [N]% illustration
+  **Page dimensions:** [width]" x [height]" per page ([total width]" x [height]" spread)
+
+  ## Layout Grid
+
+  SPREAD [N] -- "[short description]"
+  +--------------------+--+--------------------+
+  |                    |  |                    |
+  |  [ILLUSTRATION]    |G |  [ILLUSTRATION]    |
+  |                    |U |                    |
+  |  [scene desc]      |T |                    |
+  |                    |T |--------------------+
+  |                    |E |                    |
+  |  [BLEED -->]       |R |  [TEXT]            |
+  |                    |  |  "Actual text      |
+  |                    |  |   from the spread  |
+  |                    |  |   goes here..."    |
+  +--------------------+--+--------------------+
+         LEFT PAGE              RIGHT PAGE
+
+  ## Left Page
+  - **Zone:** [Full bleed illustration | Partial illustration | Text + illustration]
+  - **Illustration direction:** [What to depict -- characters, setting, action]
+  - **Bleed:** [Which edges bleed -- top, bottom, left, or all]
+  - **Key focal point:** [Where the eye should go]
+
+  ## Right Page
+  - **Zone:** [Breakdown of text vs illustration areas]
+  - **Text placement:** [Top, bottom, center, wrapped around illustration]
+  - **Text content:** [The actual text or excerpt for this page]
+  - **Illustration direction:** [What to depict in remaining space]
+
+  ## Typography Notes
+  - **Font size suggestion:** [based on target age group -- larger for younger readers]
+  - **Text alignment:** [left, centered, ragged right]
+  - **Text background:** [transparent over illustration | solid panel | semi-transparent overlay]
+
+  ## Production Notes
+  - **Gutter safety:** Keep critical text/image content 0.5" from center binding
+  - **Bleed extension:** Extend bleed illustrations 0.125" beyond trim on all bleed edges
+  - **Safe area:** Keep essential text 0.25" inside trim on all edges
+  - **Color notes:** [From ART-DIRECTION.md -- dominant colors for this spread]
+  ```
+
+  **Layout Variations by Narrative Function:**
+
+  - **Opening spread:** Full bleed illustration across both pages, minimal text (title or opening line)
+  - **Action spread:** Dynamic composition, illustration dominates, text integrated into scene
+  - **Quiet moment:** More text space, illustration as vignette or partial page
+  - **Climax/reveal:** Full bleed illustration, text minimal or absent (let the art speak)
+  - **Denouement:** Balanced text and illustration, calming composition
+  - **Final spread:** Can mirror opening spread structure for satisfying bookend
+
+  Adapt the grid layout to match the narrative function of this particular spread.
+</layout_generation>
+
+---
+
+### Output
+
+Create the output directory if needed:
+```bash
+mkdir -p .manuscript/illustrations/spreads/
+```
+
+Save to `.manuscript/illustrations/spreads/spread-{number}-layout.md`
+
+Commit: `illustration: generate spread layout for spread {number}`
+
+After saving, tell the writer:
+> Spread layout saved to `.manuscript/illustrations/spreads/spread-{number}-layout.md`.
+>
+> The layout shows [TEXT] and [ILLUSTRATION] zones with bleed areas marked.
+> Share this with your illustrator or use as reference for AI image generation.
+>
+> Adjacent spreads: `/scr:spread-layout {prev}` | `/scr:spread-layout {next}`
+
+---
+
+### Edge Cases
+
+- **Spread not in outline:** "Spread {number} is not in your outline. Your book has {N} spreads. Check `/scr:progress` for the outline structure."
+- **No drafted content:** Generate layout from OUTLINE.md beat description. Note: "Layout based on outline. Draft the spread text for more precise text zone sizing."
+- **Text too long for ratio:** Warn and suggest either splitting across two spreads or increasing text ratio: "The text for this spread is {N} words, which may be too long for {ratio}% text area. Consider splitting into two spreads or using `--text-ratio {suggested}`."
+- **Full-bleed no-text spread:** Valid for climactic moments. Generate illustration-only spread with no text zone.
+- **ART-DIRECTION.md missing:** Generate layout without color/style notes. Suggest: "Run `/scr:art-direction` for visual consistency guidance."
+- **Non-picture-book work type:** Hard stop per CONSTRAINTS.json availability check.
+
+## Response Contract
+
+Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.
+
+Use this format:
+
+```markdown
+Next commands:
+- `/scr:...`: One short sentence explaining what this path will do.
+- `/scr:...`: One short sentence explaining what this alternate path will do.
+```
+
+If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.
+
+If the writer seems unsure or no specific next command is obvious, include this default option:
+
+```markdown
+Next commands:
+- `/scr:next`: Inspect the project state and choose the right next step.
+```
+
+If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.

package/commands/scr/storyboard.md

@@ -0,0 +1,262 @@
+---
+description: Generate storyboard frames for script and visual work types with camera direction.
+argument-hint: "[--scene <ref>] [--act <number>]"
+---
+
+# /scr:storyboard -- Storyboard Frame Generator
+
+Generate storyboard frames with shot types, camera movement, transitions, and ASCII composition sketches for script and visual work types.
+
+## Usage
+```
+/scr:storyboard [--scene <ref>] [--act <number>]
+```
+
+## Instruction
+
+You are generating storyboard frames for a script or visual project. Load:
+- `.manuscript/config.json` (to get `work_type`)
+- Scriveno's installed/shared `CONSTRAINTS.json` (global `~/.scriveno/data/CONSTRAINTS.json` or project `.scriveno/data/CONSTRAINTS.json`) (to check `commands.storyboard.available` -- script and visual groups only)
+- `.manuscript/illustrations/ART-DIRECTION.md` if it exists (for visual style consistency)
+- `.manuscript/OUTLINE.md` (for scene/beat structure)
+- Drafted scene files for content
+
+**Check availability:**
+
+Look up the current work type's group in CONSTRAINTS.json. If the group is in `commands.storyboard.hidden` (prose, academic, poetry, interactive, speech_song, sacred), inform the writer:
+
+> Storyboard is designed for scripts and visual projects. Your [work_type] project uses other illustration tools instead. Try `/scr:illustrate-scene` for scene illustration prompts.
+
+Then **stop**.
+
+---
+
+### Scope Selection
+
+<scope_selection>
+  Determine what to storyboard:
+
+  - **No flags:** Generate a thumbnail overview storyboard for the entire work. Use 1 frame per scene/beat, showing the key visual moment. This gives a bird's-eye view of the visual story.
+
+  - **`--scene <ref>`:** Generate detailed frames for a single scene. Break the scene into individual beats, each getting its own frame with full camera direction. Typically 3-12 frames per scene depending on complexity.
+
+  - **`--act <number>`:** Generate frames for all scenes in the specified act. Use OUTLINE.md to identify which scenes belong to the act. Medium detail -- 2-4 frames per scene.
+
+  If the specified scene or act has no drafted content, use OUTLINE.md beat descriptions for frame content. Note: "Frames generated from outline beats. Draft the scene for more detailed storyboard frames."
+</scope_selection>
+
+---
+
+### Frame Generation (D-05 Camera Direction)
+
+<frame_generation>
+  For each frame, generate the following per D-05:
+
+  **Shot Types** (choose one per frame):
+  - `ESTABLISHING` -- Wide shot that sets location/context
+  - `WIDE` -- Full scene visible, characters in environment
+  - `MEDIUM` -- Character(s) from waist up, conversational distance
+  - `CLOSE-UP` -- Face or important object fills frame
+  - `EXTREME CLOSE-UP` -- Eyes, hands, small detail
+  - `OVER-THE-SHOULDER` -- Dialogue framing, one character's perspective
+  - `POV` -- Camera is a character's eyes
+  - `AERIAL` -- Bird's-eye view, establishing scale
+  - `LOW ANGLE` -- Looking up, conveys power/threat
+  - `HIGH ANGLE` -- Looking down, conveys vulnerability/overview
+  - `TWO-SHOT` -- Two characters framed together
+  - `GROUP` -- Multiple characters in frame
+
+  **Camera Movement** (choose one per frame):
+  - `STATIC` -- Camera does not move
+  - `PAN LEFT/RIGHT` -- Horizontal rotation on axis
+  - `PAN UP/DOWN` -- Vertical rotation on axis (tilt)
+  - `DOLLY IN/OUT` -- Camera physically moves toward/away from subject
+  - `DOLLY ALONGSIDE` -- Camera moves parallel to subject movement
+  - `ZOOM IN/OUT` -- Lens zoom (different feel from dolly)
+  - `CRANE UP/DOWN` -- Vertical camera movement
+  - `HANDHELD` -- Shaky, documentary feel
+  - `STEADICAM` -- Smooth tracking shot following subject
+  - `RACK FOCUS` -- Focus shifts between foreground and background
+
+  **Transitions** (to the next frame):
+  - `CUT` -- Instant change (default, most common)
+  - `DISSOLVE` -- Gradual blend to next frame (passage of time)
+  - `FADE TO BLACK` -- Scene ending
+  - `FADE FROM BLACK` -- Scene beginning
+  - `WIPE` -- One image pushes another off screen (stylistic)
+  - `MATCH CUT` -- Visual or thematic link between frames (same shape, motion, or concept)
+  - `SMASH CUT` -- Abrupt jarring transition for contrast
+  - `J-CUT / L-CUT` -- Audio from next/previous scene overlaps
+
+  **Frame Output Format:**
+
+  ```
+  [FRAME NN] Scene X, Beat Y -- SHOT_TYPE
+  Shot: [shot type] | Camera: [movement] | Transition: [to next]
+  +---------------------------+
+  |                           |
+  |   [ASCII COMPOSITION]     |
+  |                           |
+  |   [KEY ELEMENTS LABELED]  |
+  |                           |
+  +---------------------------+
+  Description: [What is in frame -- characters, action, key props, environment]
+  Dialogue/VO: [Key line of dialogue or voiceover, if any. "--" if none]
+  Duration: [quick (< 2s) | standard (2-5s) | lingering (5-10s) | extended (10s+)]
+  Mood/Lighting: [Atmosphere -- e.g., "warm golden hour, long shadows, intimate"]
+  ```
+
+  **ASCII Composition Sketches:**
+
+  Use simple ASCII art to show spatial relationships:
+  - `[CHAR]` or character initials for character positions
+  - `[BG]` for background elements
+  - `[FG]` for foreground elements
+  - `[PROP]` for important objects
+  - Horizontal/vertical lines to show depth planes
+  - Arrow indicators for movement direction
+
+  Examples:
+
+  ```
+  Establishing shot:
+  +---------------------------+
+  |  [SKY/HORIZON]            |
+  |                           |
+  |    [BUILDING]     [TREE]  |
+  |  [CHAR A]                 |
+  |  [FOREGROUND PATH]        |
+  +---------------------------+
+
+  Close-up dialogue:
+  +---------------------------+
+  |                           |
+  |      [CHAR A FACE]        |
+  |      eyes: determined     |
+  |      mouth: speaking      |
+  |                           |
+  +---------------------------+
+
+  Over-the-shoulder:
+  +---------------------------+
+  |                           |
+  | [CHAR A         [CHAR B]  |
+  |  shoulder/       facing   |
+  |  back of         camera]  |
+  |  head]                    |
+  +---------------------------+
+  ```
+</frame_generation>
+
+---
+
+### Storyboard Assembly
+
+<storyboard_assembly>
+  Assemble all frames into a complete storyboard document:
+
+  ```markdown
+  # Storyboard: [Title/Reference]
+
+  **Work:** [title from config.json]
+  **Scope:** [Entire work | Scene: {ref} | Act: {number}]
+  **Total frames:** [count]
+  **Generated from:** [outline beats | drafted scenes | mix]
+
+  ## Visual Style Notes
+  [From ART-DIRECTION.md if it exists -- key style reminders for visual consistency]
+
+  ---
+
+  ## [Scene/Act Header]
+
+  [FRAME 01] ...
+  [FRAME 02] ...
+  ...
+
+  ---
+
+  ## Shot Distribution Summary
+
+  | Shot Type | Count | Percentage |
+  |-----------|-------|------------|
+  | Establishing | N | N% |
+  | Wide | N | N% |
+  | Medium | N | N% |
+  | Close-up | N | N% |
+  | ... | | |
+
+  ## Transition Summary
+
+  | Transition | Count |
+  |------------|-------|
+  | Cut | N |
+  | Dissolve | N |
+  | ... | |
+
+  ## Pacing Notes
+  [Brief analysis of visual pacing -- where the rhythm speeds up (quick cuts) or slows down (lingering shots). Flag any sequences that may feel monotonous (too many similar shots in a row).]
+  ```
+
+  **Frame numbering:** Sequential across the entire storyboard (FRAME 01, FRAME 02, ...) regardless of scene boundaries.
+
+  **Scene boundaries:** Insert a horizontal rule (`---`) and scene header between scenes.
+</storyboard_assembly>
+
+---
+
+### Output
+
+Create the output directory if needed:
+```bash
+mkdir -p .manuscript/illustrations/storyboards/
+```
+
+Save to `.manuscript/illustrations/storyboards/storyboard-{ref}.md` where `{ref}` is:
+- `full` for entire work
+- Scene reference for `--scene`
+- `act-{number}` for `--act`
+
+Commit: `storyboard: generate frames for {ref}`
+
+After saving, tell the writer:
+> Storyboard saved to `.manuscript/illustrations/storyboards/storyboard-{ref}.md`.
+>
+> Each frame includes shot type, camera direction, and ASCII composition.
+> Use this as a shot list for production or as illustration direction.
+>
+> For more detail on a specific scene: `/scr:storyboard --scene {ref}`
+
+---
+
+### Edge Cases
+
+- **No drafted scenes:** Generate frames from OUTLINE.md beat descriptions. Note reduced detail level.
+- **No OUTLINE.md:** Cannot generate storyboard -- "Create an outline first with `/scr:plan`."
+- **Very long work (50+ scenes):** For full-work overview, limit to 1 frame per scene with thumbnail-level detail. Suggest `--act` for more detail.
+- **Scene with no action:** Focus on atmosphere, environment, and character positioning. Use static/lingering frames.
+- **Musical/song sequences:** Use duration notes extensively, mark rhythm changes.
+- **ART-DIRECTION.md missing:** Generate storyboard without visual style notes. Suggest: "Run `/scr:art-direction` for visual consistency across storyboard frames."
+
+## Response Contract
+
+Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.
+
+Use this format:
+
+```markdown
+Next commands:
+- `/scr:...`: One short sentence explaining what this path will do.
+- `/scr:...`: One short sentence explaining what this alternate path will do.
+```
+
+If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.
+
+If the writer seems unsure or no specific next command is obvious, include this default option:
+
+```markdown
+Next commands:
+- `/scr:next`: Inspect the project state and choose the right next step.
+```
+
+If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.

package/commands/scr/subject-touch.md

@@ -0,0 +1,168 @@
+---
+description: Update an evolving subject, idea, claim, procedure, doctrine, object, image pattern, or reader-state thread after a unit lands.
+argument-hint: "<subject> [--from <unit>]"
+---
+
+# /scr:subject-touch -- Update Subject Movement
+
+Subject files are living documents. THEMES.md, QUESTIONS.md, REFERENCES.md, DOCTRINES.md, PROCEDURES.md, and related adapted files record what the work is making the reader understand, feel, notice, believe, test, or do. Without periodic touch-ups, a theme, claim, object, procedure, doctrine, or reader promise can freeze in its early form while the manuscript has already changed its meaning.
+
+This command is the touch-up surface for non-character movement. Use it after `/scr:draft` or `/scr:editor-review`, especially when a unit changes the meaning of an object, develops an argument, resolves a misconception, alters the reader's ability, changes a doctrine's practical emphasis, or makes a procedure safer or clearer.
+
+## Usage
+
+```
+/scr:subject-touch <subject>                  # interactive update
+/scr:subject-touch <subject> --from <unit>    # base the update on a specific unit's drafted prose
+```
+
+If `<subject>` is omitted, list tracked subjects from the adapted subject files and ask which to update.
+
+## Instruction
+
+### STEP 0: BOOTSTRAP
+
+Read `.manuscript/CONTEXT.md` first if it exists. If its `Updated` timestamp is newer than `.manuscript/STATE.md` and newer than the newest file in `.manuscript/drafts/body/`, use it for orientation (project title, work type, current unit, recent activity). Step 1 still needs the full subject files because you may edit one. See `docs/context-protocol.md`.
+
+### STEP 1: LOAD CONTEXT
+
+Load these project files:
+
+- `.manuscript/config.json` -- to determine work type and file adaptations
+- Scriveno's installed/shared `CONSTRAINTS.json` -- to map adapted subject files
+- `.manuscript/WORK.md` and `.manuscript/BRIEF.md` or adapted equivalent -- reader promise and reader journey
+- The adapted subject files that exist:
+  - `.manuscript/THEMES.md` or `.manuscript/QUESTIONS.md`, `.manuscript/REFERENCES.md`, or `.manuscript/DOCTRINES.md`
+  - `.manuscript/PLOT-GRAPH.md`, `.manuscript/ARGUMENT-MAP.md`, `.manuscript/PROCEDURES.md`, or `.manuscript/THEOLOGICAL-ARC.md`
+  - `.manuscript/WORLD.md`, `.manuscript/CONTEXT.md`, `.manuscript/SYSTEM.md`, or `.manuscript/COSMOLOGY.md` when the subject is a place, system, setting pressure, or operating context
+- `.manuscript/STATE.md` -- to know which units have been drafted
+- The drafted unit file for the touch-up basis: `.manuscript/drafts/body/{N}-*-DRAFT.md` either for the unit named in `--from` or, if `--from` is omitted, the most recently modified draft file
+
+### STEP 2: RESOLVE THE SUBJECT
+
+If the writer named a subject, find the closest matching heading or table row across the adapted subject files. Search case-insensitively across headings, theme names, research questions, doctrine names, procedure names, reference topics, object names, place names, and image patterns.
+
+If no match is found, suggest the closest subjects and ask whether to create a new entry. Do not create a new subject without writer approval.
+
+If the writer did not name a subject, list tracked subjects grouped by source file and ask which one to update.
+
+### STEP 3: PROPOSE A DELTA
+
+Read the basis draft file from STEP 1. Identify how the subject changed in this unit. Cover these dimensions; skip any that did not change:
+
+1. **Reader state** -- what the reader understands, feels, notices, can do, or can verify now
+2. **Pressure or friction** -- misconception, counterclaim, risk, ambiguity, failure mode, constraint, grief, uncertainty, or practical obstacle
+3. **Interaction pattern** -- claim vs. counterclaim, rule vs. exception, step vs. failure mode, doctrine vs. practice, evidence vs. objection, object vs. meaning, place vs. memory, image vs. theme
+4. **Evidence or example** -- new proof, reference, scene evidence, procedure evidence, or concrete example now available
+5. **Watchpoint** -- what the next plan, draft, or review should preserve or test
+
+Present the proposed delta to the writer in this exact format:
+
+```
+Subject: <subject>
+Basis: <unit name from draft filename>
+Source file: <file to update>
+
+Proposed updates:
+
+  Reader state
+    was: <current text or inferred prior state>
+    now: <proposed new text>
+
+  Pressure or friction
+    + <new or sharpened pressure>
+
+  Interaction pattern
+    <pattern>: <new state>
+
+  Evidence or example
+    + <new evidence, example, citation, procedure checkpoint, image, or scene evidence>
+
+  Watchpoint
+    + <thing to preserve or test later>
+
+Apply these updates? (yes / no / edit)
+```
+
+If the writer accepts (`yes`), proceed to STEP 4. If `edit`, ask which dimension to revise and re-prompt. If `no`, exit with no changes and no log entry.
+
+### STEP 4: APPLY THE DELTA
+
+Update the relevant adapted subject file while preserving formatting:
+
+- For `THEMES.md`, update the matching theme or subject-dynamics entry.
+- For `QUESTIONS.md`, update the matching research question, claim, evidence gap, or reader-state note.
+- For `REFERENCES.md`, update source-of-truth, evidence, version, failure-mode, or verification notes.
+- For `DOCTRINES.md`, update practical emphasis, doctrinal pressure, interpretive watchpoints, or source evidence.
+- For `PROCEDURES.md`, update validation, rollback, failure mode, prerequisite, or subject dynamics notes.
+- For `ARGUMENT-MAP.md`, update claim, counterclaim, evidence, transition, or unresolved question notes.
+- For setting, system, object, or place subjects, update the adapted context file that already owns the subject.
+
+Create a `### Subject dynamics` subsection under the matching entry if the file has no obvious place for reader state, pressure, interaction pattern, evidence, or watchpoints.
+
+**Do not touch:**
+
+- STYLE-GUIDE.md or voice rules
+- Draft prose
+- Character voice anchors or character state, unless the writer explicitly asked for `/scr:character-touch`
+- Source citations in a way that invents support not present in the draft or source files
+- Technical safety instructions without preserving validation and rollback context
+
+### STEP 5: STAMP THE UPDATE
+
+Add or replace a one-line marker under the updated subject entry:
+
+```
+_Last touched: {ISO timestamp} -- after drafting <unit name>_
+```
+
+### STEP 6: HISTORY LOG
+
+Append one line to `.manuscript/HISTORY.log` per `docs/history-protocol.md`:
+
+```
+{ISO timestamp} | scr:subject-touch | subject=<subject> | basis=<unit name> | file=<updated file> | dimensions=<comma-separated list of changed dimensions> | outcome=ok
+```
+
+If the writer chose `no` and exited with no changes, do not append a line.
+
+### STEP 7: SUGGEST NEXT
+
+End with a one-line suggestion:
+
+> Updated <subject>. Future plans and drafts will read the revised subject movement. Consider `/scr:editor-review <unit>` if the change came from a fresh draft.
+
+## Edge Cases
+
+- **Character and subject both shifted:** Suggest `/scr:character-touch <name>` after this command if the character state also changed.
+- **Subject is a person:** If the requested subject is clearly a character or figure, route to `/scr:character-touch` instead.
+- **Academic evidence changed:** Do not strengthen a claim beyond its cited support. Mark unsupported movement as a watchpoint or question.
+- **Technical procedure changed:** Preserve safety, validation, and rollback. If the draft implies unsafe guidance, mark a blocking question instead of updating the procedure as if it were approved.
+- **Sacred doctrine changed:** Preserve the project's framework and source-tracking rules. If the draft creates a doctrinal tension, record it as a watchpoint or blocking question rather than smoothing it away.
+
+## Response Contract
+
+Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.
+
+Use this format:
+
+```markdown
+Next commands:
+- `/scr:...`: One short sentence explaining what this path will do.
+- `/scr:...`: One short sentence explaining what this alternate path will do.
+```
+
+If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.
+
+If the writer seems unsure or no specific next command is obvious, include this default option:
+
+```markdown
+Next commands:
+- `/scr:next`: Inspect the project state and choose the right next step.
+```
+
+If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.
+
+## Tone
+
+Brisk and editorial. Surface the proposed delta, get a yes / no / edit answer, apply, get out. The writer remains the authority on what the work means.

package/commands/scr/submit.md

@@ -0,0 +1,50 @@
+---
+description: Package and finalize a unit after editor review.
+argument-hint: "[unit number]"
+---
+
+# Submit {unit}
+
+You are finalizing a unit after editor review.
+
+## Adaptive naming
+
+Load `.manuscript/config.json` for `command_unit`. The runnable command stays `/scr:submit`; adapt the unit terminology in prompts and summaries.
+
+## Prerequisites
+
+- Review report must exist at `.manuscript/reviews/{N}-REVIEW.md`. For older projects, root-level `{N}-EDITOR-NOTES.md` also counts as a legacy review artifact.
+
+## What to do
+
+1. Load `.manuscript/config.json` for project context
+2. Check that the specified unit has been through editor review. Prefer `.manuscript/reviews/{N}-REVIEW.md`; if it is missing, accept legacy `{N}-EDITOR-NOTES.md`.
+3. Mark the unit as submitted in `STATE.md`
+4. Report: "Unit {N} submitted. {remaining} units remaining."
+
+## Response Contract
+
+Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.
+
+Use this format:
+
+```markdown
+Next commands:
+- `/scr:...`: One short sentence explaining what this path will do.
+- `/scr:...`: One short sentence explaining what this alternate path will do.
+```
+
+If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.
+
+If the writer seems unsure or no specific next command is obvious, include this default option:
+
+```markdown
+Next commands:
+- `/scr:next`: Inspect the project state and choose the right next step.
+```
+
+If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.
+
+## Tone
+
+Brief and confirmational. The writer has already done the hard work.