@neocompose/cli 0.81.1 → 0.81.3

package/package.json

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

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

@@ -222,7 +222,10 @@ the class's own parameter, such as `public Bag<T> B = new Bag<T>();`. Such an
 initializer with fields or entries, like `new Bag<T> { N = 3 }`, runs per
 instance, since each instance closes `T` differently. A type
 argument that wraps the parameter, such as `new Bag<List<T>>()`, is rejected.
-Type arguments must satisfy `extends` constraints in bodies too.
+Type arguments must satisfy `extends` constraints in bodies too. A written
+type argument list names every parameter, so `item is Tool<Asset>` is rejected
+when `Tool` declares two. A bare generic name, such as `item is Tool`, stays
+allowed.
 A type argument may be a delegate, such as `Box<NeoDelegate<int, int>>`, but
 not a `NeoAction`, which is never a value.
 
@@ -244,6 +247,9 @@ initializer as its default. Omitted fields remain virtual and resolve through
 the instance's recorded constructor or variant. They track later source-default
 edits until that field is explicitly overridden; resetting an override makes it
 virtual again.
+Editing an inline child preserves the outer construction's call-site values for
+its other fields. The child keeps that construction while its variant selection
+matches; selecting a different variant gives it an independent recipe.
 
 Declare a lookup member as `Reference<T>`. `public Reference<Config> Config`
 selects one row and reads as `Config`. `public Set<Reference<Config>> Configs`
@@ -575,6 +581,12 @@ selection. Constructor arguments and member initializers must select compatible
 targets too. An `NPC` lookup cannot select from `List<Quest>`, even when its
 initializer is typed `NPC`; status reports the conflicting collection annotation.
 
+Generic constructions can nest the same generic class, including through
+collections, such as `Box<Box<int>>` or `Box<List<Box<int>>>`. Each `new` uses
+its own type arguments during first push and stored replay. Editing a nested
+constructor argument rebuilds its projected fields in place, including fields
+stored inside a packed parent; push followed by pull leaves a clean checkout.
+
 Schema export retains a constructed default's generic arguments, including
 nested collection references. For example, a `NeoAnimationClip<ArmPart>`
 default constructs `new NeoAnimationClip<ArmPart>` and its frames reference