/**
 * deep-research-codebase / opencode
 *
 * OpenCode 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
 * OpenCode's `task` tool. The default agent must have `task: "allow"` in
 * its permission ruleset (see `.opencode/agents/worker.md` for the
 * canonical example).
 *
 * See claude/index.ts for the full design rationale and topology diagram.
 *
 * OpenCode-specific concerns baked in (see references/failure-modes.md):
 *
 *   • F3 — `result.data!.parts` is heterogenous. Batch sessions don't read
 *     `extractResponseText` for orchestrator output (sub-agents write to
 *     disk; the orchestrator reply is just a short tally), but the history
 *     pipeline still uses it.
 *
 *   • F5 — every `ctx.stage()` is a FRESH session. Batch session prompts
 *     embed everything the orchestrator needs 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 the unwrapped `{ info, parts }` payload from
 *     `result.data!`.
 */
declare const _default: import("../../../index.ts").WorkflowDefinition<"opencode", readonly [{
    readonly name: "prompt";
    readonly type: "text";
    readonly required: true;
    readonly description: "research question";
}]>;
export default _default;
//# sourceMappingURL=index.d.ts.map