@neocompose/cli 0.62.2 → 0.64.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.62.2",
+  "version": "0.64.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.2 -->
+<!-- reviewed-through-cli: 0.64.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.2 -->
+<!-- reviewed-through-cli: 0.64.0 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale

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.

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

@@ -131,10 +131,16 @@ so it must call or assign. A dictionary-literal body needs parentheses,
 List<Item> ready = this.Items.Where((item) => item.Count > 0);
 ```
 
+`==`, `!=`, `Contains`, `IndexOf`, and `Remove` compare Class, interface,
+List, Set, and Dictionary values by identity: two reads of one stored value are
+equal, and two values with identical fields are not. Primitives, enums,
+vectors, and media references compare by value. The static type decides, so an
+unconstrained generic `T` compares by value.
+
 Calling `Equals(other)` on a non-null generic value dynamically uses the
 runtime Class's one-argument `Equals` Function or NSFunction when it returns
 `bool`, including the effective override. Values without that member fall back
-to ordinary NeoScript equality.
+to value equality.
 
 Object initializers are available in method bodies and `.spec.neo` tests:
 
@@ -240,7 +246,7 @@ other collection callbacks.
 
 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`.
+the same 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