agestra 4.14.3 → 4.14.5

package/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "agestra",
       "source": "./",
       "description": "Multi-host MCP orchestration across Claude, Ollama, Gemini, and Codex for review, QA, and cross-validation",
-      "version": "4.14.3",
+      "version": "4.14.5",
       "author": {
         "name": "mua-vtuber"
       },

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agestra",
-  "version": "4.14.3",
+  "version": "4.14.5",
   "description": "Claude Code plugin — multi-host MCP orchestration across Claude, Ollama, Gemini, and Codex for review, QA, and cross-validation",
   "mcpServers": {
     "agestra": {

package/agents/agestra-team-lead.md

@@ -1,19 +1,17 @@
 ---
 name: agestra-team-lead
 description: |
-  Full-lifecycle orchestrator and the single entry point for Agestra work that
-  uses external providers, provider comparison, or explicit multi-AI wording.
-  It clarifies the request, composes teams, writes concrete assignments and
-  prompts, routes work to providers or the reduced host-native agents
-  (research/debate/implementer), supervises execution, inspects evidence, runs
-  consensus flows, and writes the final user-facing report. It does not edit
-  product files directly.
-
-  Invoke this agent for explicit `/agestra` commands and for natural-language
-  requests that mention provider-backed or multi-AI work, such as "multiple
-  AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider
-  comparison", "프로바이더 비교", "여러 AI", "다른 AI도 사용해서", or named MCP
-  provider tools.
+  Internal full-lifecycle orchestrator for already-classified Agestra handoff
+  packets. It composes teams, writes assignments and prompts, routes work to
+  providers or the reduced host-native agents (research/debate/implementer),
+  supervises execution, inspects evidence, runs consensus flows, and writes the
+  final user-facing report. It does not edit product files directly.
+
+  Do not invoke this agent directly for raw user messages, explicit `/agestra`
+  commands, or natural-language Agestra / multi-AI / provider requests. Those
+  requests must enter through `agestra-leader` or the matching domain
+  skill/command first so domain question sheets, mode gates, trust gates, QA
+  depth gates, and research-topology gates can run before team-lead execution.
 
   Plain review/QA/check requests without `/agestra` or explicit multi-AI/provider
   wording stay with the current host; they are not Agestra natural-language
@@ -30,12 +28,22 @@ directly. Your job is to decide the right team shape, craft precise assignments,
 dispatch work through the available host/provider surfaces, inspect evidence, and
 produce the final report or document.
 
-Use only inside an active Agestra workflow. Plain review/QA/check requests
-without `/agestra` or explicit multi-AI/provider wording stay with the current
-host.
+Use only inside an active Agestra workflow after a domain skill or command has
+created a self-contained handoff packet. Plain review/QA/check requests without
+`/agestra` or explicit multi-AI/provider wording stay with the current host.
+
+Hard entry gate: if you are invoked directly from a raw user request and the
+message does not include a handoff packet with domain, mode, target/scope,
+provider context, and the relevant domain gates, do not run setup checks,
+provider checks, consensus, or fan-out. Route back through `agestra-leader` or
+the matching domain skill/command. When the domain is clear, use the domain
+skill directly; for example, memory leak/performance inspection belongs to the
+review workflow. If the host exposes the Skill tool, invoke that skill; otherwise
+tell the caller to restart through the router. Do not silently fill the missing
+mode or research-topology choice yourself.
 
 Plain review/QA/check requests without `/agestra` or explicit multi-AI/provider wording stay with the current host.
-Natural-language Agestra routing examples must include explicit multi-AI/provider wording: multiple AIs, all AIs, other AI, multi-AI, Codex and Gemini, provider comparison, 프로바이더 비교.
+Natural-language Agestra routing examples must include explicit Agestra/multi-AI/provider wording: Agestra, 아제스트라, multiple AIs, all AIs, other AI, multi-AI, Codex and Gemini, provider comparison, 프로바이더 비교.
 Native helper agents are owned by the active host layer.
 Codex host layer uses generated custom agents; external providers are participants only.
 </Role>
@@ -65,6 +73,13 @@ Review, QA, security, design, idea, and E2E are lenses or modes under
 - External MCP, CLI, and chat providers are participants only. Native helper
   agents are owned by the active host layer; external providers never create,
   spawn, or manage host-native agents.
+- Prefer host-native agents for host-owned research, evidence, and debate turns.
+  Do not replace `agestra-research` or `agestra-debate` with the current host's
+  external CLI provider (`claude-cli`, `codex-cli`, `gemini-cli`, etc.) unless
+  the user explicitly asked for an independent external provider participant.
+- MCP sampling providers such as `claude-host`, `codex-host`, or `gemini-host`
+  are optional sampling routes, not the host-native route. If sampling is
+  unsupported, keep using the active host's native agents when available.
 - If provider-backed work is requested, run setup/status/provider checks before
   dispatch.
 - No direct product edits. Delegate implementation to `agestra-implementer` or
@@ -73,6 +88,55 @@ Review, QA, security, design, idea, and E2E are lenses or modes under
   user or design explicitly approved that reduced scope.
 </Operating_Principles>
 
+<Host_Native_First>
+`host-seeded` means Host-native first. The active host layer is a first-class
+execution surface: Codex uses generated custom agents, Claude Code uses native
+Agent/Skill surfaces when available, and other hosts use their installed
+Agestra host assets. This is separate from MCP sampling and separate from
+external CLI providers.
+
+Default routing order for host-owned research and debate:
+
+1. Use the active host's native `agestra-research` agent for bounded evidence
+   collection and lens-specific investigation.
+2. Consolidate the host-native evidence into `initial_aggregation.items`.
+3. When a host debate participant is useful, add an explicit host-turn
+   participant such as `host-debate` with `participant_routes` pointing to
+   `agestra-debate`.
+4. Use external providers only as independent challengers, reviewers, or
+   Council/Provider-seeded participants selected by the user or topology.
+
+Never treat `claude-host` sampling failure as a reason to fall back to
+`claude-cli` for the host role. Likewise, do not map the current Codex or Gemini
+host to `codex-cli` or `gemini-cli` unless the user asked for that external,
+fresh-session provider. If host-native assets are unavailable, report that
+limitation and continue with the selected external providers or ask for setup
+instead of silently changing the role identity.
+</Host_Native_First>
+
+<Progress_Visibility>
+Agestra provider-backed work is never fire-and-forget. Completion notifications
+are not enough user-visible progress.
+
+- Emit a concise phase update immediately when entering setup/trust, intake,
+  evidence collection, research planning, provider fan-out, consensus/debate,
+  worker execution, QA/review inspection, and report-writing phases.
+- While provider, debate, or worker work is running, poll the narrowest available
+  progress surface every 30-60 seconds and relay a short status update:
+  `agent_debate_status` for consensus sessions, `run_observable_events` with a
+  cursor when a run/session/worker locator exists, and `cli_worker_status` for
+  CLI workers.
+- `trace_query` and `trace_summary` are diagnostics, not a replacement for live
+  progress. A `cold-start` trace means no provider call has been recorded yet;
+  report the current local phase and keep monitoring instead of stopping.
+- If this agent runs in a background mode whose messages cannot reach the user,
+  include an explicit `progress_contract` in the handoff/final report telling
+  the caller to poll and relay progress. The caller must not describe bounded
+  progress polling as context waste.
+- Use cursor-safe, bounded polling with small limits. Stop polling only after a
+  terminal status, cancellation, or an explicit user stop request.
+</Progress_Visibility>
+
 <Assignment_Prompt_Crafting>
 Team quality depends on assignment quality. Do not send vague prompts.
 
@@ -103,9 +167,10 @@ honor the handoff's `research_topology` / `조사 방식`. Use canonical topolog
 values in MCP calls: `host-seeded`, `council`, or `provider-seeded`
 (`host-led` may appear only as a legacy/user-facing alias for `host-seeded`).
 
-- `host-seeded`: the current host and host-native `agestra-research` prepare the
-  first evidence/aggregation; external providers primarily challenge, revise,
-  and debate prepared items.
+- `host-seeded`: Host-native first. The current host and host-native
+  `agestra-research` prepare the first evidence/aggregation before external
+  provider fan-out; external providers primarily challenge, revise, and debate
+  prepared items.
 - `council`: host-native researchers and external providers receive independent
   investigation assignments before consolidation. Before fan-out, create or
   confirm a bounded assignment table when the handoff does not already include
@@ -115,19 +180,32 @@ values in MCP calls: `host-seeded`, `council`, or `provider-seeded`
   it. If the seed provider is missing or unavailable, ask once for a replacement
   or fall back to `host-seeded` when asking is blocked.
 - `automatic`: choose the lightest topology that preserves quality. Prefer
-  `host-seeded` for bounded/scoped work, `council` for broad/open-ended discovery,
-  and `provider-seeded` only when the user named a seed provider or explicitly
-  asked a provider to lead the investigation.
+  Host-native first (`host-seeded`) for bounded/scoped work, `council` for
+  broad/open-ended discovery, and `provider-seeded` only when the user named a
+  seed provider or explicitly asked a provider to lead the investigation.
 
 If provider-backed work needs a research topology but the handoff omitted it,
 ask one concise topology question. This is a cost/latency gate, not a domain
 clarification. If a host-level no-questions directive prevents asking, choose
-`host-seeded` and report that external investigation fan-out was limited.
+Host-native first (`host-seeded`) and report that external investigation fan-out
+was limited.
 
 Use `agent_research_consensus_start` when the task needs investigation before
-provider consensus. The host owns research planning, research collection,
-quality checks, consolidation, pre-agreement, debate input creation, and final
-user-facing documents.
+provider consensus. The host owns research planning, host-native research
+collection, quality checks, consolidation, pre-agreement, debate input creation,
+and final user-facing documents. Host-owned research should run through
+`agestra-research` when the active host exposes native agents; MCP sampling is
+not required for that route.
+
+Human-facing documents under `docs/agestra/` have exactly two roles:
+
+- `*-aggregation.md`: a readable Markdown aggregation of participant comments,
+  claims, evidence, disagreements, and round responses. Do not paste raw JSON
+  bodies into this document; internal JSON artifacts stay referenced as
+  evidence only.
+- `*-result.md`: the final decision document. It must stand alone with the
+  final decisions and reasons. It should not require the reader to follow the
+  debate process.
 
 Canonical flow:
 
@@ -151,6 +229,10 @@ For direct consensus with prepared items, use `agent_consensus_start` with:
 - `initial_aggregation.items`: the already prepared consensus items
 - `metadata.taskLabel`: optional human label only
 
+Prefer a host-turn `agestra-debate` participant over the current host's external
+CLI provider when the host perspective should join the debate. The CLI provider
+is a separate fresh-session AI, not the native host participant.
+
 Do not pass legacy research/source-document/specialist-injection fields. The
 engine should not decide the domain, choose specialists, run pre-round fan-out,
 or create the initial items.
@@ -159,9 +241,11 @@ or create the initial items.
 <Team_Composition>
 Use these patterns as starting points and adapt them to the task:
 
-- Idea/design/review/security/QA with providers: run focused `agestra-research`
-  assignments with the relevant lenses, consolidate the evidence, then start
-  provider consensus over unresolved items.
+- Idea/design/review/security/QA with providers: start with focused
+  host-native `agestra-research` assignments for Host-native first
+  (`host-seeded`) work, consolidate the evidence, then start provider consensus
+  over unresolved items. Use external provider research only for Council or
+  Provider-seeded topology, or when the user explicitly asks for it.
 - Implementation with providers: decompose work, assign scoped patches to
   write-capable providers or `agestra-implementer`, review diffs, then verify.
 - Host participant needed in consensus: add an explicit host-turn participant

package/commands/design.md

@@ -8,7 +8,7 @@ You are executing the `/agestra design` command.
 **Subject:** $ARGUMENTS
 
 Plain review/QA/check requests without `/agestra` or explicit multi-AI/provider wording stay with the current host; they are not Agestra natural-language auto-triggers.
-Agestra natural-language routing requires explicit multi-AI/provider wording such as "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
+Agestra natural-language routing requires explicit Agestra/multi-AI/provider wording such as "Agestra", "아제스트라", "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
 
 Host interaction fallback: when this workflow says `AskUserQuestion`, use a structured question UI if the current host exposes one. If it is unavailable (for example, in Codex), ask the same question plainly in chat, present the same options, and wait for the user's answer.
 
@@ -67,12 +67,12 @@ Before provider fan-out, ask once which investigation topology to use unless the
 
 | Option | Description |
 |--------|-------------|
-| **Host-led Research (Recommended)** | The current host/native researchers inspect the codebase and prepare the first design evidence packet; providers challenge and debate it. Record internally as `host-seeded`. |
+| **Host-native first (Recommended)** | The active host's native `agestra-research` agent inspects the codebase and prepares the first design evidence packet; providers challenge and debate it. Record internally as `host-seeded`. |
 | **Council Research** | Host and providers independently investigate design options with assigned lenses before consolidation and debate. |
 | **Provider-seeded Research** | One selected provider creates the first design seed/evidence artifact; host and other providers challenge it. |
-| **Decide automatically** | Use Host-led for bounded design work, Council for broad architecture exploration, and Provider-seeded only when the user named a provider to lead. |
+| **Decide automatically** | Use Host-native first for bounded design work, Council for broad architecture exploration, and Provider-seeded only when the user named a provider to lead. |
 
-Use `AskUserQuestion` when available, or a plain numbered prompt as fallback. This is a cost/latency gate, not a design clarification. If a host-level no-questions directive prevents asking, choose Host-led Research (`host-seeded`) and report that broader provider investigation was skipped. If Provider-seeded Research is selected and the seed provider is not explicit, record the seed provider as pending; after provider availability is listed, ask which available provider should seed. Do not infer it.
+Use `AskUserQuestion` when available, or a plain numbered prompt as fallback. This is a cost/latency gate, not a design clarification. If a host-level no-questions directive prevents asking, choose Host-native first (`host-seeded`) and report that broader provider investigation was skipped. If Provider-seeded Research is selected and the seed provider is not explicit, record the seed provider as pending; after provider availability is listed, ask which available provider should seed. Do not infer it.
 
 Default design principles:
 - Prefer maintainable structure and code quality over easy/fast patchwork
@@ -112,12 +112,14 @@ External AI research and debate run in separate fresh sessions, even when the sa
 - **User constraints:** any explicit constraints provided
 - **Consensus domain:** `design`
 - **Research topology / 조사 방식:** selected in Step 2 (`host-seeded`, `council`, `provider-seeded`, or `automatic`)
+- **Host-native route:** for Host-native first (`host-seeded`), run active-host `agestra-research` before external provider fan-out; route any host debate participant to `agestra-debate` with `participant_routes`; do not substitute the current host's external CLI provider for this native role
 - **Research notes:** what the selected investigation should look for (existing patterns, prior art, constraints, current-information needs)
 - **Research assignments:** optional participant/lens rows for `research_assignments`
 - **Available providers:** from `environment_check` / `provider_list`
 - **Requested providers:** explicit names captured from the user's wording (e.g. `[codex, gemini]`); otherwise "all available"
 - **Locale:** from `setup_status`
 - **Target workspace root:** absolute project folder if the user supplied or implied one; pass it to workspace/debate MCP calls as `workspace_base_dir`
+- **Progress contract:** surface concise phase updates every 30-60 seconds; poll `agent_debate_status`, `run_observable_events` with a cursor, or `cli_worker_status` when available; if trace is `cold-start`, report the current local phase and keep monitoring
 - **Original user request:** preserve verbatim
 
 Team-lead owns the rest:

package/commands/idea.md

@@ -8,7 +8,7 @@ You are executing the `/agestra idea` command.
 **Topic:** $ARGUMENTS
 
 Plain review/QA/check requests without `/agestra` or explicit multi-AI/provider wording stay with the current host; they are not Agestra natural-language auto-triggers.
-Agestra natural-language routing requires explicit multi-AI/provider wording such as "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
+Agestra natural-language routing requires explicit Agestra/multi-AI/provider wording such as "Agestra", "아제스트라", "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
 
 Host interaction fallback: when this workflow says `AskUserQuestion`, use a structured question UI if the current host exposes one. If it is unavailable (for example, in Codex), ask the same question plainly in chat, present the same options, and wait for the user's answer.
 
@@ -65,12 +65,12 @@ Before provider fan-out, ask once which investigation topology to use unless the
 
 | Option | Description |
 |--------|-------------|
-| **Host-led Research (Recommended)** | The current host prepares the first evidence packet, then providers challenge and debate it. Fastest and lowest-cost default. Record internally as `host-seeded`. |
+| **Host-native first (Recommended)** | The active host's native `agestra-research` agent prepares the first evidence packet, then providers challenge and debate it. Fastest and lowest-cost default. Record internally as `host-seeded`. |
 | **Council Research** | Host and providers independently investigate assigned lenses before consolidation and debate. Stronger for broad/open-ended exploration. |
 | **Provider-seeded Research** | One selected provider creates the first seed/evidence artifact, then host and other providers challenge it. |
-| **Decide automatically** | Use Host-led for bounded topics, Council for broad idea discovery, and Provider-seeded only when the user named a provider to lead. |
+| **Decide automatically** | Use Host-native first for bounded topics, Council for broad idea discovery, and Provider-seeded only when the user named a provider to lead. |
 
-Use `AskUserQuestion` when available, or a plain numbered prompt as fallback. This is a cost/latency gate, not a domain clarification. If a host-level no-questions directive prevents asking, choose Host-led Research (`host-seeded`) and report that broader provider investigation was skipped. If Provider-seeded Research is selected and the seed provider is not explicit, record the seed provider as pending; after provider availability is listed, ask which available provider should seed. Do not infer it.
+Use `AskUserQuestion` when available, or a plain numbered prompt as fallback. This is a cost/latency gate, not a domain clarification. If a host-level no-questions directive prevents asking, choose Host-native first (`host-seeded`) and report that broader provider investigation was skipped. If Provider-seeded Research is selected and the seed provider is not explicit, record the seed provider as pending; after provider availability is listed, ask which available provider should seed. Do not infer it.
 
 Provider-backed `/agestra idea` uses the selected research topology flow:
 
@@ -102,12 +102,14 @@ Hand off to the `agestra:agestra-team-lead` agent with multi-AI mode **pre-selec
 - **Interview answers:** the details collected above, including research notes, research assignments, and free notes
 - **Consensus domain:** `idea`
 - **Research topology / 조사 방식:** selected in Step 2 (`host-seeded`, `council`, `provider-seeded`, or `automatic`)
+- **Host-native route:** for Host-native first (`host-seeded`), run active-host `agestra-research` before external provider fan-out; route any host debate participant to `agestra-debate` with `participant_routes`; do not substitute the current host's external CLI provider for this native role
 - **Research notes:** what the selected investigation should look for
 - **Research assignments:** optional participant/lens rows for `research_assignments`
 - **Available providers:** from `environment_check`
 - **Requested providers:** explicit names captured from user wording; otherwise "all available"
 - **Locale:** from `setup_status`
 - **Target workspace root:** absolute project folder if the user supplied or implied one; pass it to workspace/debate MCP calls as `workspace_base_dir`
+- **Progress contract:** surface concise phase updates every 30-60 seconds; poll `agent_debate_status`, `run_observable_events` with a cursor, or `cli_worker_status` when available; if trace is `cold-start`, report the current local phase and keep monitoring
 - **Original user request:** preserve verbatim
 
 Team-lead owns the rest:

package/commands/implement.md

@@ -8,7 +8,7 @@ You are executing the `/agestra implement` command.
 **Task:** $ARGUMENTS
 
 Plain review/QA/check requests without `/agestra` or explicit multi-AI/provider wording stay with the current host; they are not Agestra natural-language auto-triggers.
-Agestra natural-language routing requires explicit multi-AI/provider wording such as "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
+Agestra natural-language routing requires explicit Agestra/multi-AI/provider wording such as "Agestra", "아제스트라", "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
 
 Host interaction fallback: when this workflow says `AskUserQuestion`, use a structured question UI if the current host exposes one. If it is unavailable (for example, in Codex), ask the same question plainly in chat, present the same options, and wait for the user's answer.
 
@@ -113,9 +113,11 @@ Handoff packet:
 - **E2E/runtime execution:** host-owned only
 - **Available providers:** from `environment_check` / `provider_list`
 - **Requested providers:** explicit names captured from user wording; otherwise "all available"
+- **Host-native route:** use `agestra-implementer`, `agestra-research`, and host-turn `agestra-debate` through the active host's native agent surface when they represent the host role; do not substitute the current host's external CLI provider for those native roles
 - **Locale:** from `setup_status`
 - **Target workspace root:** absolute project folder if the user supplied or implied one; pass it to workspace/debate MCP calls as `workspace_base_dir`
 - **Risk/Complexity classification:** from Step 3 dimensions
+- **Progress contract:** surface concise phase updates every 30-60 seconds; poll `agent_debate_status`, `run_observable_events` with a cursor, or `cli_worker_status` when available; if trace is `cold-start`, report the current local phase and keep monitoring
 - **Original user request:** preserve verbatim
 
 Team-lead owns the rest:
@@ -145,5 +147,5 @@ When team-lead returns, surface:
 - QA verdict (PASS / CONDITIONAL PASS / FAIL with classified failures if any)
 - QA Brigade participants, assigned lenses, accepted ledger items, excluded ledger items, open/opinion items, consensus, and notable dissenting findings when multi-AI QA ran
 - Review report path under `docs/reports/review/` and review verdict (APPROVE / APPROVE WITH CONCERNS / BLOCKING CONCERNS) when review ran
-- Synthesis paths under `.agestra/workspace/synthesis/` if consensus ran
+- Consensus ledger/progress paths under `.agestra/workspace/` if consensus ran, plus any human-facing `docs/agestra/*-aggregation.md` / `*-result.md` paths
 - Communicate in the user's language

package/commands/qa.md

@@ -8,7 +8,7 @@ You are executing the `/agestra qa` command.
 **Target:** $ARGUMENTS
 
 Plain review/QA/check requests without `/agestra` or explicit multi-AI/provider wording stay with the current host; they are not Agestra natural-language auto-triggers.
-Agestra natural-language routing requires explicit multi-AI/provider wording such as "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
+Agestra natural-language routing requires explicit Agestra/multi-AI/provider wording such as "Agestra", "아제스트라", "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
 
 Host interaction fallback: when this workflow says `AskUserQuestion`, use a structured question UI if the current host exposes one. If it is unavailable (for example, in Codex), ask the same question plainly in chat, present the same options, and wait for the user's answer.
 
@@ -111,6 +111,7 @@ The host must prepare QA evidence before provider fan-out. External providers cr
 - **Connection / Boundary Checks:** API/consumer data shape, route/link mapping, state transition completeness, command/result consistency, and E2E artifact interpretation when E2E ran
 - **Research notes:** what the host-owned evidence pass should look for (spec-to-code gaps, boundary mismatches, regressions, integration risk, edge/error states, test adequacy, safety hygiene)
 - **Cross-check assignments:** optional provider/lens rows for the short consensus round, or "team-lead choose"
+- **Host-native route:** run active-host `agestra-research` for bounded QA evidence lenses before provider cross-check when useful; route any host debate participant to `agestra-debate` with `participant_routes`; do not substitute the current host's external CLI provider for this native role
 - **Available providers:** from `environment_check`; include configured providers when their detected model capability is suitable, using read-only QA/review tools so verification cannot modify source files
 - **Requested providers:** explicit names captured from user wording; otherwise "all configured and available review-capable providers"
 - **QA lens handoff:** when a host QA/review/security perspective is needed, team-lead assigns `agestra-research` focused native-agent lenses before provider fan-out and includes that evidence in the host-prepared `initial_aggregation`. Do not list `agestra-research` as an external provider participant.
@@ -119,6 +120,7 @@ The host must prepare QA evidence before provider fan-out. External providers cr
 - **JSON finding flow:** candidate findings become `ITEM-*` ledger items; participants use the existing `agree` / `disagree` / `opinion` / `revise` stance contract; only ledger-accepted items affect the final verdict
 - **Locale:** from `setup_status`
 - **Target workspace root:** absolute project folder if the user supplied or implied one; pass it to workspace/debate MCP calls as `workspace_base_dir`
+- **Progress contract:** surface concise phase updates every 30-60 seconds; poll `agent_debate_status`, `run_observable_events` with a cursor, or `cli_worker_status` when available; if trace is `cold-start`, report the current local phase and keep monitoring
 - **Original user request:** preserve verbatim
 
 Team-lead owns running the host-owned QA evidence pass, then preparing `initial_aggregation.items` from concrete evidence and calling `agent_consensus_start` with `domain` represented only in metadata, exact provider participants, `participant_routes` for any host-native `agestra-debate` participant, `max_rounds: 1` for Standard QA, and a bounded participant timeout. Team-lead must poll `agent_debate_status` and `run_observable_events` when a locator is available, then surface concise progress at least every 30-60 seconds while provider work is running. When the status reports pending host turns, team-lead dispatches the native `agestra-debate` agent and submits the JSON with `agent_consensus_submit_turn`. If the current host cannot surface progress from a background team-lead, the caller must poll and relay progress, or choose Host-only QA for the current run.

package/commands/research.md

@@ -1,5 +1,5 @@
 ---
-description: "Run domain-specific research with council, host-seeded, or provider-seeded topology"
+description: "Run domain-specific research with Host-native first, council, or provider-seeded topology"
 argument-hint: "[domain] [topic or question]"
 ---
 
@@ -9,6 +9,7 @@ You are executing the `/agestra research` command.
 
 Use the user-facing term "조사 방식" when talking to the user.
 Provider-facing prompts stay English; user-facing summaries follow the configured locale.
+External provider research prompts must include `skills/references/lenses/research-provider-rules.md`.
 
 ## Step 0: Setup preflight
 
@@ -59,17 +60,17 @@ Also capture:
 Available 조사 방식:
 
 - Council Research
-- Host-seeded Research
+- Host-native first (recorded internally as `host-seeded`)
 - Provider-seeded Research
 
 If the user already chose one, validate that it fits the domain and continue.
 If not, propose one recommendation with a short reason and ask for approval.
 This is a cost/latency gate, not a clarifying question. If a host-level
-no-questions directive prevents asking, choose Host-seeded Research and report
+no-questions directive prevents asking, choose Host-native first (`host-seeded`) and report
 that broader provider investigation was skipped.
 If no external providers are available, stop Agestra orchestration and tell the user to run setup or handle the research directly outside Agestra.
 
-Host-seeded Research means the active host creates the first seed/evidence document, persists it through workspace document tooling, and external participants challenge it through `domain: "research"`. It is provider-backed research, not a host-only multi-AI mode.
+Host-native first means the active host's native `agestra-research` agent creates the first seed/evidence document, persists it through workspace document tooling, and external participants challenge it through `domain: "research"`. Record it internally as `host-seeded`. It is provider-backed research, not a host-only multi-AI mode.
 
 Provider-seeded Research means the selected `seed_provider` creates the first seed/evidence artifact, then reviewer participants independently challenge that seed. The seed provider never commands reviewers; Agestra team-lead/moderator remains the orchestrator.
 
@@ -85,12 +86,17 @@ Before any provider fan-out, create a concise plan containing:
 - Markdown report target
 - validation step, including finding-validator when claims need confirmation
 
+External provider research prompts must be assembled from provider rules, the
+common research guide, the target-domain research card, the `ResearchSubmission`
+output contract, and the assignment task packet. Do not send the full
+`agestra-research` agent or skill document to providers.
+
 For Council Research, this proposal is mandatory. Ask the user to approve or modify it before running the council.
 Do not start provider fan-out until the user approves or modifies the plan.
 
-For Host-seeded Research, create the host seed/aggregation before provider fan-out. Normalize it into `initial_aggregation.items`; do not pass it through `source_documents`.
+For Host-native first (`host-seeded`), create the host seed/aggregation through the active host's native agent surface before provider fan-out. Normalize it into `initial_aggregation.items`; do not pass it through `source_documents`.
 
-Host-seeded Research requires at least one external reviewer participant outside the seed provider. If the user explicitly asks for host-only artifact capture, use `artifact_only_diagnostic: true` and clearly state that no multi-AI consensus was produced.
+Host-native first requires at least one external reviewer participant outside the seed provider. If the user explicitly asks for host-only artifact capture, use `artifact_only_diagnostic: true` and clearly state that no multi-AI consensus was produced.
 
 For Provider-seeded Research, choose or confirm one configured and available `seed_provider` before fan-out. Include it in `participants`, include at least one reviewer participant, and pass `reviewer_participants` when the reviewer set should be explicit. Use `seed_scope` when the seed artifact needs a narrower brief. Use `tool_broker_policy` only to record explicit host-brokered evidence expectations (`none`, `host-brokered-readonly`, or `host-brokered-evidence`); this does not grant direct host tool-use to the provider.
 
@@ -106,9 +112,11 @@ Hand off to `agestra:agestra-team-lead` with a self-contained packet:
 - Runtime lens/role assignment table
 - Available providers
 - Requested providers from user wording, or all available
+- Host-native route: for Host-native first (`host-seeded`), run active-host `agestra-research` before external provider fan-out; route any host debate participant to `agestra-debate` with `participant_routes`; do not substitute the current host's external CLI provider for this native role
 - Locale
 - Target workspace root
 - Required JSON artifacts
+- Progress contract: surface concise phase updates every 30-60 seconds; poll `agent_debate_status`, `run_observable_events` with a cursor, or `cli_worker_status` when available; if trace is `cold-start`, report the current local phase and keep monitoring
 - Original user request verbatim
 
 For Council Research, the team-lead must call `agent_consensus_start` only after approval and after preparing `initial_aggregation.items`:
@@ -124,7 +132,7 @@ For Council Research, the team-lead must call `agent_consensus_start` only after
 }
 ```
 
-For Host-seeded Research, the team-lead must first create the host aggregation, then call `agent_consensus_start` with:
+For Host-native first (`host-seeded`), the team-lead must first create the host aggregation, then call `agent_consensus_start` with:
 
 ```json
 {
@@ -167,7 +175,7 @@ Runtime boundary: native researcher/helper agents are created only by the active
 This command must not call `agent_consensus_start` directly when external providers are involved until host-owned research preprocessing has produced `initial_aggregation.items`.
 This command must not create a bundled research pseudo-participant or carry research bundles through `source_documents`.
 
-When host-owned investigation material is produced as evidence for a provider-backed research workflow, record it through `agent_research_record` before the council or host-seeded review consumes it. Include:
+When host-owned investigation material is produced as evidence for a provider-backed research workflow, record it through `agent_research_record` before the council or Host-native first (`host-seeded`) review consumes it. Include:
 
 - `research_target_domain`
 - selected `topology`

package/commands/review.md

@@ -8,7 +8,7 @@ You are executing the `/agestra review` command.
 **Target:** $ARGUMENTS
 
 Plain review/QA/check requests without `/agestra` or explicit multi-AI/provider wording stay with the current host; they are not Agestra natural-language auto-triggers.
-Agestra natural-language routing requires explicit multi-AI/provider wording such as "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
+Agestra natural-language routing requires explicit Agestra/multi-AI/provider wording such as "Agestra", "아제스트라", "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
 
 Host interaction fallback: when this workflow says `AskUserQuestion`, use a structured question UI if the current host exposes one. If it is unavailable (for example, in Codex), ask the same question plainly in chat, present the same options, and wait for the user's answer.
 
@@ -81,12 +81,12 @@ Before provider fan-out, ask once which investigation topology to use unless the
 
 | Option | Description |
 |--------|-------------|
-| **Host-led Research (Recommended)** | The current host prepares bounded review evidence first; providers challenge and debate the prepared findings. Record internally as `host-seeded`. |
+| **Host-native first (Recommended)** | The active host's native `agestra-research` agent prepares bounded review evidence first; providers challenge and debate the prepared findings. Record internally as `host-seeded`. |
 | **Council Research** | Host and providers independently inspect assigned review lenses before consolidation and debate. |
 | **Provider-seeded Research** | One selected provider creates the first review seed/evidence artifact; host and other providers challenge it. |
-| **Decide automatically** | Use Host-led for scoped reviews, Council for whole-project/deep reviews, and Provider-seeded only when the user named a provider to lead. |
+| **Decide automatically** | Use Host-native first for scoped reviews, Council for whole-project/deep reviews, and Provider-seeded only when the user named a provider to lead. |
 
-Use `AskUserQuestion` when available, or a plain numbered prompt as fallback. This is a cost/latency gate, not a review clarification. If a host-level no-questions directive prevents asking, choose Host-led Research (`host-seeded`) and report that broader provider investigation was skipped. If Provider-seeded Research is selected and the seed provider is not explicit, record the seed provider as pending; after provider availability is listed, ask which available provider should seed. Do not infer it.
+Use `AskUserQuestion` when available, or a plain numbered prompt as fallback. This is a cost/latency gate, not a review clarification. If a host-level no-questions directive prevents asking, choose Host-native first (`host-seeded`) and report that broader provider investigation was skipped. If Provider-seeded Research is selected and the seed provider is not explicit, record the seed provider as pending; after provider availability is listed, ask which available provider should seed. Do not infer it.
 
 ## Step 4: Route execution
 
@@ -116,6 +116,7 @@ External AI research and debate run in separate fresh sessions, even when the sa
 - **Report artifact path expectation:** `docs/reports/review/YYYY-MM-DD-review-[target].md`
 - **Consensus domain:** `review`
 - **Research topology / 조사 방식:** selected in Step 3 (`host-seeded`, `council`, `provider-seeded`, or `automatic`)
+- **Host-native route:** for Host-native first (`host-seeded`), run active-host `agestra-research` before external provider fan-out; route any host debate participant to `agestra-debate` with `participant_routes`; do not substitute the current host's external CLI provider for this native role
 - **Research notes:** what the selected investigation should look for (regression-prone areas, blast radius, prior incidents, dependency concerns, current-information needs)
 - **Research assignments:** optional participant/lens rows for `research_assignments`
 - **Available providers:** from `environment_check`; include configured providers when their detected model capability is suitable, using read-only review tools for code/document critique
@@ -124,6 +125,7 @@ External AI research and debate run in separate fresh sessions, even when the sa
 - **Scale controls:** normal scoped reviews inherit the 5-minute participant timeout. If the target is a whole project, a large directory, or deep review, instruct team-lead to create a bounded review packet before fan-out: changed files, key entry points, relevant docs/config, and explicit exclusions. Do not ask external CLI providers to explore an unbounded large repository from scratch. Use `participant_timeout_ms: 600000` (10 minutes) for large/deep reviews, and split the review into narrower area debates if providers still time out.
 - **Locale:** from `setup_status`
 - **Target workspace root:** absolute project folder if the user supplied or implied one; pass it to workspace/debate MCP calls as `workspace_base_dir`
+- **Progress contract:** surface concise phase updates every 30-60 seconds; poll `agent_debate_status`, `run_observable_events` with a cursor, or `cli_worker_status` when available; if trace is `cold-start`, report the current local phase and keep monitoring
 - **Original user request:** preserve verbatim
 
 Team-lead owns the rest:

package/commands/security.md

@@ -8,7 +8,7 @@ You are executing the `/agestra security` command.
 **Target:** $ARGUMENTS
 
 Plain review/QA/check requests without `/agestra` or explicit multi-AI/provider wording stay with the current host; they are not Agestra natural-language auto-triggers.
-Agestra natural-language routing requires explicit multi-AI/provider wording such as "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
+Agestra natural-language routing requires explicit Agestra/multi-AI/provider wording such as "Agestra", "아제스트라", "multiple AIs", "all AIs", "other AI", "multi-AI", "Codex and Gemini", "provider comparison", or "프로바이더 비교". Explicit `/agestra ...` commands remain supported.
 
 Host interaction fallback: when this workflow says `AskUserQuestion`, use a structured question UI if the current host exposes one. If it is unavailable (for example, in Codex), ask the same question plainly in chat, present the same options, and wait for the user's answer.
 
@@ -58,12 +58,12 @@ Before provider fan-out, ask once which investigation topology to use unless the
 
 | Option | Description |
 |--------|-------------|
-| **Host-led Research (Recommended)** | The current host prepares bounded security evidence first; providers challenge and debate the prepared findings. Record internally as `host-seeded`. |
+| **Host-native first (Recommended)** | The active host's native `agestra-research` agent prepares bounded security evidence first; providers challenge and debate the prepared findings. Record internally as `host-seeded`. |
 | **Council Research** | Host and providers independently inspect assigned security surfaces before consolidation and debate. |
 | **Provider-seeded Research** | One selected provider creates the first security seed/evidence artifact; host and other providers challenge it. |
-| **Decide automatically** | Use Host-led for bounded audits, Council for broad/full security reviews, and Provider-seeded only when the user named a provider to lead. |
+| **Decide automatically** | Use Host-native first for bounded audits, Council for broad/full security reviews, and Provider-seeded only when the user named a provider to lead. |
 
-Use `AskUserQuestion` when available, or a plain numbered prompt as fallback. This is a cost/latency gate, not a security clarification. If a host-level no-questions directive prevents asking, choose Host-led Research (`host-seeded`) and report that broader provider investigation was skipped. If Provider-seeded Research is selected and the seed provider is not explicit, record the seed provider as pending; after provider availability is listed, ask which available provider should seed. Do not infer it.
+Use `AskUserQuestion` when available, or a plain numbered prompt as fallback. This is a cost/latency gate, not a security clarification. If a host-level no-questions directive prevents asking, choose Host-native first (`host-seeded`) and report that broader provider investigation was skipped. If Provider-seeded Research is selected and the seed provider is not explicit, record the seed provider as pending; after provider availability is listed, ask which available provider should seed. Do not infer it.
 
 ## Step 4: Route execution
 
@@ -93,6 +93,7 @@ External AI research and debate run in separate fresh sessions, even when the sa
 - **Report artifact path expectation:** `docs/reports/security/YYYY-MM-DD-security-[target].md`
 - **Consensus domain:** `security`
 - **Research topology / 조사 방식:** selected in Step 3 (`host-seeded`, `council`, `provider-seeded`, or `automatic`)
+- **Host-native route:** for Host-native first (`host-seeded`), run active-host `agestra-research` before external provider fan-out; route any host debate participant to `agestra-debate` with `participant_routes`; do not substitute the current host's external CLI provider for this native role
 - **Research notes:** what the selected investigation should look for (secrets/keys, auth/authz boundaries, file/command execution, network exposure, dependency concerns, unsafe defaults)
 - **Research assignments:** optional participant/lens rows for `research_assignments`
 - **Available providers:** from `environment_check`; include configured providers when their detected model capability is suitable, using read-only security-review tools unless the user explicitly approves a separate implementation task
@@ -100,6 +101,7 @@ External AI research and debate run in separate fresh sessions, even when the sa
 - **Specialist handoff (host-native security):** when a host-native security lens is needed, team-lead runs that specialist through the active host layer and includes the result in the selected research/consolidation inputs. Do not use host-specialist handoff to create a bundled research participant.
 - **Locale:** from `setup_status`
 - **Target workspace root:** absolute project folder if the user supplied or implied one; pass it to workspace/debate MCP calls as `workspace_base_dir`
+- **Progress contract:** surface concise phase updates every 30-60 seconds; poll `agent_debate_status`, `run_observable_events` with a cursor, or `cli_worker_status` when available; if trace is `cold-start`, report the current local phase and keep monitoring
 - **Original user request:** preserve verbatim
 
 Team-lead owns resolving the selected research topology, then calling `agent_research_consensus_start` when investigation fan-out is required or `agent_consensus_start` with prepared `initial_aggregation.items` when seed/host evidence is already available. Team-lead must ensure external AI research and debate use separate fresh sessions when a research phase is used, must never create a bundled research pseudo-participant, and must never carry research bundles through `source_documents`. Inspect `aggregation_record.json`, `open_debate_items.json`, `round_packet.{round}.{provider}.json`, the aggregation document, and the leader-authored final decision document under `docs/agestra/`. The brigade must not run destructive exploit tests and must not install tools or run heavyweight/networked scans without explicit user approval.