# Stabilization Closeout UAT Status - 2026-06-11

This note records the current GPUaaS stabilization closeout status for kind and
dev validation. It is evidence status, not a production release approval.

## Current Source

- Source SHA: `0f9393f0e65b901be28ea73fcde6ac1ab27cfd7b`
- Commit: `chore: add deterministic kind smoke profile`
- GitLab pipeline: `2635`
- CI result: pass
- CI evidence:
  `.fairway/artifacts/local-ci-monitor-2635/summary.json`

## Kind Status

Kind deploy and validation evidence exists for the current stabilization
closeout path:

- Kind deploy validation passed for source
  `ad1e92a7af1535dd296452993b436fef331e5395`.
- Deterministic kind smoke profile wrapper is now available:
  `scripts/ops/kind_smoke_profile.sh`.
- Wrapper CI passed in pipeline `2635`.
- Non-mutating kind smoke passed for:
  - deploy monitor
  - v3 persona smoke
  - role authorization smoke
  - v3 read-model smoke
  - terminal remote smoke against an existing active allocation
  - billing and finance read smoke

Important evidence:

- `.fairway/artifacts/deploy-kind-stabilization-closeout-20260611/kind-parity-up-envlocal-rerun.log`
- `.fairway/artifacts/deploy-kind-stabilization-closeout-20260611/kind-parity-validate-envlocal.log`
- `.fairway/artifacts/kind-smoke-profile-wrapper-20260611/skip-validate-final/summary.json`

## Blocking Gate

Full kind UAT and dev deploy readiness remain blocked by:

`OPS-FIX-KIND-COMPUTE-CAPACITY-PREREQ-001`

Fresh prerequisite evidence shows:

- SKU: `compute-vm-small`
- Region/provider: `local-maas-lxd`
- Availability: `unavailable`
- `available_units`: `0`
- `ready_units`: `0`
- `on_demand_units`: `0`
- `capacity_basis`: `none`

The current existing allocation can support non-mutating read/connect smoke:

`f090e861-358c-48c8-b6b0-42cc8a7db718`

It does not prove mutating compute launch capacity.

Capacity evidence:

- `.fairway/artifacts/kind-compute-capacity-recheck-20260611/prereq-baseline/summary.md`
- `.fairway/artifacts/kind-compute-capacity-recheck-20260611/prereq-baseline/logs/compute-catalog.local-maas-lxd.compute-vm-small.capacity.json`
- `.fairway/artifacts/kind-compute-capacity-recheck-20260611/ops-capacity-decision-request.md`

## Pre-UAT Readiness Status

Strict pre-UAT remains blocked.

Latest strict-safe evidence:

- `.fairway/artifacts/kind-uat-smoke-20260611/pre-uat-strict-safe/readiness.json`

Passing gates:

- service freshness
- user-safe error presentation
- harness failure injection
- UAT coverage matrix reference

Blocking gates:

- live prerequisite baseline: blocked by kind compute capacity
- app SDK live contract: not run because it requires mutating launch capacity
- blocking integration smoke: run flag was not enabled in the safe run
- clean-log observability: still needs profile-aligned rerun/classification

## Dev Validation Decision

Do not deploy to dev from this closeout yet.

Dev deploy can proceed only after one of the following is recorded:

1. kind `compute-vm-small` / `local-maas-lxd` reports ready/provider capacity;
2. an approved alternate kind profile is recorded with owner, reason, expiry,
   and evidence that it exercises the intended provisioning path;
3. an approved scoped UAT waiver is recorded with owner, reason, expiry, and
   compensating evidence.

## Next Actions

1. Ops decides one of: restore kind MAAS-LXD capacity, approve an alternate
   profile, or approve a scoped waiver.
2. Re-run strict pre-UAT with all safe gates enabled after the capacity decision.
3. Run mutating kind UAT only when capacity/profile/waiver evidence is valid.
4. Prepare dev validation only after kind evidence is acceptable.