scriveno 2.0.5 → 2.0.7

package/commands/scr/plan.md

@@ -78,12 +78,34 @@ Require `{N}-CONTEXT.md` to exist (from discuss phase). If it doesn't, offer to
 
 7. **Update STATE.md** and suggest: "Ready to draft? Run `/scr:draft N`." (Suppress the draft suggestion if any plan came back NEEDS REVISION; suggest addressing the flagged items first.)
 
+   If `.manuscript/config.json` has `autopilot.enabled: true`, all plan checks are READY, and the active profile is `full-auto`, immediately proceed to `/scr:draft N` instead of stopping at a suggestion. In `supervised`, pause here and show the plan-check summary before drafting. In `guided`, ask for approval before drafting.
+
 8. **Append one line to `.manuscript/HISTORY.log`** per `docs/history-protocol.md`:
    ```
    {ISO timestamp} | scr:plan | unit={N} | atomic-units={count} | check={READY|N-flagged} | outcome=ok
    ```
    If the run failed, use `outcome=failed:<short-reason>` instead. Create HISTORY.log if it does not exist.
 
+## Agent and Automation Status
+
+Every response must include a short status block that makes invocation visible:
+
+```text
+Agent status:
+Trigger: /scr:plan N
+Spawned agents:
+- plan-checker: {count} fresh-context invocation(s)
+Local operations:
+- plan files written: {count}
+- STATE.md updated: yes/no
+- HISTORY.log updated: yes/no
+Auto-invoked:
+- /scr:draft N: yes/no
+Why: {all plans READY plus full-auto, supervised pause, guided approval needed, or plan check blocked}
+```
+
+If the host runtime cannot spawn a native `plan-checker` agent type, load the installed `agents/plan-checker.md` prompt from the active runtime and run it in an isolated fresh context. In the status block, write `Spawned agents: native unavailable; prompt-run fallback used`.
+
 ## Response Contract
 
 Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.

package/commands/scr/progress.md

@@ -7,6 +7,8 @@ argument-hint: ""
 
 You are showing the writer their current project progress.
 
+Follow the auto-invoke policy. In the source repository it is documented at `docs/auto-invoke-policy.md`. `/scr:progress` is read-only: it can count, compare, and recommend, but it must not spawn agents or write files.
+
 ## Prerequisites
 
 - `.manuscript/STATE.md` must exist
@@ -22,6 +24,29 @@ You are showing the writer their current project progress.
    - "{word_count} words so far."
    - "{open_threads} open record threads." (only when RECORD.md exists)
    - "Next: {next_action}"
+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.
+   - If exports are stale, suggest `/scr:export` or `/scr:publish`.
+   - If translation work exists and follow-up reports are missing, suggest the next translation check.
+   - If unsaved manuscript changes exist, suggest `/scr:save`.
+
+## Automation Status
+
+Every response must include a compact status block:
+
+```text
+Automation status:
+Trigger: /scr:progress
+Spawned agents:
+- none
+Local operations:
+- progress counts computed: yes/no
+- proactive sweep: read-only
+Auto-invoked:
+- none
+Why: progress is read-only; it recommends next commands without mutating files
+```
 
 ## Response Contract
 

package/commands/scr/quick-write.md

@@ -43,6 +43,8 @@ If `--discuss`: Ask 3-5 targeted questions about tone, pacing, and purpose for t
 
 If `--research`: Spawn a focused researcher for technique guidance.
 
+If the host runtime cannot spawn a focused researcher, run the research pass in an isolated fresh context and report `prompt-run fallback used` in the status block.
+
 ### STEP 3: DRAFT
 
 Write the passage following all established style guide constraints. Target whatever length feels natural unless the writer specified a target.
@@ -58,6 +60,27 @@ Save plan (if generated) to `.manuscript/quick/{NNN}-{slug}/PLAN.md`
 
 Commit: `quick: {slug}`
 
+## Agent and Automation Status
+
+Every response must include a short status block that makes invocation visible:
+
+```text
+Agent status:
+Trigger: /scr:quick-write {flags}
+Spawned agents:
+- researcher: yes/no
+Local operations:
+- context files loaded: {count}
+- draft file written: yes/no
+- plan file written: yes/no
+Auto-invoked:
+- /scr:continuity-check: yes/no
+- /scr:voice-check: yes/no
+Why: --full runs verification after drafting; --research spawns a focused technique pass
+```
+
+In default mode, report `researcher: none` and both auto-invoked checks as `no`.
+
 ## Response Contract
 
 Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.

