FM-431: Shear fixes — scratch delete, setup guide, gitignore

.gitignore

@@ -3,4 +3,5 @@ node_modules/
 __pycache__/
 *.pyc
 e2e/.run/
-.tmp-*/
+.tmp*/
+_fm*-proof*

docs/AGENTS.md

@@ -13,6 +13,7 @@ Human docs for this plugin. First-run is the README (`omp plugin link ./` and Cl
 - README owns first-run for both hosts: `omp plugin link ./` and Claude plugin install (`marketplace add` + `pstack@pstack`, or `claude --plugin-dir ./`). Do not add `docs/getting-started.md` or teach `omp -e` as an install path.
 - README may link the numbered guide.
 - Guide on-disk skill links use `skills/do-*` so they resolve in this tree. Slash names in guide prose may still say `/how`; the live omp surface is `/skill:do-how`, Claude is `/pstack:do-how`. `/poteto-mode` stays unprefixed on omp.
+- Setup guide (`01-setup.md`) matches `do-setup-pstack`: `/model` Roles and `/agents` only. Do not teach `pstack-models.mdc`.
 - Operator install matches the root rail Native omp and Native Claude Code contracts.
 
 ## Work Guidance

docs/guide/01-setup.md

@@ -41,20 +41,18 @@ Run:
 
 On Claude Code the same skill is [`/pstack:do-setup-pstack`](../../skills/do-setup-pstack/SKILL.md).
 
-[`/skill:do-setup-pstack`](../../skills/do-setup-pstack/SKILL.md) detects the models you have access to, shows you each role (code delegates, judgment, the review panels), and asks what you want. Answer the questions. It writes `~/.cursor/rules/pstack-models.mdc`, a small rule every pstack skill reads.
+[`/skill:do-setup-pstack`](../../skills/do-setup-pstack/SKILL.md) lists each plugin agent and the `@role` it uses. Routing lives in `/model` → Roles and each agent's `model: "@role"` line, or an override in `/agents`. The skill writes nothing. Re-run it to re-list.
 
-You only override what you care about. A role with no line in the rule keeps the skill's default. To restore a default later, delete that role's line, or just run `/skill:do-setup-pstack` again.
+Want a different concrete model for a role? Open `/model` → Roles and change that `@role`. Want one agent on a different role or a concrete selector? Open `/agents` and override that agent. New `task` calls pick it up.
 
-You might be wondering what happens if you use Auto. Set a role to `inherit-parent` or `auto` and pstack omits the subagent `model` field, so the subagent inherits your parent chat model. Both values mean the same thing, and neither is a model slug. For a panel role the value is a list, and one subagent runs per entry, so the list length sets the panel size. Setup also configures `swarm workers`, the default model for every `/skill:do-swarm` worker unless a race names a model for each arm.
+N parallel models is not available from one agent definition. Diversity is prompt, path, or label unless you change that agent's `model` in `/agents`.
 
 ## Accept the verification offer, or don't
 
 At the end of setup, `/skill:do-setup-pstack` looks for a way to prove app behavior in your project, either a `verify-*` skill or an existing harness. If it finds neither, it offers once to generate one with [`/skill:do-create-verification-skill`](../../skills/do-create-verification-skill/SKILL.md).
 
 Say yes and it writes `.cursor/skills/verify-<app>/`, a project-local skill that teaches agents to drive your app the way a user does. It proves the skill works once before handing it over. Say no and setup moves on. You can run `/skill:do-create-verification-skill` yourself any time. [Verify and ship](./06-verify-and-ship.md#create-a-project-verification-skill) covers when it earns its place.
 
-After setup, start a new chat. The model rule applies to new sessions.
-
 ## Run your first task
 
 Pick something real but small, and describe it the way you'd describe it to a colleague:

docs/guide/10-recipes-and-pitfalls.md

@@ -85,7 +85,7 @@ That's the whole prompt. [`/bro`](../../skills/do-bro/SKILL.md) restates the las
 - **Parallel agents in one worktree.** They overwrite each other and the diff becomes archaeology. Say "own worktree per attempt" and the isolation is free.
 - **Using `/arena` for coverage.** `/arena` repeats one design or code brief, then picks a base and grafts the best parts. `/swarm` partitions slices or declared race arms and aggregates one report.
 - **Accepting every review comment.** Bots and humans both file real catches and noise in one list. `/interrogate` sorts findings into act-on and dismissed buckets with reasons, and you can override either way.
-- **Treating `auto` as a model slug.** `auto` and `inherit-parent` mean "omit the model field so the subagent inherits the parent chat model." [Setup](./01-setup.md) covers the roles.
+- **Editing routing files by hand.** Change a role in `/model` → Roles, or override one agent in `/agents`. Do not pass `model` on `task`. [Setup](./01-setup.md) covers it.
 - **Reporting success off a green build.** A build proves it compiles. Ask for the real command, flow, stored value, or profile, and expect the evidence in the reply.
 - **Writing a `SKILL.md` freehand.** Route it through the [Authoring or modifying a skill playbook](../../skills/do-poteto-mode/playbooks/authoring-a-skill.md) so validation and review happen.
 

e2e/AGENTS.md

@@ -7,7 +7,7 @@ Prove the plugin without chat-only guesses. Static doctor/lint + Vitest on every
 ## Ownership
 
 - `run.py` — live RPC evals; `--skip-rpc` is static-only
-- `ci_static.py` — doctor, frontmatter, size, product pack, Claude plugin layout
+- `ci_static.py` — doctor, frontmatter, size, product pack, Claude plugin layout, packaging scratch
 - `unit/` — Vitest helpers and tests
 - `ci-shims/` — `node:fs` stub for `tsc` without `@types/node`
 
@@ -21,6 +21,7 @@ Prove the plugin without chat-only guesses. Static doctor/lint + Vitest on every
 - Do not keep a repo `.omp/skills` symlink. `static_install_docs` and `unit/product-capabilities.test.ts` assert filesystem absence, not only README text.
 - Claude components stay at plugin root. `.claude-plugin/` may hold `plugin.json` and `marketplace.json` only — not `skills/`.
 - Official skill vendor-sync tests (`unit/sync-skills.test.ts`) stay offline (`--from` fixture). Do not clone `cursor/plugins` on CI.
+- Do not keep `.tmp-*` dirs or `e2e/_fm*-proof*` in the tree. Gitignore those names. `ci_static.py --quality` packaging asserts absence.
 
 ## Work Guidance