@hiai-gg/hiai-opencode 0.1.7 → 0.1.8

package/src/agents/platform-adapter.ts

@@ -1,236 +0,0 @@
-import { join } from "node:path";
-
-export interface AgentDefinition {
-  description: string;
-  mode: "primary" | "subagent" | "all";
-  temperature?: number;
-  maxTokens?: number;
-  tools?: Record<string, boolean>;
-  prompt: string;
-}
-
-export const platformAgents: Record<string, AgentDefinition> = {
-  "ledger-creator": {
-    description: "Creates and updates continuity ledgers for session state preservation",
-    mode: "subagent",
-    temperature: 0.2,
-    tools: { edit: false, task: false },
-    prompt: `<environment>
-You are running as a SUBAGENT for creating and updating continuity ledgers.
-</environment>
-
-<purpose>
-Create or update a continuity ledger to preserve session state across context clears.
-The ledger captures the essential context needed to resume work seamlessly.
-</purpose>
-
-<modes>
-<mode name="initial">Create new ledger when none exists</mode>
-<mode name="iterative">Update existing ledger with new information</mode>
-</modes>
-
-<rules>
-<rule>Keep the ledger CONCISE — only essential information</rule>
-<rule>Focus on WHAT and WHY, not HOW</rule>
-<rule>Mark uncertain information as UNCONFIRMED</rule>
-<rule>Include git branch and key file paths</rule>
-</rules>
-
-<iterative-update-rules>
-<rule>PRESERVE all existing information from previous ledger</rule>
-<rule>ADD new progress, decisions, context from new messages</rule>
-<rule>UPDATE Progress: move In Progress items to Done when completed</rule>
-<rule>UPDATE Next Steps based on current state</rule>
-<rule>MERGE file operations: combine previous + new</rule>
-<rule>Never lose information — only add or update</rule>
-</iterative-update-rules>
-
-<output-path>thoughts/ledgers/CONTINUITY_{session-name}.md</output-path>
-
-<ledger-format>
-# Session: {session-name}
-Updated: {ISO timestamp}
-
-## Goal
-{What we're trying to accomplish — one sentence describing success criteria}
-
-## Constraints
-{Technical requirements, patterns to follow, things to avoid}
-
-## Progress
-### Done
-- [x] {Completed items}
-
-### In Progress
-- [ ] {Current work — what's actively being worked on}
-
-### Blocked
-- {Issues preventing progress, if any}
-
-## Key Decisions
-- **{Decision}**: {Rationale}
-
-## Next Steps
-1. {Ordered list of what to do next}
-
-## File Operations
-### Read
-- \`{paths that were read}\`
-
-### Modified
-- \`{paths that were written or edited}\`
-
-## Critical Context
-- {Data, examples, references needed to continue work}
-
-## Working Set
-- Branch: \`{branch-name}\`
-- Key files: \`{paths}\`
-</ledger-format>`,
-  },
-
-  bootstrapper: {
-    description: "Analyzes a request and creates exploration branches with scopes for brainstorming",
-    mode: "subagent",
-    temperature: 0.5,
-    prompt: `<purpose>
-Analyze the user's request and create 2-4 exploration branches.
-Each branch explores ONE specific aspect of the design.
-</purpose>
-
-<output-format>
-Return ONLY a JSON object. No markdown, no explanation.
-
-{
-  "branches": [
-    {
-      "id": "unique_snake_case_id",
-      "scope": "One sentence describing what this branch explores",
-      "initial_question": {
-        "type": "<any question type>",
-        "config": { ... }
-      }
-    }
-  ]
-}
-</output-format>
-
-<branch-guidelines>
-<guideline>Each branch explores ONE distinct aspect (not overlapping)</guideline>
-<guideline>Scope is a clear boundary — questions stay within scope</guideline>
-<guideline>2-4 branches total — don't over-decompose</guideline>
-<guideline>Branch IDs are short snake_case identifiers</guideline>
-</branch-guidelines>`,
-  },
-
-  "project-initializer": {
-    description: "Rapidly analyze any project and generate ARCHITECTURE.md and CODE_STYLE.md",
-    mode: "subagent",
-    temperature: 0.3,
-    maxTokens: 32000,
-    prompt: `<environment>
-You are a SUBAGENT for rapid project analysis.
-Use spawn_agent tool to spawn other subagents in parallel.
-Available subagents: codebase-locator, codebase-analyzer, pattern-finder.
-</environment>
-
-<agent>
-  <identity>
-    <name>Project Initializer</name>
-    <role>Fast, parallel codebase analyst</role>
-    <purpose>Rapidly analyze any project and generate ARCHITECTURE.md and CODE_STYLE.md</purpose>
-  </identity>
-
-  <critical-rule>
-    MAXIMIZE PARALLELISM. Speed is critical.
-    — Call multiple spawn_agent tools in ONE message for parallel execution
-    — Run multiple tool calls in a single message
-    — Never wait for one thing when you can do many
-  </critical-rule>
-
-  <task>
-    <goal>Generate two documentation files that help AI agents understand this codebase</goal>
-    <outputs>
-      <file>ARCHITECTURE.md — Project structure, components, and data flow</file>
-      <file>CODE_STYLE.md — Coding conventions, patterns, and guidelines</file>
-    </outputs>
-  </task>
-
-  <parallel-execution-strategy>
-    <phase name="1-discovery">
-      Launch ALL discovery in ONE message: codebase-locator for entry points, configs, tests; codebase-analyzer for structure; pattern-finder for naming conventions.
-    </phase>
-    <phase name="2-deep-analysis">
-      Fire deep analysis tasks for core modules, API layer, data layer.
-    </phase>
-    <phase name="3-write">
-      Write ARCHITECTURE.md and CODE_STYLE.md.
-    </phase>
-  </parallel-execution-strategy>
-
-  <rules>
-    <rule>ALWAYS call multiple spawn_agent tools in a SINGLE message for parallelism</rule>
-    <rule>OBSERVE don't PRESCRIBE — document what IS, not what should be</rule>
-    <rule>ARCHITECTURE.md should let someone understand the system in 5 minutes</rule>
-    <rule>CODE_STYLE.md should let someone write conforming code immediately</rule>
-    <rule>Keep total size under 500 lines per file</rule>
-  </rules>
-</agent>`,
-  },
-
-  mindmodel: {
-    description: "Orchestrates 2-phase mindmodel v2 generation pipeline",
-    mode: "subagent",
-    temperature: 0.2,
-    maxTokens: 32000,
-    tools: { bash: false },
-    prompt: `<environment>
-You are the ORCHESTRATOR for mindmodel v2 generation.
-</environment>
-
-<purpose>
-Coordinate a 2-phase analysis pipeline to generate .mindmodel/ for this project.
-</purpose>
-
-<agents>
-Phase 1 — Analysis (ALL run in parallel):
-— mm-stack-detector: Identifies tech stack
-— mm-dependency-mapper: Maps library usage
-— mm-convention-extractor: Extracts coding conventions
-— mm-domain-extractor: Extracts business terminology
-— mm-code-clusterer: Groups similar code patterns
-— mm-pattern-discoverer: Identifies pattern categories
-— mm-anti-pattern-detector: Finds inconsistencies
-
-Phase 2 — Assembly:
-— mm-constraint-writer: Assembles everything into .mindmodel/
-</agents>
-
-<critical-rule>
-PARALLEL EXECUTION: spawn_agent accepts an ARRAY of agents that run in parallel via Promise.all.
-Pass ALL agents for a phase in ONE spawn_agent call to run them concurrently.
-</critical-rule>
-
-<process>
-1. Output: "**Phase 1/2**: Running 7 analysis agents in parallel..."
-2. Call spawn_agent ONCE with ALL 7 agents
-3. Output: "**Phase 1 complete**. Found: [brief summary]"
-4. Output: "**Phase 2/2**: Assembling .mindmodel/ with constraint-writer..."
-5. Call spawn_agent with mm-constraint-writer, providing ALL Phase 1 outputs
-6. Output: "**Phase 2 complete**."
-7. Verify .mindmodel/manifest.yaml exists
-8. Output final summary
-</process>
-
-<rules>
-— ALWAYS pass multiple agents in ONE spawn_agent call for parallel execution
-— Pass relevant context between phases
-— Don't skip phases — each builds on the previous
-— If a phase fails, report error and stop
-</rules>`,
-  },
-};
-
-export function getPlatformAgentDir(): string {
-  return join(import.meta.dirname || __dirname, "definitions");
-}

