@neocompose/cli 0.39.0 → 0.41.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.39.0",
+  "version": "0.41.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.39.0 -->
+<!-- reviewed-through-cli: 0.41.0 -->
 
 # Neo Compose CLI
 

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.39.0 -->
+<!-- reviewed-through-cli: 0.41.0 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale

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

@@ -86,6 +86,15 @@ Use context-aware typed annotations:
 - Stateful settings use contextual enum cases, such as
   `@settings(format: .Plain)` and `@settings(selection: .Multi)`.
 - `@relations(...)` only on the source class of a specialized direct relation.
+- `@distribution(kind: .Sparse | .Packed)` only on a value-owning member
+  declaration or override. It chooses whether the member's value keeps its
+  own row (`.Sparse`) or is stored inside its owning parent's row (`.Packed`).
+  Omit it unless the choice must be explicit: on a root declaration absence
+  means the automatic distribution for the member's kind and settings, and on
+  an override it means inherit. `pull` writes the annotation only where it is
+  explicitly stored. A packed subtree shares its parent's document-size limit,
+  so a write that would exceed the hard limit fails instead of falling back.
+  `.Packed` is rejected on a List whose `listKind` is unordered.
 
 Use numeric literals for numeric limits. Keep annotations separate instead of
 inventing a generic metadata bag.

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

@@ -329,5 +329,15 @@ neo migrate run [--dry-run] [--skip-invalid]
 neo migrate prune
 ```
 
+`neo migrate rekey` is different: a one-time source refactor, not an action.
+After the server's canonical value-id migration, it reads the version's
+old-to-canonical id mapping, 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. It writes nothing
+while conflict markers or unresolved pull conflicts remain, when an old id
+survives outside those two positions, or when the rewrite would introduce a
+source error. A second run is a no-op.
+
 Run checks before migration execution. Review storage ownership and every write
 intent; do not assume an action body is writable merely because it compiled.