package/commands/scr/save.md

@@ -7,6 +7,8 @@ argument-hint: "[optional message]"
 
 You are saving the writer's current work. Your job is to create a git commit with a writer-friendly message, without exposing any git terminology.
 
+Follow the auto-invoke policy. In the source repository it is documented at `docs/auto-invoke-policy.md`. `/scr:save` does not spawn agents. It owns safe local helpers for `STATE.md`, `CONTEXT.md`, and `HISTORY.log`, then saves `.manuscript/`.
+
 ## What to do
 
 1. **Check for `.manuscript/` directory.** If missing: "No manuscript found. Start with `/scr:new-work`."
@@ -69,6 +71,25 @@ You are saving the writer's current work. Your job is to create a git commit wit
 
 10. **Tell the writer** the result (see output section below).
 
+## Automation Status
+
+Every response must include a compact status block:
+
+```text
+Automation status:
+Trigger: /scr:save
+Spawned agents:
+- none
+Local operations:
+- STATE.md updated: yes/no
+- CONTEXT.md regenerated: yes/no
+- HISTORY.log appended: yes/no
+- manuscript files saved: yes/no
+Auto-invoked:
+- /scr:next route computed for CONTEXT.md: yes/no
+Why: save uses deterministic local bookkeeping, not a spawned agent
+```
+
 ## Writer mode output
 
 - **Writer mode** (`developer_mode: false`): "Saved. You can see your save history with `/scr:history`."

package/commands/scr/scan.md

@@ -7,6 +7,8 @@ argument-hint: "[--fix] [--quiet]"
 
 You are the project's drift detector. Trust nothing. Compare what `.manuscript/STATE.md`, `OUTLINE.md`, `RECORD.md`, `config.json`, and the various structural files **claim** against what the filesystem actually contains, and report every mismatch.
 
+Follow the auto-invoke policy. In the source repository it is documented at `docs/auto-invoke-policy.md`. `/scr:scan` does not spawn agents. It may run deterministic local checks and, under `--fix` after confirmation, deterministic local repairs.
+
 This is the defense against context corruption. A fresh Claude session, a writer who hand-edited files between sessions, an interrupted command, or a partial revert can all leave the project in an internally inconsistent state. STATE.md says 12 units drafted; the disk has 14. OUTLINE.md lists "Chapter 8" but no draft file exists. RECORD.md says a promise is still open but the draft paid it off. STYLE-GUIDE.md was edited yesterday but no voice-check has run since. `/scr:scan` finds those.
 
 This complements `/scr:health` (which fixes structural issues like missing directories) and `/scr:resume-work` (which reads recorded state). `/scr:scan` interrogates whether the recorded state is true.
@@ -261,6 +263,24 @@ After any auto-fix, append a single line to HISTORY.log per `docs/history-protoc
 
 ---
 
+## Automation Status
+
+Every response must include a compact status block:
+
+```text
+Automation status:
+Trigger: /scr:scan {flags}
+Spawned agents:
+- none
+Local operations:
+- drift checks run: {count}
+- auto-fixes applied: {count}
+- HISTORY.log appended: yes/no
+Auto-invoked:
+- none
+Why: scan compares disk state locally; fixes require writer confirmation
+```
+
 ## Response Contract
 
 Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.

package/commands/scr/session-report.md

@@ -7,6 +7,8 @@ argument-hint: ""
 
 You are summarizing the writer's current session. Your job is to compute actionable metrics from STATE.md and present them clearly.
 
+Follow the auto-invoke policy. In the source repository it is documented at `docs/auto-invoke-policy.md`. `/scr:session-report` is read-only and does not spawn agents.
+
 ## What to do
 
 1. **Read STATE.md "Last actions" table** to get the full history of actions.
@@ -44,6 +46,23 @@ Present the report in this format:
 | 3:15 PM | Editor review complete |
 ```
 
