@neocompose/cli 0.37.0 → 0.38.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.37.0",
+  "version": "0.38.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.37.0 -->
+<!-- reviewed-through-cli: 0.38.1 -->
 
 # Neo Compose CLI
 

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

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

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

@@ -157,10 +157,18 @@ neo login [--api <url>] [--profile editor|release] [--save-project <id>]
 neo doctor
 ```
 
+`login`, `whoami`, and `logout` use the current workspace's `apiBaseUrl` when
+run beneath a `neo.json`. An explicit `--api` takes priority. Outside a
+workspace, they use the CLI build's default API origin. Login prints the
+selected origin before it requests or stores a credential.
+
 `neo doctor` reports two different things. The authoring contracts (format,
 compiler, extension cache, source, files) decide its exit code; the document
-audit below them reports malformed records in the last pull and deliberately
-does not, so a project with records still to repair does not fail the command.
+audit below them reports the last pull's malformed records, plus base rows no
+emitted file projects and no record names, and deliberately does not, so a
+project with records still to repair does not fail the command. An unprojected
+row is invisible to `neo status` by construction, which is why `neo doctor` is
+the only place it surfaces.
 `neo doctor --json` carries a `repair` entry per finding, which is what a
 targeted repair is handed instead of scanning a project to rediscover them.
 

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

@@ -70,7 +70,9 @@ create. The server validates authored new IDs for UUID-v4 shape and uniqueness.
 Prefer generated IDs unless the structural reference needs an ID immediately.
 
 Do not invent IDs for structural rows whose identities derive from an owner
-role. Do not add a separate root/static initializer ID.
+role. Do not add a separate root/static initializer ID. A constructor argument
+is one such row — its identity comes from the schema key its parameter settles
+— so it never carries `@id`, in either the named or the positional form.
 
 ## Same-push references
 
@@ -128,7 +130,16 @@ tracking. Require either transition to appear in `neo diff`.
 
 Editing an initializer updates sparse override rows in place: projected member
 IDs remain stable, and omitted virtual rows are never emitted as authored seed
-records. A construction whose durable constructor arguments changed, whose
+records. Spelling a declared default verbatim in a new initializer lowers to
+the same absence as omitting the member — a leaf equal to its declaration, or
+a bare class construction whose members the declaration wholly settles, mints
+no override row and resumes source tracking. A stored row already spelling its
+default converges to the sparse form on its next authored touch. A stored
+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
 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