scriveno 2.0.10 → 2.0.11

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.0.10-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-2.0.11-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)
@@ -235,11 +235,11 @@ Scriveno currently ships installer targets for these AI tooling environments:
 
 ## Status
 
-**Version:** 2.0.10
+**Version:** 2.0.11
 
- Scriveno's core command surface is stable across 112 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, and route graph audits through `2.0.10`. See [Shipped Assets](docs/shipped-assets.md) for the canonical asset inventory and [Runtime Support](docs/runtime-support.md) for the runtime compatibility matrix.
+Scriveno's core command surface is stable across 112 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, and the full audit repair pass through `2.0.11`. See [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.0.10` 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.0.11` 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/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.0.10",
+  "scriveno_version": "2.0.11",
   "work_type": "<chosen>",
   "group": "<group>",
   "command_unit": "<unit>",

package/commands/scr/sacred-numbering-format.md

@@ -3,14 +3,14 @@ description: "Show verse numbering format for the active sacred tradition."
 argument-hint: "[--example <text>]"
 ---
 
-# /scr:sacred-verse-numbering -- Tradition Verse Numbering Reference
+# /scr:sacred-numbering-format -- Tradition Verse Numbering Reference
 
 Show the verse numbering format for the active sacred tradition. Reads the tradition profile from the project's config and displays the numbering system with example citations.
 
 ## Usage
 
 ```
-/scr:sacred-verse-numbering [--example <text>]
+/scr:sacred-numbering-format [--example <text>]
 ```
 
 If `--example <text>` is provided, format the given text as a citation in the tradition's numbering system.

package/data/CONSTRAINTS.json

