agestra 4.13.4 → 4.14.0

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.13.4",
+      "version": "4.14.0",
       "author": {
         "name": "mua-vtuber"
       },

package/.claude-plugin/plugin.json

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

package/.gemini/commands/agestra/design.toml

@@ -1,16 +1,16 @@
-description = "Run the Agestra design workflow for an architecture or implementation topic."
+# Generated by Agestra. Managed file.
+description = "Explore architecture and design trade-offs before implementation"
 prompt = """
-You are executing the Agestra design workflow inside Gemini CLI.
+You are executing the `/agestra design` Gemini command.
 
-User topic:
-{{args}}
+- Start with `setup_status`, then `environment_check` and `provider_list`.
+- For investigation-including workflows, route through `agent_research_consensus_start`.
+- Host research consensus contract:
+  호스트가 조사한다.
+  호스트가 정리한다.
+  시스템이 토론한다.
+  호스트가 문서화한다.
+- External AI research and debate run in separate fresh sessions, even when the same provider participates in both phases.
 
-Use the shared workflow spec below as the source of truth and adapt it to the current Gemini host session:
 @{commands/design.md}
-
-Gemini-specific rules:
-- Start with `setup_status`, then `environment_check` and `provider_list`.
-- Prefer Agestra MCP tools, workspace documents, and debate flows over free-form brainstorming.
-- Translate Claude-specific wording into leader-host wording when Gemini is the active host.
-- Keep the final answer in the user's language.
 """

package/.gemini/commands/agestra/idea.toml

@@ -1,16 +1,16 @@
-description = "Run the Agestra idea workflow to discover improvements or compare options."
+# Generated by Agestra. Managed file.
+description = "Discover and refine ideas with Agestra"
 prompt = """
-You are executing the Agestra idea workflow inside Gemini CLI.
+You are executing the `/agestra idea` Gemini command.
 
-User topic:
-{{args}}
+- Start with `setup_status`, then `environment_check` and `provider_list`.
+- For investigation-including workflows, route through `agent_research_consensus_start`.
+- Host research consensus contract:
+  호스트가 조사한다.
+  호스트가 정리한다.
+  시스템이 토론한다.
+  호스트가 문서화한다.
+- External AI research and debate run in separate fresh sessions, even when the same provider participates in both phases.
 
-Use the shared workflow spec below as the source of truth and adapt it to the current Gemini host session:
 @{commands/idea.md}
-
-Gemini-specific rules:
-- Start with `setup_status`, then `environment_check` and `provider_list`.
-- Prefer Agestra MCP tools, workspace documents, and provider comparisons over one-shot brainstorming.
-- Translate Claude-specific wording into leader-host wording when Gemini is the active host.
-- Keep the final answer in the user's language.
 """

package/.gemini/commands/agestra/implement.toml

@@ -1,17 +1,16 @@
-description = "Run the Agestra implementation workflow with leader-only or multi-provider execution."
+# Generated by Agestra. Managed file.
+description = "Coordinate implementation through Agestra"
 prompt = """
-You are executing the Agestra implementation workflow inside Gemini CLI.
+You are executing the `/agestra implement` Gemini command.
 
-User task:
-{{args}}
+- Start with `setup_status`, then `environment_check` and `provider_list`.
+- For investigation-including workflows, route through `agent_research_consensus_start`.
+- Host research consensus contract:
+  호스트가 조사한다.
+  호스트가 정리한다.
+  시스템이 토론한다.
+  호스트가 문서화한다.
+- External AI research and debate run in separate fresh sessions, even when the same provider participates in both phases.
 
-Use the shared workflow spec below as the source of truth and adapt it to the current Gemini host session:
 @{commands/implement.md}
-
-Gemini-specific rules:
-- Start with `setup_status`, then `environment_check` and `provider_list`.
-- Prefer Agestra MCP tools and worker orchestration over ad-hoc shell-heavy implementation plans.
-- Treat "Leader-host only" as the Gemini-led local path when Gemini is the active host.
-- Use the shared `agestra-implementer` role semantics for host-local code edits.
-- Keep the final answer in the user's language.
 """

package/.gemini/commands/agestra/qa.toml

@@ -1,16 +1,16 @@
-description = "Run the Agestra QA workflow for document-based verification and optional E2E."
+# Generated by Agestra. Managed file.
+description = "Run document-first QA with Agestra"
 prompt = """
-You are executing the Agestra QA workflow inside Gemini CLI.
+You are executing the `/agestra qa` Gemini command.
 
-User target:
-{{args}}
+- Start with `setup_status`, then `environment_check` and `provider_list`.
+- For investigation-including workflows, route through `agent_research_consensus_start`.
+- Host research consensus contract:
+  호스트가 조사한다.
+  호스트가 정리한다.
+  시스템이 토론한다.
+  호스트가 문서화한다.
+- External AI research and debate run in separate fresh sessions, even when the same provider participates in both phases.
 
-Use the shared workflow spec below as the source of truth and adapt it to the current Gemini host session:
 @{commands/qa.md}
-
-Gemini-specific rules:
-- Start with `setup_status`, then `environment_check` and `provider_list`.
-- Prefer Agestra MCP tools and prompt assets over ad-hoc QA prompting.
-- If the workflow refers to Claude-specific wording, translate it to the current leader-host path rather than asking the user to switch hosts.
-- Keep the final answer in the user's language.
 """

package/.gemini/commands/agestra/research.toml

@@ -0,0 +1,16 @@
+# Generated by Agestra. Managed file.
+description = "Run research using a selected investigation topology"
+prompt = """
+You are executing the `/agestra research` Gemini command.
+
+- Start with `setup_status`, then `environment_check` and `provider_list`.
+- For investigation-including workflows that continue into domain consensus, route through `agent_research_consensus_start`.
+- Host research consensus contract:
+  호스트가 조사한다.
+  호스트가 정리한다.
+  시스템이 토론한다.
+  호스트가 문서화한다.
+- External AI research and debate run in separate fresh sessions, even when the same provider participates in both phases.
+
+@{commands/research.md}
+"""

package/.gemini/commands/agestra/review.toml

@@ -1,16 +1,16 @@
-description = "Run the Agestra review workflow for a target, diff, or feature."
+# Generated by Agestra. Managed file.
+description = "Run a code or document review with Agestra"
 prompt = """
-You are executing the Agestra review workflow inside Gemini CLI.
+You are executing the `/agestra review` Gemini command.
 
-User target:
-{{args}}
+- Start with `setup_status`, then `environment_check` and `provider_list`.
+- For investigation-including workflows, route through `agent_research_consensus_start`.
+- Host research consensus contract:
+  호스트가 조사한다.
+  호스트가 정리한다.
+  시스템이 토론한다.
+  호스트가 문서화한다.
+- External AI research and debate run in separate fresh sessions, even when the same provider participates in both phases.
 
-Use the shared workflow spec below as the source of truth and adapt it to the current Gemini host session:
 @{commands/review.md}
-
-Gemini-specific rules:
-- Start with `setup_status`, then `environment_check` and `provider_list`.
-- Prefer Agestra MCP tools and prompt assets over ad-hoc review prompting.
-- If the workflow refers to Claude-specific wording, translate it to the current leader-host path rather than asking the user to switch hosts.
-- Keep the final answer in the user's language.
 """

package/.gemini/commands/agestra/security.toml

@@ -1,17 +1,16 @@
-description = "Run the Agestra dedicated security audit workflow."
+# Generated by Agestra. Managed file.
+description = "Run a security review with Agestra"
 prompt = """
-You are executing the Agestra security workflow inside Gemini CLI.
+You are executing the `/agestra security` Gemini command.
 
-User target:
-{{args}}
+- Start with `setup_status`, then `environment_check` and `provider_list`.
+- For investigation-including workflows, route through `agent_research_consensus_start`.
+- Host research consensus contract:
+  호스트가 조사한다.
+  호스트가 정리한다.
+  시스템이 토론한다.
+  호스트가 문서화한다.
+- External AI research and debate run in separate fresh sessions, even when the same provider participates in both phases.
 
-Use the shared workflow spec below as the source of truth and adapt it to the current Gemini host session:
 @{commands/security.md}
-
-Gemini-specific rules:
-- Start with `setup_status`, then `environment_check` and `provider_list`.
-- Prefer Agestra MCP tools and prompt assets over ad-hoc security prompting.
-- If the workflow refers to Claude-specific wording, translate it to the current leader-host path rather than asking the user to switch hosts.
-- Do not run destructive exploit tests or ask the user to paste real secrets.
-- Keep the final answer in the user's language.
 """

