@neocompose/cli 0.84.0 → 0.84.2

package/package.json

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

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

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

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

@@ -515,6 +515,15 @@ Do not default parameters of deferred functions, delegates, actions,
 closures, or overrides. Enum defaults store the option id, so renaming the
 option changes the emitted `.Option` spelling without a record change.
 
+Editing a stored object's constructor arguments rebuilds it under the same
+identity. Initializers that read that object, including collection projections,
+wait for its replacement before evaluating its members.
+
+Stored objects created with an implicit constructor may have required fields
+settled in their object body. Keep that body when editing initializer behavior
+or adding a parameterless constructor; an empty stored argument list does not
+require inventing constructor arguments.
+
 ## Required constructors and settlement
 
 Put one required constructor on the class header when the entire class body

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

@@ -24,6 +24,15 @@ Keep computed getters, setters, functions, dialogue logic, group logic, and
 constructors inline in their owning `.neo` or `.neoflow` declaration. Do not
 create `Scripts/<Class>/<Member>.neo` sidecars.
 
+Explicit constructions such as `new MissingClass(5)` require a declared type,
+including inside stored object initializers, constructor arguments, and collections.
+The editor reports an unresolved class at its type name and refreshes the diagnostic
+when the declaration changes. Contextual `new(...)` still uses the expected type.
+
+If resolving a stored reference encounters an invalid initializer elsewhere,
+the diagnostic points to that initializer's authored file and position. Fix the
+reported initializer; a valid downstream `Reference(...)` is not the error site.
+
 Declare a setter's value type explicitly with the canonical form
 `set(int value) { ... }`. Project analysis, candidate materialization, and
 focused script commands all use the same accessor extraction. A property can have at most one getter and one setter. Concrete setters need a body (an empty body is a valid no-op); typed setters must use the property type and the parameter name `value`. Abstract and interface properties declare bodyless accessor contracts.
@@ -103,6 +112,18 @@ A generic receiver may call methods from its class or interface constraint,
 including void calls used as statements. Generic arguments substitute through
 the constraint; nullable receivers still require narrowing or null handling.
 
+Runtime `is` tests on generic values check whether the bound can overlap the
+tested type. A class bound need not implement an interface itself when a
+subclass can implement it. A successful pattern binding exposes that interface's
+members, including after `if (item.Data is not IReceiver receiver) continue;`.
+Sealed classes without the interface and unrelated class bounds remain disjoint.
+
+An interface guard also narrows the original receiver without a pattern binding.
+After `if (item is not IReceiver) continue;`, `item` exposes both its declared
+class members and `IReceiver` members. The same applies to guards that return,
+throw, or break. Reassignment clears the proof, and paths that did not pass the
+guard cannot use it.
+
 Functions, natives and interface functions can declare their own type
 parameters after the name, each with an optional constraint and default: