@cat-factory/executor-harness 1.129.0 → 1.131.0

package/dist/agent.js

@@ -861,6 +861,10 @@ export function buildSingleRepoCodingSpec(job, pushBranch) {
         guardLimits: job.guardLimits,
         ...(job.persistentCheckout ? { persistentCheckout: true } : {}),
         ...(job.streamFollowUps ? { streamFollowUps: true } : {}),
+        // The task's linked documents, materialised into `.cat-context/` for the agent to read on
+        // demand. Every other caller of `runAgentInWorkspace` forwards these; this spread was the one
+        // that did not, so the implementer's prompt named files its checkout had never been given.
+        ...(job.contextFiles?.length ? { contextFiles: job.contextFiles } : {}),
         // Whether a pull request will open at all is exactly `job.pr` (see the `if (job.pr)` guard in
         // `runSingleRepoCoding`), and it is what decides whether the repo's PR template is worth
         // resolving. Read off the same field rather than a new job-body flag, so the two can't drift.

package/dist/coding-agent.d.ts

@@ -1,4 +1,4 @@
-import type { HarnessAuthFields, ImageManifestSpec, RepoSpec, SkillSpec, McpServerSpec } from './job.js';
+import type { ContextFileSpec, HarnessAuthFields, ImageManifestSpec, RepoSpec, SkillSpec, McpServerSpec } from './job.js';
 import type { HarnessCallMetric } from './pi.js';
 import type { PiRunStats } from './pi-reduction.js';
 import { type EffortReport } from './effort.js';
@@ -99,6 +99,21 @@ export interface CodingAgentSpec extends HarnessAuthFields {
      * `docs/initiatives/bugfix-reproduction-proof.md`.
      */
     reproduction?: ReproductionSpec;
+    /**
+     * The run's LINKED CONTEXT documents (the task's attached brief, an RFC, a tracker issue body),
+     * materialised into `.cat-context/<path>` in the checkout and enumerated for the agent in its
+     * `AGENTS.md` context block. Absent ⇒ none.
+     *
+     * Carried here because the CODING agent is the one that needs them most and was the ONE path
+     * that dropped them: every sibling caller of {@link runAgentInWorkspace} (the explore paths, the
+     * conflict path, `multi-repo-coding.ts`) forwarded `job.contextFiles` and this one did not, so a
+     * task whose brief was too long for `description` and therefore rode an attached document
+     * reached the implementer as a prompt naming `.cat-context/<file>.md` and a checkout with no
+     * such directory. The agent then rebuilt the brief from whatever summary the prompt carried and
+     * reported the gap as a follow-up question, which is the most expensive way to discover a
+     * missing field spread.
+     */
+    contextFiles?: ContextFileSpec[];
     /**
      * The skills to make available for this run — a `skill` step's pick and/or the running kind's
      * declared playbooks. Threaded into {@link runAgentInWorkspace}, which installs them

package/dist/coding-agent.js

@@ -246,6 +246,8 @@ export async function runCodingAgent(spec, opts = {}) {
             webToolsGuidance: spec.webToolsGuidance,
             webSearchProxy: spec.webSearchProxy,
             guardLimits: spec.guardLimits,
+            // Materialised into `.cat-context/` and enumerated in the agent's AGENTS.md block.
+            ...(spec.contextFiles?.length ? { contextFiles: spec.contextFiles } : {}),
             ...(spec.skills?.length ? { skills: spec.skills } : {}),
             ...(spec.mcpServers?.length ? { mcpServers: spec.mcpServers } : {}),
             ...(spec.referenceScreenshots

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cat-factory/executor-harness",
-  "version": "1.129.0",
+  "version": "1.131.0",
   "description": "Container payload: a thin TypeScript wrapper that runs the Pi coding agent against a cloned repo and opens a PR. Runs in the Cloudflare Container (and, in local native mode, as a host process); carries no secrets.",
   "repository": {
     "type": "git",
@@ -25,14 +25,14 @@
     "access": "public"
   },
   "devDependencies": {
+    "@cat-factory/kernel": "0.318.0",
+    "@cat-factory/server": "0.305.0",
+    "@cat-factory/spend": "0.16.12",
     "@hono/node-server": "^2.1.1",
     "@types/node": "^26.2.0",
     "hono": "^4.13.3",
     "typescript": "7.0.2",
-    "vitest": "^4.1.11",
-    "@cat-factory/kernel": "0.316.0",
-    "@cat-factory/server": "0.302.0",
-    "@cat-factory/spend": "0.16.9"
+    "vitest": "^4.1.11"
   },
   "scripts": {
     "build": "tsc -p tsconfig.json",

package/src/agent.ts

@@ -1024,6 +1024,10 @@ export function buildSingleRepoCodingSpec(
     guardLimits: job.guardLimits,
     ...(job.persistentCheckout ? { persistentCheckout: true } : {}),
     ...(job.streamFollowUps ? { streamFollowUps: true } : {}),
+    // The task's linked documents, materialised into `.cat-context/` for the agent to read on
+    // demand. Every other caller of `runAgentInWorkspace` forwards these; this spread was the one
+    // that did not, so the implementer's prompt named files its checkout had never been given.
+    ...(job.contextFiles?.length ? { contextFiles: job.contextFiles } : {}),
     // Whether a pull request will open at all is exactly `job.pr` (see the `if (job.pr)` guard in
     // `runSingleRepoCoding`), and it is what decides whether the repo's PR template is worth
     // resolving. Read off the same field rather than a new job-body flag, so the two can't drift.

package/src/coding-agent.ts

@@ -2,6 +2,7 @@ import { mkdir } from 'node:fs/promises'
 import { join } from 'node:path'
 import { runCapturedCommand } from './captured-command.js'
 import type {
+  ContextFileSpec,
   HarnessAuthFields,
   ImageManifestSpec,
   RepoSpec,
@@ -162,6 +163,21 @@ export interface CodingAgentSpec extends HarnessAuthFields {
    * `docs/initiatives/bugfix-reproduction-proof.md`.
    */
   reproduction?: ReproductionSpec
+  /**
+   * The run's LINKED CONTEXT documents (the task's attached brief, an RFC, a tracker issue body),
+   * materialised into `.cat-context/<path>` in the checkout and enumerated for the agent in its
+   * `AGENTS.md` context block. Absent ⇒ none.
+   *
+   * Carried here because the CODING agent is the one that needs them most and was the ONE path
+   * that dropped them: every sibling caller of {@link runAgentInWorkspace} (the explore paths, the
+   * conflict path, `multi-repo-coding.ts`) forwarded `job.contextFiles` and this one did not, so a
+   * task whose brief was too long for `description` and therefore rode an attached document
+   * reached the implementer as a prompt naming `.cat-context/<file>.md` and a checkout with no
+   * such directory. The agent then rebuilt the brief from whatever summary the prompt carried and
+   * reported the gap as a follow-up question, which is the most expensive way to discover a
+   * missing field spread.
+   */
+  contextFiles?: ContextFileSpec[]
   /**
    * The skills to make available for this run — a `skill` step's pick and/or the running kind's
    * declared playbooks. Threaded into {@link runAgentInWorkspace}, which installs them
@@ -508,6 +524,8 @@ export async function runCodingAgent(
             webToolsGuidance: spec.webToolsGuidance,
             webSearchProxy: spec.webSearchProxy,
             guardLimits: spec.guardLimits,
+            // Materialised into `.cat-context/` and enumerated in the agent's AGENTS.md block.
+            ...(spec.contextFiles?.length ? { contextFiles: spec.contextFiles } : {}),
             ...(spec.skills?.length ? { skills: spec.skills } : {}),
             ...(spec.mcpServers?.length ? { mcpServers: spec.mcpServers } : {}),
             ...(spec.referenceScreenshots