@moretea-labs/forge 1.6.0 → 1.7.1

package/docs/operations/controller-performance-and-502.md

@@ -39,6 +39,149 @@ Call `GET /health` on the local MCP endpoint. The response includes:
 
 A growing `rejectedOverload` value with no matching capacity-eviction or close activity means clients are submitting protected work faster than the Controller can accept it. A pool full of stream-only sessions should now self-recover. Retrying with backoff is preferable to increasing every limit.
 
+## Runtime Activation Failure Looks Like a 502 (2026-08-23 incident)
+
+When a new Runtime release activation fails, the public MCP path can return
+HTTP `500` on `initialize`, which the tunnel surfaces as a `502`-style
+connection failure. The chain observed on 2026-08-23:
+
+1. A Runtime release activation started a new `mcp serve` process while the
+   launchd gateway already owned `127.0.0.1:8767`. The new process failed to
+   bind (`Failed to start server. Is port 8767 in use?`) but did **not exit**;
+   it kept running as an orphan (`PPID 1`) spinning at ~98% CPU.
+2. The canonical Runtime (port 8765) failed to start for the new release
+   (`RUNTIME_RELEASE_AUTHORITY_MISMATCH` in
+   `runtime/service/logs/stderr.log`), so the gateway could not complete MCP
+   `initialize` and returned HTTP 500.
+3. `tunnel-client` posted the upstream error to the control plane
+   (`dispatcher received MCP upstream error`, `upstream_status=500`,
+   `rpc_method=initialize`), which the remote client saw as a failed
+   connection / 502.
+
+Diagnostic fingerprint:
+
+- `gateway.stderr.log` contains `Failed to start server. Is port 8767 in use?`
+- `runtime/service/logs/stderr.log` contains repeated
+  `RUNTIME_RELEASE_AUTHORITY_MISMATCH`
+- recovery watchdog log shows `restart_primary_runtime` attempts followed by
+  `action":"rollback"` restoring the previous release
+- a stray `bun ... mcp serve` process with `PPID 1` and high `%CPU`
+
+Remediation:
+
+- The standalone Recovery watchdog automatically rolls back after the bounded
+  restart budget is exhausted; wait for `action":"healthy"` in
+  `recovery/audit/watchdog.log` before doing anything else.
+- Kill the orphaned `mcp serve` child of the failed release (verify it holds no
+  listening sockets first); it only burns CPU after a failed port bind.
+- Verify the canonical Runtime answers `initialize` on its own port and that
+  the tunnel log shows no new `upstream_status=500` entries.
+
+Known code defect to fix: `mcp serve` should exit with a non-zero status when
+the requested port is already in use instead of staying alive in a hot loop.
+
+## Connector/Activation Recovery Gaps Behind Intermittent 502 (2026-08-27)
+
+A second class of intermittent `502` was traced to release/Connector coherence rather
+than to a permanently dead Recovery service.
+
+Observed evidence:
+
+- a live Forge MCP request returned `502` while independent Recovery observed the
+  Canonical Runtime briefly as `RUNTIME_NOT_RUNNING`; the Runtime became ready again
+  a few seconds later after release authority reverted to the prior package release;
+- separate MCP connection failures also occurred while independent Recovery still
+  observed the Canonical Runtime as ready, proving that not every `502` is a whole-
+  Runtime failure;
+- the persistent package Connector health probe accepted any received HTTP status,
+  so `500`/`502` could be classified as healthy and the broken service reused;
+- detached macOS package activation scheduled the Runtime switch and then rebound the
+  Connector to the candidate release before the activation helper committed the
+  Runtime service. If helper activation failed, Runtime authority/service rolled back
+  while Connector authority/plist could remain on the candidate generation;
+- standalone Recovery's Connector action previously restarted the already-installed
+  launchd service. A stale/mutable launch spec therefore remained stale after restart.
+
+Corrected invariants:
+
+1. Connector reuse accepts only the expected MCP/OAuth endpoint semantics (`200` or
+   the unauthenticated `401` Bearer challenge); `5xx` is always unhealthy.
+2. Detached activation does not switch the Connector in the installer. The activation
+   helper installs the Runtime service first and only then commits the Connector to the
+   same immutable package release. A Runtime activation failure therefore leaves the
+   prior Connector generation untouched.
+3. Connector-only Recovery first reconciles the canonical package Connector against
+   the active immutable Runtime release, then verifies local ownership/public MCP, and
+   only then decides whether a launchd/tunnel restart is still required.
+4. Whole-Runtime rollback remains deliberately stricter than Connector recovery. A
+   known-good Runtime is not rolled back merely because its Connector or external
+   tunnel drifted; those hops must be repaired independently.
+5. Recovery `runtime_status` reports bounded Watchdog decision evidence (last action,
+   reason and restart/failure counters) so incident review can distinguish "Recovery
+   never fired" from "Recovery fired and the client observed the bounded outage".
+
+## Recurring Connection Failure Ledger
+
+Keep these failure signatures distinct. A public `502` identifies the failed
+hop; it does not identify the failed owner or authorize a whole-Runtime
+rollback.
+
+| Signature | Verified evidence | Correct recovery owner |
+| --- | --- | --- |
+| Runtime activation/port conflict | `RUNTIME_RELEASE_AUTHORITY_MISMATCH`, port `8767` already in use, or orphaned `mcp serve` | Whole-Runtime Recovery transaction; see the 2026-08-23 incident above. |
+| Connector/release binding drift | Runtime `ready=true`, but Connector loopback/public MCP fails or returns `5xx` | Connector Recovery reconciles the active immutable release, then verifies local ownership and the public endpoint. |
+| Connector launched with a Recovery-role binary | Connector plist starts `forge-recovery-gateway` or `forge-recovery-watchdog`; stderr repeats `RECOVERY_*_ROLE_ONLY` | Repair the Connector with the absolute interpreter recorded by Runtime activation. A Connector launch spec must reject a Recovery-role binary. |
+| Connector outage misclassified as a Runtime outage | Runtime status and local active Gateway are healthy while the Watchdog records `restart_primary_runtime` for a Connector probe failure | Count and restart the Connector under its own bounded budget; do not consume the Runtime restart/rollback budget. |
+
+The launch interpreter is part of the Connector's immutable release binding:
+detached activation passes its recorded absolute `nodeExecutable` to candidate
+and rollback Connector installs, and Recovery services retain the same explicit
+interpreter for later binding repair. Regression coverage must exercise a
+failed Connector while the Canonical Runtime remains healthy.
+
+## Session Continuation Fails With 404 MCP_TOOL_SURFACE_CHANGED (2026-08-23)
+
+Second incident on the same day, different failure mode. After a session is
+created, every follow-up (`notifications/initialized`, `tools/call`) returned
+HTTP 404 with:
+
+```json
+{"error":"session_not_found","code":"MCP_TOOL_SURFACE_CHANGED",
+ "message":"MCP Runtime tool surface changed; initialize a new session so tools/list is refreshed.",
+ "recoverable":true,"action":"reinitialize",
+ "previousFingerprint":"<session>","currentFingerprint":"<published>"}
+```
+
+Root cause: the Gateway session fence compares the **live** Runtime schema
+fingerprint captured at `initialize` (`readCanonicalRuntimeToolSchema` ->
+`proxy.listTools()`) against the **published** fingerprint in
+`runtime/status.json`. The Runtime publishes `status.json` once at startup and
+does not republish when its live tool surface changes at runtime (e.g. a
+plugin registers or code edits change the tool set). Once the two values
+diverge, every session continuation is rejected as a tool-surface change, so
+the tunnel/connector appears broken even though `/health` shows both
+fingerprints matching the published value.
+
+Diagnostic fingerprint:
+
+- Gateway `/health` shows `toolSurfaceFingerprint` equal to
+  `runtimeToolSurfaceFingerprint` (both read the published value), but a real
+  `initialize` session stores a different fingerprint.
+- Follow-up requests get the `MCP_TOOL_SURFACE_CHANGED` 404 with
+  `previousFingerprint != currentFingerprint`.
+
+Remediation:
+
+- Restart the canonical Runtime service
+  (`launchctl kickstart -k gui/$UID/com.moretea.forge.runtime.<suffix>`) so it
+  republishes `status.json` from its current surface, then verify
+  `initialize` -> `notifications/initialized` (202) -> `tools/call` (200) with
+  a valid OAuth token.
+- Known code defect to fix: the Runtime should republish `status.json`
+  whenever its live tool surface changes (tool list changed), and/or the
+  Gateway fence should prefer the live fingerprint for the current-schema
+  comparison instead of trusting a stale publication.
+
 Call `GET /ready` separately. A 503 from `/ready` with `/health` still returning 200 means the Runtime is live but cannot safely admit another initialize. `sessionCapacity.recoveryRecommended=false` preserves active work and waits; `true` is evidence for standalone Recovery's bounded whole-Runtime restart policy after the configured stall limit.
 
 ## Diagnostic Order

