@neocompose/cli 0.46.0 → 0.46.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@neocompose/cli",
3
- "version": "0.46.0",
3
+ "version": "0.46.2",
4
4
  "description": "Neo Compose native project-source CLI with bidirectional sync.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -9,7 +9,7 @@ description: >-
9
9
  `@neocompose/cli` or `node cli/bin/neo.mjs` in the neo-compose repository.
10
10
  ---
11
11
 
12
- <!-- reviewed-through-cli: 0.46.0 -->
12
+ <!-- reviewed-through-cli: 0.46.2 -->
13
13
 
14
14
  # Neo Compose CLI
15
15
 
@@ -60,6 +60,11 @@ NeoScript compilation in the browser-safe `@neocompose/neoscript-language`
60
60
  service. Monaco, VS Code, CLI, trusted server, and corpus tooling must consume
61
61
  that shared implementation. Do not add language intelligence to one adapter.
62
62
 
63
+ Keep evaluation and plain project context projection in `src/runtime/`. The CLI,
64
+ server, workers, and editor consume those modules through host lookups; the
65
+ runtime must not import UI state. The runtime boundary and import-cycle checks
66
+ run with `npm run lint:architecture`.
67
+
63
68
  Keep project context refreshable without accumulating stale Monaco providers or
64
69
  LSP state. Preserve diagnostics, completion, hover, signatures, definition,
65
70
  references, rename, symbols, semantic tokens, code actions, and formatting
@@ -83,7 +88,7 @@ wrappers.
83
88
  The marker near the top of `SKILL.md` must exactly match the package version:
84
89
 
85
90
  ```html
86
- <!-- reviewed-through-cli: 0.46.0 -->
91
+ <!-- reviewed-through-cli: 0.46.2 -->
87
92
  ```
88
93
 
89
94
  The quoted version above is checked too, so this instruction cannot go stale
@@ -31,7 +31,9 @@ and managed binaries. Reset retains declaration file grouping already recorded
31
31
  by the workspace, while declarations with no prior placement use the canonical
32
32
  per-declaration layout. Use `--force` only to discard local edits for the server
33
33
  version. Normal pulls persist a transaction cursor and fetch only changed
34
- records; an undo/reset metadata change invalidates the cursor and causes a safe
34
+ records. If the remote head is unchanged, pull preserves the local source
35
+ without compiling it; use `neo status` to inspect local edits and diagnostics.
36
+ An undo/reset metadata change invalidates the cursor and causes a safe
35
37
  full-snapshot fallback.
36
38
 
37
39
  Treat `neo push --dry-run` as a full local commit rehearsal: source emission,
@@ -52,6 +54,11 @@ bodies affected by changed declarations. Use `--force-recompile` with either a
52
54
  dry run or a real push only when diagnosing stale derived IR: it retains the
53
55
  exhaustive project-wide body sweep and is intentionally slower.
54
56
 
57
+ Interactive status, diff, pull, and test commands report workspace loading and
58
+ preparation phases. Spinners continue animating during synchronous compilation;
59
+ `NO_COLOR` removes color without stopping the animation. JSON reporters and
60
+ piped status/test output contain no terminal animation.
61
+
55
62
  Interactive pushes report the active preparation phase before workspace
56
63
  discovery, lowering, compilation, source hashing, and validation begin.
57
64
  A normal push prepares that transport once before confirmation and reuses it