package/.gemini/commands/agestra/setup.toml

@@ -1,12 +1,7 @@
-description = "Run the Agestra setup workflow for provider selection and UI language."
+# Generated by Agestra. Managed file.
+description = "Select AI providers and UI language for Agestra workflows"
 prompt = """
-You are executing the Agestra setup workflow inside Gemini CLI.
+You are executing the `/agestra setup` Gemini command.
 
-Use the shared workflow spec below as the source of truth and adapt it to the current Gemini host session:
 @{commands/setup.md}
-
-Gemini-specific rules:
-- Start with `environment_check`, `provider_list`, and `setup_status`.
-- Prefer Agestra MCP tools over ad-hoc shell edits.
-- Keep all user-facing questions and the final answer in the user's language.
 """

package/AGENTS.md

@@ -1,45 +1,53 @@
-# Agestra for Codex
-
-This repository includes a Codex-friendly host wrapper for Agestra.
-
-## First Run
-
+# Agestra for Codex
+
+This repository includes a Codex-friendly host wrapper for Agestra.
+
+## First Run
+
 1. Build the bundled MCP server if needed: `npm run bundle`
-2. Register Agestra with Codex and install generated custom agents: `npm run install:codex:assets`
-3. Open this repository in Codex. This `AGENTS.md` file is loaded automatically.
-
-Use `npm run install:codex` only when you intentionally want MCP registration without generated `.codex/agents/*.toml` assets.
-Low-level MCP calls do not silently write setup. High-level Agestra workflows must call `setup_status` first; if it reports `Setup required: yes`, run the interactive setup questions immediately, call `setup_apply` after the user chooses providers/locale, then resume the original workflow.
-Use `host_assets_status` to inspect generated host assets, and only call `host_assets_install` after the user agrees to install or refresh Codex custom agents.
-
-## How to Work Here
-
-- Treat `commands/*.md` as the source of truth for Agestra workflows.
-- When the user asks for review, QA, security, design, idea, or implementation help, start with `setup_status`, `environment_check`, and `provider_list`. If `setup_status` reports `Setup required: yes`, complete interactive setup first and then resume the original workflow.
-- Prefer Agestra MCP tools over ad-hoc multi-provider prompting.
-- If any legacy workflow text mentions "Claude only", interpret that as the current leader-host-only path when Claude is not the active host.
-
-## Workflow Mapping
-
-- Review requests: follow `commands/review.md`
-- QA / verification requests: follow `commands/qa.md`
-- Security audit requests: follow `commands/security.md`
-- Review, QA, and security workflows write durable reports under `docs/reports/review/`, `docs/reports/qa/`, and `docs/reports/security/` unless the user asks for chat-only output.
-- Persistent E2E test creation/maintenance is internal: QA produces `E2E_TEST_WORK_REQUEST`, the leader asks the user, and approved work goes to `agestra-e2e-writer`.
-- Design and architecture requests: follow `commands/design.md`
-- Idea discovery requests: follow `commands/idea.md`
-- Implementation requests: follow `commands/implement.md`
-
-## Core MCP Tools
-
-- `environment_check` and `provider_list`: inspect host/provider state first
-- `agent_debate_structured` (with `agent_debate_approve`/`_continue`/`_reject`) and `agent_debate_review`: run approval-gated multi-provider review flows
-- `cli_worker_spawn`, `agent_changes_review`, `agent_changes_accept`, `agent_changes_reject`: use for autonomous Codex/Gemini worker tasks
-- `host_assets_status`, `host_assets_install`, `host_assets_uninstall`: inspect and explicitly manage generated host-native assets such as Codex custom agents
-- `qa_run`: run workspace build/test verification before reporting implementation completion
-
+2. Register this checkout with Codex and install user-scope generated custom agents/skills: `npm run install:codex`
+3. For a real npm-global install from this checkout instead, run `npm run bundle`, `npm install -g .`, then `npm run install:codex:global`
+4. Open the target repository in Codex. Its `AGENTS.md` file is loaded automatically when the project is trusted.
+
+Use `npm run install:codex:mcp` only when you intentionally want MCP registration without generated Codex agents/skills. Use `npm run install:codex:assets` only when you intentionally want project-local `.codex/agents` and `.codex/skills` assets in the current checkout.
+Low-level MCP calls do not silently write setup. High-level Agestra workflows must call `setup_status` first; if it reports `Setup required: yes`, run the interactive setup questions immediately, call `setup_apply` after the user chooses providers/locale, then resume the original workflow.
+Use `host_assets_status` to inspect generated Codex host assets, and only call `host_assets_install` after the user agrees to install or refresh Codex custom agents. The `host_assets_*` MCP tools currently manage Codex assets only.
+
+## How to Work Here
+
+- Default to direct Codex work using the workspace `AGENTS.md` contract, oh-my-codex workflows, and Superpowers-style skills when they apply.
+- Use Agestra primarily for explicit multi-AI or provider orchestration requests, such as when the user names Agestra, Codex/Gemini/Ollama providers, "multi-AI", "multiple AI", "provider", `agent_debate_*`, `cli_worker_*`, or asks to gather/compare several AI opinions.
+- 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.
+- Native helper agents are created by the active host layer. In Codex, use the generated custom agents installed from these assets; external MCP/CLI/chat providers participate through Agestra tools and never create or manage Codex native agents.
+- Keep Agestra setup/status/provider checks as installation and health checks, not as workflow-routing triggers.
+- Run `setup_status`, `environment_check`, and `provider_list` when the task concerns Agestra installation, MCP registration, host assets, provider availability, or before entering an Agestra workflow. If `setup_status` reports `Setup required: yes`, complete interactive setup first and then resume the original task.
+- Do not treat ordinary review, QA, security, design, idea, implementation, cleanup, build-fix, or planning requests as Agestra workflows just because setup/status/provider checks exist.
+- When an Agestra workflow is active, treat `commands/*.md` as the source of truth for that workflow.
+- Prefer Agestra MCP tools over ad-hoc multi-provider prompting only when the task is actually in Agestra/multi-provider mode.
+- If any legacy workflow text mentions old single-host Agestra execution, treat it as obsolete. Direct current-host work should happen outside Agestra workflows.
+
+## Workflow Mapping
+
+- When Agestra is active, review requests follow `commands/review.md`
+- When Agestra is active, QA / verification requests follow `commands/qa.md`
+- When Agestra is active, security audit requests follow `commands/security.md`
+- Review, QA, and security workflows write durable reports under `docs/reports/review/`, `docs/reports/qa/`, and `docs/reports/security/` unless the user asks for chat-only output.
+- Persistent E2E test creation/maintenance is internal: QA produces `E2E_TEST_WORK_REQUEST`, the leader asks the user, and approved work goes to `agestra-implementer` with `mode: e2e-test-authoring`.
+- When Agestra is active, design and architecture requests follow `commands/design.md`
+- When Agestra is active, idea discovery requests follow `commands/idea.md`
+- When Agestra is active, implementation requests follow `commands/implement.md`
+
+## Core MCP Tools
+
+- `setup_status`, `environment_check`, and `provider_list`: inspect installation, host, and provider state for Agestra health checks and active Agestra workflows
+- `agent_consensus_start` (with `agent_debate_approve`/`_continue`/`_reject`) and `agent_debate_review`: run approval-gated consensus flows from prepared `initial_aggregation`
+- `cli_worker_spawn`, `agent_changes_review`, `agent_changes_accept`, `agent_changes_reject`: use for explicit autonomous Codex/Gemini worker tasks
+- `host_assets_status`, `host_assets_install`, `host_assets_uninstall`: inspect and explicitly manage generated Codex host-native assets such as custom agents and skills
+- `qa_run`: run workspace build/test verification before reporting implementation completion
+
 ## Project Assets
 
