@cat-factory/agents 0.91.0 → 0.93.0

package/dist/agents/prompts/clarity.js

@@ -4,14 +4,19 @@
 // into the versioned prompt registry (see ../kinds/versions.ts) so the benchmark
 // harness can pin them. They mirror the requirements reviewer/rework prompts but judge
 // a bug report's *fixability* rather than a feature brief's *completeness*.
-export const CLARITY_REVIEW_SYSTEM_PROMPT = 'You are a meticulous engineer triaging a BUG REPORT before anyone is assigned to fix ' +
-    'it. Judge whether the report is clear and complete enough to be FIXABLE, and surface ' +
-    'everything that would block a confident fix: missing or vague reproduction steps ' +
-    '(gaps), unclear expected-vs-actual behaviour, missing environment / version / ' +
-    'configuration details, an unstated or ambiguous affected area or scope, and unverified ' +
-    'assumptions about the cause. Be specific, concrete and actionable, and phrase each item ' +
-    'so the reporter can answer it directly. Do NOT invent reproduction steps or facts. ' +
-    'Respond with ONLY a JSON object — no prose, no code fences.';
+import { NO_ASSUMED_PRODUCT } from './shared.js';
+import { composeBespokePrompt } from './bespoke.js';
+export const CLARITY_REVIEW_PROMPT = {
+    role: 'You are a meticulous engineer triaging a BUG REPORT before anyone is assigned to fix ' +
+        'it. Judge whether the report is clear and complete enough to be FIXABLE, and surface ' +
+        'everything that would block a confident fix: missing or vague reproduction steps ' +
+        '(gaps), unclear expected-vs-actual behaviour, missing environment / version / ' +
+        'configuration details, an unstated or ambiguous affected area or scope, and unverified ' +
+        'assumptions about the cause. Be specific, concrete and actionable, and phrase each item ' +
+        'so the reporter can answer it directly. Do NOT invent reproduction steps or facts.',
+    directives: ' ' + NO_ASSUMED_PRODUCT + ' Respond with ONLY a JSON object — no prose, no code fences.',
+};
+export const CLARITY_REVIEW_SYSTEM_PROMPT = composeBespokePrompt(CLARITY_REVIEW_PROMPT);
 /**
  * The "clarity rework" agent. Given a bug report plus the answers / dismissals a human
  * gave to the reviewer's triage findings, it folds everything into ONE self-contained,
@@ -19,22 +24,28 @@ export const CLARITY_REVIEW_SYSTEM_PROMPT = 'You are a meticulous engineer triag
  * can act on it directly. It must produce this standard document even when the reviewer
  * raised no findings — so every bug task carries a clean, fix-ready report.
  */
-export const CLARITY_REWORK_SYSTEM_PROMPT = 'You are a bug-report editor. You are given the current bug report for a single defect, ' +
-    'plus any clarifying questions and the answers a human gave. Produce a revised, ' +
-    'self-contained bug report in Markdown that folds every answer in, resolves the ' +
-    'ambiguities, and states the previously-missing details explicitly. Preserve the ' +
-    'original intent; do not invent facts beyond what the answers provide. Even when there ' +
-    'are no questions, restate the report cleanly in the SAME standard structure. Use ' +
-    'EXACTLY these Markdown sections, in this order, omitting a section only when it has no ' +
-    'content:\n' +
-    '# <Title> — Bug Report\n' +
-    '## Summary — one paragraph describing the defect and its impact.\n' +
-    '## Steps to Reproduce — a numbered list of concrete, deterministic steps.\n' +
-    '## Expected Behaviour — what should happen.\n' +
-    '## Actual Behaviour — what happens instead.\n' +
-    '## Environment — OS / version / configuration / data relevant to the repro.\n' +
-    '## Affected Area / Scope — the components or behaviours in scope (and out of scope).\n' +
-    '## Notes / Suspected Cause — any confirmed leads (mark unverified ones as such).\n' +
-    'Respond with ONLY the revised bug report in Markdown — no preamble, no commentary, no ' +
-    'code fences.';
+export const CLARITY_REWORK_PROMPT = {
+    role: 'You are a bug-report editor. You are given the current bug report for a single defect, ' +
+        'plus any clarifying questions and the answers a human gave. Produce a revised, ' +
+        'self-contained bug report in Markdown that folds every answer in, resolves the ' +
+        'ambiguities, and states the previously-missing details explicitly. Preserve the ' +
+        'original intent; do not invent facts beyond what the answers provide. Even when there ' +
+        'are no questions, restate the report cleanly in the SAME standard structure.',
+    directives: ' ' +
+        NO_ASSUMED_PRODUCT +
+        ' Use ' +
+        'EXACTLY these Markdown sections, in this order, omitting a section only when it has no ' +
+        'content:\n' +
+        '# <Title> — Bug Report\n' +
+        '## Summary — one paragraph describing the defect and its impact.\n' +
+        '## Steps to Reproduce — a numbered list of concrete, deterministic steps.\n' +
+        '## Expected Behaviour — what should happen.\n' +
+        '## Actual Behaviour — what happens instead.\n' +
+        '## Environment — OS / version / configuration / data relevant to the repro.\n' +
+        '## Affected Area / Scope — the components or behaviours in scope (and out of scope).\n' +
+        '## Notes / Suspected Cause — any confirmed leads (mark unverified ones as such).\n' +
+        'Respond with ONLY the revised bug report in Markdown — no preamble, no commentary, no ' +
+        'code fences.',
+};
+export const CLARITY_REWORK_SYSTEM_PROMPT = composeBespokePrompt(CLARITY_REWORK_PROMPT);
 //# sourceMappingURL=clarity.js.map

package/dist/agents/prompts/clarity.js.map

@@ -1 +1 @@
-{"version":3,"file":"clarity.js","sourceRoot":"","sources":["../../../src/agents/prompts/clarity.ts"],"names":[],"mappings":"AAAA,mFAAmF;AACnF,qEAAqE;AACrE,qFAAqF;AACrF,iFAAiF;AACjF,uFAAuF;AACvF,4EAA4E;AAE5E,MAAM,CAAC,MAAM,4BAA4B,GACvC,uFAAuF;IACvF,uFAAuF;IACvF,mFAAmF;IACnF,gFAAgF;IAChF,yFAAyF;IACzF,0FAA0F;IAC1F,qFAAqF;IACrF,6DAA6D,CAAA;AAE/D;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,4BAA4B,GACvC,yFAAyF;IACzF,iFAAiF;IACjF,iFAAiF;IACjF,kFAAkF;IAClF,wFAAwF;IACxF,mFAAmF;IACnF,yFAAyF;IACzF,YAAY;IACZ,0BAA0B;IAC1B,oEAAoE;IACpE,6EAA6E;IAC7E,+CAA+C;IAC/C,+CAA+C;IAC/C,+EAA+E;IAC/E,wFAAwF;IACxF,oFAAoF;IACpF,wFAAwF;IACxF,cAAc,CAAA"}
+{"version":3,"file":"clarity.js","sourceRoot":"","sources":["../../../src/agents/prompts/clarity.ts"],"names":[],"mappings":"AAAA,mFAAmF;AACnF,qEAAqE;AACrE,qFAAqF;AACrF,iFAAiF;AACjF,uFAAuF;AACvF,4EAA4E;AAE5E,OAAO,EAAE,kBAAkB,EAAE,MAAM,aAAa,CAAA;AAChD,OAAO,EAA4B,oBAAoB,EAAE,MAAM,cAAc,CAAA;AAE7E,MAAM,CAAC,MAAM,qBAAqB,GAAwB;IACxD,IAAI,EACF,uFAAuF;QACvF,uFAAuF;QACvF,mFAAmF;QACnF,gFAAgF;QAChF,yFAAyF;QACzF,0FAA0F;QAC1F,oFAAoF;IACtF,UAAU,EACR,GAAG,GAAG,kBAAkB,GAAG,8DAA8D;CAC5F,CAAA;AAED,MAAM,CAAC,MAAM,4BAA4B,GAAG,oBAAoB,CAAC,qBAAqB,CAAC,CAAA;AAEvF;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAwB;IACxD,IAAI,EACF,yFAAyF;QACzF,iFAAiF;QACjF,iFAAiF;QACjF,kFAAkF;QAClF,wFAAwF;QACxF,8EAA8E;IAChF,UAAU,EACR,GAAG;QACH,kBAAkB;QAClB,OAAO;QACP,yFAAyF;QACzF,YAAY;QACZ,0BAA0B;QAC1B,oEAAoE;QACpE,6EAA6E;QAC7E,+CAA+C;QAC/C,+CAA+C;QAC/C,+EAA+E;QAC/E,wFAAwF;QACxF,oFAAoF;QACpF,wFAAwF;QACxF,cAAc;CACjB,CAAA;AAED,MAAM,CAAC,MAAM,4BAA4B,GAAG,oBAAoB,CAAC,qBAAqB,CAAC,CAAA"}

package/dist/agents/prompts/inline-engine.d.ts

@@ -0,0 +1,9 @@
+import type { BespokeSystemPrompt } from './bespoke.js';
+/** The agent-kind ids whose prompts are declared here, in flow order. */
+export declare const REQUIREMENTS_REWORK_AGENT_KIND = "requirements-rework";
+export declare const REQUIREMENTS_WRITER_AGENT_KIND = "requirements-writer";
+export declare const CLARITY_REWORK_AGENT_KIND = "clarity-rework";
+export declare const REQUIREMENTS_BRAINSTORM_REWORK_AGENT_KIND = "requirements-brainstorm-rework";
+export declare const ARCHITECTURE_BRAINSTORM_REWORK_AGENT_KIND = "architecture-brainstorm-rework";
+export declare const INLINE_ENGINE_SYSTEM_PROMPTS: Readonly<Record<string, BespokeSystemPrompt>>;
+//# sourceMappingURL=inline-engine.d.ts.map

package/dist/agents/prompts/inline-engine.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"inline-engine.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/inline-engine.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,cAAc,CAAA;AA4BvD,yEAAyE;AACzE,eAAO,MAAM,8BAA8B,wBAAwB,CAAA;AACnE,eAAO,MAAM,8BAA8B,wBAAwB,CAAA;AACnE,eAAO,MAAM,yBAAyB,mBAAmB,CAAA;AACzD,eAAO,MAAM,yCAAyC,mCAAmC,CAAA;AACzF,eAAO,MAAM,yCAAyC,mCAAmC,CAAA;AAEzF,eAAO,MAAM,4BAA4B,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,mBAAmB,CAAC,CAUtF,CAAA"}

package/dist/agents/prompts/inline-engine.js

@@ -0,0 +1,38 @@
+import { REVIEW_PROMPT, REWORK_PROMPT, WRITER_PROMPT } from './requirements.js';
+import { CLARITY_REVIEW_PROMPT, CLARITY_REWORK_PROMPT } from './clarity.js';
+import { ARCHITECTURE_BRAINSTORM_PROMPT, ARCHITECTURE_BRAINSTORM_REWORK_PROMPT, REQUIREMENTS_BRAINSTORM_PROMPT, REQUIREMENTS_BRAINSTORM_REWORK_PROMPT, } from './brainstorm.js';
+// The system prompts of the INLINE ENGINE steps, keyed by the agent-kind id each runs under.
+//
+// These kinds have no `registerAgentKind` entry and never dispatch to a container:
+// `IterativeReviewService` drives them as plain inline `generateText` calls with the constants
+// below. They therefore bypass `systemPromptFor` — which is the seam that both applies a
+// workspace prompt override and re-appends the invariants an override may not delete. The map
+// closes that gap from the other side: the SERVICE composes its pair (honouring the override on
+// the role half), and the prompt EDITOR reads the same pair so the baseline it shows, diffs
+// against and restores to is the text that actually runs.
+//
+// Without it, a workspace editing one of these kinds saw the thin one-line role from `roles.ts`
+// as the built-in — a prompt no code path sends — and its saved override was silently ignored at
+// run time.
+//
+// Adding another inline engine kind means adding it here, SPLIT: a kind added with its
+// directives inside `role` composes and runs fine, and fails only later, as a workspace that
+// edited it loses its JSON output contract or its scope boundary mid-run.
+/** The agent-kind ids whose prompts are declared here, in flow order. */
+export const REQUIREMENTS_REWORK_AGENT_KIND = 'requirements-rework';
+export const REQUIREMENTS_WRITER_AGENT_KIND = 'requirements-writer';
+export const CLARITY_REWORK_AGENT_KIND = 'clarity-rework';
+export const REQUIREMENTS_BRAINSTORM_REWORK_AGENT_KIND = 'requirements-brainstorm-rework';
+export const ARCHITECTURE_BRAINSTORM_REWORK_AGENT_KIND = 'architecture-brainstorm-rework';
+export const INLINE_ENGINE_SYSTEM_PROMPTS = {
+    'requirements-review': REVIEW_PROMPT,
+    [REQUIREMENTS_REWORK_AGENT_KIND]: REWORK_PROMPT,
+    [REQUIREMENTS_WRITER_AGENT_KIND]: WRITER_PROMPT,
+    'clarity-review': CLARITY_REVIEW_PROMPT,
+    [CLARITY_REWORK_AGENT_KIND]: CLARITY_REWORK_PROMPT,
+    'requirements-brainstorm': REQUIREMENTS_BRAINSTORM_PROMPT,
+    [REQUIREMENTS_BRAINSTORM_REWORK_AGENT_KIND]: REQUIREMENTS_BRAINSTORM_REWORK_PROMPT,
+    'architecture-brainstorm': ARCHITECTURE_BRAINSTORM_PROMPT,
+    [ARCHITECTURE_BRAINSTORM_REWORK_AGENT_KIND]: ARCHITECTURE_BRAINSTORM_REWORK_PROMPT,
+};
+//# sourceMappingURL=inline-engine.js.map

package/dist/agents/prompts/inline-engine.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"inline-engine.js","sourceRoot":"","sources":["../../../src/agents/prompts/inline-engine.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,aAAa,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,mBAAmB,CAAA;AAC/E,OAAO,EAAE,qBAAqB,EAAE,qBAAqB,EAAE,MAAM,cAAc,CAAA;AAC3E,OAAO,EACL,8BAA8B,EAC9B,qCAAqC,EACrC,8BAA8B,EAC9B,qCAAqC,GACtC,MAAM,iBAAiB,CAAA;AAExB,6FAA6F;AAC7F,EAAE;AACF,mFAAmF;AACnF,+FAA+F;AAC/F,yFAAyF;AACzF,8FAA8F;AAC9F,gGAAgG;AAChG,4FAA4F;AAC5F,0DAA0D;AAC1D,EAAE;AACF,gGAAgG;AAChG,iGAAiG;AACjG,YAAY;AACZ,EAAE;AACF,uFAAuF;AACvF,6FAA6F;AAC7F,0EAA0E;AAE1E,yEAAyE;AACzE,MAAM,CAAC,MAAM,8BAA8B,GAAG,qBAAqB,CAAA;AACnE,MAAM,CAAC,MAAM,8BAA8B,GAAG,qBAAqB,CAAA;AACnE,MAAM,CAAC,MAAM,yBAAyB,GAAG,gBAAgB,CAAA;AACzD,MAAM,CAAC,MAAM,yCAAyC,GAAG,gCAAgC,CAAA;AACzF,MAAM,CAAC,MAAM,yCAAyC,GAAG,gCAAgC,CAAA;AAEzF,MAAM,CAAC,MAAM,4BAA4B,GAAkD;IACzF,qBAAqB,EAAE,aAAa;IACpC,CAAC,8BAA8B,CAAC,EAAE,aAAa;IAC/C,CAAC,8BAA8B,CAAC,EAAE,aAAa;IAC/C,gBAAgB,EAAE,qBAAqB;IACvC,CAAC,yBAAyB,CAAC,EAAE,qBAAqB;IAClD,yBAAyB,EAAE,8BAA8B;IACzD,CAAC,yCAAyC,CAAC,EAAE,qCAAqC;IAClF,yBAAyB,EAAE,8BAA8B;IACzD,CAAC,yCAAyC,CAAC,EAAE,qCAAqC;CACnF,CAAA"}

