@neocompose/cli 0.61.2 → 0.61.4

package/package.json

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

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

@@ -219,6 +219,10 @@ qualified static, or reached through a stable root path. For example,
 `protected int Slots = FeatureFlags.StartInventorySize;` evaluates the current
 static field or getter whenever a new instance is constructed; it is not baked
 into a persisted literal during push.
+Root paths such as `root.Save.World.Time.Year` remain executable even when
+`World` and `Time` exist only through construction defaults. This also applies
+inside `new() { Year = root.Save.World.Time.Year }`: the child field retains
+its initializer and reads the root when the instance is constructed.
 
 Declare overloadable constructors as members when each constructor body owns
 its parameter scope:

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

@@ -158,6 +158,11 @@ chain, so `config.Hat?.Head.Idle.Down.Frames` safely returns null when `Hat` is
 null. A descendant that is itself nullable still needs its own `?.`, `??`, `!`,
 or narrowing guard before the next access.
 
+Inside an instance body, `Member` and `this.Member` share null and type-check
+narrowing. A local or parameter named `Member` shadows the implicit member;
+`this.Member` still names the instance field. Reassigning a narrowed path to a
+nullable value clears its non-null fact.
+
 Treat lookup-return values with the same nullable narrowing rules.
 
 Runtime declaration patterns follow the possible runtime type, not only the

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

@@ -130,7 +130,11 @@ the edit is not a target, and lookup/dialogue references must still satisfy
 assignability, collection membership, multiplicity, and group constraints.
 
 `collectionValue` references follow the same post-push resolution and
-membership rules as member defaults.
+membership rules as member defaults. Name the collection itself, for example
+`Reference(root.Assets.Quests.Daily)`. 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.
 
 ## Defaults and localization