skill: name the terminal case — no launcher at all is a refusal

The dispatch rule covered sh-then-ps1 but left two edges implicit: a host
with NEITHER launcher (now explicitly a refusal to report, not a license
to improvise), and the script-less install on a Windows host — the
ZeroClaw-on-Windows combination — which needs the ps1-from-checkout
command spelled out, not derived.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

.agents/skills/peltier/SKILL.md

@@ -39,14 +39,18 @@ availability, not OS: try `sh` first; if the **launcher itself** is missing
 (`sh: not found` — a launch failure, not a refusal), run the PowerShell entry
 point instead. A `STATUS=refuse` from either is **final**: never run the
 second entry point hoping for a different answer — they are kept
-byte-identical in CI precisely so there is no different answer.
+byte-identical in CI precisely so there is no different answer. And if
+neither launcher exists on this host, that is itself a preflight refusal:
+report it; do not improvise a substitute.
 
 Some harnesses block script files inside skills, so your installation may
-carry no `scripts/` directory. The script still exists exactly once — in the
+carry no `scripts/` directory. Both entry points still exist exactly once —
-peltier checkout this skill drives (which you need anyway; it is where
+in the peltier checkout this skill drives (which you need anyway; it is where
-`bench-runner` lives). Run it from there:
+`bench-runner` lives). Run one from there, same dispatch rule:
 
     sh "$PELTIER_HOME/.claude/skills/peltier/scripts/preflight.sh"
+    # or, sh launcher missing on this host:
+    powershell -NoProfile -ExecutionPolicy Bypass -File "$env:PELTIER_HOME\.claude\skills\peltier\scripts\preflight.ps1"
 
 Never transcribe or re-implement the preflight logic inline; if you cannot
 locate a checkout to run it from, that IS a preflight refusal — report it.

.agents/skills/peltier/references/verify.md

@@ -9,11 +9,14 @@ faster. Find out. Works on any pair of shell commands, in any language.
     # `sh` launcher missing ("sh: not found" — a launch failure, NOT a refusal)?
     # same contract, byte-diffed against the sh version in CI:
     powershell -NoProfile -ExecutionPolicy Bypass -File <skill-dir>/scripts/preflight.ps1
-    # installation carries no scripts/ (script-blocking harness)? run from the checkout:
+    # installation carries no scripts/ (script-blocking harness)? run from the
+    # checkout — either entry point, same dispatch rule:
     sh "$PELTIER_HOME/.claude/skills/peltier/scripts/preflight.sh"
+    powershell -NoProfile -ExecutionPolicy Bypass -File "$env:PELTIER_HOME\.claude\skills\peltier\scripts\preflight.ps1"
 
 A `STATUS=refuse` from either entry point is final — do not run the other one
-looking for a different answer.
+looking for a different answer. If no entry point can launch at all, that too
+is a refusal: report it rather than improvising a substitute.
 
 Read the `key=value` output; you need `BENCH_RUNNER` and `PIN_SUPPORTED`. A
 refusal ends the **claim**, not the work — report the reason verbatim and do

.claude/skills/peltier/SKILL.md

@@ -39,14 +39,18 @@ availability, not OS: try `sh` first; if the **launcher itself** is missing
 (`sh: not found` — a launch failure, not a refusal), run the PowerShell entry
 point instead. A `STATUS=refuse` from either is **final**: never run the
 second entry point hoping for a different answer — they are kept
-byte-identical in CI precisely so there is no different answer.
+byte-identical in CI precisely so there is no different answer. And if
+neither launcher exists on this host, that is itself a preflight refusal:
+report it; do not improvise a substitute.
 
 Some harnesses block script files inside skills, so your installation may
-carry no `scripts/` directory. The script still exists exactly once — in the
+carry no `scripts/` directory. Both entry points still exist exactly once —
-peltier checkout this skill drives (which you need anyway; it is where
+in the peltier checkout this skill drives (which you need anyway; it is where
-`bench-runner` lives). Run it from there:
+`bench-runner` lives). Run one from there, same dispatch rule:
 
     sh "$PELTIER_HOME/.claude/skills/peltier/scripts/preflight.sh"
+    # or, sh launcher missing on this host:
+    powershell -NoProfile -ExecutionPolicy Bypass -File "$env:PELTIER_HOME\.claude\skills\peltier\scripts\preflight.ps1"
 
 Never transcribe or re-implement the preflight logic inline; if you cannot
 locate a checkout to run it from, that IS a preflight refusal — report it.

.claude/skills/peltier/references/verify.md

@@ -9,11 +9,14 @@ faster. Find out. Works on any pair of shell commands, in any language.
     # `sh` launcher missing ("sh: not found" — a launch failure, NOT a refusal)?
     # same contract, byte-diffed against the sh version in CI:
     powershell -NoProfile -ExecutionPolicy Bypass -File <skill-dir>/scripts/preflight.ps1
-    # installation carries no scripts/ (script-blocking harness)? run from the checkout:
+    # installation carries no scripts/ (script-blocking harness)? run from the
+    # checkout — either entry point, same dispatch rule:
     sh "$PELTIER_HOME/.claude/skills/peltier/scripts/preflight.sh"
+    powershell -NoProfile -ExecutionPolicy Bypass -File "$env:PELTIER_HOME\.claude\skills\peltier\scripts\preflight.ps1"
 
 A `STATUS=refuse` from either entry point is final — do not run the other one
-looking for a different answer.
+looking for a different answer. If no entry point can launch at all, that too
+is a refusal: report it rather than improvising a substitute.
 
 Read the `key=value` output; you need `BENCH_RUNNER` and `PIN_SUPPORTED`. A
 refusal ends the **claim**, not the work — report the reason verbatim and do