chatroom-cli 1.123.3 → 1.124.0

package/dist/index.js

@@ -20376,6 +20376,10 @@ var init_agent_role = __esm(() => {
         { teamId: "duo", order: 40 },
         { teamId: "solo", order: 40 }
       ]
+    },
+    researcher: {
+      tags: ["ephemeral" /* Ephemeral */],
+      teams: [{ teamId: "duo", order: 25 }]
     }
   };
   AGENT_ROLE_DEFINITIONS = Object.fromEntries(Object.entries(roleMetadata).map(([role, metadata]) => [role, { role, ...metadata }]));
@@ -99325,7 +99329,7 @@ var init_team_presets = __esm(() => {
     duo: {
       structureId: TEAM_STRUCTURE_IDS.duo,
       name: "Duo",
-      description: "A planner and builder working as a pair, planner as coordinator, with optional ephemeral architect, triage, and uiux-engineer roles",
+      description: "A planner and builder working as a pair, planner as coordinator, with optional ephemeral architect, researcher, triage, and uiux-engineer roles",
       roles: getBuiltinRolesForTeam("duo"),
       entryPoint: "planner"
     },
@@ -100007,6 +100011,8 @@ function getPlannerToBuilderHandoffTemplate() {
 
 ${getDelegationBriefIntro()}
 
+**Before you delegate:** if this slice introduces anything not yet grounded in the repository (a new library, API, external platform behavior, or an unresolved design choice), hand off to \`researcher\` first and delegate only after its brief returns. Skip this for small, well-understood edits. The \`researcher\` handoff template defines the criteria.
+
 **Division of labor:** You (planner) own architecture and API shape. The UI/UX engineer owns UI/UX design. Include its target markup, classes, and styles in UI implementation briefs; the builder implements the components.
 
 **Detail bar:** Specify down to **every file** the builder will create or modify (full repo paths). Include code snippets — types, signatures, stubs, or target implementations — until a competent builder **cannot misinterpret** what to write. Vague layers ("update the backend", "fix the component") are not acceptable.
@@ -100260,12 +100266,96 @@ function getChatToUserHandoffTemplate() {
 }
 var init_chat_handoff_template = () => {};
 
-// ../../services/backend/prompts/teams/triage-handoff-templates.ts
+// ../../services/backend/prompts/teams/researcher-handoff-templates.ts
 function normalizeEntryPointRole3(entryPointRole) {
   return entryPointRole.trim().toLowerCase() || "planner";
 }
-function getEntryPointToTriageHandoffTemplate(entryPointRole) {
+function getEntryPointToResearcherHandoffTemplate(entryPointRole) {
   const entryPoint = normalizeEntryPointRole3(entryPointRole);
+  return `${getHandoffRecipientVisibilityCallout("researcher")}
+
+## Handoff Template (${entryPoint} → researcher)
+
+The automatically injected \`<user-message>\` is the authoritative request. Pass the decisions the research must ground, the specific research questions, known constraints, and the files or areas already suspected. Ask the researcher for a report only: do not edit files, implement code, or design alternative architectures.
+
+### When to research
+
+Research before delegating when the slice introduces something not already grounded in this repository:
+- a new library, API, external service, platform behavior, or version-sensitive dependency;
+- an unfamiliar subsystem;
+- a change with several plausible designs;
+- any ambiguity the user has not resolved.
+
+Skip research when the change is a small, well-understood edit in code you have already inspected.
+
+After completing the research, the researcher must return the evidence-backed brief to \`${entryPoint}\` with the normal handoff command.
+
+\`\`\`bash
+${handoffCommand({
+    chatroomId: "<chatroom-id>",
+    role: entryPoint,
+    nextRole: "researcher",
+    cliEnvPrefix: ""
+  })}
+\`\`\``;
+}
+function getResearcherToEntryPointHandoffTemplate(entryPointRole) {
+  const entryPoint = normalizeEntryPointRole3(entryPointRole);
+  return `${getHandoffRecipientVisibilityCallout(entryPoint)}
+
+## Handoff Template (Researcher → ${entryPoint})
+
+Return a complete, evidence-backed research brief for the authoritative request. The researcher is advisory: do not edit files, implement code, or present alternative architectures beyond what grounds the decision. Answer only the questions asked. Separate every finding into confirmed (with evidence), inferred (with reasoning), or unknown. Never present a guess as fact. External claims must cite the source URL together with the version or date checked. Use the exact sections below, in this order.
+
+## Summary
+<state the answer to the core question in two to four sentences and whether any decision remains open>
+
+## Research questions
+<list each question exactly as asked or as derived from the request, numbered>
+
+## Answers
+<one entry per question, each tagged \`confirmed\` (with evidence), \`inferred\` (with reasoning), or \`unknown\`>
+
+## Repository evidence
+<concrete repository paths and symbols with what each shows; quote the relevant lines briefly>
+
+## External sources
+<URL, version or date checked, and the specific claim each source supports; write exactly \`None consulted.\` if no external source was needed, and say why>
+
+## Grounded facts for the plan
+<the facts the planner can rely on when decomposing and delegating, each tagged confirmed or inferred>
+
+## Remaining ambiguity
+<each open decision, who must decide it, and a recommended default; write exactly \`None observed.\` if none remain>
+
+## Risks and constraints
+<constraints from the repository or external platform, and risks the plan must account for>
+
+## Work completed
+<paths inspected, searches run, and sources opened, with the result of each>
+
+## Handoff
+Run the normal handoff command to \`${entryPoint}\` with this complete brief, then stop.
+
+\`\`\`bash
+${handoffCommand({
+    chatroomId: "<chatroom-id>",
+    role: "researcher",
+    nextRole: entryPoint,
+    cliEnvPrefix: ""
+  })}
+\`\`\``;
+}
+var init_researcher_handoff_templates = __esm(() => {
+  init_command2();
+});
+
+// ../../services/backend/prompts/teams/triage-handoff-templates.ts
+function normalizeEntryPointRole4(entryPointRole) {
+  return entryPointRole.trim().toLowerCase() || "planner";
+}
+function getEntryPointToTriageHandoffTemplate(entryPointRole) {
+  const entryPoint = normalizeEntryPointRole4(entryPointRole);
   return `${getHandoffRecipientVisibilityCallout("triage")}
 
 ## Handoff Template (${entryPoint} → triage)
@@ -100284,7 +100374,7 @@ ${handoffCommand({
 \`\`\``;
 }
 function getTriageToEntryPointHandoffTemplate(entryPointRole) {
-  const entryPoint = normalizeEntryPointRole3(entryPointRole);
+  const entryPoint = normalizeEntryPointRole4(entryPointRole);
   return `${getHandoffRecipientVisibilityCallout(entryPoint)}
 
 ## Handoff Template (Triage → ${entryPoint})
@@ -100335,17 +100425,19 @@ var init_planner = __esm(() => {
   init_planner_to_user();
   init_chat_handoff_template();
   init_architect_handoff_templates();
+  init_researcher_handoff_templates();
   init_triage_handoff_templates();
   init_uiux_engineer_handoff_templates();
   duoPlannerHandoffContract = {
     role: "planner",
-    receivesFrom: ["user", "builder", "architect", "uiux-engineer", "triage"],
-    returnsTo: ["builder", "architect", "uiux-engineer", "triage", "user"],
+    receivesFrom: ["user", "builder", "architect", "uiux-engineer", "triage", "researcher"],
+    returnsTo: ["builder", "architect", "uiux-engineer", "triage", "researcher", "user"],
     outboundTemplates: {
       builder: () => getPlannerToBuilderHandoffTemplate(),
       architect: () => getEntryPointToArchitectHandoffTemplate("planner"),
       "uiux-engineer": () => getEntryPointToUiuxEngineerHandoffTemplate("planner"),
       triage: () => getEntryPointToTriageHandoffTemplate("planner"),
+      researcher: () => getEntryPointToResearcherHandoffTemplate("planner"),
       user: (query) => query.conversationMode === "chat" ? getChatToUserHandoffTemplate() : getPlannerToUserReportTemplate({
         chatroomId: query.chatroomId,
         role: query.role,
@@ -100355,6 +100447,20 @@ var init_planner = __esm(() => {
   };
 });
 
+// ../../services/backend/prompts/teams/duo/handoff-templates/researcher.ts
+var duoResearcherHandoffContract;
+var init_researcher = __esm(() => {
+  init_researcher_handoff_templates();
+  duoResearcherHandoffContract = {
+    role: "researcher",
+    receivesFrom: ["planner"],
+    returnsTo: ["planner"],
+    outboundTemplates: {
+      planner: () => getResearcherToEntryPointHandoffTemplate("planner")
+    }
+  };
+});
+
 // ../../services/backend/prompts/teams/duo/handoff-templates/triage.ts
 var duoTriageHandoffContract;
 var init_triage = __esm(() => {
@@ -100524,6 +100630,7 @@ var init_handoff_templates = __esm(() => {
   init_architect();
   init_builder();
   init_planner();
+  init_researcher();
   init_triage();
   init_uiux_engineer();
   init_contracts();
@@ -100531,6 +100638,7 @@ var init_handoff_templates = __esm(() => {
     planner: duoPlannerHandoffContract,
     builder: duoBuilderHandoffContract,
     architect: duoArchitectHandoffContract,
+    researcher: duoResearcherHandoffContract,
     "uiux-engineer": duoUiuxEngineerHandoffContract,
     triage: duoTriageHandoffContract
   };
@@ -101143,6 +101251,31 @@ var init_planner2 = __esm(() => {
   init_sections();
 });
 
+// ../../services/backend/prompts/cli/roles/researcher.ts
+var RESEARCHER_GUIDANCE;
+var init_researcher2 = __esm(() => {
+  init_sections();
+  RESEARCHER_GUIDANCE = `## Researcher Operating Model
+
+You are the researcher responsible for grounding a request with evidence so the planner can decide and delegate without ambiguity. You are advisory only: do not edit files, implement code, or act as the builder or planner.
+
+${"{SESSION_CONTINUITY}"}
+
+${getInterRoleHandoffRule()}
+
+1. Recover the authoritative request and the research questions from the injected task and chatroom history. If the questions are not explicit, derive the decisions the planner must make and answer those.
+2. Investigate the repository first: existing modules, APIs, types, patterns, tests, and conventions that bear on the request. Cite concrete paths and symbols.
+3. Investigate external sources when the request depends on libraries, APIs, platform behavior, versions, or recent changes. Prefer official documentation and primary sources. Record the URL, the version, and the date checked.
+4. Label every finding \`confirmed\`, \`inferred\`, or \`unknown\`. Never present a guess as fact.
+5. Resolve ambiguity where evidence allows. For the rest, state the open question, who must decide it, and a recommended default.
+6. Follow the injected \`<handoff-templates>\` research brief exactly, in its order. Answer only the questions asked. Do not present alternative architectures beyond what grounds the decision.
+7. Hand the brief to the configured entry point with the normal command, then stop:
+
+\`\`\`bash
+chatroom handoff --chatroom-id="<chatroom-id>" --role="researcher" --next-role="{ENTRY_POINT_ROLE}"
+\`\`\``;
+});
+
 // ../../services/backend/prompts/cli/roles/uiux-engineer.ts
 var UIUX_ENGINEER_GUIDANCE;
 var init_uiux_engineer3 = __esm(() => {
@@ -101191,6 +101324,7 @@ var init_fromContext2 = __esm(() => {
   init_architect3();
   init_builder2();
   init_planner2();
+  init_researcher2();
   init_uiux_engineer3();
   init_fromContext();
 });
@@ -101268,6 +101402,19 @@ var init_templates = __esm(() => {
       ],
       defaultHandoffTarget: "planner"
     },
+    researcher: {
+      role: "researcher",
+      title: "Researcher",
+      description: "You are the researcher responsible for producing one evidence-backed research brief that grounds the request for planning; you are not an implementer.",
+      responsibilities: [
+        "Recover the authoritative user request and the decisions the planner must make",
+        "Inspect the repository for existing code, patterns, and constraints that bear on the request",
+        "Consult official documentation and primary sources for external facts, APIs, versions, and behavior",
+        "Label every finding as confirmed, inferred, or unknown, with citations",
+        "Hand one grounded research brief to the planner, including the remaining ambiguity and a recommended default"
+      ],
+      defaultHandoffTarget: "planner"
+    },
     triage: {
       role: "triage",
       title: "Triage Agent",
@@ -128856,4 +129003,4 @@ program2.hook("preAction", async (_thisCommand, actionCommand) => {
 });
 program2.parse();
 
-//# debugId=A4F00C6913ED47A764756E2164756E21
+//# debugId=63EAC0BA8745C9A064756E2164756E21