pantheon-opencode 1.6.0-beta.11 → 1.6.0-beta.12

package/AGENTS.global.md

@@ -1,7 +1,7 @@
 <!-- pantheon:generated:begin — Pantheon-managed region; regenerated on install/upgrade, never edit inside -->
 <!-- Generated by scripts/build-agents-md.mjs — do not edit directly. -->
 <!-- Source of truth: src/instructions/*.instructions.md + the static sections in this script. -->
-<!-- pantheon:agents-md v2 artifact=global generated-at=2026-10-15T14:32:32-03:00 sha=66bf918 -->
+<!-- pantheon:agents-md v2 artifact=global generated-at=2026-10-16T15:32:02-03:00 sha=2cda37c -->
 
 # Pantheon Agent System — OpenCode
 
@@ -140,8 +140,8 @@ These rules apply to all agents; each agent file may add domain-specific rules.
 - Use a targeted query (`top_k=2`); do not search the whole prompt by default. Missing or irrelevant results never block current work.
 
 ### Persistence
-- A memory write is optional and conditional on a write tool being exposed and permitted in the active session. Search permission does not imply write permission; in the reported Beta 10 Zeus root, `memory_store` is not exposed/granted.
-- Store at most one concise, reusable top-level result; never persist routine child summaries, phase updates, test logs, or temporary state. Confirm a successful write before claiming persistence.
+- Tool grants vary by agent/runtime. Zeus's installed allowlist has `memory_search` and temporary `context_save`/`context_get` checkpoints, but no durable writes; Mnemosyne's includes `memory_store` and other durable-memory tools. Use only tools exposed and permitted in the active session.
+- Store at most one concise, reusable top-level result; never persist routine child summaries, phase updates, test logs, or temporary state. Confirm a successful write before claiming persistence. Never store secrets, credentials, or tokens. `memory_store` stores submitted values and metadata without guaranteed redaction; omit sensitive content or redact it before storage.
 - If no write tool is available or the write did not succeed, say that the information was not persisted. Do not imply automatic memory storage or recovery. Add ADRs to the memory bank only when explicitly requested.
 
 ### Relevance and permanent records

package/AGENTS.md

@@ -1,7 +1,7 @@
 <!-- pantheon:generated:begin — Pantheon-managed region; regenerated on install/upgrade, never edit inside -->
 <!-- Generated by scripts/build-agents-md.mjs — do not edit directly. -->
 <!-- Source of truth: the static project sections in scripts/build-agents-md.mjs. -->
-<!-- pantheon:agents-md v2 artifact=project generated-at=2026-10-15T14:32:32-03:00 sha=66bf918 -->
+<!-- pantheon:agents-md v2 artifact=project generated-at=2026-10-16T15:32:02-03:00 sha=2cda37c -->
 
 # Pantheon — Repository Setup
 

package/CHANGELOG.md

@@ -18,6 +18,28 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## ✅ Closed Issues
 
+## [v1.6.0-beta.12] - 2026-10-17
+
+## 🆕 What's New
+
+- **Raise the Node.js support floor to 26.4.0** for the package, CLI, installer,
+  and Node-based tooling. This release drops Node 22, Node 24, and Node
+  26.0–26.3; the npm `beta` dist-tag remains the intended publication channel.
+- **Clarify runtime boundaries:** this package requirement is not a universal
+  OpenCode host-runtime claim. Official OpenCode V2.0.31 has a Bun runtime path
+  and a separate Node build pinned to 26.4.0; no Bun minimum is asserted.
+- **Keep `node:sqlite` as a separate capability threshold:** Node >=22.5 may
+  provide the optional `pantheon_cost` backend, but does not imply package
+  support on that Node version.
+- **Recommend a persistent external Git worktree location** in interactive TTY
+  setup summaries and the shipped worktrees skill. This is guidance only;
+  Pantheon does not create worktrees or directories automatically.
+
+## 🐞 Fixed
+
+- **Synchronize Beta 12 version metadata and Node engine policy** across package
+  manifests, locks, citation/release metadata, CLI guards, doctor, and CI.
+
 ## [v1.6.0-beta.11] - 2026-10-15
 
 ## 🆕 What's New

package/README.md

@@ -31,16 +31,17 @@ way to plan work, make progress, check results, and keep useful project context.
 ## Start in 2 minutes
 
 Requirements: [OpenCode 1.18.4+](https://opencode.ai/docs/) and Node.js
-22.22.2+ (or 24.15.0+ / 26+). For which OpenCode generation each Pantheon
-release line supports, see
+26.4.0+ for the Pantheon CLI, installer, and Node-based tooling. For which
+OpenCode generation each Pantheon release line supports, see
 [Compatibility and support policy](#compatibility-and-support-policy).
 
-Pantheon declares `engines.node` as `^22.22.2 || ^24.15.0 || >=26.0.0`. The
-floor reflects what the dependency tree actually needs — the transitive
-`ini@7` rejects earlier 22.x/24.x builds with `EBADENGINE` — and odd-numbered
-Node releases (23, 25) are out of range. The `pantheon_cost` tool also needs
-`node:sqlite`, which requires Node >= 22.5; `doctor` warns when the running
-runtime cannot load it.
+Pantheon declares `engines.node` as `>=26.4.0`; Node 22, Node 24, and Node
+26.0–26.3 are not supported by this release. This package floor does not imply
+that every OpenCode host runs on Node: official OpenCode V2.0.31 has a Bun
+runtime path and a separate Node build pinned to Node 26.4.0. No Bun minimum is
+asserted here. The optional `pantheon_cost` SQLite backend has its own capability
+threshold, `node:sqlite` on Node >= 22.5; that feature threshold does not lower
+Pantheon's package or CLI support floor.
 
 From the project where you want to use Pantheon:
 
@@ -53,22 +54,63 @@ The installer guides you through the available setup. For optional MCP servers,
 project-local installation, or non-interactive setup, see the
 [installation guide](docs/INSTALLATION.md).
 
+In an interactive TTY setup summary, Pantheon recommends the persistent
+external worktree location
+`<project-parent>/.pantheon-worktrees/<exact-repository-directory-basename>/<task>`
+(for example, `/home/user/.pantheon-worktrees/My Project/feature-name`). Use the
+project directory's exact basename, including spaces; do not normalize it into
+a slug. This is guidance for future agent work only; Pantheon does not create
+Git worktrees or directories automatically. See the shipped
+[worktrees skill](src/skills/worktrees/SKILL.md) for the agent workflow.
+
 A non-interactive apply requires `--yes` (alias `-y`): without a TTY and
 without `--yes`, `init` prints the change plan and applies nothing. Exit codes:
 `0` success or plan/no-apply, `1` failure, `2` apply requested without
-authorization, `3` drift (a planned target changed between plan and apply),
-`130` canceled. Drift is checked within a single run (plan → apply); it cannot
-be detected across two separate CLI invocations (no plan is persisted).
-
-Preview without writing anything with `init --dry-run`. Before the first write,
-`init` saves an exact backup set under `.pantheon/backups/<timestamp>/`
-(directory `0700`, files `0600`, the 5 most recent kept); it is a byte-for-byte
-copy and therefore also contains any API keys or tokens already present in your
-files — it is never printed. Recover with
-`pantheon-opencode restore [--project] [--yes]` (there is no automatic
-rollback; an interrupted apply is recoverable the same way). The
-`postinstall`/`sync-tui` step only refreshes TUI artifacts and is deliberately
-outside this approval flow — no prompt is possible there.
+authorization, `3` drift (a planned target changed before apply), `130` canceled.
+
+Preview with `init --dry-run`. To review and apply across separate invocations,
+save a versioned plan and then explicitly authorize it:
+
+```bash
+npx pantheon-opencode init --dry-run --project --no-mcp --components agents \
+  --save-plan .pantheon-install-plan.json
+npx pantheon-opencode init --apply-plan .pantheon-install-plan.json --yes
+npx pantheon-opencode init --dry-run --json  # machine-readable preview on stdout
+```
+
+Saved plans use mode `0600`, contain operation metadata and fingerprints rather
+than generated file contents, and are bound to their original target and plan
+file path. Applying rechecks the package source and destination snapshots; drift
+aborts before writes. Saved plans do not support `--force`/`--clean`, and
+machine-readable previews reject those options because clean performs bulk removal.
+A dry-run skips probing the OpenCode host to avoid host-side writes; when no version hint
+is configured, it assumes V1 and reports that advisory. Pass
+`--opencode-version v1|v2` to preview a specific generation.
+Saving an artifact is supported on Linux, Darwin, FreeBSD, OpenBSD, and NetBSD
+when the required descriptor paths and filesystem flags are usable. Cross-platform
+behavior has not been fully tested; unsupported platforms fail closed rather
+than risk writing through a replaced parent directory.
+Previews describe managed-file operations, not every bulk or external effect
+(such as Python environment setup). The `postinstall`/`sync-tui` step also only
+refreshes TUI artifacts and is outside this approval flow.
+
+Before the first managed-file write, `init` saves an exact backup set under
+`.pantheon/backups/<timestamp>/` (directory `0700`, files `0600`, the 5 most
+recent kept); it is a byte-for-byte copy and therefore also contains any API
+keys or tokens already present in your files — it is never printed. Recover with
+`pantheon-opencode restore [--project] [--yes]`. There is no automatic rollback;
+an interrupted apply is recoverable from the backup in the same way.
+To remove Pantheon-managed files, review with
+`pantheon-opencode uninstall --project --dry-run` (or `--global`) before applying
+with `--force`. The opt-in `--purge-data` removes only a verified install-state
+file and never removes recovery backups; see the installation guide for details.
+New installs also record a versioned per-file ownership inventory. Review stale,
+unchanged installer-owned files with `pantheon-opencode reconcile --project --dry-run`
+(or `--global --dry-run`); preview is read-only, and apply requires `--apply --yes` or a
+saved reviewed plan. Legacy files without inventory, modified files, and
+symlinks are preserved for manual review. An explicit `--target PATH` uses project
+layout; combine it with `--global` to select the flat global layout. See the
+[installation guide](docs/INSTALLATION.md).
 The bundled Python MCP servers use the pinned MCP SDK 2.2.0 and standalone
 FastMCP 4.0.10 runtime; see the [MCP guide](docs/MCP.md).
 The installer also turns each agent's `mcp_tools` allowlist into native
@@ -254,7 +296,7 @@ available.
 
 | Variable | Default | Purpose |
 |----------|---------|---------|
-| `PANTHEON_NODE` | `node` from `PATH` | Path to a Node.js >= 22.5 binary used by the CLI fallback; an explicit path must exist and be executable, otherwise the tool fails fast instead of ignoring the override |
+| `PANTHEON_NODE` | `node` from `PATH` | Path to a Node.js >= 22.5 binary used only for the `node:sqlite` capability in the CLI fallback; this is not the Pantheon package support floor. An explicit path must exist and be executable, otherwise the tool fails fast instead of ignoring the override |
 
 Tool interpretation matters: `pantheon_model status` reports configuration, not the model serving a completion. V2 manual model overrides are project-only; global override files are neither read nor applied, and global mutation is unsupported until a future surface can obtain separate explicit human authorization. V2 ignores static presets and applies only explicit per-agent project model/variant overrides, leaving the host default unchanged otherwise; V1 preset behavior remains legacy pending compatibility decisions. `pantheon_cost` is a rolling token aggregate, not a session-level or monetary cost report. See the [OpenCode plugin tool notes](docs/mcp-tools.md#opencode-plugin-tools) for details and measurement limits.
 
@@ -543,13 +585,10 @@ Key order does not matter.
 One command keeps an existing installation current:
 
 ```bash
-# Without a global install, ALWAYS pin the dist-tag — plain `npx
-# pantheon-opencode` resolves `latest`, which is the stable release (1.4.3):
-npx pantheon-opencode@beta update            # npm beta channel + config refresh
-npx pantheon-opencode@beta update --stable   # stable channel instead
-
-# With a global install, use the global bin (defaults to the beta channel):
-pantheon-opencode update
+# Install globally first; update refuses local, workspace, and npx copies.
+npm install -g pantheon-opencode@beta
+pantheon-opencode update            # npm beta channel + config refresh
+pantheon-opencode update --stable   # stable channel instead
 ```
 
 `update` compares your installed version with the npm dist-tag, runs
@@ -851,7 +890,7 @@ or whole-file binary classification. The host-backed evidence is in
 
 `npm run coverage:plugin-v2` runs the `tests/pantheon/*.test.ts` suite with
 Node's source-mapped native coverage and enforces an 80% line-coverage minimum
-for `src/plugin-v2.ts` only. It requires Node `v24.15.0`; branch and function
+for `src/plugin-v2.ts` only. It requires Node `>=26.4.0`; branch and function
 coverage are reported but are not gates. This is not a repository-wide coverage
 claim.
 

package/README.pt-BR.md

@@ -31,7 +31,9 @@ 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 `^22.22.2 || ^24.15.0 || >=26.0.0`.
+Requisitos: [OpenCode 1.18.4+](https://opencode.ai/docs/) e Node.js `>=26.4.0` para a CLI, o instalador e as ferramentas Node do Pantheon. Node 22, Node 24 e Node 26.0–26.3 não são compatíveis com esta versão.
+
+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.
 
 No projeto em que você quer usar o Pantheon:
 
@@ -75,8 +77,7 @@ verificações repetíveis e passagens claras entre etapas do trabalho.
 
 ## Status
 
-Versão operacional neste checkout: **v1.6.0-beta.1** (primeira beta compatível
-com OpenCode 2; esta página não afirma publicação). O Pantheon foi feito para OpenCode e depende da
+Versão operacional neste checkout: **v1.6.0-beta.12** (esta página não afirma publicação). O Pantheon foi feito para OpenCode e depende da
 disponibilidade e da configuração do OpenCode e dos serviços opcionais que você
 escolher. Veja as [releases](https://github.com/ils15/pantheon-opencode/releases)
 e o [changelog](CHANGELOG.md) para acompanhar as mudanças publicadas.
@@ -536,7 +537,7 @@ anteriores foram preservadas separadamente em
 
 `npm run coverage:plugin-v2` executa a suíte `tests/pantheon/*.test.ts` com a
 cobertura nativa do Node habilitada para source maps e exige pelo menos 80% de
-cobertura de linhas somente para `src/plugin-v2.ts`. Requer Node `v24.15.0`;
+cobertura de linhas somente para `src/plugin-v2.ts`. Requer Node `>=26.4.0`;
 coberturas de branches e funções são informativas, não gates. Isso não é uma
 alegação de cobertura do repositório inteiro.