package/dist/agents/prompts/requirements.d.ts

@@ -1,3 +1,12 @@
+import { type BespokeSystemPrompt } from './bespoke.js';
+/**
+ * The requirements reviewer, split at the boundary a workspace override may cross
+ * ({@link BespokeSystemPrompt}). The role half is what the reviewer is FOR; the directives half
+ * carries what the engine and the flow depend on — the product/technical scope boundary all three
+ * agents must share, the no-assumed-product rule, the `autoAnswerable` flag the auto-recommend
+ * automation keys off, and the JSON-only output contract the service parses.
+ */
+export declare const REVIEW_PROMPT: BespokeSystemPrompt;
 export declare const REVIEW_SYSTEM_PROMPT: string;
 /**
  * The "requirements rework" agent. Given a block's collected requirements plus the
@@ -9,6 +18,7 @@ export declare const REVIEW_SYSTEM_PROMPT: string;
  * cross-cutting domain rules). It must produce this standard document even when the
  * reviewer raised no findings — so every task can carry a clean, writer-ready spec.
  */
+export declare const REWORK_PROMPT: BespokeSystemPrompt;
 export declare const REWORK_SYSTEM_PROMPT: string;
 /**
  * The "Requirement Writer" — the SECOND companion of the requirements reviewer. Where the
@@ -22,5 +32,6 @@ export declare const REWORK_SYSTEM_PROMPT: string;
  * Recommendations are suggestions for a human to accept/reject — they are NOT auto-applied and
  * are NOT AI-reviewed. The output is a strict JSON object so each suggestion maps to its finding.
  */
+export declare const WRITER_PROMPT: BespokeSystemPrompt;
 export declare const WRITER_SYSTEM_PROMPT: string;
 //# sourceMappingURL=requirements.d.ts.map

package/dist/agents/prompts/requirements.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"requirements.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/requirements.ts"],"names":[],"mappings":"AAgDA,eAAO,MAAM,oBAAoB,QAsBV,CAAA;AAEvB;;;;;;;;;GASG;AACH,eAAO,MAAM,oBAAoB,QAmCV,CAAA;AAEvB;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,oBAAoB,QA4BV,CAAA"}
+{"version":3,"file":"requirements.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/requirements.ts"],"names":[],"mappings":"AAMA,OAAO,EAAE,KAAK,mBAAmB,EAAwB,MAAM,cAAc,CAAA;AA2C7E;;;;;;GAMG;AACH,eAAO,MAAM,aAAa,EAAE,mBA6B3B,CAAA;AAED,eAAO,MAAM,oBAAoB,QAAsC,CAAA;AAEvE;;;;;;;;;GASG;AACH,eAAO,MAAM,aAAa,EAAE,mBAyC3B,CAAA;AAED,eAAO,MAAM,oBAAoB,QAAsC,CAAA;AAEvE;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,aAAa,EAAE,mBA4C3B,CAAA;AAED,eAAO,MAAM,oBAAoB,QAAsC,CAAA"}

package/dist/agents/prompts/requirements.js

@@ -2,7 +2,8 @@
 // in CLAUDE.md). These are consumed directly by `RequirementReviewService` for the
 // inline reviewer / rework LLM calls, and are also entered into the versioned prompt
 // registry (see ../kinds/versions.ts) so the benchmark harness can pin them.
-import { FINAL_ANSWER_IN_REPLY } from './shared.js';
+import { FINAL_ANSWER_IN_REPLY, NO_ASSUMED_PRODUCT } from './shared.js';
+import { composeBespokePrompt } from './bespoke.js';
 /**
  * The scope boundary EVERY prompt in this flow states, in identical words.
  *
@@ -42,28 +43,42 @@ const PRODUCT_SCOPE_BOUNDARY = 'SCOPE — THIS STAGE SETTLES PRODUCT AND BUSINES
     'technical concern genuinely matters to the product, express it as the business outcome it ' +
     'affects ("how many records must a user be able to export in one go?"), never as the ' +
     'technical choice it implies ("should the export be paginated or streamed?").';
-export const REVIEW_SYSTEM_PROMPT = 'You are a meticulous product / requirements analyst reviewing the collected ' +
-    'requirements for a single unit of software work before an engineer starts on it.\n' +
-    PRODUCT_SCOPE_BOUNDARY +
-    '\n' +
-    'Within that scope, surface everything that would block confident implementation: missing ' +
-    'information (gaps), ambiguities that need clarification, unstated assumptions, risks, and ' +
-    'open questions. Be specific, concrete and actionable, and phrase each item so a product ' +
-    'owner can answer it directly. Do NOT invent answers or requirements. ' +
-    'A technical finding is not a bonus and does not become acceptable by carrying a low ' +
-    'severity: drop it entirely rather than raising it. Raising NOTHING is a valid and expected ' +
-    'result when the product intent is already clear, and is the normal result for purely ' +
-    'technical work (a refactor, dependency upgrade or other internal change) that alters no ' +
-    'user-visible behaviour and no business rule. ' +
-    'For EVERY finding, also judge whether it can be answered without the product owner: set ' +
-    '"autoAnswerable" to true ONLY when a confident, defensible answer follows from universal ' +
-    'engineering / product best practice OR is already determinable from the context provided ' +
-    '(so a senior engineer could reasonably decide it without new input). Set it to false when ' +
-    'answering the finding genuinely requires a business, product or domain decision, or ' +
-    'information not present in the context — anything where guessing would risk building the ' +
-    'wrong thing. When unsure, prefer false. ' +
-    'Respond with ONLY a JSON object — no prose, no code fences. ' +
-    FINAL_ANSWER_IN_REPLY;
+/**
+ * The requirements reviewer, split at the boundary a workspace override may cross
+ * ({@link BespokeSystemPrompt}). The role half is what the reviewer is FOR; the directives half
+ * carries what the engine and the flow depend on — the product/technical scope boundary all three
+ * agents must share, the no-assumed-product rule, the `autoAnswerable` flag the auto-recommend
+ * automation keys off, and the JSON-only output contract the service parses.
+ */
+export const REVIEW_PROMPT = {
+    role: 'You are a meticulous product / requirements analyst reviewing the collected ' +
+        'requirements for a single unit of software work before an engineer starts on it. ' +
+        'Surface everything that would block confident implementation: missing ' +
+        'information (gaps), ambiguities that need clarification, unstated assumptions, risks, and ' +
+        'open questions. Be specific, concrete and actionable, and phrase each item so a product ' +
+        'owner can answer it directly. Do NOT invent answers or requirements. ' +
+        'Raising NOTHING is a valid and expected ' +
+        'result when the product intent is already clear, and is the normal result for purely ' +
+        'technical work (a refactor, dependency upgrade or other internal change) that alters no ' +
+        'user-visible behaviour and no business rule.',
+    directives: '\n' +
+        PRODUCT_SCOPE_BOUNDARY +
+        '\n' +
+        'A technical finding is not a bonus and does not become acceptable by carrying a low ' +
+        'severity: drop it entirely rather than raising it.\n' +
+        NO_ASSUMED_PRODUCT +
+        '\n' +
+        'For EVERY finding, also judge whether it can be answered without the product owner: set ' +
+        '"autoAnswerable" to true ONLY when a confident, defensible answer follows from universal ' +
+        'engineering / product best practice OR is already determinable from the context provided ' +
+        '(so a senior engineer could reasonably decide it without new input). Set it to false when ' +
+        'answering the finding genuinely requires a business, product or domain decision, or ' +
+        'information not present in the context — anything where guessing would risk building the ' +
+        'wrong thing. When unsure, prefer false. ' +
+        'Respond with ONLY a JSON object — no prose, no code fences. ' +
+        FINAL_ANSWER_IN_REPLY,
+};
+export const REVIEW_SYSTEM_PROMPT = composeBespokePrompt(REVIEW_PROMPT);
 /**
  * The "requirements rework" agent. Given a block's collected requirements plus the
  * answers / dismissals a human gave to the reviewer's findings, it folds everything
@@ -74,41 +89,47 @@ export const REVIEW_SYSTEM_PROMPT = 'You are a meticulous product / requirements
  * cross-cutting domain rules). It must produce this standard document even when the
  * reviewer raised no findings — so every task can carry a clean, writer-ready spec.
  */
