flanders 0.3.0 → 0.5.0

package/lib/commands/Install.js

@@ -112,6 +112,34 @@ const CLAUDE_CROSS_FAMILY_ALIASES = [
 ];
 const CLAUDE_BACK_LABEL = "← back";
 const REVIEWER_INDEXED_RE = /^--reviewer-(\d+)-(tool|model|effort)=/;
+const REVIEWER_OPTIONAL_INDEXED_RE = /^--reviewer-(\d+)-optional$/;
+function validateWeightedFlagsForReviewerCount(reviewerMinimum, optionalReviewerIndices, reviewerCount) {
+    if (reviewerCount === 1) {
+        if (reviewerMinimum !== undefined) {
+            return "Invalid flag for a single-reviewer configuration: --reviewer-minimum. Weighted-review flags require two or more reviewers.\n";
+        }
+        if (optionalReviewerIndices !== undefined) {
+            const idx = optionalReviewerIndices[0];
+            const flag = idx === 1 ? "--reviewer-optional" : `--reviewer-${idx}-optional`;
+            return `Invalid flag for a single-reviewer configuration: ${flag}. Weighted-review flags require two or more reviewers.\n`;
+        }
+        return null;
+    }
+    if (reviewerMinimum !== undefined && (reviewerMinimum < 1 || reviewerMinimum > reviewerCount)) {
+        return `Invalid value for --reviewer-minimum: "${reviewerMinimum}". Must be an integer between 1 and ${reviewerCount}.\n`;
+    }
+    if (optionalReviewerIndices !== undefined) {
+        for (const idx of optionalReviewerIndices) {
+            if (idx > reviewerCount) {
+                return `Invalid reviewer flag: --reviewer-${idx}-optional references reviewer ${idx}, beyond the configured reviewer list of ${reviewerCount}.\n`;
+            }
+        }
+    }
+    if (reviewerMinimum === reviewerCount && optionalReviewerIndices !== undefined) {
+        return `Invalid flag combination: --reviewer-minimum equal to the reviewer count (${reviewerCount}) leaves no reviewer that can be optional, so it cannot be combined with --reviewer[-N]-optional.\n`;
+    }
+    return null;
+}
 function parseInstallFlags(rawArgs) {
     var _a;
     const hasGlobal = rawArgs.includes("--global");
@@ -226,6 +254,38 @@ function parseInstallFlags(rawArgs) {
         }
         answers.reviewers = list;
     }
+    const optionalIndices = new Set();
+    for (const arg of rawArgs) {
+        if (arg === "--reviewer-optional") {
+            optionalIndices.add(1);
+            continue;
+        }
+        const match = arg.match(REVIEWER_OPTIONAL_INDEXED_RE);
+        if (match === null) {
+            continue;
+        }
+        const idx = Number(match[1]);
+        if (idx < 1) {
+            return { ok: false, diagnostic: `Invalid reviewer flag: "${arg}". --reviewer-N-optional requires N >= 1.\n` };
+        }
+        optionalIndices.add(idx);
+    }
+    if (optionalIndices.size > 0) {
+        answers.optionalReviewerIndices = [...optionalIndices].sort((a, b) => a - b);
+    }
+    const minimumRaw = extractFlagValue(rawArgs, "--reviewer-minimum");
+    if (minimumRaw !== undefined) {
+        if (!/^\d+$/.test(minimumRaw)) {
+            return { ok: false, diagnostic: `Invalid value for --reviewer-minimum: "${minimumRaw}". Expected a non-negative integer.\n` };
+        }
+        answers.reviewerMinimum = Number(minimumRaw);
+    }
+    if (answers.reviewers !== undefined) {
+        const diagnostic = validateWeightedFlagsForReviewerCount(answers.reviewerMinimum, answers.optionalReviewerIndices, answers.reviewers.length);
+        if (diagnostic !== null) {
+            return { ok: false, diagnostic };
+        }
+    }
     return { ok: true, answers };
 }
 class Install {
@@ -590,6 +650,95 @@ class Install {
                     idx++;
                 }
             }