@@ -1,6 +1,6 @@
 {
   "$schema": "./constraints.schema.json",
-  "version": "2.0.10",
+  "version": "2.0.11",
   "description": "Scriveno constraint system: work types, command availability, exports, and dependencies. Every command checks this file at runtime.",
   "_notes": {
     "sacred_keys": "Sacred subcommands live at commands/scr/sacred/<name>.md and run as /scr:sacred:<name>. Their CONSTRAINTS keys use the sacred:<name> form so /scr:help can render the runnable slash-command path directly. The sacred-numbering-format entry is a separate flat command (commands/scr/sacred-numbering-format.md) that surfaces the active tradition's numbering format. It used to be named sacred-verse-numbering, which collided with sacred:verse-numbering at install time -- both flattened to scr-sacred-verse-numbering. Renamed in v1.6.x; the installer now refuses to install when two sources share a flat skill name."

package/data/demo/.manuscript/plans/5-the-reunion-PLAN.md

@@ -49,4 +49,4 @@ Close third (Elias), past tense. Intimate distance. The narrator stays inside El
 - Elias's established speech patterns from previous scenes
 
 ---
-*This is a planning document. Draft with /scr:draft-scene 5.*
+*This is a planning document. Draft with /scr:draft 5.*

package/docs/command-reference.md

@@ -4,6 +4,8 @@ Scriveno has **112 commands** organized into **14 categories**. Commands adapt a
 
 Commands marked with **adaptive terminology** change how Scriveno talks about your work type's `command_unit` in `.manuscript/config.json`, while keeping the runnable command id stable. Commands marked with **group adaptation** have different labels for specific work type groups (academic, sacred, etc.).
 
+This page covers writer-facing `/scr:*` commands. Package-level audit commands live in the `scriveno` CLI: `scriveno status --project . --apply-safe`, `scriveno sync --check`, `scriveno smoke`, `scriveno agents`, and `scriveno routes`. See [Auto-Invoke Policy](auto-invoke-policy.md), [Runtime Support](runtime-support.md), and [Route Graph Audit](route-graph.md) for those surfaces.
+
 ## Table of Contents
 
 1. [Core](#core) -- The main workflow: create, discuss, plan, draft, review, submit

package/docs/configuration.md

@@ -57,7 +57,7 @@ When a writer runs `/scr:new-work`, Scriveno creates `.manuscript/config.json`.
 
 ```json
 {
-  "scriveno_version": "2.0.10",
+  "scriveno_version": "2.0.11",
   "work_type": "<chosen>",
   "group": "<group>",
   "command_unit": "<unit>",
@@ -217,6 +217,15 @@ And for release-facing changes, also run:
 npm run release:check
 ```
 
+When configuration changes touch runtime paths, route logic, agent prompts, sync behavior, or installed audit surfaces, also run:
+
+```bash
+scriveno sync --check
+scriveno smoke --json
+scriveno agents --json
+scriveno routes --json
+```
+
 ## Related docs
 
 - [Getting Started](getting-started.md)

package/docs/contributing.md

@@ -381,6 +381,9 @@ When a package release changes the public story, update the release docs alongsi
 - `README.md` -- current version/status blurb when the release changes the headline positioning
 - `docs/shipped-assets.md` -- canonical inventory when bundled docs, templates, proof assets, or trust-critical files change
 - `docs/command-reference.md` -- command contract reference when command behavior or flags change
+- `docs/auto-invoke-policy.md` -- proactive routing, safe apply, local-helper, and agent-spawn policy
+- `docs/runtime-support.md` -- runtime matrix, install-surface checks, and agent availability claims
+- `docs/route-graph.md` -- route graph, automation lanes, and priority fixtures when route logic changes
 - `templates/*/README.md` and `data/proof/*/README.md` -- shipped profile and proof documentation when those assets change
 - `.planning/` milestone summary files -- only when the release closes out milestone work or changes the archive story
 
@@ -391,7 +394,8 @@ When a package release changes the public story, update the release docs alongsi
 3. Update `docs/release-notes.md` with a concise explanation of what changed, why, and how it was verified
 4. Run `npm test`
 5. Run `npm run release:check`
-6. Publish only after the docs and package metadata tell the same story
+6. For runtime, installer, agent, sync, or route-intelligence changes, run `scriveno sync --check`, `scriveno smoke --json`, `scriveno agents --json`, and `scriveno routes --json`
+7. Publish only after the docs and package metadata tell the same story
 
 ## Code Style
 

package/docs/development.md

@@ -120,6 +120,21 @@ node bin/install.js --runtime codex --global --developer --silent
 
 The writer-facing form of this maintenance operation is `/scr:sync`.
 
+For a full cross-runtime refresh from this checkout, use:
+
+```bash
+node bin/install.js --runtimes claude-code,cursor,gemini-cli,codex,opencode,copilot,windsurf,antigravity,manus,perplexity-desktop,generic --global --developer --silent
+```
+
+After installation, the shared audit commands should pass:
+
+```bash
+scriveno sync --check
+scriveno smoke --json
+scriveno agents --json
+scriveno routes --json
+```
+
 ## Docs and release workflow
 
 Docs are part of the shipped product. If you change visible behavior, update every affected documentation surface in the same pass: root docs, files under `docs/`, proof READMEs, template READMEs, and command markdown that exposes user-facing contracts.
@@ -131,6 +146,9 @@ For release-oriented documentation surfaces, the main files are:
 - `docs/release-notes.md`
 - `docs/shipped-assets.md`
 - `docs/command-reference.md`
+- `docs/auto-invoke-policy.md`
+- `docs/runtime-support.md`
+- `docs/route-graph.md`
 - `templates/*/README.md` when shipped profiles or templates change
 - `.planning/` milestone summaries when you are still using the GSD planning layer
 
@@ -141,7 +159,8 @@ A good pre-ship pass for Scriveno changes is:
 1. run the targeted tests for the touched surface
 2. run `npm test`
 3. run `npm run release:check` for package-facing changes
-4. review trust-sensitive docs for runtime, asset, and support claims
+4. run the proactive audit commands when routing, runtime, installer, or agent surfaces changed
+5. review trust-sensitive docs for runtime, asset, and support claims
 
 ## Related docs
 
@@ -149,4 +168,7 @@ A good pre-ship pass for Scriveno changes is:
 - [Configuration](configuration.md)
 - [Testing](testing.md)
 - [Contributing](contributing.md)
+- [Auto-Invoke Policy](auto-invoke-policy.md)
+- [Runtime Support](runtime-support.md)
+- [Route Graph Audit](route-graph.md)
 - [Release Notes](release-notes.md)

package/docs/getting-started.md

@@ -210,5 +210,6 @@ If you want the trust surfaces around installation and shipping details, continu
 
 - [Runtime Support](runtime-support.md) -- installer targets, support levels, and verification status
 - [Auto-Invoke Policy](auto-invoke-policy.md) -- status engine, visible automation, and agent-spawn boundaries
+- [Route Graph Audit](route-graph.md) -- generated route graph, automation lanes, and priority fixtures
 - [Shipped Assets](shipped-assets.md) -- what the npm package actually includes on the trust-critical surface
 - [Release Notes](release-notes.md) -- what changed in the latest package release

package/docs/proof-artifacts.md

@@ -53,4 +53,6 @@ Read the bundle in order if you want to inspect sentence rhythm, metaphor select
 
 - [Shipped Assets](shipped-assets.md) -- canonical inventory of the trust-critical files Scriveno actually bundles
 - [Runtime Support](runtime-support.md) -- canonical runtime matrix and installer-baseline framing
+- [Auto-Invoke Policy](auto-invoke-policy.md) -- proactive status, safe apply, local-helper, and agent-spawn boundaries
+- [Route Graph Audit](route-graph.md) -- generated route graph, automation lanes, and priority fixtures
 - [Release Notes](release-notes.md) -- summary of what changed in the latest package release

package/docs/release-notes.md

@@ -2,6 +2,44 @@
 
 This document is the public-facing summary of what changed between package releases. For package history, see the root [CHANGELOG](../CHANGELOG.md).
 
+## 2.0.11 - 2026-05-16
+
+### What changed
+
+- Scriveno received a full repo audit across 500 tracked files and the latest 242-file package surface.
+- The sacred numbering command now consistently advertises `/scr:sacred-numbering-format` instead of the stale `/scr:sacred-verse-numbering` name.
+- Sacred doctrine and lineage templates now point to `/scr:sacred:doctrinal-check`, matching the shipped command surface.
+- The demo manuscript plan now tells users to run `/scr:draft 5` instead of the removed `/scr:draft-scene 5` command.
+- Archived planning summaries no longer use decorative test-output markers that violate the repository writing policy.
+- README badges, Route Graph, Configuration, changelog, package metadata, constraints metadata, generated config metadata, and release tests are aligned on `2.0.11`.
+
+### Why it matters
+
+This release tightens the shipped surface after the automation releases. Writers should see current command names in docs, templates, demo files, and installed runtime copies. Developers now have a cleaner package baseline before the next milestone begins.
+
+### Affected areas
+
+- command documentation
+- sacred project templates
+- demo manuscript assets
+- release metadata
+- planning state
+- README badge and status copy
+- cross-runtime installed surfaces
+- regression tests for release metadata and sacred command naming
+
+### Verification
+
+- `npm run release:check`
+- `node bin/install.js routes --json`
+- `node bin/install.js agents --json`
+- `node bin/install.js sync --check --json`
+- `node bin/install.js smoke --json`
+- `npm audit --omit=dev --json`
+- `npm pack --dry-run`
+- `git diff --check`
+- repository policy scan for em dashes, en dashes, and decorative emoji-style markers
+
 ## 2.0.10 - 2026-05-16
 
 ### What changed

package/docs/route-graph.md

@@ -13,7 +13,7 @@ The text report summarizes command count, graph edges, agent-capable routes, loc
 
 ## Current Shape
 
-As of `2.0.10`, the route graph contains:
+As of `2.0.11`, the route graph contains:
 
 - 112 commands
 - intent-order edges from `command_intents`

package/docs/sacred-texts.md

@@ -182,7 +182,7 @@ Apply or adjust verse numbering systems to your drafted text. Supports 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.
+The top-level `/scr:sacred-numbering-format` 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`
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "scriveno",
-  "version": "2.0.10",
+  "version": "2.0.11",
   "description": "Spec-driven creative writing, publishing, and translation pipeline for AI coding agents. From blank page to published book.",
   "bin": {
     "scriveno": "bin/install.js"

package/templates/config.json

@@ -1,5 +1,5 @@
 {
-  "scriveno_version": "2.0.10",
+  "scriveno_version": "2.0.11",
   "work_type": "",
   "group": "",
   "command_unit": "",

package/templates/sacred/DOCTRINES.md

@@ -42,4 +42,4 @@
 
 ---
 
-*Drafter agents check this file to avoid contradicting established doctrines when drafting passages. `/scr:doctrinal-check` flags any unit that contradicts or undermines an affirmed doctrine without explicit intent.*
+*Drafter agents check this file to avoid contradicting established doctrines when drafting passages. `/scr:sacred:doctrinal-check` flags any unit that contradicts or undermines an affirmed doctrine without explicit intent.*

package/templates/sacred/LINEAGES.md

@@ -49,4 +49,4 @@
 
 ---
 
-*When drafting any unit involving figures, the drafter agent checks this file to verify lineage claims, covenant references, and relationships. Contradictions are flagged by `/scr:doctrinal-check`.*
+*When drafting any unit involving figures, the drafter agent checks this file to verify lineage claims, covenant references, and relationships. Contradictions are flagged by `/scr:sacred:doctrinal-check`.*