Parent: #1264 · Labels: enhancement, area/tests (auto), area/ci
(auto), area/docs (auto) · Size: S (retire) / M (revive) · Depends on:
none (independent of DC1–DC6; carries its own design debate, peeled from DC6)

Goal. Make and implement a recorded revive-or-retire decision for the dead Azure
UAT scaffolding so nothing dead lingers.

Scope.

• tests/uat/azure/tests/cuj{1,2}-*/ exist with no workflow referencing them (no
  uat-azure.yaml). Either add a uat-azure.yaml + tests/uat/azure/run
  • cluster-config.yaml (revive, only if Azure GPU capacity is actually
    available and a reservation row can be added to infra/uat/reservations.yaml), or
    remove the dead tests/uat/azure/ tree.
• Record the decision in docs/contributor/uat.md.
• Default recommendation: retire unless a concrete Azure reservation exists
  (mirrors ADR-007's "don't pre-build without demand").

Out of scope. Any Azure work beyond the decision and its implementation. Adding
Azure to the launch matrix (would be a future reservation-row data edit, DC1/DC5).

Key files. tests/uat/azure/**, infra/uat/reservations.yaml (DC1, only if
reviving), docs/contributor/uat.md.

Tests. The decision is reflected: a uat-azure.yaml added + green (revive), or
the tree removed and referenced nowhere with the docs note (retire).

Acceptance. Azure decided and implemented (workflow added + green, or tree
removed + docs updated); decision recorded in docs/contributor/uat.md.

Decomposition note. DC6 originally bundled five heterogeneous gap-fills; the two
items carrying independent design debate are peeled out: Azure revive-or-retire
is now its own child (DC7), and the merge-gate cluster-smoke is a Deferred
proposal (not committed scope) rather than a DC6 line item. DC6 retains only the
three mechanical fixes (no-hard-fail/superseded-run guard, orphaned-Kind, opt-in
per-PR GPU) and is splittable into small PRs.

Child of #1264 · staged from docs/design/011-uat-dynamic-clusters.md (DC7).