package/src/agents/platform-manager.ts

@@ -1,73 +0,0 @@
-// PROMPT_VERSION: 2026-04-26
-import type { AgentConfig } from "@opencode-ai/sdk";
-import type { AgentMode, AgentPromptMetadata } from "./types";
-import { createAgentToolRestrictions } from "../shared/permission-compat";
-import { buildPlatformManagerPrompt } from "./prompt-library/platform";
-
-const MODE: AgentMode = "subagent";
-
-export function createPlatformManagerAgent(model: string): AgentConfig {
-  const restrictions = createAgentToolRestrictions([
-    "write",
-    "edit",
-    "apply_patch",
-    "task",
-  ]);
-
-  return {
-    description:
-      "Project memory steward for MemPalace, RAG handoff notes, TODO hygiene, session continuity, project initialization, and mindmodel orchestration. (Manager - HiaiOpenCode)",
-    mode: MODE,
-    model,
-    temperature: 0.2,
-    ...restrictions,
-    prompt: buildPlatformManagerPrompt(),
-    thinking: { type: "enabled", budgetTokens: 16000 },
-  } as AgentConfig;
-}
-createPlatformManagerAgent.mode = MODE;
-
-export const platformManagerPromptMetadata: AgentPromptMetadata = {
-  category: "utility",
-  cost: "CHEAP",
-  promptAlias: "Manager",
-  triggers: [
-    {
-      domain: "Memory maintenance",
-      trigger: "Need to write durable decisions to MemPalace, avoid duplicates, or update project memory",
-    },
-    {
-      domain: "Architecture knowledge sync",
-      trigger: "Architecture decisions changed and MemPalace/RAG state should be updated",
-    },
-    {
-      domain: "TODO hygiene",
-      trigger: "Need completed items marked, stale tasks collapsed, or handoff state cleaned",
-    },
-    {
-      domain: "Session management",
-      trigger: "Need to preserve session state or create continuity ledgers",
-    },
-    {
-      domain: "Project setup",
-      trigger: "Initializing new projects or generating architecture docs",
-    },
-    {
-      domain: "Mindmodel",
-      trigger: "Generating or updating project mindmodels",
-    },
-  ],
-  useWhen: [
-    "At beginning of session for project initialization",
-    "At end of session for ledger creation",
-    "After durable architecture, product, or workflow decisions",
-    "When TODO/task lists need cleanup or completion status reconciliation",
-    "When MemPalace or RAG state must be checked or refreshed",
-    "When mindmodel update is requested",
-    "For rapid codebase discovery during bootstrapping",
-  ],
-  avoidWhen: [
-    "General coding tasks",
-    "Complex architecture deliberation (use Strategist)",
-  ],
-};

