pantheon-opencode 1.6.0-beta.15 → 1.6.0-beta.18

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (39) hide show
  1. package/CHANGELOG.md +52 -1
  2. package/README.md +95 -26
  3. package/README.pt-BR.md +14 -14
  4. package/package.json +3 -3
  5. package/plugin.json +1 -1
  6. package/pyproject.toml +1 -1
  7. package/scripts/_pantheon_paths.py +24 -0
  8. package/scripts/doctor.mjs +7 -2
  9. package/scripts/install-mcp.mjs +1 -1
  10. package/scripts/mcp_persistence.py +1489 -1039
  11. package/scripts/memory_mcp.py +12 -843
  12. package/scripts/test-opencode-v2-sandbox.sh +2 -115
  13. package/skills-lock.json +3 -3
  14. package/src/agents/apollo.md +1 -2
  15. package/src/agents/athena.md +1 -2
  16. package/src/agents/gaia.md +0 -1
  17. package/src/agents/hermes.md +1 -1
  18. package/src/agents/iris.md +0 -1
  19. package/src/agents/mnemosyne.md +3 -2
  20. package/src/agents/zeus.md +1 -1
  21. package/src/mcp/_pantheon_paths.py +24 -0
  22. package/src/mcp/mcp_codemap_module.py +86 -18
  23. package/src/mcp/mcp_persistence.py +1489 -1039
  24. package/src/mcp/memory_mcp.py +101 -57
  25. package/src/pantheon/goal-loop.ts +11 -8
  26. package/src/pantheon/task-result-guard.ts +38 -2
  27. package/src/pantheon/v2-execute-after.ts +117 -20
  28. package/src/pantheon/v2-tools.ts +10 -1
  29. package/src/plugin-v2.ts +6 -4
  30. package/src/plugin.ts +3 -2
  31. package/src/plugins/tui/dist/tui-v2.js +2 -2
  32. package/src/plugins/tui/dist/tui.js +1 -1
  33. package/src/plugins/tui/package-lock.json +2 -2
  34. package/src/plugins/tui/package.json +1 -1
  35. package/src/routing.yml +4 -4
  36. package/src/skills/codemap/SKILL.md +1 -1
  37. package/src/skills/memory-bank/SKILL.md +17 -13
  38. package/src/skills/session-goal/SKILL.md +12 -22
  39. package/scripts/probe-context-rehydrate.mjs +0 -263
package/CHANGELOG.md CHANGED
@@ -18,6 +18,57 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
18
18
 
19
19
  ## ✅ Closed Issues
20
20
 