package/docs/operations/controller-reliability-runbook.md

@@ -68,7 +68,7 @@ A release change is performed only as an explicitly authorized whole-Runtime ope
 1. validate one immutable release manifest, configuration, database compatibility range, and Worker protocol;
 2. quiesce admission and stop the complete Runtime;
 3. atomically select the candidate as the one active whole release;
-4. let the single Forge Runtime service start `forge-runtime` from that complete release;
+4. atomically mirror the selected release's signed `forge-runtime` entrypoint to the fixed physical service path `runtime/service/active-forge-runtime`, then let the single Forge Runtime service start that stable path with the selected release manifest/environment;
 5. require binary whole-Runtime readiness;
 6. on failure, stop the service, restore the previous release and its bound local SQLite backup, then start and verify the complete previous Runtime.
 

package/docs/operations/features.md

@@ -26,8 +26,8 @@ These features are part of the default local setup:
 | Tailscale / Cloudflare | Stable HTTPS endpoint for ChatGPT MCP | Tunnel client and appropriate account/domain configuration. |
 | Browser | Playwright navigation, screenshots, and bounded browser evidence | Browser binaries and HTTP(S) URL scheme validation. |
 | CodeGraph | Additional code relationships and impact navigation | CodeGraph CLI; native Windows automatic setup is not yet enabled. |