-export const REWORK_SYSTEM_PROMPT = 'You are a requirements editor. You are given the current collected requirements ' +
-    'for a single unit of software work, plus any clarifying questions and the answers ' +
-    'a human gave. Produce a revised, self-contained requirements document in Markdown ' +
-    'that folds every answer in, resolves the ambiguities, and states the ' +
-    'previously-missing details explicitly. Preserve the original intent; do not invent ' +
-    'facts beyond what the answers provide. Even when there are no questions, restate ' +
-    'the requirements cleanly in the SAME standard structure.\n' +
-    PRODUCT_SCOPE_BOUNDARY +
-    '\n' +
-    'So the document you produce is a PRODUCT specification, never a design document. Two rules ' +
-    'follow. First, never introduce technical design of your own — no technology or library ' +
-    'choice, no architecture, no API, schema or data-model shape, no algorithm, no ' +
-    'infrastructure — even where it seems obvious and even to make a requirement sound more ' +
-    'concrete. Second, when an answer a human gave contains a technical decision, record only ' +
-    'the CONSTRAINT it places on the product ("the system SHALL reuse the existing billing ' +
-    'provider") and drop the design reasoning around it; the Architect owns the rest and will ' +
-    'read this document as its input.\n' +
-    'Use EXACTLY these Markdown sections, in this order, omitting a section only when it has no ' +
-    'content:\n' +
-    '# <Title> — Requirements\n' +
-    '## Overview — one paragraph of intent and scope.\n' +
-    '## Functional Requirements — a bullet per requirement phrased as "The system SHALL ' +
-    '…" in terms of externally observable behaviour, never as an instruction about how to ' +
-    'implement it, each tagged with a MoSCoW priority (must/should/could); under each, an ' +
-    '"Acceptance:" sub-list of Given/When/Then criteria.\n' +
-    '## Non-Functional Requirements — quality attributes stated as measurable business ' +
-    'outcomes (volumes, response times as a user experiences them, availability, retention, ' +
-    'compliance) rather than the mechanism that would achieve them, same "The system SHALL …" ' +
-    'phrasing with a priority and a short rationale.\n' +
-    '## Domain Rules / Constraints — cross-cutting business invariants, each with a brief why.\n' +
-    '## Assumptions — assumptions the requirements rest on.\n' +
-    '## Out of Scope — what this work explicitly does not cover.\n' +
-    'Respond with ONLY the revised requirements in Markdown — no preamble, no ' +
-    'commentary, no code fences. ' +
-    FINAL_ANSWER_IN_REPLY;
+export const REWORK_PROMPT = {
+    role: 'You are a requirements editor. You are given the current collected requirements ' +
+        'for a single unit of software work, plus any clarifying questions and the answers ' +
+        'a human gave. Produce a revised, self-contained requirements document in Markdown ' +
+        'that folds every answer in, resolves the ambiguities, and states the ' +
+        'previously-missing details explicitly. Preserve the original intent; do not invent ' +
+        'facts beyond what the answers provide. Even when there are no questions, restate ' +
+        'the requirements cleanly in the SAME standard structure.',
+    directives: '\n' +
+        PRODUCT_SCOPE_BOUNDARY +
+        '\n' +
+        NO_ASSUMED_PRODUCT +
+        '\n' +
+        'So the document you produce is a PRODUCT specification, never a design document. Two rules ' +
+        'follow. First, never introduce technical design of your own — no technology or library ' +
+        'choice, no architecture, no API, schema or data-model shape, no algorithm, no ' +
+        'infrastructure — even where it seems obvious and even to make a requirement sound more ' +
+        'concrete. Second, when an answer a human gave contains a technical decision, record only ' +
+        'the CONSTRAINT it places on the product ("the system SHALL reuse the existing billing ' +
+        'provider") and drop the design reasoning around it; the Architect owns the rest and will ' +
+        'read this document as its input.\n' +
+        'Use EXACTLY these Markdown sections, in this order, omitting a section only when it has no ' +
+        'content:\n' +
+        '# <Title> — Requirements\n' +
+        '## Overview — one paragraph of intent and scope.\n' +
+        '## Functional Requirements — a bullet per requirement phrased as "The system SHALL ' +
+        '…" in terms of externally observable behaviour, never as an instruction about how to ' +
+        'implement it, each tagged with a MoSCoW priority (must/should/could); under each, an ' +
+        '"Acceptance:" sub-list of Given/When/Then criteria.\n' +
+        '## Non-Functional Requirements — quality attributes stated as measurable business ' +
+        'outcomes (volumes, response times as a user experiences them, availability, retention, ' +
+        'compliance) rather than the mechanism that would achieve them, same "The system SHALL …" ' +
+        'phrasing with a priority and a short rationale.\n' +
+        '## Domain Rules / Constraints — cross-cutting business invariants, each with a brief why.\n' +
+        '## Assumptions — assumptions the requirements rest on.\n' +
+        '## Out of Scope — what this work explicitly does not cover.\n' +
+        'Respond with ONLY the revised requirements in Markdown — no preamble, no ' +
+        'commentary, no code fences. ' +
+        FINAL_ANSWER_IN_REPLY,
+};
+export const REWORK_SYSTEM_PROMPT = composeBespokePrompt(REWORK_PROMPT);
 /**
  * The "Requirement Writer" — the SECOND companion of the requirements reviewer. Where the
  * reviewer raises findings and the rework editor folds human answers in, the Writer is asked
@@ -121,32 +142,48 @@ export const REWORK_SYSTEM_PROMPT = 'You are a requirements editor. You are give
  * Recommendations are suggestions for a human to accept/reject — they are NOT auto-applied and
  * are NOT AI-reviewed. The output is a strict JSON object so each suggestion maps to its finding.
  */
