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

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

@@ -36,7 +36,7 @@ sequenceDiagram
     participant T as Themis (Audit + Moderator)
 
     U->>Z: /pantheon [--research] question
-    Z->>M: memory_search(council_decisions)
+    Z->>M: memory_search(query, namespace="council_decisions")
     alt Precedent found (score > 0.85)
         M-->>Z: ⚠️ Cached decision
         Z->>U: Fast-path precedent
@@ -85,7 +85,7 @@ sequenceDiagram
 ## Dispatch Sequence (9-Step Protocol)
 
 ### Step 0 — Precedent Fast-Path (Fase 1)
-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.
+Run the precedent read path defined in `## Memory Protocol > Council Decisions Namespace` (`memory_search(query=question, 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.

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]
+}

package/src/plugin-v2.ts

@@ -5,7 +5,7 @@
  * - 3 self-sufficient tools via V2 tool.transform (hashline_edit,
  *   pantheon_cost, pantheon_model — see ./pantheon/v2-tools.ts; the goal tools
  *   need V1 infrastructure and are absent from this surface)
- * - 4 event subscriptions (session.created, idle, error, compacted)
+ * - 5 event subscriptions (session.created, idle, deleted, error, compacted)
  * - Session hooks (prompt, context, compaction)
  * - A tool `execute.before` hook that ENFORCES read-only sessions: the agent
  *   arrives on the host's event, a read-only agent (apollo/gaia) registers its
@@ -94,6 +94,7 @@ import {
   type V2ContextLike,
 } from './pantheon/v2-bridge.ts'
 import { createV2ToolDefinitions, type V2ToolResult } from './pantheon/v2-tools.ts'
+import { V2_UNSUPPORTED_FEATURE_SEED } from './pantheon/v2-unsupported.mjs'
 import { type HookPayload, runHook } from './plugins/hook-runner.ts'
 
 // ─── Unsupported Features Registry ───────────────────────────────────────
@@ -103,37 +104,18 @@ import { type HookPayload, runHook } from './plugins/hook-runner.ts'
  * the observed host. A listed feature is not necessarily a host-absent API.
  * Additional features are appended during setup when a required API is missing.
  */
-export const V2_UNSUPPORTED_FEATURES: string[] = [
-  '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: the caller/target delegation matrix
-  // needs a session hierarchy seeded from session metadata, and V2 exposes no
-  // seed path for it — SessionHierarchyRegistry.isRoot reports `true` for
-  // unknown sessions while unseeded, which would deny every `task()` call. The
-  // branch is therefore skipped rather than left to deny indiscriminately.
-  // Read-only depth-2 still holds via the blocked-tool list in the guard below,
-  // so this marker records an unenforced matrix, not an unenforced depth limit.
-  'delegation-matrix',
-]
+/**
+ * Live unsupported-feature list: the shared seed plus anything `markUnsupported`
+ * appends while this process talks to a real host.
+ *
+ * The seed lives in `src/pantheon/v2-unsupported.mjs` — a plain-`.mjs` module —
+ * so that the V2 installer and `scripts/doctor.mjs` report the SAME strings
+ * without either of them having to import TypeScript. This array stays a
+ * mutable copy rather than the shared seed itself: `markUnsupported` appends to
+ * it, and the seed must stay frozen. `getUnsupportedFeatures()` still returns
+ * this exact reference.
+ */
+export const V2_UNSUPPORTED_FEATURES: string[] = [...V2_UNSUPPORTED_FEATURE_SEED]
 
 // ─── Constants ───────────────────────────────────────────────────────────
 
@@ -508,6 +490,9 @@ async function handleV2SessionEvent(event: V2SessionEvent): Promise<void> {
     case 'session.idle':
       await onSessionIdle(event)
       break
+    case 'session.deleted':
+      await onSessionDeleted(event)
+      break
     case 'session.error':
       await onSessionError(event)
       break
@@ -522,18 +507,44 @@ async function handleV2SessionEvent(event: V2SessionEvent): Promise<void> {
 /**
  * Session-created handler: currently a no-op on the V2-only surface.
  *
- * V1 seeds session state here (`sessionHierarchy.register(info)` plus the
- * root-session set) from the full session metadata carried by its own event.
- * The V2 event does not carry that metadata, and — more to the point — V1 is a
- * separate plugin instance that is not loaded when only `plugin-v2` is
- * configured. So nothing runs here on a V2-only install. Do not read the bridge
- * check below as coverage: a non-null bridge means a host process that ALSO
- * loaded V1, and V1 does the seeding itself.
+ * V1 seeds session state here — `sessionHierarchy.register(info)` plus the
+ * root-session set — from the full session metadata carried by its own event.
+ *
+ * THE V2 EVENT CARRIES THE SAME METADATA, so this is an UNWIRED seed, not an
+ * impossible one. The V2 SDK types `session.created` as
+ * `{ sessionID: string; info: Session }`, and `Session` declares
+ * `parentID?: string` (`@opencode-ai/sdk` v2 `gen/types.gen.d.ts`) — a superset
+ * of the two fields V1 reads on this exact event. Seeding here would be a copy
+ * of V1's line. An earlier revision of this comment claimed the metadata was
+ * absent from the V2 event; the SDK types refute that, so do not restore it.
+ *
+ * WHAT IS NOT MEASURED, in either direction: whether a live 2.0.22 host
+ * populates `info.parentID` on this event. The tool canary records
+ * `Object.keys(ctx)` from inside the host, not event payloads, so host
+ * population is UNVERIFIED. What is proven is only that the type carries the
+ * field and that no code path here reads it.
+ *
+ * The real asymmetry is the OTHER of V1's two seed sources. Besides this event,
+ * V1 runs a fail-open startup seed from `client.session.list()`
+ * (`seedRootSessionsInBackground`, `src/plugin.ts`) to cover sessions that
+ * predate plugin load, because opencode does not replay `session.created` for
+ * them. V2's `PluginContext` exposes no `client` at all — `options`, `agent`,
+ * `aisdk`, `catalog`, `command`, `integration`, `plugin`, `reference`, `skill`,
+ * and nothing else — so that enumeration has NO V2 EQUIVALENT. Wiring this
+ * handler would recover live sessions only, never resumed ones.
  *
- * The absent hierarchy seed is why the V2 enforcement guard is built without
- * `isRootSession` / `isChildSession`; see `docs/UPGRADING.md`, "Known
- * limitation — V2 enforcement covers the blocked-tool list, not the V1
- * delegation matrix".
+ * And — more to the point — V1 is a separate plugin instance that is not loaded
+ * when only `plugin-v2` is configured, so on a V2-only install nothing seeds
+ * the hierarchy at all. Do not read the bridge check below as coverage: a
+ * non-null bridge means a host process that ALSO loaded V1, and V1 does the
+ * seeding itself.
+ *
+ * The unwired hierarchy seed is ONE of the two reasons the V2 enforcement guard
+ * is built without `isRootSession` / `isChildSession`; the other — and the one
+ * that would actually deny every `task()` call — is the absent
+ * `getSessionAgent`. See the `v2EnforcementGuard` comment below for both, and
+ * `docs/UPGRADING.md`, "Known limitation — V2 enforcement covers the
+ * blocked-tool list, not the V1 delegation matrix".
  */
 async function onSessionCreated(_event: V2SessionEvent): Promise<void> {
   const _bridge = resolveBridge()
@@ -560,6 +571,58 @@ async function onSessionIdle(_event: V2SessionEvent): Promise<void> {
   }
 }
 
+/**
+ * Session-deleted handler: drop the read-only registration.
+ *
+ * `readOnlyRegistry` is a process-wide singleton and the `execute.before` hook
+ * populates it on every delegated `apollo`/`gaia` call. V1 prunes it on
+ * `session.deleted` (`src/plugin.ts`); V2 did not, so on a long-lived host
+ * every finished investigation session stayed registered for the life of the
+ * process — a slow leak, and a stale entry that would keep denying tools if
+ * the id were ever reused.
+ *
+ * This mirrors V1: unregister the session, which drops its agent entry with it
+ * (the registry stores one `ReadOnlyEntry` per session id). V1 also clears a
+ * `sessionAgents` map here; V2 has no such map and needs no equivalent, since
+ * it reads the active agent off the event instead of caching it.
+ *
+ * The id is read from `properties.sessionID` — the field the sibling
+ * `session.idle` handler already uses — falling back to V1's
+ * `properties.info.id`. Both spellings are accepted because the V2 SDK types
+ * `session.deleted` as `{ sessionID, info }` and a miss here is a silent leak,
+ * which is precisely the bug this handler exists to close.
+ *
+ * A payload with NEITHER spelling is fail-open, and unavoidably so: unregistering
+ * is what needs the id, so an id that cannot be resolved cannot be cleaned up
+ * and the entry survives. The docstring used to leave that as a documented
+ * silent branch; it now warns on the way out, because the only other symptom of
+ * a renamed field is a registry that grows for the life of the process.
+ */
+async function onSessionDeleted(event: V2SessionEvent): Promise<void> {
+  const properties = event.properties
+  if (properties === undefined) return
+  const info = properties.info
+  const sessionID =
+    typeof properties.sessionID === 'string'
+      ? properties.sessionID
+      : info !== null && typeof info === 'object'
+        ? (info as { id?: unknown }).id
+        : undefined
+  if (typeof sessionID !== 'string' || sessionID === '') {
+    // Fail-open by necessity, loud by choice: the entry for this session (if
+    // any) cannot be identified, so it stays registered. Same `console.warn`
+    // channel as the event-subscription error above — this module has no
+    // logger, and a diagnostic nobody reads on stderr is still a silent leak.
+    console.warn(
+      '[Pantheon V2] session.deleted carried no session id ' +
+        '(neither properties.sessionID nor properties.info.id); ' +
+        'its read-only registration cannot be pruned and will persist.',
+    )
+    return
+  }
+  readOnlyRegistry.unregister(sessionID)
+}
+
 /**
  * Session-error handler: no V2-side implementation.
  *
@@ -768,15 +831,41 @@ interface V2ToolExecuteBeforeEvent {
  * tool — `hashline_edit` and `pantheon_model` are denied here for exactly the
  * reason they are denied in V1.
  *
- * Deliberately NOT passed `getSessionAgent` / `isRootSession` / `isChildSession`:
- * those drive V1's native-`task()` delegation matrix, which needs a session
- * hierarchy seeded from session metadata. `SessionHierarchyRegistry.isRoot`
- * reports `true` for unknown sessions while unseeded, so passing an unseeded
- * predicate here would DENY every `task()` call in every session. Leaving them
- * out skips that branch (the guard tests `options?.isRootSession !== undefined`).
- * `task` is still denied inside a read-only session via the blocked-tool list,
- * so depth-2 holds for apollo/gaia; the caller/target matrix itself is NOT
- * enforced on V2. That is a known gap, not a covered case.
+ * Deliberately NOT passed `getSessionAgent` / `isRootSession` / `isChildSession`.
+ * There are TWO distinct reasons, and conflating them is what produced a wrong
+ * causal chain here once already — keep them apart:
+ *
+ * 1. MISSING `getSessionAgent` (wiring). This is what would deny every
+ *    `task()` call. V2 learns the active agent from the `execute.before` event
+ *    itself and keeps no session→agent map, so there is no lookup to hand the
+ *    guard. The guard would call `isDelegationAllowed(undefined, target)`,
+ *    which returns `false`, and throw "caller agent is unavailable" — for
+ *    every caller, including Zeus. Note what is NOT happening: an unseeded
+ *    `isRootSession` would *pass* the root gate (`isRoot` reports `true` for an
+ *    unknown session), so the hierarchy is not what denies here.
+ *
+ * 2. UNWIRED HIERARCHY (design). `SessionHierarchyRegistry` is what gates
+ *    exactly two things, and nothing else: the depth-2 child deny
+ *    (`isChildSession`) and the root-session gate (`isRootSession`). Left
+ *    unseeded, `isChild` is `false` for every session, so depth-2 would never
+ *    fire on a genuine child — a hierarchy that cannot tell a child from a root
+ *    is not a trustworthy input to either check.
+ *
+ *    "Unwired", not "impossible": the V2 `session.created` event carries
+ *    `properties.info: Session` including `parentID?`, the same field V1 seeds
+ *    from on the same event, so one line in `onSessionCreated` would seed live
+ *    sessions (see its docstring). What has no V2 equivalent is V1's SECOND
+ *    source, the `client.session.list()` startup seed — V2's `PluginContext`
+ *    exposes no `client`. Whether a live 2.0.22 host populates `info.parentID`
+ *    is UNVERIFIED; no canary reads an event payload. So the correct summary is
+ *    "seeded for nothing", not "unseedable", and the guard's omission is right
+ *    today for the weaker reason that nothing seeds it at all.
+ *
+ * Omitting all three skips the branch wholesale: the guard only enters it when
+ * `options?.isRootSession !== undefined`. `task` is still denied inside a
+ * read-only session via the blocked-tool list, so depth-2 holds for
+ * apollo/gaia; the caller/target matrix itself is NOT enforced on V2. That is
+ * a known gap, not a covered case.
  */
 const v2EnforcementGuard = createEnforcementGuard({
   getReadOnlySessions: () => readOnlyRegistry.sessionIDs(),
@@ -1115,7 +1204,14 @@ export function v2Dispose(): void {
 }
 
 /**
- * Get the current list of unsupported V2 features (for diagnostics).
+ * The current list of unsupported V2 features.
+ *
+ * Read by the installer and by `doctor` (both via the shared seed in
+ * `src/pantheon/v2-unsupported.mjs`) so the markers a user is shown are the
+ * same ones this returns, rather than a hand-copied duplicate.
+ *
+ * This returns the LIVE array: the shared seed plus whatever `markUnsupported`
+ * appended while this process talked to a real host.
  */
 export function getUnsupportedFeatures(): readonly string[] {
   return V2_UNSUPPORTED_FEATURES

package/src/plugins/tui/dist/tui.js

@@ -167,7 +167,7 @@ async function detectVersion(api) {
 			if (ver) return ver;
 		}
 	} catch {}
-	return "1.6.0-beta.4";
+	return "1.6.0-beta.6";
 }
 /**
 * usage-bar — AI subscription usage gauge for the opencode TUI.

package/src/plugins/tui/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "pantheon-tui",
-  "version": "1.6.0-beta.4",
+  "version": "1.6.0-beta.6",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "pantheon-tui",
-      "version": "1.6.0-beta.4",
+      "version": "1.6.0-beta.6",
       "license": "MIT",
       "dependencies": {
         "@opencode-ai/plugin": "1.18.33",

package/src/plugins/tui/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pantheon-tui",
   "type": "module",
-  "version": "1.6.0-beta.4",
+  "version": "1.6.0-beta.6",
   "description": "Pantheon TUI plugin — sidebar (version, preset, sessions, real-time delegations) + AI subscription usage gauges incl. OpenCode Go/Zen dollar limits (vendored, MIT)",
   "license": "MIT",
   "engines": {

package/src/skills/auto-continue/SKILL.md

@@ -163,19 +163,19 @@ Should I now run the migration tests? [waiting]
 Session state is **not** file-based. It lives in **pantheon-persistence** under the
 `checkpoint:<slug>` namespace and is cleaned up automatically by a 4h TTL.
 
-Write state with `context_save(slug, key, value, session_id=...)` and read it back with
-`context_get(slug, "latest", session_id=...)`. Capture `session_id` from the first `context_save`
+Write state with `context_save(slug=slug, key=key, content=JSON.stringify(state), session_id=...)` and read it back with
+`context_get(slug=slug, key="latest", session_id=...)`. Capture `session_id` from the first `context_save`
 of the session and reuse it for the rest of the session, so the `latest` pointer survives
 compaction.
 
 ### Heartbeat Check
-- If `context_get(slug, "heartbeat")` returns a checkin older than 300s, log a stall warning and resume
+- If `context_get(slug=slug, key="heartbeat", session_id=...)` returns a checkin older than 300s, log a stall warning and resume
 - Write a heartbeat after every anti-stall recovery action
 
 ### Checkpoint Rules
 1. Save a checkpoint before **every** delegate dispatch and after every agent returns
 2. Include current phase, turn count, and remaining tasks
-3. On resume: `context_get(slug, "latest")` restores the most recent checkpoint
+3. On resume: `context_get(slug=slug, key="latest", session_id=...)` restores the most recent checkpoint
 
 > Do not create `heartbeat.json`, `checkpoint-<N>.json`, or `session.json` under
 > `.pantheon/deepwork/`. That file-based mechanism is retired — TTL handles cleanup, and reading

package/src/skills/context-compression/SKILL.md

@@ -639,7 +639,7 @@ Allowed fields: file paths, status, pass/fail verdicts, phase names, agent names
 
 ### Layer 2 — Regex pattern scrub (automatic via MCP layer)
 
-**Source of truth:** `scripts/scrub-secrets.py` — the single canonical scrubber. Both `memory_mcp_server.py` and `compress-inline.py` load it via `importlib` (the filename has a hyphen and cannot be `import`ed normally). Do NOT maintain a separate inline pattern list.
+**Source of truth:** `scripts/scrub-secrets.py` — the single canonical scrubber. Both `memory_mcp.py` and `compress-inline.py` load it via `importlib` (the filename has a hyphen and cannot be `import`ed normally). Do NOT maintain a separate inline pattern list.
 
 **Real signature:**
 

package/opencode.json

@@ -1,58 +0,0 @@
-{
-  "$schema": "https://opencode.ai/config.json",
-  "provider": {
-    "opencode-go": {
-      "models": {
-        "mimo-v2.5": {
-          "attachment": true,
-          "modalities": { "input": ["text", "image"] }
-        }
-      }
-    }
-  },
-  "default_agent": "zeus",
-  "plugins": ["src/plugin-v2"],
-  "experimental": {
-    "subagent_depth": 2
-  },
-  "permission": {
-    "skill": {
-      "*": "allow"
-    },
-    "websearch": "deny",
-    "bash": {
-      "git *": "allow",
-      "npm *": "allow",
-      "npx *": "allow",
-      "pytest *": "allow",
-      "ruff *": "allow",
-      "pip *": "allow",
-      "python3 *": "allow"
-    }
-  },
-  "mcp": {
-    "bifrost": {
-      "type": "remote",
-      "url": "https://llm.ofertachina.cloud/mcp",
-      "enabled": true
-    }
-  },
-  "agent": {
-    "talos": {
-      "permission": {
-        "edit": {
-          "*": "allow",
-          "**/migrations/**": "deny",
-          "**/alembic/**": "deny",
-          "**/models/**": "deny",
-          "**/auth/**": "deny",
-          "**/*.sql": "deny"
-        },
-        "bash": {
-          "*": "allow",
-          "alembic *": "deny"
-        }
-      }
-    }
-  }
-}