@neocompose/cli 0.74.0 → 0.75.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.74.0",
+  "version": "0.75.1",
   "description": "Neo Compose native project-source CLI with bidirectional sync.",
   "license": "MIT",
   "type": "module",
@@ -36,6 +36,7 @@
   "dependencies": {
     "@inquirer/prompts": "^8.7.3",
     "convex": "^1.46.0",
+    "editorconfig": "^3.0.2",
     "fflate": "^0.8.3",
     "ignore": "^7.0.12",
     "valibot": "^1.5.0"
@@ -46,7 +47,9 @@
     "@neocompose/neoscript-language": "file:../packages/neoscript-language",
     "esbuild": "^0.28.2",
     "prettier": "^3.9.9",
-    "uuid": "^14.0.2"
+    "uuid": "^14.0.2",
+    "@neocompose/models": "file:../packages/models",
+    "@neocompose/neoscript-runtime": "file:../packages/neoscript-runtime"
   },
   "repository": {
     "type": "git",

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.74.0 -->
+<!-- reviewed-through-cli: 0.75.1 -->
 
 # Neo Compose CLI
 
@@ -299,3 +299,14 @@ Before a real push, report the files changed, the relevant `neo diff`, dialogue
 dry-run results when applicable, and `neo push --dry-run`. Do not claim success
 from parsing alone when construction, reference membership, runtime ownership,
 or server verification is involved.
+
+## Formatting
+
+The CLI and VS Code extension share NeoScript formatting and read `.editorconfig`
+for `.neo` and `.neoflow` files. Set `indent_style`, `indent_size`, `end_of_line`,
+and `insert_final_newline` there to keep regenerated source consistent with your
+editor. Defaults are two spaces, LF, and a final newline. Push preserves authored
+text when regeneration has the same tokens; pull preserves semantically unchanged
+files. Formatting-only body or source-location changes do not create a subsequent
+push; real code and string-content edits still do. Formatting preferences belong
+to the checkout, not stored script bodies.

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

@@ -76,10 +76,17 @@ NeoScript compilation in the browser-safe `@neocompose/neoscript-language`
 service. Monaco, VS Code, CLI, trusted server, and corpus tooling must consume
 that shared implementation. Do not add language intelligence to one adapter.
 
-Keep evaluation and plain project context projection in `src/runtime/`. The CLI,
-server, workers, and editor consume those modules through host lookups; the
-runtime must not import UI state. The runtime boundary and import-cycle checks
-run with `npm run lint:architecture`.
+Resolve disk formatting through the Node-only `node-format-options` entrypoint
+and `.editorconfig`; keep filesystem configuration out of browser imports.
+Format regenerated source before compiling it so cached source ranges match
+the written files. Preserve authored source when a push changes no source tokens.
+
+Keep evaluation in `@neocompose/neoscript-runtime` and shared schema/value
+contracts in `@neocompose/models`. Models depend on language and manifest;
+runtime depends on those packages. App context projection, database adapters,
+and reactive hosts remain in the app. Packages must not import host code.
+Boundary and import-cycle checks run with `npm run lint:architecture`;
+`npm run test:runtime-package` checks a standalone custom database host.
 
 Keep project context refreshable without accumulating stale Monaco providers or
 LSP state. Preserve diagnostics, completion, hover, signatures, definition,
@@ -97,8 +104,9 @@ forking it in the CLI. The server still verifies a push's uploaded
 project-file bytes, and web editor commits use the shared client preparation protocol.
 Unrelated source files are not uploaded or recompiled on every push.
 Optional source maps missing from valid stored bodies do not request a backfill.
-Existing map changes still refresh locations on push; authored edits, dependency
-changes, and explicit forced recompilation retain their normal compile scope. A CLI lowering mismatch on a normal push is exposed by the next
+Formatting-only source location changes do not create pushes, including when
+other records change. Evaluation maps the current local layout; authored edits,
+dependency changes, and explicit forced recompilation retain their normal compile scope. A CLI lowering mismatch on a normal push is exposed by the next
 canonical pull; `neo push --dry-run` remains the complete source-to-record
 rehearsal.
 
@@ -118,7 +126,7 @@ wrappers.
 The marker near the top of `SKILL.md` must exactly match the package version:
 
 ```html
-<!-- reviewed-through-cli: 0.74.0 -->
+<!-- reviewed-through-cli: 0.75.1 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale

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

@@ -557,7 +557,8 @@ receiver.Handler`; use `-=` to remove the same receiver/handler pair. Handlers
 are noncapturing, return void, and accept the field's type. Bindings to Session
 receivers stay Session-only. Gameplay hosts dispatch after the write batch.
 Authoring, replay, migration, and dialogue dry-run hosts retain wiring without
-invoking callbacks.
+invoking callbacks. `owner.Field.OnChanged.Clear()` removes every handler,
+including `@listeners` defaults, in both Save and Session wiring.
 
 Instance getters take the same syntax, for example
 `this._quantity.Value.OnChanged += this.QuantityChanged`. A getter
@@ -566,7 +567,8 @@ function, effect, lifecycle hook, or dialogue action, never a constructor,
 initializer, or migration. Subscribing reads the getter once. The SDK calls the
 handler with a fresh result whenever something that read depended on changes,
 even if the result is equal, and several changes before the next read call it
-once. Static getters, `base.Value`, and `@listeners` can't observe a getter.
+once. `Clear()` ends the subscription, and a constructor can't call it on a
+getter. Static getters, `base.Value`, and `@listeners` can't observe a getter.
 `neo test` dispatches getter subscriptions the same way, treating the test body
 as the host: handlers run after each of its statements, so the next statement
 sees their effects. A getter that reads through `Clone()` or a grid query can