+            if (suppliedReviewers === undefined) {
+                const diagnostic = validateWeightedFlagsForReviewerCount(answers.reviewerMinimum, answers.optionalReviewerIndices, reviewers.length);
+                if (diagnostic !== null) {
+                    contexts.output.writeError(diagnostic);
+                    return 1;
+                }
+            }
+            let minimumReviews;
+            const reviewerConfigs = [];
+            if (reviewers.length === 1) {
+                minimumReviews = 1;
+                reviewerConfigs.push({ ...reviewers[0], optional: false });
+            }
+            else {
+                const reviewerCount = reviewers.length;
+                if (answers.reviewerMinimum !== undefined) {
+                    minimumReviews = answers.reviewerMinimum;
+                }
+                else {
+                    if (this._disposed) {
+                        return 1;
+                    }
+                    let chosen = null;
+                    while (chosen === null) {
+                        const entry = await promptText(contexts.ask, {
+                            question: "Minimum reviewers that must run to a verdict in each review round",
+                            placeholder: `1-${reviewerCount}, empty for ${reviewerCount}`
+                        });
+                        if (entry === null) {
+                            return 1;
+                        }
+                        if (this._disposed) {
+                            return 1;
+                        }
+                        const trimmed = entry.trim();
+                        if (trimmed === "") {
+                            chosen = reviewerCount;
+                        }
+                        else {
+                            const parsed = Number(trimmed);
+                            if (/^\d+$/.test(trimmed) && parsed >= 1 && parsed <= reviewerCount) {
+                                chosen = parsed;
+                            }
+                            else {
+                                contexts.output.write(`Enter an integer between 1 and ${reviewerCount}, or leave empty for ${reviewerCount}.\n`);
+                            }
+                        }
+                    }
+                    minimumReviews = chosen;
+                }
+                if (minimumReviews < reviewerCount) {
+                    if (answers.optionalReviewerIndices !== undefined) {
+                        const optionalSet = new Set(answers.optionalReviewerIndices);
+                        for (let i = 0; i < reviewerCount; i++) {
+                            reviewerConfigs.push({ ...reviewers[i], optional: optionalSet.has(i + 1) });
+                        }
+                    }
+                    else {
+                        for (let i = 0; i < reviewerCount; i++) {
+                            if (this._disposed) {
+                                return 1;
+                            }
+                            const reviewer = reviewers[i];
+                            const modelLabel = reviewer.model === "" ? "default configured model" : reviewer.model;
+                            const effortLabel = reviewer.effort === "" ? "default configured effort" : reviewer.effort;
+                            const optionalOption = await promptChoice(contexts.ask, {
+                                header: `Reviewer ${i + 1} optional`,
+                                question: `Is reviewer ${i + 1} (${reviewer.tool} · ${modelLabel} · ${effortLabel}) optional?`,
+                                options: [
+                                    { label: "no", description: "Required — always waits out its rate-limit waits; the round never completes without its verdict" },
+                                    { label: "yes", description: "Optional — reviews exactly like a required reviewer; the only difference is the round abandons it while it is in a rate-limit wait, once every required reviewer is in and the minimum is met" }
+                                ]
+                            });
+                            if (!optionalOption) {
+                                return 1;
+                            }
+                            if (this._disposed) {
+                                return 1;
+                            }
+                            reviewerConfigs.push({ ...reviewer, optional: optionalOption.label === "yes" });
+                        }
+                    }
+                }
+                else {
+                    for (let i = 0; i < reviewerCount; i++) {
+                        reviewerConfigs.push({ ...reviewers[i], optional: false });
+                    }
+                }
+            }
             const scopeRoot = mode === "global"
                 ? contexts.platform.homedir()
                 : options.projectRoot;