-export const WRITER_SYSTEM_PROMPT = 'You are a senior engineer acting as a Requirement Writer: for each requirements-review ' +
-    'finding you are given, recommend a concrete, defensible answer the product owner could ' +
-    'adopt.\n' +
-    PRODUCT_SCOPE_BOUNDARY +
-    '\n' +
-    'So every recommendation is a PRODUCT decision the owner can accept or reject on business ' +
-    'grounds — a behaviour, a rule, a limit, a boundary — never a technical design. The ' +
-    'technical material you are given (the `tech-spec/` excerpts, the standards) is there to ' +
-    'keep your recommendation FEASIBLE and consistent with what already exists, not to license ' +
-    'you to design: read a constraint out of it, do not write one into your answer. If a ' +
-    'finding turns out to be a technical design question that ' +
-    'slipped past the reviewer, do not answer it as one — recommend the product-level decision ' +
-    'it actually depends on, or say plainly that it should be left to the Architect step.\n' +
-    'Ground every recommendation in reality, in THIS order of precedence: (1) the ' +
-    "project's best-practice standards provided to you — if a standard already settles the " +
-    'finding, recommend exactly that and set "fromStandard" to its id; (2) the in-repo `spec/` ' +
-    '(business requirements) and `tech-spec/` (architecture, tech-stack, cross-cutting patterns ' +
-    'like pagination / transport) excerpts provided; (3) web search, for anything the project ' +
-    'material leaves open — prefer current, widely-adopted practice and cite it BRIEFLY (a ' +
-    'standard id, or a source name / short URL) rather than explaining at length. Be precise, ' +
-    'concrete and SUCCINCT: state the answer directly in at most two or three sentences (or a few ' +
-    'short bullets) — do NOT restate the finding, add preamble, or pad the wording. Give a concrete ' +
-    'default rather than hedging with "it depends". Respond with ONLY a JSON object of this exact ' +
-    'shape — no prose, no code fences:\n' +
-    '{ "recommendations": [ { "itemId": "<the finding id>", "recommendation": "<the concrete ' +
-    'suggested answer — precise and succinct>", "fromStandard": "<best-practice fragment id if the ' +
-    'answer came straight from one, else null>" } ] }\n' +
-    FINAL_ANSWER_IN_REPLY;
+export const WRITER_PROMPT = {
+    role: 'You are a senior engineer acting as a Requirement Writer: for each requirements-review ' +
+        'finding you are given, recommend a concrete, defensible answer the product owner could ' +
+        'adopt.',
+    directives: '\n' +
+        PRODUCT_SCOPE_BOUNDARY +
+        '\n' +
+        NO_ASSUMED_PRODUCT +
+        '\n' +
+        'So every recommendation is a PRODUCT decision the owner can accept or reject on business ' +
+        'grounds — a behaviour, a rule, a limit, a boundary — never a technical design. The ' +
+        'technical material you are given (the `tech-spec/` excerpts, the standards) is there to ' +
+        'keep your recommendation FEASIBLE and consistent with what already exists, not to license ' +
+        'you to design: read a constraint out of it, do not write one into your answer. If a ' +
+        'finding turns out to be a technical design question that ' +
+        'slipped past the reviewer, do not answer it as one — recommend the product-level decision ' +
+        'it actually depends on, or say plainly that it should be left to the Architect step.\n' +
+        'Ground every recommendation in reality, in THIS order of precedence: (1) the ' +
+        "project's best-practice standards provided to you — if a standard already settles the " +
+        'finding, recommend exactly that and set "fromStandard" to its id; (2) the in-repo `spec/` ' +
+        '(business requirements) and `tech-spec/` (architecture, tech-stack, cross-cutting patterns ' +
+        'like pagination / transport) excerpts provided; (3) web search, for anything the project ' +
+        'material leaves open — prefer current, widely-adopted practice and cite it BRIEFLY (a ' +
+        'standard id, or a source name / short URL) rather than explaining at length. When the ' +
+        'context does not identify which system this work belongs to, search only for GENERAL ' +
+        'practice for the kind of behaviour under discussion — never for a named product, vendor or ' +
+        'platform you had to guess at, which would dress an invented subject up as researched fact. ' +
+        'Be precise, ' +
+        'concrete and SUCCINCT: state the answer directly in at most two or three sentences (or a few ' +
+        'short bullets) — do NOT restate the finding, add preamble, or pad the wording. Give a concrete ' +
+        'default rather than hedging with "it depends". Respond with ONLY a JSON object of this exact ' +
+        'shape — no prose, no code fences:\n' +
+        '{ "recommendations": [ { "itemId": "<the finding id>", "recommendation": "<the concrete ' +
+        'suggested answer — precise and succinct>", "fromStandard": "<best-practice fragment id if the ' +
+        'answer came straight from one, else null>", "groundedIn": "standard|project-spec|web|' +
+        'general-practice" } ] }\n' +
+        'Set "groundedIn" to the precedence level the answer actually came from — `standard` for a ' +
+        "team/org standard, `project-spec` for the project's own `spec/`/`tech-spec/`, `web` for a " +
+        'search result, `general-practice` when it rests on your own general knowledge with none of ' +
+        'the above behind it. Report where the answer came FROM, never where it would ideally come ' +
+        'from: a human deciding whether to trust a suggestion needs that to be accurate.\n' +
+        FINAL_ANSWER_IN_REPLY,
+};
+export const WRITER_SYSTEM_PROMPT = composeBespokePrompt(WRITER_PROMPT);
 //# sourceMappingURL=requirements.js.map

package/dist/agents/prompts/requirements.js.map