-| Google Workspace | Gmail and Calendar assistant actions | Explicit OAuth setup and plugin permission. |
-| Schedules and findings | Supervised recurring checks and candidate findings | Canonical Forge Runtime running; live actions remain policy-gated. |
+| Google Workspace | Gmail and Calendar plugin actions | Explicit OAuth setup and plugin permission. |
+| Schedules | Supervised recurring checks | Canonical Forge Runtime running; live actions remain policy-gated. |
 
 ## Tool exposure
 

package/docs/operations/github-repository.md

@@ -42,7 +42,7 @@ Use Issues for reproducible defects and scoped feature requests. Use Discussions
 
 ## Documentation ownership
 
-The GitHub Wiki is a presentation target. Versioned source lives under `docs/wiki/`. Deeper engineering detail remains under `docs/architecture/current/` and `docs/operations/`.
+The GitHub Wiki is a presentation target. Versioned source lives under `docs/wiki/`. Deeper engineering detail remains under `docs/architecture/CURRENT.md` and `docs/operations/`.
 
 Public documentation must distinguish current facts from historical evidence. Avoid hard-coding “next release” versions in operational runbooks; derive versions from `package.json` so routine releases do not leave stale docs behind.
 

package/docs/operations/homebrew.md

@@ -6,8 +6,8 @@ Homebrew is planned as a convenience layer after the first stable npm/GitHub rel
 
 Do not publish a formula until all of the following are true:
 
-- `@moretea-labs/forge@1.6.0` exists on npm;
-- Git tag and GitHub Release `v1.6.0` exist and point to the tested commit;
+- `@moretea-labs/forge@1.7.1` exists on npm;
+- Git tag and GitHub Release `v1.7.1` exist and point to the tested commit;
 - the npm tarball has an immutable checksum;
 - macOS installation and `forge --version` / `forge doctor` tests pass;
 - upgrade and uninstall behavior is documented.

package/docs/operations/mcp-tool-exposure.md

@@ -6,8 +6,9 @@ Controller MCP uses one stable default schema so ChatGPT can reliably read, edit
 
 | Toolset | CLI | Behavior |
 | --- | --- | --- |
-| **advanced** (default) | `--toolset advanced` | Stable repair-capable surface, capped at 128 tools. Includes the five `rh_*` facades plus high-value repository, Direct Edit, command, Git, Work/Job, Agent, Goal/Work, plugin, browser, iOS, artifact, and recovery tools. |
-| **core** | `--toolset core` | Compatibility label for the same stable default schema. It does not reduce capability or require reconnecting. |
+| **facade** (opt-in) | `--toolset facade` | Five-tool ChatGPT orchestration surface: `rh_access`, `rh_status`, `rh_inbox`, `rh_context`, `rh_work`. Internal handlers and capabilities remain registered; only MCP discovery is reduced. Intended for latency/tool-selection A/B before any default migration. |
+| **advanced** (default) | `--toolset advanced` | Current stable 19-tool controller surface. Includes the five `rh_*` facades plus repository, Direct Edit, command, check, plugin-dispatch, Process, and result/evidence tools. |
+| **core** | `--toolset core` | Compatibility label for the same stable default 19-tool schema. It does not reduce capability or require reconnecting. |
 | **full** | `--toolset full` | Every historical legacy and runtime definition. Use only for old integrations or deep compatibility diagnosis because the much larger schema can reduce tool-selection quality. |
 
 Configure via CLI flags, `FORGE_MCP_TOOLSET`, or Controller Home MCP config. Empty/default controller configuration resolves to `advanced`.
@@ -31,7 +32,7 @@ The current implementation separates orchestration from capability without delet
 2. **Typed atomic tools:** repository inspection, Direct Edit, command, Git, Work/Job, Issue/Task, Goal/Work, plugin, browser, iOS, artifact, and recovery handlers remain public because their schemas preserve operation-specific validation and evidence.
 3. **Internal handlers and capability registry:** capabilities are grouped as `controller`, `repository-core`, `git`, `issue-task`, `browser`, `ios`, `plugin`, `evidence`, and `runtime-maintenance`. `rh_status`, `rh_context`, and `controller_capabilities` expose this metadata.
 
-The MCP transport currently publishes a static stable schema. It does **not** support loading a domain schema only after ChatGPT selects that domain. Therefore capability grouping improves selection and documentation, but it must not be described as dynamic tool loading. A future transport-level implementation may reduce the discovered schema while retaining the same internal handlers.
+The MCP transport publishes a static schema for each selected toolset. It does **not** dynamically load a domain schema after ChatGPT selects that domain. The opt-in `facade` toolset reduces initial discovery to five facade tools while retaining the same internal handlers; `core`/`advanced` keep the current 19-tool stable schema and `full` keeps the exhaustive compatibility schema.
 
 Capability metadata changes do not change `tools/list`; restart the Controller to load new code, but reconnect/rescan ChatGPT only when tool names or input schemas change.
 
@@ -45,6 +46,7 @@ Remote writes, destructive actions, outside-repository paths, and secret access
 
 - Prefer `rh_status`, `rh_access`, `rh_context`, `rh_work`, and `rh_inbox` for normal orchestration.
 - Use first-class Direct Edit, command, Git, `quick_agent_session`, Goal/Work, iOS, plugin, and artifact tools when the facade is not the shortest reliable path.
+- Use `--toolset facade` only for explicit experiments/clients until latency and workflow coverage are validated; the default remains the stable 19-tool surface.
 - Keep the stable surface unique and at or below 128 tools.
 - Add new public tools only when they unlock a real end-to-end workflow; otherwise route capabilities through an existing facade or plugin action.
 

package/docs/wiki/Architecture.md

@@ -75,11 +75,11 @@ One Canonical Runtime owns the active local execution authority and one whole-re
 
 ## Authoritative documents
 
