@neocompose/cli 0.48.3 → 0.50.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.48.3",
+  "version": "0.50.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.48.3 -->
+<!-- reviewed-through-cli: 0.50.0 -->
 
 # Neo Compose CLI
 

package/skills/neocompose-cli/references/animation-and-world-authoring.md

@@ -24,6 +24,29 @@ For world layer links, derive a concrete project class from
 `targetLayer` relation. Do not add value-level target metadata or ask painting
 operations to create/repair relation targets.
 
+## Tile placements
+
+Use `@tile(VoidTile)` on a `NeoTileInstance` construction to select its tile
+class. The named spelling `@tile(asset: VoidTile)` is equivalent; the asset is
+required and only the argument label is optional.
+
+```neo
+@tile(VoidTile)
+new NeoTileInstance() {
+  Cell = new(9, -4)
+}
+```
+
+Pull emits the positional spelling. The annotation writes the placement's
+`assetClassId` metadata and does not construct a tile value or add a generic
+argument. The asset must be a concrete, non-generic descendant of `NeoTile`.
+Use the annotation on persisted literal constructions; executable NeoScript
+and evaluated placement constructors reject it.
+The grid's imports and the tile's compatible-layer relations still constrain
+where the placement can be used. Existing placement overrides remain attached
+when the selected asset is unchanged; recreate a placement to change its asset
+when it has overrides or a variant.
+
 ## Object variants
 
 A variant is a named configuration of one `NeoObject`-derived class: how to

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

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

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

@@ -136,11 +136,14 @@ member creates a sparse override with its deterministic projected ID; removing
 that member from an existing initializer resets the override and resumes source
 tracking. Require either transition to appear in `neo diff`.
 
-A concrete generic argument can carry a default that its type spelling does
-not show. Pull writes nonlocalized scalar and empty aggregate binding defaults at implicit
-construction sites, for example `DefaultData = new()`. Keeping that expression
-unchanged or omitting it retains the virtual default; editing it creates an
-override. A default that selects a subtype keeps the explicit subtype name.
+Generic arguments specify types, not default values. A required generic member
+must be supplied at construction unless its member declaration or an inherited
+member declaration supplies a default. Missing required members are compile
+errors. Pull preserves incomplete stored objects for repair; add the missing
+initializer or declare the intended member default before testing or pushing.
+An override without a local initializer inherits an available base member
+default, including when its stored `defaultValue` carrier is null. An explicit
+`= null` initializer is a literal nullable default, not an inheritance marker.
 
 Editing an initializer updates sparse override rows in place: projected member
 IDs remain stable, and omitted virtual rows are never emitted as authored seed