pantheon-opencode 1.6.0-beta.4 → 1.6.0-beta.5

package/scripts/sync-artifacts.mjs

@@ -31,13 +31,13 @@ import {
 
 /** Canonical MCP script sources — mirrors installOpenCode phase 2.10. */
 const MCP_SCRIPTS = {
-  'mcp_resources_server.py': () => join(ROOT, 'src', 'mcp', 'mcp_resources_server.py'),
-  'code_mode_server.py': () => join(ROOT, 'src', 'mcp', 'code_mode_server.py'),
-  'memory_mcp_server.py': () => join(ROOT, 'src', 'mcp', 'memory_mcp_server.py'),
-  'mcp_persistence_server.py': () => join(ROOT, 'src', 'mcp', 'mcp_persistence_server.py'),
+  'mcp_resources.py': () => join(ROOT, 'src', 'mcp', 'mcp_resources.py'),
+  'code_mode.py': () => join(ROOT, 'src', 'mcp', 'code_mode.py'),
+  'memory_mcp.py': () => join(ROOT, 'src', 'mcp', 'memory_mcp.py'),
+  'mcp_persistence.py': () => join(ROOT, 'src', 'mcp', 'mcp_persistence.py'),
   '_pantheon_paths.py': () => join(ROOT, 'src', 'mcp', '_pantheon_paths.py'),
   'mcp_codemap_module.py': () => join(ROOT, 'src', 'mcp', 'mcp_codemap_module.py'),
-  'pantheon_vision_server.py': () => join(ROOT, 'src', 'mcp', 'pantheon_vision_server.py'),
+  'pantheon_vision.py': () => join(ROOT, 'src', 'mcp', 'pantheon_vision.py'),
   'eval_store.py': () => join(ROOT, 'src', 'mcp', 'eval_store.py'),
   'scrub-secrets.py': () => join(ROOT, 'scripts', 'scrub-secrets.py'),
 }

package/scripts/test-opencode-v2-sandbox.sh

@@ -241,11 +241,11 @@ try:
 except OSError:
     raise SystemExit(1)
 expected = {
-    "code_mode_server.py",
-    "memory_mcp_server.py",
-    "mcp_persistence_server.py",
-    "mcp_resources_server.py",
-    "pantheon_vision_server.py",
+    "code_mode.py",
+    "memory_mcp.py",
+    "mcp_persistence.py",
+    "mcp_resources.py",
+    "pantheon_vision.py",
 }
 pattern = re.compile(
     r"spawning process \{\s*"
@@ -515,11 +515,11 @@ try:
 except OSError:
     raise SystemExit(1)
 expected = {
-    "code_mode_server.py",
-    "memory_mcp_server.py",
-    "mcp_persistence_server.py",
-    "mcp_resources_server.py",
-    "pantheon_vision_server.py",
+    "code_mode.py",
+    "memory_mcp.py",
+    "mcp_persistence.py",
+    "mcp_resources.py",
+    "pantheon_vision.py",
 }
 pattern = re.compile(
     r"spawning process \{\s*"
@@ -642,11 +642,11 @@ config_path = Path(os.environ["CONFIG_PATH"])
 runtime_dir = os.environ["RUNTIME_DIR"]
 python_bin = os.environ["MCP_PYTHON"]
 managed = {
-    "pantheon-code-mode": "code_mode_server.py",
-    "pantheon-memory": "memory_mcp_server.py",
-    "pantheon-persistence": "mcp_persistence_server.py",
-    "pantheon-resources": "mcp_resources_server.py",
-    "pantheon-vision": "pantheon_vision_server.py",
+    "pantheon-code-mode": "code_mode.py",
+    "pantheon-memory": "memory_mcp.py",
+    "pantheon-persistence": "mcp_persistence.py",
+    "pantheon-resources": "mcp_resources.py",
+    "pantheon-vision": "pantheon_vision.py",
 }
 try:
     config = json.loads(config_path.read_text(encoding="utf-8"))
@@ -829,7 +829,7 @@ else
 fi
 
 echo "--- Gate (b): pantheon://agents CONTENT check ---"
-RESOURCES_SRV="$PANTHEON_GLOBAL/scripts/mcp_resources_server.py"
+RESOURCES_SRV="$PANTHEON_GLOBAL/scripts/mcp_resources.py"
 if [ ! -f "$RESOURCES_SRV" ]; then
   record_status "pantheon://agents resource" "FAIL" "resources server not found at $RESOURCES_SRV"
 else
@@ -1013,11 +1013,11 @@ config_path = Path(os.environ["CONFIG_PATH"])
 runtime_dir = os.environ["RUNTIME_DIR"]
 python_bin = os.environ["MCP_PYTHON"]
 managed = {
-    "pantheon-code-mode": "code_mode_server.py",
-    "pantheon-memory": "memory_mcp_server.py",
-    "pantheon-persistence": "mcp_persistence_server.py",
-    "pantheon-resources": "mcp_resources_server.py",
-    "pantheon-vision": "pantheon_vision_server.py",
+    "pantheon-code-mode": "code_mode.py",
+    "pantheon-memory": "memory_mcp.py",
+    "pantheon-persistence": "mcp_persistence.py",
+    "pantheon-resources": "mcp_resources.py",
+    "pantheon-vision": "pantheon_vision.py",
 }
 
 try:

package/skills-lock.json

@@ -5,7 +5,7 @@
   "src/skills/clonedeps/SKILL.md": "3e0b43cf96da98c83699dc48db3fd58fbfda84b9022bb70d3747875c81c3e124",
   "src/skills/code-review-checklist/SKILL.md": "0e59367c65ef4608db80a0674279f32cfc3f67dca7236f233b61a47fe506579f",
   "src/skills/codemap/SKILL.md": "87af5271e1576e154cadff313eab16264b726e43d094520736b7a5b03b409a4a",
-  "src/skills/context-compression/SKILL.md": "ebc721c715c1fa20e4ebf5177007fde94e001540b16cef4316393a665633c16f",
+  "src/skills/context-compression/SKILL.md": "9c65c132beb0dc7bd20335cfd7f41c589f5168a72dcf5d51740bc66f2865e027",
   "src/skills/git-workflow-and-versioning/SKILL.md": "685a94041f1b4ce2a430301f517b89102055696267c369a7e8fb191606659276",
   "src/skills/incremental-implementation/SKILL.md": "7065ddb45da3c6b6751de07f290e92e6cb072e949a2e3aaae13ee7762f0a70fc",
   "src/skills/loop-engineering/SKILL.md": "f804e545821b9cca8fe0ec517307ed902446f28c2ca8ff9194c0f987cf7229e3",

package/src/agents/apollo.md

@@ -38,7 +38,10 @@ mcp_tools:
 - Generate structured summaries (not raw dumps)
 
 ### 2. External Research
-- Web search via bifrost MCP tools for documentation, blog posts, GitHub repos
+- Web search through whatever web-search MCP the USER has configured — Pantheon
+  bundles none and does not assume one. If no search tool is available, skip
+  external search and say so; never present an unverified recollection as a
+  citation.
 - Context7 for library documentation
 - Read URLs with webfetch for known resource URLs
 
@@ -50,7 +53,9 @@ mcp_tools:
 ##  TOOLS NOT AVAILABLE
 - bash - forbidden (cannot run commands)
 - edit - forbidden (read-only agent)
-- bifrost - use bifrost MCP tools for search
+- Web search by default - no search MCP is bundled or pre-configured. Use one
+  ONLY if the user's own config exposes it; otherwise state that external search
+  was unavailable instead of improvising.
 
 ## MCP Security
 - Never embed credentials in URLs (grep for token=, key=, secret=)

package/src/agents/zeus.md

@@ -284,7 +284,35 @@ 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)
+### /cost — pantheon_cost tool (disponivel com o version gate corrigido)
+`pantheon_cost` volta a existir assim que o version gate corrigido estiver
+instalado **e após o usuário re-rodar `init`**: em host 2.x, `auto` resolve
+para `v2` e registra o entry de diretorio `src/plugin-v2`, que expoe
+exatamente 3 tools — `hashline_edit`, `pantheon_cost` e `pantheon_model`
+(V2 nao registra as 3 goal tools; ver `docs/INSTALLATION.md` ->
+"OpenCode V1/V2 — contrato de plugin").
+**Caveat**: a tool so reaparece para quem re-rodar `init` depois do fix. O
+`postinstall` nao re-executa `init`, entao ate la o config existente continua
+resolvendo para V1 e a tool segue ausente — nesse estado, tratar `/cost` como
+indisponivel.
+
+Causa raiz como era na tag `1.6.0-beta.4` (registro para quem ainda tem um
+install quebrado): o host `opencode v2.0.22` rejeita caminhos de arquivo `.ts` nos
+arrays de plugin do config (recusa `configured plugin path must be a directory`,
+medida em runtime nesse host; o repo so registra a parafrase `must be a
+directory`), e a selecao de geracao caia sempre em V1 — a geracao V1 escreve
+entradas `.ts` sob a chave singular `plugin` (`config.plugin`, o bloco de merge
+em `scripts/install/opencode.mjs`) e o host descarta todas, logo nenhum
+modulo Pantheon entra no processo Node. **O que mudou**: `resolveOpenCodeVersion`
+agora tem default `'auto'` nos dois call sites e no proprio signature, e `auto`
+consulta o host. Precedencia `auto`: flag explicito > `OPENCODE_VERSION` >
+basename `opencode2` > probe `--version` do host (major >= 2 => v2) > soft-fail
+para V1 com warning visivel. Precedencia e criterios do probe estao em
+`docs/INSTALLATION.md` -> "OpenCode V1/V2 — contrato de plugin".
+
+Comportamento da tool — **NAO VERIFICADO em runtime**: em 1.6.0-beta.4 o modulo
+(`src/pantheon/cost-command.ts`) nunca era carregado no processo, e o fix nao foi
+exercitado end-to-end, entao este descritivo permanece nao verificado.
 `pantheon_cost({ days?: number })` le o `opencode.db` READ-ONLY usando o backend
 unico `node:sqlite`; se indisponivel, retorna `UNSUPPORTED`, sem fallback. Devolve tabela markdown de custo + tokens por
 agente nos ultimos N dias (default 7). Uso: quando Nyx pedir visibilidade de

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

@@ -58,8 +58,14 @@ Para otimizar decisoes de delegacao e reduzir gasto de tokens:
 2. Se score > 0.85 → reutiliza agente + background_mode do cache
 3. Se score ≤ 0.85 → aplica regras estaticas e memory_store() com:
    - key: deleg:<task_type>
-   - value: {agent, background, pattern}
-   - metadata: {type: "decision", score: N}
+   - value: JSON.stringify({agent, background, pattern})
+   - metadata: JSON.stringify({type: "decision", score: N})
+
+   `value` E `metadata` sao JSON-encoded strings — o runtime exige que o
+   chamador serialize os dois. Objeto cru em `metadata` e rejeitado pelo
+   `BeforeValidator` do servidor com `metadata must be a JSON object encoded
+   as a string (got object). json.dumps it first. Example: metadata='{"type":
+   "decision", "score": 0.9}'`.
 
 4. **kv_store("deleg:<pattern>", ...)** para padroes recorrentes de delegacao
 5. **kv_get("deleg:<pattern>")** para reusar decisoes ja tomadas
@@ -88,14 +94,19 @@ memory_store({
     precedent_used: false,
     timestamp: "<ISO-8601>"
   },
-  metadata: {
+  metadata: JSON.stringify({
     type: "council_decision",
     specialist_count: N,
     model_tier_used: "premium|default|fast"
-  }
+  })
 })
 ```
 `value` is JSON-serialized before storing (the MCP `memory_store.value` argument is a string).
+`metadata` works the same way — it is a JSON object encoded as a **string**, so pass
+`JSON.stringify({...})`. A raw object is rejected with `metadata must be a JSON object
+encoded as a string (got object). json.dumps it first. Example: metadata='{"type":
+"decision", "score": 0.9}'` (enforced by a `BeforeValidator` in
+`memory_mcp.py`). **Both `value` and `metadata` must be serialized by the caller.**
 
 ### Read Path (Precedent Fast-Path)
 Before dispatching a new council, Zeus runs:

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