21
+ ## [v1.6.0-beta.18] - 2026-10-22
22
+
23
+ - **Persistence goal-schema initialization and migration guidance:** a pristine
24
+ project database now starts with both checkpoint and goal schemas; startup
25
+ does not add goal DDL to an existing database. Existing-DB migration is only
26
+ for users who want manual goal tools. When the schema is absent, the goal tools
27
+ themselves return the exact migration command. User-facing guidance covers
28
+ dry-run first, a stopped server, target confirmation, and verified `0600`
29
+ backups.
30
+
31
+ ## [v1.6.0-beta.17] - 2026-10-21
32
+
33
+ - **Persistence MCP reduced to six registered tools:** only `context_save`,
34
+ `context_get`, and the four `goal_*` tools remain exposed; the twelve KV and
35
+ context-management tools were unregistered while internal SQLite KV helpers
36
+ remain for checkpoint storage. Goal tools are Zeus-only because goals are
37
+ session-scoped and cannot be read across sessions, so Athena/Themis cannot
38
+ read Zeus's goal or create one in their own root session.
39
+ - **Phase 7 — Memory search error contract:** `memory_search` now returns a
40
+ typed, sanitized error when the memory store cannot be read instead of an
41
+ empty list; an empty result now means nothing matched. All-stopword queries
42
+ previously fell back to a literal FTS match and now return no results, making
43
+ the behavior uniform with queries whose stopwords are dropped.
44
+ - **Phase 8 — Memory MCP packaging:** `scripts/memory_mcp.py` is now a thin shim
45
+ delegating to canonical `src/mcp/memory_mcp.py`, removing the stale divergent
46
+ copy; the sync test now asserts that their registered tool lists are equal.
47
+
48
+ ## 🆕 What's New
49
+
50
+ - **V1 goal tools soft-deprecated:** `pantheon_goal_create`,
51
+ `pantheon_goal_update`, and `pantheon_goal_get` remain available with
52
+ unchanged behavior, but stored legacy goals are not automatically continued
53
+ in the current build. The durable manual replacement is the Persistence MCP
54
+ `goal_*` surface available in this branch. Tool removal is deferred to a
55
+ future release and requires explicit human approval.
56
+
57
+ ## 🐞 Fixed
58
+
59
+ - **Disabled goal loop does not suppress idle enforcement:** `hasActiveGoal`
60
+ now returns false while the loop is disabled, so stored legacy goals do not
61
+ prevent the todo enforcer from receiving idle events.
62
+ - **Empty child-dispatch result is an explicit error:** an empty result returned by a child dispatch is now surfaced as an error instead of being passed through as a normal result.
63
+
64
+ ## ⚠️ Known Issues
65
+
66
+ - **`pantheon_cost` aggregates by agent and phase:** V1 reports both dimensions; V2 reports the literal phase `unknown`. The shipped tool has no per-session, per-model, per-provider or USD dimension; per-session aggregation exists only in the unpublished benchmark harness.
67
+ - **An empty child result can arrive as a completed call:** the host supplies the placeholder `Subagent completed without a text response.`; Pantheon’s guard replaces the payload with its explicit error text, while the host’s completed status remains unchanged.
68
+ - **A user `opencode.jsonc` can change the effective plugin set:** the host merges `opencode.json` with a sibling `opencode.jsonc` (scalars from `.jsonc` win, arrays are unioned), and Pantheon registers its plugin only in `opencode.json`.
69
+
70
+ ## ✅ Closed Issues
71
+
21
72
  ## [v1.6.0-beta.15] - 2026-10-19
22
73
 
23
74
  ## 🆕 What's New
@@ -1234,7 +1285,7 @@ latência total e wall de F1 segue inconclusivo.
1234
1285
 
1235
1286
  - **Todo continuation enforcer**: auto-continues sessions with incomplete todos on `session.idle` (4 guards: board-running, in-flight, exponential cooldown, max-failures cap) + kill-switch `PANTHEON_TODO_ENFORCER=off`
1236
1287
  - **Hashline hash-anchored edits**: `hashline_edit` tool with sha256-truncated line tags, additive read enhancer, validate-before-write with `>>>` mismatch hints + Did-you-mean suggestions; blocked in read-only sessions
1237
- - **Full-auto goal loop** (opt-in `full_auto.enabled: false`): `pantheon_goal_create/update/get` tools, atomic GoalStore, priority idle dispatcher (goal suppresses enforcer), max 25 continuations
1288
+ - **Full-auto goal loop:** `pantheon_goal_create/update/get` tools, atomic GoalStore, priority idle dispatcher (active goal suppresses enforcer), max 25 continuations. The loop is disabled by the hard-coded plugin defaults; `routing.yml` documents defaults and guards but does not enable it.
1238
1289
  - **Dispatch retry-on-empty**: classifies empty results (mode 1: 0 tokens; mode 2: reasoning without text) with cap-1 automatic retry
1239
1290
  - **Cost tracking**: JSONL ledger + `pantheon_cost` command reading opencode.db (zero-dep, node:sqlite → scripts/cost.mjs fallback)
1240
1291
  - **Themis phase reviews** route to deepseek-v4-flash (pro reserved for final release gate); Athena stays premium (council red-line)
package/README.md CHANGED
@@ -179,8 +179,13 @@ Memory is used selectively: the coordinator searches once only when project
179
179
  history could affect a task, then passes relevant results to specialists. Store
180
180
  one concise, reusable outcome at task completion when it will matter later;
