@neocompose/cli 0.68.4 → 0.69.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.68.4",
+  "version": "0.69.0",
   "description": "Neo Compose native project-source CLI with bidirectional sync.",
   "license": "MIT",
   "type": "module",
@@ -41,6 +41,7 @@
     "valibot": "^1.4.2"
   },
   "devDependencies": {
+    "@formatjs/icu-messageformat-parser": "^3.5.21",
     "@neocompose/manifest": "file:../packages/manifest",
     "@neocompose/neoscript-language": "file:../packages/neoscript-language",
     "esbuild": "^0.28.1",

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.68.4 -->
+<!-- reviewed-through-cli: 0.69.0 -->
 
 # Neo Compose CLI
 

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

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

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

@@ -290,13 +290,26 @@ honor both variables.
 Pass explicit project/version IDs and flags in automation. Prefer `--json` for
 machine-readable output and do not depend on interactive pickers or confirms.
 
-## Unity code export
-
-`neo export unity --out <UnityAssetsDir>` writes separate C# files under
-`Scripts/Neo/Generated/`, named after the generated C# types, plus project and localization JSON. It compares
-contents before writing C#, preserves unchanged `.meta` files, removes obsolete
-outputs listed in `NeoGeneratedFiles.json`, and removes the former
-`NeoGeneratedTypes.cs`. Stable identities in the manifest preserve `.meta` GUIDs when types are renamed. Keep the manifest with the generated files.
+## Unity export
+
+`neo export` builds the Unity export from the last pull, offline, and writes it
+into the directories the Unity project's `NeoComposeConfig` asset names:
+`project.json` with a partition index, `Partitions/*.json` holding value rows
+by storage partition, localization files, and generated C# under
+`<generatedTypesDirectory>/Generated/`. It writes only files whose bytes
+changed, skips codegen when only values changed since the last export into
+that Unity project, and writes `Library/NeoCompose/export.json` last for
+Unity to ingest. Local edits are not exported: push and pull them first.
+
+- The Unity project comes from `unityConfigPath`. Without it, an interactive
+  export offers to link the one config asset naming this project; scripts get
+  an error with the line to add.
+- `--unity-project <dir>` exports into another Unity project without linking
+  it. Agent rigs use it.
+- An error diagnostic, or a project file whose bytes differ from the pulled
+  file, stops the export before anything is written.
+- `NeoGeneratedFiles.json` keeps `.meta` GUIDs across type renames. Keep it
+  with the generated files.
 
 ## Push timing diagnostics