@@ -66,9 +66,17 @@ No file I/O, no checkpoint_session.py — TTL (4h) handles cleanup automatically
 Before ANY delegate dispatch, save a checkpoint:
 ```
 context_save(slug, "phase:N", json({
-  "phase": N, "turn_count": N, "agent": "...", "summary": "..."
+  "phase": {"current": N, "total": M, "name": "..."},
+  "turn_count": N, "agent": "...", "summary": "..."
 }), session_id=SESSION_ID)
 ```
+**`content.phase` must be an OBJECT, not a bare number.** `{"phase": 1}` is rejected with
+`context_save: content.phase must be an object (got number)`. The server reads `current`
+and `total` (non-negative ints) and `name` (string, max 256 **bytes** — the guard
+measures `len(value.encode())`, so multi-byte characters count as more than one). That
+set is not closed: any other key inside `phase` is accepted and ignored, never an
+error. The `"phase:N"` slot KEY above is unrelated to `content.phase` and stays a plain
+string.
 All checkpoints auto-expire after 4h (TTL=14400).
 
 ### Gatilho de Pré-Compactação (Anti-perda de estado)

package/src/mcp/{code_mode_server.py → code_mode.py}

@@ -5,12 +5,12 @@ Provides a confined execution environment for orchestration scripts
 via MCP tools and resources.
 
 Usage:
