/**
 * deep-research-codebase / copilot
 *
 * Copilot replica of the Claude deep-research-codebase workflow. Specialist
 * sub-agents are dispatched as separate headless `ctx.stage()` calls — each
 * binds the SDK's session to a single named agent via `sessionOpts: { agent }`,
 * which is the SDK-native way to spawn a sub-agent on Copilot.
 *
 * Copilot-specific concerns baked in (see references/failure-modes.md):
 *
 *   • F5 — every `ctx.stage()` is a FRESH session. Each specialist receives
 *     everything it needs (research question, scope, scout overview, and —
 *     for layer-2 specialists — verbatim locator output) in its first prompt.
 *
 *   • F1 — Copilot's last assistant turn is often empty when the agent ends
 *     on a tool call. We use `getAssistantText()` (canonical concatenation
 *     of every top-level non-empty assistant turn, ignoring sub-agent
 *     `parentToolCallId` traffic) instead of `.at(-1).data.content`.
 *
 *   • F6 — every prompt explicitly requires trailing prose AFTER any tool
 *     call so `getAssistantText()` and downstream `transcript()` reads are
 *     never empty.
 *
 *   • F9 — `s.save()` receives `SessionEvent[]` from `s.session.getMessages()`.
 *
 * See claude/index.ts for the full design rationale and topology diagram.
 */
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