@@ -656,7 +805,8 @@ class Install {
             }
             const config = {
                 worker: { tool: workerTool, model: workerModel, effort: workerEffort },
-                reviewers
+                reviewers: reviewerConfigs,
+                minimumReviews
             };
             const configWrittenPath = await (0, FlandersConfig_1.write)(contexts.fs, {
                 scope: mode,

package/lib/commands/InstallModelProbe.js

@@ -9,6 +9,39 @@ function isCommandNotFound(combinedOutput) {
     const lower = combinedOutput.toLowerCase();
     return COMMAND_NOT_FOUND_MARKERS.some(marker => lower.includes(marker));
 }
+function parseModelCatalog(stdout) {
+    let parsed;
+    try {
+        parsed = JSON.parse(stdout);
+    }
+    catch {
+        return null;
+    }
+    if (typeof parsed !== "object" || parsed === null || Array.isArray(parsed)) {
+        return null;
+    }
+    const models = parsed.models;
+    if (!Array.isArray(models)) {
+        return null;
+    }
+    const slugs = [];
+    for (const entry of models) {
+        if (typeof entry !== "object" || entry === null || Array.isArray(entry)) {
+            return null;
+        }
+        const record = entry;
+        if (typeof record.slug !== "string" || typeof record.visibility !== "string") {
+            return null;
+        }
+        if (record.visibility === "list") {
+            slugs.push(record.slug);
+        }
+    }
+    if (slugs.length === 0) {
+        return { kind: "no-list" };
+    }
+    return { kind: "list", models: slugs };
+}
 function probeModelList(script) {
     return new Promise(resolve => {
         const stdoutChunks = [];
@@ -48,52 +81,17 @@ function probeModelList(script) {
         });
         proc.on("exit", (code) => {
             const stdout = stdoutChunks.join("");
+            const catalog = parseModelCatalog(stdout);
+            if (catalog) {
+                settle(catalog);
+                return;
+            }
             const stderr = stderrChunks.join("");
             if (code === 127 || isCommandNotFound(stderr + stdout)) {
                 notStarted(null);
                 return;
             }
-            if (code !== 0) {
-                settle({ kind: "no-list" });
-                return;
-            }
-            let parsed;
-            try {
-                parsed = JSON.parse(stdout);
-            }
-            catch {
-                settle({ kind: "no-list" });
-                return;
-            }
-            if (typeof parsed !== "object" || parsed === null || Array.isArray(parsed)) {
-                settle({ kind: "no-list" });
-                return;
-            }
-            const models = parsed.models;
-            if (!Array.isArray(models)) {
-                settle({ kind: "no-list" });
-                return;
-            }
-            const slugs = [];
-            for (const entry of models) {
-                if (typeof entry !== "object" || entry === null || Array.isArray(entry)) {
-                    settle({ kind: "no-list" });
-                    return;
-                }
-                const record = entry;
-                if (typeof record.slug !== "string" || typeof record.visibility !== "string") {
-                    settle({ kind: "no-list" });
-                    return;
-                }
-                if (record.visibility === "list") {
-                    slugs.push(record.slug);
-                }
-            }
-            if (slugs.length === 0) {
-                settle({ kind: "no-list" });
-                return;
-            }
-            settle({ kind: "list", models: slugs });
+            settle({ kind: "no-list" });
         });
     });
 }

package/lib/plan/PlanFile.d.ts

@@ -27,6 +27,7 @@ export type PlanParseResult = Readonly<{
 }>;
 export declare const TASK_LINE: RegExp;
 export declare function parsePlan(content: string): PlanParseResult;
+export declare function extractFullTaskText(content: string, taskLineNumber: number): string;
 export declare function parseLinkedPaths(content: string, taskLineNumber: number): TaskLinkedPaths;
 export declare class PlanFile {
     readonly path: string;
@@ -40,6 +41,7 @@ export declare class PlanFile {
     markDone(lineNumber: number, metrics: TaskMetrics): Promise<void>;
     markOpen(lineNumber: number, metrics: TaskMetrics): Promise<void>;
     linkedPaths(task: PlanTask): TaskLinkedPaths;
+    fullTaskText(task: PlanTask): string;
     planTotals(): TaskMetrics;
     private _rewriteTaskLine;
 }

package/lib/plan/PlanFile.js

@@ -2,6 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.PlanFile = exports.TASK_LINE = void 0;
 exports.parsePlan = parsePlan;
+exports.extractFullTaskText = extractFullTaskText;
 exports.parseLinkedPaths = parseLinkedPaths;
 exports.TASK_LINE = /^(\s*[-*+]\s+)\[([ xX])\](\{[^}]*\})(\s.*)?$/;
 const MALFORMED_TASK_LINE = /^\s*[-*+]\s+\[[^\]]*\]\{/;
@@ -88,14 +89,12 @@ function parsePlan(content) {
         size: content.length
     };
 }
-const BACKTICK_PATH = /`([^`]+)`/g;
-function extractPathsFromLine(text) {
-    const paths = [];
-    let m;
-    while ((m = BACKTICK_PATH.exec(text)) !== null) {
-        paths.push(m[1]);
-    }
-    return paths;
+const MARKDOWN_LINK = /\[[^\]]*\]\(([^)]+)\)/g;
+const CONTRACTS_SEGMENT = ".spec/contracts/";
+const RULES_SEGMENT = ".spec/rules/";
+function detectNewline(content) {
+    const newlineMatch = /\r\n|\n/.exec(content);
+    return newlineMatch ? newlineMatch[0] : "\n";
 }
 function taskBodyLines(content, taskLineNumber) {
     const lines = content.split(/\r?\n/);
@@ -108,17 +107,30 @@ function taskBodyLines(content, taskLineNumber) {
     }
     return body;
 }
+function extractFullTaskText(content, taskLineNumber) {
+    const lines = content.split(/\r?\n/);
+    const taskLine = lines[taskLineNumber - 1];
+    const body = taskBodyLines(content, taskLineNumber);
+    return [taskLine, ...body].join(detectNewline(content));
+}
 function parseLinkedPaths(content, taskLineNumber) {
     const body = taskBodyLines(content, taskLineNumber);
-    let contracts = [];
-    let rules = [];
+    const contracts = [];
+    const rules = [];
     for (const line of body) {
-        const trimmed = line.trimStart();
-        if (trimmed.startsWith("Linked contracts:")) {
-            contracts = extractPathsFromLine(trimmed.slice("Linked contracts:".length));
-        }
-        else if (trimmed.startsWith("Linked rules:")) {
-            rules = extractPathsFromLine(trimmed.slice("Linked rules:".length));
+        let m;
+        while ((m = MARKDOWN_LINK.exec(line)) !== null) {
+            const path = m[1].split("#")[0].replace(/^\//, "");
+            if (path.includes(CONTRACTS_SEGMENT)) {
+                if (!contracts.includes(path)) {
+                    contracts.push(path);
+                }
+            }
+            else if (path.includes(RULES_SEGMENT)) {
+                if (!rules.includes(path)) {
+                    rules.push(path);
+                }
+            }
         }
     }
     return { contracts, rules };
@@ -156,6 +168,9 @@ class PlanFile {
     linkedPaths(task) {
         return parseLinkedPaths(this._content, task.line);
     }
+    fullTaskText(task) {
+        return extractFullTaskText(this._content, task.line);
+    }
     planTotals() {
         const { tasks } = parsePlan(this._content);
         let it = 0, ot = 0, t = 0;
@@ -168,8 +183,7 @@ class PlanFile {
     }
     async _rewriteTaskLine(lineNumber, metrics, flip) {
         validateMetricsInput(metrics);
-        const newlineMatch = /\r\n|\n/.exec(this._content);
-        const newline = newlineMatch ? newlineMatch[0] : "\n";
+        const newline = detectNewline(this._content);
         const lines = this._content.split(/\r?\n/);
         const idx = lineNumber - 1;
         const raw = lines[idx];

package/lib/prompts/prompts.d.ts

@@ -1,7 +1,6 @@
 export declare const enum Placeholders {
     PLAN_PATH = "<PLAN_PATH>",
-    TASK_LINE = "<TASK_LINE>",
-    TASK_TITLE = "<TASK_TITLE>",
+    TASK_TEXT = "<TASK_TEXT>",
     BUILD_SCRIPT_PATH = "<BUILD_SCRIPT_PATH>",
     TEST_SCRIPT_PATH = "<TEST_SCRIPT_PATH>",
     ERROR_LOG_PATH = "<ERROR_LOG_PATH>",
@@ -43,6 +42,5 @@ export declare const prompts: {
     detectBuildAndTest: string;
     worker: string;
     reviewer: string;
-    prep: string;
     previousIterationBriefing: string;
 };

package/lib/prompts/prompts.js

@@ -35,7 +35,7 @@ ${s.readOnlyParagraph}`;
 2. A contract referenced by ${s.specRef} is not honored.
 3. A rule referenced by ${s.specRef} is not applied in the changes — you have the positive obligation to verify that every referenced rule is actively applied; a referenced rule that is not applied is FAIL.
 4. A contract or rule from the global lists above that you determine should have been applied but was not, even if not referenced by ${s.specRef}, is FAIL.