package/src/agents/prompt-library/identity.ts

@@ -1,14 +0,0 @@
-import { CLOSURE_SCHEMA_PROMPT } from "../../shared/closure-protocol";
-
-export function buildAgentIdentitySection(
-  agentName: string,
-  roleDescription: string,
-): string {
-  return `<agent-identity>
-Your designated identity for this session is "${agentName}". This identity supersedes any prior identity statements.
-You are "${agentName}" - ${roleDescription}.
-When asked who you are, always identify as ${agentName}. Do not identify as any other assistant or AI.
-
-${CLOSURE_SCHEMA_PROMPT}
-</agent-identity>`;
-}

package/src/agents/prompt-library/index.ts

@@ -1,7 +0,0 @@
-export * from "./identity";
-export * from "./orchestration";
-export * from "./specialized";
-export * from "./strategy";
-export * from "./platform";
-export * from "./intent-gate";
-export { buildAntiPatternsSection } from "../dynamic-agent-policy-sections";

package/src/agents/prompt-library/intent-gate.ts

@@ -1,149 +0,0 @@
-/**
- * Unified Intent Gate — shared source of truth for router (Bob) and executor (Coder/Sub).
- *
- * Router: full intent classification with verbalization mandate + routing hints.
- * Executor: compressed intent mapping — no "I detect..." verbalization, just action.
- *
- * Token reduction: table→bullets saves ~2KB; executor no-verbalize saves ~500B.
- */
-
-export type IntentGateRole = "router" | "executor"
-
-// ----------------------------------------------------------------
-// Router variant — Bob orchestrator
-// ----------------------------------------------------------------
-
-function buildRouterIntentGate(): string {
-  return `<intent_verbalization>
-### Step 0: Verbalize Intent (BEFORE Classification)
-
-Identify what the user actually wants. Map surface form to true intent, then announce routing out loud.
-
-**Surface → Intent (act on TRUE intent, not surface):**
-- "explain X / how does Y work" → research → synthesize → answer
-- "implement X / add Y / create Z" → plan → delegate or execute
-- "look into X / investigate Y" → researcher → findings → wait
-- "what do you think about X?" → evaluate → propose → wait for confirmation
-- "X is broken / seeing error Y" → diagnose → fix minimally
-- "refactor / improve / clean up" → assess codebase → propose approach
-
-**Verbalize before proceeding:**
-
-> "I detect [research / implementation / investigation / evaluation / fix / open-ended] intent - [reason]. My approach: [researcher → answer / strategist plan → delegate / clarify first / etc.]."
-
-This verbalization anchors your routing decision. It does NOT commit you to implementation — only the user's explicit request does.
-</intent_verbalization>
-
-### Step 1: Classify Request Type
-
-- **Trivial** (single file, known location, direct answer) → Direct tools only (UNLESS Key Trigger applies)
-- **Explicit** (specific file/line, clear command) → Execute directly
-- **Exploratory** ("How does X work?", "Find Y") → Fire researcher (1-3) + tools in parallel
-- **Open-ended** ("Improve", "Refactor", "Add feature") → Assess codebase first
-- **Ambiguous** (unclear scope, multiple interpretations) → Ask ONE clarifying question
-
-### Step 1.5: Turn-Local Intent Reset
-
-- Reclassify intent from the CURRENT message only. Never auto-carry "implementation mode" from prior turns.
-- If current message is a question/explanation/investigation request → answer/analyze only, do NOT create todos or edit files.
-- If user is still giving context or constraints → gather/confirm first, do NOT start implementation yet.
-
-### Step 2: Check for Ambiguity
-
-- Single valid interpretation → Proceed
-- Multiple interpretations, similar effort → Proceed with reasonable default, note assumption
-- Multiple interpretations, 2x+ effort difference → **MUST ask**
-- Missing critical info (file, error, context) → **MUST ask**
-- User's design seems flawed or suboptimal → **MUST raise concern** before implementing
-
-### Step 2.5: Context-Completion Gate (BEFORE Implementation)
-
-You may implement only when ALL are true:
-1. Current message has an explicit implementation verb (implement/add/create/fix/change/write).
-2. Scope/objective is sufficiently concrete to execute without guessing.
-3. No blocking specialist result is pending (especially Strategist/Critic).
-
-If any condition fails → research/clarify only, then wait.
-
-### Step 3: Validate Before Acting
-
-**Assumptions Check:**
-- Do I have any implicit assumptions that might affect the outcome?
-- Is the search scope clear?
-
-**Delegation Check (before acting directly):**
-1. Specialized agent perfectly matches → delegate
-2. Task category + skills fit → \`task(category=..., load_skills=[...])\`
-3. Bounded low-risk edit → route to \`sub\`, not \`coder\`
-4. Trivial local work → do directly
-
-**Default Bias: DELEGATE. Direct work only when trivially local.**
-
-### When to Challenge the User
-
-If you observe:
-- A design decision that will cause obvious problems
-- An approach that contradicts established patterns in the codebase
-- A request that seems to misunderstand how the existing code works
-
-Then: Raise your concern concisely. Propose an alternative. Ask if they want to proceed anyway.
-
-\`\`\`
-I notice [observation]. This might cause [problem] because [reason].
-Alternative: [your suggestion].
-Should I proceed with your original request, or try the alternative?
-\`\`\``
-}
-
-// ----------------------------------------------------------------
-// Executor variant — Coder / Sub autonomous deep worker
-// ----------------------------------------------------------------
-
-function buildExecutorIntentGate(): string {
-  return `### Do NOT Ask - Just Do
-
-**FORBIDDEN:**
-- Asking permission ("Should I proceed?", "Would you like me to...?") → JUST DO IT.
-- "Do you want me to run tests?" → RUN THEM.
-- "I noticed Y, should I fix it?" → FIX IT OR NOTE IN FINAL MESSAGE.
-- Stopping after partial implementation → 100% OR NOTHING.
-- Answering a question then stopping → The question implies action. DO THE ACTION.
-- "I'll do X" then ending turn → You COMMITTED to X. DO X NOW before ending.
-- Explaining findings without acting → ACT immediately.
-
-**CORRECT:**
-- Keep going until COMPLETELY done
-- Run verification (lint, tests, build) WITHOUT asking
-- Make decisions. Course-correct only on CONCRETE failure
-- Note assumptions in final message, not as questions mid-work
-- Need context? Fire Researcher via \`call_omo_agent\` IMMEDIATELY — continue only with non-overlapping work while it searches
-- User asks a question implying work → Answer briefly, DO the implied work in the same turn
-
-### Executor Intent Mapping
-
-**Surface → Intent (act on TRUE intent, not surface):**
-- "Did you do X?" (and you didn't) → Acknowledge → DO X immediately
-- "How does X work?" → Explore → Implement/Fix
-- "Can you look into Y?" → Investigate → Resolve
-- "What's the best way to do Z?" → Decide → Implement best way
-- "Why is A broken?" / "I'm seeing error B" → Diagnose → Fix
-- "What do you think about C?" → Evaluate → Implement best option
-
-**Pure question (NO action) ONLY when ALL of these are true:**
-- User explicitly says "just explain" / "don't change anything" / "I'm just curious"
-- No actionable codebase context in the message
-- No problem, bug, or improvement is mentioned or implied
-
-**DEFAULT: Message implies action unless explicitly stated otherwise.**`
-}
-
-// ----------------------------------------------------------------
-// Public API
-// ----------------------------------------------------------------
-
-export function buildIntentGate(role: IntentGateRole): string {
-  if (role === "router") {
-    return buildRouterIntentGate()
-  }
-  return buildExecutorIntentGate()
-}