@@ -1 +1 @@
-{"version":3,"file":"requirements.js","sourceRoot":"","sources":["../../../src/agents/prompts/requirements.ts"],"names":[],"mappings":"AAAA,iFAAiF;AACjF,mFAAmF;AACnF,qFAAqF;AACrF,6EAA6E;AAE7E,OAAO,EAAE,qBAAqB,EAAE,MAAM,aAAa,CAAA;AAEnD;;;;;;;;;;;;;;GAcG;AACH,MAAM,sBAAsB,GAC1B,6FAA6F;IAC7F,0FAA0F;IAC1F,wEAAwE;IACxE,2FAA2F;IAC3F,2FAA2F;IAC3F,8FAA8F;IAC9F,2FAA2F;IAC3F,4FAA4F;IAC5F,2FAA2F;IAC3F,gFAAgF;IAChF,0FAA0F;IAC1F,8FAA8F;IAC9F,yFAAyF;IACzF,4FAA4F;IAC5F,sFAAsF;IACtF,4FAA4F;IAC5F,4EAA4E;IAC5E,2FAA2F;IAC3F,4FAA4F;IAC5F,sFAAsF;IACtF,yFAAyF;IACzF,4FAA4F;IAC5F,sFAAsF;IACtF,8EAA8E,CAAA;AAEhF,MAAM,CAAC,MAAM,oBAAoB,GAC/B,8EAA8E;IAC9E,oFAAoF;IACpF,sBAAsB;IACtB,IAAI;IACJ,2FAA2F;IAC3F,4FAA4F;IAC5F,0FAA0F;IAC1F,uEAAuE;IACvE,sFAAsF;IACtF,6FAA6F;IAC7F,uFAAuF;IACvF,0FAA0F;IAC1F,+CAA+C;IAC/C,0FAA0F;IAC1F,2FAA2F;IAC3F,2FAA2F;IAC3F,4FAA4F;IAC5F,sFAAsF;IACtF,2FAA2F;IAC3F,0CAA0C;IAC1C,8DAA8D;IAC9D,qBAAqB,CAAA;AAEvB;;;;;;;;;GASG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAC/B,kFAAkF;IAClF,oFAAoF;IACpF,oFAAoF;IACpF,uEAAuE;IACvE,qFAAqF;IACrF,mFAAmF;IACnF,4DAA4D;IAC5D,sBAAsB;IACtB,IAAI;IACJ,6FAA6F;IAC7F,yFAAyF;IACzF,gFAAgF;IAChF,yFAAyF;IACzF,2FAA2F;IAC3F,wFAAwF;IACxF,2FAA2F;IAC3F,oCAAoC;IACpC,6FAA6F;IAC7F,YAAY;IACZ,4BAA4B;IAC5B,oDAAoD;IACpD,qFAAqF;IACrF,uFAAuF;IACvF,uFAAuF;IACvF,uDAAuD;IACvD,oFAAoF;IACpF,yFAAyF;IACzF,2FAA2F;IAC3F,mDAAmD;IACnD,6FAA6F;IAC7F,0DAA0D;IAC1D,+DAA+D;IAC/D,2EAA2E;IAC3E,8BAA8B;IAC9B,qBAAqB,CAAA;AAEvB;;;;;;;;;;;GAWG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAC/B,yFAAyF;IACzF,yFAAyF;IACzF,UAAU;IACV,sBAAsB;IACtB,IAAI;IACJ,2FAA2F;IAC3F,qFAAqF;IACrF,0FAA0F;IAC1F,4FAA4F;IAC5F,sFAAsF;IACtF,2DAA2D;IAC3D,4FAA4F;IAC5F,wFAAwF;IACxF,+EAA+E;IAC/E,wFAAwF;IACxF,4FAA4F;IAC5F,6FAA6F;IAC7F,2FAA2F;IAC3F,wFAAwF;IACxF,2FAA2F;IAC3F,+FAA+F;IAC/F,iGAAiG;IACjG,+FAA+F;IAC/F,qCAAqC;IACrC,0FAA0F;IAC1F,gGAAgG;IAChG,oDAAoD;IACpD,qBAAqB,CAAA"}
+{"version":3,"file":"requirements.js","sourceRoot":"","sources":["../../../src/agents/prompts/requirements.ts"],"names":[],"mappings":"AAAA,iFAAiF;AACjF,mFAAmF;AACnF,qFAAqF;AACrF,6EAA6E;AAE7E,OAAO,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,MAAM,aAAa,CAAA;AACvE,OAAO,EAA4B,oBAAoB,EAAE,MAAM,cAAc,CAAA;AAE7E;;;;;;;;;;;;;;GAcG;AACH,MAAM,sBAAsB,GAC1B,6FAA6F;IAC7F,0FAA0F;IAC1F,wEAAwE;IACxE,2FAA2F;IAC3F,2FAA2F;IAC3F,8FAA8F;IAC9F,2FAA2F;IAC3F,4FAA4F;IAC5F,2FAA2F;IAC3F,gFAAgF;IAChF,0FAA0F;IAC1F,8FAA8F;IAC9F,yFAAyF;IACzF,4FAA4F;IAC5F,sFAAsF;IACtF,4FAA4F;IAC5F,4EAA4E;IAC5E,2FAA2F;IAC3F,4FAA4F;IAC5F,sFAAsF;IACtF,yFAAyF;IACzF,4FAA4F;IAC5F,sFAAsF;IACtF,8EAA8E,CAAA;AAEhF;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,aAAa,GAAwB;IAChD,IAAI,EACF,8EAA8E;QAC9E,mFAAmF;QACnF,wEAAwE;QACxE,4FAA4F;QAC5F,0FAA0F;QAC1F,uEAAuE;QACvE,0CAA0C;QAC1C,uFAAuF;QACvF,0FAA0F;QAC1F,8CAA8C;IAChD,UAAU,EACR,IAAI;QACJ,sBAAsB;QACtB,IAAI;QACJ,sFAAsF;QACtF,sDAAsD;QACtD,kBAAkB;QAClB,IAAI;QACJ,0FAA0F;QAC1F,2FAA2F;QAC3F,2FAA2F;QAC3F,4FAA4F;QAC5F,sFAAsF;QACtF,2FAA2F;QAC3F,0CAA0C;QAC1C,8DAA8D;QAC9D,qBAAqB;CACxB,CAAA;AAED,MAAM,CAAC,MAAM,oBAAoB,GAAG,oBAAoB,CAAC,aAAa,CAAC,CAAA;AAEvE;;;;;;;;;GASG;AACH,MAAM,CAAC,MAAM,aAAa,GAAwB;IAChD,IAAI,EACF,kFAAkF;QAClF,oFAAoF;QACpF,oFAAoF;QACpF,uEAAuE;QACvE,qFAAqF;QACrF,mFAAmF;QACnF,0DAA0D;IAC5D,UAAU,EACR,IAAI;QACJ,sBAAsB;QACtB,IAAI;QACJ,kBAAkB;QAClB,IAAI;QACJ,6FAA6F;QAC7F,yFAAyF;QACzF,gFAAgF;QAChF,yFAAyF;QACzF,2FAA2F;QAC3F,wFAAwF;QACxF,2FAA2F;QAC3F,oCAAoC;QACpC,6FAA6F;QAC7F,YAAY;QACZ,4BAA4B;QAC5B,oDAAoD;QACpD,qFAAqF;QACrF,uFAAuF;QACvF,uFAAuF;QACvF,uDAAuD;QACvD,oFAAoF;QACpF,yFAAyF;QACzF,2FAA2F;QAC3F,mDAAmD;QACnD,6FAA6F;QAC7F,0DAA0D;QAC1D,+DAA+D;QAC/D,2EAA2E;QAC3E,8BAA8B;QAC9B,qBAAqB;CACxB,CAAA;AAED,MAAM,CAAC,MAAM,oBAAoB,GAAG,oBAAoB,CAAC,aAAa,CAAC,CAAA;AAEvE;;;;;;;;;;;GAWG;AACH,MAAM,CAAC,MAAM,aAAa,GAAwB;IAChD,IAAI,EACF,yFAAyF;QACzF,yFAAyF;QACzF,QAAQ;IACV,UAAU,EACR,IAAI;QACJ,sBAAsB;QACtB,IAAI;QACJ,kBAAkB;QAClB,IAAI;QACJ,2FAA2F;QAC3F,qFAAqF;QACrF,0FAA0F;QAC1F,4FAA4F;QAC5F,sFAAsF;QACtF,2DAA2D;QAC3D,4FAA4F;QAC5F,wFAAwF;QACxF,+EAA+E;QAC/E,wFAAwF;QACxF,4FAA4F;QAC5F,6FAA6F;QAC7F,2FAA2F;QAC3F,wFAAwF;QACxF,wFAAwF;QACxF,uFAAuF;QACvF,6FAA6F;QAC7F,6FAA6F;QAC7F,cAAc;QACd,+FAA+F;QAC/F,iGAAiG;QACjG,+FAA+F;QAC/F,qCAAqC;QACrC,0FAA0F;QAC1F,gGAAgG;QAChG,uFAAuF;QACvF,2BAA2B;QAC3B,4FAA4F;QAC5F,4FAA4F;QAC5F,6FAA6F;QAC7F,4FAA4F;QAC5F,mFAAmF;QACnF,qBAAqB;CACxB,CAAA;AAED,MAAM,CAAC,MAAM,oBAAoB,GAAG,oBAAoB,CAAC,aAAa,CAAC,CAAA"}

package/dist/agents/prompts/shared.d.ts

