@neocompose/cli 0.12.0 → 0.14.0

package/CHANGELOG.md

@@ -1,5 +1,77 @@
 # Changelog
 
+## [0.14.0] - 2026-07-28
+
+### Added
+
+- Stamp authored provenance on every row a materialized default produces.
+  Writing `new EyePart { Name = "RightEye" }` as a row in `EyesPart.Children`
+  copies `EyePart`'s default graph, and until now the copy had no link home:
+  a clip declared on `EyePart` addresses `EyePart`'s own class-default rows,
+  which no copy of them named, so it resolved on no nested instance at all.
+  Each copied row now carries the class-default row it came from, forwarding
+  that row's own stamp so a part three levels deep still points at the
+  original rather than an intermediate copy. Clips on nested class rows
+  resolve, at any depth, and the Unity exporter chains the stamp through a
+  placement unchanged. `neo pull` output is byte-identical either way.
+
+### Fixed
+
+- Push two sibling bare `new()` rows of a class whose default is row-backed.
+  Re-lowering a declared initializer adopted the `@id` written on it as the
+  copy's identity — which is the class-default row's id — so
+  `[new EyePart(), new EyePart()]` minted one id twice and failed with
+  `Value construction reuses identity`, and even a single such row was
+  rejected by the server as an existing value. That id is now the copy's
+  provenance instead of its identity.
+- Keep `genericBindings` and `bindingMembers` on an authored seed row across
+  the push transport. The schema commit route rebuilt each seed from a field
+  whitelist that omitted both, so an authored `NeoAnimationChildOverride` row
+  lost its concrete generic environment between the CLI and the server's own
+  re-lowering, and the push failed as a trusted-lowering mismatch.
+
+### Removed
+
+- The nested-clip-owner advisory added in 0.12.0, along with the `warnings`
+  array `neo push --json`, `neo status --json` and `neo diff --json` carried
+  it in. It described a defect that provenance now fixes, so leaving it would
+  warn on correct code.
+
+## [0.13.0] - 2026-07-28
+
+### Added
+
+- Author a single field of a structured leaf member inside an animation
+  override graph. P42 gives `SpriteInfo`, `Vector2`, `Vector2Int`, `Vector3`,
+  `Vector3Int` and `Color` a named field surface — `FileId`/`SliceIndex`,
+  `x`/`y`/`z`, `r`/`g`/`b`/`a` — and a frame's `Overrides` can now name one of
+  them: `Sprite = new { SliceIndex = 2 }` animates the slice while the sheet
+  stays whatever the played instance holds, and `Position = new { y = 0.5 }`
+  leaves `x` and `z` alone. The explicit `new Partial<SpriteInfo> { ... }` form
+  is accepted alongside the inferred `new { ... }`, matching how a class
+  override already reads, and an empty `new { }` still means no change.
+- Accept a bare `Images.<Name>` in a `FileId` field position. It is the one
+  place a sprite file is named without a slice; as a whole sprite value it is
+  still rejected in favour of `Images.<Name>.Slice(index)`.
+
+### Changed
+
+- Reject a non-integer component of a `Vector2Int` or `Vector3Int` in source,
+  naming the member and the field. `new(0.5, 0.5)` used to lower unchecked and
+  fail later at commit against a server guard, which reported the record rather
+  than the line that wrote it.
+- Reject `new { ... }` for a structured leaf outside an animation override
+  graph — a member declaration default, or a top-level value binding — instead
+  of accepting a partial value in a position that can never be composed with
+  anything.
+
+### Fixed
+
+- Stop emitting the literal text `null` for a sprite value that carries no
+  `fileId`. Now that a sprite field can be overridden on its own, a `neo pull`
+  of such a value wrote source that the next `neo push` read as a deletion of
+  the override.
+
 ## [0.12.0] - 2026-07-28
 
 ### Added