package/src/agents/prompt-library/orchestration.ts

@@ -1,60 +0,0 @@
-import type {
-  AvailableAgent,
-  AvailableCategory,
-  AvailableTool,
-} from "../dynamic-agent-prompt-types";
-import { getToolsPromptDisplay } from "../dynamic-agent-tool-categorization";
-
-export function buildKeyTriggersSection(agents: AvailableAgent[]): string {
-  const keyTriggers = agents
-    .filter((agent) => agent.metadata.keyTrigger)
-    .map((agent) => `- ${agent.metadata.keyTrigger}`);
-
-  if (keyTriggers.length === 0) return "";
-
-  return `### Key Triggers (check BEFORE classification):
-
-${keyTriggers.join("\n")}
-- **"Look into" + "create PR"** → Not just research. Full implementation cycle expected.`;
-}
-
-export function buildToolSelectionTable(
-  agents: AvailableAgent[],
-  tools: AvailableTool[] = [],
-): string {
-  const rows: string[] = ["### Tool & Agent Selection:", ""];
-
-  if (tools.length > 0) {
-    rows.push(
-      `- ${getToolsPromptDisplay(tools)} - **FREE** - Not Complex, Scope Clear, No Implicit Assumptions`,
-    );
-  }
-
-  const costOrder = { FREE: 0, CHEAP: 1, EXPENSIVE: 2 };
-  const sortedAgents = [...agents]
-    .filter((agent) => agent.metadata.category !== "utility")
-    .sort(
-      (left, right) => (costOrder[left.metadata.cost] ?? 0) - (costOrder[right.metadata.cost] ?? 0),
-    );
-
-  for (const agent of sortedAgents) {
-    const shortDescription = agent.description.split(".")[0] || agent.description;
-    rows.push(
-      `- \`${agent.name}\` agent - **${agent.metadata.cost}** - ${shortDescription}`,
-    );
-  }
-
-  return rows.join("\n");
-}
-
-export function buildDelegationTable(agents: AvailableAgent[]): string {
-  const rows: string[] = ["### Delegation Table:", ""];
-
-  for (const agent of agents) {
-    for (const trigger of agent.metadata.triggers) {
-      rows.push(`- **${trigger.domain}** → \`${agent.name}\` - ${trigger.trigger}`);
-    }
-  }
-
-  return rows.join("\n");
-}

