scriveno 2.0.5 → 2.0.6

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.5-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-2.0.6-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)
 
@@ -203,11 +203,11 @@ Scriveno currently ships installer targets for these AI tooling environments:
 
 ## Status
 
-**Version:** 2.0.5
+**Version:** 2.0.6
 
- 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, and domain-grilling work through `2.0.5`. 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, and installer-marker cleanup work through `2.0.6`. 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.5` publishes Scriveno under the package name `scriveno`, so the current install command is `npx scriveno@latest`. The older `scriveno-cli` package name remains historical; new docs and package metadata now point at `scriveno`. 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.6` 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/bin/install.js

@@ -686,7 +686,7 @@ function rewriteInstalledCommandRefs(content, transform) {
 }
 
 function markInstalledCommand(content, runtimeKey, commandRef, sourcePath) {
-  const marker = `<!-- scriveno-cli-installed-command runtime:${runtimeKey} command:${commandRef} source:${sourcePath} -->`;
+  const marker = `<!-- scriveno-installed-command runtime:${runtimeKey} command:${commandRef} source:${sourcePath} -->`;
   return insertMarkerComment(content, marker);
 }
 
@@ -708,7 +708,7 @@ function generateCodexCommandContent(entry, sourceContent) {
 function isScrivenoInstalledCommandFile(filePath) {
   if (!fs.existsSync(filePath)) return false;
   const content = fs.readFileSync(filePath, 'utf8');
-  return content.includes('scriveno-cli-installed-command');
+  return content.includes('scriveno-installed-command') || content.includes('scriveno-cli-installed-command');
 }
 
 function cleanFlatCommandFiles(commandsDir, currentFileNames, legacyDirs = []) {
@@ -754,7 +754,7 @@ function cleanFlatCommandFiles(commandsDir, currentFileNames, legacyDirs = []) {
 function writeInstalledCommandManifest(commandsDir, runtimeKey, fileNames) {
   const manifestPath = path.join(commandsDir, '.scriveno-installed.json');
   const manifest = {
-    installer: 'scriveno-cli',
+    installer: 'scriveno',
     version: VERSION,
     runtime: runtimeKey,
     files: fileNames,
@@ -1194,7 +1194,7 @@ function cleanCodexSkillDirs(skillsDir, currentSkillNames) {
 function writeCodexSkillManifest(skillsDir, skillNames) {
   const manifestPath = path.join(skillsDir, '.scriveno-installed.json');
   const manifest = {
-    installer: 'scriveno-cli',
+    installer: 'scriveno',
     version: VERSION,
     skills: skillNames,
     generated_at: new Date().toISOString(),

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

package/commands/scr/sync.md

@@ -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:

package/data/CONSTRAINTS.json

@@ -1,6 +1,6 @@
 {
   "$schema": "./constraints.schema.json",
-  "version": "2.0.5",
+  "version": "2.0.6",
   "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/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.6",
   "work_type": "<chosen>",
   "group": "<group>",
   "command_unit": "<unit>",

package/docs/release-notes.md

@@ -2,6 +2,34 @@
 
 This document is the public-facing summary of what changed between package releases. For package history, see the root [CHANGELOG](../CHANGELOG.md).
 
+## 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 +39,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 +48,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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "scriveno",
-  "version": "2.0.5",
+  "version": "2.0.6",
   "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.5",
+  "scriveno_version": "2.0.6",
   "work_type": "",
   "group": "",
   "command_unit": "",