scripts/install.mjs reads install.json. skills and agents list the repo paths to link and the directories to link them into. hooks and env have the same shape as the keys of the same name in ~/.claude/settings.json.

• It links each path on its own, named after its last segment, so skills and agents from other places stay beside them. It tries a symbolic link first. On Windows without the right to make one, it makes a directory junction for a skill and copies an item it cannot link. --copy copies every item.
• It replaces a link that points somewhere else. It leaves a real file or directory it did not make, reports the conflict and exits 1.
• It merges hooks and env into ~/.claude/settings.json. It removes only the hook entries that run pstack-hook.mjs or the older session-context.mjs, appends the groups from install.json and sets each env variable. Before it writes, it copies the old file to settings.json.bak-<time>.
• --dry-run prints each change prefixed with would and writes nothing.
• --opt-in agents also links the skills into ~/.agents/skills, which Codex and other agents read.

Run /setup-pstack once to choose the models each role uses. To update, run git pull in the clone. The links point into it, so a changed skill is live on its next read. Run the installer again when install.json changes. A second run changes nothing that is already in place.

To install by hand on macOS, Linux or Git Bash:

repo=~/pstack-for-cc
paths() { (cd "$repo" && node -p "require('./install.json').$1.paths.join(' ')"); }
mkdir -p ~/.claude/skills ~/.claude/agents
for p in $(paths skills); do ln -s "$repo/$p" ~/.claude/skills/; done
for p in $(paths agents); do ln -s "$repo/$p" ~/.claude/agents/; done

In PowerShell, which needs Developer Mode or an administrator shell to make a symbolic link:

$repo = "$HOME/pstack-for-cc"
$manifest = Get-Content -Raw "$repo/install.json" | ConvertFrom-Json
foreach ($group in $manifest.skills, $manifest.agents) {
	foreach ($into in $group.into) {
		foreach ($path in $group.paths) {
			$link = Join-Path ($into -replace '^~', $HOME) (Split-Path $path -Leaf)
			New-Item -ItemType SymbolicLink -Path $link -Target (Join-Path $repo $path)
		}
	}
}

Then open ~/.claude/settings.json, remove any hook entry that runs pstack-hook.mjs, and copy each event under hooks and each variable under env from install.json into it.

The harness is eval/parity. It runs five synthetic tasks in sealed sandboxes, with every worker on Opus 5.5 at medium effort, across five arms:

• B. Claude Code with this port, three runs per task. The runs used an earlier commit whose installed files differ from this tree only in the check-port.mjs maintenance script and in test files and fixtures.
• E. Claude Code with michael-denyer/pstack-claude at commit c02fd49, installed as its Claude Code plugin, three runs per task. It had 645 stars on 2026-09-27.
• A. Cursor with upstream pstack v0.15.2, two runs per task.
• N. Claude Code with no pstack, three runs per task.
• C. Cursor with no pstack, two runs per task.

Two judges grade each reply against a written rubric for each behavior, and a script decides the behaviors that are plain facts. Each cell is the passing units over the graded units. "Split" counts the units the two judges disagreed on, which are left out of the count. A dash means the arm had no unit to grade.

The raw counts and intervals are in report.json. node scripts/chart.mjs draws the chart from it. Each run's judge packet, seal and verdicts are under eval/parity/results/s5/runs/.

To run the comparison again, you need Windows with cursor-agent installed by its Windows installer, Claude Code, and Cursor usage for the Cursor arms. --init clones pstack-claude once, so it needs the network. Run the tick until --status shows every run and judgment done:

node eval/parity/parity.mjs --init --stamp s5 --tree B=HEAD --tree E=c02fd4922b25ee005f42042463d741d236c2c35e
node eval/parity/parity.mjs --tick --stamp s5
node eval/parity/parity.mjs --status --stamp s5
node eval/parity/parity.mjs --report --stamp s5

--report writes report.md and report.json under pstack-parity/s5 in the temp directory.

install.json decides what a machine installs, so a file can sit in the repo without reaching ~/.claude.

Run these from the repo root:

node --test $(git ls-files '*.test.js')
node skills/poteto-mode/scripts/check-port.mjs skills agents
node scripts/drift.mjs --check

The first runs every test, the second prints 0 findings, and the third prints DRIFT.md is current.

• check-port.mjs fails on text that still assumes a feature of the plugin's original host, such as a todolist, /goal, readonly or /tmp, and on a shipped model default outside the known tiers. An owner can list their own project names, one regex per line, in .port-check-terms at the repo root, and the check then flags any file that names one. The file is ignored by git.
• drift.mjs --check compares each file against the three history tags. It fails when a changed file has no drift class in scripts/drift.mjs or when DRIFT.md is stale. It needs those tags in the clone.
• .github/workflows/check.yml runs all three on every pull request, with the Bun tests for the orch and watch-pr scripts.

To prove the hook in real sessions, run bash skills/verify-pstack/scripts/drive.sh after installing. It starts three headless sessions and prints eight verdicts: hook-context, mode-reminder, step-ledger, gate, action-gate, reader, task-tools and port-clean. It exits 0 only when all eight read VERIFIED. skills/verify-pstack/SKILL.md says what each verdict checks.

node scripts/audit-transcripts.mjs --skills ~/.claude/skills <session.jsonl> reports how a recorded session used pstack. node scripts/replay-demands.mjs <session.jsonl> prints each ask the hook would raise over a recorded session.

The history starts with three tagged layers, and every later change sits on top of them.

DRIFT.md lists every file that changed from upstream, by layer, with the reason for each change. To record a new change, add a class to the last layer in scripts/drift.mjs, commit, run node scripts/drift.mjs, and commit DRIFT.md.

Diff pstack/ in cursor/plugins from 032be14 to the new commit and apply the changes you want under the same paths. Then run node skills/poteto-mode/scripts/port-codemod.mjs for the mechanical rewrites, fix what check-port.mjs still reports, and record the drift.