@neocompose/cli 0.71.2 → 0.71.4

package/package.json

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

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

@@ -497,3 +497,41 @@ project candidate, including new dialogues and pending schema or value changes,
 without fetching or committing server content. Exit 1 means the graph
 would fail on device. Keep every dialogue edit in the tracked `.neoflow` source
 and commit it with `neo push`.
+
+### Dialogue group names and local symbols
+
+Use `DialogueGroup QuestUnlocks = new(kind: .Standard, parent: Quests, name: "Unlocks")`
+when the local identifier should differ from the record's display name. Omitting
+`name` uses the identifier. Unity generates its dialogue API from the stored
+name (`Quests.Unlocks`), independently of the local identifier. Pull, force-pull,
+and reset retain the local identifier and authored file path by `@id`; a remote
+rename updates the `name:` argument.
+
+Trigger groups accept both `group: QuestUnlocks.Medium` and
+`group: Quests.Unlocks.Medium`. Qualified paths use the group's display name
+converted to an identifier; priority options use their declared names.
+Completion, hover, navigation, and diagnostics resolve both forms. Sibling
+groups that produce the same path segment require their distinct local aliases.
+
+### NeoFlow display names
+
+For `Text`, `Actions`, `Conditions`, `Option`, and `Outcome`, omitting `name:`
+infers the label from a custom authored symbol. `Option Accept = new()` gets
+label `Accept`, regardless of its prose. Dialogue classes use the same rule
+when `@settings(name: ...)` is omitted.
+
+Generated symbols such as `Text1`, `Actions2`, `Option1_2`, `Outcome1`, and the
+identity-based `Node_...` forms stay unlabeled for their corresponding kinds.
+A symbol from another kind is custom: `Option Text1` gets label `Text1`.
+Explicit names win, including
+`name: ""` for clearing a label, or `name: null` on optional graph labels. Dialogues and outcomes store
+an empty string for an unset label; optional graph labels store null. Pull
+writes explicit empty overrides where omission would otherwise infer a name,
+and omits a redundant label equal to the inferred symbol.
+
+The fixed `Trigger` member does not infer a label. Reusable condition and action
+functions keep their function identifiers as `sourceFunctionName`; they have
+no separate display-name field or `name:` constructor. Rename the function
+and its uses to change that source name. Linked-value aliases likewise retain
+their `sourceName`. These names never come from prose, and the naming rule does
+not change IDs, destinations, or condition/action use identities.

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

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

package/skills/neocompose-cli/references/commands-and-sync.md

@@ -37,6 +37,9 @@ declarations with no prior placement use the canonical per-declaration layout. U
 version. Normal pulls persist a transaction cursor and fetch only changed
 records. If the remote head is unchanged, pull preserves the local source
 without compiling it; use `neo status` to inspect local edits and diagnostics.
+Pull ignores records whose hashes already match the saved server baseline,
+including echoes of this checkout's last push, and advances its cursor without
+compiling or rewriting source. Later remote edits still count as changes.
 An undo/reset metadata change invalidates the cursor and causes a safe
 full-snapshot fallback.