+## Automation Status
+
+Every response must include a compact status block:
+
+```text
+Automation status:
+Trigger: /scr:session-report
+Spawned agents:
+- none
+Local operations:
+- session metrics computed: yes/no
+- quality pass summary computed: yes/no
+Auto-invoked:
+- none
+Why: session-report summarizes disk state without mutating files
+```
+
 ## Edge cases
 
 - **No actions this session:** If the Last actions table is empty or has no entries after the last pause/resume marker, say: "Nothing to report yet. Start working with `/scr:next`."

package/commands/scr/sync.md

@@ -7,7 +7,7 @@ argument-hint: "[--check] [--apply] [--runtime <key>] [--detected] [--global|--p
 
 You are synchronizing Scriveno's installed agent surfaces with the current Scriveno source tree.
 
-This command is for local runtime drift: Codex skills, Codex command mirrors, Claude command files, Cursor command files, and agent prompts that no longer match the source files in the Scriveno package or repo.
+This command is for local runtime drift: Codex skills, Codex command mirrors, Claude Code command files, command-directory runtimes, skills runtimes, guided setup assets, and agent prompts that no longer match the source files in the Scriveno package or repo.
 
 This is not a package upgrade command. Do not fetch a newer Scriveno release, do not change npm dependencies, and do not modify manuscript content. If the writer wants a newer published package version, that belongs to a future `/scr:update` command.
 
@@ -32,7 +32,7 @@ If you cannot find a Scriveno source root, stop and explain that `/scr:sync` nee
 
 1. Locate the Scriveno source root:
    - First, check the current working directory and its parents for `package.json` with `"name": "scriveno"` or legacy `"name": "scriveno-cli"` plus `bin/install.js`.
-   - If running from an installed command copy that contains a `scriveno-cli-installed-command` marker, derive the source root from that marker's `source:` path.
+   - If running from an installed command copy that contains a `scriveno-installed-command` marker, derive the source root from that marker's `source:` path. Older `scriveno-cli-installed-command` markers are accepted as legacy input only.
    - If neither works, stop with the prerequisite message above.
 2. Read `package.json` from the source root and report the source version.
 3. Detect target runtimes:
@@ -47,9 +47,15 @@ If you cannot find a Scriveno source root, stop and explain that `/scr:sync` nee
      - GitHub Copilot: `~/.github/commands/scr/`, `~/.github/agents/`
      - Windsurf: `~/.windsurf/commands/scr/`, `~/.windsurf/agents/`
      - Antigravity: `~/.gemini/antigravity/commands/scr/`, `~/.gemini/antigravity/agents/`
+     - Manus Desktop: `~/.manus/skills/scriveno/SKILL.md` plus mirrored `commands/scr/` and `agents/` inside that skill bundle
+     - Perplexity Desktop: `~/.scriveno/perplexity/SETUP.md` and `connector-command.txt`
+     - Generic skills fallback: `~/.scriveno/skills/SKILL.md` plus mirrored `commands/scr/` and `agents/`
 4. Compare source files against installed files:
    - Compare command counts.
    - Compare a representative hash set for `commands/scr/autopilot.md`, `commands/scr/next.md`, `commands/scr/scan.md`, `commands/scr/sync.md`, and all generated Codex `SKILL.md` wrappers when present.
+   - Check that Claude Code flat commands include `/scr-*` invocation rewrites and source-marker behavior after reinstall.
+   - Check that standard command-directory runtimes preserve nested command paths under their `commands/scr/` directory.
+   - Check that skills runtimes include `SKILL.md`, mirrored commands, and mirrored agent prompts inside their skill bundle.
    - Check that installed Codex commands include current response-contract and source-marker behavior after reinstall.
    - Report each runtime as `current`, `stale`, `missing`, or `unknown`.
 5. Decide mode:
@@ -70,15 +76,57 @@ Adjust flags from the command arguments:
 7. After applying, verify:
    - Re-read installed command counts.
    - Confirm `sync.md` is installed for each target runtime.
