@neocompose/cli 0.61.5 → 0.62.1

package/package.json

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

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

@@ -59,6 +59,12 @@ Use ordinary `public`, `protected`, `private`, `static`, `virtual`, `abstract`,
 `sealed`, and `override` semantics. A sealed class is an instantiable leaf:
 it may extend another class but cannot be extended, cannot also be abstract,
 and can only be sealed while it has no subclasses. Interfaces are non-generic.
+A read-only override may narrow a class or interface contract to an assignable
+class or derived interface, including a non-null value for a nullable contract.
+Generated Unity C# keeps the inherited property type for Mono compatibility;
+NeoScript sees the narrowed type. Stored implementations of an abstract getter
+remain get-only in generated C#.
+
 Do not put `@id` on inferred list/dictionary type entries or on derived
 structural descriptors.
 
@@ -381,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/neoscript.md

@@ -23,7 +23,7 @@ create `Scripts/<Class>/<Member>.neo` sidecars.
 
 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.
+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.
 
 A body whose whole point is one expression may be written as an expression
 body, `=> expr;`. It is pure sugar for the block form — same compiled
@@ -423,3 +423,5 @@ intent; do not assume an action body is writable merely because it compiled.
 locally, like push. If another commit lands while it runs, the run is refused:
 run it again. `neo loc` writes work the same way: a write refused because
 another commit landed is run again.
+
+VS Code rename follows override families and class constructors, resolves contextual enum options such as `.Success`, and keeps local-variable renames scoped to their declaration. Assigned IDs are not required for these refactorings.

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.