scriveno 2.5.0 → 2.7.1

package/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/aihxp/scriveno/actions/workflows/ci.yml/badge.svg)](https://github.com/aihxp/scriveno/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Version](https://img.shields.io/badge/version-2.5.0-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-2.7.1-blue)](CHANGELOG.md)
 [![npm](https://img.shields.io/npm/v/scriveno.svg)](https://www.npmjs.com/package/scriveno)
 [![Downloads](https://img.shields.io/npm/dm/scriveno.svg)](https://www.npmjs.com/package/scriveno)
 [![Status CLI](https://img.shields.io/badge/status%20CLI-scriveno%20status-blue)](docs/runtime-support.md#shared-auto-invoke-engine)
@@ -40,7 +40,7 @@ Scriveno is a command system that turns your AI coding agent into a voice-preser
 The wedge comes first: Scriveno profiles the writer, loads that voice into every drafting step, and keeps each unit on fresh context so the prose stays specific to the project. From there, it expands into 113 writing commands covering the rest of the pipeline:
 
 - **Create** -- Set up a project with tailored context files. Progressive onboarding, never overwhelming.
-- **Write** -- Discuss, plan, draft, and revise one unit at a time. The drafter agent loads your Voice DNA and writes in *your* voice, not generic AI prose.
+- **Write** -- Discuss, plan, draft, and revise one unit at a time. The drafter agent loads your Voice DNA and writes in *your* voice, not generic AI prose. Run `/scr:progress` any time to open a per-unit ledger (`.manuscript/PROGRESS.md`) showing what is done, in progress, and untouched.
 - **Polish** -- Editor review, line edit, copy edit, continuity check, voice check, beta reader simulation, sensitivity review.
 - **Publish** -- Front/back matter, cover art, blurbs, query letters, KDP packages, IngramSpark packages, EPUB, PDF, Fountain, Final Draft, LaTeX.
 - **Translate** -- Deep translation with glossary management, cultural adaptation, back-translation verification, multi-language simultaneous publishing.
@@ -141,6 +141,8 @@ For sacred and historical texts, Voice DNA is supplemented by 10 sacred voice re
 
 **Interactive:** interactive fiction, game narrative
 
+**Speech:** speech
+
 **Sacred & historical:** scripture (Biblical, Quranic, Torah, Vedic, Buddhist, generic), commentary/exegesis, devotional, liturgical text, historical chronicle, historical account, mythological collection, religious epic, sermon, homiletic collection
 
 Each work type has its own structural hierarchy and **industry-standard word count and page range guidance** -- a novel targets 70,000-100,000 words across 20-35 chapters, a screenplay targets 90-120 pages across 3-5 acts. These ranges guide outlining, progress tracking, and drafter pacing. The runnable command ids stay stable, while Scriveno adapts the wording around them -- a Torah commentary still runs `/scr:plan 3`, but frames that work as planning Parashah 3.
@@ -244,11 +246,11 @@ Scriveno currently ships installer targets for these AI tooling environments:
 
 ## Status
 
-**Version:** 2.5.0
+**Version:** 2.7.1
 
 Scriveno's core command surface is stable across 113 commands, 50 work types, and 11 installer targets. The current repo baseline includes shipped planning milestones through `v2.0 Publishing Cover Packaging`, plus the creative-context, record-store, branching-next, runtime-sync, adaptive concierge, human-first writing-safeguard, authenticity-diagnostic, domain-grilling, installer-marker cleanup, cross-runtime agent metadata, visible automation status, the shared `scriveno status --project .` auto-invoke engine, route-intelligence lanes, safe apply reporting, runtime smoke checks, agent availability checks, route graph audits, the full audit repair pass through `2.0.11`, the first-run proof surface in `2.5.0`, and the executable `/scr:first-run` path. See [Quick Proof](docs/quick-proof.md) for the fastest proof path, [Shipped Assets](docs/shipped-assets.md) for the canonical asset inventory, and [Runtime Support](docs/runtime-support.md) for the runtime compatibility matrix.
 
-Version `2.5.0` publishes Scriveno under the package name `scriveno`, so the current install command is `npx scriveno@latest`. The older `scriveno-cli` package name is historical and was unpublished during the rename, so npm cannot attach a deprecation notice to it while it has no active registry record. The older `scriven-cli` package remains on npm only as a deprecated legacy name that points users to `scriveno`. Do not treat either legacy package name as active unless a deliberate compatibility shim is republished. See [CHANGELOG](CHANGELOG.md) for the full list and [docs/release-notes.md](docs/release-notes.md) for the public-facing summary.
+Version `2.7.1` publishes Scriveno under the package name `scriveno`, so the current install command is `npx scriveno@latest`. The older `scriveno-cli` package name is historical and was unpublished during the rename, so npm cannot attach a deprecation notice to it while it has no active registry record. The older `scriven-cli` package remains on npm only as a deprecated legacy name that points users to `scriveno`. Do not treat either legacy package name as active unless a deliberate compatibility shim is republished. See [CHANGELOG](CHANGELOG.md) for the full list and [docs/release-notes.md](docs/release-notes.md) for the public-facing summary.
 
 Package history is tracked in [CHANGELOG.md](CHANGELOG.md), and the public-facing summary for this release is in [docs/release-notes.md](docs/release-notes.md).
 

package/agents/voice-checker.md

@@ -147,6 +147,16 @@ Map the band to the existing tiers:
 - **60-74, Mixed signals (notable) / leaning AI:** Fail. Noticeable drift. Offer to re-draft problem sections.
 - **Below 60, Reads AI-generated:** Severe. Clustered dead-giveaways, uniform rhythm, or chat-artifact contamination. Do not proceed. Recommend re-drafting with an updated STYLE-GUIDE.md or running `/scr:voice-test` to recalibrate.
 
+### Normalized drift (for callers that need a 0-1 figure)
+
+Some callers -- `/scr:draft`, `/scr:autopilot`, and the `voice.drift_threshold` config knob -- need drift on a 0-1 scale rather than this 0-100 score. Convert with:
+
+```
+drift = (100 - score) / 100
+```
+
+So a score of 100 is 0.00 drift, 90 is 0.10, 70 is 0.30, 60 is 0.40. The default `drift_threshold` of 0.3 therefore means "pause or offer a re-draft when the voice score falls below 70" -- the FAIL band and worse. This is the single definition of drift; callers reference it rather than inventing their own scale.
+
 Before finalizing a low score, re-read the strongest human markers you found and ask whether the band is honestly supported. Scoring genuine careful human prose low because it is formal or clean is this check's worst failure.
 
 ## Tone

package/commands/scr/autopilot-publish.md

@@ -78,7 +78,7 @@ Continuity check: 1 warning
 Proceeding with export. Review full reports after completion.
 ```
 
-**Quality gate policy (D-09):** Always proceed to the export pipeline regardless of quality gate results. The quality gate is advisory -- it gives the writer information, not a veto. Even if voice check scores FAIL (below 60) or continuity check finds major contradictions, log the warnings and continue.
+**Quality gate policy (D-09):** The quality gate is advisory and never blocks. Always proceed to the export pipeline, including when the voice check or continuity check finds problems. autopilot-publish is the unattended path: it does not stop to ask the writer and it does not abort the run. The gate exists to make problems visible, not to veto. One case gets extra visibility: when the voice score is below 60 (the voice-checker's "Reads AI-generated / do not proceed" band), flag it prominently in the quality-gate summary, write the full voice-check report to the output directory, and list it as the top issue in the final completion report with an explicit recommendation to re-draft the flagged units before publishing. Still finish the export so the run stays unattended; the writer decides whether to publish the package or re-draft after reading the report.
 
 ---
 

package/commands/scr/autopilot-translate.md

@@ -56,8 +56,8 @@ RTL_LANGUAGES = ["ar", "he", "ur", "fa", "yi", "ps", "sd"]
 CJK_LANGUAGES = ["zh", "ja", "ko"]
 ```
 
-- RTL languages receive `--text-direction rtl` when passed to export commands
-- CJK languages receive appropriate font and spacing flags
+- RTL languages: `/scr:multi-publish` derives text direction from the language code, so no extra flag is needed
+- CJK languages: `/scr:multi-publish` applies CJK font and spacing handling from the language code
 - All other languages default to LTR
 
 Log the detection:
@@ -123,9 +123,8 @@ Log drift annotation counts:
 
 If `--skip-publish` is NOT set:
 - Determine text direction for this language (RTL/LTR/CJK from Step 2)
-- Run `/scr:multi-publish --language {lang}` for all available export formats
-- For RTL languages, pass `--text-direction rtl` to ensure correct PDF and EPUB output
-- For CJK languages, pass `--cjk-mode` to enable CJK-specific line breaking and font handling
+- Run `/scr:multi-publish --languages {lang}` for all available export formats
+- RTL and CJK output is handled automatically: `/scr:multi-publish` sets text direction and CJK line breaking from the language code, so no extra flags are required
 
 If `--skip-publish` IS set:
 - Log: `"[fr] Phase 6/6: Multi-publish skipped (--skip-publish)."`
@@ -209,7 +208,7 @@ Next Steps:
 
 - **NEVER** skip the glossary phase -- term consistency across the manuscript depends on it
 - **NEVER** run cultural adaptation before translation is complete for that language
-- **NEVER** export RTL languages without setting `--text-direction rtl` -- the PDF and EPUB will be unreadable
+- **ALWAYS** confirm the language code is correct before export; `/scr:multi-publish` uses it to set RTL direction and CJK handling, and a wrong code yields unreadable PDF and EPUB
 - **NEVER** continue past a blocking error without logging it -- all errors must appear in the completion summary
 - **NEVER** modify the source manuscript -- translation works on copies in `.manuscript/translation/{lang}/`
 

package/commands/scr/autopilot.md

@@ -38,7 +38,7 @@ FOR each unit in OUTLINE.md (starting from current position):
     If writer says "skip": advance to next unit, update STATE.md
 ```
 
-When the loop completes (all units through all stages), show a completion summary: total units, total word count, voice consistency across the manuscript, open record threads or promises, and any flags or issues encountered.
+When the loop completes (all units through all stages), show a completion summary: total units, total word count, voice consistency across the manuscript, open record threads or promises, any flags or issues encountered, and a pointer to the per-unit ledger at `.manuscript/PROGRESS.md`.
 
 ## Profile rules
 
@@ -88,7 +88,7 @@ The writer trusts the pipeline. Autopilot runs until the entire manuscript is co
 **Pause behavior:** Run until ALL units are complete. Pause ONLY on these conditions:
 
 1. **Continuity contradiction** the agent cannot resolve (e.g., a character is in two places at once, a previously established fact is contradicted)
-2. **Voice drift** exceeding `config.voice.drift_threshold` (default 0.3). After each unit, compare the drafted prose against STYLE-GUIDE.md. If drift exceeds threshold, pause.
+2. **Voice drift** exceeding `config.voice.drift_threshold` (default 0.3). After each unit, run the voice-checker agent against STYLE-GUIDE.md to get an Overall score (0-100). Compute normalized drift as `drift = (100 - score) / 100` (see the "Normalized drift" section of `voice-checker.md`) and pause when `drift` exceeds the threshold -- at the default 0.3 that means a voice score below 70, the voice-checker's FAIL band.
 3. **Plot hole** with no clear resolution path (e.g., a setup with no payoff, a character motivation gap)
 4. **Missing critical information** that prevents drafting (character motivation gap, setting inconsistency, unresolved plot dependency)
 5. **Record drift** against `.manuscript/RECORD.md` that the agent cannot resolve safely (e.g., a promised payoff is contradicted, an open thread is closed without being recorded, or a next-unit obligation is skipped)
@@ -108,7 +108,7 @@ The writer trusts the pipeline. Autopilot runs until the entire manuscript is co
 **On completion:** Show a comprehensive summary:
 - Total units drafted
 - Total word count
-- Voice consistency score across the manuscript
+- Voice consistency: the voice-checker Overall score (0-100), averaged across the units that were voice-checked during the run
 - Open record threads, reader promises, and unresolved next-unit obligations from RECORD.md
 - Any flags or issues encountered during the run
 - List of any quality gate pauses that occurred and how they were resolved
@@ -141,6 +141,7 @@ After each stage execution:
 2. Update progress counters: `units_discussed`, `units_planned`, `units_drafted`, `units_reviewed`, `units_submitted`
 3. Update `current_unit` and next step
 4. Update `total_words` running count
+5. Refresh `.manuscript/PROGRESS.md` so the openable ledger advances unit by unit during the run, per `docs/progress-protocol.md`
 
 On pause or stop:
 1. Write current position to "Session handoff" section so `--resume` can pick up exactly where you left off
@@ -168,6 +169,7 @@ Spawned agents:
 - continuity-checker: {count}
 Local operations:
 - STATE.md updated: yes/no
+- PROGRESS.md refreshed: yes/no
 - HISTORY.log updated: yes/no
 Pause:
 - status: none/guided/supervised/quality-gate/blocker
@@ -201,11 +203,13 @@ If the command stops because a prerequisite is missing, suggest the command that
 
 ## Tone
 
-**Progress updates:** Concise, one line per unit.
-- "Drafted chapter 3: 1,247 words. Voice check: passed."
+**Progress updates:** Concise, one line per unit, anchored to the whole manuscript so progress is visible during the run.
+- "Drafted chapter 3 (3 of 12, 25%): 1,247 words. Voice check: passed."
 - "Planned scenes 1-4 for chapter 5."
 - "Editor review complete for chapter 2: 3 notes."
 
+Every few units, show a one-line manuscript bar pulled from the deliverable progress in `docs/progress-protocol.md`, for example: `████░░░░░░ 5/12 chapters done (42%)`. The full per-unit ledger is `.manuscript/PROGRESS.md`.
+
 **At pause points:** Warm, non-technical.
 - "Chapter 3 is ready for your review."
 - "The first act is complete -- 4 chapters, 12,340 words."
@@ -223,7 +227,7 @@ If the command stops because a prerequisite is missing, suggest the command that
 
 - **NEVER** run without updating STATE.md -- resume depends on accurate state
 - **NEVER** show raw git output in writer mode (when `developer_mode` is `false`)
-- **NEVER** skip the voice comparison after drafting -- even if the voice-check command from Phase 4 is not yet available, use the drafter's built-in self-check (Step 4 in drafter.md)
+- **NEVER** skip the voice comparison after drafting -- run the voice-checker agent against STYLE-GUIDE.md; if the host runtime cannot spawn it, fall back to the drafter's built-in self-check (Step 4 in drafter.md)
 - **NEVER** re-draft a unit that STATE.md shows as already submitted -- submitted means the writer approved it
 - **NEVER** skip stages in the chain (discuss-plan-draft-review-submit) unless the writer explicitly says "skip"
 - **NEVER** continue past a quality gate pause in full-auto without writer input -- the whole point is that these are conditions the pipeline cannot resolve alone

package/commands/scr/beta-reader.md

@@ -1,10 +1,13 @@
 ---
-description: Simulate a beta reader's experience of the manuscript with cross-AI peer review.
+description: Simulate a beta reader's experience of the manuscript using a fresh-context reader persona.
+argument-hint: "[N] [--focus <area>]"
 ---
 
-# /scr:beta-reader -- Cross-AI Peer Review
+# /scr:beta-reader -- Reader-Perspective Review
 
-Simulate a beta reader's experience of the manuscript.
+Simulate a beta reader's experience of the manuscript using a fresh-context reader persona.
+
+This command simulates an independent reader in a fresh context using the same model, not a second or external AI. Genuine cross-AI review would require an external CLI call that Scriveno does not currently wire.
 
 ## Usage
 ```

package/commands/scr/build-ebook.md

@@ -153,7 +153,7 @@ Apply tradition data to `.manuscript/output/metadata.yaml` (before STEP 3f write
   - `tibetan` script -> `bo`
   - `devanagari` script -> `sa` (Sanskrit)
   - `latin` script -> use the project language from config.json (default `en`)
-- Set `font-family:` to the first entry in the manifest's `font_stack`.
+- Set `mainfont:` to the first entry in the manifest's `font_stack`. (For the EPUB itself the non-Latin font is applied through `scriveno-epub.css`; `mainfont` keeps the metadata key aligned with the print build.)
 
 If `rtl: true` in the manifest, add `--metadata dir=rtl` to the Pandoc invocation in STEP 4.
 

package/commands/scr/build-print.md

@@ -156,7 +156,7 @@ Apply tradition data to `.manuscript/output/metadata.yaml` (before STEP 3f write
   - `tibetan` script -> `bo`
   - `devanagari` script -> `sa` (Sanskrit)
   - `latin` script -> use the project language from config.json (default `en`)
-- Set `font-family:` to the first entry in the manifest's `font_stack`.
+- Set `mainfont:` to the first entry in the manifest's `font_stack`. (`mainfont` is the Pandoc variable the Typst book/chapbook templates read for the body font; `font-family` is not.)
 
 If `rtl: true` in the manifest, add `--metadata dir=rtl` to the Pandoc invocation in STEP 4.
 
@@ -415,7 +415,7 @@ estimated_pages = Math.round(word_count / manifest.trim_sizes[trim].wpp)
 
 Compare against `manifest.max_pages`:
 - For paperback: compare against `manifest.max_pages.paperback`
-- For hardcover: only KDP hardcover applies -- compare against `manifest.max_pages.hardcover` only if `--hardcover` flag is passed (otherwise use paperback limit)
+- For hardcover: the hardcover page limit applies to KDP only. Compare against `manifest.max_pages.hardcover` only if `--hardcover` was passed AND the platform is `kdp` AND the manifest defines `max_pages.hardcover`. For any other platform (for example `ingram`, which defines only `max_pages.paperback`), ignore `--hardcover` for the page-limit check and use `manifest.max_pages.paperback`.
 
 If `estimated_pages` exceeds the limit:
 

package/commands/scr/continuity-check.md

@@ -1,5 +1,6 @@
 ---
 description: Automated continuity verification to scan for narrative contradictions across the manuscript.
+argument-hint: "[N]"
 ---
 
 # /scr:continuity-check -- Scan for Narrative Contradictions

package/commands/scr/copy-edit.md

@@ -1,5 +1,6 @@
 ---
 description: Perform a correctness pass for grammar, spelling, punctuation, and consistency.
+argument-hint: "[N]"
 ---
 
 # /scr:copy-edit -- Grammar and Correctness Pass

package/commands/scr/dialogue-audit.md

@@ -1,5 +1,6 @@
 ---
 description: Audit dialogue for character voice differentiation, attribution clarity, and talking-head detection.
+argument-hint: "[N]"
 ---
 
 # /scr:dialogue-audit -- Character Dialogue Quality Audit

package/commands/scr/discussion-questions.md

@@ -1,5 +1,6 @@
 ---
 description: Generate reading group discussion questions exploring themes, characters, and craft.
+argument-hint: "[--count <N>]"
 ---
 
 # /scr:discussion-questions -- Reading Group Discussion Questions

package/commands/scr/draft.md

@@ -35,7 +35,7 @@ Require `.manuscript/plans/{N}-*-PLAN.md` files to exist. If none exist, also ch
 
 3. **Save drafted output** to `.manuscript/drafts/body/{N}-{A}-DRAFT.md`.
 
-4. **After all atomic units in the unit are drafted, do a voice-check pass.** Load the full drafted unit, compare against STYLE-GUIDE.md, flag any scenes that drift from the voice profile by more than the configured threshold. If drift is detected, offer to re-draft the problem scenes.
+4. **After all atomic units in the unit are drafted, run a voice-check pass.** Invoke the installed `voice-checker.md` agent in a fresh context on the drafted unit -- the same agent `/scr:voice-check` uses. It loads the unit and STYLE-GUIDE.md and returns an Overall score (0-100). Convert to normalized drift (`drift = (100 - score) / 100`; see the "Normalized drift" section of `voice-checker.md`) and, if drift exceeds `config.voice.drift_threshold` (default 0.3, i.e. a voice score below 70), flag the scenes that drove the score down and offer to re-draft them. If the host runtime cannot spawn the voice-checker, fall back to the drafter's built-in self-check (Step 4 in `drafter.md`) and say so in the status block.
 
 5. **Update RECORD.md.** After drafting, extract what the new draft establishes on page. Update `.manuscript/RECORD.md` with only durable, reader-visible changes:
    - established facts, claims, events, definitions, procedures, objects, relationships, or constraints
@@ -49,9 +49,9 @@ Require `.manuscript/plans/{N}-*-PLAN.md` files to exist. If none exist, also ch
 
 6. **Surface state nudges.** If the drafter emits `CHARACTER STATE NUDGE`, suggest `/scr:character-touch <name>` after drafting. If the drafter emits `SUBJECT DYNAMICS NUDGE`, suggest `/scr:subject-touch <subject>` after drafting. These nudges go to the writer, not into the draft file.
 
-7. **Update STATE.md:** mark unit as drafted, note word count, flag any voice-check issues.
+7. **Update STATE.md:** mark unit as drafted, note word count, flag any voice-check issues. Then refresh `.manuscript/PROGRESS.md` so the ledger advances (this unit moves to in progress or done) per `docs/progress-protocol.md`.
 
-8. **Tell the writer:** "Drafted {unit} {N}: X words across Y {atomic_units}. Voice consistency: Z%. Updated RECORD.md with what the draft established. Ready for editor review? Run `/scr:editor-review N` or `/scr:next`."
+8. **Tell the writer:** "Drafted {unit} {N} ({N} of {total}, {pct}% of the manuscript): X words across Y {atomic_units}. Voice consistency: Z% (the voice-checker Overall score for this unit; omit this figure if the voice-check could not run). Updated RECORD.md with what the draft established. Ready for editor review? Run `/scr:editor-review N` or `/scr:next`." The full per-unit ledger is in `.manuscript/PROGRESS.md`.
 
 ## Agent and Automation Status
 
@@ -67,6 +67,7 @@ Local operations:
 - draft files written: {count}
 - RECORD.md updated: yes/no
 - STATE.md updated: yes/no
+- PROGRESS.md refreshed: yes/no
 Auto-invoked:
 - /scr:editor-review N: yes/no
 Why: {autopilot.enabled true, full-auto profile, supervised pause, or writer-facing manual mode}
@@ -113,6 +114,6 @@ If the command stops because a prerequisite is missing, suggest the command that
 
 ## Tone
 
-Don't narrate each atomic unit being drafted. That's noise. Show progress concisely: "Drafted scene 1/4... 2/4... 3/4... 4/4. Voice check: passed."
+Don't narrate each atomic unit being drafted. That's noise. Show progress concisely, and anchor it to the whole manuscript so the writer sees momentum: "Drafted scene 1/4... 2/4... 3/4... 4/4. Voice check: passed. Chapter 5 of 12 done (42%)." Pull the unit-of-total figure and percent from the deliverable progress defined in `docs/progress-protocol.md`.
 
 Let the writer read the actual prose in the draft files. Your job is orchestration, not performance.

package/commands/scr/editor-review.md

@@ -168,6 +168,7 @@ Write the standard review report to `.manuscript/reviews/{N}-REVIEW.md`. If an o
 
 If all beats passed:
 - Mark act as "reviewed" in STATE.md
+- Refresh `.manuscript/PROGRESS.md` so the ledger reflects the new review status, per `docs/progress-protocol.md`
 - Apply confirmed compact updates to RECORD.md when the review established or corrected the work's durable content state
 - Suggest moving to `/scr:submit N` or `/scr:discuss {N+1}`
 

package/commands/scr/export.md

@@ -341,7 +341,7 @@ title: "[title from config.json]"
 subtitle: "[subtitle if available]"
 author:
   - name: "[author from config.json]"
-language: "[language from config.json, default en-US]"
+lang: "[language from config.json, default en-US]"
 rights: "Copyright [year] [author]. All rights reserved."
 date: "[current year]"
 description: "[description if available]"

package/commands/scr/help.md

@@ -34,7 +34,7 @@ You are helping the user navigate Scriveno commands. Load Scriveno's installed/s
 
 ## The "getting started" view (no project yet)
 
-Ask the user what they want to do. Don't list 170 commands -- show them this:
+Ask the user what they want to do. Don't list all 113 commands -- show them this:
 
 ```
 Scriveno -- ready to start.

package/commands/scr/line-edit.md

@@ -1,5 +1,6 @@
 ---
 description: Perform a line-level prose quality pass with inline annotations.
+argument-hint: "[N]"
 ---
 
 # /scr:line-edit -- Line-Level Prose Quality Pass

package/commands/scr/manuscript-stats.md

@@ -94,17 +94,17 @@ If the user passes `--detail`, append a per-unit breakdown table after the summa
 ```
 Unit Breakdown
 --------------
-Ch 1: The Beginning        3,200 words   ~13 pages
-Ch 2: The Middle           4,100 words   ~16 pages
-Ch 3: The Climax           2,800 words   ~11 pages
-  (not yet drafted)
-Ch 4: The Resolution         --- words    --- pages
+Ch 1: The Beginning    [x] done          3,200 words   ~13 pages
+Ch 2: The Middle       [x] done          4,100 words   ~16 pages
+Ch 3: The Climax       [~] in progress   2,800 words   ~11 pages
+Ch 4: The Resolution   [ ] untouched      --- words    --- pages
 --------------
-Total                     10,100 words   ~40 pages
+Total                                   10,100 words   ~40 pages
 ```
 
 - Use the hierarchy's mid-level label (e.g., "Ch" for chapter, "Sc" for scene, "Sec" for section) from CONSTRAINTS.json.
-- For units not yet drafted, show `(not yet drafted)` with dashes for counts.
+- Show each unit's status (`[x]` done, `[~]` in progress, `[ ]` untouched) derived from disk per `docs/progress-protocol.md`. The full per-unit ledger lives in `.manuscript/PROGRESS.md`.
+- For units not yet drafted, show dashes for counts.
 - Right-align word counts and page counts for visual clarity.
 - Include a total row at the bottom.
 

package/commands/scr/map-manuscript.md

@@ -1,5 +1,6 @@
 ---
 description: Spawn parallel analysis agents to understand an existing manuscript's voice, structure, characters, and themes.
+argument-hint: "[area]"
 ---
 
 # /scr:map-manuscript -- Analyze Existing Manuscript

package/commands/scr/multi-publish.md

@@ -199,7 +199,7 @@ Determine text direction from language code:
 
 Set the appropriate direction for Pandoc and Typst output:
 - Pandoc: `--variable dir=rtl` or `--variable dir=ltr`
-- Typst: Uses `text-dir` parameter (already prepared in Phase 5 template)
+- Typst: the book interior template reads the Pandoc `dir` variable set above to orient text
 
 #### 5d. Number Formatting
 
@@ -238,7 +238,7 @@ title: "[translated title]"
 subtitle: "[translated subtitle]"
 author:
   - name: "[author name]"
-language: "[lang code]"
+lang: "[lang code]"
 dir: "[ltr or rtl]"
 rights: "Copyright [year] [author]. [Translated rights statement]."
 date: "[current year]"
@@ -274,6 +274,7 @@ pandoc .manuscript/translation/{lang}/assembled-manuscript.md \
 pandoc .manuscript/translation/{lang}/assembled-manuscript.md \
   -o .manuscript/output/translations/{lang}/manuscript-{lang}.pdf \
   --pdf-engine=typst \
+  --template=data/export-templates/scriveno-book.typst \
   --metadata-file=.manuscript/translation/{lang}/metadata.yaml \
   --toc --toc-depth=1 \
   -V dir={ltr|rtl}

package/commands/scr/new-character.md

@@ -1,5 +1,6 @@
 ---
 description: Build a complete character profile through guided interactive interview.
+argument-hint: "<name>"
 ---
 
 # /scr:new-character -- Interactive Character Creation

package/commands/scr/new-work.md

@@ -69,7 +69,7 @@ Always create `RECORD.md` from `templates/RECORD.md` without renaming it. It is
 Write `.manuscript/config.json` by starting from `templates/config.json` and filling the project-specific values. The generated config must include the shared settings blocks that later commands read:
 ```json
 {
-  "scriveno_version": "2.5.0",
+  "scriveno_version": "2.7.1",
   "work_type": "<chosen>",
   "group": "<group>",
   "command_unit": "<unit>",

package/commands/scr/next.md

@@ -62,6 +62,7 @@ Proactive checks:
   Translation: <none | follow-up available>
   Export: <fresh | stale, suggest /scr:export>
   Save: <clean | unsaved manuscript changes, suggest /scr:save>
+  Progress: <X/Y units done -- see .manuscript/PROGRESS.md or /scr:progress>
 ```
 
 ## Routing logic

package/commands/scr/originality-check.md

@@ -1,5 +1,6 @@
 ---
 description: Scan drafted prose for AI-generated patterns and unintentional similarity to published works.
+argument-hint: "[N]"
 ---
 
 # /scr:originality-check -- AI Pattern & Similarity Scan

package/commands/scr/outline.md

@@ -22,7 +22,7 @@ You are an outline manager. 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 `work_types[type].hierarchy` for unit labels, and `file_adaptations`)
 - `.manuscript/OUTLINE.md` (the outline data -- read it fully)
-- `.manuscript/STATE.md` (to get drafted/planned/pending status per unit)
+- `.manuscript/STATE.md` (aggregate counters) plus each unit's files on disk (plans, drafts, reviews) to derive per-unit status -- see `docs/progress-protocol.md`. The persisted per-unit ledger is `.manuscript/PROGRESS.md` when present.
 
 **Work-type adaptation:** Read the hierarchy from CONSTRAINTS.json for the current work type to determine the correct unit terminology:
 - Novel: part > chapter > scene
@@ -56,7 +56,7 @@ Present the hierarchical outline with:
 2. **For each unit, show:**
    - Unit number and title
    - 1-line summary (from OUTLINE.md)
-   - Status: drafted | planned | pending (from STATE.md)
+   - Status: drafted | planned | pending (derived from disk per `docs/progress-protocol.md`, not from STATE.md aggregates)
    - Word count (if drafted, from STATE.md or draft file)
    - Arc position (if mapped in PLOT-GRAPH.md)
 

package/commands/scr/pacing-analysis.md

@@ -1,5 +1,6 @@
 ---
 description: Generate a structure-aware pacing report analyzing scene tempo and narrative flow.
+argument-hint: "[N]"
 ---
 
 # /scr:pacing-analysis -- Structure-Aware Pacing Report

package/commands/scr/pause-work.md

@@ -33,7 +33,7 @@ You are helping the writer pause their session gracefully. Your job is to captur
    - Outcome: `Paused session`
    Keep this pause marker in the Last actions table because `/scr:session-report` and future resume logic use it as a session boundary.
 
-6. **Regenerate `.manuscript/CONTEXT.md`** using the `templates/CONTEXT.md` scaffold and the field set described in `/scr:save` step 7, with `{{LAST_COMMAND}}` set to `/scr:pause-work`. This is the file the next session reads first; refreshing it on pause means the writer (or a fresh AI session) returns to a current view without having to call `/scr:resume-work` to bootstrap.
+6. **Regenerate `.manuscript/CONTEXT.md`** using the `templates/CONTEXT.md` scaffold and the field set described in `/scr:save` step 7, with `{{LAST_COMMAND}}` set to `/scr:pause-work`. This is the file the next session reads first; refreshing it on pause means the writer (or a fresh AI session) returns to a current view without having to call `/scr:resume-work` to bootstrap. Also regenerate `.manuscript/PROGRESS.md` (the per-unit progress ledger) per `/scr:save` step 8 and `docs/progress-protocol.md`, so the saved ledger matches where the writer is pausing.
 
 7. **Append one line to `.manuscript/HISTORY.log`** per `docs/history-protocol.md`:
    ```

package/commands/scr/polish.md

@@ -1,5 +1,6 @@
 ---
 description: Chain line-edit, copy-edit, and voice-check for comprehensive prose polish.
+argument-hint: "[N]"
 ---
 
 # /scr:polish -- Comprehensive Prose Polish

package/commands/scr/progress.md

@@ -1,5 +1,5 @@
 ---
-description: Show current project state and next step. How far along, what is drafted, what is pending.
+description: Show project progress -- a unit progress bar, what is done / in progress / untouched, pipeline position, and a pointer to the per-unit ledger.
 argument-hint: ""
 ---
 
@@ -18,7 +18,7 @@ node "$HOME/.scriveno/lib/auto-invoke-engine.js" --project "$PWD" --trigger /scr
 node .scriveno/lib/auto-invoke-engine.js --project "$PWD" --trigger /scr:progress
 ```
 
-This engine is installed into Scriveno shared assets for every runtime, including Claude Code, Codex, Cursor, Gemini CLI, OpenCode, GitHub Copilot, Windsurf, Antigravity, Manus, Perplexity Desktop, and the generic skill fallback. If the engine is not present, perform the read-only progress logic below.
+This engine is installed into Scriveno shared assets for every runtime, including Claude Code, Codex, Cursor, Gemini CLI, OpenCode, GitHub Copilot, Windsurf, Antigravity, Manus, Perplexity Desktop, and the generic skill fallback. The engine exposes `computeProgressLedger(manuscriptDir)` (see `lib/auto-invoke-engine.js` and `docs/progress-protocol.md`), which returns the deliverable bar, percent, and the done / in progress / untouched bucket counts deterministically from disk; a runtime that loads the module should prefer it over re-deriving counts by hand. If the engine is not present, perform the read-only progress logic below.
 
 ## Prerequisites
 
@@ -26,15 +26,19 @@ This engine is installed into Scriveno shared assets for every runtime, includin
 
 ## What to do
 
-1. Load `.manuscript/STATE.md`, `.manuscript/OUTLINE.md`, `.manuscript/RECORD.md` when present, and `.manuscript/config.json`
-2. Count total units, drafted units, submitted units, and pending units
-3. Calculate word count from existing draft files
-4. Determine the next step (what unit to discuss, plan, or draft next)
-5. Display a progress summary:
-   - "{drafted}/{total} units drafted. {submitted}/{total} submitted."
+1. Load `.manuscript/STATE.md`, `.manuscript/OUTLINE.md`, `.manuscript/config.json`, and `.manuscript/RECORD.md` when present. Read `.manuscript/PROGRESS.md` if it exists -- it is the saved ledger snapshot.
+2. Derive per-unit status from disk per `docs/progress-protocol.md`: for each outline unit, resolve its stage (untouched / discussed / planned / drafted / reviewed / submitted) and its headline bucket (done / in progress / untouched). Count units in each bucket plus the total, and calculate word count from existing draft files.
+3. Determine the pipeline position: the first incomplete stage on the writing lifecycle `seed > voice > outline > discuss > plan > draft > review > revise > publish > translate`, expressed as `Stage {index} of {total}: {Name}`.
+4. Determine the next step (what unit to discuss, plan, or draft next), using the work type's unit label from CONSTRAINTS.json (chapter, act, surah, section, and so on).
+5. Display the progress report, leading with the deliverable view:
+   - A progress bar over units, for example `████████░░ 4/5 scenes done (80%)` (block characters `U+2588` filled and `U+2591` empty; use the work type's plural unit label).
+   - "Done: {done}   In progress: {in_progress}   Untouched: {untouched}."
    - "{word_count} words so far."
+   - "Pipeline: Stage {index} of {total} ({stage_name})."
    - "{open_threads} open record threads." (only when RECORD.md exists)
    - "Next: {next_action}"
+   - "Full per-unit ledger: `.manuscript/PROGRESS.md`" -- the file the writer can open any time to see every unit's status. If it is missing or older than the newest draft, add: "(run `/scr:save` to refresh the saved ledger)".
+   When the project is small (20 units or fewer) or the writer asks, render the per-unit ledger table inline per `docs/progress-protocol.md` instead of only pointing at the file.
 6. Run the Level 1 proactive sweep:
    - If STATE.md counts disagree with draft files, suggest `/scr:scan`.
    - If reports show unresolved review items, suggest the matching review command.
@@ -55,14 +59,15 @@ Candidate agents:
 - <recommended agent route or none>
 Local operations:
 - progress counts computed: yes/no
+- per-unit ledger rendered: yes/no
 - proactive sweep: read-only
 Candidate local helpers:
-- <recommended helper or none>
+- /scr:save to refresh the saved .manuscript/PROGRESS.md when it is stale
 Manual gates:
 - <writer-owned route or none>
 Auto-invoked:
 - none
-Why: progress is read-only; it recommends next commands without mutating files
+Why: progress is read-only; it renders the ledger live and points at .manuscript/PROGRESS.md without writing it
 ```
 
 ## Response Contract

package/commands/scr/quick-write.md

@@ -1,5 +1,6 @@
 ---
 description: Write a scene, passage, or chapter outside the full planning workflow.
+argument-hint: "[--discuss] [--research] [--full]"
 ---
 
 # /scr:quick-write -- Ad-Hoc Writing Without Full Planning
@@ -18,7 +19,7 @@ Write a scene, passage, or chapter outside the full planning workflow.
 
 ## Instruction
 
-Quick write gives you Scriveno guarantees (continuity tracking, voice consistency, atomic commits) with a faster path.
+Quick write is the fast path. It loads STYLE-GUIDE.md, drafts in the current conversation context (not a fresh per-unit context), and commits atomically. It runs continuity and voice checks only when you pass `--full`. For voice-critical work, prefer `/scr:draft`, which drafts each unit in a fresh context and always runs a voice-check.
 
 ### STEP 1: GATHER INTENT
 
@@ -49,6 +50,8 @@ If the host runtime cannot spawn a focused researcher, run the research pass in
 
 Write the passage following all established style guide constraints. Target whatever length feels natural unless the writer specified a target.
 
+Quick-write drafts in the current conversation context rather than spawning the drafter in a fresh per-unit context; this trades some voice isolation for speed. When fresh-context voice fidelity matters, use `/scr:draft` instead.
+
 ### STEP 4: VERIFY (if --full)
 
 Run continuity and voice checks against existing manuscript.

package/commands/scr/resume-work.md

@@ -46,7 +46,7 @@ You are welcoming the writer back and orienting them. Your job is to read the se
    Example:
    > Last time you drafted chapter 3 (1,247 words across 4 scenes, voice check passed). You were working on chapter 4 -- you noted you wanted it shorter and more tense, with Marcus discovering the letter. I'd suggest starting with /scr:discuss 4 to shape the plan.
 
-6. **Regenerate `.manuscript/CONTEXT.md`** using the `templates/CONTEXT.md` scaffold and the same field set described in `/scr:save` step 7, with `{{LAST_COMMAND}}` set to `/scr:resume-work`. This refreshes the bootstrap file so the next session opens to a current view -- the act of resuming is itself a state event worth recording.
+6. **Regenerate `.manuscript/CONTEXT.md`** using the `templates/CONTEXT.md` scaffold and the same field set described in `/scr:save` step 7, with `{{LAST_COMMAND}}` set to `/scr:resume-work`. This refreshes the bootstrap file so the next session opens to a current view -- the act of resuming is itself a state event worth recording. Also regenerate `.manuscript/PROGRESS.md` (the per-unit progress ledger) per `/scr:save` step 8 and `docs/progress-protocol.md`.
 
 7. **Append one line to `.manuscript/HISTORY.log`** per `docs/history-protocol.md`:
    ```

package/commands/scr/save.md

@@ -56,20 +56,22 @@ Follow the auto-invoke policy. In the source repository it is documented at `doc
    - `{{LAST_SCAN}}`, `{{LAST_SCAN_VERDICT}}` -- from STATE.md if recorded; otherwise `never run` and `unknown`
    Save to `.manuscript/CONTEXT.md`. This file is committed alongside STATE.md.
 
-8. **Append one line to `.manuscript/HISTORY.log`** per `docs/history-protocol.md`:
+8. **Regenerate `.manuscript/PROGRESS.md`** before staging. This is the openable per-unit progress ledger. Use the `templates/PROGRESS.md` scaffold and derive per-unit status from disk per `docs/progress-protocol.md` (plan, draft, and review files reconciled with STATE.md). Fill the unit ledger, the deliverable progress bar, the pipeline position, and the bucket counts (done / in progress / untouched). Save to `.manuscript/PROGRESS.md`; it is committed alongside STATE.md and CONTEXT.md.
+
+9. **Append one line to `.manuscript/HISTORY.log`** per `docs/history-protocol.md`:
    ```
    {ISO timestamp} | scr:save | message="{generated message}" | files={changed file count} | outcome=committed
    ```
    If HISTORY.log does not exist, create it. Do not stage it as a separate operation -- step 9 picks it up.
 
-9. **Execute the save:**
+10. **Execute the save:**
    ```
    git add .manuscript/
    git commit -m "{generated message}"
    ```
-   This commit must include the `STATE.md`, `CONTEXT.md`, and `HISTORY.log` updates from steps 6 through 8 so the worktree is clean immediately after a successful save.
+   This commit must include the `STATE.md`, `CONTEXT.md`, `PROGRESS.md`, and `HISTORY.log` updates from steps 6 through 9 so the worktree is clean immediately after a successful save.
 
-10. **Tell the writer** the result (see output section below).
+11. **Tell the writer** the result (see output section below).
 
 ## Automation Status
 
@@ -85,6 +87,7 @@ Candidate agents:
 Local operations:
 - STATE.md updated: yes/no
 - CONTEXT.md regenerated: yes/no
+- PROGRESS.md regenerated: yes/no
 - HISTORY.log appended: yes/no
 - manuscript files saved: yes/no
 Candidate local helpers: