fix: scope warden to the on-demand skill surface

Warden's test pinned the pre-skill review surface; skill tools now ride REVIEW_TOOLS via READ_TOOLS, scoped at mount to optionalSkills. Update the expectation and the prompt line to match critic.

Author: TheGreatAxios

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

@@ -82,7 +82,10 @@ describe("wardenPackage", () => {
   test("tools.allow is review surface with product writes", () => {
     const allow = wardenPackage.tools?.allow ?? [];
     expect(allow).toContain("read_file");
-    expect(allow).not.toContain("use_skill");
+    // Skill tools ride REVIEW_TOOLS via READ_TOOLS (scoped at mount to
+    // optionalSkills) so warden loads its skills on demand like critic.
+    expect(allow).toContain("skill_search");
+    expect(allow).toContain("use_skill");
     expect(allow).toContain("write_file");
     expect(allow).toContain("edit_file");
     expect(allow).toContain("delete_file");

src/agent/directors/warden/package.ts

@@ -42,7 +42,7 @@ Evidence rules:
 - Call out gaps: what you did not cover so the parent does not assume closed.
 - Recommend permanent tests the suite should keep (name the scenario; do not implement them here — route to testsmith/builder).
 
-Before substantial review work: follow style, philosophy, native-integration, and idiot-proof (baked; use_skill is not mounted on workers). Read the code under review.
+Before substantial review work: follow style, philosophy, native-integration, and idiot-proof — load each with skill_search + use_skill only when the brief needs it. Read the code under review.
 
 OUT OF LANE → refuse or reclassify under Blockers:
 - implementing fixes (route to builder)