-- [System overview](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/system-overview.md)
-- [Architecture invariants](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/architecture-invariants.md)
-- [Multi-repository execution](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/multi-repository-execution.md)
-- [Verification and release gates](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/verification-and-release-gates.md)
-- [Implementation status](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/implementation-status.md)
-- [Runtime directory map](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/runtime-directory-map.md)
+- [System overview](https://github.com/moretea-labs/forge/blob/main/docs/architecture/../architecture/CURRENT.md)
+- [Architecture invariants](https://github.com/moretea-labs/forge/blob/main/docs/architecture/../architecture/CURRENT.md)
+- [Multi-repository execution](https://github.com/moretea-labs/forge/blob/main/docs/architecture/../architecture/CURRENT.md)
+- [Verification and release gates](https://github.com/moretea-labs/forge/blob/main/docs/architecture/../architecture/CURRENT.md)
+- [Implementation status](https://github.com/moretea-labs/forge/blob/main/docs/architecture/../architecture/CURRENT.md)
+- [Runtime directory map](https://github.com/moretea-labs/forge/blob/main/docs/architecture/../architecture/CURRENT.md)
 
 Historical snapshots explain previous designs but are not current Runtime contracts.

package/docs/wiki/Implementation.md

@@ -143,8 +143,8 @@ Primary code and docs:
 ```text
 src/runtime/root/release-store.ts
 src/runtime/health/
-docs/architecture/current/failure-recovery.md
-docs/architecture/current/verification-and-release-gates.md
+docs/architecture/../architecture/CURRENT.md
+docs/architecture/../architecture/CURRENT.md
 ```
 
 The primary Runtime cannot be the only authority deciding its own recovery. Standalone Recovery observes the Runtime independently and may perform bounded whole-release restart/rollback only under its own evidence and lock contract.

package/docs/wiki/Integrations.md

@@ -18,9 +18,9 @@ GitHub operations cover issues, pull requests, checks, repository settings, Wiki
 
 Browser and local-system plugins are optional controller capabilities. They use separate grants and do not turn repository access into unrestricted machine access.
 
-## Google Workspace and personal workflows
+## Google Workspace
 
-Gmail, Calendar, Contacts, and related assistant routines remain connector-specific. Credentials and personal data are not stored in repository source.
+Gmail, Calendar, Contacts, and other Workspace integrations remain connector-specific. Credentials and personal data are not stored in repository source.
 
 ## Apple tooling
 

package/docs/wiki/Work-Lifecycle.md

@@ -28,4 +28,4 @@ Commit explicit paths, merge through the intended strategy, and record the integ
 
 Update task evidence, delete merged branches and temporary worktrees, and verify the target branch is clean. Blocked or failed states remain recoverable; they are not treated as immutable terminal truth.
 
-For detailed lifecycle contracts, see [Job and Run Lifecycle](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/job-and-run-lifecycle.md).
+For detailed lifecycle contracts, see [Job and Run Lifecycle](https://github.com/moretea-labs/forge/blob/main/docs/architecture/../architecture/CURRENT.md).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moretea-labs/forge",
-  "version": "1.6.0",
+  "version": "1.7.1",
   "description": "Local-first action assistant for software work with resumable execution, bounded tools, and reviewable evidence",
   "license": "MIT",
   "author": "Moretea Labs contributors",
@@ -54,8 +54,6 @@
     "docs/forge-chatgpt-mcp-setup.md",
     "docs/forge-github-issue-launcher.md",
     "docs/forge-runtime-self-healing-loop.md",
-    "docs/forge-autonomous-goal-loop.md",
-    "docs/forge-provider-configuration.md",
     "docs/forge-plugin-management.md",
     "README.en.md",
     "README.zh-CN.md",
@@ -83,7 +81,21 @@
     "check:controller-ui": "bun scripts/build-controller-ui.ts --check",
     "check:design": "npx -y @google/design.md@0.4.0 lint DESIGN.md",
     "benchmark:skills": "bun scripts/run-skill-evals.ts",
+    "benchmark:controller-hotpath": "bun scripts/benchmark-controller-hotpath.ts",
+    "benchmark:thin-harness-mcp-e2e": "bun scripts/benchmark-thin-harness-mcp-e2e.ts --json",
+    "benchmark:mcp-transport": "bun scripts/benchmark-mcp-transport.ts",
+    "benchmark:mcp-host": "bash scripts/benchmark-mcp-host.sh",
+    "benchmark:work-efficiency": "bun scripts/benchmark-work-efficiency.ts",
     "benchmark:route-session-concurrency": "bun scripts/benchmark-route-session-concurrency.ts",
+    "benchmark:quality-harness": "bun scripts/benchmark-quality-harness.ts",
+    "benchmark:background-check-overlap": "bun scripts/benchmark-background-check-overlap.ts",
+    "check:quality-harness": "bun scripts/benchmark-quality-harness.ts",
+    "check:evaluation-framework": "bun test tests/evaluation-framework.test.ts",
+    "check:background-check-overlap": "bun scripts/benchmark-background-check-overlap.ts",
+    "check:typescript-navigation": "bun scripts/benchmark-typescript-navigation.ts",
+    "check:semantic-navigation-providers": "bun test tests/runtime/semantic-navigation-provider.test.ts",
+    "check:check-scheduling": "bun test tests/runtime/check-scheduling.test.ts",
+    "check:bootstrap-files": "bun test tests/bootstrap-files.test.ts",
     "test": "bun scripts/test-governance.ts affected",
     "test:browser-live": "bun tests/live/browser-native-silent.e2e.ts",
     "test:core": "bun scripts/test-governance.ts core",
@@ -94,6 +106,8 @@
     "test:coverage": "bun test --coverage",
     "check:type": "bun x tsc --noEmit",
     "check:runtime-architecture": "node scripts/check-runtime-architecture.mjs",
+    "check:generated-authority": "node scripts/sync-generated-authority.mjs --check",
+    "check:source-duplication": "node scripts/check-source-duplication.mjs",
     "check:executable-modes": "bun scripts/repair-executable-modes.ts --check",
     "repair:executable-modes": "bun scripts/repair-executable-modes.ts",
     "check:test-governance": "bun scripts/test-governance.ts validate",
@@ -106,6 +120,7 @@
     "check:main": "bun scripts/run-governed-gate.ts main",
     "check:ci": "bun run check:main",
     "check:release": "bun scripts/run-governed-gate.ts release",
+    "check:stable-baseline": "bun scripts/check-stable-baseline.ts",
     "check:release-surface": "bash scripts/check-public-release-surface.sh",
     "check:release-readiness": "bash scripts/check-release-readiness.sh",
     "check:open-source-surface": "bash scripts/check-open-source-tracked-surface.sh",
@@ -125,8 +140,8 @@
     "check:context-files": "forge run check-context-files",
     "check:deploy-sql": "forge run check-deploy-sql-order",
     "check:architecture-sync": "forge run check-architecture-sync",
-    "check:task-sync": "node bin/forge.mjs run check-task-sync",
-    "check:task-workflow": "bash scripts/check-task-workflow.sh --strict",
+    "check:task-sync": "forge run check-task-sync",
+    "check:task-workflow": "forge run check-task-workflow --strict",
     "runtime:activate-source-baseline": "bun scripts/activate-source-baseline.ts request",
     "plugin:install-desktop-operator": "bun scripts/install-desktop-operator-registration.ts",
     "sync:brain-docs": "forge run sync-brain-docs --all",
@@ -138,15 +153,16 @@
     "test:bun": "bun -e 'console.error(\"[tests] test:bun is deprecated; running explicit test:full\")' && bun run test:full",
     "test:node-smoke": "node --test tests/node/*.test.mjs",
     "check:ci:portable": "FORGE_ALLOW_NODE_ONLY=1 bash scripts/check-ci.sh",
-    "dev:controller-ui": "vite --config src/cli/local-bridge/frontend/vite.config.ts"
+    "dev:controller-ui": "vite --config src/cli/local-bridge/frontend/vite.config.ts",
+    "prepack": "node scripts/sync-generated-authority.mjs --check"
   },
   "devDependencies": {
     "@colbymchenry/codegraph": "1.0.1",
     "@types/bun": "latest",
-    "@types/cors": "^2.8.17",
-    "@types/express": "^5.0.0",
-    "@types/react": "^19.2.0",
-    "@types/react-dom": "^19.2.0",
+    "@types/cors": "^2.8.19",
+    "@types/express": "^5.0.6",
+    "@types/react": "^19.2.18",
+    "@types/react-dom": "^19.2.4",
     "@vitejs/plugin-react": "^5.2.0",
     "vite": "^7.3.0"
   },
@@ -156,11 +172,17 @@
     "express": "^5.2.1",
     "playwright": "^1.54.1",
     "react": "^19.2.0",
-    "react-dom": "^19.2.0",
+    "react-dom": "^19.2.8",
     "typescript": "^6.0.3"
   },
   "packageManager": "npm@10.0.0",
   "optionalDependencies": {
+    "@colbymchenry/codegraph-darwin-arm64": "1.0.1",
+    "@colbymchenry/codegraph-darwin-x64": "1.0.1",
+    "@colbymchenry/codegraph-linux-arm64": "1.0.1",
+    "@colbymchenry/codegraph-linux-x64": "1.0.1",
+    "@colbymchenry/codegraph-win32-arm64": "1.0.1",
+    "@colbymchenry/codegraph-win32-x64": "1.0.1",
     "agent-device": "0.20.2"
   }
 }

package/scripts/activate-source-baseline.ts

@@ -64,19 +64,17 @@ interface CheckDefinition {
 const CHECKS: readonly CheckDefinition[] = [
   { id: 'package:check:type', args: ['run', 'check:type'], timeoutMs: 10 * 60_000 },
   { id: 'package:check:runtime-architecture', args: ['run', 'check:runtime-architecture'], timeoutMs: 3 * 60_000 },
-  {
-    id: 'focused:runtime-architecture-replacement',
-    args: [
-      'test',
-      'tests/runtime/process-runtime.test.ts',
-      'tests/runtime/work-terminal-cleanup.test.ts',
-      'tests/runtime/canonical-single-runtime.test.ts',
-      'tests/cli/runtime-command.test.ts',
-      'tests/runtime/stable-state-and-bootstrap.test.ts',
-      'tests/cli/mcp-controller.test.ts',
-    ],
-    timeoutMs: 15 * 60_000,
-  },
+  ...[
+    'tests/runtime/process-runtime.test.ts',
+    'tests/runtime/work-terminal-cleanup.test.ts',
+    'tests/runtime/canonical-single-runtime.test.ts',
+    'tests/cli/runtime-command.test.ts',
+    'tests/cli/mcp-http.test.ts',
+  ].map((path) => ({
+    id: `focused:runtime-architecture-replacement:${path}`,
+    args: ['test', '--max-concurrency', '1', `./${path}`],
+    timeoutMs: 5 * 60_000,
+  })),
   { id: 'package:test:core', args: ['run', 'test:core'], timeoutMs: 30 * 60_000 },
 ];
 
@@ -172,6 +170,12 @@ function terminalOutcome(handle: ReturnType<typeof listWorkHandles>[number]): Wo
 
 function cleanupSafety(repoRoot: string, worktreePath: string): { safe: boolean; reason?: string } {
   if (!existsSync(worktreePath)) return { safe: true };
+  const repository = runProcess('git', ['rev-parse', '--is-inside-work-tree'], {
+    cwd: worktreePath,
+    timeoutMs: 10_000,
+    maxOutputBytes: 100_000,
+  });
+  if (!repository.ok || repository.stdout.trim() !== 'true') return { safe: false, reason: 'WORKTREE_NOT_GIT_REPOSITORY' };
   const status = git(worktreePath, ['status', '--porcelain']);
   if (status) return { safe: false, reason: 'WORKTREE_DIRTY' };
   const head = git(worktreePath, ['rev-parse', 'HEAD']);