@neocompose/cli 0.59.2 → 0.59.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.59.2",
+  "version": "0.59.4",
   "description": "Neo Compose native project-source CLI with bidirectional sync.",
   "license": "MIT",
   "type": "module",

package/skills/neocompose-cli/SKILL.md

@@ -9,7 +9,7 @@ description: >-
   `@neocompose/cli` or `node cli/bin/neo.mjs` in the neo-compose repository.
 ---
 
-<!-- reviewed-through-cli: 0.59.2 -->
+<!-- reviewed-through-cli: 0.59.4 -->
 
 # Neo Compose CLI
 

package/skills/neocompose-cli/references/cli-development.md

@@ -101,7 +101,7 @@ wrappers.
 The marker near the top of `SKILL.md` must exactly match the package version:
 
 ```html
-<!-- reviewed-through-cli: 0.59.2 -->
+<!-- reviewed-through-cli: 0.59.4 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale

package/skills/neocompose-cli/references/commands-and-sync.md

@@ -239,13 +239,12 @@ run beneath a `neo.json`. An explicit `--api` takes priority. Outside a
 workspace, they use the CLI build's default API origin. Login prints the
 selected origin before it requests or stores a credential.
 
-`neo doctor` reports two different things. The authoring contracts (format,
-compiler, extension cache, source, files) decide its exit code; the document
-audit below them reports the last pull's malformed records, plus base rows no
-emitted file projects and no record names, and deliberately does not, so a
-project with records still to repair does not fail the command. An unprojected
-row is invisible to `neo status` by construction, which is why `neo doctor` is
-the only place it surfaces.
+`neo doctor` checks authoring contracts (format, compiler, extension cache, source,
+files) and the last pull's document integrity. Malformed records fail the command.
+The partition audit follows ownership: a lookup can reference a value stored in a
+different partition without moving it into the lookup's partition. The document
+audit also reports base rows no emitted file projects and no record names; these
+rows are invisible to `neo status`.
 `neo doctor --json` carries a `repair` entry per finding, which is what a
 targeted repair is handed instead of scanning a project to rediscover them.
 `neo doctor --fix` consumes those entries for the `unprojected-value-row`