-5. A behavior rule from the behavior-rule list above whose \`.docs/flanders\` scope encloses the files the working-tree changes touch is not honored by the changes, even if ${s.specRef} did not reference it, is FAIL.
+5. A behavior rule from the behavior-rule list above whose \`.spec/flanders\` scope encloses the files the working-tree changes touch is not honored by the changes, even if ${s.specRef} did not reference it, is FAIL.
 
 Exhaustiveness: do not stop at the first violation. Run every verification you are required to run and every additional check your judgment deems applicable, even after one of them has already produced a FAIL. The five conditions above and the ${s.critProtocolName} are executed in full on every invocation; encountering a violation in one of them does not exempt you from completing the rest. The goal is that a single review produces the complete list of fixes ${s.nextWorker} needs to apply.
 
@@ -149,21 +149,22 @@ If you cannot confidently determine how to build the project, leave the build sc
 
 ## Available rules
 
-Each path below is the rule's namespace. Before deciding the build or test commands, scan this list and open every rule whose scope governs how the project is built or how its tests are run — for example, any rule under a \`testing/\` or \`build/\` subfolder of a \`.docs/rules\` folder, or any rule that prescribes a specific runner, invocation form, required flag, or toolchain convention. Reading is not optional for rules whose scope matches build/test invocation. The commands you write must honor those rules: if a rule pins the test runner to a specific invocation form or required flag, the script you write must use that exact invocation.
+Each path below is the rule's namespace. Before deciding the build or test commands, scan this list and open every rule whose scope governs how the project is built or how its tests are run — for example, any rule under a \`testing/\` or \`build/\` subfolder of a \`.spec/rules\` folder, or any rule that prescribes a specific runner, invocation form, required flag, or toolchain convention. Reading is not optional for rules whose scope matches build/test invocation. The commands you write must honor those rules: if a rule pins the test runner to a specific invocation form or required flag, the script you write must use that exact invocation.
 
 ${"<RULE_LIST>"}
 
 Git boundary: you must not execute any git command that modifies repository state. Read-only git commands (\`git status\`, \`git log\`, \`git show\`, \`git diff\`, \`git blame\`, \`git ls-files\`) are allowed if they help you understand the project; commits, staging, branches, tags, stashes, resets, restores, merges, rebases, edits under \`.git/\`, and any remote git operation are forbidden. See rules/ai/agents/no-git-writes.md for the full obligation.
 
-Spec-folder write boundary: you must not create, modify, delete, or rename any file inside any \`.docs/contracts\` folder, any \`.docs/rules\` folder, or the \`plans/\` folder. These folders are governed by dedicated skills and the implement command's bounded checkpoint updates; no other agent may write to them. See shared/spec-folder-write-authority.md for the full obligation.
+Spec-folder write boundary: you must not create, modify, delete, or rename any file inside any \`.spec/contracts\` folder, any \`.spec/rules\` folder, or the \`plans/\` folder. These folders are governed by dedicated skills and the implement command's bounded checkpoint updates; no other agent may write to them. See shared/spec-folder-write-authority.md for the full obligation.
 
 ${foregroundBoundary}`,
     worker: `You are the worker agent for the Flanders implement iteration loop.
 
-Plan file path: ${"<PLAN_PATH>"}
+The plan file is at ${"<PLAN_PATH>"}; you may open it for broader context.
 
-The current task is on line ${"<TASK_LINE>"} of that plan file. Its title, verbatim, is:
-${"<TASK_TITLE>"}
+## Your task
+
+${"<TASK_TEXT>"}
 
 ## Adversarial review awaits
 
@@ -173,12 +174,12 @@ Your output will be inspected by an adversarial reviewer immediately after you f
 2. A contract referenced by the task is not honored.
 3. A rule referenced by the task is not actively applied — acknowledging a rule is not enough; the changes must demonstrate compliance.
 4. A contract or rule from the global lists below that the reviewer determines should have been applied but was not — even if the task did not reference it.
-5. A behavior rule from the behavior-rule list below whose \`.docs/flanders\` scope encloses the files your changes touch is not honored by the changes — in-scope behavior rules are mandatory whether or not the task links them.
+5. A behavior rule from the behavior-rule list below whose \`.spec/flanders\` scope encloses the files your changes touch is not honored by the changes — in-scope behavior rules are mandatory whether or not the task links them.
 
 Condition 4 causes most rejections in practice. Rules whose scope matches your changes (testing rules when you touch tests, disposable rules when you touch async resources, UI rules when you change terminal output, etc.) are mandatory whether the task links them or not. Treat the global contract and rule lists below as part of your specification, not as optional reading. The reviewer will also enumerate every occurrence of a pattern violation, not just the first one, so partial compliance within a file is itself a FAIL.
 
 Procedure:
-1. Open the plan file and find that line. Read the full task description and its acceptance criteria. You are not required to re-read the linked contracts and rules — on iteration 1 their content is already in context through the prep fork, and on later iterations it is preserved by your own session continuity. You may consult them at your discretion, but you must respect their obligations exactly.
+1. Read the task shown above and respect the obligations of every contract and rule it references exactly. You may consult those files, or the plan file for broader context, at your discretion.
 2. Implement the task. Update or extend tests so the new behavior is covered.
 3. If your implementation changes how the project builds or how its tests run, also update the build and test scripts at:
    - Build script: ${"<BUILD_SCRIPT_PATH>"}
@@ -209,7 +210,7 @@ Do not flip the task's checkbox in the plan file. Flanders flips the checkbox it
 
 Git boundary: you must not execute any git command that modifies repository state — no \`git add\`, \`git commit\`, \`git stash\`, \`git reset\`, \`git restore\`, \`git checkout -b\`, \`git branch\`, \`git tag\`, \`git rebase\`, \`git merge\`, \`git cherry-pick\`, no edits under \`.git/\`, and no remote git operations (\`fetch\`, \`pull\`, \`push\`). Read-only git commands (\`git status\`, \`git diff\`, \`git log\`, \`git show\`, \`git blame\`, \`git ls-files\`) are allowed when you need to inspect the repo. Leave your implementation as a dirty working tree — Flanders performs the commit itself once your changes pass build, test, and review. If your task seems to require a git write, stop and explain it in your final message instead of doing it. The full obligation lives in rules/ai/agents/no-git-writes.md.
 
-Spec-folder write boundary: you must not create, modify, delete, or rename any file inside any \`.docs/contracts\` folder, any \`.docs/rules\` folder, or the \`plans/\` folder. These folders are governed by dedicated skills and the implement command's bounded checkpoint updates; no other agent may write to them. See shared/spec-folder-write-authority.md for the full obligation.
+Spec-folder write boundary: you must not create, modify, delete, or rename any file inside any \`.spec/contracts\` folder, any \`.spec/rules\` folder, or the \`plans/\` folder. These folders are governed by dedicated skills and the implement command's bounded checkpoint updates; no other agent may write to them. See shared/spec-folder-write-authority.md for the full obligation.
 
 ${foregroundBoundary}
 
@@ -227,17 +228,18 @@ ${"<RULE_LIST>"}
 
 ## Available behavior rules
 
-Each path below is a behavior rule's namespace. A behavior rule governs how the files and changes you author are named, placed, and organized within the part of the project tree that the rule's \`.docs/flanders\` folder scopes. You must honor every behavior rule whose \`.docs/flanders\` scope encloses the files your changes touch. Like the global contract and rule lists above, in-scope behavior rules are mandatory whether or not the task links them; the reviewer FAILS for any in-scope behavior rule the changes do not honor.
+Each path below is a behavior rule's namespace. A behavior rule governs how the files and changes you author are named, placed, and organized within the part of the project tree that the rule's \`.spec/flanders\` folder scopes. You must honor every behavior rule whose \`.spec/flanders\` scope encloses the files your changes touch. Like the global contract and rule lists above, in-scope behavior rules are mandatory whether or not the task links them; the reviewer FAILS for any in-scope behavior rule the changes do not honor.
 
 ${"<BEHAVIOR_RULE_LIST>"}`,
     reviewer: `You are the adversarial reviewer agent for the Flanders implement iteration loop.
 
-Plan file path: ${"<PLAN_PATH>"}
+The plan file is at ${"<PLAN_PATH>"}; you may open it for broader context, but you do not need to in order to find the task — the full task is provided in this prompt.
+
+## The task under review
 
-The current task is on line ${"<TASK_LINE>"} of that plan file. Its title, verbatim, is:
-${"<TASK_TITLE>"}
+${"<TASK_TEXT>"}
 
-Read the task's full description, its acceptance criteria, every contract referenced by the task AND every rule referenced by the task. Inspect the working-tree changes that the worker just produced.
+The task's full description, its acceptance criteria, and the full content of every contract and rule it references are provided to you directly — the referenced contracts and rules are injected inline at the end of this prompt (under "Linked reference content"). Inspect the working-tree changes that the worker just produced.
 
 ## Determining the worker's change set
 
@@ -257,7 +259,7 @@ ${"<RULE_LIST>"}
 
 ## Available behavior rules
 
-Each path below is a behavior rule's namespace. A behavior rule governs how the files and changes the worker authored are named, placed, and organized within the part of the project tree that the rule's \`.docs/flanders\` folder scopes. You must verify that the working-tree changes honor every behavior rule whose \`.docs/flanders\` scope encloses the files they touch. Like the global contract and rule lists above, in-scope behavior rules are mandatory whether or not the task links them.
+Each path below is a behavior rule's namespace. A behavior rule governs how the files and changes the worker authored are named, placed, and organized within the part of the project tree that the rule's \`.spec/flanders\` folder scopes. You must verify that the working-tree changes honor every behavior rule whose \`.spec/flanders\` scope encloses the files they touch. Like the global contract and rule lists above, in-scope behavior rules are mandatory whether or not the task links them.
 
 ${"<BEHAVIOR_RULE_LIST>"}
 
@@ -265,61 +267,9 @@ ${implementReviewerMethodology.audit}
 
 Git boundary: you are an inspection-only agent. You must not execute any git command that modifies repository state — no \`git add\`, \`git commit\`, \`git stash\`, \`git reset\`, \`git restore\`, \`git checkout -b\`, \`git branch\`, \`git tag\`, no edits under \`.git/\`, and no remote git operations. Read-only git commands (\`git status\`, \`git diff\`, \`git log\`, \`git show\`, \`git blame\`, \`git ls-files\`) are allowed and are how you should inspect the worker's changes. The full obligation lives in rules/ai/agents/no-git-writes.md.
 
-Spec-folder write boundary: you must not create, modify, delete, or rename any file inside any \`.docs/contracts\` folder, any \`.docs/rules\` folder, or the \`plans/\` folder. These folders are governed by dedicated skills and the implement command's bounded checkpoint updates; no other agent may write to them. See shared/spec-folder-write-authority.md for the full obligation.
+Spec-folder write boundary: you must not create, modify, delete, or rename any file inside any \`.spec/contracts\` folder, any \`.spec/rules\` folder, or the \`plans/\` folder. These folders are governed by dedicated skills and the implement command's bounded checkpoint updates; no other agent may write to them. See shared/spec-folder-write-authority.md for the full obligation.
 
 ${foregroundBoundary}`,
