@neocompose/cli 0.58.3 → 0.59.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.58.3",
+  "version": "0.59.1",
   "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.58.3 -->
+<!-- reviewed-through-cli: 0.59.1 -->
 
 # Neo Compose CLI
 
@@ -38,8 +38,8 @@ Those are not part of format 4.
    or push merely to obtain compiled initializer bodies.
 5. Run `neo push --dry-run` before every real push. It performs the full local
    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,
+   then runs the preparation a real push ships — compilation, schema-commit
+   materialization, and whole-graph validation — against the pulled document,
    without prompting, uploading, committing, or rewriting the checkout. Pull
    once with the installed CLI so the workspace carries compatible
    derived-edge extractor metadata. Pending getters and functions compile before
@@ -258,9 +258,10 @@ a pull conflict by itself; if an older CLI retained such a metadata-only
 conflict without writing source markers, either side settles it the same way
 while preserving any real local source edit.
 
-`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` prepares the commit locally, recompiling changed NeoScript bodies
+and schema-affected callers, and the server commits the prepared changes under
+CAS. If another commit lands after your pull, the push fails as
+`non-fast-forward`: pull, then push again. 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

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

@@ -72,14 +72,18 @@ 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 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.
+The CLI prepares every push with the server's own preparation code: it
+compiles changed NeoScript bodies and callers affected by schema-contract
+changes, materializes values, and validates the whole graph against the pulled
+head. The server accepts that preparation only from a CLI on its NeoScript
+compiler revision and re-checks the head, authorization, row shapes, and CAS
+bases. A modified CLI can therefore write bad rows to a project its user may
+already write; keep preparation in shared `src/database` code rather than
+forking it in the CLI. The server still verifies a push's uploaded
+project-file bytes, and web editor commits still prepare on the server.
+Unrelated source files are not uploaded or recompiled on every push. 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.
 
 A committed push result is journaled in `.neo/state.json` before source
 projection. If projection fails, `neo pull` consumes that result and preserves
@@ -97,7 +101,7 @@ wrappers.
 The marker near the top of `SKILL.md` must exactly match the package version:
 
 ```html
-<!-- reviewed-through-cli: 0.58.3 -->
+<!-- reviewed-through-cli: 0.59.1 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale

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

@@ -73,11 +73,10 @@ restarts. Upgrade the CLI together with the P83 server read protocol.
 
 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.
+verification all run. It also runs the preparation a real push ships —
+compilation, schema-commit materialization, seeded structural rows, and
+whole-graph validation — so a rejection reports before anything is sent. It
+does not prompt, upload, commit, or rewrite source.
 
 Dry-run also compares the CLI's derived-edge extractor with the server version
 saved by the last pull. Run `neo pull` after upgrading the CLI or when an older
@@ -90,8 +89,10 @@ dry run or a real push only when diagnosing stale derived IR: it retains the
 exhaustive project-wide body sweep and is intentionally slower.
 
 Changed member bodies and migration bodies share one schema projection and its
-indexes throughout push preparation. Each changed member body is compiled once,
-so a batch of scripted changes does not rebuild the whole schema for every body.
+indexes throughout push preparation, so a batch of scripted changes does not
+rebuild the whole schema for every body. Each changed body compiles once for
+local evaluation and once more, against minted ids, in the preparation the push
+ships.
 
 Interactive status, diff, pull, and test commands report workspace loading and
 preparation phases. Spinners continue animating during synchronous compilation;
@@ -105,17 +106,14 @@ 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:
-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.
+last-pulled state, so the server still grades the live head: the project-head
+check, per-change CAS bases, authorization, row shapes, project-file staging,
+admission, chunk planning, and finalization. A push whose head moved fails as
+`non-fast-forward`. 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
+copy of the prepared 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 hashes the exact authored source
 inputs already read during preparation, including file paths and formatting,