@neocompose/cli 0.21.5 → 0.22.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.21.5",
+  "version": "0.22.0",
   "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.21.5 -->
+<!-- reviewed-through-cli: 0.22.0 -->
 
 # Neo Compose CLI
 
@@ -30,7 +30,7 @@ Those are not part of format 4.
    existed before the task began.
 4. Run `neo dialogue dryrun <ref>` after dialogue changes.
 5. Run `neo push --dry-run` before every real push. It performs the full local
-   bundle, ID-assignment, transport-shape, hash, and repeat-verification path,
+   source emission, ID-assignment, transport-shape, hash, and repeat-verification path,
    then rehearses the server's preparation phase — schema-commit
    materialization and whole-graph validation — against the pulled document,
    without prompting, uploading, committing, or rewriting the checkout.
@@ -51,7 +51,7 @@ opaque JSON or guessed syntax.
 - Preserve existing `@id` annotations through rename, reorder, and file moves.
 - Do not add a second `@id` to a root or static member initializer. The member
   ID owns that stored binding. Nested class/list rows still carry their own IDs.
-- Treat `.neo/` as private state and the source bundle as the authorable input.
+- Treat `.neo/` as private state and tracked Neo source as the authorable input.
 - Never seek a force-CAS bypass. Pull, resolve, review, and retry.
 
 ## Set up a format-4 workspace
@@ -191,8 +191,11 @@ Conflict source deliberately fails compilation. Edit the desired final source,
 or use `neo resolve --mine|--theirs` as a whole-side convenience. Then pull,
 review, dry-run, and push again.
 
-`neo push` sends the complete hashed source bundle for trusted server
-recompilation but commits only the semantic diff under CAS. On
+`neo push` sends the authenticated semantic diff plus a deterministic source
+hash, while the server recompiles the changed NeoScript bodies and
+schema-affected callers and commits only that diff under CAS. Use
+`neo push --dry-run` for the complete source-to-record round-trip check; a
+normal push deliberately does not upload or re-lower the whole source tree. On
 `base-hash-conflict`, pull and resolve. On `version-bump-required`, inspect the
 classification and pass `neo push --accept-bump` only when intended.
 

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

@@ -60,9 +60,14 @@ LSP state. Preserve diagnostics, completion, hover, signatures, definition,
 references, rename, symbols, semantic tokens, code actions, and formatting
 parity for `.neo` and `.neoflow`.
 
-Keep trusted server recompilation and verification independent of client
-outputs. The CLI emits a complete source bundle; client-generated IR, structural
-rows, hashes, storage stamps, and pending IDs are not trusted.
+Keep trusted server validation independent of client-generated IR. The CLI
+sends the authenticated semantic diff and a deterministic source identity;
+the server recompiles changed NeoScript bodies and callers affected by
+schema-contract changes. Structural rows, hashes, storage stamps, identities,
+materialization, and CAS bases remain server-validated; unrelated source files
+are not uploaded or recompiled on every push. The explicit trade-off is that 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.
 
 ## Package and release maintenance
 
@@ -73,7 +78,7 @@ wrappers.
 The marker near the top of `SKILL.md` must exactly match the package version:
 
 ```html
-<!-- reviewed-through-cli: 0.21.5 -->
+<!-- reviewed-through-cli: 0.22.0 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale

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

@@ -22,6 +22,7 @@ neo diff
 neo dialogue dryrun <dialogue-ref>
 neo push --dry-run
 neo push
+neo push --dry-run --force-recompile
 ```
 
 Use `neo pull --regenerate-source-names` to refresh readable naming while
@@ -29,23 +30,42 @@ retaining normal merge behavior. Use `--reset` to regenerate canonical source
 and managed binaries. Use `--force` only to discard local edits for the server
 version.
 
-Treat `neo push --dry-run` as a full local commit rehearsal: bundle emission,
-pending-ID assignment on a clone, transport shapes, hashes, and repeat
+Treat `neo push --dry-run` as a full local commit rehearsal: source emission,
+in-memory pending-ID assignment, transport shapes, hashes, and repeat
 verification all run. It also runs the server's preparation phase locally —
 schema-commit materialization, seeded structural rows, and whole-graph
 validation — so a rejection that used to cost a real push and return an opaque
 `preparation-failed` now reports before anything is sent. It does not prompt,
 upload, commit, or rewrite source.
 
-Interactive pushes show `Preparing push…` before workspace discovery,
-lowering, and compilation begin. JSON and non-TTY output remain structured and
-do not emit that terminal-only spinner.
+Normal preparation follows typed compiler dependencies and recompiles only
+bodies affected by changed declarations. Use `--force-recompile` with either a
+dry run or a real push only when diagnosing stale derived IR: it retains the
+exhaustive project-wide body sweep and is intentionally slower.
+
+Interactive pushes report the active preparation phase before workspace
+discovery, lowering, compilation, source hashing, and validation begin.
+A normal push prepares that transport once before confirmation and reuses it
+after confirmation; it does not run a second local preparation pass. JSON and
+non-TTY output remain structured and do not emit that terminal-only spinner.
 
 A clean dry-run does not promise a clean push. The workspace holds its
 last-pulled state, so everything that grades the live head is still server-only:
-re-verification of the uploaded bundle bytes, project-file staging, the
-snapshot-id and content-head cross-check, admission classification, chunk
-planning, and finalization. Pull again before pushing if time has passed.
+project-file staging, authoritative changed/affected NeoScript compilation,
+record/identity/materialization validation, the snapshot-id and content-head
+cross-check, admission classification, chunk planning, and finalization. The
+server does not recompile every unchanged source file merely to prove that an
+authenticated developer used the CLI. Pull again before pushing if time has
+passed.
+
+Durable preparation is selected from the semantic record workload, not the
+size of the project-wide source identity. Its storage artifact carries one
+copy of the authored transaction, and resumable staging reads one plan per
+bounded batch while preserving an atomic write boundary per physical chunk.
+The complete source stays local: normal push sends its deterministic hash for
+reconnect identity, not the source bytes. A lowering mismatch can
+therefore surface on the next canonical pull; dry-run is the opt-in full
+source-to-record proof.
 
 One accepted push atomically commits records, main-locale text, stored bindings,
 and staged file metadata under CAS. Pending durable IDs and source rewrites