claude-harness-canary

# Claude Harness Canary Run all three groups serially against the currently installed Claude Code. Take no arguments and do not offer group selectors. Target 5–8 minutes, but preserve bounded waits and evidence over that estimate. Keep this canary core-only, current-Claude-only, interactive-tmux-only, and loaded through `--plugin-dir`. Never add it to CI, release commands, or `$pre-release-review`. ## Shared probe prerequisite Reuse the installed `$probe` lifecycle. Before creating canary state, read its active `SKILL.md` and require all of these properties: - real interactive Claude in tmux, never `claude -p`, Codex, or another PTY; - no interactive `--no-session-persistence`; - `tmux pipe-pane` starts before any input; - one bounded readiness phase that detects the trust dialog, accepts it only when present, handles only explicitly recognized startup onboarding, and waits for the normal prompt; - a unique output-only completion nonce whose complete value is never contiguous in the injected prompt; - completion accepted only from assistant output after the requested evidence, never prompt echo; - one bounded wait per canary action; - teardown with `rm -r` only after validating the exact scratch path. If any property is absent, stop before preflight and report: `PREREQUISITE BLOCKED — update the local $probe protocol` Do not recreate generic tmux lifecycle rules locally or hand-roll a fallback. Extend the probe lifecycle only for the multi-action assertions below. ##...