pantheon-opencode 1.5.0-beta.15 → 1.5.0-beta.17

package/AGENTS.md

@@ -301,7 +301,9 @@ memory_store({
     agreements: ["point1", "point2"],
     divergences: [{"issue": "...", "resolution": "..."}],
     response_rate: "X of Y",
-    themis_audit: "approved|issues"
+    themis_audit: "approved|issues",
+    precedent_used: false,
+    timestamp: "<ISO-8601>"
   },
   metadata: {
     type: "council_decision",
@@ -310,6 +312,7 @@ memory_store({
   }
 })
 ```
+`value` is JSON-serialized before storing (the MCP `memory_store.value` argument is a string).
 
 ### Read Path (Precedent Fast-Path)
 Before dispatching a new council, Zeus runs:
@@ -320,8 +323,8 @@ memory_search(question, top_k=2, namespace="council_decisions")
 Result interpretation:
 | Score | Age | Action |
 |-------|-----|--------|
-| > 0.85 | < 30 days | Return precedent as fast-path answer. Skip council dispatch entirely. |
-| > 0.85 | >= 30 days | Return with warning "Reavaliar se contexto mudou" + proceed with council |
+| > 0.85 | < 30 days | Return precedent verbatim (note "⚠️ Decisão de [data] — reavaliar se contexto mudou") as fast-path answer. Skip council dispatch entirely. |
+| > 0.85 | >= 30 days | Return with warning "Reavaliar se contexto mudou — decisão tem mais de 30 dias" + proceed with council |
 | 0.5 - 0.85 | Any | Include as context for specialists but still dispatch council |
 | < 0.5 | Any | Ignore, proceed with fresh council |
 
@@ -371,7 +374,7 @@ You MUST self-monitor for these stall conditions:
 | Symptom | Detection Rule | Recovery Action |
 |---------|---------------|-----------------|
 | Silent loop | 3+ consecutive turns with no tool call AND no visible progress | Output `[STALL_DETECTED]` and re-read your task definition. If still stuck, escalate to user with: "I appear to be stuck on [task]. Options: (1) retry with different approach, (2) delegate to specialist, (3) simplify scope." |
-| Delegation black hole | Agent dispatched but no response after 2x the timeout from routing.yml | Log the hang, cancel via `cancel_task`, dispatch to fallback agent, report to user |
+| Delegation black hole | Agent dispatched but no response after 2x the timeout from routing.yml | Log the hang, cancel via `cancel_task`, then follow the fallback chain in `## ⏱️ Timeout & Retry Enforcement` |
 | Circular delegation | Same specialist re-dispatched for same task 2+ times without progress | Break cycle: dispatch to different specialist OR escalate to user |
 | Idle after completion | All background tasks completed but no synthesis/next step for 2+ turns | Force synthesis: summarize all completed results and propose next action |
 | Context thrash | Re-reading same files repeatedly without new action | Stop re-reading. State: "Already have context on [file]. Proceeding with [action]." |
@@ -397,9 +400,7 @@ When a delegation fails (timeout, empty response, error):
 
 2. **Retry ONCE** with rephrased prompt — add: "Previous attempt failed with: [error]. Adjusted approach: [what changed]."
 
-3. **If retry also fails** → DO NOT retry a third time blindly. Instead:
-   - Dispatch to fallback agent (from routing.yml)
-   - If no fallback, escalate to user with: "Task [X] failed after retry. Options: (a) simplify, (b) different agent, (c) manual intervention."
+3. **If retry also fails** → do NOT retry blindly; follow the fallback chain and escalation protocol in `## ⏱️ Timeout & Retry Enforcement`.
 
 ## Progress Checkpoint
 
@@ -564,10 +565,7 @@ sequenceDiagram
 ## Dispatch Sequence (9-Step Protocol)
 
 ### Step 0 — Precedent Fast-Path (Fase 1)
-Before any dispatch: `memory_search(query, top_k=2, namespace="council_decisions")`
-- Score > 0.85 AND age < 30 days → return precedent verbatim with note "⚠️ Decisão de [data] — reavaliar se contexto mudou". SKIP entire dispatch.
-- Score > 0.85 AND age > 30 days → return precedent with ⚠️ "Reavaliar se contexto mudou — decisão tem mais de 30 dias"
-- Else → proceed to Step 0b
+Run the precedent read path defined in `## Memory Protocol > Council Decisions Namespace` (`memory_search(query, top_k=2, namespace="council_decisions")`). If no precedent applies, proceed to Step 0b.
 
 ### Step 0b — Apollo Pre-Scan (Fase 2, --research flag)
 If `/pantheon --research <question>`: dispatch @apollo with 30s timeout. Inject findings as `shared_context` into ALL specialist prompts. Skip if flag absent.
@@ -669,33 +667,11 @@ task(subagent_type: "themis", prompt: "Audit this council synthesis for fidelity
 - If issues → fix each issue before delivering to user
 
 ### Step 9 — Persist & Reconcile (Fase 1)
-```
-memory_store({
-  namespace: "council_decisions",
-  key: "council:<yyyy-mm-dd>:<slug>",
-  value: JSON.stringify({
-    question, specialists, recommendation, confidence,
-    agreements, divergences, precedent_used, timestamp
-  }),
-  metadata: {type: "council_decision", specialist_count: N}
-})
-board.markReconciled("<task-id>")
-```
+Persist the decision using the write path in `## Memory Protocol > Council Decisions Namespace`, then `board.markReconciled("<task-id>")`.
 
 ## Specialist Output Format (Fase 1 — machine-parseable structured fields)
 
-Specialists MUST return these structured fields in their response:
-
-```
-## specialist_response
-**position:** <clear one-sentence position>
-**reasoning:** <2-4 sentences>
-**trade_offs:** <what's gained vs lost>
-**risks:** <what could go wrong>
-**confidence:** High | Medium | Low
-**agreement_signals:** agree: @agent1, @agent2 on [issue] | disagree: @agent3 on [issue]
-**specific_claims:** <count of specific factual claims in response>
-```
+Specialists MUST return the structured `## specialist_response` format (position, reasoning, trade_offs, risks, confidence, agreement_signals, specific_claims) defined in `## Agent Return Format > Council Specialist Response Format`.
 
 ## Domain-to-Specialist Mapping
 
@@ -928,39 +904,14 @@ ANY NO  → full task (IMPL artifact + Themis review mandatory)
 3. **No Themis dependency** — output doesn't feed into a phase that requires review
 
 ## Subtask Return Format
-Expect a `subtask_summary` response with:
-```
-## subtask_summary
-**files_changed:** [paths]
-**summary:** What was done
-**tests:** ✅ or N/A
-**status:** complete | partial | escalated
-```
+Return the standard `## subtask_summary` defined in `## Agent Return Format` (files_changed, summary, tests, coverage, tokens, status, blockers).
 
 ## Timeout Parcial (Partial Results)
 
-Timeout parcial is ONLY for read-only, independent agents:
-- ✅ @apollo — can return partial file list ("found 7 of 12 files before timeout")
-- ✅ @gaia — can return partial literature findings
-
-- ✅ @talos — can confirm progress if hotfix times out
-- ❌ Never for implementers or reviewers — must complete or fail
-
-When dispatching with partial-OK, set expectation:
-```
-@apollo Search for auth files. Timeout parcial OK — return whatever you have.
-```
+Only agents marked ✅ in the Timeout Behavior table above may return partial results: @apollo (partial file list, e.g. "found 7 of 12 files before timeout"), @gaia (partial literature findings) and @talos (confirm progress if a hotfix times out). Never for implementers or reviewers — they must complete or fail. When dispatching with partial-OK, set the expectation: `@apollo Search for auth files. Timeout parcial OK — return whatever you have.`
 
 ---
 
 # 📊 TIMEOUT TRACKING
 
-Maintain awareness of in-flight delegations:
-
-| Agent | Timeout | Status | Partial OK? |
-|-------|---------|--------|-------------|
-| @apollo | 60s | ✅ complete | ✅ |
-| @hermes | 180s | ⏳ in progress | ❌ |
-| @themis | 120s | ⏳ in progress | ❌ |
-
-Log timeouts to `/memories/session/timeout-log.md` for later analysis.
+Track in-flight delegations against the Timeout Behavior table above. Log timeouts to `/memories/session/timeout-log.md` for later analysis.

package/CHANGELOG.md

@@ -18,6 +18,61 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## ✅ Closed Issues
 
+## [v1.5.0-beta.17] - 2026-09-15
+
+<!-- Add new changes here. Running `node scripts/versioning.mjs apply` will
+     move this section to a versioned entry and reset the template below. -->
+
+## 🆕 What's New
+
+- **Delegação nativa no host:** o motor `pantheon_delegate` foi removido
+  (~3,9k linhas) junto com as tools `pantheon_delegate`,
+  `pantheon_delegation_read` e `pantheon_delegation_list`; a delegação agora usa
+  o **`task()` nativo** do host (child sessions). 16 arquivos de teste obsoletos
+  removidos.
+- **TUI — painel Delegations lê a sessão nativa:** o painel passa a derivar de
+  `session.children` + `session.status` + md (o arquivo de board deixou de ser
+  fonte). Mantidas as cores de status, retenção, ceiling, filtro de sessão e
+  guards.
+- **Camada fina preservada:** `task-result-guard` (verified completion de child
+  vazio), `native-task-status` e guards de enforcement.
+
+## 🐞 Fixed
+
+- **Read-only enforcement re-apontado para sessões nativas:** aplicado no
+  público via hook `chat.params` e `hashline_edit` bloqueado para `apollo`/`gaia`,
+  fechando o bypass aberto após a remoção do motor de delegação.
+- **Docs/comentários limpos:** referências aos módulos removidos atualizadas,
+  incluindo nits de comentário em `tests/pantheon/tui-delegations.test.ts` e
+  `src/pantheon/session-id.ts`.
+
+## [v1.5.0-beta.16] - 2026-09-15
+
+<!-- Add new changes here. Running `node scripts/versioning.mjs apply` will
+     move this section to a versioned entry and reset the template below. -->
+
+## 🆕 What's New
+
+- **Modernização CI/supply-chain:** 22 actions SHA-pinadas; `gitleaks-action` v3
+  (fix crítico — a v2 morria com Node 20 em 2026-09-16) com CLI 8.30.1; cache
+  npm/pip; Dependabot; CodeQL `+python` e `codeql-config`; permissões reduzidas
+  no `docs.yml`; job `version-check` fundido no `validate`; `upload-artifact` v7
+  e `download-artifact` v8.
+- **Lean:** ~17 módulos mortos removidos de `src/pantheon/`, docs/scripts
+  obsoletos, `teste/`/`testes/`, `Dockerfile`/`docker-compose` (de outro projeto)
+  e caches; ~38% dos arquivos de teste removidos/consolidados; testes mínimos
+  readicionados para os módulos vivos (tool-ceiling, native-probe).
+- **Instructions:** deduplicação das instruções compartilhadas — contexto menor
+  sem perder nenhuma regra.
+
+## 🐞 Fixed
+
+- **2 flakes determinísticos eliminados:** TTL do MCP persistence
+  (`test_ttl_expiry_real_time`) e `logger.test.mjs` deixaram de depender de
+  timing/carga do host.
+- **Refs stale corrigidas:** referências de versão/ambiente atualizadas para
+  Node 22+.
+
 ## [v1.5.0-beta.15] - 2026-09-15
 
 <!-- Add new changes here. Running `node scripts/versioning.mjs apply` will

package/README.md

@@ -76,25 +76,14 @@ availability and configuration of OpenCode and any optional services you choose
 to use. Check the [releases](https://github.com/ils15/pantheon-opencode/releases)
 and [changelog](CHANGELOG.md) for the latest published changes.
 
-## Delegation engines (legacy default, native opt-in)
+## Delegation (native `task()`)
 
-Pantheon exposes two delegation engines behind one tool surface:
-
-- **Legacy (default)** — `pantheon_delegate`, the original engine registered by
-  the V1 plugin. No configuration is required.
-- **Native (opt-in, experimental)** — OpenCode's native `task()` child-session
-  engine, selected with `PANTHEON_DELEGATE_MODE=native`. Native is strict: it
-  does not use foreground fallback, model failover, or retry; it performs a
-  lazy capability probe on the first dispatch and includes the resulting
-  status in the delegation receipt.
-
-Legacy stays the default for v1.5.x; native is not promoted to default until
-v1.6. See [ADR-0011](.pantheon/memory-bank/adr/0011-delegation-engine-contract.md)
-(Proposed) for the engine contract, rationale, and migration prerequisites.
-
-**Kill-switch:** set `PANTHEON_DELEGATION=off` (case-insensitive) to disable
-delegation entirely. The switch covers **both** engines — the legacy
-`pantheon_delegate`/read/list tools throw, and the native manager throws too.
+Pantheon delegates exclusively through OpenCode's native `task()` child-session
+engine. The former custom `pantheon_delegate` tool and the V1 delegation engine
+(`delegation.ts`, `delegate-manager.ts` and supporting modules) were removed;
+there is no Pantheon-specific delegation tool surface to configure. See
+[ADR-0011](.pantheon/memory-bank/adr/0011-delegation-engine-contract.md) for the
+historical engine contract.
 
 ## Cost tool backend
 
@@ -172,8 +161,7 @@ script's SHA-256 without regenerating it.
   covering OpenCode V1/V2 side by side — see
   [Sandbox validation](#sandbox-validation-v1v2).
 - Beta2 agent-economy policy: direct native delegation, bounded compaction
-  carry-forward, compact context encoding, and quality floors — see
-  [Beta2 agent economy policy](docs/ws3-token-opt-measurements.md#beta2-agent-economy-policy).
+  carry-forward, compact context encoding, and quality floors.
 - A `--prompts` installer flag is planned for a future release.
 
 ## OpenCode V1/V2 — Dual Version (1.5.0-beta.2)
@@ -186,23 +174,22 @@ per installation; V1 and V2 Pantheon plugins must never be registered together.
 |---|---|---|
 | OpenCode config key | singular `plugin` | plural `plugins` |
 | Pantheon registration | `src/plugin.ts` plus `src/plugins/pantheon-hooks.ts` | `<installed>/src/plugin-v2` directory (`index.ts` re-exports `src/plugin-v2.ts`) |
-| Runtime contract | Legacy Pantheon plugin, including `pantheon_delegate`, read/list tools, event/tool hooks and V1 compaction handling | Full V2 plugin: 9 orchestration tools, 4 event subscriptions, session hooks (`prompt`, `context`), tool hooks (`execute.before`/`after`), plus configuration transforms |
+| Runtime contract | Pantheon V1 plugin: 6 tools (`hashline_edit`, the 3 goal tools, `pantheon_cost`, `pantheon_model`), event/tool hooks and V1 compaction handling | Full V2 plugin: 6 orchestration tools, 4 event subscriptions, session hooks (`prompt`, `context`), tool hooks (`execute.before`/`after`), plus configuration transforms |
 | V1 APIs | Registered | Own tool definitions via `ctx.tool.transform()` — not the V1 plugin path |
 
-The V2 plugin provides 9 orchestration tools (`pantheon_delegate`,
-`pantheon_delegation_read`, `pantheon_delegation_list`, `hashline_edit`,
+The V2 plugin provides 6 orchestration tools (`hashline_edit`,
 `pantheon_goal_create`, `pantheon_goal_get`, `pantheon_goal_update`,
 `pantheon_cost`, `pantheon_model`), 4 event subscriptions (`session.created`,
 `session.idle`, `session.error`, `session.compacted`), session hooks (`prompt`,
 `context`), and tool hooks (`execute.before`, `execute.after`). The only
-unsupported V2 feature is `legacy-hooks` (the V1-specific delegate API surface).
+unsupported V2 feature is `legacy-hooks` (the V1-specific hook surface).
 
 The package exposes both contracts as importable exports: `pantheon-opencode/plugin`
 (V1), `pantheon-opencode/plugin-v2` (V2) and `pantheon-opencode/v2-bridge`
 (optional interop), so a host can load either contract explicitly.
 
 The V1→V2 bridge (`src/pantheon/v2-bridge.ts`) enables optional interop:
-V1 infrastructure singletons (BackgroundJobBoard, DelegationClient, GoalStore,
+V1 infrastructure singletons (BackgroundJobBoard, GoalStore,
 TodoEnforcer, VisionHandler) are passed through V2 `ctx.options`. The bridge is
 optional — V2 works standalone with graceful degradation.
 
@@ -340,8 +327,8 @@ child session returns an empty or missing result. Instead of surfacing a silent
 `completed` with no payload (which confuses the orchestrator), the guard now
 raises an explicit error. This catches the common free-tier failure mode where a
 child session exceeds the uncached-prefill token budget (`BackendAdmissionRejected`)
-and returns nothing. For large payloads, prefer `pantheon_delegate` over native
-`task()` — the delegation layer has better timeout and error handling.
+and returns nothing. Prefer `background=true` dispatches with an explicit
+`task_status(wait=true)` fan-in so large payloads are collected deterministically.
 
 
 ## Documentation

package/README.pt-BR.md

@@ -31,7 +31,7 @@ de planejar o trabalho, avançar, conferir resultados e preservar o contexto
 
 ## Comece em 2 minutos
 
-Requisitos: [OpenCode 1.18.4+](https://opencode.ai/docs/) e Node.js 18+.
+Requisitos: [OpenCode 1.18.4+](https://opencode.ai/docs/) e Node.js 22+.
 
 No projeto em que você quer usar o Pantheon:
 
@@ -130,16 +130,15 @@ registrados juntos.
 |---|---|---|
 | Chave de config do OpenCode | `plugin` singular | `plugins` plural |
 | Registro Pantheon | `src/plugin.ts` mais `src/plugins/pantheon-hooks.ts` | `pantheon-opencode/plugin-v2` (`src/plugin-v2.ts`) |
-| Contrato de runtime | Plugin Pantheon legado, incluindo `pantheon_delegate`, ferramentas read/list, hooks de evento/ferramenta e tratamento de compactação V1 | Plugin V2 completo: 9 ferramentas de orquestração, 4 assinaturas de eventos, session hooks (`prompt`, `context`), tool hooks (`execute.before`/`after`), além de transforms de configuração |
+| Contrato de runtime | Plugin Pantheon V1: 6 ferramentas (`hashline_edit`, as 3 ferramentas de goal, `pantheon_cost`, `pantheon_model`), hooks de evento/ferramenta e tratamento de compactação V1 | Plugin V2 completo: 6 ferramentas de orquestração, 4 assinaturas de eventos, session hooks (`prompt`, `context`), tool hooks (`execute.before`/`after`), além de transforms de configuração |
 | APIs V1 | Registradas | Definições próprias de ferramentas via `ctx.tool.transform()` — não pelo caminho do plugin V1 |
 
-O plugin V2 fornece 9 ferramentas de orquestração (`pantheon_delegate`,
-`pantheon_delegation_read`, `pantheon_delegation_list`, `hashline_edit`,
+O plugin V2 fornece 6 ferramentas de orquestração (`hashline_edit`,
 `pantheon_goal_create`, `pantheon_goal_get`, `pantheon_goal_update`,
 `pantheon_cost`, `pantheon_model`), 4 assinaturas de eventos (`session.created`,
 `session.idle`, `session.error`, `session.compacted`), session hooks (`prompt`,
 `context`) e tool hooks (`execute.before`, `execute.after`). O único recurso V2
-sem suporte é `legacy-hooks` (a superfície de API de delegate específica do V1).
+sem suporte é `legacy-hooks` (a superfície de hooks específica do V1).
 
 O pacote expõe os dois contratos como exports importáveis:
 `pantheon-opencode/plugin` (V1), `pantheon-opencode/plugin-v2` (V2) e
@@ -147,7 +146,7 @@ O pacote expõe os dois contratos como exports importáveis:
 explicitamente o contrato desejado.
 
 A ponte V1→V2 (`src/pantheon/v2-bridge.ts`) habilita interop opcional:
-singletons de infraestrutura V1 (BackgroundJobBoard, DelegationClient,
+singletons de infraestrutura V1 (BackgroundJobBoard,
 GoalStore, TodoEnforcer, VisionHandler) são repassados via `ctx.options` do V2.
 A ponte é opcional — o V2 funciona standalone com degradação graciosa.
 

package/commands/pantheon.md

@@ -9,41 +9,7 @@ agent: zeus
 **When:** Architecture trade-offs, technology selection, security assessments, multi-stakeholder concerns
 **Returns:** Structured synthesis with recommendation, confidence level, resolved divergences
 
-## Dispatch Selection
-
-Choose 2-3 agents based on domain:
-
-| Domain | Specialists |
-|--------|-------------|
-| Architecture | hermes, demeter, themis, athena |
-| Security | themis, hermes, prometheus, nyx |
-| Database | demeter, hermes, prometheus |
-| AI/RAG | hephaestus, nyx |
-| Infrastructure | prometheus, hermes, themis |
-| Frontend/UX | aphrodite, themis, hermes |
-| Observability | nyx, hermes |
-| General | athena, themis, hermes |
-
-Send ALL `task()` calls in a single message. Each must return: Recommendation · Reasoning · Trade-offs · Risks · Confidence.
-
-## Synthesis Structure
-
-After ALL responses arrive, produce EXACTLY this structure:
-
-### 📋 Individual Assessments
-For each specialist: Recommendation, Reasoning, Trade-offs, Risks, Confidence
-
-### ✅ Agreements
-Where 2+ specialists converge
-
-### ⚡ Divergences
-Where they disagree — resolve each one with reasoning
-
-### 🔥 Total Divergence
-If ALL specialists disagree on a point, call this out explicitly
-
-### 🏆 Recommendation
-Decisive conclusion with confidence level
+Dispatch, specialist selection, and synthesis follow the canonical `## Zeus Council Synthesis` protocol (Steps 0–9: precedent fast-path, dispatch, confidence cross-validation, rebuttal, tie-break, Themis audit, persist). Send ALL `task()` calls in a single message; each specialist returns the `## specialist_response` structure from `## Agent Return Format`.
 
 ## Question:
 $ARGUMENTS

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pantheon-opencode",
-  "version": "1.5.0-beta.15",
+  "version": "1.5.0-beta.17",
   "description": "Multi-agent orchestration for OpenCode — 14 specialized agents, TDD, Themis review gates.",
   "type": "module",
   "publishConfig": {

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "pantheon",
   "publisher": "ils15",
-  "version": "1.5.0-beta.15",
+  "version": "1.5.0-beta.17",
   "displayName": "Pantheon",
   "description": "Conductor-Delegate orchestration platform with 14 specialized agents, 21 skills, and OpenCode support.",
   "agents": "./src/agents",

package/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.backends._legacy:_Backend"
 
 [project]
 name = "pantheon"
-version = "1.5.0-beta.15"
+version = "1.5.0-beta.17"
 description = "Multi-agent orchestration framework"
 requires-python = ">=3.11"
 dependencies = []

package/scripts/mcp_persistence_server.py

@@ -1323,7 +1323,7 @@ def build_rehydration_blocks(checkpoint: dict) -> list[str] | None:
     """Build deterministic rehydration blocks from a checkpoint dict.
 
     Pure string templating — no LLM, no embeddings. Mirrors the
-    ``<mission_context>`` convention of delegation-compaction.ts: only a
+    ``<mission_context>`` convention of the compaction-context builder: only a
     non-done goal is re-emitted. Returns None when nothing critical remains.
     """
     if not isinstance(checkpoint, dict) or not checkpoint:

package/src/agents/apollo.md

@@ -12,6 +12,7 @@ permission:
   glob: allow
   webfetch: allow
   edit: deny
+  hashline_edit: deny
   bash: deny
   task:
     "*": deny

package/src/agents/gaia.md

@@ -11,6 +11,7 @@ permission:
   grep: allow
   webfetch: allow
   edit: deny
+  hashline_edit: deny
   bash: deny
   task:
     "*": deny

package/src/agents/zeus.md

@@ -144,33 +144,11 @@ task_status(task_id="ses_xxx", wait=true)
   -> bloqueia ate completar: { state: "completed", task_result: "..." }
 ```
 
-### Pantheon Delegation Tools (plugin) — 3-tool API
+### DELEGATION_RULES (native task API)
 
-O plugin Pantheon adiciona 3 tools de delegacao gerenciada pelo BackgroundJobBoard:
-
-```
-pantheon_delegate({prompt, agent, description?, read_only?})
-  -> cria sessao filha, registra no board, retorna alias: [apo-1]
-pantheon_delegation_read({id: "apo-1"})
-  -> BLOQUEIA ate o job terminar, retorna o report markdown, marca reconciled
-  -> durante a espera, mostra o que o agente esta fazendo: seccao final "## Agent Activity"
-     (amostra as messages do child a cada ~2s; tool calls + args truncados / texto)
-pantheon_delegation_list()
-  -> lista jobs da sessao, com [unread] para jobs terminados nao lidos
-  -> jobs RUNNING mostram "last activity:" (ultima acao visivel do child)
-  -> fail-open: sem suporte a messages, formato atual inalterado
-```
-
-- **Read-only enforcement:** agentes read-only (apollo, gaia — `read_only_agents` no routing.yml) tem `edit`, `write`, `bash`, `task` NEGADOS dentro da sessao delegada (o guard de `tool.execute.before` THROW com mensagem acionavel). Use `read_only: true` no delegate para qualquer agente de investigacao.
-- **Depth-2 hard-enforced:** sessao read-only NAO cria subagentes (`task` bloqueado) — investigacao nunca vira arvore.
-- **Compactacao:** jobs em voo (running + unread terminal) sao injetados no contexto de compactacao via `experimental.session.compacting` — delegacao em andamento nao se perde ao compactar.
-
-### DELEGATION_RULES (plugin path)
-
-1. **NUNCA** polle `pantheon_delegation_list` para checar se um job terminou.
-2. Voce NAO recebe notificacao injetada no chat — politica do usuario: ZERO `task-notification` no transcript. Visibilidade de conclusao: marcador `[unread]` em `pantheon_delegation_list`, `pantheon_delegation_read({id})`, toasts TUI (pantheon-hooks) e carry-forward de compactacao.
-3. Use `pantheon_delegation_read({id})` APENAS para fan-in explicito / recuperacao de resultado sob demanda (bloqueia ate o fim).
-4. `pantheon_delegation_list` e para diagnostico, nao para polling.
+1. Todo dispatch usa `task(background=true, subagent_type=..., prompt=...)`.
+2. Recolha com `task_status(task_id=..., wait=true)` — bloqueia ate o fim, sem polling.
+3. Use `task_status(wait=true)` apenas para fan-in explicito / recuperacao sob demanda.
 
 ### Background (sempre usar)
 - **Apollo, Hermes, Aphrodite, Demeter, Hephaestus, Prometheus**
@@ -302,9 +280,10 @@ vão a idle com todos incompletos. Guards (todos no `src/pantheon/todo-enforcer.
 ## Wave 4 (PR #46): Empty-Result Retry + /cost + Themis Tier
 
 ### Empty-Result Retry (runtime — automatic)
-Empty-response detection (`empty-mode1` / `empty-mode2`) and stuck-agent
-classification are wired at runtime in `delegation-classifier.ts` (consumed by
-`delegation.ts`). No manual retry helper is required.
+Empty-response detection for native `task()` subagent calls is wired at runtime
+in `task-result-guard.ts` (plugin `tool.execute.after` chain): an
+empty/whitespace-only result is converted into an explicit error so a silent
+child failure is never mistaken for success. No manual retry helper is required.
 
 ### /cost — pantheon_cost tool (WIRED no plugin)
 `pantheon_cost({ days?: number })` le o `opencode.db` READ-ONLY usando o backend

package/src/instructions/memory-protocol.instructions.md

@@ -84,7 +84,9 @@ memory_store({
     agreements: ["point1", "point2"],
     divergences: [{"issue": "...", "resolution": "..."}],
     response_rate: "X of Y",
-    themis_audit: "approved|issues"
+    themis_audit: "approved|issues",
+    precedent_used: false,
+    timestamp: "<ISO-8601>"
   },
   metadata: {
     type: "council_decision",
@@ -93,6 +95,7 @@ memory_store({
   }
 })
 ```
+`value` is JSON-serialized before storing (the MCP `memory_store.value` argument is a string).
 
 ### Read Path (Precedent Fast-Path)
 Before dispatching a new council, Zeus runs:
@@ -103,8 +106,8 @@ memory_search(question, top_k=2, namespace="council_decisions")
 Result interpretation:
 | Score | Age | Action |
 |-------|-----|--------|
-| > 0.85 | < 30 days | Return precedent as fast-path answer. Skip council dispatch entirely. |
-| > 0.85 | >= 30 days | Return with warning "Reavaliar se contexto mudou" + proceed with council |
+| > 0.85 | < 30 days | Return precedent verbatim (note "⚠️ Decisão de [data] — reavaliar se contexto mudou") as fast-path answer. Skip council dispatch entirely. |
+| > 0.85 | >= 30 days | Return with warning "Reavaliar se contexto mudou — decisão tem mais de 30 dias" + proceed with council |
 | 0.5 - 0.85 | Any | Include as context for specialists but still dispatch council |
 | < 0.5 | Any | Ignore, proceed with fresh council |
 

package/src/instructions/zeus-anti-stall.instructions.md

@@ -15,7 +15,7 @@ You MUST self-monitor for these stall conditions:
 | Symptom | Detection Rule | Recovery Action |
 |---------|---------------|-----------------|
 | Silent loop | 3+ consecutive turns with no tool call AND no visible progress | Output `[STALL_DETECTED]` and re-read your task definition. If still stuck, escalate to user with: "I appear to be stuck on [task]. Options: (1) retry with different approach, (2) delegate to specialist, (3) simplify scope." |
-| Delegation black hole | Agent dispatched but no response after 2x the timeout from routing.yml | Log the hang, cancel via `cancel_task`, dispatch to fallback agent, report to user |
+| Delegation black hole | Agent dispatched but no response after 2x the timeout from routing.yml | Log the hang, cancel via `cancel_task`, then follow the fallback chain in `## ⏱️ Timeout & Retry Enforcement` |
 | Circular delegation | Same specialist re-dispatched for same task 2+ times without progress | Break cycle: dispatch to different specialist OR escalate to user |
 | Idle after completion | All background tasks completed but no synthesis/next step for 2+ turns | Force synthesis: summarize all completed results and propose next action |
 | Context thrash | Re-reading same files repeatedly without new action | Stop re-reading. State: "Already have context on [file]. Proceeding with [action]." |
@@ -41,9 +41,7 @@ When a delegation fails (timeout, empty response, error):
 
 2. **Retry ONCE** with rephrased prompt — add: "Previous attempt failed with: [error]. Adjusted approach: [what changed]."
 
-3. **If retry also fails** → DO NOT retry a third time blindly. Instead:
-   - Dispatch to fallback agent (from routing.yml)
-   - If no fallback, escalate to user with: "Task [X] failed after retry. Options: (a) simplify, (b) different agent, (c) manual intervention."
+3. **If retry also fails** → do NOT retry blindly; follow the fallback chain and escalation protocol in `## ⏱️ Timeout & Retry Enforcement`.
 
 ## Progress Checkpoint
 

package/src/instructions/zeus-council-synthesis.instructions.md

@@ -85,10 +85,7 @@ sequenceDiagram
 ## Dispatch Sequence (9-Step Protocol)
 
 ### Step 0 — Precedent Fast-Path (Fase 1)
-Before any dispatch: `memory_search(query, top_k=2, namespace="council_decisions")`
-- Score > 0.85 AND age < 30 days → return precedent verbatim with note "⚠️ Decisão de [data] — reavaliar se contexto mudou". SKIP entire dispatch.
-- Score > 0.85 AND age > 30 days → return precedent with ⚠️ "Reavaliar se contexto mudou — decisão tem mais de 30 dias"
-- Else → proceed to Step 0b
+Run the precedent read path defined in `## Memory Protocol > Council Decisions Namespace` (`memory_search(query, top_k=2, namespace="council_decisions")`). If no precedent applies, proceed to Step 0b.
 
 ### Step 0b — Apollo Pre-Scan (Fase 2, --research flag)
 If `/pantheon --research <question>`: dispatch @apollo with 30s timeout. Inject findings as `shared_context` into ALL specialist prompts. Skip if flag absent.
@@ -190,33 +187,11 @@ task(subagent_type: "themis", prompt: "Audit this council synthesis for fidelity
 - If issues → fix each issue before delivering to user
 
 ### Step 9 — Persist & Reconcile (Fase 1)
-```
-memory_store({
-  namespace: "council_decisions",
-  key: "council:<yyyy-mm-dd>:<slug>",
-  value: JSON.stringify({
-    question, specialists, recommendation, confidence,
-    agreements, divergences, precedent_used, timestamp
-  }),
-  metadata: {type: "council_decision", specialist_count: N}
-})
-board.markReconciled("<task-id>")
-```
+Persist the decision using the write path in `## Memory Protocol > Council Decisions Namespace`, then `board.markReconciled("<task-id>")`.
 
 ## Specialist Output Format (Fase 1 — machine-parseable structured fields)
 
-Specialists MUST return these structured fields in their response:
-
-```
-## specialist_response
-**position:** <clear one-sentence position>
-**reasoning:** <2-4 sentences>
-**trade_offs:** <what's gained vs lost>
-**risks:** <what could go wrong>
-**confidence:** High | Medium | Low
-**agreement_signals:** agree: @agent1, @agent2 on [issue] | disagree: @agent3 on [issue]
-**specific_claims:** <count of specific factual claims in response>
-```
+Specialists MUST return the structured `## specialist_response` format (position, reasoning, trade_offs, risks, confidence, agreement_signals, specific_claims) defined in `## Agent Return Format > Council Specialist Response Format`.
 
 ## Domain-to-Specialist Mapping
 

package/src/instructions/zeus-timeout-retry.instructions.md

@@ -126,39 +126,14 @@ ANY NO  → full task (IMPL artifact + Themis review mandatory)
 3. **No Themis dependency** — output doesn't feed into a phase that requires review
 
 ## Subtask Return Format
-Expect a `subtask_summary` response with:
-```
-## subtask_summary
-**files_changed:** [paths]
-**summary:** What was done
-**tests:** ✅ or N/A
-**status:** complete | partial | escalated
-```
+Return the standard `## subtask_summary` defined in `## Agent Return Format` (files_changed, summary, tests, coverage, tokens, status, blockers).
 
 ## Timeout Parcial (Partial Results)
 
-Timeout parcial is ONLY for read-only, independent agents:
-- ✅ @apollo — can return partial file list ("found 7 of 12 files before timeout")
-- ✅ @gaia — can return partial literature findings
-
-- ✅ @talos — can confirm progress if hotfix times out
-- ❌ Never for implementers or reviewers — must complete or fail
-
-When dispatching with partial-OK, set expectation:
-```
-@apollo Search for auth files. Timeout parcial OK — return whatever you have.
-```
+Only agents marked ✅ in the Timeout Behavior table above may return partial results: @apollo (partial file list, e.g. "found 7 of 12 files before timeout"), @gaia (partial literature findings) and @talos (confirm progress if a hotfix times out). Never for implementers or reviewers — they must complete or fail. When dispatching with partial-OK, set the expectation: `@apollo Search for auth files. Timeout parcial OK — return whatever you have.`
 
 ---
 
 # 📊 TIMEOUT TRACKING
 
-Maintain awareness of in-flight delegations:
-
-| Agent | Timeout | Status | Partial OK? |
-|-------|---------|--------|-------------|
-| @apollo | 60s | ✅ complete | ✅ |
-| @hermes | 180s | ⏳ in progress | ❌ |
-| @themis | 120s | ⏳ in progress | ❌ |
-
-Log timeouts to `/memories/session/timeout-log.md` for later analysis.
+Track in-flight delegations against the Timeout Behavior table above. Log timeouts to `/memories/session/timeout-log.md` for later analysis.

package/src/mcp/mcp_persistence_server.py

@@ -1323,7 +1323,7 @@ def build_rehydration_blocks(checkpoint: dict) -> list[str] | None:
     """Build deterministic rehydration blocks from a checkpoint dict.
 
     Pure string templating — no LLM, no embeddings. Mirrors the
-    ``<mission_context>`` convention of delegation-compaction.ts: only a
+    ``<mission_context>`` convention of the compaction-context builder: only a
     non-done goal is re-emitted. Returns None when nothing critical remains.
     """
     if not isinstance(checkpoint, dict) or not checkpoint: