add-unit-testlisted

## Step -1 — Resolve where the rule books and conventions come from This skill runs **with or without** a prior `setup-test-context`. **Resolve the plugin templates root once, unconditionally** — you also pass it to every subagent, because subagents cannot resolve it themselves. The bundled rule books sit two directories above this `SKILL.md`, under `resources/templates`. Prefer bash injection at load time: !`echo "${CLAUDE_SKILL_DIR}/../../resources/templates"` Call the result `PLUGIN_TEMPLATES`. If that line did not expand to a real absolute path (it still shows a literal `${CLAUDE_SKILL_DIR}`), run `echo "$CLAUDE_SKILL_DIR/../../resources/templates"` with the Bash tool; if `$CLAUDE_SKILL_DIR` is empty too, ask the user for the `test-authoring` plugin install path. The Read tool normalises the `../..` segments. **If it still cannot be resolved, degrade — loudly — rather than stopping.** The sibling-learning path does not depend on the plugin, so tests can still be written; what is lost is the rule books, and that loss must be visible rather than silent. Print this **as prose in your reply**, not merely as reasoning, so it lands in the transcript and the dashboard: ``` ⚠ Rule books unreachable — running in DEGRADED mode. Could not resolve the test-authoring plugin path, so the shared rule books are not loaded: fix rules, the verifier's check sequence, the fix protocol, SUT analysis. Tests will still be written from the nearest sibling, but the anti-gaming guardra