dxcomplete 0.2.0 → 0.2.1

package/README.md

@@ -113,7 +113,7 @@ DX Complete uses one package version, one workspace compatibility gate, and one
 
 The MCP `surfaceVersion` field is a stable surface identifier. Use `surfaceFingerprint` for exact surface reconciliation and `workspaceCompatibility` for upgrade decisions.
 
-## Runtime Dogfood
+## Runtime and MCP
 
 The documentation scaffold is the first milestone. The next layer is a hosted runtime and MCP server so DX Complete can coordinate its own records. The runtime now treats Workspace as the boundary for one service scope.
 
@@ -148,11 +148,11 @@ npm run build
 npm run runtime:check
 ```
 
-The first runtime collections cover workspaces, statements, journal entries, environments, components, estimates, benefits, expectations, requirements, commitments, deferrals, tasks, changes, decisions, and risks. Dogfooding should use the normal MCP tools to create and link those records inside the intended workspace. Workspace-scoped lifecycle records receive a human-readable reference such as `REQ-0001` while UUID remains the primary key and link target.
+The first runtime collections cover workspaces, statements, journal entries, environments, components, estimates, benefits, expectations, requirements, commitments, deferrals, tasks, changes, decisions, and risks. Use the MCP tools to create and link those records inside the intended workspace. Workspace-scoped lifecycle records receive a human-readable reference such as `REQ-0001` while UUID remains the primary key and link target.
 
 Environment and Component records form the Operational Registry. The registry is an inventory of operational state: what exists in each environment, where it lives, and which secret names or locations are relevant. It is not monitoring, diagnostics, a secret vault, an event log, or a runbook engine. Secret pointers should identify stores and keys only; do not record secret values.
 
-Useful MCP tools for dogfooding include:
+Useful MCP tools include:
 
 - `runtime_status` to confirm the connected server process and MCP surface fingerprint.
 - `get_process_guide` to give MCP clients the current phase guide: Orient, Elicit, Weigh, Build, Go Live, Operate, and Measure.
@@ -175,11 +175,11 @@ Useful MCP tools for dogfooding include:
 - `link_records` and `unlink_records` for explicit relationships when a typed tool does not already create or remove the link.
 - `archive_record` for cleanup without deleting evidence.
 
-Hosted MCP is exposed at `/api/mcp`. The workspace route uses Streamable HTTP, advertises OAuth metadata for remote MCP clients, proxies OAuth through the central service, sends users through Google OAuth, and then returns DX Complete bearer tokens scoped to the configured workspace. The installed repo supplies workspace identity through `dxcomplete/workspace.json`; the central service stores workspace memberships and executes MCP tools. The current dogfood workspace grants Owner access to `sam.bourque@gmail.com`.
+Hosted MCP is exposed at `/api/mcp`. The workspace route uses Streamable HTTP, advertises OAuth metadata for remote MCP clients, proxies OAuth through the central service, sends users through Google OAuth, and then returns DX Complete bearer tokens scoped to the configured workspace. The installed repo supplies workspace identity through `dxcomplete/workspace.json`; the central service stores workspace memberships and executes MCP tools.
 
 The central service exposes internal routes under `/api/dxcomplete/service/*`. Workspace servers authenticate to those routes with `DXC_SERVICE_CLIENT_ID` and `DXC_SERVICE_CLIENT_SECRET`. The provisioning route creates the workspace record, seeds the Owner membership, and returns the one-time workspace service-client secret.
 
-For Google OAuth provisioning, set the callback URL to `/api/auth/callback/google` on the hosted workspace domain. For the dogfood deployment, use `https://dxcomplete.directeddomains.com/api/auth/callback/google`.
+For Google OAuth provisioning, set the callback URL to `/api/auth/callback/google` on the hosted workspace domain.
 
 Use `runtime_status` to reconcile the MCP-facing contract. `surfaceFingerprint` is the single client-facing identity for the tools, tool schemas, process guide, and on-demand doc references together. `get_process_guide` and `get_doc` return the same `surfaceVersion` and `surfaceFingerprint`, so an MCP client can treat a mismatch as a stale or inconsistent surface and refresh before continuing.
 
@@ -191,14 +191,6 @@ The Journal is shared workspace context, not a private ticket. It is for useful
 
 The Operating Guide explains record routing by role. Engineer/Codex work defaults to Requirement -> Task. Tester evidence usually belongs in Task entries, review notes, Risk, Decision, or Journal. Operator work uses Change for run-side alterations, Incident for specific service-impacting occurrences, Problem for underlying or recurring causes, and Environment or Component for operational inventory. Support Agent work starts with DX Complete Ticket, then promotes to shared records only when needed.
 
-For dogfood maintenance work that needs direct database access, batch the work in one process instead of running repeated one-off Mongo commands:
-
-```sh
-npm run dogfood:work-order -- --plan ./work-order.json
-```
-
-The work-order runner opens one runtime connection, runs ticket summaries, ticket reads, DX Complete replies, simple archives, link-residue checks, or a local one-off module, then closes the connection. It is a maintainer tool for dogfood cleanup and migration work; the normal product path remains the hosted MCP tools.
-
 Run the hosted MCP smoke test after runtime changes:
 
 ```sh

package/dist/validate.js

@@ -70,7 +70,7 @@ function packageRequiredFiles() {
         path.join("templates", "AGENTS.md"),
         path.join("scripts", "check-env-surface.mjs"),
         path.join("scripts", "smoke-mcp-http.mjs"),
-        path.join("scripts", "dogfood-work-order.mjs"),
+        path.join("scripts", "runtime-work-order.mjs"),
         path.join("scripts", "check-public-copy.mjs"),
         path.join("scripts", "check-service-boundary.mjs"),
         path.join("templates", "next", "pages", "api", "mcp.js"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dxcomplete",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Install a Next.js workspace scaffold for DX Complete process records, MCP routes, and service lifecycle documentation.",
   "type": "module",
   "keywords": [
@@ -61,7 +61,7 @@
     "smoke:mcp:http:change": "node scripts/smoke-mcp-http.mjs --area=change",
     "smoke:mcp:http:tickets": "node scripts/smoke-mcp-http.mjs --area=tickets",
     "smoke:mcp:http:journal": "node scripts/smoke-mcp-http.mjs --area=journal",
-    "dogfood:work-order": "node scripts/dogfood-work-order.mjs",
+    "runtime:work-order": "node scripts/runtime-work-order.mjs",
     "validate:package": "node dist/cli.js validate --target . --package-layout",
     "runtime:check": "node dist/cli.js check-runtime"
   },

package/scripts/{dogfood-work-order.mjs → runtime-work-order.mjs}

@@ -473,14 +473,14 @@ function elapsedSeconds(started) {
 }
 
 function printHelp() {
-  console.log(`dogfood-work-order
+  console.log(`runtime-work-order
 
 Usage:
-  node scripts/dogfood-work-order.mjs --plan ./work-order.json
-  node scripts/dogfood-work-order.mjs --module ./one-off.mjs
+  node scripts/runtime-work-order.mjs --plan ./work-order.json
+  node scripts/runtime-work-order.mjs --module ./one-off.mjs
 
 Purpose:
-  Open Mongo once and batch dogfood reads, ticket replies, simple verification,
+  Open one runtime connection and batch ticket reads, ticket replies, simple verification,
   and optional one-off work-order modules.
 
 Plan shape:

package/src/validate.ts

@@ -89,7 +89,7 @@ function packageRequiredFiles(): string[] {
     path.join("templates", "AGENTS.md"),
     path.join("scripts", "check-env-surface.mjs"),
     path.join("scripts", "smoke-mcp-http.mjs"),
-    path.join("scripts", "dogfood-work-order.mjs"),
+    path.join("scripts", "runtime-work-order.mjs"),
     path.join("scripts", "check-public-copy.mjs"),
     path.join("scripts", "check-service-boundary.mjs"),
     path.join("templates", "next", "pages", "api", "mcp.js"),