0.9.86

The upstream pin moves from 997ffc7 to 99743e9, upstream v0.15.25, 15 pstack commits. /in-your-own-words plays back the user's goal and the problem before work starts, and /sharpen aims a task the way a top expert would without overspecifying it. /poteto-help routes to both. /ketchup answers in about 150 words built on real visuals, and the autopilot ticks and replies catch the operator up through it. principle-fix-root-causes proposes a cheap always-on signal after a deep dig. principle-attack-the-premise and three other principles state their rules as reasoning, and four skills drop marginal sections. The package now carries 39 public skills and 24 principles.

poteto-mode gains upstream's rule to match each subagent's effort to the job, and the skills that spawn subagents point at it. On Claude Code the rule moves the effort level through the Reasoning effort section's @level values and effort agents. Fast mode is a session setting on Claude Code, so a spawn never changes its speed. Model fallbacks in arena and interrogate go by model name as before. When a delegate agent has to find the skill itself, it picks the newest install by .claude-plugin/plugin.json; a substitution rule and a denylist token keep upstream's .cursor-plugin/plugin.json out of the port.

Upstream rewrote the Autopilot-full, Autopilot-stack, and Shipping playbooks as rules with their reasons. The port takes the new text and keeps its own policy inside it. In Autopilot-full, owners stop at merge-ready, the operator clicks every merge, the program's size waits for the operator's go above three owners, and a PR stops at two fix-forwards. Upstream now runs the full swarm once and lets trunk defects pass without gating the PR, which the port's fork used to add, so those lines are upstream's. Autopilot-stack keeps the verdict record, pending-merge cancellation, and leased pushes. Shipping keeps landing under a service-enforced head condition, arming auto-merge only behind enforcing repository rules, ship-pr cancellation before any chain change, the confirmed landing, and the watcher's blocker routing, now inside upstream's six steps. principle-attack-the-premise takes upstream's text, which now covers the port's falsifying-check line, and its fork is gone. principle-test-behavior-not-implementation keeps one port line, on constant pins.

Orchestrate no longer uses Graphite. orch frontier set walks the PR base chain from the checkout's current branch through gh, or through Origin's CLI with --forge origin, so gt drops out of the dependency table in docs/reference.md, the Pi equivalence table, and the Codex, Pi, and Copilot mappings. The port keeps its guards on the new code: frontier SHAs come from exact refs/heads/<branch> refs, the current branch is read from the full HEAD ref so a same-named tag cannot shadow it, the gh chain keeps only pull requests whose head repository is the one the current branch pushes to, so a stack opened from your fork resolves while another fork's same-named branch stays out and is named in the error when it is the only match, each gh pr list call lists up to 1000 pull requests instead of gh's 30, forge calls run without an environment override under a 60-second SIGKILL timeout, and tests inject a fake forge through the store's forgePaths option. The guards for Graphite's output went with the code they guarded. watch-pr reads a Code Review Gate check that concludes ACTION_REQUIRED as the owner-approval gate, as upstream now does.

/ketchup asks for charts rendered from the data where upstream names Cursor's /visualize command, and the sync denylist now rejects /visualize.

New substitution rules translate upstream's effort sentence, the reworded cloud-agent and driver-skill sentences, the "re-reads from trunk" tick, and the orchestrate worker placement, so the next sync derives those lines without a conflict.

Measured in two runs of bun tools/sync.mjs pstack. The step to c86f349 merged clean: 4 updated, 1 added, 1 merged. The step to 99743e9, over 106 files with 37 excluded, left 60 unchanged, updated 24, added 1, merged 6, and wrote 15 conflicts, each resolved by hand from upstream's new text plus the lines its forks.json entry names.