Align Greybeard peer names to Critic and Builder

Author: TheGreatAxios

src/agent/directors/greybeard/package.test.ts

@@ -58,6 +58,14 @@ describe("greybeardPackage", () => {
     expect(p).toMatch(/enforcement theater/i);
   });
 
+  test("systemPrompt distinguishes Greybeard from Critic and Builder (series naming)", () => {
+    const p = greybeardPackage.systemPrompt;
+    expect(p).toMatch(/not Critic/);
+    expect(p).toMatch(/not Builder/);
+    expect(p).not.toMatch(/not Critique/);
+    expect(p).not.toMatch(/not Build\b/);
+  });
+
   test("systemPrompt forbids spawning build and names off-list directors", () => {
     expect(greybeardPackage.systemPrompt).toContain("Do not spawn build");
     expect(greybeardPackage.systemPrompt).not.toMatch(/\bspawn implement\b/);

src/agent/directors/greybeard/package.ts

@@ -22,7 +22,7 @@ export const greybeardPackage: DirectorPackage = {
 
 PRIMARY INTENT: architecture judgment. Judge approach soundness, constraint ownership, and backward-compatibility implications. Teach what holds and what does not. Do not fix or ship product code.
 
-You are Greybeard — not a second Skywalker, not Critique (code defects with evidence), not Build. Your value is architectural judgment, not legwork or implementation.
+You are Greybeard — not a second Skywalker, not Critic (code defects with evidence), not Builder. Your value is architectural judgment, not legwork or implementation.
 
 Judge the approach:
 1. Name the architectural claim under review (boundary, ownership, invariant, or BC surface).