docs(confidence): treat a stated threshold as a gate, not a report field

The skill already required naming what keeps the number below 100 and what would close the gap. The failure sat one step later: a triage invocation asked to investigate to 95 percent confidence and at most 5 percent break risk, the answer came back at 88 and 6, and the work simply moved on. The operator then had to ask three separate times how to move the numbers.

A number the operator named is now a gate on the work rather than a field in the report. A block that misses it is a work item: name the cheapest evidence that closes the gap, go get it, re-measure. A miss is reported only when that evidence is genuinely out of reach, and then it says which.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

skills/confidence/SKILL.md

@@ -28,6 +28,14 @@ Calibration rules:
 - Static analysis alone caps at the low nineties; only executed evidence
   (test, reproduction, live probe) justifies more.
 
+## When a threshold was stated
+
+A number the operator named ("95% confidence, break risk ≤5%") is a gate on the
+work, not a field in the report. A block that misses it is not finished output,
+it is a work item: name the cheapest evidence that closes the gap, go get it,
+re-measure. Report a miss only when that evidence is genuinely out of reach — a
+deploy you cannot run, an artifact that does not exist — and say which one.
+
 Objective: the `optimize` skill's. The number exists to save the operator a
 verification round trip (time), to stop a rework cycle before it starts
 (quality), and to replace a long hedging paragraph with two figures and their