package/src/agents/prompt-library/platform.ts

@@ -1,70 +0,0 @@
-import { platformAgents } from "../platform-adapter";
-
-export function buildPlatformManagerPrompt(): string {
-  const ledger = platformAgents["ledger-creator"]?.prompt || "";
-  const bootstrapper = platformAgents["bootstrapper"]?.prompt || "";
-  const initializer = platformAgents["project-initializer"]?.prompt || "";
-  const mindmodel = platformAgents["mindmodel"]?.prompt || "";
-
-  return `
-<Platform_Manager_Identity>
-# Platform Manager
-You are the Unified Platform Manager, responsible for orchestration, session continuity, and project initialization.
-You consolidate the capabilities of the Ledger Creator, Bootstrapper, Project Initializer, and Mindmodel Orchestrator.
-</Platform_Manager_Identity>
-
-<Memory_And_Knowledge_Stewardship>
-## Mode: Memory, RAG, and Task Hygiene
-
-You are the durable project memory steward. Your job is to keep only decision-grade knowledge current, not to dump transcripts.
-
-### MemPalace protocol
-- Start memory work with \`mempalace_status\` when the MemPalace MCP is available.
-- Search before writing: use \`mempalace_search\` or related read tools to avoid duplicates.
-- Write only durable facts: architectural decisions, accepted tradeoffs, project conventions, long-lived TODO ownership, release decisions, and important user preferences.
-- Do not write noise: transient debugging attempts, failed commands without lasting lesson, repeated summaries, raw chat logs, or obvious file diffs.
-- When facts change, invalidate or update old knowledge instead of appending conflicting facts.
-- Prefer AAAK-style concise entries: actor, artifact, action, knowledge, timestamp/context.
-- Use diary entries for session summaries only when they contain decisions or handoff-relevant state.
-
-### RAG protocol
-- Treat the bundled RAG MCP as retrieval-first unless its configured endpoint exposes write/upsert tools.
-- When architecture decisions change, first store the durable decision in MemPalace.
-- If a RAG write/upsert capability is available, sync the same decision-level summary there.
-- If RAG is search-only, report "RAG sync pending/search-only" rather than pretending it was updated.
-
-### TODO and task hygiene
-- Verify active TODO/task lists before closure.
-- Mark completed items as completed; do not leave finished work as pending.
-- Preserve unfinished work with owner, next action, and blocker.
-- Remove or collapse stale duplicate TODOs.
-- Before final response, provide a short ledger: memory updated, RAG updated or pending, TODO state clean or remaining.
-
-### When to run Manager
-- Session start: load current memory and identify stale/important project state.
-- After architecture/design decisions: update MemPalace and, when possible, RAG.
-- Before handoff/final closure: clean TODO state and write a concise memory checkpoint.
-- During long work: periodically consolidate only durable decisions.
-</Memory_And_Knowledge_Stewardship>
-
-<Capability_Ledger>
-## Mode: Session Continuity (Ledger)
-${ledger}
-</Capability_Ledger>
-
-<Capability_Exploration>
-## Mode: Exploration & Brainstorming (Bootstrapper)
-${bootstrapper}
-</Capability_Exploration>
-
-<Capability_Initialization>
-## Mode: Project Initialization
-${initializer}
-</Capability_Initialization>
-
-<Capability_Mindmodel>
-## Mode: Mindmodel Orchestration
-${mindmodel}
-</Capability_Mindmodel>
-`;
-}

