agestra 4.13.2 → 4.13.4

package/hooks/user-prompt-submit.js

@@ -212,8 +212,8 @@ process.stdin.on("end", () => {
         "  1. Call `setup_status`, `environment_check`, and `provider_list`",
         "  2. Follow `commands/implement.md`",
         "  3. Present a task-to-provider routing table before spawning workers",
-        "  4. Use Ollama only for simple/repetitive proposal work unless a safe edit-capable path exists",
-        "  5. Use `agestra-implementer` or Codex/Gemini CLI workers for actual code edits",
+        "  4. Distribute work according to detected model capability, including frontier and local models",
+        "  5. Use safe edit-capable paths for actual code edits: `agestra-implementer`, Codex/Gemini CLI workers, or write-enabled local/tool models when policy and capability qualify",
         "",
         "If user selects NO:",
         "  Proceed without Agestra task distribution. Handle the task directly.",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "agestra",
-  "version": "4.13.2",
-  "description": "Multi-host AI orchestration toolkit for Claude Code, Codex CLI, and Gemini CLI",
+  "version": "4.13.4",
+  "description": "Multi-host MCP orchestration for Claude Code, Codex CLI, Gemini CLI, and local models",
   "type": "module",
   "packageManager": "npm@11.11.0",
   "workspaces": [
@@ -56,14 +56,20 @@
   },
   "keywords": [
     "claude-code-plugin",
+    "mcp-server",
     "codex-cli",
     "gemini-cli",
     "mcp",
+    "multi-agent",
     "multi-ai",
     "ollama",
+    "local-llm",
     "gemini",
     "codex",
-    "ai-orchestration"
+    "ai-orchestration",
+    "agent-orchestration",
+    "code-review",
+    "cross-validation"
   ],
   "repository": {
     "type": "git",

package/skills/design.md

@@ -127,7 +127,7 @@ Team-lead owns:
 - Spawn `agestra:agestra-moderator` or `agestra:agestra-designer` directly when external providers are involved
 - Build individual documents or hand-edit generated debate/synthesis Markdown
 
-Direct execution from this skill bypasses team-lead's quality-based routing (`trace_summary`), task design, and consistency enforcement. Always go through team-lead in Branch B.
+Direct execution from this skill bypasses team-lead's capability-based routing and optional trace-assisted signals (`trace_summary`), task design, and consistency enforcement. Always go through team-lead in Branch B.
 
 When team-lead returns, present the synthesis to the user in the user's language. Preserve each provider's rationale on disputed positions.
 

package/skills/idea.md

@@ -118,7 +118,7 @@ Team-lead owns:
 - Spawn `agestra:agestra-moderator` or `agestra:agestra-ideator` directly when external providers are involved
 - Build individual documents or hand-edit generated debate/synthesis Markdown
 
-Direct execution from this skill bypasses team-lead's quality-based routing (`trace_summary`), task design, and consistency enforcement. Always go through team-lead in Branch B.
+Direct execution from this skill bypasses team-lead's capability-based routing and optional trace-assisted signals (`trace_summary`), task design, and consistency enforcement. Always go through team-lead in Branch B.
 
 When team-lead returns, present the synthesis to the user in the user's language. Preserve each provider's rationale on disputed positions. Treat `.agestra/workspace/` as the internal research/debate workspace; the user-facing decision record belongs under `docs/ideas/`.
 

package/skills/provider-guide.md

@@ -68,9 +68,9 @@ Two modes available via team-lead orchestration:
 | **Leader-host only** | `agestra-implementer` applies scoped code changes; reviewer/QA verify | Simple or risky tasks that should stay under the current host |
 | **Suggested AI distribution** | Team lead proposes which enabled AIs should do which work, asks for approval, then dispatches | Complex, repetitive, or parallelizable tasks |
 
-Small is not the same as simple:
+Small is not the same as simple. Distribute work according to detected model capability, including frontier and local models:
 - **Small but hard/risky:** one-line auth, security, concurrency, data-loss, or release logic. Keep with `agestra-implementer` or a high-capability CLI worker plus QA.
-- **Large but simple:** repeated safe pattern across many files. Prefer Ollama for a patch plan or candidate transform, then `agestra-implementer` applies it unless a safe edit-capable worker is available.
+- **Large but simple:** repeated safe pattern across many files. Prefer a capability-matched local/tool model for a patch plan, candidate transform, or scoped edit when execution policy allows; otherwise have `agestra-implementer` apply it.
 
 ## CLI Workers
 
@@ -91,10 +91,10 @@ Use the `worker-manage` skill for user-friendly worker operations.
 
 | Task Complexity | Route To |
 |---|---|
-| Simple repetitive proposal work (formatting, pattern matching) | Ollama local model preferred for suggestions; implementer applies |
-| Moderate (code review, summarization) | Ollama >= 3 GB or cloud |
-| Complex implementation (multi-file, multi-step) | CLI worker (Codex/Gemini) |
-| Complex analysis (architecture, refactoring) | Cloud providers (Gemini, Codex) via ai_chat |
+| Simple repetitive proposal work (formatting, pattern matching) | Capability-matched local/tool model or host implementer |
+| Moderate (code review, summarization) | Local model tier that qualifies, or a frontier provider |
+| Complex implementation (multi-file, multi-step) | High-capability CLI worker (for example Codex/Gemini) or host implementer |
+| Complex analysis (architecture, refactoring) | Highest-capability detected model, usually a frontier provider |
 | No providers available | Handle directly — do not suggest agestra tools |
 
 ## When to Suggest Agestra Tools
@@ -176,7 +176,7 @@ When team-lead orchestrates multi-AI work, the full pipeline is:
 Phase 0: Clarity Gate (designer — ambiguity scoring, skip if request is clear)
 Phase 1: Situation Assessment (team-lead — environment_check, providers, design doc)
 Phase 2: Task Design (team-lead — work mode selection, decompose, route by AI capability)
-Phase 3: Parallel Execution (team-lead — implementer + CLI workers + Ollama proposal work, monitor loop)
+Phase 3: Parallel Execution (team-lead — implementer + CLI workers + capability-matched local/tool model work, monitor loop)
 Phase 4: Result Inspection (team-lead — review diffs, check consistency, merge)
 Phase 5: QA Cycle (qa — spec-to-code map, verify, classify failures → team-lead auto-fixes, max 5 cycles) [host-local mode]
 Phase 5M: Structured QA Debate (mode:"review", cross-validation across providers)         [multi-AI mode]
@@ -190,7 +190,7 @@ Phase 7: Report
 
 **Work modes:**
 - `Leader-host only`: `agestra-implementer` implements, no external workers
-- `Multi-AI`: CLI workers + Ollama proposal work for parallelized execution; team lead supervises and merges
+- `Multi-AI`: CLI workers + capability-matched local/tool model work for parallelized execution; team lead supervises and merges
 
 **QA domain:**
 - `/agestra qa` verifies existing work without code changes. It asks Standard vs Full E2E depth, writes a QA report under `docs/reports/qa/`, then runs host-local QA or multi-AI QA debate. It never spawns implementer or CLI workers for product fixes. If QA decides persistent E2E tests are needed, team-lead asks the user and routes only the approved test work to `agestra-e2e-writer`.

package/skills/review.md

@@ -105,7 +105,7 @@ Team-lead owns:
 - Spawn `agestra:agestra-moderator` or `agestra:agestra-reviewer` directly when external providers are involved
 - Build individual documents or aggregate them yourself
 
-Direct execution from this skill bypasses team-lead's task design, quality-based routing (`trace_summary`), and consistency enforcement. Always go through team-lead in Branch B.
+Direct execution from this skill bypasses team-lead's task design, capability-based routing with optional trace-assisted signals (`trace_summary`), and consistency enforcement. Always go through team-lead in Branch B.
 
 ### Phase 4: Review Verdict