/**
 * deep-research-codebase / copilot
 *
 * Copilot replica of the Claude deep-research-codebase workflow with the
 * same **batched** Task-tool fan-out. Specialist sub-agents run inside batch
 * sessions: each batch is a single `ctx.stage()` whose orchestrator turn
 * dispatches up to MAX_TASKS_PER_BATCH (≈10) specialists in parallel via
 * Copilot's `agent` tool (alias `Task`, see Copilot subagents docs).
 * Research-history specialists remain as their own sequential sub-pipeline.
 *
 * See claude/index.ts for the full design rationale and topology diagram.
 *
 * Copilot-specific concerns baked in (see references/failure-modes.md):
 *
 *   • F1 — Copilot's last assistant turn is often empty when the agent ends
 *     on a tool call. Batch sessions don't read `getAssistantText` for the
 *     orchestrator output (sub-agents write to disk; the orchestrator's text
 *     reply is just a short tally), so this is no longer load-bearing for
 *     Stage 2 — but the history pipeline still depends on it.
 *
 *   • F5 — every `ctx.stage()` is a FRESH session. Batch session prompts
 *     embed everything the orchestrator needs (per-task subagent_type,
 *     output path, and verbatim specialist prompt) in the first turn.
 *
 *   • F6 — orchestrator prompt requires a single-line tally as the trailing
 *     turn so transcripts are never empty.
 *
 *   • F9 — `s.save()` receives `SessionEvent[]` from `s.session.getMessages()`.
 */
declare const _default: import("../../../index.ts").WorkflowDefinition<"copilot", readonly [{
    readonly name: "prompt";
    readonly type: "text";
    readonly required: true;
    readonly description: "research question";
}]>;
export default _default;
//# sourceMappingURL=index.d.ts.map