@neocompose/cli 0.60.2 → 0.61.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.60.2",
+  "version": "0.61.1",
   "description": "Neo Compose native project-source CLI with bidirectional sync.",
   "license": "MIT",
   "type": "module",
@@ -17,8 +17,8 @@
     "access": "public"
   },
   "scripts": {
-    "contract:generate": "node schema-contract/generate.mjs",
-    "contract:check": "node schema-contract/generate.mjs --check",
+    "contract:generate": "node ../packages/manifest/schema-contract/generate.mjs",
+    "contract:check": "node ../packages/manifest/schema-contract/generate.mjs --check",
     "fixtures:update": "node schema-contract/generate-corpus-fixtures.mjs",
     "fixtures:check": "node schema-contract/generate-corpus-fixtures.mjs --check",
     "build": "npm run build:local",

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.60.2 -->
+<!-- reviewed-through-cli: 0.61.1 -->
 
 # Neo Compose CLI
 

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

@@ -390,6 +390,21 @@ let the last write win.
 
 ## NeoFlow dialogues
 
+Lookup dialogue groups use the same collection paths as lookup members:
+
+```neo
+DialogueGroup FishingVictory = new(
+  kind: .Lookup,
+  collection: Assets.FishEncounters,
+  collectionValue: Reference(root.Assets.FishEncounters),
+);
+```
+
+The collection member and its value may be created in the same push without
+explicit IDs. Pull emits readable paths when the collection has a stable root
+path. Raw `Reference<Member>(id: "...")` and `Reference(id: "...")` forms remain
+readable, and values without a root path retain the ID form.
+
 Node and option prose lowers to localized-text records with canonical node or
 choice backlinks. Existing translations and unrelated localization links are
 preserved when the source is pushed.

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

@@ -53,8 +53,17 @@ authoring capability. P52's document header still says proposed, but try/catch
 shipped in CLI 0.18; implementation and parity tests take precedence over that
 stale header.
 
+CLI 0.61 adds `while` and `do / while` loops, ordinal string `Replace`,
+ordered-list `Insert`, and method calls whose results may be discarded.
+See the [NeoScript reference](neoscript.md) for authoring syntax and limits.
+
 ## Shared implementation contract
 
+Manifest contracts, document comparison, normalization, and three-way merge
+live in `packages/manifest`. Contract generation and its registry live in
+`packages/manifest/schema-contract`. Web, backend, and CLI consumers import
+`@neocompose/manifest`; production application code must not import CLI internals.
+
 The CLI uses plain document snapshots and shared runtime functions. Keep Retree and web view models out of its imports. The headless architecture check follows CLI imports, and `cli/build.mjs` rejects UI modules and packages in the actual bundle metadata.
 
 Keep parsing, strict resolution, formatting, diagnostics, symbols, and
@@ -80,7 +89,7 @@ compiler revision and re-checks the head, authorization, row shapes, and CAS
 bases. A modified CLI can therefore write bad rows to a project its user may
 already write; keep preparation in shared `src/database` code rather than
 forking it in the CLI. The server still verifies a push's uploaded
-project-file bytes, and web editor commits still prepare on the server.
+project-file bytes, and web editor commits use the shared client preparation protocol.
 Unrelated source files are not uploaded or recompiled on every push. A CLI lowering mismatch on a normal push is exposed by the next
 canonical pull; `neo push --dry-run` remains the complete source-to-record
 rehearsal.
@@ -101,7 +110,7 @@ wrappers.
 The marker near the top of `SKILL.md` must exactly match the package version:
 
 ```html
-<!-- reviewed-through-cli: 0.60.2 -->
+<!-- reviewed-through-cli: 0.61.1 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale

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

@@ -82,6 +82,16 @@ neo script eval --returns string 'return root.Assets.Outposts[0].FullDisplayText
 neo script eval --function Outpost.RefreshUnlock --this-value <id> --args '[3]'
 ```
 
+Method calls may be used as statements even when they return a value. The
+runtime evaluates the call and discards the result. This also applies to
+collection methods, delegates, actions, and fluent calls:
+
+```neo
+this.TryRefresh();
+this.Items.Insert(0, item);
+this.Items.Remove(item);
+```
+
 Prefer `--json` for automation.
 
 `neo script check --all` reconstructs the prospective project entirely from
@@ -198,6 +208,17 @@ enum, parameter, or local may shadow it. Qualified members use their owner's
 namespace and may be named `Math`; access one as `this.Math` or
 `SomeValue.Math` without colliding with the builtin qualifier.
 
+## String builtins
+
+Use `text.Replace(search, replacement)` to return a string with every
+non-overlapping occurrence replaced. Matching is ordinal and case-sensitive.
+The search must be nonempty; an empty search throws an error. Neither argument
+may be null. The receiver stays unchanged.
+
+```neo
+return "banana".Replace("a", "o"); // "bonono"
+```
+
 ## Collection builtins
 
 Lists expose their size as either `items.Count` or `items.Count()`. Use
@@ -210,6 +231,10 @@ Use `items.IndexOf(value)` to return the zero-based index of the first equal
 list entry, or `-1` when the value is absent. `IndexOf` is list-only and uses
 the same value/reference equality as `Contains`.
 
+Use `items.Insert(index, value)` to insert an entry into a writable ordered
+list. The index may range from zero through `items.Count`; the count appends
+the entry. Other indices throw an error. `Insert` returns void.
+
 Use `List.Repeat(value, count)` to build a list of `count` copies of a value
 instead of hand-counting a literal or looping around `Add`:
 
@@ -298,7 +323,22 @@ Use `break` for the nearest loop or switch and `continue` for the nearest
 loop. A `continue` inside a switch nested in a loop continues the loop.
 
 All nested loops and called NeoScript bodies share a 10,000-iteration budget.
-Do not use or teach `while` or `do`; they are not supported.
+A `while` loop checks its boolean condition before each iteration. A
+`do / while` loop runs its body once before checking the condition. Both
+require braces; the `do / while` condition ends with a semicolon.
+
+```neo
+while (this.HasWork()) {
+  this.ProcessNext();
+}
+
+do {
+  this.ProcessNext();
+} while (this.HasWork());
+```
+
+`continue` checks the condition again in both loops. Each executed body counts
+against the shared iteration budget.
 
 ## Switch