`verification/rollout/RESULT.md`

49 lines

# DW activation rollout — TK-11314

Steve approved the reviewed rollout and one monitored publication with “go do it.”
The production changes were installed September 9, 2026 under the existing worker
locks. All 19 installed file hashes match the reviewed release, and all 45 tests
passed against the installed code. The code changes are committed locally:

| Runtime repository | Commit |
| --- | --- |
| dw-rotation-activator | c88ff69 |
| dw-five-field-step0 | 7891e2a |
| Designer-Wallcoverings | 1d91950f |

The independently verified canary, **DWDX-220334 / Cork, Dove**, changed from DRAFT
to ACTIVE and is published at
https://www.designerwallcoverings.com/products/cork-dove-dwdx-220334.
The storefront returned HTTP 200 and the correct product ID. Variant prices and
SKUs were unchanged. The activation ledger increased exactly from 0 to 1. The
existing Google publication exclusion was preserved; this is not a GMC enrollment.

Both task-owned locks were released at 17:20:33 UTC. The already-loaded launchd
jobs retain their schedules: activation at minute 25 (21 per slot, 500 per day),
field repair at minute 10. Those are limits, not a guarantee of daily volume.

The repair worker's dry-run operational path was exercised without product
mutation. A fresh persisted progress read afterward still reports 20,034 tasks,
17,445 completed, and 2,589 unresolved. Those unresolved rows have blank DW SKUs;
the worker safely skips them rather than inventing product identities.

## Remaining blocker

One real image-review probe returned **HTTP 429 RESOURCE_EXHAUSTED: prepaid credits
are depleted**. The product remained HELD, and the failed call recorded zero
estimated charge. Restoring credits requires the billing owner's action and a
separate spend approval. No billing, credential, or quota settings were changed.
Tracked separately as **TK-11321**. Product-data checks still apply after funding.

## Evidence

- `deployment-manifest.json`: before/after hashes, source backups, lock release.
- `canary-before.json` and `canary-verified.json`: independent live API/PDP proof.
- `vision-provider-probe.json`: exact sanitized provider failure and held outcome.
- `loaded-schedules.json`: selected fields from the loaded jobs.
- `../rollback-rehearsal.json`: source reversal/reapplication proof in temporary copies.

The natural 10:25 AM PDT run completed at 10:33:05 AM with exit code 0: 1,863 scanned, 15 activated and published, four already active, 1,340 product-data failures, and 504 image-review holds. The daily ledger is 16/500 including the canary. A separate Shopify API verifier confirmed all 15 scheduled activations are ACTIVE, published to Online Store, and excluded from Google under the existing policy; first/last storefront pages returned HTTP 200 with correct product IDs. The ledger and audit reconcile exactly. See `scheduled-run-verified.json`, `current-readiness-summary.json`, and `post-run-schedules.json`.

The existing calendar prune removed the 16 activated products from its staged schedule. Both worker locks are absent, and both existing jobs remain loaded.