@neocompose/cli 0.40.0 → 0.42.0

package/CHANGELOG.md

@@ -1,5 +1,89 @@
 # Changelog
 
+## [0.42.0] - 2026-09-02
+
+### Fixed
+
+- `neo pull --reset` and `neo pull --regenerate-source-names` rewrote every
+  dialogue binding to its type name. Binding names are derived from a value's
+  `Name` child, and the placement index read the pulled rows as stored rather
+  than expanding packed subtree storage first, so a packed `Name` resolved to
+  nothing and `Outpost CaelusAnchorpoint` came back as `Outpost Outpost`. Every
+  linked dialogue and node then showed up as an update in `neo status` whose
+  only difference was the regenerated name. The index now expands packed
+  children into the logical rows they are.
+- `neo pull` left a member declared by more than one class disagreeing with
+  itself. A changed record was rewritten in the single file the emission
+  attributes it to, so a change to a shared member updated one class and
+  froze the others at their previously emitted text, and the next command
+  refused the CLI's own output with "Shared member id … has inconsistent
+  declarations." Pull now rewrites every file that declares a changed record.
+
+### Removed
+
+- `neo migrate rekey`. The canonical value-id migration it served has run on
+  every deployment and the server no longer serves the old-to-canonical
+  mapping page it read, so the command had nothing left to rewrite.
+  `neo migrate` keeps `new | list | check | run | prune`.
+
+## [0.41.0] - 2026-09-01
+
+### Added
+
+- `neo migrate rekey`, the one-time source refactor for the canonical
+  value-id migration. It reads the server's old-to-canonical mapping for the
+  workspace's version, rewrites `@id` pins and `Reference(id: ...)` literals in
+  tracked `.neo` and `.spec.neo` source, and moves `.neo/state.json` bases onto
+  the new ids, so the next `pull` merges field by field instead of reporting
+  every rekeyed value as a delete plus a create. The command refuses to write
+  anything when conflict markers or unresolved pull conflicts remain, when an
+  old id survives outside those two syntactic positions, or when the rewrite
+  introduces a source error. Running it a second time is a no-op.
+- `@distribution(kind: .Sparse | .Packed)` on value-owning member
+  declarations, backed by schema contract 4.1. It chooses whether a member's
+  materialized value keeps its own row or is stored inside its owning parent
+  row.
+- Omitting the annotation is a third state, not a synonym for `.Sparse`: on a
+  root declaration it means the automatic distribution for the member's kind
+  and settings, and on an override it means inherit. Pull emits the annotation
+  only where the field is explicitly stored and never writes an automatic
+  result into source.
+
+- Read packed subtree storage. A `.Packed` child has no record of its own; it
+  is stored as a `{ "~packed": ... }` envelope at its position inside its
+  owning parent's body. The CLI now expands those envelopes into logical value
+  rows when it builds the stored ownership graph, so placements, emitted
+  source, root paths, and `neo check` see a packed child exactly as they see a
+  sparse one. A malformed packed payload now reports its owning row instead of
+  the child disappearing without a diagnostic.
+
+- Push packed subtree storage. Value lowering keeps producing the logical row
+  graph; `neo status` and `neo push` now fold it into the physical rows the
+  server stores, through the same shared fold the server write path runs. A
+  packed child no longer reports a phantom create beside a spurious update of
+  its parent, so `pull` followed by `push --dry-run` of a packed project is
+  clean, and an edit of a packed member is one write of the row that stores it.
+- Converge a sparse project as it is pushed. Rewriting a value row repacks the
+  whole subtree it stores and retires the child records it supersedes, in one
+  push. Rows no push touches keep the residency they already have — nothing
+  rewrites a project that was only pulled.
+
+### Changed
+
+- Reject `@distribution(kind: .Packed)` on a List whose `listKind` is
+  unordered. An unordered list's membership is the set of live rows carrying
+  its id, so its entries occupy no position inside a parent row to be packed
+  into.
+
+### Compatibility
+
+- Project source format stays 4; the schema contract moves 4.0 to 4.1.
+- The wire and `.neo` workspace state keep storing records in their physical
+  form, so merge bases and content hashes are unchanged.
+- A push that edits a value whose member packs now writes the owning row and
+  deletes the child's superseded record, where it previously wrote the child
+  row. Both plans describe the same logical graph.
+
 ## [0.40.0] - 2026-08-30
 
 ### Changed