package/src/agents/prompt-library/specialized.ts

@@ -1,39 +0,0 @@
-import type { AvailableAgent } from "../dynamic-agent-prompt-types";
-
-export type ResearcherMode = "internal" | "external" | "both";
-
-/**
- * Specialized researcher section builder.
- * The canonical buildResearcherSection lives in dynamic-agent-core-sections.ts;
- * this module exists for specialized/complementary researcher descriptions
- * when mode-specific variants are needed.
- */
-export function buildResearcherSection(
-  agents: AvailableAgent[],
-  mode: ResearcherMode = "both",
-): string {
-  const researcherAgent = agents.find((agent) => agent.name === "researcher");
-  if (!researcherAgent) return "";
-
-  const useWhen = researcherAgent.metadata.useWhen || [];
-
-  if (mode === "internal") {
-    return `### Researcher = Internal Codebase Discovery
-Use it for discovery in this repo.
-${useWhen.map((entry) => `- ${entry}`).join("\n")}`;
-  }
-
-  if (mode === "external") {
-    return `### Researcher = External Docs and OSS Research
-Search official references, API docs, OSS examples, and the web when needed.
-${useWhen.map((entry) => `- "${entry}"`).join("\n")}`;
-  }
-
-  // "both" mode — use the canonical full section from dynamic-agent-core-sections.ts
-  // This function is provided for callers that need mode-specific variants.
-  // For the full researcher description, import buildResearcherSection from
-  // dynamic-agent-core-sections.ts directly.
-  return `### Researcher = Internal + External Research
-Use it for both codebase discovery (internal) and external docs/OSS research.
-${useWhen.map((entry) => `- ${entry}`).join("\n")}`;
-}