product-console-companion 0.4.0 → 0.5.0

package/README.md

@@ -9,12 +9,12 @@ your own machine, so:
   `MAX_FILE_CHARS`/`MAX_TREE_PATHS` don't apply here at all);
 - AI spend bills against your own key/subscription, not the workspace's shared/BYOK credential.
 
-Covers every AI call the hosted Console makes that reads your code — six task kinds as of this
-release (`verify_module` — "Check against code" on a module card; `generate_spec_batch` —
-writing full specs during setup; `propose_skeleton` and `propose_new_capabilities` — the two
-shallow whole-repo scans; `design_prompt` — the free-text export; `analyse_shipment` — the
-passive per-commit drift check behind the GitHub webhook and the "Check GitHub" button), two
-backends, chosen per connection at `connect` time:
+Runs every AI task the hosted Console dispatches. That includes the repo-aware setup and code
+checks as well as graph reasoning such as impact analysis, reviews, coupling maps, graph Q&A,
+edge descriptions, and exports. Graph-reasoning tasks receive all of their context from the
+Console and run connectionless with zero filesystem access. New server-side graph-reasoning task
+kinds use the same safe fallback without requiring another companion release. Two backends are
+available, chosen per connection at `connect` time:
 
 - **`api-key`** (default) — no CLI dependency. Calls Anthropic directly with your own API key
   (`api-key-caller.ts`), running its own two-pass file-select-then-judge, mirroring

package/dist/api-key-caller.js

@@ -300,7 +300,16 @@ ${repoCtx.packageJson ?? '(none found)'}
     const text = message.content.find((b) => b.type === 'text');
     if (!text || text.type !== 'text')
         throw new Error('No result returned.');
-    return { result: JSON.parse(text.text), filesRead: [] };
+    return { result: spec.schema ? JSON.parse(text.text) : text.text, filesRead: [] };
+}
+/** Forward-compatible fallback for server-created graph/spec reasoning tasks. The server sends
+ *  the complete self-describing spec, so these calls never need or receive filesystem context. */
+export async function runGenericTask(client, task, repoPath) {
+    const spec = task.payload?.spec;
+    if (!spec || typeof spec !== 'object' || Array.isArray(spec)) {
+        throw new Error(`Cannot run task kind "${task.kind}": payload.spec is missing or not an object.`);
+    }
+    return runShallowRepoTask(client, spec, repoPath, true);
 }
 export async function runProposeSkeletonTask(client, task, repoPath) {
     const payload = task.payload;

package/dist/claude-cli-caller.js

@@ -135,6 +135,15 @@ async function runViaCli(spec, maxBudgetUsd, repoPath, connectionless = false) {
         await sandbox.cleanup();
     }
 }
+/** Forward-compatible fallback for server-created graph/spec reasoning tasks. The server sends
+ *  the complete self-describing spec, so these calls run connectionless with zero tools. */
+export async function runGenericTaskViaCli(task, repoPath) {
+    const spec = task.payload?.spec;
+    if (!spec || typeof spec !== 'object' || Array.isArray(spec)) {
+        throw new Error(`Cannot run task kind "${task.kind}": payload.spec is missing or not an object.`);
+    }
+    return runViaCli(spec, task.maxBudgetUsd, repoPath, true);
+}
 export async function runVerifyModuleTaskViaCli(task, repoPath) {
     const payload = task.payload;
     return runViaCli(payload.spec, task.maxBudgetUsd, repoPath);

package/dist/cli.js

@@ -5,8 +5,8 @@ import { resolve } from 'node:path';
 import { addConnection, configPath, enableWorkspacePolling, loadConfig } from './config.js';
 import { CompanionClient, CompanionHttpError } from './http-client.js';
 import { assertIsRepo, currentCommit } from './local-scan.js';
-import { runAnalyseShipmentTask, runDesignPromptTask, runGenerateSpecBatchTask, runProposeNewCapabilitiesTask, runProposeSkeletonTask, runVerifyModuleTask } from './api-key-caller.js';
-import { runAnalyseShipmentTaskViaCli, runDesignPromptTaskViaCli, runGenerateSpecBatchTaskViaCli, runProposeNewCapabilitiesTaskViaCli, runProposeSkeletonTaskViaCli, runVerifyModuleTaskViaCli } from './claude-cli-caller.js';
+import { runAnalyseShipmentTask, runDesignPromptTask, runGenerateSpecBatchTask, runGenericTask, runProposeNewCapabilitiesTask, runProposeSkeletonTask, runVerifyModuleTask } from './api-key-caller.js';
+import { runAnalyseShipmentTaskViaCli, runDesignPromptTaskViaCli, runGenerateSpecBatchTaskViaCli, runGenericTaskViaCli, runProposeNewCapabilitiesTaskViaCli, runProposeSkeletonTaskViaCli, runVerifyModuleTaskViaCli } from './claude-cli-caller.js';
 /** A flag with nothing after it (end of argv, or the next token is itself another "--flag") is
  *  treated as a bare boolean ("true") rather than swallowing the following flag as its value —
  *  needed for --no-run below. Every existing "--flag value" pair still parses exactly as before. */
@@ -136,9 +136,11 @@ const IDLE_POLL_MS = 5000;
 /** How often to extend a claimed task's lease while it's in flight — comfortably inside the
  *  server's ~2-minute lease window (server/store.ts's LOCAL_TASK_LEASE_MS). */
 const HEARTBEAT_MS = 30_000;
-/** The task-kind registry, companion-side — one entry per kind this companion knows how to run,
- *  each backed by both backends. Grows by one entry per phase, same as the server's own registry
- *  (server/companion.ts's TASK_RESULT_SCHEMAS) — the two lists should always name the same kinds. */
+/** The explicitly repo-aware task kinds, companion-side. Everything else falls through to a
+ *  connectionless runner: only our server creates tasks, their ModelTaskSpec is self-describing
+ *  (model, effort, maxTokens, system, stable/volatile text, optional schema), and graph reasoning
+ *  has nothing legitimate to read from disk. That also makes future server kinds work without a
+ *  companion release. */
 async function runTask(task, backend, anthropic, repoPath) {
     if (task.kind === 'verify_module') {
         return backend === 'cli' ? runVerifyModuleTaskViaCli(task, repoPath) : runVerifyModuleTask(anthropic, task, repoPath); // anthropic is always set for backend 'api-key' — see cmdRun
@@ -158,7 +160,7 @@ async function runTask(task, backend, anthropic, repoPath) {
     if (task.kind === 'analyse_shipment') {
         return backend === 'cli' ? runAnalyseShipmentTaskViaCli(task, repoPath) : runAnalyseShipmentTask(anthropic, task, repoPath);
     }
-    throw new Error(`This companion doesn't know how to run task kind "${task.kind}" yet.`);
+    return backend === 'cli' ? runGenericTaskViaCli(task, repoPath) : runGenericTask(anthropic, task, repoPath);
 }
 async function runOneTask(anthropic, backend, client, repoPath, task) {
     console.log(`[${new Date().toISOString()}] claimed ${task.kind} task ${task.id} via ${backend} (budget $${task.maxBudgetUsd.toFixed(2)} — not yet enforced client-side, see README)`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "product-console-companion",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Local-first BYOS companion for the Fynch Product Console — reads code and runs AI calls from your own machine instead of the hosted server.",
   "type": "module",
   "license": "MIT",