agestra 4.8.4 → 4.9.0

package/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "agestra",
       "source": "./",
       "description": "Orchestrate Ollama, Gemini, and Codex for multi-AI debates, cross-validation, and GraphRAG memory",
-      "version": "4.8.4",
+      "version": "4.9.0",
       "author": {
         "name": "mua-vtuber"
       },

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agestra",
-  "version": "4.8.4",
+  "version": "4.9.0",
   "description": "Claude Code plugin — orchestrate Ollama, Gemini, and Codex for multi-AI debates, cross-validation, and GraphRAG memory",
   "mcpServers": {
     "agestra": {

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

@@ -0,0 +1,12 @@
+description = "Run the Agestra setup workflow for provider selection and UI language."
+prompt = """
+You are executing the Agestra setup workflow inside Gemini CLI.
+
+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/agestra-moderator.md

@@ -130,9 +130,9 @@ Idempotency: a second call on a terminal state (`approved`, `rejected`, `leader-
               ▼    │    ▼
           approved │   running (snapshot reloaded; max_rounds += additional_rounds)
      (snapshot    │
-      removed)    │ _reject
+       kept)      │ _reject
                    ▼
-               rejected (snapshot removed)
+               rejected (snapshot kept)
 
 (ready-for-approval ─ 24h no tool call ─▶ leader-timeout [snapshot kept])
 (running ─ uncaught internal error ─▶ error)
@@ -367,7 +367,7 @@ If `max_rounds` is hit with open proposals, the moderator surfaces the choice to
 <Tool_Usage>
 - `provider_list` — check available providers at the start.
 - `agent_debate_structured` — **recommended entry point for Structured Debate**: runs individual reviews, alias-clarification phase (if needed), round loop with vote aggregation, parks the session in `ready-for-approval`, and writes the `{sessionId}.approval.json` snapshot. Does NOT write synthesis.
-- `agent_debate_approve` — write synthesis markdown, delete snapshot, close the session.
+- `agent_debate_approve` — write synthesis markdown, mark the snapshot `approved`, close the session.
 - `agent_debate_continue` — force additional rounds on a `ready-for-approval` session.
 - `agent_debate_reject` — close without synthesis; optionally spawn an issue branch listing non-accepted proposals.
 - `agent_debate_create` / `agent_debate_turn` / `agent_debate_conclude` — legacy manual-mode tools used only by the pre-structured debate flow.

package/agents/agestra-team-lead.md

@@ -270,7 +270,7 @@ A 24h inactivity timer starts the moment the session enters `ready-for-approval`
 Before deciding, read the on-disk outputs — the debate writes three folders under the workspace:
 
 - `.agestra/workspace/individual/` — per-participant individual reviews (`individual_{participant}_{topic}_{date}_{seq}.md`). Includes auto-injected specialists like `claude-reviewer` / `claude-qa` when present.
-- `.agestra/workspace/debates/` — debate transcript (`debate_{topic}_{date}_{seq}.md`) plus the approval snapshot (`{sessionId}.approval.json`) while the session is parked.
+- `.agestra/workspace/debates/` — debate transcript (`debate_{topic}_{date}_{seq}.md`) plus the approval snapshot (`{sessionId}.approval.json`). The snapshot remains after `approve` / `reject` for idempotent replays and audit.
 - `.agestra/workspace/synthesis/` — the final synthesis document, written only after `agent_debate_approve` succeeds.
 
 Use `Read` / `Grep` against these paths plus the in-result snapshot to judge whether the debate outcome matches the design.
@@ -279,8 +279,8 @@ Use `Read` / `Grep` against these paths plus the in-result snapshot to judge whe
 
 Pick exactly one of the three follow-up tools, based on inspection:
 
-1. **Accept the outcome** → call `agent_debate_approve` with `debate_id` and an optional `leader_note` (appended to the synthesis footer under "Leader approval notes"). The moderator writes the synthesis markdown, deletes the snapshot, and returns `synthesisDocPath`. Proceed to Phase 7 and relay the path to the user.
-2. **Need more deliberation** → call `agent_debate_continue` with `debate_id` and `additional_rounds` (typical values: `3`, `5`, or `10`; max `20`). The engine resumes the round loop from the prior snapshot and eventually re-parks the session in `ready-for-approval`. Loop back to 5M.2. Use this when the debate was close but unresolved, or when `escalated` came too early.
+1. **Accept the outcome** → call `agent_debate_approve` with `debate_id` and an optional `leader_note` (appended to the synthesis footer under "Leader approval notes"). The moderator writes the synthesis markdown, updates the snapshot to `approved`, and returns `synthesisDocPath`. Proceed to Phase 7 and relay the path to the user.
+2. **Need more deliberation** → call `agent_debate_continue` with `debate_id` and `additional_rounds` (`3`, `5`, or `10` only). The engine resumes the round loop from the prior snapshot and eventually re-parks the session in `ready-for-approval`. Loop back to 5M.2. Use this when the debate was close but unresolved, or when `escalated` came too early.
 3. **Reject the outcome** → call `agent_debate_reject` with `debate_id` and a `reason` (captured in the transcript footer). Optionally set `spawn_issue: true` to write a lightweight issue branch document into `individual/` listing non-accepted proposals for later handling. No synthesis is produced. The debate is closed.
 
 All three tools are idempotent on terminal states — re-calling returns the cached outcome.
@@ -401,7 +401,7 @@ The design document is the authority. If an AI's output conflicts with the desig
 - `trace_summary` / `trace_record` / `trace_compare` — provider quality tracking
 - `ai_chat` / `ai_analyze_files` / `ai_compare` — query external AI
 - `agent_debate_structured` — start a structured multi-AI debate (individual reviews → clarification → rounds → aggregation → `ready-for-approval`). Supports `auto_inject_specialists` (default `true`) to auto-add `claude-reviewer` / `claude-qa` based on topic, and `exclude_participants` as the escape hatch (also the way to keep Ollama or any other provider out — there is no automatic Ollama filter).
-- `agent_debate_approve` / `agent_debate_continue` / `agent_debate_reject` — leader-only finalization tools for a `ready-for-approval` session. `approve` writes the synthesis under `.agestra/workspace/synthesis/`; `continue(additional_rounds=N)` extends the debate (typical N ∈ {3, 5, 10}, max 20); `reject(reason=..., spawn_issue?=true)` closes the session with no synthesis.
+- `agent_debate_approve` / `agent_debate_continue` / `agent_debate_reject` — leader-only finalization tools for a `ready-for-approval` session. `approve` writes the synthesis under `.agestra/workspace/synthesis/`; `continue(additional_rounds=N)` accepts only `3`, `5`, or `10`; `reject(reason=..., spawn_issue?=true)` closes the session with no synthesis.
 - `agent_debate_create/turn/status/summary/list/close/reset` — low-level debate primitives (legacy / diagnostic use).
 - `agent_cross_validate` — cross-validate outputs between providers
 - `cli_worker_spawn` / `cli_worker_status` / `cli_worker_collect` / `cli_worker_stop` — manage Codex/Gemini CLI workers

package/commands/setup.md

@@ -0,0 +1,84 @@
+---
+description: "Select AI providers and UI language for Agestra workflows"
+argument-hint: ""
+---
+
+You are executing the `/agestra setup` command.
+
+## Step 1: Inspect current state
+
+Call these tools first:
+- `environment_check`
+- `provider_list`
+- `setup_status`
+
+Use the results to identify:
+- which providers are currently available
+- which providers are already enabled in `providers.config.json`
+- which locale is currently configured
+
+## Step 2: Handle the no-provider case
+
+If `setup_status` shows that no providers are detected:
+- Explain this in the user's language.
+- Briefly tell the user they need to install at least one supported provider (Ollama, Gemini CLI, Codex CLI, or Claude CLI).
+- Stop without calling `setup_apply`.
+
+## Step 3: Ask for provider selection
+
+Use AskUserQuestion with **multiSelect: true** in the user's language.
+
+Present one option per currently available provider from `setup_status`.
+- Label: provider ID (`ollama`, `gemini`, `codex`, `claude-cli`, etc.)
+- Description: short capability hint from `provider_list`
+
+Guidance:
+- If one or more providers are already enabled, pre-select them conceptually in your reasoning.
+- Recommend enabling at least one external provider.
+- If the user wants Claude-only operation, allow an empty selection only if they explicitly ask for it. Otherwise prefer at least one enabled provider.
+
+## Step 4: Ask for default provider
+
+If the selected provider count is 0:
+- Skip this step and use `default_provider = null`.
+
+If the selected provider count is 1:
+- Use that provider as `default_provider` automatically.
+
+If the selected provider count is 2+:
+- Use AskUserQuestion in the user's language to ask which selected provider should be the default.
+
+## Step 5: Ask for language
+
+Use AskUserQuestion in the user's language with these choices:
+
+| Option | Description |
+|--------|-------------|
+| **한국어** | Korean UI / moderator text |
+| **English** | English UI / moderator text |
+| **日本語** | Japanese UI / moderator text |
+| **中文** | Chinese UI / moderator text |
+
+Map these to locale codes:
+- `한국어` → `ko`
+- `English` → `en`
+- `日本語` → `ja`
+- `中文` → `zh`
+
+## Step 6: Apply setup
+
+Call `setup_apply` with:
+- `enabled_providers`: the selected provider IDs
+- `default_provider`: the chosen default, if any
+- `locale`: the selected locale code
+- `selection_policy`: `default-only`
+
+## Step 7: Report result
+
+Respond in the user's language with:
+- enabled providers
+- default provider
+- selected language
+- the path to `providers.config.json`
+
+If the user changed providers, mention that future Agestra workflows will use the new setup on the next run/read of config.