setup-statuslisted

<instructions> # Setup Status Read-only cross-analysis over every **setup skill** in the brewcode suite. It answers one question: *what is already set up in this project, what drifted, what was never installed* — and hands back the exact command to run for each row. **This skill writes nothing.** No file is created, edited or deleted; `allowed-tools` carries no `Write`, no `Edit`, no `Agent`. Every probe is an existence check, a `cmp`, or a one-line grep. ## Why it does not run the setups Each setup skill is an interactive generator: it fans out subagents, analyses the repo and asks the user real questions. Running two of them back-to-back in one session degrades both — the context fills with the first one's analysis, and the second one's questions get answered against stale findings. So the correct flow is: > **This skill reports. The user runs each setup by hand, ideally one per fresh session.** There is no `--run`, no `--fix`, no auto mode, and no plan to add one. If the user asks for one, say this paragraph and print the run-list instead. **Arguments:** `$ARGUMENTS` — empty = full report. A plugin name (`brewcode`, `brewtools`, `brewdoc`) filters to that plugin's rows. A skill name (`semble-setup`, `docsync`, `task board`) filters to that one row and prints its detection rule in full. Unrecognised text = full report. --- ## Two questions, two signals Every setup artifact in a project carries a `version` — the plugin version that produced it. The field contract