-- `agents/`: canonical role prompts (`agestra-team-lead`, `agestra-e2e-writer`, `agestra-reviewer`, etc.)
+- `agents/`: canonical role prompts (`agestra-team-lead`, `agestra-research`, `agestra-debate`, `agestra-implementer`)
 - `skills/`: reusable workflow references
 - `GEMINI.md` and `.gemini/commands/`: Gemini-specific host assets; keep behavior aligned with them when updating shared workflows

package/GEMINI.md

@@ -2,11 +2,14 @@
 
 This repository includes Gemini-native wrapper assets for Agestra.
 
+Runtime contract: native helper agents are a capability of the active host layer. External MCP/CLI/chat providers participate in Agestra workflows, but they do not create or manage Gemini native agents. These generated Gemini assets are host-neutral workflow assets; verify real Gemini native-agent team behavior before claiming parity with Claude nested teams or Codex custom-agent behavior.
+
 ## First Run
 
 1. Build the bundled MCP server if needed: `npm run bundle`
-2. Register Agestra with Gemini in this project: `npm run install:gemini`
-3. Open the repository in Gemini CLI. `GEMINI.md` and `.gemini/commands/` are loaded automatically.
+2. Register this checkout with Gemini and install the user-scope `agestra` extension: `npm run install:gemini`
+3. For a real npm-global install from this checkout instead, run `npm run bundle`, `npm install -g .`, then `npm run install:gemini:global`
+4. Open the target repository in Gemini CLI. `GEMINI.md` and `.gemini/commands/` are loaded automatically when present.
 
 ## Project Commands
 
