tpu_performance_autoresearch_wiki: Skill for Claude Code

You are stopping the autoresearch loop cleanly. Follow this sequence — do not abbreviate.

Step 1 — Stop the loop

Step 1·0 — Final audit gate (BLOCKING — before the watcher is disarmed)

You are the agent the watcher supervises; you may not end your own supervision unaudited. Dispatch the process-auditor SYNC over the closing delta (the stop/at-ceiling claim, retrospective, and evidence table included). Then:

• stop blocked / FABRICATION finding → ABORT /stop-experiment. The watcher stays armed; apply the corrections and return to the loop (kernel family: the failing gate is the next K2 input). Exception: a user-ordered infrastructure stop making NO at-ceiling claim converts to a PAUSE (Stop rule's PAUSE ≠ STOP) instead of aborting — record the resume state and continue shutdown. A PAUSE claims no close, so the .stop-authorized requirement does NOT apply to it: disarm is permitted (the pause marker records the family OPEN; LINT's unauthorized-stop check keys on clean-close/at-ceiling markers only — without this carve-out a paused session could never disarm and the revive service would fight the operator's pause).
• ALL-CLEAR (or only non-blocking findings, applied) → the auditor writes <family>/pallas/.stop-authorized (its ALL-CLEAR line + cursor SHAs). VERIFY THE FILE EXISTS before proceeding — test -e <family>/pallas/.stop-authorized. No file = the audit did not complete clean = you may NOT proceed (wait for it or apply its findings; dispatching the audit is not the gate — its written authorization is). You may NEVER create this file yourself — that is fabrication-class and voids the close. Also record the auditor's report line verbatim; Step 6's marker cites it. A marker without a matching .stop-authorized is an unauthorized stop (LINT voids + reopens). Proceed to the disarm.

Step 1·1 — Disarm the watcher

Only after Step 1·0 passes AND <family>/pallas/.stop-authorized exists on disk (or Step 1·0 resolved to a PAUSE — no close claimed), disarm the Step 9·0 process watcher — the persistent, self-rescheduling process-auditor task that /start-experiment armed at launch. Cancelling the watcher task at ANY other moment — including as "teardown hygiene" while an audit is still running — is a process violation that voids the close (the 2026-07-21 cohort's signature failure: three sessions cancelled their auditor mid-final-audit and closed unaudited). Its revive service would otherwise wake the session back up after this clean shutdown: