nexarch 0.12.35 → 0.12.39

package/dist/commands/agent-identify.js

@@ -4,6 +4,7 @@ import { homedir } from "os";
 import { join } from "path";
 import { requireCredentials } from "../lib/credentials.js";
 import { callMcpTool, mcpInitialize, mcpListTools } from "../lib/mcp.js";
+import { cliVersion } from "../lib/version.js";
 function parseFlag(args, flag) {
     return args.includes(flag);
 }
@@ -60,7 +61,7 @@ export async function agentIdentify(args) {
     const client = parseOptionValue(args, "--client");
     const sessionId = parseOptionValue(args, "--session-id");
     const framework = parseOptionValue(args, "--framework");
-    const toolVersion = parseOptionValue(args, "--tool-version");
+    const toolVersion = parseOptionValue(args, "--tool-version") ?? cliVersion();
     const capabilities = parseCsv(parseOptionValue(args, "--capabilities"));
     const notes = parseOptionValue(args, "--notes");
     if (!provider || !model || !client) {

package/dist/commands/init-agent.js

@@ -8,6 +8,7 @@ import { requireCredentials } from "../lib/credentials.js";
 import { fetchAgentRegistryOrThrow } from "../lib/agent-registry.js";
 import { callMcpTool, mcpInitialize, mcpListTools } from "../lib/mcp.js";
 import { buildVersionAttributes } from "../lib/version-normalization.js";
+import { cliVersion } from "../lib/version.js";
 import { requestTrustAttestation, TRUST_ATTESTATION_SCOPE } from "../lib/trust.js";
 const CLI_VERSION = (() => {
     try {
@@ -684,7 +685,7 @@ export async function initAgent(args) {
     const clientArg = parseOptionValue(args, "--client");
     const frameworkArg = parseOptionValue(args, "--framework");
     const sessionIdArg = parseOptionValue(args, "--session-id");
-    const toolVersionArg = parseOptionValue(args, "--tool-version");
+    const toolVersionArg = parseOptionValue(args, "--tool-version") ?? cliVersion();
     const capabilitiesArg = parseCsv(parseOptionValue(args, "--capabilities"));
     const notesArg = parseOptionValue(args, "--notes");
     const agentId = explicitAgentId ?? getDefaultAgentId();

package/dist/lib/mcp.js

@@ -51,12 +51,29 @@ async function requestOnce(method, params, options) {
                     const raw = Buffer.concat(chunks).toString("utf-8");
                     const json = JSON.parse(raw);
                     if (json.error) {
-                        const detail = json.error.data &&
-                            typeof json.error.data === "object" &&
-                            "detail" in json.error.data &&
-                            typeof json.error.data.detail === "string"
-                            ? json.error.data.detail
+                        const errData = json.error.data;
+                        const explicitDetail = errData && typeof errData === "object" && "detail" in errData && typeof errData.detail === "string"
+                            ? errData.detail
                             : null;
+                        // INVALID_TOOL_ARGUMENTS carries Zod detail — without this,
+                        // every schema violation surfaced as the bare, undiagnosable
+                        // "Invalid tool arguments" and nothing else, e.g. a missing
+                        // required entity field on a create looked identical to an
+                        // unrelated request shape mistake. Prefer `issues` (full dotted
+                        // path per error, e.g. "entities.0.name: Required") over the
+                        // older `fieldErrors` shape, which collapses a nested path down
+                        // to just its top-level key and loses which field/index failed.
+                        const zodDetail = !explicitDetail && errData && typeof errData === "object" && "issues" in errData
+                            ? errData.issues
+                                .map(({ path, message }) => (path ? `${path}: ${message}` : message))
+                                .join("; ") || null
+                            : !explicitDetail && errData && typeof errData === "object" && "fieldErrors" in errData
+                                ? Object.entries(errData.fieldErrors)
+                                    .filter(([, messages]) => Array.isArray(messages) && messages.length > 0)
+                                    .map(([field, messages]) => `${field}: ${messages.join(", ")}`)
+                                    .join("; ") || null
+                                : null;
+                        const detail = explicitDetail ?? zodDetail;
                         reject(new Error(detail ? `${json.error.message} (${detail})` : json.error.message));
                     }
                     else if (json.result !== undefined) {

package/dist/lib/skills.js

@@ -104,28 +104,30 @@ skill is the check-in → claim → complete loop for working that queue.
 - \`nexarch_check_in\` previews pending commands and draft/proposed
   applications for this agent. It does **not** claim or change anything —
   safe to call any time, including proactively at the start of a session.
-- If you have a **confirmed** application ref — returned by an earlier tool
-  call in this session (\`target_entity_key\` from a prior check-in,
-  \`nexarch_list_entities\`, \`nexarch_resolve_reference\`), or the human gave
-  you the exact ref — pass it as
-  \`applicationContext: { accessibleApplicationRefs: ["application:<ref>"] }\`
-  on this **first** call to skip a redundant round trip.
-- **Never guess the ref from a project/repo/directory name.** A repository
-  named \`veri-viva-platform\` does not mean its application ref is
-  \`application:veri_viva_platform\` — the real one might be
-  \`application:veri_viva_platform_website\` or anything else; projects and
-  applications are different entities with independently-chosen refs (see
-  the architecture-graph skill). A wrong-but-plausible-looking ref doesn't
-  just fail to claim — it silently filters real pending commands out of the
-  response, and check-in will wrongly report nothing pending. If you're not
-  certain a ref is correct, call check-in bare instead.
+- If you have a **confirmed** ref — returned by an earlier tool call in this
+  session (\`target_entity_key\` from a prior check-in, \`nexarch_list_entities\`,
+  \`nexarch_resolve_reference\`), or the human gave you the exact ref — pass
+  it as \`applicationContext: { accessibleApplicationRefs: ["<ref>"] }\` on
+  this **first** call to skip a redundant round trip.
+- **A project ref works here too, and is often the one you actually have.**
+  You're usually registered against the repository's \`project:\` ref, not
+  any specific \`application:\` ref inside it — passing the project ref is
+  fine; check-in expands it to every application \`sourced_from\` it and
+  scopes to all of them. A monorepo project can source several
+  applications, so this is different from — and safer than — guessing which
+  single application ref applies: don't construct an application ref by
+  pattern-matching the project/repo name (\`project:veri_viva_platform\` does
+  not imply \`application:veri_viva_platform\` exists; the real one might be
+  \`application:veri_viva_platform_website\` or something else entirely).
+  Pass the project ref you actually have, not a guessed application ref.
+- If a scoped call's response includes \`project_ref_expanded_to_applications\`,
+  that's normal — it's telling you which application(s) a project ref
+  resolved to. \`application_context_ref_unresolved\` means a ref you passed
+  matched nothing at all. \`pending_commands_outside_requested_scope\` means
+  the resolved scope still didn't cover everything pending — call check-in
+  again with no \`applicationContext\` to see the rest.
 - Calling bare (no \`applicationContext\`) is always safe and returns every
-  pending command's real \`target_entity_key\` — use that to make an
-  informed scoped call afterward.
-- If a scoped call's response includes a
-  \`pending_commands_outside_requested_scope\` warning, the ref you supplied
-  didn't match everything — it's very likely wrong. Re-call bare rather than
-  trusting the (incomplete) result.
+  pending command's real \`target_entity_key\` if you have no ref at all yet.
 - Report exactly what check-in found. Don't reinterpret "check in" as
   registration (\`init-agent\`) or as a general health check
   (\`nexarch_get_governance_summary\`) — they're different actions.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nexarch",
-  "version": "0.12.35",
+  "version": "0.12.39",
   "description": "Your architecture workspace for AI delivery.",
   "keywords": [
     "nexarch",