@neocompose/cli 0.50.6 → 0.50.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.50.6",
+  "version": "0.50.8",
   "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.50.6 -->
+<!-- reviewed-through-cli: 0.50.8 -->
 
 # Neo Compose CLI
 
@@ -44,6 +44,8 @@ Those are not part of format 4.
    once with the installed CLI so the workspace carries compatible
    derived-edge extractor metadata.
 6. Push one reviewed atomic change with `neo push`.
+   Completion arrives through a live subscription. Progress counts refresh every
+   five seconds while the durable job runs; a disconnect does not cancel it.
 
 Treat pull followed immediately by status or dry-run as a semantic no-op. If it
 reports project changes, stop and report a round-trip bug instead of pushing.

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

@@ -88,7 +88,7 @@ wrappers.
 The marker near the top of `SKILL.md` must exactly match the package version:
 
 ```html
-<!-- reviewed-through-cli: 0.50.6 -->
+<!-- reviewed-through-cli: 0.50.8 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale

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

@@ -89,11 +89,21 @@ 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
+The complete source stays local. Normal push hashes the exact authored source
+inputs already read during preparation, including file paths and formatting,
+without regenerating canonical source. The same source bytes and workspace base
+retain reconnect identity across candidate UUID allocation. A formatting or path
+change produces a new identity. Dry-run uses the same authored hash and separately
+rehearses the complete canonical source round trip. A lowering mismatch can
 therefore surface on the next canonical pull; dry-run is the opt-in full
 source-to-record proof.
 
+When a transaction commits, its status response carries the first bounded result
+page. The CLI downloads further pages when needed and validates the full result
+count before advancing its base. Result application rechecks source bytes,
+managed binaries, and the workspace base before reusing local preparation; edits
+made while waiting trigger fresh analysis and the existing merge behavior.
+
 One accepted push atomically commits records, main-locale text, stored bindings,
 and staged file metadata under CAS. Pending durable IDs and source rewrites
 become real only after acceptance.
@@ -254,3 +264,16 @@ machine-readable output and do not depend on interactive pickers or confirms.
 contents before writing C#, preserves unchanged `.meta` files, removes obsolete
 outputs listed in `NeoGeneratedFiles.json`, and removes the former
 `NeoGeneratedTypes.cs`. Stable identities in the manifest preserve `.meta` GUIDs when types are renamed. Keep the manifest with the generated files.
+
+## Push timing diagnostics
+
+Set `NEO_COMPOSE_TRACE_PERFORMANCE=1` when measuring a push. It writes
+`neo-performance` JSON lines to stderr for workspace loading, local candidate
+preparation, file uploads, submission, authentication, live transaction completion,
+result download, and local result application. `startedMs` is relative to the
+CLI process and `durationMs` covers the named operation. Nested spans overlap;
+do not add all durations. Normal command JSON remains on stdout.
+
+Durable pushes submit compressed JSON directly to a Convex HTTP action and subscribe to completion with the scoped session's refreshing JWT. Bodies above 1 MiB and staged media use an internal Node action; requests beyond the direct transport's bounds use the existing server upload route. The CLI pins the deployment through the authenticated app origin before sending it a session token.
+Results pin the workspace to that transaction's hash, so a concurrent later commit still
+requires a pull before another push.

package/skills/neocompose-cli/references/values-identities-and-references.md

@@ -163,7 +163,11 @@ construction predating the P75 collapse converges the same way: its next push
 drops the constructor-settled keys the body duplicated from the creation data
 and stamps the construction's provenance. That is a one-time storage
 convergence, not an edit — resolved values do not change, and the argument
-rows stay reachable through the creation data that already named them. A construction whose durable constructor arguments changed, whose
+rows stay reachable through the creation data that already named them.
+
+Defaulted members may be added without recreating existing instances, including
+instances whose sparse arguments are retained only as constructor data.
+A construction whose durable constructor arguments changed, whose
 class changed, or which predates a required constructor parameter fails with
 `construction-arguments-conflict` instead of silently replaying a different
 recipe. Edit members supported by the recorded construction, or delete and