nexarch 0.1.19 → 0.1.21

package/dist/commands/init-agent.js

@@ -4,7 +4,7 @@ import { join } from "path";
 import process from "process";
 import { requireCredentials } from "../lib/credentials.js";
 import { callMcpTool, mcpInitialize, mcpListTools } from "../lib/mcp.js";
-const CLI_VERSION = "0.1.19";
+const CLI_VERSION = "0.1.21";
 const AGENT_ENTITY_TYPE = "agent";
 const TECH_COMPONENT_ENTITY_TYPE = "technology_component";
 function parseFlag(args, flag) {

package/dist/commands/init-project.js

@@ -445,29 +445,39 @@ STEP 2 — Enrich the project entity. Run this command with the description you'
     --name "<proper product name from README>" \\
     --description "<2–4 sentence summary of what it does and why>"
 ${subPackages.length > 0 ? `
-STEP 3 — Register each sub-application as its own entity.
-  The scanner found ${subPackages.length} workspace package(s). For each one, read its
-  README / package.json description, then run:
+STEP 3 — Classify and register each sub-package as its own entity.
+  The scanner found ${subPackages.length} workspace package(s):
 
-  Sub-packages detected:
 ${subPackages.map((sp) => `    • ${sp.name}  (${sp.relativePath})`).join("\n")}
 
-  For each sub-package run:
+  For each one, READ its package.json and any README to understand what it actually is,
+  then choose the correct entity type and subtype before running update-entity:
 
-  npx nexarch update-entity \\
-    --key "application:<slugified-package-name>" \\
-    --entity-type "application" \\
-    --subtype "app_custom_built" \\
-    --name "<sub-app name>" \\
-    --description "<what this sub-app does>"
+  CLASSIFICATION GUIDE — pick the best fit:
+    Deployable web app (has a dev/start/build script, runs in a browser or as a server)
+      → --entity-type application --subtype app_web
+    Deployable background service, worker, or data pipeline (runs as a process, no UI)
+      → --entity-type application --subtype app_custom_built  (or app_integration_service for crawlers/ETL)
+    Shared internal library or package (imported by other packages, not deployed on its own)
+      → --entity-type technology_component --subtype tech_library
+    Shared UI component library
+      → --entity-type technology_component --subtype tech_framework
+    Type definitions or utility package with no runtime
+      → --entity-type technology_component --subtype tech_library
+
+  For each sub-package, run:
 
-  Then wire it to the parent project:
+  npx nexarch update-entity \\
+    --key "<entity-type>:<slugified-package-name>" \\
+    --entity-type "<chosen entity type>" \\
+    --subtype "<chosen subtype>" \\
+    --name "<human readable name>" \\
+    --description "<what this package does and its role in the project>"
 
-  npx nexarch add-relationship \\
-    --from "application:<slugified-package-name>" \\
-    --to "${projectExternalKey}" \\
-    --type "part_of"
+  Then wire it to the parent project using the appropriate relationship:
+    • Deployable apps  → relationship type: part_of
+    • Shared libraries → relationship type: depends_on  (parent depends on the library)
 
-  (Note: add-relationship is coming soon — skip if not yet available)
+  (Note: add-relationship command is coming — skip wiring for now if unavailable)
 ` : ""}`);
 }

package/dist/commands/update-entity.js

@@ -41,6 +41,7 @@ export async function updateEntity(args) {
     const agentContext = {
         agentId: "nexarch-cli:update-entity",
         agentRunId: `update-entity-${Date.now()}`,
+        repoRef: externalKey,
         observedAt: nowIso,
         source: "nexarch-cli",
         model: "n/a",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nexarch",
-  "version": "0.1.19",
+  "version": "0.1.21",
   "description": "Connect AI coding tools to your Nexarch architecture workspace",
   "keywords": [
     "nexarch",