@neocompose/cli 0.25.2 → 0.26.0

package/package.json

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

package/skills/neocompose-cli/SKILL.md

@@ -9,13 +9,14 @@ description: >-
   `@neocompose/cli` or `node cli/bin/neo.mjs` in the neo-compose repository.
 ---
 
-<!-- reviewed-through-cli: 0.25.2 -->
+<!-- reviewed-through-cli: 0.26.0 -->
 
 # Neo Compose CLI
 
 Treat a format-4 `neo/` directory as a Git-like checkout of one Neo Compose
-project version. Native source and the web UI are peer authoring surfaces over
-the same granular records; the server remains the shared source of truth.
+project version. Tracked native source is the CLI authoring source of truth:
+edit it and use `neo push` for schema, values, dialogues, and managed files.
+The web UI remains a peer authoring surface over the shared server records.
 
 Do not look for a C# schema project, Roslyn compiler, authoring DLL, generated
 SDK, `ValueRegistry`, per-member script sidecars, or checked-in dialogue JSON.

package/skills/neocompose-cli/references/animation-and-world-authoring.md

@@ -255,5 +255,5 @@ terminal text/actions to fall through. Keep all statements for
 `Actions Empty = new();` inside its body.
 
 After editing, run `neo dialogue dryrun <dialogue-ref>`. Exit 1 means the graph
-would fail on device. Use `neo dialogue compile '<logic-block-json>'` only for
-low-level inspection or repair of one logic block.
+would fail on device. Keep every dialogue edit in the tracked `.neoflow` source
+and commit it with `neo push`.

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

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

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

@@ -7,7 +7,7 @@ branches, releases, history, and authentication.
 
 - Pull, inspect, and push
 - Conflicts and files
-- Low-level operations
+- Localization operations
 - Branches, releases, and history
 - Authentication and automation
 
@@ -83,44 +83,30 @@ For `base-hash-conflict`, pull and merge. For `version-bump-required`, inspect
 the classification and use `neo push --accept-bump` only when the bump is
 intended.
 
-Inspect and stage files with:
+Add, replace, or remove managed binaries and their typed registry declarations
+in tracked source. `neo push` stages their metadata and verified bytes with the
+source transaction. Keep local bytes during binary conflict resolution and
+inspect the server copy under `.neo/conflicts/files/<file-id>/`.
 
-```sh
-neo files list
-neo files add <path> [--template <Name>]
-```
-
-Keep local bytes during binary conflict resolution. Inspect the server copy
-under `.neo/conflicts/files/<file-id>/`.
+## Localization operations
 
-## Low-level operations
-
-Prefer checked-in source for normal authoring. Use low-level commands only for
-automation, repair, or inspection:
+Main-locale strings are authored in `.neo` and `.neoflow`, but those files do
+not represent the full localization record. Use `neo loc` for other locales,
+statuses, comments, archives, and targeted localization repair:
 
 ```sh
-neo records query [--kind <recordKind>]
-neo records get <kind> <id>
-neo values list [memberId]
-neo values get <valueId>
-neo values set <valueId> '<raw-json-value>'
-neo values bind <staticMemberId> <valueId>
-neo values unbind <staticMemberId>
-neo values create '<raw-json-value>' [--class <classId>] --bind <staticMemberId>
 neo loc locales
 neo loc list
 neo loc set <textId> <locale> "text"
-neo dialogue list
-neo dialogue show <ref>
-neo dialogue compile '<logic-block-json>'
+neo loc status-set <textId> <locale> <statusId>
+neo loc comment-set <textId> <locale> "comment"
+neo loc archive <textId>
+neo loc restore <textId>
 ```
 
-Pass a JSON-array batch on stdin or `--file` where supported so related writes
-remain atomic. A `values set` payload is the raw value, not
-`{ "value": ... }`. Static bind/unbind changes the live binding.
-
-Low-level commands do not rewrite local project source. Run `neo pull` after
-any low-level or web mutation before further source edits or push.
+Pass a JSON-array batch on stdin or `--file` where supported. Localization
+commands do not rewrite local project source. Run `neo pull` after any
+`neo loc` or web mutation before further source edits or push.
 
 ## Branches, releases, and history
 

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

@@ -29,7 +29,6 @@ neo script check --mode nsfunction --member Outpost.RefreshUnlock 'return this.L
 neo script compile --mode nsfunction --member Outpost.RefreshUnlock 'return this.Level > 0;'
 neo script eval --returns string 'return root.Assets.Outposts[0].FullDisplayText;'
 neo script eval --function Outpost.RefreshUnlock --this-value <id> --args '[3]'
-neo script apply --mode action '...'
 ```
 
 Prefer `--json` for automation.
@@ -141,8 +140,8 @@ rolled back.
 ## Evaluation and migrations
 
 `neo script eval` uses authored values and the same evaluator as the web app.
-`neo script apply` previews ordered write intents unless its explicit command
-contract offers a commit mode.
+It reports effects from the isolated evaluation but never commits them. Put
+persistent NeoScript and data changes in tracked source and use `neo push`.
 
 Keep migrations as tracked action files under `Migrations/`:
 

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

@@ -161,8 +161,8 @@ creates a pending file with a provisional deterministic symbol. Status,
 diff, and dry-run do not rewrite its registry. A successful push creates the
 record, uploads verified bytes, and materializes its declaration and ID.
 
-Use `neo files add <path> [--template <Name>]` to scaffold a declaration before
-push when desired.
+Edit the typed registry declaration directly when an explicit symbol or
+non-default template is needed before push.
 
 Pull/push compare server-verified SHA-256, not storage ETags. A divergent
 binary keeps local bytes and writes the verified remote side under