@neocompose/cli 0.62.0 → 0.62.2

package/package.json

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

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

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

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

@@ -314,3 +314,17 @@ CLI pins the deployment through the authenticated app origin before sending it
 a session token.
 Results pin the workspace to that transaction's hash, so a concurrent later commit still
 requires a pull before another push.
+
+## Test execution
+
+`neo test` compiles unpushed production source and validates the candidate graph.
+It does not perform the additional source serialization round trip that
+`neo push --dry-run` uses. Invalid production source still stops test execution.
+Unchanged project and spec inputs reuse content-addressed local caches.
+
+Spec files run in parallel using up to four available CPU workers. Set
+`test.maxWorkers` in `neo.json`, override it with `neo test --maxWorkers <n>`,
+or use `neo test --runInBand` to run serially. Each file preserves hook and test
+order; fixtures and mocks stay isolated. Reports retain discovery order.
+Parallel test work is summed across workers and can exceed elapsed execution;
+JSON `timings.executeMs` and `timings.workerStartupMs` give elapsed phase times.

package/skills/neocompose-cli/references/declarations-and-construction.md

@@ -387,3 +387,8 @@ class PlacedItem<
 ```
 
 Executable object initializer blocks can set immutable stored members on the newly constructed instance, including nested `new` expressions. Ordinary assignments after construction remain subject to storage restrictions. `readonly` declarations still change only through class defaults.
+
+Populated unordered member defaults, such as `@settings(kind: .Unordered)` with
+`List<Entry> Entries = [new Entry()]`, are constructed by an initializer for
+each instance. A declaration has no container value row to own unordered entries.
+Nested unordered lists already have container rows and retain their stored values.

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

@@ -131,7 +131,9 @@ assignability, collection membership, multiplicity, and group constraints.
 
 `collectionValue` references follow the same post-push resolution and
 membership rules as member defaults. Name the collection itself, for example
-`Reference(root.Assets.Quests.Daily)`. A path may traverse construction defaults
+`root.Assets.Quests.Daily` or `Reference(root.Assets.Quests.Daily)`. Invalid
+reference-valued settings are errors; they never silently remove the binding.
+A path may traverse construction defaults
 and declarations created in the same push. Preparation materializes the target
 collection and its required ancestor rows together, preserving the virtual
 identities. No preliminary push or manual value ID is needed.