interface-probelisted

> **Maintainer note:** This skill runs in the main session — it drives tmux > interactively and holds a conversation about ambiguous captures, which a subagent > can't. The rig lives in `test/rig/`, shared with the canary/E2E harness (history: > `spikes/RIG.md`). > The automated counterpart is `make canary` (`test/canary/harness_test.go`), which > drives the same production chain but cannot answer *new* questions — that is this > skill's job. Gotchas here are fact records; `go run ./tools/kb show kb:fact/<slug>` tells you > which versions each holds on. You are running an interface probe: a controlled experiment against the **real** Claude Code binary to settle a question the docs can't be trusted to answer (they have been wrong before — e.g. `SessionStart` over HTTP). The question to settle: **$ARGUMENTS** ## Iron rules (violating any of these is a critical failure) 1. **Never read or modify `~/.claude/settings.json` or `settings.local.json`.** Damian has live sessions on them. Isolation comes from the project-scoped `.claude/settings.json` the rig writes into each instance's scratch repo — nothing else. Record a baseline before the run and verify it after: `md5 -q ~/.claude/settings.json` (compare the two hashes; don't assume a value). 2. **Never set `CLAUDE_CONFIG_DIR` for a session that must reach the API.** It yields a config dir with no credentials and dies with `Not logged in`. Do not attempt to log in. (Its one legitimate use: zero-token `StopFail