-    python scripts/code_mode_server.py
+    python scripts/code_mode.py
 
 Or via MCP client (stdio transport):
     pantheon-code-mode:
         command: python
-        args: ["scripts/code_mode_server.py"]
+        args: ["scripts/code_mode.py"]
 """
 
 from __future__ import annotations

package/src/mcp/eval_store.py

@@ -2,7 +2,7 @@
 """Plugin eval certification storage — ``plugin_eval`` memory namespace.
 
 Thin stdlib-only wrapper around the memory SQLite DB (same schema as
-``src/mcp/memory_mcp_server.py``) for plugin-eval certification results.
+``src/mcp/memory_mcp.py``) for plugin-eval certification results.
 
 Namespace: ``plugin_eval``
 Key format: ``eval:<name>:<date>``  (e.g. ``eval:tdd-with-agents:2026-08-21``)
@@ -30,7 +30,7 @@ from typing import Any
 
 NAMESPACE = "plugin_eval"
 
-# Minimal schema — matches memory_mcp_server.SCHEMA_SQL for the memories
+# Minimal schema — matches memory_mcp.SCHEMA_SQL for the memories
 # table (vec/FTS tables are initialized by the memory MCP server on first
 # run; eval entries remain readable via list/recall regardless).
 _SCHEMA_SQL = """

package/src/mcp/{mcp_persistence_server.py → mcp_persistence.py}

@@ -5,7 +5,7 @@ Key-Value store with FTS5 full-text search, TTL-based expiration,
 and namespace isolation. Uses SQLite with zero external dependencies.
 
 Usage:
-    python scripts/mcp_persistence_server.py
+    python scripts/mcp_persistence.py
 """
 
 from __future__ import annotations

