scriveno 2.0.5

package/docs/sacred-texts.md

@@ -0,0 +1,296 @@
+# Sacred Text Guide
+
+Scriveno adapts its entire workflow for sacred, historical, and mythological writing. When you choose a sacred work type, every command, every structural label, and every voice setting shifts to use tradition-native vocabulary. Novels use "chapters" -- but Quranic commentary uses "surahs," Torah scholarship uses "parashot," and Vedic texts use "suktas." This is not cosmetic. The vocabulary shapes how the AI agent thinks about your text, producing drafts that respect the traditions they come from.
+
+This guide covers everything specific to sacred writing in Scriveno: the 15 sacred work types, 10 voice registers, sacred-exclusive commands, command adaptations, sacred translation, and tradition-aware front and back matter.
+
+## Sacred Work Types
+
+Scriveno supports 15 work types in the sacred group, spanning six traditions and several cross-tradition categories. Each work type defines its own structural hierarchy -- the levels at which your text is organized -- and its own command unit, the level at which you discuss, plan, draft, and review.
+
+### Scripture Types
+
+| Work Type | Label | Hierarchy (Top / Mid / Atomic) | Command Unit | Tradition |
+|-----------|-------|-------------------------------|--------------|-----------|
+| `scripture_biblical` | Scripture (Biblical) | testament / book / verse | book | Christian Bible, Apocrypha |
+| `scripture_quranic` | Scripture (Quranic) | -- / surah / ayah | surah | Quran, Hadith collections |
+| `scripture_torah` | Scripture (Torah) | chumash / parashah / pasuk | parashah | Torah, Talmud, Mishnah |
+| `scripture_vedic` | Scripture (Vedic) | veda / mandala / sukta | mandala | Rigveda, Upanishads, Bhagavad Gita |
+| `scripture_buddhist` | Scripture (Buddhist) | pitaka / nikaya / sutta | sutta | Pali Canon, Mahayana sutras |
+| `scripture_generic` | Scripture (Generic) | testament / book / verse | book | Any tradition not listed above |
+
+**Config defaults:** Some scripture types include tradition-specific configuration defaults. Biblical and Torah types use Masoretic verse numbering. Quranic types use Hafs verse numbering and the Hijri calendar. Torah types use the Hebrew calendar. Vedic types use Vikram Samvat. Buddhist types use the Buddhist Era calendar.
+
+## Tradition Profiles and Config
+
+Sacred projects use a top-level `tradition` key in `.manuscript/config.json`. That key points to one of the shipped profile directories under `templates/sacred/`:
+
+- `catholic`
+- `orthodox`
+- `tewahedo`
+- `protestant`
+- `jewish`
+- `islamic-hafs`
+- `islamic-warsh`
+- `pali`
+- `tibetan`
+- `sanskrit`
+
+New projects also store sacred profile settings as top-level config keys, including `verse_numbering_system`, `calendar_system`, `translation_philosophy`, `canonical_alignment`, `annotation_traditions`, `doctrinal_framework`, `preserve_source_terms`, and `transliteration_style`. Older projects that still have a nested `sacred` object are accepted as legacy input by commands that read those values, but new projects use the top-level shape.
+
+Tradition-aware commands load `templates/sacred/{tradition}/manifest.yaml` for book order, script direction, numbering formats, font stack, and approval-block guidance. Build commands use that manifest to set language/script metadata and warn when the selected tradition expects an approval block before publication.
+
+### Sacred Prose Types
+
+| Work Type | Label | Hierarchy (Top / Mid / Atomic) | Command Unit | Use For |
+|-----------|-------|-------------------------------|--------------|---------|
+| `commentary` | Commentary / Exegesis | -- / section / annotation_block | section | Tafsir, Midrash, biblical commentary, philosophical exegesis |
+| `devotional` | Devotional | -- / theme / entry | entry | Daily devotionals, prayer journals, spiritual meditations |
+| `liturgical` | Liturgical Text | rite / section / rubric | section | Liturgies, prayer books, ritual texts, service orders |
+| `sermon` | Sermon / Homily | -- / movement / beat | sermon | Individual sermons, homilies, khutbahs |
+| `homiletic_collection` | Homiletic Collection | liturgical_year / -- / sermon | sermon | Sermon cycles, collected homilies organized by liturgical calendar |
+| `religious_epic` | Religious Epic | book / canto / verse | canto | Paradise Lost, Mahabharata, Divine Comedy, Shahnameh |
+
+### Historical and Mythological Types
+
+| Work Type | Label | Hierarchy (Top / Mid / Atomic) | Command Unit | Use For |
+|-----------|-------|-------------------------------|--------------|---------|
+| `historical_chronicle` | Historical Chronicle | era / chapter / event | chapter | Annals, dynastic histories, chronicles |
+| `historical_account` | Historical Account | part / chapter / scene | chapter | Narrative histories, biographical accounts |
+| `mythological_collection` | Mythological Collection | cycle / -- / tale | tale | Norse Eddas, Greek myth compilations, folklore anthologies |
+
+## Tradition-Native Vocabulary
+
+When you create a project with `/scr:new-work` and select a sacred work type, Scriveno renames structural units throughout the entire system. This means every command you run uses the vocabulary of your tradition, not generic publishing terms.
+
+Here is how vocabulary flows for each scripture type:
+
+- **Biblical:** You discuss, plan, and draft **books** (command unit). Your text is organized into **testaments** at the top level and **verses** at the atomic level.
+- **Quranic:** You discuss, plan, and draft **surahs**. The atomic unit is the **ayah**. There is no top-level grouping -- surahs stand alone.
+- **Torah:** You discuss, plan, and draft **parashot** (singular: parashah). The top level is the **chumash** (the five books). The atomic unit is the **pasuk**.
+- **Vedic:** You discuss, plan, and draft **mandalas**. The top level is the **veda**. The atomic unit is the **sukta** (hymn).
+- **Buddhist:** You discuss, plan, and draft **suttas** (or sutras). The top level is the **pitaka** (basket). The mid level is the **nikaya** (collection).
+- **Generic:** Uses the default testament / book / verse hierarchy for traditions not specifically configured.
+
+This vocabulary carries through every command automatically. When you run `/scr:draft`, you are drafting a surah, a parashah, or a sutta -- not a "chapter." When you run `/scr:plan`, you are planning a mandala or a canto. The AI agent receives these tradition-native labels and adjusts its approach accordingly.
+
+Non-scripture sacred types use vocabulary appropriate to their form: a `liturgical` text is organized into **rites** containing **sections** and **rubrics**. A `religious_epic` uses **books**, **cantos**, and **verses**. A `mythological_collection` uses **cycles** and **tales**.
+
+## Voice Registers
+
+Sacred texts use voice registers instead of a single narrative voice. A register is a mode of sacred speech -- the difference between a prophet's urgent declarations and a sage's measured observations. Scriveno defines 10 registers, each with distinct characteristics. You set the register per unit in the plan file, and the drafter agent writes in that register.
+
+Your STYLE-GUIDE.md has a "Sacred voice registers" section where you customize how YOUR writing handles each register. The register descriptions below are defaults -- your STYLE-GUIDE.md always takes precedence, because the goal is your voice in that register, not a generic version.
+
+### Prophetic-Oracular
+
+Urgent, declarative, oracular. Short sentences, imperative mood, "Thus says the Lord" framing. Direct address to the audience. Present and future tense dominance. Repetition for emphasis ("Woe, woe, woe"). Exclamatory. No hedging. The prophet speaks with certainty because they speak on behalf of the divine.
+
+**When to use:** Prophetic books, oracles, divine pronouncements, apocalyptic warnings. Any passage where a figure speaks with absolute authority on behalf of a higher power.
+
+### Wisdom-Didactic
+
+Aphoristic, reflective, balanced. Parallelism -- antithetical, synonymous, synthetic. Comparative structure ("Better X than Y"). Observational tone. Third person often. Conditional constructions ("If you...then"). Measured cadence. The sage observes the world and distills truths.
+
+**When to use:** Proverbs, wisdom literature, philosophical passages, didactic sections. When the text teaches through observation and comparison rather than narrative.
+
+### Legal-Prescriptive
+
+Precise, conditional, imperative. Case-law structure ("If a man does X, then Y"). Categorical. Exhaustive enumeration. No ambiguity tolerated. Present tense. Second person direct address for commandments ("You shall / You shall not"). Every word carries binding weight.
+
+**When to use:** Legal codes, commandments, halakhic rulings, fiqh, monastic rules, canonical law. Any passage that prescribes behavior with binding authority.
+
+### Liturgical-Devotional
+
+Formal, rhythmic, responsive. Call-and-response patterns. Doxological language (praise, blessing, thanksgiving). Repetitive refrains. Elevated vocabulary. Present tense. Address to the divine or congregation. Musical awareness -- these words are meant to be spoken aloud or sung.
+
+**When to use:** Prayers, blessings, liturgical services, doxologies, invocations. Any text designed for corporate worship or personal devotion where rhythm and elevation matter.
+
+### Narrative-Historical
+
+Chronicle-like, temporal, factual. Sequential narration ("And it came to pass"). Genealogical asides. Geographic precision. Past tense. Third person. Minimal editorializing. Wayyiqtol-style consecutive narration rhythm. The narrator records what happened, not what should have happened.
+
+**When to use:** Historical books, chronicles, hagiographies, narrative sections of scripture. The default register when none is specified -- most sacred texts contain significant narrative.
+
+### Apocalyptic-Visionary
+
+Visionary, symbolic, cosmic. "I saw..." framing. Numbers as symbols (7, 12, 40). Animal imagery. Throne-room scenes. Cosmic battle. Dream logic. Urgency. Future tense and prophetic perfect. Interpreting angel as guide. Reality bends -- the visionary describes what lies beyond ordinary perception.
+
+**When to use:** Apocalyptic literature (Revelation, Daniel), visionary accounts, mystical visions, eschatological passages. Any text where the writer describes transcendent reality through symbolic imagery.
+
+### Epistolary
+
+Personal, didactic, pastoral. Greeting formula. "Dear brothers/sisters" address. Practical instruction. Theological argument. Exhortation. Closing benediction. Mix of personal warmth and doctrinal authority. The writer knows their audience and writes to their specific situation.
+
+**When to use:** Letters, epistles, encyclicals, pastoral communications. Any sacred text structured as correspondence from an authority figure to a community.
+
+### Poetic-Hymnic
+
+Musical, metaphorical, parallelism-heavy. Hebrew parallelism patterns (synonymous, antithetical, synthetic, climactic). Nature imagery. Emotional range (lament, praise, thanksgiving, royal, penitential). Selah markers. Acrostic potential. Chiastic structures. Address to God and self ("O my soul"). Raw emotion given artistic form.
+
+**When to use:** Psalms, hymns, canticles, religious poetry, song lyrics for worship. Any passage where emotion is expressed through poetic form and musical structure.
+
+### Parabolic
+
+Story-within-story, allegorical. "The kingdom of heaven is like..." framing. Concrete imagery from daily life (seeds, sheep, merchants, vineyards). Surprising twist that overturns expectations. Open-ended or with explicit moral. Accessible surface, deep meaning. The parable teaches through indirection -- the listener must do the interpretive work.
+
+**When to use:** Parables, allegories, teaching stories, Zen koans, Sufi tales. Any embedded narrative designed to teach a spiritual truth through analogy.
+
+### Contemplative-Mystical
+
+The didactic register adapted for systematic teaching. Instructional, systematic, expository. Topic-by-topic structure. Definition and explanation. Q&A format possible. Teacher-student dynamic. Building from simple to complex. Summary and application. Catechetical structure. The teacher organizes knowledge for transmission.
+
+**When to use:** Catechisms, systematic theologies, doctrinal instruction, dharma talks. Any passage that teaches through organized, progressive exposition rather than story or poetry.
+
+## Sacred-Exclusive Commands
+
+These 8 commands are only available when your work type belongs to the sacred group. They appear in the command list automatically when you create a sacred project and are hidden for all other work types.
+
+### `/scr:sacred:concordance`
+
+Build or search a concordance of key terms, names, and phrases across your sacred text. Tracks every occurrence of significant terms to enable cross-referencing and intertextual study. Run with `--build` to generate a full concordance from your drafted text, or `--search <term>` to find all occurrences of a specific term.
+
+**Requires:** At least one drafted unit.
+
+### `/scr:sacred:cross-reference`
+
+Map connections between passages within your text or between your text and other sacred sources. Identifies parallel passages, quotations, allusions, and thematic echoes. Essential for commentary and exegetical work where intertextuality is central.
+
+**Requires:** At least one drafted unit.
+
+### `/scr:sacred:genealogy`
+
+Build and visualize genealogical trees and lineage relationships from your FIGURES.md file. For biblical genealogies, Quranic lineages, mythological family trees, or any sacred text where figures are connected by descent, marriage, or spiritual succession.
+
+**Requires:** FIGURES.md with at least 2 figures.
+
+### `/scr:sacred:chronology`
+
+Construct a timeline of events across your sacred text. Handles multiple calendar systems (Gregorian, Hijri, Hebrew, Vikram Samvat, Buddhist Era) and can cross-reference events with external historical timelines. Unlike the standard `/scr:timeline` command, this is designed for texts spanning centuries or millennia.
+
+**No prerequisites** -- can be started at any point.
+
+### `/scr:sacred:annotation-layer`
+
+Add scholarly annotations, footnotes, and commentary layers to your drafted text. Supports multiple annotation layers (textual, historical, theological, linguistic) that can be toggled independently in the exported output.
+
+**Requires:** At least one drafted unit.
+
+### `/scr:sacred:verse-numbering`
+
+Apply or adjust verse numbering systems to your drafted text. Supports tradition-specific systems (Masoretic for Hebrew Bible, Hafs for Quran, etc.) and can convert between systems. Ensures your verse references match the numbering expected by your tradition.
+
+**Requires:** At least one drafted unit.
+
+The top-level `/scr:sacred-verse-numbering` compatibility command is read-only: it shows the active tradition's numbering format and can render example citations. The nested `/scr:sacred:verse-numbering` command changes or verifies the project's numbering system.
+
+### `/scr:sacred:source-tracking`
+
+Track and document the source traditions, manuscripts, and textual variants underlying your sacred text. For critical editions, translation projects, and any work that draws from multiple source texts.
+
+**No prerequisites** -- can be started at any point.
+
+### `/scr:sacred:doctrinal-check`
+
+Verify that your drafted text is consistent with the doctrines recorded in your DOCTRINES.md file. Flags any assertions, implications, or narrative choices that might contradict your established doctrinal framework.
+
+**Requires:** At least one drafted unit and DOCTRINES.md.
+
+## Command Adaptations
+
+When you are working on a sacred work type, selected review commands pick up tradition-appropriate labels in help and output. You still invoke the canonical file-backed command unless your runtime explicitly installs an alias.
+
+| Standard Command | Sacred Label | Why |
+|-----------------|---------------|-----|
+| `/scr:sensitivity-review` | `interfaith-review` | Review for **interfaith** sensitivity, not general sensitivity |
+| `/scr:editor-review` | `scholarly-review` | Sacred texts undergo **scholarly** review |
+| `/scr:voice-check` | `register-check` | Checking **register** consistency, not character voice |
+| `/scr:beta-reader` | `theological-review` | Review by a **theological** perspective, not a casual reader |
+
+Sacred-specific workflows like chronology, doctrinal review, and verse numbering are exposed through the dedicated `/scr:sacred:*` command family instead of by relabeling hidden base commands.
+
+## Sacred Translation
+
+Sacred translation is the most demanding form of translation work. Terms carry centuries of theological weight, registers must survive the crossing between languages, and readers have strong expectations about how canonical texts sound.
+
+Scriveno's translation pipeline (accessed via `/scr:translate`) enters **sacred mode** when the work type is in the sacred group. Sacred mode adds several capabilities beyond standard translation:
+
+### Translation Philosophy
+
+You choose your translation approach per project:
+
+- **Formal equivalence** -- Word-for-word as much as possible. Preserves source language syntax. Footnotes idiomatic expressions. Best for academic audiences who want precision.
+- **Dynamic equivalence** -- Thought-for-thought. Natural target language expression. Preserves meaning, not form. Best for general audiences who want clarity.
+- **Paraphrase** -- Free rendering for modern accessibility. Simplifies complex theology. Conversational tone. Best for new readers.
+- **Interlinear** -- Source word, transliteration, gloss, and target word for each element. A scholarly tool, not readable prose.
+
+### Canonical Alignment
+
+When set (e.g., KJV, NRSV, Sahih International), the translator matches the vocabulary and phrasing of the specified canonical translation. Readers familiar with "lovingkindness" (KJV) or "steadfast love" (NRSV) will encounter the language they expect.
+
+### Preserved Source Terms
+
+Certain terms are never translated. They appear in the source language (with transliteration if non-Latin script) and are footnoted on first occurrence. Examples: YHWH, hesed, shalom, dharma, sutra, logos, ruach, taqwa.
+
+### Liturgical Preservation
+
+When enabled, the translator preserves the rhythmic and musical qualities of liturgical passages -- maintaining parallelism, meter, cadence, antiphonal structures, and chiastic patterns even at the cost of literal accuracy. These texts are meant to be read aloud or chanted.
+
+### Register-Aware Translation
+
+Each of the 10 voice registers has established conventions in major translation traditions. The translator preserves the specific register (prophetic, wisdom, legal, liturgical, etc.) in the target language, so a prophetic oracle sounds prophetic in French or Arabic, not merely translated.
+
+For full translation pipeline details including glossary management, translation memory, and multi-language export, see the Translation Guide when available, or use `/scr:translate --help`.
+
+## Tradition-Aware Front and Back Matter
+
+Sacred texts need front and back matter that respects their tradition. The standard `/scr:front-matter` and `/scr:back-matter` commands enter **sacred behavior mode** when the work type is in the sacred group.
+
+### Front Matter
+
+Sacred front matter can include:
+
+- **Invocations** -- Bismillah for Quranic texts, "In the Name of the Father" for Christian liturgical texts, Om for Vedic texts
+- **Dedication** -- Traditional dedications appropriate to the tradition
+- **Preface** -- Context for the work, including textual tradition, source manuscripts, and translation philosophy
+- **Introduction** -- Historical and theological context
+- **Guide to use** -- How to read and study the text, including any special notation or apparatus
+- **List of abbreviations** -- Sources, manuscripts, and reference works cited
+- **Maps and timelines** -- Geographic and chronological context
+
+### Back Matter
+
+Sacred back matter can include:
+
+- **Glossary** -- Key terms with definitions in the tradition's vocabulary
+- **Concordance** -- Cross-referenced index of terms (generated by `/scr:sacred:concordance`)
+- **Bibliography** -- Source texts, commentaries, and reference works
+- **Scriptural index** -- References to other sacred texts cited or alluded to
+- **Subject index** -- Topical index
+- **Colophon** -- Scribal tradition, publication notes
+- **Benediction** -- Closing blessing or prayer appropriate to the tradition
+- **Appendices** -- Textual variants, manuscript notes, supplementary material
+
+## Getting Started with Sacred Writing
+
+Here is a quick walkthrough for starting a sacred writing project:
+
+1. **Create your project.** Run `/scr:new-work` and select a sacred work type. For example, choose `commentary` for a Quranic tafsir, `scripture_biblical` for a new translation, or `mythological_collection` for a retelling of Norse myths.
+
+   The generated config stores `tradition` and the sacred profile fields at the top level. If you already know the tradition profile you want, choose one of the shipped slugs listed above.
+
+2. **Set up your voice.** Run `/scr:profile-writer` to generate your STYLE-GUIDE.md. Pay special attention to the "Sacred voice registers" section at the bottom -- this is where you customize how YOUR writing voice handles each register. A prophetic passage in your voice should sound different from a prophetic passage in someone else's.
+
+3. **Explore and plan.** Use `/scr:discuss` (it adapts automatically to your sacred work type) to shape your first unit. Discuss the theological themes, source traditions, and structural approach you want to take.
+
+4. **Draft.** Run `/scr:draft`. In sacred projects, Scriveno frames the work in the right unit terminology (surah, parashah, sutta, and so on) while the drafter writes in the register specified in your plan file, using your voice as defined in STYLE-GUIDE.md.
+
+5. **Review.** Use `/scr:editor-review` for expert review, `/scr:sacred:doctrinal-check` to verify consistency with your DOCTRINES.md, and `/scr:voice-check` for sacred register fidelity.
+
+6. **Build your apparatus.** As you draft, use `/scr:sacred:concordance` to build cross-references, `/scr:sacred:chronology` for timelines, `/scr:sacred:genealogy` for lineage trees, and `/scr:sacred:annotation-layer` for scholarly footnotes.
+
+## See Also
+
+- [Getting Started](getting-started.md) -- Install Scriveno and create your first project
+- [Command Reference](command-reference.md) -- Full reference for all 112 commands, including the [Sacred Exclusive](command-reference.md#sacred-exclusive) section
+- [README](../README.md) -- Project overview and feature list

package/docs/shipped-assets.md

@@ -0,0 +1,129 @@
+# Shipped Assets
+
+Scriveno's launch surface should point to what is actually bundled in this repo today. This document is the canonical inventory for shipped export templates, drafter-quality assets, and other trust-critical launch files.
+
+## Drafter Quality Assets Shipped Today
+
+These files ship in `templates/` and provide layered rule scaffolding loaded by the drafter, voice-checker, and originality-check after `STYLE-GUIDE.md`. See [docs/drafter-quality.md](drafter-quality.md) for the full system.
+
+- `templates/WRITING-RULES.md` (universal human-first and AI-tell rulebook; loaded after `STYLE-GUIDE.md`)
+
+Per-work-type pitfall packs in `templates/pitfalls/`:
+
+- `pitfalls/novel.md` (prose: filter words, POV breaches, dialogue traps, genre stock phrases)
+- `pitfalls/memoir.md` (prose: retrospective voice traps, sentimentality, self-presentation)
+- `pitfalls/screenplay.md` (script: unfilmable description, action-line bloat, on-the-nose dialogue)
+- `pitfalls/runbook.md` (technical: imperatives, missing preconditions, verification and rollback)
+- `pitfalls/research_paper.md` (academic: hedge stacks, citation hygiene, methodology traps)
+- `pitfalls/poetry_collection.md` (poetry: image cliches, diction traps, sentimentality, form pitfalls)
+- `pitfalls/comic.md` (visual: script-versus-art boundary, panel rhythm, caption voice)
+- `pitfalls/commentary.md` (sacred: register drift, anachronism, source-handling, doctrinal precision)
+
+Conflict resolution is top-down: `STYLE-GUIDE.md` beats `WRITING-RULES.md` beats the pitfall pack. The writer's voice is sovereign; the rule layers are scaffolding for human-first restraint, variance over substitution, factual integrity, sourced stance, register awareness, artifact cleanup, and type-specific polish.
+
+`WRITING-RULES.md` also ships the "Diagnostic discipline (honest read)" section that governs the evaluative side of the rules. The diagnostic surface is `/scr:voice-check`, `/scr:originality-check`, and the `voice-checker` agent: they report an authenticity band then a 0-100 score then flagged spans, match scrutiny to evidence density, credit strong false positives as score-raising human markers, and never rewrite. Diagnosis and rewriting (`/scr:line-edit`, `/scr:polish`, re-draft) stay separate steps with the writer between them, which is what stops a score-then-rewrite gaming loop.
+
+A contributor adding `templates/pitfalls/<work_type>.md` is automatically picked up by `lib/architectural-profiles.js#listPitfallPacks` with no edits to library code or `CONSTRAINTS.json`.
+
+## Context Integrity Assets Shipped Since 2.0.0
+
+These files ship in `templates/` and `docs/` and provide the trust trio for session-aware AI work:
+
+- `templates/CONTEXT.md` -- one-page session bootstrap scaffold copied into every project. Auto-regenerated on `/scr:save`, `/scr:pause-work`, `/scr:resume-work`. Read first by `/scr:next` and `/scr:resume-work` for orientation, with stale-detection + STATE.md fallback.
+- `templates/RECORD.md` -- compact established-content store copied into every project. It tracks what the work has established, including open threads, promises, payoffs, continuity facts, movement, and next-unit obligations. It is deliberately neutral so sacred, academic, technical, poetry, script, visual, and prose projects can all use the same filename.
+- `docs/context-protocol.md` -- canonical contract for the CONTEXT.md preference rule. The 12 high-impact commands that opt into the protocol reference this doc.
+- `docs/history-protocol.md` -- canonical line-format spec for `.manuscript/HISTORY.log`, the append-only audit trail. Pipe-delimited, UTC ISO timestamps, committed to git.
+
+`STATE.md` (workflow data) + `RECORD.md` (established content) + `CONTEXT.md` (narrative bootstrap) + `HISTORY.log` (audit trail) together form the integrity layer. `/scr:scan` is the trust check that interrogates whether the recorded state still matches disk.
+
+## Runtime Sync Asset Shipped Today
+
+- `commands/scr/sync.md` -- local runtime-surface synchronization command. It compares and refreshes installed Scriveno commands, Codex skills, command mirrors, and agent prompts from the current source tree by delegating to `bin/install.js`.
+
+## Export Templates Shipped Today
+
+These export templates are currently bundled in `data/export-templates/`:
+
+- `scriveno-book.typst` -- default book interior and print-ready PDF template
+- `scriveno-stageplay.typst` -- stage play interior template
+- `scriveno-picturebook.typst` -- picture-book interior template
+- `scriveno-chapbook.typst` -- chapbook and poetry-collection interior template
+- `scriveno-epub.css` -- standard EPUB styling and KDP-compatible ebook CSS
+- `scriveno-fixed-layout-epub.css` -- fixed-layout EPUB stylesheet
+- `scriveno-fixed-layout.opf` -- fixed-layout EPUB OPF stub
+- `scriveno-academic.latex` -- generic academic/thesis LaTeX template
+- `scriveno-ieee.latex` -- IEEE wrapper template
+- `scriveno-acm.latex` -- ACM wrapper template
+- `scriveno-lncs.latex` -- LNCS wrapper template
+- `scriveno-elsevier.latex` -- Elsevier wrapper template
+- `scriveno-apa7.latex` -- APA7 wrapper template
+- `scriveno-smashwords.docx` -- Smashwords reference DOCX
+- `scriveno-smashwords-styles.md` -- Smashwords style guide companion
+- `scriveno-poetry-submission.docx` -- poetry-submission reference DOCX
+- `scriveno-poetry-submission-styles.md` -- poetry-submission style guide companion
+
+## Export Template Behaviors
+
+- Manuscript DOCX export currently relies on Pandoc's default DOCX styling unless the user supplies a custom Pandoc reference document.
+- Formatted DOCX export currently relies on Pandoc's default DOCX output unless the user supplies a custom Pandoc reference document for styled review copies.
+- `scriveno-manuscript.docx` is not shipped today.
+- `scriveno-formatted.docx` is not shipped today.
+- `scriveno-kdp-cover.typst` is not shipped today.
+- `scriveno-ingram-cover.typst` is not shipped today.
+- Cover deliverables are manuscript build assets, not bundled export templates:
+  - Ebook front cover: `.manuscript/build/ebook-cover.jpg` (or `.png`)
+  - Paperback full wrap: `.manuscript/build/paperback-cover.pdf`
+  - Hardcover case wrap: `.manuscript/build/hardcover-cover.pdf`
+- Those cover files are designer-provided or externally produced assets that Scriveno's build/export commands reference; exact paperback and hardcover wrap geometry still comes from the active platform cover template generator.
+
+## Platform Profiles Shipped Today
+
+These platform manifests are currently bundled in `templates/platforms/` and loaded by build commands:
+
+- `kdp`
+- `ingram`
+- `apple`
+- `bn`
+- `d2d`
+- `kobo`
+- `google`
+- `smashwords`
+
+`/scr:build-ebook` validates the selected platform, loads `templates/platforms/{platform}/manifest.yaml`, checks `formats_accepted` for EPUB support, and carries the manifest's `label` and `epub_variant` into output metadata. `/scr:build-print` uses print and academic platform metadata for trim-size, page-count, and template routing.
+
+## Sacred Tradition Profiles Shipped Today
+
+These tradition manifests are currently bundled in `templates/sacred/` and accepted as top-level `tradition` values in `.manuscript/config.json`:
+
+- `catholic`
+- `orthodox`
+- `tewahedo`
+- `protestant`
+- `jewish`
+- `islamic-hafs`
+- `islamic-warsh`
+- `pali`
+- `tibetan`
+- `sanskrit`
+
+Sacred commands read top-level sacred profile keys in new projects and preserve legacy fallback reads for older projects that still have a nested `sacred` object.
+
+## Trust-Critical Launch Files
+
+- `README.md` -- primary launch narrative and status claims
+- `CHANGELOG.md` -- package-level release history
+- `docs/release-notes.md` -- public-facing release summary
+- `docs/proof-artifacts.md` -- canonical proof hub for sample-flow and voice-preservation evidence
+- `docs/runtime-support.md` -- canonical runtime matrix, Node baseline, and support-confidence framing
+- `docs/command-reference.md` -- canonical command surface reference
+- `docs/configuration.md` -- canonical project config and package metadata reference
+- `data/proof/watchmaker-flow/README.md` -- canonical sample-flow proof bundle rooted in shipped demo files
+- `data/proof/voice-dna/README.md` -- canonical Voice DNA proof bundle
+- `commands/scr/export.md` -- source of truth for export command behavior
+- `docs/publishing.md` -- user-facing explanation of export formats and publishing packages
+- `docs/contributing.md` -- contributor-facing guidance for extending export support
+- `docs/drafter-quality.md`: canonical reference for the drafter's three rule layers and the `draft` config block
+- `templates/WRITING-RULES.md`: canonical universal AI-tell rulebook loaded by drafter, voice-checker, and originality-check
+- `templates/pitfalls/<work_type>.md`: per-work-type pitfall packs that refine `WRITING-RULES.md` for a given work type
+- `AGENTS.md` -- project instructions that shape planning and implementation claims
+- `CLAUDE.md` -- mirrored project instructions and product-plan context

package/docs/testing.md

@@ -0,0 +1,156 @@
+# Testing
+
+Scriveno uses Node’s built-in test runner to lock the shipped command, docs, installer, and package surfaces against regression.
+
+## Test runner
+
+The root `package.json` defines:
+
+```json
+"scripts": {
+  "test": "node --test test/*.test.js",
+  "pack:check": "npm pack --dry-run",
+  "release:check": "npm test && npm run pack:check",
+  "prepublishOnly": "npm run release:check"
+}
+```
+
+That means:
+
+- `npm test` runs the whole test suite
+- `npm run pack:check` verifies the package contents that would ship
+- `npm run release:check` runs both test and package checks
+- publishing is guarded by `release:check` through `prepublishOnly`
+
+## Run the suite
+
+Full run:
+
+```bash
+npm test
+```
+
+Direct Node invocation:
+
+```bash
+node --test test/*.test.js
+```
+
+Target one or two files while iterating:
+
+```bash
+node --test test/package.test.js test/constraints.test.js
+```
+
+## What is covered
+
+The `test/` directory currently includes coverage for:
+
+- package metadata and npm packaging behavior
+- command inventory and constraints integrity
+- installer behavior and runtime-target setup
+- demo and baseline product surfaces
+- milestone-specific trust, publishing, translation, illustration, and collaboration regressions
+
+Representative files:
+
+- `test/package.test.js`
+- `test/constraints.test.js`
+- `test/installer.test.js`
+- `test/commands.test.js`
+- `test/phase13-launch-surface-integrity.test.js`
+- `test/phase14-runtime-credibility.test.js`
+- `test/phase18-technical-writing-domain-modeling.test.js`
+- `test/phase19-verification-trust-surface-updates.test.js`
+
+## High-signal test categories
+
+### Package and release safety
+
+Use these when changing package metadata, release docs, or shipped-file expectations:
+
+- `test/package.test.js`
+- `npm run release:check`
+
+These catch drift around Node baseline, packed files, and release-facing package claims.
+
+### Constraints and command inventory
+
+Use these when changing command registration, work-type counts, or adaptive terminology:
+
+- `test/constraints.test.js`
+- `test/commands.test.js`
+
+### Installer and runtime support
+
+Use these when touching `bin/install.js`, runtime docs, or installer target messaging:
+
+- `test/installer.test.js`
+- `test/phase14-runtime-credibility.test.js`
+- `test/phase16-trust-regression.test.js`
+
+### Documentation and trust surfaces
+
+Use these when changing README, docs, shipped-assets claims, or milestone trust wording:
+
+- `test/phase13-launch-surface-integrity.test.js`
+- `test/phase15-proof-artifacts-positioning.test.js`
+- `test/phase19-verification-trust-surface-updates.test.js`
+- `test/repository-policy.test.js`
+
+### Feature-family regression tests
+
+Use these when changing milestone-specific capabilities:
+
+- `test/phase5-export-publishing.test.js`
+- `test/phase6-illustration.test.js`
+- `test/phase7-translation-localization.test.js`
+- `test/phase8-collaboration-platform-sacred.test.js`
+- `test/phase18-technical-writing-domain-modeling.test.js`
+
+## When to add tests
+
+Add or extend tests when a change affects:
+
+- visible command counts or work-type counts
+- docs that make trust-sensitive claims
+- installer targets or setup instructions
+- package contents
+- adaptation logic in `data/CONSTRAINTS.json`
+- new milestone surfaces that should stay locked after shipping
+
+If a user-facing claim can silently drift, it probably deserves a test.
+
+## Package checks outside the test runner
+
+Some important release checks are shell commands rather than Node tests:
+
+```bash
+npm pack --dry-run
+npm publish --dry-run
+```
+
+For the standard release gate, prefer:
+
+```bash
+npm run release:check
+```
+
+Use those for release prep so you can inspect what would ship without mutating the registry.
+
+## Practical workflow
+
+For most changes:
+
+1. run the targeted test files first
+2. make the fix
+3. rerun the targeted files
+4. run `npm test`
+5. if packaging or release docs changed, run `npm run release:check`
+
+## Related docs
+
+- [Development](development.md)
+- [Configuration](configuration.md)
+- [Contributing](contributing.md)
+- [Release Notes](release-notes.md)