pi-pstack-adapter 0.6.0 → 0.8.0

package/CHANGELOG.md

@@ -2,6 +2,28 @@
 
 All notable changes to this project are documented here. release-please writes new entries from Conventional Commit PR titles.
 
+## [0.8.0](https://github.com/elderfo/pi-pstack-adapter/compare/v0.7.0...v0.8.0) (2026-11-01)
+
+
+### Features
+
+* **host-mapping:** scan for unmapped Cursor terms and port upstream's Claude Code harness lessons ([#27](https://github.com/elderfo/pi-pstack-adapter/issues/27)) ([5a787f0](https://github.com/elderfo/pi-pstack-adapter/commit/5a787f064b61d8cdf3dd100b10bb97c6b1435805))
+* **models:** add upstream's panel roles and warn when a panel runs on one model ([#28](https://github.com/elderfo/pi-pstack-adapter/issues/28)) ([dcf1684](https://github.com/elderfo/pi-pstack-adapter/commit/dcf1684d5c48fe91f433e04da6a4ef315985bbaf))
+* **pstack:** certify pstack 0.15.29 ([#21](https://github.com/elderfo/pi-pstack-adapter/issues/21)) ([5cb1ba9](https://github.com/elderfo/pi-pstack-adapter/commit/5cb1ba96e89c5926b451984ddb53d84dfc3f7ab1))
+* **pstack:** certify pstack 0.15.30 with statechart ([#23](https://github.com/elderfo/pi-pstack-adapter/issues/23)) ([8fc2e93](https://github.com/elderfo/pi-pstack-adapter/commit/8fc2e9370dab422870e3661dd18f8bf4d4a400f5))
+* **pstack:** certify pstack 0.15.32 with ketchup-video ([#24](https://github.com/elderfo/pi-pstack-adapter/issues/24)) ([4272d99](https://github.com/elderfo/pi-pstack-adapter/commit/4272d9998ed7c904b8c5ba57f578dbbb739f07e1))
+* **pstack:** certify pstack 0.15.34, with statechart experimental after a Windows crash ([#25](https://github.com/elderfo/pi-pstack-adapter/issues/25)) ([5c569fe](https://github.com/elderfo/pi-pstack-adapter/commit/5c569fe9330a99fb4a46388e96664a2522b043b3))
+* **pstack:** certify pstack 0.15.36 ([#26](https://github.com/elderfo/pi-pstack-adapter/issues/26)) ([8491d49](https://github.com/elderfo/pi-pstack-adapter/commit/8491d49e9e7f7797a3203515b6c68ea1dec7de4c))
+
+## [0.7.0](https://github.com/elderfo/pi-pstack-adapter/compare/v0.6.0...v0.7.0) (2026-10-19)
+
+
+### Features
+
+* **pstack:** certify pstack 0.15.26 with create-formal-verification-skill ([#17](https://github.com/elderfo/pi-pstack-adapter/issues/17)) ([82367d9](https://github.com/elderfo/pi-pstack-adapter/commit/82367d93e372fc49c603f56e79469197a77814a2))
+* **pstack:** certify pstack 0.15.28 with maintain-formal-verification-skill ([#20](https://github.com/elderfo/pi-pstack-adapter/issues/20)) ([0dee303](https://github.com/elderfo/pi-pstack-adapter/commit/0dee303dbd349dfd9726ff6e3c17a8d96ecf95a2))
+* **roles:** add a general role and cap delegate thinking at the configured level ([#19](https://github.com/elderfo/pi-pstack-adapter/issues/19)) ([df1db04](https://github.com/elderfo/pi-pstack-adapter/commit/df1db045c49907665b7a2ef504b3ab52da287502))
+
 ## [0.6.0](https://github.com/elderfo/pi-pstack-adapter/compare/v0.5.0...v0.6.0) (2026-10-17)
 
 

package/README.md

@@ -135,8 +135,10 @@ skill.
 
 ## Choose models for pstack roles
 
-pstack assigns work to named model roles such as `feature`, `bug-fix`, and `judgment`. A role you
-leave unset uses the current Pi session model.
+pstack assigns work to named model roles such as `feature`, `bug-fix`, and `judgment`. The
+`general` role covers every other delegate, such as explorers, swarm workers, and ad-hoc helpers.
+A role you leave unset uses `general`, and uses the model of the agent that starts it only when
+`general` is unset too.
 
 To list the models in your Pi installation and assign them to roles, run the setup skill:
 
@@ -157,11 +159,27 @@ Add a thinking level to a role with a `:level` suffix. The levels are `off`, `mi
 PISTACK_MODELS='feature=provider/model:medium,judgment=provider/other-model:high' pi
 ```
 
+Panels such as `arena`'s runners and judge, `architect`'s runners, and `interrogate`'s adversaries
+use the panel roles `arena-runners`, `arena-cross-judge-pool`, `architect-runners`, and
+`interrogate-reviewers`. A panel holds a list of models, one seat each, separated by spaces.
+An `inherit` entry uses the model and thinking of the agent that starts the panel, which is
+your session unless a delegate runs the workflow:
+
+```bash
+PISTACK_MODELS='arena-runners=provider/model:high other-provider/other-model:high' pi
+```
+
+Upstream pstack defaults each panel to two model families. A panel you leave unset uses
+`judgment`, then `general`, so it covers two families only when those roles do. The status
+report warns when a panel's seats all run on one model.
+
 Role names are lowercase letters, digits, and hyphens. A model value is printable ASCII with no spaces or markup characters, at most 128 characters. A config entry that breaks these rules stops the adapter at startup with an error that names the file, so fix the key there and restart Pi.
 
-A role without a level passes none, so the delegation backend applies its own default. A role you leave unset inherits the
-session model and the session thinking level, so a session at high thinking makes every
-inheriting delegate expensive. The `pstack_adapter` tool's `set_model` action takes the same
+A role without a level passes none, so the delegation backend applies its own default. A role's
+level is a ceiling: a delegate may lower it for routine work but never raises it. A role you leave
+unset, with `general` unset too, inherits the model and thinking level of the agent that starts
+it. A `strongest-judgment` delegate at `xhigh` would then start every helper at `xhigh`, so set
+`general` to keep helpers at a cheaper level. The `pstack_adapter` tool's `set_model` action takes the same
 level in its `thinking` parameter. A level the model does not offer is clamped by Pi at run time.
 
 ## Run Pi noninteractively
@@ -202,7 +220,7 @@ settings to `.pi/pi-pstack-adapter.json`. Environment variables override both fi
 | `PISTACK_UPSTREAM_PLUGIN_PATH` | Selects the plugin directory inside the checkout. |
 | `PISTACK_ALLOW_BOOTSTRAP` | Allows a noninteractive first download. |
 | `PISTACK_CACHE_DIR` | Changes the cache directory. |
-| `PISTACK_MODELS` | Assigns models as comma-separated `role=provider/model[:thinking]` pairs. |
+| `PISTACK_MODELS` | Assigns models as comma-separated `role=provider/model[:thinking]` pairs. A panel role takes its entries separated by spaces. |
 | `PISTACK_DELEGATION` | Sets the delegation provider to try first: `t3` (default) or `pi-subagents`. The config file key is `delegation`. |
 
 ## Security and trust

package/VERSION

@@ -1 +1 @@
-0.6.0
+0.8.0

package/adapter-skills/setup.md

@@ -9,8 +9,9 @@ Three things are configurable. Model roles, the upstream source, and the delegat
 ## Model roles
 
 pstack skills name a model per role. In Pi those names mean nothing, so each role maps to a
-model in your own catalogue. A role you never configure inherits the parent session model,
-which is a working default, not a failure.
+model in your own catalogue. A role you never configure uses the `general` role. When `general` is
+unconfigured too, the role inherits the model of whichever agent starts it, which is a working
+default, not a failure.
 
 Roles used by pstack workflows.
 
@@ -23,6 +24,27 @@ Roles used by pstack workflows.
 | `hillclimb` | sustained metric improvement |
 | `judgment` | prose, review, and judgment delegates |
 | `strongest-judgment` | the hardest cross-cutting changes |
+| `general` | every other delegate: explorers, investigators, swarm and verification workers, ad-hoc helpers, and any unconfigured role |
+
+Upstream also has panel lines, which hold a list of models with one seat per entry. The adapter
+keeps them as panel roles.
+
+| panel role | used by |
+| --- | --- |
+| `arena-runners` | `arena`'s candidates |
+| `arena-cross-judge-pool` | `arena`'s one judge, which `architect` uses too |
+| `architect-runners` | `architect`'s design candidates |
+| `interrogate-reviewers` | `interrogate`'s adversaries |
+
+Upstream defaults each panel to two model families, one Claude model and one Grok model. A panel
+left unset uses `judgment`, then `general`, so it spans two families only when those roles do.
+`arena` takes its judge from the pool only when the model is from a family other than the
+session's model, so a pool on the session's family skips the judge. The status report warns when
+a panel's seats all land on one model.
+
+A panel value lists entries in order. An entry is a model id, optionally with a thinking level,
+or `inherit` for the model and thinking of the agent that starts the panel, which is the
+session unless a delegate runs the workflow. An `inherit` entry never judges.
 
 The status report lists the same roles, so read it back rather than trusting this table if the
 adapter has been upgraded.
@@ -30,9 +52,11 @@ adapter has been upgraded.
 Each role also has a thinking level: `off`, `minimal`, `low`, `medium`, `high`, `xhigh`, or
 `max`. Upstream pstack calls this a reasoning budget and encodes it in the model slug. A role with
 no thinking level passes none, so the delegation backend applies its own default. A role left on
-`inherit` uses the parent session's model and thinking level, so a parent at high thinking makes
-every inheriting child expensive. Model choice often affects cost more than thinking level does,
-so consider a cheaper model for the bulk roles as well.
+`inherit` with `general` also on `inherit` uses the model and thinking level of the agent that
+starts it. A `strongest-judgment` delegate at `xhigh` would then start every helper at `xhigh`, so
+configure `general` to stop that. A role's level is a ceiling: delegates may lower it for routine
+work, but never raise it. Model choice often affects cost more than thinking level does, so
+consider a cheaper model for the bulk roles as well.
 
 Steps.
 
@@ -45,10 +69,10 @@ Steps.
    role is on `inherit`. It applies to every role that got a model in step 2. A role on
    `inherit` cannot have a level, so tell the user that and say that those roles follow the
    parent session's level. Ask one single-select question first. Put the whole choice in each option
-   title so the user can pick without opening anything else, for example "Balanced: code roles
+   title so the user can pick without opening anything else, for example "Balanced: code and general roles
    medium, judgment high, strongest-judgment xhigh (suggested)".
 
-   | choice | code roles (`feature`, `refactoring`, `bug-fix`, `perf-issue`, `hillclimb`) | `judgment` | `strongest-judgment` |
+   | choice | code and general roles (`feature`, `refactoring`, `bug-fix`, `perf-issue`, `hillclimb`, `general`) | `judgment` | `strongest-judgment` |
    | --- | --- | --- | --- |
    | Balanced (suggest this first) | `medium` | `high` | `xhigh` |
    | Low cost | `low` | `medium` | `high` |
@@ -58,7 +82,7 @@ Steps.
 
    These are starting points, not measurements. They keep the heaviest reasoning on the roles
    that make the hardest calls. Offer Custom for a user who wants different levels. Ask once for
-   the code roles, once for `judgment`, and once for `strongest-judgment`. Ask a role on its own
+   the code and general roles, once for `judgment`, and once for `strongest-judgment`. Ask a role on its own
    only when the user says it should differ from its group. Backend default passes no level and
    leaves the choice to the delegation backend. A Custom user who wants thinking disabled picks
    `off`.
@@ -69,12 +93,21 @@ Steps.
    `provider/model` id, and `thinking` when step 3 picked a level. Pass `scope: "project"` when
    the user wants the choice to apply only to this repository. Calling `set_model` for a role
    again without `thinking` clears a level set earlier, so always pass it again.
-5. Read back `action: "status"` and show the user what was written, including the thinking
-   column.
+5. Set the panels. Read the `panel roles` table of `action: "status"` and show the user each
+   panel's seats. When a panel's seats share one model, or one family, say so and suggest two
+   families from step 1, as upstream's defaults do. Never say a family is missing unless the
+   step 1 list shows it. Ask whether to keep each panel or set it. For each panel the user sets,
+   call `set_model` with the panel role and its entries in `model`, separated by commas, for
+   example `model: "provider/model-a, provider/model-b"`. Pass `thinking` for the level of the
+   `judgment` column in step 3, unless the user picked another. An entry with its own `:level`
+   keeps it. Pass `model: "inherit"` to unset a panel.
+6. Read back `action: "status"` and show the user what was written, including the thinking
+   column and the panel roles.
 
 For a scripted environment, set `PISTACK_MODELS` instead, for example
 `PISTACK_MODELS=feature=anthropic/claude-sonnet-4-5:medium,bug-fix=openai/gpt-5:high`. The
-optional `:level` suffix sets the thinking level. The environment wins
+optional `:level` suffix sets the thinking level. A panel's entries are separated by spaces, as
+in `PISTACK_MODELS='arena-runners=anthropic/claude-sonnet-4-5:high openai/gpt-5:high'`. The environment wins
 over both config files, so CI never needs this dialog.
 
 ## Upstream source

package/docs/compatibility.md

@@ -4,7 +4,7 @@ The compatibility registry in `src/registry.ts` assigns one support tier to ever
 certified pstack revision. Generation reads it, the wrapper frontmatter publishes it, and
 `/pistack-status` reports it.
 
-Certified revision: pstack `0.15.25` at `101b274dd991f694e1f7024be2157e5f3adf07de` in
+Certified revision: pstack `0.15.36` at `c742dd61706fbacc1b95f1a20b7b988cf096ce6c` in
 `https://github.com/cursor/plugins`.
 
 ## Platforms
@@ -21,17 +21,230 @@ executables in the shell the skills run in, with Pi's `shellCommandPrefix` appli
 that matters most, because Git Bash adds `/usr/bin` and `/mingw64/bin` to the `PATH` Pi
 started with. A shell that is missing, inactive, or cannot run a command blocks every workflow.
 
-Windows evidence was last gathered at pstack `0.15.23`, on Windows 11 with Git for Windows 2.53,
-Node 22, Bun 1.3, and Pi 1.2.0. CI runs the unit suite on Windows at `0.15.25`; the rest of this
-list has not been rerun there:
-
-- The unit suite and the type check pass. `npm run test:isolated` passes from Git Bash: Pi
-  registers all 54 skills, and a later run reuses the cache without the network. CI runs the
-  unit suite on Windows for every change.
-- The certification probe passes on an LF export of the tree: no diagnostics, 52 bodies
-  byte-identical, and none mismatched. The adapter's cache checkout matches that export byte for
-  byte.
-- `in-your-own-words`, `ketchup`, and `poteto-help` ran end to end in the isolated install, with
+pstack `0.15.36` was certified on Linux. No skill or agent was added or removed. The skills
+changed only in text, and the Orchestrate playbook's `orch` scripts were deleted; no adapter
+gate named them. `0.15.36` has not been checked on native Windows. The statechart scripts did
+not change, so the `0.15.34` Windows findings below still describe them.
+
+Ten skills then ran end to end in two isolated installs built from the packed package, on
+Pi 1.4.0 with the CLIProxyAPI provider extension. The parent model was Claude Opus 5.5, with the
+`judgment` role on Claude and the `general` role on GPT 6.1. One install had no delegation or
+question tool. The other added pi-subagents 0.83.0, and later pi-ask-user 0.17.0, as Pi
+packages, so their children loaded the same provider. Each skill ran in a throwaway copy of a
+small Git repository holding a token-bucket rate limiter with two marked bugs.
+
+- Without delegation, `sharpen` handed back a rewritten prompt and did not do the task, so it
+  rises to `native`. `statechart` found the uncapped refill as the shortest path to a broken
+  rule. With only an older Node on PATH, its launcher named the versions it needs and exited
+  127. `ketchup-video` drew five slides and rendered a subtitled 35-second mp4 with `ffmpeg`.
+- With pi-subagents, `interrogate`, `arena`, and `show-me-your-work` completed every delegation
+  step against a real provider, on two model families, so each rises to `adapted`.
+  `interrogate`'s two adversaries proved the same two bugs in their own worktrees. `arena`'s
+  judge came from the family other than the parent's. `show-me-your-work`'s reviewer read the
+  parent's Pi session file.
+- The transcript mapping held. `recall`, `reflect`, `automate-me`, and the `show-me-your-work`
+  reviewer read this workspace's Pi session files and nothing else in the session folder.
+  `recall` rises to `dependency-gated`, because the transcript was its only Cursor-specific
+  step. In a fresh session it read the two earlier chats itself, so its fan-out did not run. An
+  earlier fresh run looked in the default session folder, which the sandbox had moved, so the
+  host mapping now says to find the folder from `$PI_SESSION_FILE` first. `reflect` copied the upstream skill
+  to a Pi skill location before editing it, but its create-skill route did not run, and
+  `automate-me` found nothing to draft, so both stay `experimental`.
+- `poteto-mode`'s Orchestrate playbook ran a two-unit program in a linked worktree. Each unit had
+  an owner on its own branch and worktree, and a verifier from another model family checked the
+  owner's head before a new agent merged it. The tracker and store went in a folder it added to
+  the exclude file that `git rev-parse --git-path info/exclude` names, which lives in the main
+  repository's Git directory. That run led to the host mapping rule that a substitute is not a
+  skip. `poteto-mode` stays `experimental`: its other playbooks and sticky mode were not rerun.
+- `ketchup-video` stays `experimental`, because whether a Pi client plays its embedded video is
+  still unverified.
+- Upstream does not name a `/goal` command at `0.15.36`. Its `/loop` now has a host mapping row,
+  and the vocabulary scan finds it.
+
+pstack `0.15.34` was certified on Linux, then checked on native Windows 11 (build 26200) with
+Git for Windows, Node 22.23.2, and mise, over SSH from Git Bash. On Windows:
+
+- The type check passes. The unit suite runs 189 tests: 186 pass, none fail, and 3 skip. All ten
+  integration tests pass with no skips. The probe on an LF export of the certified commit
+  matches Linux: 59 skills, two agents, no diagnostics, 57 bodies byte-identical, `setup-pstack`
+  replaced, and none mismatched.
+- The isolated install passes with the CLIProxyAPI scratch copy described below: 59 skills, no
+  `subagent` or `ask_user` with the provider extension loaded, and cache reuse without bootstrap
+  permission. `/pistack-check pistack-statechart` clears.
+- The `0.15.34` statechart scripts crash. On upstream's own `MediaPlayer` corpus model, the
+  launcher exits 1 with an unhandled `spawn /bin/sh ENOENT`, before TLC runs. It writes no
+  output folder and leaves an empty hidden staging folder beside it and an empty `statechart-`
+  folder in the temporary folder. No worker or TLC process is left running. This reproduction
+  lowers `statechart` to `experimental`.
+
+The Windows statechart findings further below describe the `0.15.32` scripts. The other skills
+that changed in `0.15.34` changed only in text. Linux evidence for the `0.15.34` statechart
+scripts, gathered on Node 26.12.1, Bun, Deno 2.9.8, and mise 2026.10.17:
+
+- `/pistack-check pistack-statechart` clears in the isolated install, and `statechart` ran there
+  against a checkout fixture whose 5-second timeout shows "Try again" while the first charge is
+  still in flight. From the code, it wrote a TLA+ model and a `--view` module. TLC found the rule
+  "the shopper is never charged twice for one cart" broken (21 model states), and the report gave
+  the five-step path. A replay test drove the real module with a fake gateway and clock and
+  reproduced two charges, and the regenerate command rebuilt the same chart into a fresh folder.
+  The fixture repository stayed clean.
+- A cold run installed TLC 1.7.4 and Java temurin-25 with `mise`. The `TLA2TOOLS` path, with
+  `JAVA` set and with `java` from PATH, gave the same report and chart. The scripts also ran
+  under Bun and Deno. A rerun into a folder that is not empty exits 2 and writes nothing.
+- Upstream's own suite passes on Linux with `TLA2TOOLS` set: 367 tests, none failed or skipped.
+- `pele@1.9.0`, installed with `--ignore-scripts`, rendered the fixture's `chart.mmd` to SVG with
+  the options that `references/render.md` gives.
+
+Earlier Windows evidence, gathered at pstack `0.15.32` on Windows 11 Pro with Git for Windows
+2.53.0, Node 22.23.2, npm 10.9.8, Pi 1.3.0, mise 2026.10.8, and ffmpeg 8.1. No JDK was on
+PATH and `TLA2TOOLS` was unset, so statechart took the `mise` path:
+
+- The type check and unit suite pass: 189 tests, 185 passed, none failed, and the four symlink
+  tests skipped. All ten integration tests pass with no skips, including the Windows 8.3
+  short-path case and the `plugins/cache/` host-mapping regression.
+- The probe on an LF export of the certified commit reports 59 skills, two agents, no
+  diagnostics, 57 bodies byte-identical, `setup-pstack` replaced, and none mismatched. That
+  matches the Linux probe.
+- The isolated install passes from Git Bash with the CLIProxyAPI scratch copy described below:
+  59 skills, no `subagent` or `ask_user` with the provider extension loaded, and cache reuse
+  without bootstrap permission. `/pistack-check` clears `pistack-statechart`, with `node` and
+  `npm` on PATH, and `pistack-ketchup-video`.
+- The 0.15.32 statechart scripts run on native Windows from a cold machine. `from-chart` on
+  upstream's own `upload.mmd` with `--png` installed `pele` and `@resvg/resvg-js` with `npm`
+  under `~/.cache/statechart/`, installed TLC 1.7.4 and Java temurin-25 with `mise`, drew the
+  chart back unchanged, and rendered the PNG. The `npx` defect from `0.15.30` is gone. A rerun
+  into the same `--out` folder still fails with `EPERM` and exit code 2. It leaves the old folder
+  unchanged, and it names the temporary folder that holds the new files.
+- `statechart` ran in the isolated install against a checkout fixture whose 5-second timeout
+  shows "Try again" while the first charge is still in flight. From the code, it wrote a TLA+
+  model and a mapping. TLC found the rule "The customer is charged at most once for one cart"
+  broken, and also found that a declined charge leaves the screen on "Paying" (19 model states
+  and 33 steps, drawn as 10 chart states and 15 arrows). The PNGs rendered through `--png` with
+  no workaround, and the numbered five-step double-charge path read correctly. A replay test
+  drove the real module with a fake gateway and clock and reproduced both bugs, and the
+  regenerate script it wrote rebuilt every chart into a fresh folder. The fixture repository
+  stayed clean. This supports `dependency-gated` for the 0.15.32 scripts.
+- Upstream's own `scripts/test/statechart.test.mjs` still does not pass on Windows. Of its 150
+  tests, the first 126 ran: 99 pass, 3 skip for missing fonts, and 24 fail. The 127th, which
+  kills a run during TLC, waits for TLC to write into `TMPDIR`, which Node ignores on Windows,
+  and hangs. The remaining tests were not run. Ten failures are the `EPERM` rename. Six fake
+  `mise` with a shell script, which Windows cannot start. Five expect the temporary folder that
+  `TMPDIR` names, and three expect `/` in paths that Windows prints with `\`.
+- `ketchup-video` ran in the isolated install after a session that fixed a pricing bug and
+  committed the fix. It drew four slides with `ffmpeg` and the Windows Arial font, rendered a
+  16-second 1280x720 mp4 outside the repository, and left the repository unchanged. The slides
+  read correctly. Its reply embedded the video as an HTML `video` tag. Whether a Pi client plays
+  it inline was not checked, so the skill stays `experimental`.
+
+Earlier Windows evidence, gathered at pstack `0.15.30` on Windows 11 Pro with Git for Windows
+2.53.0, Node 22.23.2, Bun 1.3.14, Pi 1.3.0, and a portable Temurin JDK 21.0.12 with the latest
+`tla2tools.jar`. Its statechart findings describe the scripts that `0.15.32` replaced:
+
+- The type check and unit suite pass: 187 tests, 183 passed, none failed, and the four symlink
+  tests skipped. All nine integration tests pass with no skips, including the Windows 8.3
+  short-path case and the statechart wrapper regression with its nested support files.
+- The isolated install passes from Git Bash with the CLIProxyAPI scratch copy described below:
+  58 skills, no `subagent` or `ask_user` with the provider extension loaded, and cache reuse
+  without bootstrap permission. The installed checkout's 184 files match an LF export of the
+  pinned tree byte for byte. The probe reports 58 skills, two agents, no diagnostics, 56 bodies
+  byte-identical, `setup-pstack` replaced, and none mismatched. The 11 statechart support files
+  sit beside the generated wrapper and match upstream.
+- The installed status report shows `tested` trust at the certified commit. `/pistack-check`
+  ran for all 58 skills. Each delegating skill names the missing `delegation` capability,
+  `benchmark-checklist` still names `uptime`, and every other skill clears.
+  `/pistack-check pistack-statechart` names `java` until a JDK is on PATH, then clears.
+  Git Bash rewrites a leading `/` in a `pi -p` argument into a Windows path, so pass
+  `MSYS2_ARG_CONV_EXCL='/pistack;/skill'` when scripting these commands.
+- `statechart` ran in the isolated install against a checkout fixture whose 5-second timeout
+  shows "Try again" while the first charge is still in flight. From the code, it wrote a TLA+
+  model and a mapping, and TLC found the rule "A customer is never charged twice for one cart"
+  broken (20 model states, 9 chart states). It rendered both charts to PNG, and the numbered
+  five-step bug path read correctly. A replay script drove the real module with a fake gateway
+  and clock and reproduced two charges. The fixture repository stayed clean. Two upstream
+  defects needed workarounds. `--png` calls `spawnSync("npx")`, which cannot start `npx.cmd`
+  on Windows, so the PNGs were rendered by running `npx` directly. Renaming a directory onto an
+  existing one fails with `EPERM` on Windows, not `ENOTEMPTY` or `EEXIST`, so every rerun
+  into an existing output folder fails and leaves it unchanged until the folder is deleted.
+  This supports `dependency-gated` with those workarounds in its note.
+- Upstream's own `scripts/test/statechart.test.mjs` does not pass on Windows: of 58 tests, 41
+  pass, 2 skip, 12 fail, and 3 hang. The two defects above cause eight failures. Three expect
+  `/` in paths that Windows prints with `\`, and one of those also sets `TMPDIR`, which Node
+  ignores on Windows. One runs a fake `java` shell script, which Windows cannot start. The three
+  hangs wait for TLC to write into `TMPDIR`, which Node ignores on Windows, so they never see
+  it start.
+- `poteto-help` routed a request to show a PM a double-charge path to
+  `/skill:pistack-statechart`. It named the `pistack-` prefix and listed the missing `java` and
+  `TLA2TOOLS` prerequisites.
+
+Earlier Windows evidence, gathered at pstack `0.15.28` with the same toolchain:
+
+- The type check and unit suite pass: 183 tests, 179 passed, none failed, and the four symlink
+  tests skipped. All eight integration tests pass with no skips, including the Windows 8.3
+  short-path case and both formal-verification wrapper regressions.
+- The isolated install passes from Git Bash with the same CLIProxyAPI scratch copy as below: 57
+  skills, no `subagent` or `ask_user` with the provider extension loaded, and cache reuse without
+  bootstrap permission. The installed checkout's 172 files match an LF export of the pinned tree
+  byte for byte. The probe reports 57 skills, two agents, no diagnostics, 55 bodies
+  byte-identical, `setup-pstack` replaced, and none mismatched.
+- The installed status report shows `tested` trust at the certified commit, and
+  `/pistack-check pistack-maintain-formal-verification-skill` clears the workflow. `git` is
+  its only executable, and Git for Windows bundles it.
+- `maintain-formal-verification-skill` ran in the isolated install against a fixture whose
+  `.pi/skills/` verify skill recorded a sync commit, followed by a rename of a covered function
+  and a new batch function that wrote the guarded state without its duplicate-ID guard. It
+  found the skill, ran the stale check (it crashed on the rename), read all three commits since
+  the sync commit, renamed the call, extended the harness to the new function, and reported the
+  bug with the commit that introduced it and a two-step counterexample. It proved the updated
+  check could pass and fail by temporarily fixing and then breaking the product file, restored
+  it, moved the sync commit, and committed only the verification and verify-skill changes.
+  This supports `dependency-gated` on `git`.
+- The changed `create-formal-verification-skill` reran in the isolated install. It generated
+  `.pi/skills/verify-inventory-ledger/SKILL.md` with the coverage record and sync commit new in
+  `0.15.28`, plus a dependency-free Node verifier over the real functions (28 states, 168 calls).
+  The check caught six deliberate breaks, and the product file's content was unchanged after
+  each restore. `adapted` still holds.
+
+Earlier Windows evidence, gathered at pstack `0.15.26` with the same toolchain:
+
+- The type check and unit suite pass: 173 tests passed, none failed, and four symlink tests
+  skipped because Windows requires Developer Mode or administrator rights. The seven scheduled
+  integration tests pass with no skips: six cache-containment cases, including a Windows 8.3
+  short-path case, and a formal-verification wrapper regression.
+  Run these separately with `npm run test:integration`; their CI lane is daily and manually
+  dispatchable, not per PR. The existing unit-suite CI matrix still covers all three platforms.
+- The isolated install passes from Git Bash: the cold run registers no skills without bootstrap
+  permission, the permitted run registers all 56 skills, and a later run reuses the cache
+  without bootstrap permission. The local CLIProxyAPI provider requires its extension, config,
+  and model catalog in the sandbox; a scratch copy of the install script supplies them. Its
+  tool probe still reports no `subagent` or `ask_user`. Sandbox credentials are removed on exit.
+- The certification probe passes on an LF export of the pinned tree: 56 skills, two agents,
+  no diagnostics, 54 bodies byte-identical, `setup-pstack` replaced, and none mismatched.
+  All 171 files in the isolated installed cache match the LF export byte for byte.
+- `create-formal-verification-skill` completed in the isolated install without `subagent` or
+  `ask_user`. It generated `.pi/skills/verify-inventory-reservations/SKILL.md` and a dependency-free
+  Node 22 explicit-state verifier that imports the fixture's actual reserve/release functions.
+  It checked 49 reachable states and 490 transitions for stock 0–3 and five request IDs, caught
+  six mutant copies, then caught a removed retry guard in the actual product file. Restoring
+  that file restored the passing result and its original hash. This supports `adapted`: the
+  generated skill path is mapped to Pi. It does not certify TLA+, proof assistants, installation
+  of other verifiers, unbounded inputs, or real database/async concurrency.
+- The revised `ketchup` ran read-only in a separate fixture. It listed both supplied product
+  choices (CSV versus JSON and seven versus thirty days of history), drew a Mermaid sequence
+  diagram for a late-retry edge case it reproduced, and left the fixture unchanged. It did not
+  contact GitHub for this fixture-only task.
+- Installed status reports show native Windows plugin and generated-skill paths and `tested`
+  trust at the certified commit. `/pistack-check` clears the formal-verification workflow and
+  `ketchup`, but still names `uptime` as missing for `benchmark-checklist`. Delegation and
+  structured questions remain unavailable in the isolated install; no delegating tier changed.
+- A cache inside a Git worktree must own its worktree, Git directory, and common directory before
+  bootstrap or reuse can change Git state. The Windows run exposed ancestor discovery from an
+  empty nested cache; this is fixed. Regressions also cover incomplete metadata, a foreign Git
+  file, foreign worktree/common directory settings, and short paths, while checking that the
+  enclosing repository's HEAD, config, index, and tracked bytes stay unchanged.
+
+Historical coverage below has not been rerun at `0.15.26` unless stated otherwise:
+
+- At `0.15.23`, `in-your-own-words`, `ketchup`, and `poteto-help` ran end to end in the isolated install, with
   no `subagent` or `ask_user` tool. `ketchup` reported a commit and a pending decision with
   Mermaid diagrams and changed nothing. `poteto-help` answered with `/pistack-mode on` and read
   the guide from the `plugin directory` row, whose Windows path it resolved.
@@ -45,7 +258,8 @@ list has not been rerun there:
 - At `0.15.25`, `orch.ts` resolves the stack frontier through `gh`, or `origin` with
   `--forge origin`, instead of `gt`. `poteto-mode` already requires `gh`. `worktree-audit.sh`
   reads PR state through `origin` when it is installed, otherwise `gh`, and reports no PR state
-  when neither works. Neither helper has run on Windows at `0.15.25`.
+  when neither works. Neither helper has run on Windows at `0.15.25`. `orch.ts` was deleted at
+  `0.15.36`.
 - At pstack `0.15.9`, `show-me-your-work/scripts/log.sh`, `watch-pr`, and `orch.ts` also ran
   in Git Bash. None of them changed in a way that adds an executable or a path assumption.
 - Git for Windows bundles `git`, `curl`, `nproc`, and the POSIX tools the skill bodies call,
@@ -87,7 +301,7 @@ Lowering a tier needs one reproduction of the failure and a note saying what bro
 
 ## Registry
 
-### native (31)
+### native (32)
 
 | upstream skill | Pi skill | capabilities | executables | why |
 | --- | --- | --- | --- | --- |
@@ -118,33 +332,37 @@ Lowering a tier needs one reproduction of the failure and a note saying what bro
 | `principle-test-behavior-not-implementation` | `/skill:pistack-principle-test-behavior-not-implementation` | - | - | - |
 | `principle-type-system-discipline` | `/skill:pistack-principle-type-system-discipline` | - | - | - |
 | `setup-pstack` | `/skill:pistack-setup` | - | - | The upstream body only writes a Cursor .mdc rule, so the adapter replaces it with a Pi setup workflow. |
+| `sharpen` | `/skill:pistack-sharpen` | - | - | Verified end to end in Pi on Linux at pstack 0.15.36: it handed back four short sections and a rewritten prompt for a vague gateway task, left the decisions that were the user's open, and did not start the task. Since pstack 0.15.29 it hands back a rewritten prompt and does not do the task. Its body is prompt-only, with no tool, delegation, or executable, and it runs only when you type it. |
 | `tdd` | `/skill:pistack-tdd` | - | - | - |
 | `technical-writing` | `/skill:pistack-technical-writing` | - | - | - |
 | `typescript-best-practices` | `/skill:pistack-typescript-best-practices` | - | - | - |
 | `unslop` | `/skill:pistack-unslop` | - | - | - |
 
-### adapted (2)
+### adapted (6)
 
 | upstream skill | Pi skill | capabilities | executables | why |
 | --- | --- | --- | --- | --- |
+| `arena` | `/skill:pistack-arena` | `delegation` | `git` | The whole skill is spawning N candidate subagents plus a judge. Since pstack 0.15.36 the judge must come from a model family other than the parent's. The adapter maps the cross-judge pool to the `arena-cross-judge-pool` panel role, which uses `judgment`, then `general` while unset, so when the parent knows its model, the judge runs only when one of its entries is on another family. The status report and `check` warn when that pool is on one model. Otherwise arena skips the judge, picks the base alone, and says so. When the parent does not know its model, arena tries the pool in order anyway and says the family check did not run. Verified end to end in Pi on Linux at pstack 0.15.36 with pi-subagents: two candidates on the `judgment` and `general` roles, then a judge from the family other than the parent's, which scored them. The parent picked a base, took the fixes for two bugs from the other candidate, fixed a third that both shared, and finished with passing tests. It left the candidate worktrees for comparison. |
+| `create-formal-verification-skill` | `/skill:pistack-create-formal-verification-skill` | - | - | Manual invocation only; no delegation. It installs or runs the verification tool it chooses and temporarily breaks product code to prove the check. Generated skills belong under `.pi/skills/` in Pi. Verified on a Windows Node finite-state fixture; other toolchains need their own prerequisites. Since pstack 0.15.32, a generated TLA+ check tells the next agent to read its results with statechart, which has its own prerequisites. |
 | `create-verification-skill` | `/skill:pistack-create-verification-skill` | - | - | Only the generated skill's output path needs remapping to Pi's skill directory. |
+| `interrogate` | `/skill:pistack-interrogate` | `delegation` | `git` | Multi-model adversarial review is entirely one subagent per configured model. Since pstack 0.15.36 it picks adversaries the way arena picks runners, from the `interrogate reviewers` line, and gives each one its own worktree with the scope's uncommitted changes. Each adversary must prove a finding with a run, and the skill keeps only findings whose command it reruns and sees fail. It reports findings and applies no fixes, but adversaries write and run repro commands, and the skill reruns them, all with your permissions. A worktree is not a sandbox, so read each repro before it reruns, especially on code you do not trust. The rubric, the lead's judgment, and the code-quality lens are gone. Verified end to end in Pi on Linux at pstack 0.15.36 with pi-subagents: two adversaries on the `judgment` and `general` roles, from two model families, each in its own worktree, proved the same two real bugs, and the skill reran both repros before it reported them. It left the adversary worktrees in the temporary folder and named the commands that remove them. |
 | `ketchup` | `/skill:pistack-ketchup` | - | - | Read-only. Pi has no `/visualize` skill or image generation, so its visuals are Mermaid diagrams and screenshots that already exist. It checks PR and CI state only for work the chat touched. |
+| `show-me-your-work` | `/skill:pistack-show-me-your-work` | `delegation` | - | The mandatory cross-model review of the trail requires spawning a different-family subagent. Verified end to end in Pi on Linux at pstack 0.15.36 with pi-subagents: it kept a decision log the repository ignores, and its reviewer on another model family read the parent's Pi session file and checked each row against it. Its own scripts ran unchanged. |
 
-### dependency-gated (13)
+### dependency-gated (12)
 
 | upstream skill | Pi skill | capabilities | executables | why |
 | --- | --- | --- | --- | --- |
 | `architect` | `/skill:pistack-architect` | `delegation` | - | Phase B delegates to arena runners, so it cannot run without parallel subagents. |
-| `arena` | `/skill:pistack-arena` | `delegation` | `git` | The whole skill is spawning N candidate subagents plus a judge. |
 | `benchmark-checklist` | `/skill:pistack-benchmark-checklist` | - | `uptime`, `nproc` | Its setup step checks load with `uptime` and cores with `nproc`. macOS has no `nproc` without GNU coreutils, and Git Bash on Windows has no `uptime`. |
 | `blast-radius` | `/skill:pistack-blast-radius` | - | `git`, `gh` | Needs git and gh to read the diff, commits, and PR before any analysis. |
 | `correct` | `/skill:pistack-correct` | - | `git` | Mines commit history, then commits fixes and edits lint, CI, and agent instruction files. Run it on a branch you will review. |
 | `figure-it-out` | `/skill:pistack-figure-it-out` | `delegation` | - | Phase B fan-out and the architect/arena routing require parallel subagents. |
 | `how` | `/skill:pistack-how` | `delegation` | - | Every path spawns explorer or explainer subagents; nothing runs inline. |
-| `interrogate` | `/skill:pistack-interrogate` | `delegation` | `git` | Multi-model adversarial review is entirely one subagent per configured model. |
+| `maintain-formal-verification-skill` | `/skill:pistack-maintain-formal-verification-skill` | - | `git` | Verified end to end on a Windows Node finite-state fixture at pstack 0.15.28. Manual invocation only; no delegation. It diffs the covered code with git from the verify skill's sync commit, edits only the verification and the verify skill, and temporarily breaks product code to prove an updated check can still fail. In Pi, look for the verify skill under `.pi/skills/`; the verification tool needs its own prerequisites. |
 | `maintain-verification-skill` | `/skill:pistack-maintain-verification-skill` | `delegation` | - | Source wave launches one read-only subagent per feature file. |
 | `no-comments` | `/skill:pistack-no-comments` | `delegation` | `git` | Step 1 must spawn the comment-sicko agent; the skill only triages its report. |
-| `show-me-your-work` | `/skill:pistack-show-me-your-work` | `delegation` | - | The mandatory cross-model review of the trail requires spawning a different-family subagent. |
+| `recall` | `/skill:pistack-recall` | `delegation` | `git`, `gh` | Its core corpus is Cursor's on-disk transcript JSONL. The host mapping points it at this workspace's Pi session files instead. Verified end to end in Pi on Linux at pstack 0.15.36: in a fresh session it found the two earlier chats in the folder that holds `$PI_SESSION_FILE`, read their user messages, checked their claims against git and the code, and rebuilt the threads, problems, and next move. With two chats to read, it read them itself, so it did not fan out to subagents, and that step has not run in Pi. A run before the host mapping said to start from `$PI_SESSION_FILE` looked in the default folder instead, which a custom `PI_CODING_AGENT_DIR` had moved, and found nothing. |
 | `teach` | `/skill:pistack-teach` | `delegation` | - | It runs the how and why skills, both of which need subagents. |
 | `why` | `/skill:pistack-why` | `delegation` | `git`, `gh` | Default posture spawns one investigator subagent per evidence category plus a synthesizer. |
 
@@ -152,12 +370,12 @@ Lowering a tier needs one reproduction of the failure and a note saying what bro
 
 | upstream skill | Pi skill | capabilities | executables | why |
 | --- | --- | --- | --- | --- |
-| `automate-me` | `/skill:pistack-automate-me` | `delegation`, `structured-question` | `git`, `gh` | Mining step depends on Cursor transcript files and the built-in create-skill skill, with no Pi equivalent. |
+| `automate-me` | `/skill:pistack-automate-me` | `delegation`, `structured-question` | `git`, `gh` | Its mining step reads this workspace's transcripts. The host mapping points it at this workspace's Pi session files, which use a different format. Verified end to end in Pi on Linux at pstack 0.15.36: it read only this workspace's sessions, told the parent chat from its subagents' files, found no stated preference there, and changed nothing. The built-in create-skill skill it drafts with has no Pi equivalent, and that step has not run in Pi. |
+| `ketchup-video` | `/skill:pistack-ketchup-video` | - | - | New in pstack 0.15.32. One end-to-end Pi run on native Windows drew its slides and rendered an mp4 with `ffmpeg` alone, before pstack 0.15.36 added subtitles. Verified end to end in Pi on Linux at pstack 0.15.36: it drew five slides as SVG, rendered a 35-second 1280x720 mp4 with `ffmpeg`, with each subtitle burned into a strip below its slide, and checked frames from the file. Manual invocation only; no delegation or structured question. It follows ketchup, read-only, but shows what happened as a short slide video with no audio, rendered outside the repository, with the waiting calls as text under it. Since pstack 0.15.36 it burns a one-line subtitle into each slide's frames, in a strip below the slide, and measures each slide's hold by matching the rendered frames to the slide. Its body names no renderer, so it needs whatever video tool the session has, such as `ffmpeg`, and Pi has no image generation. Its reply embedded the video as an HTML `video` tag with the file path, and whether a Pi client plays it inline is unverified. When the render fails, it says so in one line and gives only the calls. |
 | `poteto-help` | `/skill:pistack-poteto-help` | - | - | Its answers describe Cursor setup, the slash menu, and Custom Modes. A request for work runs poteto-mode, which is experimental. It asks a multiple-choice question only when the need is unclear. Its README and guide links resolve under the status report's plugin directory. |
-| `poteto-mode` | `/skill:pistack-poteto-mode` | `delegation`, `structured-question` | `git`, `gh` | Sticky-mode hosting plus references to Cursor built-in and plugin skills only partially map to Pi. |
-| `recall` | `/skill:pistack-recall` | `delegation` | `git`, `gh` | Core corpus is Cursor's on-disk transcript JSONL, so only the git/gh and shared-record half survives. |
-| `reflect` | `/skill:pistack-reflect` | `delegation` | - | Transcript mining and create-skill routing are Cursor-specific, though the digest fallback partly works. |
-| `sharpen` | `/skill:pistack-sharpen` | - | - | New in pstack 0.15.25 and not yet run end to end in Pi. Its body is prompt-only, with no tool, delegation, or executable, and it runs only when you type it. |
+| `poteto-mode` | `/skill:pistack-poteto-mode` | `delegation`, `structured-question` | `git`, `gh` | Sticky-mode hosting plus references to Cursor built-in and plugin skills only partially map to Pi. Since pstack 0.15.36 the Orchestrate playbook calls no scripts, because the `orch` helpers are gone, and watches PRs through event subscriptions only when the harness has them. Pi has none. Its Project tracker and Project store, and forking a worker with its built state, have no Pi equivalent; the host mapping says what to do instead. Verified end to end in Pi on Linux at pstack 0.15.36 with pi-subagents and a question tool: Orchestrate ran a two-unit program in a linked worktree, with an owner per unit on its own branch and worktree, a verifier from another model family at the owner's head, and local merges. It kept the tracker and store in a folder it added to the exclude file Git resolved for the worktree, and handed state to new agents instead of messaging old ones. Its other playbooks and sticky mode were not rerun. |
+| `reflect` | `/skill:pistack-reflect` | `delegation` | - | Its reviewers read the active transcript, and the host mapping points them at the current Pi session file. Verified end to end in Pi on Linux at pstack 0.15.36 with pi-subagents: three reviewers on two model families and a synthesizer read the session file, and the run found a regression the earlier review missed. When told to apply two edits, it copied the upstream skill from the plugin directory to a Pi skill location under a new name and edited only the copy. Its create-skill routing for a new skill is Cursor-specific and has not run in Pi. It never opens a PR or pushes. |
+| `statechart` | `/skill:pistack-statechart` | - | `node`, `sh`, `dirname`, `sed` | Lowered from dependency-gated at pstack 0.15.34, because its new scripts crash on native Windows, a certified platform. There, the launcher starts `/bin/sh` by that path to stop TLC's process group, Node cannot start it even when `sh` is on PATH, and with no error handler the run exits 1 with `spawn /bin/sh ENOENT`. It writes no output and leaves an empty hidden staging folder beside the output folder and an empty `statechart-` folder in the temporary folder, so delete those by hand. `/pistack-check` still clears it there, because the gates are found. Use it from Linux, macOS, or WSL. Verified end to end on a Linux checkout fixture at pstack 0.15.34, and again at pstack 0.15.36, where it found the uncapped refill in a token bucket as the shortest path to a broken rule. The Windows end-to-end evidence from pstack 0.15.32 and 0.15.30 describes the scripts it replaced. Manual invocation only; no delegation or structured question. `scripts/statechart` is a POSIX `sh` launcher for TypeScript scripts, and it runs `dirname` and `sed` on every start. It runs the scripts under Node 22.18 to 22.x or Node 23.6 or later, then Bun 1.1.5 or later, then Deno 2.0 or later, and exits with code 127 when none is found. The prerequisite check gates on `node` but cannot check its version. The launcher does: with only an older Node on PATH, it names the versions it needs and exits 127. The command checks a TLA+ spec with TLC and writes `report.md` and TLC output to a new or empty `--out` folder, `SPEC-chart` beside the spec by default, and refuses a folder that is not empty. It also writes `chart.mmd`, except when TLC finds more than 500 states and no rule breaks. It stages its work in a hidden folder beside the output folder and in the system temporary folder, and deletes both. TLC runs from `TLA2TOOLS`, the path to a downloaded `tla2tools.jar`, with the binary in `JAVA` or `java` from PATH. Without `TLA2TOOLS`, it uses TLC 1.7.4 and Java temurin-25 from `mise`, and installs whichever is missing with `mise`, which needs the network. `JAVA` then changes only the binary that runs TLC, and does not skip the `mise` lookup or install of Java. Either `mise` or `TLA2TOOLS` with Java works, so neither is gated, and the script names what is missing when neither is set up. It imports the `--view` module as JavaScript with full process permissions, so review an existing view before you run it. Since pstack 0.15.34 the scripts render no images and do not run `npm`. For an image, the body has the agent install `pele@1.9.0` with `npm` once, outside the repository, which needs `npm` and the network, and render SVG with it. The body does not ask for `--ignore-scripts`, so pass it, and rendering still imports Pele with full process permissions. Run it in a scratch folder outside the repository. Git for Windows bundles `sh`, `dirname`, and `sed`, but not `node`, `mise`, or Java. |
 | `swarm` | `/skill:pistack-swarm` | `delegation` | - | Cloud background workers and cloud_base_branch have no Pi mapping; only local fan-out approximates it. |
 
 ### unsupported (1)
@@ -206,8 +424,10 @@ through `delegate_task`. That run is the evidence the tier rules above require.
 
 ## Skills the adapter replaces
 
-`setup-pstack` writes a Cursor `.mdc` rule and nothing else, so the adapter substitutes its own
-body and publishes it as `/skill:pistack-setup`. The upstream skill stays represented, and the
+`setup-pstack` writes a Cursor `.mdc` rule, so the adapter substitutes its own body and
+publishes it as `/skill:pistack-setup`. Upstream's optional closing offers to run
+`create-verification-skill` and `create-formal-verification-skill` are left out of the Pi body;
+both skills stay available by name. The upstream skill stays represented, and the
 wrapper frontmatter records `pistack-upstream-skill: setup-pstack`.
 
 ## Unknown skills