181
181
  routine child summaries and phase updates stay in the current handoff. The
182
- session-checkpoint tools are separate, optional persistence APIs and are not
183
- called automatically by compaction hooks. See [Memory usage](docs/MEMORY.md).
182
+ `pantheon-memory` MCP is the durable SQLite entry store; project files under
183
+ `.pantheon/memory-bank/` are read on demand through `pantheon://memory-bank/{path}`
184
+ and are not auto-loaded. Session-checkpoint tools are separate, optional
185
+ Persistence APIs and are not called automatically by compaction hooks. Global
186
+ and sandbox doctor profiles require `pantheon-memory`, `pantheon-resources`,
187
+ and `pantheon-persistence`; lite mode keeps MCP checks optional. See
188
+ [Memory usage](docs/MEMORY.md).
184
189
 
185
190
  Delegated handoffs may include optional `memory_context` only when useful
186
191
  memory affects the subtask: include safe references and a concise takeaway,
@@ -218,6 +223,26 @@ Both columns of the 1.6.x row are real, and they are not the same claim. Read
218
223
  [the plugin contract](#opencode-v1v2--dual-version-160-beta1) for what each
219
224
  generation actually registers.
220
225
 
226
+ ### Node runtime floor
227
+
228
+ `engines.node` is `>=26.4.0`: Pantheon's own alignment policy with the official
229
+ OpenCode Node build, which CI pins to exactly 26.4.0 — not a claim about the
230
+ host runtime. Below the floor the package still installs, but `postinstall`
231
+ only warns and skips the TUI and config sync, and the CLI stops with an
232
+ explicit version message before any setup write. The `node:sqlite` threshold
233
+ (Node >= 22.5) is a separate, lower capability bound for the optional
234
+ `pantheon_cost` SQLite backend.
235
+
236
+ ### Config registration and the host's config merge
237
+
238
+ Pantheon registers its plugin in `opencode.json`; the installer never writes
239
+ `opencode.jsonc`. The OpenCode V2 host also loads a sibling `opencode.jsonc`
240
+ from the same config directory when one exists, and merges the two files:
241
+ scalars from `.jsonc` win, and arrays are unioned. A `plugin`/`plugins` entry
242
+ in `.jsonc` therefore joins the effective plugin set instead of replacing the
243
+ registration Pantheon wrote. The merge is silent, so a host can load a plugin
244
+ that appears only in `.jsonc`.
245
+
221
246
  ### What "supported on OpenCode 1.X" concretely means
222
247
 
223
248
  On the 1.6 line, an OpenCode 1.X host gets the **V1 plugin**:
@@ -268,6 +293,46 @@ before child creation, and rejects a matrix-valid dispatch from a child. The
268
293
  remaining V2 surface still has unsupported goal tools and registration-only
269
294
  session/compaction hooks, so the 1.6 line is not full V2 feature parity.
270
295
 
296
+ ### Manual goals are Persistence MCP tools, not V2 plugin tools
297
+
298
+ The Persistence MCP exposes exactly six tools: `context_save`, `context_get`,
299
+ `goal_create`, `goal_get`, `goal_update`, and `goal_done`. The KV table remains
300
+ internal checkpoint storage; the former KV management/search and context
301
+ list/statistics/rehydration/summary operations are not registered.
302
+
303
+ The existing `pantheon-persistence` server provides manual `goal_create`,
304
+ `goal_get`, `goal_update`, and `goal_done` tools for the current OpenCode
305
+ session. The four goal tools are granted only to Zeus. Goals are partitioned by OpenCode session ID in the Persistence
306
+ deployment database; the session ID is a correlation key, not authentication.
307
+ In a global install, different projects share this database. The
308
+ supported boundary is OpenCode v2.0.30 local stdio, not independent clients or
309
+ HTTP. Same-user clients that bypass OpenCode, host bypasses, and compromised
310
+ OpenCode configuration are outside the trust model. Athena and Themis do not
311
+ receive `goal_get`: a child session cannot read Zeus's goal, and as root they
312
+ cannot create a goal in their own session because only Zeus has `goal_create`.
313
+ All other agents are also denied. Grant changes come from
314
+ canonical agent frontmatter and take effect through controlled init/restart
315
+ plus effective-permission verification, not promised hot reload.
316
+
317
+ These are manual records only: they do not replace or migrate the V1
318
+ `src/pantheon/goal-store.ts` authority, write to it, or trigger continuation,
319
+ reinjection, an evaluator, loop, board, TUI/RPC, or `ctx.storage`. The V1 JSON
320
+ store at `.pantheon/goals/*.json` is untouched and not imported. The V2 plugin's
321
+ own goal tools remain unsupported.
322
+
323
+ Fresh/pristine Persistence project databases start with both checkpoint and goal
324
+ schemas; startup performs no goal-schema DDL on an existing database containing
325
+ user schema. Users who do not use manual goals need do nothing; only users who
326
+ want the tools on an existing Persistence project DB need the explicit
327
+ human-run migration. If the schema is absent, the goal tools fail closed and
328
+ return the exact `<venv-python> <installed-script> --migrate-goals` command (with
329
+ installation-specific command forms). Skipping migration leaves checkpoint
330
+ tools working and goal tools unavailable, without data loss or corruption.
331
+ Never migrate `global.db` or the V1 JSON goal store. See
332
+ [Persistence migration guidance](docs/persistence-mcp.md#fresh-databases-and-existing-database-migration)
333
+ for target resolution, dry-run confirmation, backups, and the stopped-server
334
+ procedure.
335
+
271
336
  ### Verified against which OpenCode versions
272
337
 
273
338
  | What | Verified against | How |
@@ -430,19 +495,26 @@ per installation; V1 and V2 Pantheon plugins must never be registered together.
430
495
  |---|---|---|
431
496
  | OpenCode config key | singular `plugin` | plural `plugins` |
432
497
  | Pantheon registration | `src/plugin.ts` plus `src/plugins/pantheon-hooks.ts` | `<installed>/src/plugin-v2` directory (`index.ts` re-exports `src/plugin-v2.ts`) |
433
- | 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: 3 orchestration tools plus `vision_describe` when the model catalog is available, 5 event subscriptions, session hooks (`prompt`, `context`), a read-only-enforcing tool `execute.before` hook, plus configuration transforms |
498
+ | 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: 3 unconditional orchestration tools plus up to 2 host-dependent ones (`vision_describe` when the model catalog is available, `pantheon_bounded_read` when the host exposes its permission and session APIs), 5 event subscriptions, session hooks (`prompt`, `context`), a read-only-enforcing tool `execute.before` hook, plus configuration transforms |
434
499
  | V1 APIs | Registered | Own tool definitions via `ctx.tool.transform()` — not the V1 plugin path |
435
500
 
436
- The V2 plugin provides 3 orchestration tools (`hashline_edit`, `pantheon_cost`,
437
- `pantheon_model`), 5 event subscriptions (`session.created`, `session.idle`,
501
+ The V2 plugin provides 3 unconditional orchestration tools (`hashline_edit`,
502
+ `pantheon_cost`, `pantheon_model`) plus up to 2 host-dependent ones —
503
+ `vision_describe` when the host exposes its model catalog, and
504
+ `pantheon_bounded_read` when the host exposes its permission and session APIs
505
+ (root Zeus sessions only, see
506
+ [Bounded workspace reads](#bounded-workspace-reads-f3b)) — 5 event
507
+ subscriptions (`session.created`, `session.idle`,
438
508
  `session.deleted`, `session.error`, `session.compacted`), session hooks
439
509
  (`prompt`, `context`),
440
510
  and a tool `execute.before` hook that enforces read-only sessions. The 3 goal
441
511
  tools are **not**
442
512
  registered on V2: the goal loop needs a `GoalStore`, a `GoalLoopClient` and a
443
513
  `BackgroundJobBoard`, none of which the V2 `PluginContext` exposes, so the gap
444
- is reported as the `goal-tools` unsupported-feature marker. Use the V1
445
- contract if you need the goal loop.
514
+ is reported as the `goal-tools` unsupported-feature marker. The V1 contract
515
+ still registers the deprecated legacy goal tools, but they store/read goals
516
+ without automatically continuing the session in the current build. For durable
517
+ manual goals, use the Persistence MCP `goal_*` surface available in this branch.
446
518
 
447
519
  V2 also registers `vision_describe` when `ctx.model.list()` is available. It
448
520
  checks the live catalog for image input, prefers the paid OpenCode Go
@@ -785,20 +857,14 @@ scripts/test-opencode-v2-sandbox.sh --prepare # tarball + install + init in
785
857
  ~/pantheon-sandbox/start-pantheon.sh # interactive TUI in that isolated beta sandbox
786
858
  scripts/test-opencode-v2-sandbox.sh --run v2 # base validation only
787
859
  scripts/test-opencode-v2-sandbox.sh --prompts # base validation + prompt battery
788
- scripts/test-opencode-v2-sandbox.sh --rehydrate # offline context rehydration/session-summary probe
789
860
  scripts/test-opencode-v2-sandbox.sh --hooks # V2 hook callback canary
790
- scripts/test-opencode-v2-sandbox.sh --rehydrate --hooks # run both canaries
791
861
  scripts/test-opencode-v2-sandbox.sh --reset # wipe the sandbox root
792
862
  ```
793
863
 
794
- Modes are combinable (e.g. `--prepare --run v2 --prompts`). `--rehydrate` runs
795
- offline `context_rehydrate` and `context_session_summary` probes. `--hooks` runs
796
- a V2 hook canary against the sandbox binary to check that hook callbacks fire;
797
- it does not test transform callback effects or prove Pantheon's
798
- `execute.before` security enforcement. With the probe-only `--rehydrate --hooks`
799
- pair (without `--run`, `--prompts`, or `--cost`), the hooks canary still runs if
800
- rehydration fails, and the command returns a failing status afterward. These
801
- are test/sandbox canaries, not proof of Pantheon security enforcement. Binaries
864
+ Modes are combinable (e.g. `--prepare --run v2 --prompts`). `--hooks` runs a V2
865
+ hook canary against the sandbox binary to check that hook callbacks fire; it does
866
+ not test transform callback effects or prove Pantheon's `execute.before` security
867
+ enforcement. These are test/sandbox canaries, not proof of Pantheon security enforcement. Binaries
802
868
  are resolved strictly inside the sandbox npm prefix — a non-prepared sandbox
803
869
  fails fast instead of silently testing the host installation. The sandbox is
804
870
  always built from the checkout this script lives in; it never infers a
@@ -830,8 +896,11 @@ name. Scenario A performs real web research, so its variance is
830
896
  network-dependent and recorded per run.
831
897
 
832
898
  `reportVersion` remains `3`; token usage fields are unchanged and
833
- `tokens.sessionBreakdown` is an optional additive field. When available, it
834
- reports input, output, and input+output total per unique session, plus root and
899
+ `tokens.sessionBreakdown` is an optional additive field. It belongs to the
900
+ benchmark report in the unpublished `bench/` harness, not to the shipped
901
+ `pantheon_cost` tool. That tool aggregates by agent and phase in V1; V2 reports
902
+ the phase as the literal `unknown`. When available, `sessionBreakdown` reports
903
+ input, output, and input+output total per unique session, plus root and
835
904
  descendant subtotals. These are overlapping views of the aggregate, not extra
836
905
  usage; no agent/call/section attribution is inferred. Incomplete token-field
837
906
  coverage or a session without assistant usage makes the breakdown unavailable
@@ -973,14 +1042,14 @@ Env overrides:
973
1042
  Exit codes: `0` no real failures · `1` real failure (see `prompts-report.md`
974
1043
  in the sandbox root) · `2` usage error · `3` sandbox not prepared.
975
1044
 
976
- ### Intentional memory MCP divergence
1045
+ ### Memory MCP source of truth
977
1046
 
978
- `scripts/memory_mcp.py` and `src/mcp/memory_mcp.py` are
979
- intentionally different. The standalone `scripts/` copy keeps the lightweight
980
- `memory_*` contract; the installed `src/mcp/` copy additionally exposes the
981
- optional codemap schema and `code_index`, `code_query`, and `code_neighbors`.
982
- The other shared MCP copies remain identical. Do not overwrite one memory copy
983
- with the other.
1047
+ `src/mcp/memory_mcp.py` is the canonical Memory MCP server and exposes the six
1048
+ `memory_*` tools plus three `code_*` codemap tools. `scripts/memory_mcp.py` is a
1049
+ source-tree compatibility entrypoint that delegates to it. The runtime installer
1050
+ copies the canonical source into the installed scripts directory, while
1051
+ `install-mcp.mjs` prefers that installed copy and falls back to the source-tree
1052
+ entrypoint when running from a checkout.
984
1053
 
985
1054
  ### Task-result guard
986
1055
 
package/README.pt-BR.md CHANGED
@@ -37,6 +37,8 @@ Com a configuração padrão do npm, versões incompatíveis podem gerar um avis
37
37
 
38
38
  Esse requisito do pacote não significa que todo host OpenCode execute Node: o OpenCode V2.0.31 oficial oferece um caminho de runtime Bun e um build Node separado fixado em Node 26.4.0. Não há aqui um requisito mínimo para Bun. O backend SQLite opcional de `pantheon_cost` tem um limite de capacidade distinto (`node:sqlite` requer Node >=22.5), que não reduz o requisito de suporte do pacote.
39
39
 
40
+ O piso `>=26.4.0` é a política de alinhamento do próprio pacote com o build Node oficial do OpenCode, que a CI fixa exatamente em 26.4.0; não é uma afirmação sobre o runtime do host.
41
+
40
42
  No projeto em que você quer usar o Pantheon:
41
43
 
42
44
  ```bash
@@ -79,7 +81,7 @@ verificações repetíveis e passagens claras entre etapas do trabalho.
79
81
 
80
82
  ## Status
81
83
 
82
- Versão operacional neste checkout: **v1.6.0-beta.15** (esta página não afirma publicação). O Pantheon foi feito para OpenCode e depende da
84
+ Versão operacional neste checkout: **v1.6.0-beta.17** (esta página não afirma publicação). O Pantheon foi feito para OpenCode e depende da
83
85
  disponibilidade e da configuração do OpenCode e dos serviços opcionais que você
84
86
  escolher. Veja as [releases](https://github.com/ils15/pantheon-opencode/releases)
85
87
  e o [changelog](CHANGELOG.md) para acompanhar as mudanças publicadas.
@@ -129,12 +131,15 @@ registrados juntos.
129
131
  |---|---|---|
130
132
  | Chave de config do OpenCode | `plugin` singular | `plugins` plural |
131
133
  | Registro Pantheon | `src/plugin.ts` mais `src/plugins/pantheon-hooks.ts` | `pantheon-opencode/plugin-v2` (`src/plugin-v2.ts`) |
132
- | 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: 3 ferramentas de orquestração mais `vision_describe` quando o catálogo de modelos está disponível, 5 assinaturas de eventos, session hooks (`prompt`, `context`), um hook `execute.before` que impõe sessões somente-leitura, além de transforms de configuração |
134
+ | 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: 3 ferramentas de orquestração incondicionais mais até 2 dependentes do host (`vision_describe` quando o catálogo de modelos está disponível, `pantheon_bounded_read` quando o host expõe suas APIs de permissão e sessão), 5 assinaturas de eventos, session hooks (`prompt`, `context`), um hook `execute.before` que impõe sessões somente-leitura, além de transforms de configuração |
133
135
  | APIs V1 | Registradas | Definições próprias de ferramentas via `ctx.tool.transform()` — não pelo caminho do plugin V1 |
134
136
 
135
- O plugin V2 fornece 3 ferramentas de orquestração (`hashline_edit`,
136
- `pantheon_cost`, `pantheon_model`), 4 assinaturas de eventos (`session.created`,
137
- `session.idle`, `session.error`, `session.compacted`), session hooks (`prompt`,
137
+ O plugin V2 fornece 3 ferramentas de orquestração incondicionais
138
+ (`hashline_edit`, `pantheon_cost`, `pantheon_model`) mais até 2 dependentes do
139
+ host — `vision_describe` quando o host expõe seu catálogo de modelos, e
140
+ `pantheon_bounded_read` quando o host expõe suas APIs de permissão e sessão
141
+ (apenas sessões root do Zeus) — 5 assinaturas de eventos (`session.created`,
142
+ `session.idle`, `session.deleted`, `session.error`, `session.compacted`), session hooks (`prompt`,
138
143
  `context`) e um hook de ferramenta `execute.before` que impõe sessões
139
144
  somente-leitura. As 3 ferramentas de goal **não** são
140
145
  registradas no V2: o goal loop precisa de um `GoalStore`, de um
@@ -428,21 +433,16 @@ exclusivo V2, portanto há uma única perna.
428
433
  scripts/test-opencode-v2-sandbox.sh --prepare # tarball + install + init no sandbox
429
434
  scripts/test-opencode-v2-sandbox.sh --run v2 # apenas validação base
430
435
  scripts/test-opencode-v2-sandbox.sh --prompts # validação base + bateria de prompts
431
- scripts/test-opencode-v2-sandbox.sh --rehydrate # sondas offline de rehydration/summary de sessão
432
436
  scripts/test-opencode-v2-sandbox.sh --hooks # canário de callbacks de hooks V2
433
- scripts/test-opencode-v2-sandbox.sh --rehydrate --hooks # executa os dois canários
434
437
  scripts/test-opencode-v2-sandbox.sh --reset # limpa a raiz do sandbox
435
438
  ```
436
439
 
437
- Os modos são combináveis (ex.: `--prepare --run v2 --prompts`). `--rehydrate`
438
- executa sondas offline de `context_rehydrate` e `context_session_summary`.
439
- `--hooks` executa um canário de hooks V2 com o binário do sandbox para verificar
440
+ Os modos são combináveis (ex.: `--prepare --run v2 --prompts`). `--hooks` executa
441
+ um canário de hooks V2 com o binário do sandbox para verificar
440
442
  se os callbacks de hooks são disparados; ele não testa os efeitos dos callbacks
441
443
  de transform nem comprova o enforcement de segurança `execute.before` do
442
- Pantheon. Com o par de sondas `--rehydrate --hooks` (sem `--run`, `--prompts` ou
443
- `--cost`), o canário de hooks ainda é executado se a rehydration falhar, e o
444
- comando retorna falha em seguida. Esses canários de teste/sandbox não são prova
445
- de enforcement de segurança do Pantheon. Os binários são resolvidos estritamente
444
+ Pantheon. Esses canários de teste/sandbox não são prova de enforcement de
445
+ segurança do Pantheon. Os binários são resolvidos estritamente
446
446
  dentro do prefix npm do sandbox — um sandbox não preparado falha rápido em vez
447
447
  de testar silenciosamente a instalação do host.
448
448
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pantheon-opencode",
3
- "version": "1.6.0-beta.15",
3
+ "version": "1.6.0-beta.18",
4
4
  "description": "Multi-agent orchestration for OpenCode — 14 specialized agents, TDD, Themis review gates.",
5
5
  "type": "module",
6
6
  "workspaces": [
@@ -101,9 +101,9 @@
101
101
  "dependencies": {
102
102
  "@clack/prompts": "1.8.1",
103
103
  "@opencode-ai/plugin": "1.18.33",
104
+ "@opencode-ai/sdk": "1.18.33",
104
105
  "js-yaml": "^5.4.2",
105
- "zod": "4.1.8",
106
- "@opencode-ai/sdk": "1.18.33"
106
+ "zod": "4.1.8"
107
107
  },
108
108
  "devDependencies": {
109
109
  "@biomejs/biome": "2.5.14",
package/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "pantheon",
3
3
  "publisher": "ils15",
4
- "version": "1.6.0-beta.15",
4
+ "version": "1.6.0-beta.18",
5
5
  "displayName": "Pantheon",
6
6
  "description": "Conductor-Delegate orchestration platform with 14 specialized agents, 20 skills, and OpenCode support.",
7
7
  "agents": "./src/agents",
package/pyproject.toml CHANGED
@@ -4,7 +4,7 @@ build-backend = "setuptools.backends._legacy:_Backend"
4
4
 
5
5
  [project]
6
6
  name = "pantheon"
7
- version = "1.6.0-beta.15"
7
+ version = "1.6.0-beta.18"
8
8
  description = "Multi-agent orchestration framework"
9
9
  requires-python = ">=3.11"
10
10
  dependencies = []
@@ -72,6 +72,30 @@ def pantheon_project() -> Path | None:
72
72
  return None
73
73
 
74
74
 
75
+ def trusted_project_root() -> Path | None:
76
+ """Return an explicitly host-bound project root, or ``None``.
77
+
78
+ The globally launched Memory MCP commonly runs with its working directory
79
+ set to the installed runtime, not the active project. Therefore this
80
+ security-sensitive lookup deliberately accepts only an absolute
81
+ ``PANTHEON_PROJECT`` binding and never falls back to ``PWD`` or cwd.
82
+ """
83
+ configured_root = os.environ.get("PANTHEON_PROJECT")
84
+ if not configured_root:
85
+ return None
86
+
87
+ candidate = Path(configured_root)
88
+ if not candidate.is_absolute():
89
+ return None
90
+ try:
91
+ root = candidate.resolve(strict=True)
92
+ except (OSError, RuntimeError):
93
+ return None
94
+ if not root.is_dir() or root == Path(root.anchor):
95
+ return None
96
+ return root
97
+
98
+
75
99
  def _is_valid_logical_cwd(logical_cwd: str, physical_cwd: str) -> bool:
76
100
  """Validate a launcher-provided logical cwd without resolving its result.
77
101
 
@@ -333,7 +333,10 @@ function checkMcpConfig(args) {
333
333
  section('B. MCP Configuration')
334
334
 
335
335
  const configs = collectMcpConfigs(args)
336
- const requiredMcpNames = args.profile === 'lite' ? [] : ['pantheon-memory', 'pantheon-resources']
336
+ // This required-server check tests config-entry presence only. It does not
337
+ // verify enabled state, command/transport usability, connectivity, or health.
338
+ const requiredMcpNames =
339
+ args.profile === 'lite' ? [] : ['pantheon-memory', 'pantheon-resources', 'pantheon-persistence']
337
340
 
338
341
  if (configs.length === 0) {
339
342
  if (requiredMcpNames.length > 0) {
@@ -447,7 +450,9 @@ function checkMcpConfig(args) {
447
450
  const configured = new Set(configs.flatMap((cfg) => Object.keys(cfg.data.mcp ?? {})))
448
451
  for (const required of requiredMcpNames) {
449
452
  if (configured.has(required))
450
- pass(`Required MCP "${required}" configured in an available config`)
453
+ pass(
454
+ `Required MCP "${required}" entry is present (presence check only; this check does not verify enabled state, command/transport usability, connectivity, or health)`,
455
+ )
451
456
  else error(`Required MCP "${required}" not configured in any available config`)
452
457
  }
453
458
  }
@@ -259,7 +259,7 @@ export const MCPS = {
259
259
  tier: 1,
260
260
  name: 'Pantheon Persistence',
261
261
  description:
262
- 'Pantheon Persistence MCP Server — key-value store with FTS5 full-text search, TTL-based expiration, and namespace isolation',
262
+ 'Pantheon Persistence MCP Server — operational-state checkpoints via context_save/context_get and four manual session-scoped goal tools',
263
263
  env: [],
264
264
  platforms: {
265
265
  opencode: {