@@ -23,17 +26,28 @@ Each command delegates to the shared workflow specs in `commands/*.md`.
 
 ## Usage Rules
 
+- 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.
 - Start orchestration requests with `setup_status`, then `environment_check` and `provider_list`.
 - Prefer Agestra MCP tools instead of rebuilding workflows in free-form prompts.
 - Treat `commands/*.md` and `agents/*.md` as the canonical workflow and role assets.
-- If any legacy shared workflow text mentions "Claude only", translate that to the current leader-host-only path when Gemini is the active host.
+- Keep native agent creation host-owned. Providers reached through MCP, CLI workers, or chat are participants only.
+- For investigation-including workflows, route through `agent_research_consensus_start`.
+- Use this host research consensus contract verbatim:
+  호스트가 조사한다.
+  호스트가 정리한다.
+  시스템이 토론한다.
+  호스트가 문서화한다.
+- External AI research and debate run in separate fresh sessions, even when the same provider participates in both phases.
+- If any legacy shared workflow text mentions old single-host Agestra execution, treat it as obsolete. Direct current-host work should happen outside Agestra workflows.
 
 ## Core MCP Tools
 
-- `agent_debate_structured`, `agent_debate_approve`/`_continue`/`_reject`, `agent_debate_review`: structured multi-provider reviews and approval-gated debates
+- `agent_research_consensus_start`: host-led research, consolidation, system debate, engine aggregation docs, and host-authored final decision docs for investigation-including workflows
+- `agent_consensus_start`, `agent_debate_approve`/`_continue`/`_reject`, `agent_debate_review`: direct consensus sessions from prepared `initial_aggregation` and approval-gated debate artifacts
 - `cli_worker_spawn`, `agent_changes_review`, `agent_changes_accept`, `agent_changes_reject`: autonomous worker lifecycle
 - `workspace_*`: document-backed review and aggregation flows
 - `qa_run`: workspace build/test verification before implementation completion
 
 Review, QA, and security workflows write durable reports under `docs/reports/review/`, `docs/reports/qa/`, and `docs/reports/security/` unless the user asks for chat-only output.
-Persistent E2E test creation/maintenance is internal: QA produces `E2E_TEST_WORK_REQUEST`, the leader asks the user, and approved work goes to `agestra-e2e-writer`. There is no standalone Gemini `/agestra:e2e` command yet.
+Persistent E2E test creation/maintenance is internal: QA produces `E2E_TEST_WORK_REQUEST`, the leader asks the user, and approved work goes to `agestra-implementer` with `mode: e2e-test-authoring`. There is no standalone Gemini `/agestra:e2e` command yet.