+   - For Claude Code, confirm `scr-sync.md` exists and installed agent prompts are present in the chosen `agents/` directory.
+   - For standard command-directory runtimes, confirm `commands/scr/sync.md` and installed agent prompts are present.
+   - For skills runtimes, confirm `SKILL.md`, `commands/scr/sync.md`, and bundled agent prompts are present.
+   - For Perplexity Desktop, confirm the setup guide and connector recipe are present.
    - For Codex, confirm both `~/.codex/commands/scr/sync.md` and `~/.codex/skills/scr-sync/SKILL.md` exist in the chosen scope.
+   - For Codex, confirm installed Scriveno agents have matching `.toml` metadata files in the chosen `agents/` directory when the Codex runtime supports agent metadata.
    - Confirm no stale runtime files remain in the checked target set.
-8. Report:
+8. Report a compact sync status trail:
    - Source version
    - Runtime targets checked
    - Runtime targets updated
    - Any skipped targets and why
+   - Trigger: `check`, `apply`, or `prompted apply`
+   - Agent: `none` for this command
+   - Engine: `bin/install.js` when applying, or `hash/count comparison` when checking only
+   - Local operations: command files compared, Claude flat commands checked, standard command directories checked, skills manifests checked, guided setup assets checked, agent prompts checked, Codex skills checked, Codex command mirrors checked, Codex agent metadata checked when applicable
+   - Result counts: commands, skills, agent prompts, metadata files, stale files removed, and skipped targets
    - Suggested project-level follow-up with `/scr:scan`
 
+Use this report shape:
+
+```text
+Sync status:
+Trigger: /scr:sync --apply --detected --global --developer
+Agent: none
+Why: runtime sync is installer-driven, not a writing or review agent task
+Engine: bin/install.js
+Checked:
+- commands: 112 source, 112 installed
+- Claude Code flat commands: 112 installed
+- standard command directories: current
+- skills manifests: current
+- guided setup assets: current
+- Codex skills: 112 installed
+- agent prompts: 6 installed
+- Codex agent metadata: 6 installed
+Updated:
+- Claude Code command files
+- standard command directories
+- skills manifests
+- guided setup assets
+- Codex command mirrors
+- Codex skills
+- Codex agent prompts
+- Codex agent metadata
+Skipped:
+- none
+```
+
+If no files were changed, keep the same shape and set `Updated: none`. If an agent was not spawned, always say `Agent: none` and explain why.
+
 ## Safety Rules
 
 - Only overwrite Scriveno-owned installed runtime files.

package/commands/scr/track.md

