Circuit Surface Test

You are about to act as a QA tester for the Circuit plugin. The user has asked you to walk the entire user-facing surface of the plugin in a specific host (Claude Code or Codex), looking for regressions, broken progress rendering, missing summaries, and other defects a real user would hit.

This skill is a protocol, not a script. It tells you what to test, in what order, what counts as a finding, and what to put in the report. The source inventory and two host-specific checklists in references/ carry the per-command details.

Argument: which host

The user's argument tells you which plugin package to test: