@neocompose/cli 0.62.1 → 0.63.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.62.1",
+  "version": "0.63.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.62.1 -->
+<!-- reviewed-through-cli: 0.63.0 -->
 
 # 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.1 -->
+<!-- reviewed-through-cli: 0.63.0 -->
 ```
 
 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

@@ -105,6 +105,12 @@ Use context-aware typed annotations:
   explicitly stored. A packed subtree shares its parent's document-size limit,
   so a write that would exceed the hard limit fails instead of falling back.
   `.Packed` is rejected on a List whose `listKind` is unordered.
+- `@effect` only on a class member function. The Unity runtime runs it for
+  every live instance and reruns it whenever data it read changes; the web
+  editor, `neo test`, and dry runs never run effects. It must be an immediate,
+  parameterless `void` instance function with a NeoScript or abstract body.
+  An override without the annotation inherits; `@effect(kind: .None)` stops
+  an inherited effect. Use it instead of polling or relaying changes by hand.
 
 Use numeric literals for numeric limits. Keep annotations separate instead of
 inventing a generic metadata bag.