@@ -494,6 +494,26 @@ For standard revision tracks where only the track has changes (canon is unmodifi
 
 The `.manuscript/merge-log.json` file accumulates entries from every co-writing merge. Each entry preserves both versions of contradictory passages, the resolution chosen, and any reconciled text. This provides a history of how parallel work was integrated and supports future continuity auditing.
 
+### Automation Status
+
+Every `track merge` response must include a compact status block:
+
+```text
+Automation status:
+Trigger: /scr:track merge {track}
+Auto-invoked:
+- /scr:continuity-check equivalent: yes/no
+Spawned agents:
+- continuity-checker: yes/no
+Local operations:
+- track metadata checked: yes/no
+- canon and track changes compared: yes/no
+- merge log updated: yes/no
+Why: co-writing or parallel canon changes require continuity verification before accepting revisions
+```
+
+If continuity verification did not run, say why: standard revision track, canon unchanged, or writer cancelled before merge. If native `continuity-checker` spawning is unavailable, use the installed prompt in an isolated fresh context and report `prompt-run fallback used`.
+
 ---
 
 ## Writer-Friendly Language Guide

package/commands/scr/translate.md

@@ -171,6 +171,8 @@ Invoke the translator agent (`agents/translator.md`) with fresh context, providi
 
 **Fresh context per unit is mandatory.** Each translator invocation is independent -- this prevents translation drift, glossary inconsistency, and register collapse across a long manuscript.
 
+If the host runtime cannot spawn a native `translator` agent type, load the installed `agents/translator.md` prompt from the active runtime and run it in an isolated fresh context. Record that fallback in the status block.
+
 **5d. Post-unit processing:**
 
 After each unit translation:
@@ -214,6 +216,29 @@ After all units are translated, show a summary:
 > - Back-translate to verify: `/scr:back-translate [lang]`
 > - Export translation: `/scr:export --format [format] --language [lang]`
 
+## Agent and Automation Status
+
+Every response must include a short status block that makes invocation visible:
+
+```text
+Agent status:
+Trigger: /scr:translate {language}
+Spawned agents:
+- translator: {count} fresh-context invocation(s)
+Local operations:
+- glossary loaded: yes/no
+- translation memory loaded: yes/no
+- units written: {count}
+- new glossary terms flagged: {count}
+Auto-invoked:
+- /scr:translation-memory {language} --build: yes/no
+- /scr:cultural-adaptation {language}: yes/no
+- /scr:back-translate {language}: yes/no
+Why: {manual translation mode, autopilot-translate phase, or writer requested chained verification}
+```
+
+Plain `/scr:translate` does not auto-run translation memory, cultural adaptation, or back-translation unless the writer requested a chained verification or the command is being run inside `/scr:autopilot-translate`. Show `Auto-invoked: no` for those follow-up checks in manual mode.
+
 ## Response Contract
 
 Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.

package/commands/scr/voice-check.md

@@ -45,6 +45,8 @@ Spawn the voice-checker agent (`agents/voice-checker.md`) with:
 - The scoped drafted prose (unit `N` or all units)
 - If available, previously approved units as reference anchors for comparison
 
+If the host runtime cannot spawn a native `voice-checker` agent type, load the installed `agents/voice-checker.md` prompt from the active runtime and run it in an isolated fresh context. Record that fallback in the status block.
+
 Because STYLE-GUIDE.md is present, this is voice-deviation framing: the agent measures deviation *from* the writer's voice, not against a generic ideal. An authentic writer habit is not a tell for that writer even when a generic catalog would flag it; STYLE-GUIDE.md wins.
 
 The voice-checker agent runs its diagnostic discipline: a scrutiny pre-check (match scrutiny to evidence density; low density biases hard toward a high score), a mandatory false-positive audit with veto power (lone weak signals dropped without lowering the score; strong false positives reclassified as human markers that raise it), and an internal-consistency check (sharp register or sophistication seams flagged against the document's own baseline). It performs deep analysis across four dimensions:
@@ -109,6 +111,24 @@ Save the full report to `.manuscript/{scope}-VOICE-CHECK-REPORT.md` where `{scop
 
 Present the score, status, and top issues to the writer. Offer to show the full report.
 
+## Agent Status
+
+Every response must include a short status block that makes invocation visible:
+
+```text
+Agent status:
+Trigger: /scr:voice-check {scope}
+Spawned agents:
+- voice-checker: 1 fresh-context diagnostic invocation
+Local operations:
+- STYLE-GUIDE.md loaded: yes/no
+- drafted files checked: {count}
+- report written: yes/no
+Auto-invoked:
+- none
+Why: voice-check is diagnostic only; fixes are writer-chosen handoffs
+```
+
 ## Response Contract
 
 Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.

package/data/CONSTRAINTS.json

@@ -1,6 +1,6 @@
 {
   "$schema": "./constraints.schema.json",
-  "version": "2.0.5",
+  "version": "2.0.7",
   "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/docs/auto-invoke-policy.md

@@ -0,0 +1,100 @@
+# Auto-Invoke Policy
+
+Scriveno can be proactive, but it must be proactive from disk evidence. Commands should inspect `.manuscript/`, reports, timestamps, config, and installed runtime surfaces before choosing an automatic helper.
+
+## Cross-Platform Agent Rules
+
+Scriveno agent prompts live in `agents/*.md`. Each host runtime exposes them differently:
+
+- Claude Code installs command files in `~/.claude/commands/` and agent prompts in `~/.claude/agents/`.
+- Codex installs `$scr-*` skills, mirrored command files, agent prompts, and `.toml` metadata so Codex can expose agent types.
+- Cursor, Gemini CLI, OpenCode, Copilot, Windsurf, and Antigravity install nested command directories and agent prompts in their runtime-specific agent directories.
+- Manus and the generic skill runtime bundle `SKILL.md`, commands, and agents inside the skill directory.
+
+When a host supports native fresh-context spawning, use the native agent or subagent mechanism. When it does not, load the installed agent prompt from the active runtime and run it in an isolated fresh context. When the action is only a file operation, report `Agent: none`.
+
+Every automatic path must make the distinction visible.
+
+```text
+Agent status:
+Trigger: <command or state condition>
+Spawned agents:
+- <agent-name>: <count, none, or prompt-run fallback used>
+Local operations:
+- <operation>: <result>
+Auto-invoked:
+- <command or helper>: yes/no
+Why: <one sentence tied to disk state>
+```
+
+Use `Automation status:` for command chains and `Sync status:` for runtime install or sync checks.
+
+## Levels
+
+| Level | Behavior | Default | Examples |
+|-------|----------|---------|----------|
+| 1 | Read-only suggestion | Run by default | `/scr:next` route, progress sweep, review queue surfacing |
+| 2 | Safe local helper | Run when directly triggered | `CONTEXT.md` regeneration, `HISTORY.log` append, scan report, stats count |
+| 3 | Scoped agent | Spawn when the command implies it or evidence is bounded | drafter, plan-checker, voice-checker, continuity-checker, translator, beta-reader |
+| 4 | Writer-owned action | Require confirmation | publishing, destructive edits, merge decisions, accepting review findings |
+
+## Level 1: Auto-Suggest
+
+Run these read-only checks in `/scr:next`, `/scr:progress`, and closeouts for major commands:
+
+- If `STATE.md`, `CONTEXT.md`, `HISTORY.log`, or draft mtimes disagree, suggest `/scr:scan`.
+- If voice or continuity reports have unresolved issues, suggest `/scr:voice-check`, `/scr:continuity-check`, or `/scr:editor-review`.
+- If editor notes or track proposals exist, suggest `/scr:editor-review --notes`, `/scr:editor-review --respond`, or `/scr:track`.
+- If translation folders exist or config lists target languages, suggest translation follow-ups.
+- If export outputs are older than source files, suggest `/scr:export` or `/scr:publish`.
+- If no save exists after recent manuscript changes, suggest `/scr:save`.
+
+These checks must not mutate files.
+
+## Level 2: Auto-Run Local Helpers
+
+Run these only when the current command directly owns the file operation:
+
+- `/scr:save` regenerates `.manuscript/CONTEXT.md`, appends `HISTORY.log`, and commits `.manuscript/`.
+- `/scr:scan --fix` applies deterministic state repairs after confirmation and appends `HISTORY.log`.
+- `/scr:resume-work` may regenerate `CONTEXT.md` from disk state.
+- `/scr:progress` may count drafts, submitted units, open record threads, and stale reports, but does not write.
+- Runtime `/scr:sync --apply` runs the installer and verifies installed command, skill, and agent surfaces.
+
+Report these as local operations, not spawned agents.
+
+## Level 3: Auto-Spawn Scoped Agents
+
+Spawn or prompt-run fallback is appropriate when the command already implies a specialist role:
+
+- `/scr:plan` invokes `plan-checker` per plan.
+- `/scr:draft` invokes `drafter` per atomic unit and a voice diagnostic pass when a draft was produced.
+- `/scr:voice-check` invokes `voice-checker`.
+- `/scr:continuity-check` invokes `continuity-checker`.
+- `/scr:translate` invokes `translator` per unit.
+- `/scr:beta-reader` invokes a beta reader persona.
+- `/scr:map-manuscript` invokes analysis workers, or isolated sequential analysis if parallel workers are unavailable.
+- `/scr:editor-review` invokes revision diagnostics only for flagged issue groups.
+
+Do not pretend command-local analysis workers are installed agent files unless they actually are.
+
+## Level 4: Manual Only
+
+Never auto-run these without explicit writer confirmation:
+
+- deleting or removing units
+- accepting, rejecting, or applying editor decisions
+- merging revision tracks
+- clearing review findings
+- final publish or submission packaging
+- overwriting generated export packages
+- destructive repair, reset, revert, or cleanup
+- broad translation or cultural adaptation chains outside autopilot
+
+## Required Closeout
+
+Every proactive command should end with:
+
+- one recommended next command
+- a short reason tied to disk state
+- status showing whether agents spawned, local operations ran, or manual boundaries stopped automation

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.5",
+  "scriveno_version": "2.0.7",
   "work_type": "<chosen>",
   "group": "<group>",
   "command_unit": "<unit>",

package/docs/release-notes.md

@@ -2,6 +2,67 @@
 
 This document is the public-facing summary of what changed between package releases. For package history, see the root [CHANGELOG](../CHANGELOG.md).
 
+## 2.0.7 - 2026-05-16
+
+### What changed
+
+- Codex installs now generate agent metadata beside Scriveno agent prompts so native agent spawning can work when the host exposes those roles.
+- Non-Codex runtimes keep their own install surfaces: Claude Code flat commands and agents, command-directory runtimes, skill-file runtimes, Manus, guided Perplexity Desktop setup, and the generic fallback.
+- Scriveno now has a shared auto-invoke policy for read-only suggestions, deterministic local helpers, scoped agent spawns, and manual-only writer actions.
+- `/scr:next` and `/scr:progress` now do read-only proactive checks and explain what they found.
+- `/scr:save`, `/scr:scan`, `/scr:health`, `/scr:session-report`, `/scr:sync`, and multi-agent workflows now show visible status blocks that say what spawned, what ran locally, and why.
+- Package and shipped metadata are aligned on `2.0.7`.
+
+### Why it matters
+
+Writers and developers should not have to guess whether Scriveno used a native agent, a prompt fallback, or a local file operation. This release makes those paths visible and keeps runtime behavior honest across Codex, Claude Code, and the other supported install targets.
+
+The practical effect is calmer automation: Scriveno can be more proactive about the next safe move, while still keeping writer-owned actions like publishing, destructive edits, merges, and submissions behind explicit approval.
+
+### Affected areas
+
+- Codex agent metadata generation
+- Claude Code and other runtime install verification
+- proactive command guidance
+- local helper visibility
+- `/scr:sync` status reporting
+- README, changelog, release notes, and version metadata
+- regression tests for agent spawning, prompt fallback, and runtime install surfaces
+
+### Verification
+
+- `node --test`
+- `npm run release:check`
+- `git diff --check`
+
+## 2.0.6 - 2026-05-15
+
+### What changed
+
+- New installed command files now use the `scriveno-installed-command` ownership marker.
+- New installed manifests now record `installer: "scriveno"`.
+- Existing installs that still contain the older `scriveno-cli-installed-command` marker remain supported for cleanup and sync detection.
+- `/scr:sync` now documents the current marker and treats the older marker as compatibility-only input.
+- Package and shipped metadata are aligned on `2.0.6`.
+
+### Why it matters
+
+This finishes the visible package rename for new runtime installs. Writers still install with `npx scriveno@latest`, and freshly generated local metadata now matches that package name without breaking older installed command surfaces.
+
+### Affected areas
+
+- installer-generated command markers
+- installed runtime manifests
+- `/scr:sync` guidance
+- README, changelog, release notes, and version metadata
+- regression tests for package-name compatibility
+
+### Verification
+
+- `npm test`
+- `npm run pack:check`
+- `git diff --check`
+
 ## 2.0.5 - 2026-05-15
 
 ### What changed
@@ -11,6 +72,8 @@ This document is the public-facing summary of what changed between package relea
 - The package executable remains `scriveno`, so the installer behavior and command surfaces are unchanged after installation.
 - `/scr:sync` now recognizes both the new source package name `scriveno` and the legacy package name `scriveno-cli` when locating a local source checkout.
 - Package and shipped metadata are aligned on `2.0.5`.
+- The older `scriveno-cli` package name was unpublished during the rename, so npm cannot show a deprecation notice for it unless a compatibility shim is republished under that name.
+- The older `scriven-cli` package name remains on npm as a deprecated legacy package and now points users to `npx scriveno@latest`.
 
 ### Why it matters
 
@@ -18,6 +81,8 @@ The package name now matches the product name. This removes the extra `-cli` suf
 
 Existing installed runtime surfaces do not need to change immediately. The old installed-command marker remains stable so local sync and compatibility checks can keep recognizing prior installs.
 
+For contributors: treat `scriveno` as the only active npm package name. Do not assume `scriveno-cli` can be deprecated in place while it remains unpublished, and do not revive `scriven-cli` except for a deliberate compatibility transition.
+
 ### Affected areas
 
 - npm package metadata