test: govern unavailable conditional environments

docs/conditional-testing.md

@@ -12,6 +12,13 @@ days, and treats evidence older than eight days as stale. Every workflow run pub
 a summary showing selected, successful, failed, and not-selected/no-fresh-evidence
 gates.
 
+Unavailable hardware or credential-bound gates may use a committed environment
+waiver for at most 30 days. Each waiver names one gate, a canonical tracking issue,
+the reason, its opening and expiry dates, and the support claim it blocks. Invalid,
+duplicate, future-dated, overlong, or expired waivers fail the policy job. The current
+waivers are tracked by [issue #110](https://github.com/elder-plinius/OBLITERATUS/issues/110)
+and expire on 2026-09-15; they are not evidence that any waived backend works.
+
 ## Hosted gates
 
 The model gate downloads only
@@ -99,4 +106,8 @@ hosted runner-minutes plus any provider charge.
 failure, error, or skip. A selected workflow job therefore cannot become green through
 an availability skip or unconditional success conversion. The final summary also
 fails if any selected job is not successful. Unselected jobs are explicitly reported
-as `not_selected_no_fresh_evidence`; they are not evidence of backend support.
+as `not_selected_no_fresh_evidence`; they are not evidence of backend support. An
+unselected hardware or credential-bound gate with a valid waiver is reported as
+`waived_no_support_claim`, including its tracker, expiry, and blocked claim. Selecting
+and successfully running that gate produces `success` instead of relying on the
+waiver.