@neocompose/cli 0.46.1 → 0.47.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.46.1",
+  "version": "0.47.0",
   "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.46.1 -->
+<!-- reviewed-through-cli: 0.47.0 -->
 
 # Neo Compose CLI
 

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

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

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

@@ -13,11 +13,15 @@ branches, releases, history, and authentication.
 
 ## Pull, inspect, and push
 
+`neo doctor` fails on malformed records in the last-pulled document. Pull first to audit the current
+head. After a reviewed `neo doctor --fix`, pull and check again.
+
 Use the high-level source workflow:
 
 ```sh
 neo pull
 neo status
+neo doctor
 neo diff
 neo dialogue dryrun <dialogue-ref>
 neo push --dry-run
@@ -31,8 +35,13 @@ and managed binaries. Reset retains declaration file grouping already recorded
 by the workspace, while declarations with no prior placement use the canonical
 per-declaration layout. Use `--force` only to discard local edits for the server
 version. Normal pulls persist a transaction cursor and fetch only changed
-records; an undo/reset metadata change invalidates the cursor and causes a safe
+records. If the remote head is unchanged, pull preserves the local source
+without compiling it; use `neo status` to inspect local edits and diagnostics.
+An undo/reset metadata change invalidates the cursor and causes a safe
 full-snapshot fallback.
+Pull pins every page and snapshot batch to one published generation and logical
+revision. If either changes during assembly, the CLI discards the attempt and
+restarts. Upgrade the CLI together with the P83 server read protocol.
 
 Treat `neo push --dry-run` as a full local commit rehearsal: source emission,
 in-memory pending-ID assignment, transport shapes, hashes, and repeat
@@ -52,6 +61,11 @@ bodies affected by changed declarations. Use `--force-recompile` with either a
 dry run or a real push only when diagnosing stale derived IR: it retains the
 exhaustive project-wide body sweep and is intentionally slower.
 
+Interactive status, diff, pull, and test commands report workspace loading and
+preparation phases. Spinners continue animating during synchronous compilation;
+`NO_COLOR` removes color without stopping the animation. JSON reporters and
+piped status/test output contain no terminal animation.
+
 Interactive pushes report the active preparation phase before workspace
 discovery, lowering, compilation, source hashing, and validation begin.
 A normal push prepares that transport once before confirmation and reuses it
@@ -162,6 +176,9 @@ neo history resume --run <run-id>
 Treat branches as copy-on-write forks and releases as immutable snapshots. The
 server derives the minimum compatibility bump; a caller may only raise it.
 Require the release login profile for release operations.
+Branch creation waits for the durable copy to publish before reporting success.
+The source stays readable while copying; the destination becomes readable only
+after verification and publication.
 
 History rewrites require project owner or admin authority. `prune` and
 `flatten` create immutable plans without deleting anything. `apply` starts the

package/skills/neocompose-cli/references/values-identities-and-references.md

@@ -145,11 +145,18 @@ recipe. Edit members supported by the recorded construction, or delete and
 recreate the value.
 
 Write main-locale text directly in localizable string initializers. Pull/lower
-preserves other locales, comments, statuses, archive state, and unrelated
-localized-text links, including when the initializer is a class member default.
-Do not author localized-text IDs in place of prose. An empty string remains a
-valid authored string value; nullability, not text length, controls whether the
-member is required.
+retargets only the edited assignment. Equal primary-locale text on the same
+declared member shares a localization record across member overrides and
+instances. Different members keep separate translation contexts. Editing a
+class default updates its inheriting instances; editing one instance does not
+change that default. Reverting the instance text to its default restores the
+shared assignment and archives an unreferenced unique text record.
+
+An empty string stores no localization ID. Entering nonempty primary-locale
+text selects or creates the member's shared localization record. Do not author
+localized-text IDs in place of prose. Nullability, not text length, controls
+whether the member is required. Other locales remain translations of their
+linked source record.
 
 ## Managed files