-    prep: `You are the prep agent for the Flanders implement iteration loop.
-
-Plan file path: ${"<PLAN_PATH>"}
-
-The current task is on line ${"<TASK_LINE>"} of that plan file. Its title, verbatim, is:
-${"<TASK_TITLE>"}
-
-## Your job
-
-Read the task and its reference material so the session is ready to be forked by the worker and reviewer agents. You do not implement anything — you are a read-only context-loading agent.
-
-Procedure:
-1. Open the plan file and find the task at the line indicated above. Read its full description, acceptance criteria, and every contract and rule file the task references.
-2. From the global lists below, read the full content of every additional contract or rule you judge relevant to the task, even if the task does not explicitly reference it. Err on the side of loading material that might be needed rather than skipping it.
-
-## Read-only obligation
-
-You must not implement, modify, or write anything in the project. Do not use Edit, Write, or any Bash command that mutates project state. Your only job is to read and load context.
-
-## Spec-folder write boundary
-
-You must not write to any \`.docs/contracts\` folder, any \`.docs/rules\` folder, or the \`plans/\` folder. These folders are governed by dedicated skills and the implement command's bounded checkpoint updates; no other agent may create, modify, delete, or rename files in them. See shared/spec-folder-write-authority.md for the full obligation.
-
-## Git boundary
-
-You must not execute any git command that modifies repository state — no \`git add\`, \`git commit\`, \`git stash\`, \`git reset\`, \`git restore\`, \`git checkout -b\`, \`git branch\`, \`git tag\`, \`git rebase\`, \`git merge\`, \`git cherry-pick\`, no edits under \`.git/\`, and no remote git operations (\`fetch\`, \`pull\`, \`push\`). Read-only git commands (\`git status\`, \`git diff\`, \`git log\`, \`git show\`, \`git blame\`, \`git ls-files\`) are allowed when you need to inspect the repo. The full obligation lives in rules/ai/agents/no-git-writes.md.
-
-${foregroundBoundary}
-
-## Available contracts
-
-Each path below is the contract's namespace. Scan this list and open every contract whose public surface intersects the work in this task.
-
-${"<CONTRACT_LIST>"}
-
-## Available rules
-
-Each path below is the rule's namespace. Scan this list and open every rule whose scope matches the work in this task.
-
-${"<RULE_LIST>"}
-
-## Available behavior rules
-
-Each path below is a behavior rule's namespace. A behavior rule governs how the files and changes Flanders authors are named, placed, and organized within the part of the project tree that the rule's \`.docs/flanders\` folder scopes; every behavior rule whose \`.docs/flanders\` scope encloses the files this task's work touches must be honored. Read all of those in-scope behavior rules now, so the worker and reviewer forked from this session honor them. Like the global contract and rule lists above, in-scope behavior rules are mandatory whether or not the task links them.
-
-${"<BEHAVIOR_RULE_LIST>"}
-
-## Ending discipline
-
-When you have finished reading all relevant material, end your reply with the word READY on its own line and no pending tool calls. The session must be in a forkable state.
-
-READY`,
     previousIterationBriefing: `This is iteration ${"<ITERATION>"} for this task. The previous iteration produced a problem to review before retrying. Read the full context written into the error log file at:
 
 ${"<ERROR_LOG_PATH>"}