@neocompose/cli 0.34.2 → 0.35.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.34.2",
+  "version": "0.35.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.34.2 -->
+<!-- reviewed-through-cli: 0.35.1 -->
 
 # Neo Compose CLI
 
@@ -47,9 +47,8 @@ Treat pull followed immediately by status or dry-run as a semantic no-op. If it
 reports project changes, stop and report a round-trip bug instead of pushing.
 
 The compiler reports file:line:column diagnostics and fails closed. Unknown
-non-null authorable server fields require a CLI contract update; never preserve
-them as opaque JSON or guessed syntax. An unknown top-level document field whose
-value is exactly JSON `null` is treated as absent.
+authorable server fields require a CLI contract update; never preserve them as
+opaque JSON or guessed syntax.
 
 ## Honor hard authoring invariants
 
@@ -198,6 +197,8 @@ AudioClipRegistry AudioClips = new() {
 Use `Images.Sword.Slice(0)` for a sprite and `AudioClips.SwordHit` for audio.
 Renaming the registry symbol, moving the local presentation, or replacing bytes
 retains the file ID.
+Omitting `@settings(template: ...)` uses the complete built-in Unity import
+defaults for that file kind.
 
 ## Resolve conflicts by identity
 

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

@@ -45,9 +45,17 @@ NeoVariant<ExampleObject> Down = new(
   required: it is the only way to construct through the variant.
 - `apply` takes exactly one parameter of the target class and is void. Omit it
   for a variant that is only ever constructed.
-- Both are ordinary delegate closures: parenthesized parameter list, block
-  body, no expression-bodied form. The server compiles them, so authored source
-  carries only the code.
+- Both are ordinary delegate closures: parenthesized parameter list, then
+  either a block body or an expression body. `initialize` returns, so
+  `() => new ExampleObject(.Down)` works; `apply` is void, so its expression
+  body must be a call or an assignment, as in
+  `(source) => source.FacingDir = .Down`. The server compiles them, so authored
+  source carries only the code. Each closure has its own lexical scope, so
+  local names may be reused between `initialize` and `apply`.
+- `overrides` and each child override's `overrides` value are `Partial<T>`
+  deltas over existing instances. They may use inferred `new { ... }` or
+  explicit `new Partial<T> { ... }`, and never pass arguments to or invoke
+  `T`'s constructor—even when `T` has a required constructor.
 
 Folders are records too, declared as their own globals and assigned per
 variant. Nesting is spelled in the path with `/`; intermediate segments are
@@ -346,8 +354,11 @@ node bindings scoped to their node/children. Give each persisted condition use,
 action invocation, mutation, pause, option, and node its own owner-scoped ID.
 
 Use `=> Next` or a trailing block with `return Next;`; do not author a `to:`
-argument. Require destinations for triggers, options, and outcomes. Permit
-terminal text/actions to fall through. Keep all statements for
+argument. A destination arrow always follows an `=` initializer, as in
+`= new(...) => Welcome;`; an arrow that instead follows a member name or a
+parameter list's `)` is a NeoScript expression body, so the two never collide.
+Require destinations for triggers, options, and outcomes. Permit terminal
+text/actions to fall through. Keep all statements for
 `Actions Empty = new();` inside its body.
 
 After editing, run `neo dialogue dryrun <dialogue-ref>`. Exit 1 means the graph

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

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

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

@@ -25,6 +25,41 @@ 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 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
+instructions, same diagnostics, same stored source — and is available on
+getter-only properties, individual accessors, and functions:
+
+```neo
+public bool HasVisited => this.VisitCount > 0;
+
+public int Clamped {
+  get => Math.Clamp(this.Raw, 0, 10);
+  set(int value) { this.Raw = value; }
+}
+
+public bool Unlocked(int level) => this.Level >= level;
+```
+
+The `=>` is only an expression body where it directly follows the member name
+or the parameter list's `)`. An arrow after an `=` initializer is always a
+NeoFlow destination, so `override Trigger Trigger = new(...) => Welcome;`
+keeps its meaning.
+
+In a void context — a `void` function, a setter, or a void delegate — `=> expr`
+is an expression statement rather than a return, so the expression must do
+something: a call such as `void Ping() => this.OnChanged();`, or an assignment
+such as `set(int value) => this.Raw = value;`. An expression whose value would
+simply be discarded is rejected with a diagnostic that names the block body as
+the fix.
+
+`neo push` and `neo pull` canonicalize a stored body to the shorthand when its
+authored spelling is exactly one `return` statement that fits on one line;
+anything else re-emits as a block. Setters always re-emit as blocks. A push
+preserves the form you authored for members it did not otherwise rewrite, so
+choosing longhand for a one-line getter is stable; a fresh `neo pull` writes
+the canonical shorthand.
+
 Declare a bodyless NeoScript contract with `abstract`, for example
 `public abstract bool Equals(Item other);`. Reserve `native` for host-provided
 functions; concrete NeoScript overrides inherit the abstract signature.
@@ -55,6 +90,15 @@ so later changes to the outer binding do not alter the closure. Explicit lambda
 parameter annotations accept the same type grammar as declarations, including
 `decimal`, generic parameters, collections, arrays, and nullable types.
 
+A lambda may use an expression body too: `(x) => x * 2` is the block body
+`(x) => { return x * 2; }`. In a void delegate the expression is a statement,
+so it must call or assign. A dictionary-literal body needs parentheses,
+`() => ({ "a": 1 })`, because a bare `{` after the arrow always opens a block.
+
+```neo
+List<Item> ready = this.Items.Where((item) => item.Count > 0);
+```
+
 Calling `Equals(other)` on a non-null generic value dynamically uses the
 runtime Class's one-argument `Equals` Function or NSFunction when it returns
 `bool`, including the effective override. Values without that member fall back

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

@@ -39,9 +39,7 @@ class Assets {
   };
 
   @id("home-getter-id")
-  static Outpost Home {
-    get { return Assets.Capitol; }
-  }
+  static Outpost Home => Assets.Capitol;
 }
 ```
 
@@ -172,7 +170,8 @@ diff, and dry-run do not rewrite its registry. A successful push creates the
 record, uploads verified bytes, and materializes its declaration and ID.
 
 Edit the typed registry declaration directly when an explicit symbol or
-non-default template is needed before push.
+non-default template is needed before push. With no template annotation, the
+CLI persists the complete built-in Unity defaults for the file kind.
 
 Pull/push compare server-verified SHA-256, not storage ETags. A divergent
 binary keeps local bytes and writes the verified remote side under