@@ -16,6 +16,35 @@ export declare const STANDARDS_FOOTER = "Treat every best-practice standard appe
  * legitimately end with no final text, and telling them otherwise is wrong.
  */
 export declare const FINAL_ANSWER_IN_REPLY: string;
+/**
+ * Appended to every agent that reasons about a work item WITHOUT a checkout to orient itself in —
+ * the inline reviewers and structured-dialogue agents (requirements review + rework, the Writer,
+ * clarity triage, both brainstorm stages).
+ *
+ * Those agents receive a task's title and description and nothing else that names the software
+ * under discussion, and a bare title ("implement webhooks") is domain-ambiguous. Asked for
+ * concrete findings against it, a model will supply the missing product itself — and once one
+ * pass has named a product, the incorporated document carries that invention into every later
+ * pass. Naming the absent product is the finding; inventing one buries the real question under
+ * confident detail about software that does not exist.
+ *
+ * Stated once here because it only holds if every agent in a flow honours it: a reviewer that
+ * stays with the stated system, an editor that does not write an assumed one into the document,
+ * and a Writer that does not recommend against one.
+ */
+export declare const NO_ASSUMED_PRODUCT: string;
+/**
+ * Appended to EVERY kind's system prompt by `systemPromptFor`, alongside the surface directives.
+ *
+ * The platform's own mechanics are visible to an agent from the inside — `cat-factory/<block>`
+ * branch names, `.cat-context/` and `.cat-*` sentinel files, managed markers in a pull request
+ * body — and a task with no product context of its own gives a model nothing else concrete to
+ * anchor on. The platform name is then the most salient proper noun in the whole prompt, which is
+ * how a neutral "implement webhooks" comes back as a design for the orchestrator's webhooks.
+ *
+ * Appended after any workspace override, so an edited prompt cannot delete it.
+ */
+export declare const PLATFORM_IS_NOT_THE_PRODUCT: string;
 /**
  * Appended by the CONSENSUS executor to every participant's system prompt, because a panel runs
  * its participants as plain inline model calls — no filesystem, no shell, no subagents.

package/dist/agents/prompts/shared.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"shared.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/shared.ts"],"names":[],"mappings":"AAIA;;;;GAIG;AACH,eAAO,MAAM,gBAAgB,+FACiE,CAAA;AAE9F;;;;;;;;;;GAUG;AACH,eAAO,MAAM,qBAAqB,QAIV,CAAA;AAExB;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,oBAAoB,QAQA,CAAA;AAEjC;;;;;;;;;;;GAWG;AACH;;;;;GAKG;AACH,eAAO,MAAM,kBAAkB,qBAAqB,CAAA;AAEpD;;;;;;;GAOG;AACH,eAAO,MAAM,sBAAsB,QASc,CAAA;AAEjD;;;;GAIG;AACH,eAAO,MAAM,mBAAmB,2BAA2B,CAAA;AAE3D;;;;;;;;GAQG;AACH,eAAO,MAAM,uBAAuB,QAoBX,CAAA;AA2BzB,eAAO,MAAM,2BAA2B,QAOyC,CAAA;AAEjF,eAAO,MAAM,yCAAyC,QAQF,CAAA;AAEpD,eAAO,MAAM,kBAAkB,QAW0C,CAAA"}
+{"version":3,"file":"shared.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/shared.ts"],"names":[],"mappings":"AAIA;;;;GAIG;AACH,eAAO,MAAM,gBAAgB,+FACiE,CAAA;AAE9F;;;;;;;;;;GAUG;AACH,eAAO,MAAM,qBAAqB,QAIV,CAAA;AAExB;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,kBAAkB,QAQiD,CAAA;AAEhF;;;;;;;;;;GAUG;AACH,eAAO,MAAM,2BAA2B,QAQT,CAAA;AAE/B;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,oBAAoB,QAQA,CAAA;AAEjC;;;;;;;;;;;GAWG;AACH;;;;;GAKG;AACH,eAAO,MAAM,kBAAkB,qBAAqB,CAAA;AAEpD;;;;;;;GAOG;AACH,eAAO,MAAM,sBAAsB,QASc,CAAA;AAEjD;;;;GAIG;AACH,eAAO,MAAM,mBAAmB,2BAA2B,CAAA;AAE3D;;;;;;;;GAQG;AACH,eAAO,MAAM,uBAAuB,QAoBX,CAAA;AA2BzB,eAAO,MAAM,2BAA2B,QAOyC,CAAA;AAEjF,eAAO,MAAM,yCAAyC,QAQF,CAAA;AAEpD,eAAO,MAAM,kBAAkB,QAW0C,CAAA"}

package/dist/agents/prompts/shared.js

@@ -22,6 +22,49 @@ export const FINAL_ANSWER_IN_REPLY = 'Your deliverable is the text of your FINAL
     'visible content of that reply, NOT inside your private reasoning or thinking. A final ' +
     'reply whose visible content is empty is treated as a failure even when your reasoning ' +
     'contains the answer.';
+/**
+ * Appended to every agent that reasons about a work item WITHOUT a checkout to orient itself in —
+ * the inline reviewers and structured-dialogue agents (requirements review + rework, the Writer,
+ * clarity triage, both brainstorm stages).
+ *
+ * Those agents receive a task's title and description and nothing else that names the software
+ * under discussion, and a bare title ("implement webhooks") is domain-ambiguous. Asked for
+ * concrete findings against it, a model will supply the missing product itself — and once one
+ * pass has named a product, the incorporated document carries that invention into every later
+ * pass. Naming the absent product is the finding; inventing one buries the real question under
+ * confident detail about software that does not exist.
+ *
+ * Stated once here because it only holds if every agent in a flow honours it: a reviewer that
+ * stays with the stated system, an editor that does not write an assumed one into the document,
+ * and a Writer that does not recommend against one.
+ */
+export const NO_ASSUMED_PRODUCT = 'THE SYSTEM UNDER DISCUSSION IS ONLY WHAT THE CONTEXT NAMES. Never assume, infer or introduce ' +
+    'a product, company, vendor, framework, platform, tool or business domain the context you were ' +
+    'given does not name — not to make a point concrete, and not as an illustrative example. If the ' +
+    'context does not identify which system this work belongs to, treat that as a FACT ABOUT THE ' +
+    'CONTEXT and not a gap in your knowledge: stay at the level the text actually supports, say ' +
+    'plainly that the system is unidentified, and where a point genuinely depends on knowing which ' +
+    'system this is, raise THAT as the point ("which service / product is this for?"). A confident ' +
+    'answer about the wrong software is worse than an explicit "not stated here".';
+/**
+ * Appended to EVERY kind's system prompt by `systemPromptFor`, alongside the surface directives.
+ *
+ * The platform's own mechanics are visible to an agent from the inside — `cat-factory/<block>`
+ * branch names, `.cat-context/` and `.cat-*` sentinel files, managed markers in a pull request
+ * body — and a task with no product context of its own gives a model nothing else concrete to
+ * anchor on. The platform name is then the most salient proper noun in the whole prompt, which is
+ * how a neutral "implement webhooks" comes back as a design for the orchestrator's webhooks.
+ *
+ * Appended after any workspace override, so an edited prompt cannot delete it.
+ */
+export const PLATFORM_IS_NOT_THE_PRODUCT = 'THE PLATFORM RUNNING YOU IS NOT THE PRODUCT YOU WORK ON. You are executed by an agent ' +
+    'orchestration platform (cat-factory), and its mechanics are visible around you: branch names ' +
+    'under `cat-factory/`, `.cat-context/` context files, `.cat-*` sentinel files, and managed ' +
+    'markers in pull request bodies. Those belong to the harness running you. Never treat that ' +
+    'platform, its name, its conventions or its features as part of the product, the domain or the ' +
+    'requirements of the work you were given — and never let them stand in as the subject of a ' +
+    'task that does not name a subject. They are in scope only when the work you were handed is ' +
+    'itself about that platform.';
 /**
  * Appended by the CONSENSUS executor to every participant's system prompt, because a panel runs
  * its participants as plain inline model calls — no filesystem, no shell, no subagents.

package/dist/agents/prompts/shared.js.map

@@ -1 +1 @@
-{"version":3,"file":"shared.js","sourceRoot":"","sources":["../../../src/agents/prompts/shared.ts"],"names":[],"mappings":"AAAA,iFAAiF;AACjF,kFAAkF;AAClF,4DAA4D;AAE5D;;;;GAIG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAC3B,4FAA4F,CAAA;AAE9F;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAChC,oFAAoF;IACpF,wFAAwF;IACxF,wFAAwF;IACxF,sBAAsB,CAAA;AAExB;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAC/B,gGAAgG;IAChG,+FAA+F;IAC/F,8FAA8F;IAC9F,+FAA+F;IAC/F,iGAAiG;IACjG,wFAAwF;IACxF,6FAA6F;IAC7F,+BAA+B,CAAA;AAEjC;;;;;;;;;;;GAWG;AACH;;;;;GAKG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,kBAAkB,CAAA;AAEpD;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,sBAAsB,GACjC,6FAA6F;IAC7F,gBAAgB,kBAAkB,2DAA2D;IAC7F,8FAA8F;IAC9F,yFAAyF;IACzF,uFAAuF;IACvF,0FAA0F;IAC1F,+FAA+F;IAC/F,+FAA+F;IAC/F,+CAA+C,CAAA;AAEjD;;;;GAIG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,wBAAwB,CAAA;AAE3D;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAClC,6FAA6F;IAC7F,yCAAyC,mBAAmB,6BAA6B;IACzF,uFAAuF;IACvF,4FAA4F;IAC5F,0FAA0F;IAC1F,2FAA2F;IAC3F,oFAAoF;IACpF,6FAA6F;IAC7F,uFAAuF;IACvF,uFAAuF;IACvF,6FAA6F;IAC7F,0FAA0F;IAC1F,yFAAyF;IACzF,yFAAyF;IACzF,+FAA+F;IAC/F,gGAAgG;IAChG,8FAA8F;IAC9F,6FAA6F;IAC7F,8FAA8F;IAC9F,uBAAuB,CAAA;AAEzB;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,+BAA+B,GACnC,0FAA0F;IAC1F,4FAA4F;IAC5F,iFAAiF;IACjF,+FAA+F;IAC/F,gGAAgG;IAChG,YAAY,CAAA;AAEd,MAAM,CAAC,MAAM,2BAA2B,GACtC,gGAAgG;IAChG,+FAA+F;IAC/F,SAAS;IACT,+BAA+B;IAC/B,qFAAqF;IACrF,4FAA4F;IAC5F,+EAA+E,CAAA;AAEjF,MAAM,CAAC,MAAM,yCAAyC,GACpD,gGAAgG;IAChG,oGAAoG;IACpG,0FAA0F;IAC1F,oDAAoD;IACpD,+BAA+B;IAC/B,iGAAiG;IACjG,2FAA2F;IAC3F,kDAAkD,CAAA;AAEpD,MAAM,CAAC,MAAM,kBAAkB,GAC7B,oFAAoF;IACpF,uFAAuF;IACvF,wFAAwF;IACxF,mFAAmF;IACnF,kFAAkF;IAClF,iFAAiF;IACjF,oFAAoF;IACpF,yFAAyF;IACzF,uFAAuF;IACvF,yFAAyF;IACzF,uEAAuE,CAAA"}
+{"version":3,"file":"shared.js","sourceRoot":"","sources":["../../../src/agents/prompts/shared.ts"],"names":[],"mappings":"AAAA,iFAAiF;AACjF,kFAAkF;AAClF,4DAA4D;AAE5D;;;;GAIG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAC3B,4FAA4F,CAAA;AAE9F;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAChC,oFAAoF;IACpF,wFAAwF;IACxF,wFAAwF;IACxF,sBAAsB,CAAA;AAExB;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC7B,+FAA+F;IAC/F,gGAAgG;IAChG,iGAAiG;IACjG,8FAA8F;IAC9F,6FAA6F;IAC7F,gGAAgG;IAChG,gGAAgG;IAChG,8EAA8E,CAAA;AAEhF;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,2BAA2B,GACtC,wFAAwF;IACxF,+FAA+F;IAC/F,4FAA4F;IAC5F,4FAA4F;IAC5F,gGAAgG;IAChG,4FAA4F;IAC5F,6FAA6F;IAC7F,6BAA6B,CAAA;AAE/B;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAC/B,gGAAgG;IAChG,+FAA+F;IAC/F,8FAA8F;IAC9F,+FAA+F;IAC/F,iGAAiG;IACjG,wFAAwF;IACxF,6FAA6F;IAC7F,+BAA+B,CAAA;AAEjC;;;;;;;;;;;GAWG;AACH;;;;;GAKG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,kBAAkB,CAAA;AAEpD;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,sBAAsB,GACjC,6FAA6F;IAC7F,gBAAgB,kBAAkB,2DAA2D;IAC7F,8FAA8F;IAC9F,yFAAyF;IACzF,uFAAuF;IACvF,0FAA0F;IAC1F,+FAA+F;IAC/F,+FAA+F;IAC/F,+CAA+C,CAAA;AAEjD;;;;GAIG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,wBAAwB,CAAA;AAE3D;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAClC,6FAA6F;IAC7F,yCAAyC,mBAAmB,6BAA6B;IACzF,uFAAuF;IACvF,4FAA4F;IAC5F,0FAA0F;IAC1F,2FAA2F;IAC3F,oFAAoF;IACpF,6FAA6F;IAC7F,uFAAuF;IACvF,uFAAuF;IACvF,6FAA6F;IAC7F,0FAA0F;IAC1F,yFAAyF;IACzF,yFAAyF;IACzF,+FAA+F;IAC/F,gGAAgG;IAChG,8FAA8F;IAC9F,6FAA6F;IAC7F,8FAA8F;IAC9F,uBAAuB,CAAA;AAEzB;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,+BAA+B,GACnC,0FAA0F;IAC1F,4FAA4F;IAC5F,iFAAiF;IACjF,+FAA+F;IAC/F,gGAAgG;IAChG,YAAY,CAAA;AAEd,MAAM,CAAC,MAAM,2BAA2B,GACtC,gGAAgG;IAChG,+FAA+F;IAC/F,SAAS;IACT,+BAA+B;IAC/B,qFAAqF;IACrF,4FAA4F;IAC5F,+EAA+E,CAAA;AAEjF,MAAM,CAAC,MAAM,yCAAyC,GACpD,gGAAgG;IAChG,oGAAoG;IACpG,0FAA0F;IAC1F,oDAAoD;IACpD,+BAA+B;IAC/B,iGAAiG;IACjG,2FAA2F;IAC3F,kDAAkD,CAAA;AAEpD,MAAM,CAAC,MAAM,kBAAkB,GAC7B,oFAAoF;IACpF,uFAAuF;IACvF,wFAAwF;IACxF,mFAAmF;IACnF,kFAAkF;IAClF,iFAAiF;IACjF,oFAAoF;IACpF,yFAAyF;IACzF,uFAAuF;IACvF,yFAAyF;IACzF,uEAAuE,CAAA"}