package/{scripts/mcp_resources_server.py → src/mcp/mcp_resources.py}

@@ -7,7 +7,7 @@ Provides MCP resources for the Pantheon agent framework:
   plans/status, memory-bank files
 
 Usage:
-    python scripts/mcp_resources_server.py
+    python scripts/mcp_resources.py
 """
 
 from __future__ import annotations

package/src/mcp/{memory_mcp_server.py → memory_mcp.py}

@@ -19,7 +19,7 @@ Tools:
     memory_stats   — DB statistics
 
 Usage:
-    python scripts/memory_mcp_server.py
+    python scripts/memory_mcp.py
 """
 
 from __future__ import annotations

package/src/pantheon/v2-unsupported.d.mts

@@ -0,0 +1,11 @@
+/**
+ * Type declarations for v2-unsupported.mjs (the V2 feature-reduction seed).
+ * Consumed by src/plugin-v2.ts via `import ... from './pantheon/v2-unsupported.mjs'`,
+ * and by the plain-`.mjs` install/health scripts at runtime.
+ */
+
+/** Statically-known V2 feature reductions, in report order. */
+export declare const V2_UNSUPPORTED_FEATURE_SEED: readonly string[]
+
+/** A fresh, mutable copy of the seed, so a reporter cannot mutate the shared list. */
+export declare function listV2UnsupportedFeatures(): string[]

package/src/pantheon/v2-unsupported.mjs

@@ -0,0 +1,113 @@
+#!/usr/bin/env node
+/**
+ * v2-unsupported.mjs — the SEED of V2 feature reductions, in plain ESM.
+ *
+ * WHY A SEPARATE PLAIN-`.mjs` MODULE: these strings must be readable by three
+ * very different consumers, and only one of them can import TypeScript.
+ *
+ *   - `src/plugin-v2.ts` (TypeScript) — owns the LIVE list, appending to it at
+ *     runtime via `markUnsupported()` when a host API turns out to be missing,
+ *     and exposes it through `getUnsupportedFeatures()`.
+ *   - `scripts/install/opencode.mjs` — reports the reduction at install time
+ *     for a V2-generation install.
+ *   - `scripts/doctor.mjs` — reports it in the health gate.
+ *
+ * The scripts are plain Node ESM and must stay that way, and `.mjs` is a
+ * REPO-WIDE INVARIANT rather than a judgement about Node: `tsx` is a
+ * devDependency only, and no plain-Node script in `scripts/` or `bin/` imports
+ * a `.ts` module — every `.ts` path there is a string to copy, stat or read as
+ * text (`scripts/install/opencode.mjs`, `scripts/probe-pantheon-cost.mjs`,
+ * `scripts/package-evidence.mjs`, `scripts/check-plugin-v2-coverage.mjs`).
+ * So a `.mjs` import is the only form all three consumers can share, and it
+ * matches the existing `src/pantheon/presets.mjs` + `.d.mts` precedent.
+ *
+ * NOT the reason: type-stripping. `package.json#engines` admits
+ * `^22.22.2 || ^24.15.0 || >=26.0.0`, every admitted version already defaults to
+ * unflagged type-stripping (it landed in 22.18.0), so that argument would not
+ * have held on any admitted version. The live hazard is that `engines` is not
+ * ENFORCED: a Node 20 user can run `doctor` and would get no type-stripping,
+ * which is an argument for a runtime version check, not for this file's shape.
+ *
+ * The SEED is the statically-known half of `getUnsupportedFeatures()`: what a
+ * migrating user loses by choosing the V2 contract, knowable with no host at
+ * all. Runtime-appended entries (`tool-transform`, `event-stream`, …) are
+ * observations about one live host and are deliberately NOT seeded here — they
+ * are not known until the plugin runs against a real V2 host.
+ *
+ * ONE SOURCE OF TRUTH: install and doctor both read the seed from here, so the
+ * two cannot drift apart, and what they report IS what this file lists. Note the
+ * scope of that claim: it holds between the SEED and the two reporters. The
+ * LIVE list `getUnsupportedFeatures()` returns is this seed PLUS markers appended
+ * at runtime (`tool-transform`, `event-stream`, …), so it is a superset and the
+ * two are expected to differ there. Do not copy these strings into a script;
+ * import them.
+ *
+ * @module v2-unsupported
+ */
+
+/**
+ * Statically-known V2 feature reductions, in the order a reader should meet
+ * them. Frozen: `plugin-v2.ts` copies it into its own mutable live array, and
+ * every other consumer goes through {@link listV2UnsupportedFeatures}.
+ *
+ * @type {readonly string[]}
+ */
+export const V2_UNSUPPORTED_FEATURE_SEED = Object.freeze([
+  'legacy-hooks',
+  // `ctx.catalog` is the one domain a live 2.0.22 host does NOT have: it is
+  // absent from `Object.keys(ctx)`, measured in
+  // tests/canary/plugin-v2-tool-canary.test.mjs. (`catalog` IS in the 1.18.33
+  // SDK's PluginContext, so the SDK types it and the host does not provide it.)
+  'catalog-transform',
+  // Adapter support, NOT host availability: 2.0.22 exposes ctx.integration and
+  // ctx.skill with callable transforms, and Pantheon deliberately registers
+  // neither. These entries record what this plugin does not implement.
+  'integration-transform',
+  // The inspected SkillEditor shape has no `source()` helper — i.e. no
+  // `SkillEditor.source()` — for adding a directory source. This is narrower
+  // than (and distinct from) ctx.skill's host availability or callable
+  // transform, which a live 2.0.22 host does provide.
+  'skill-transform',
+  // Adapter limitation, not a host gap: the goal loop needs a GoalStore, a
+  // GoalLoopClient and a BackgroundJobBoard, none of which the V2
+  // PluginContext exposes, and the V1 bridge resolves to null outside V1.
+  // pantheon_goal_create/get/update are therefore absent from the V2 surface
+  // rather than registered as non-functional placeholders.
+  'goal-tools',
+  // Adapter limitation, not a host gap — TWO separate reasons, which are easy
+  // to conflate and were once stated wrongly (see the v2EnforcementGuard
+  // comment in src/plugin-v2.ts for the long form):
+  //   - MISSING WIRING: V2 keeps no session→agent map (the host puts the agent
+  //     on the execute.before event), so there is no `getSessionAgent` to pass.
+  //     The guard would then call isDelegationAllowed(undefined, target) → false
+  //     and throw "caller agent is unavailable" on EVERY task() call.
+  //   - UNWIRED HIERARCHY: V2 seeds no session→parent map anywhere, and an
+  //     unseeded SessionHierarchyRegistry gates exactly two things — the depth-2
+  //     child deny and the root-session gate. Unseeded, isChild is always false,
+  //     so neither can be trusted. UNWIRED, not impossible: the V2
+  //     `session.created` event carries `properties.info: Session` with
+  //     `parentID?`, the same field V1 seeds from on the same event, and one
+  //     line in onSessionCreated would seed live sessions. V1's OTHER source —
+  //     the client.session.list() startup seed for sessions predating plugin
+  //     load — has no V2 equivalent at all, because V2's PluginContext exposes
+  //     no `client`. Whether a live 2.0.22 host populates info.parentID on that
+  //     event is UNVERIFIED: the canary records Object.keys(ctx), not payloads.
+  // Note the hierarchy is NOT what would deny: isRoot reports `true` for an
+  // unknown session while unseeded, which PASSES the root gate.
+  // Read-only depth-2 still holds via the blocked-tool list in the guard, so
+  // this marker records an unenforced matrix, not an unenforced depth limit.
+  'delegation-matrix',
+])
+
+/**
+ * A fresh, mutable copy of the seed.
+ *
+ * Callers get a copy so a reporter that sorts, filters or appends cannot reach
+ * back into the shared list — this is what makes "both surfaces report the same
+ * strings" a structural property rather than a convention.
+ *
+ * @returns {string[]}
+ */
+export function listV2UnsupportedFeatures() {
+  return [...V2_UNSUPPORTED_FEATURE_SEED]
+}