@neocompose/cli 0.75.0 → 0.75.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.75.0",
+  "version": "0.75.2",
   "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.75.0 -->
+<!-- reviewed-through-cli: 0.75.2 -->
 
 # Neo Compose CLI
 
@@ -299,3 +299,15 @@ 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, including stored initializer recipes, computed member defaults, and inline
+constructor delegates; 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,12 @@ 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. Stored initializer recipes, computed member defaults, and
+inline constructor delegates preserve their pulled code and compiled bodies when
+source tokens are unchanged. String-literal content remains significant.
+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 +129,7 @@ wrappers.
 The marker near the top of `SKILL.md` must exactly match the package version:
 
 ```html
-<!-- reviewed-through-cli: 0.75.0 -->
+<!-- reviewed-through-cli: 0.75.2 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale

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

@@ -446,3 +446,28 @@ A lookup's declared class must be assignable to the entry class of its
 selection. Constructor arguments and member initializers must select compatible
 targets too. An `NPC` lookup cannot select from `List<Quest>`, even when its
 initializer is typed `NPC`; status reports the conflicting collection annotation.
+
+Schema export retains a constructed default's generic arguments, including
+nested collection references. For example, a `NeoAnimationClip<ArmPart>`
+default constructs `new NeoAnimationClip<ArmPart>` and its frames reference
+`List<NeoAnimationFrame<ArmPart>>`.
+
+When a construction leaves a required member unsettled, CLI diagnostics point to
+`new` and include the member declaration as a related location. Fix that
+construction before pushing. Valid root initializers still participate in
+reference checking, so an unrelated root error does not imply their values are
+missing or deleted. Independent reference errors remain visible.
+
+Object initializer assignments use commas. The last comma is optional; the
+semicolon terminating the enclosing declaration is valid:
+
+```neo
+AudioSettings AUDIO_SETTINGS = new() {
+  Main = new AudioMixerGroupSettingsFolder("Main", "Master", "MasterVolume", []),
+};
+```
+
+A semicolon after `Main = ...` inside the initializer is invalid. Editor and CLI
+diagnostics highlight that separator in the authored file, including global,
+static member, and protected root initializers. Statement semicolons inside
+function or delegate bodies remain valid.