Run 3: Validation — Completion Report

Date: 2026-03-19 Status: Complete — GO GO/NO-GO document: go-no-go.md

Exit Criteria Results

#	Criterion	Status
1	deploy.yaml succeeded during validation	Pass (run 23321972310)
2	redeploy.yaml succeeded with specific SHA	Pass (Amplify job 6, commit 34a27571432f)
3	Demo site functional after deployment	Pass (Items, Order Queue, Receiving — 0 console errors)
4	Existing partitions unaffected	Pass (dev: job 93, stage: job 170, prod: job 97 — no new builds)
5	GO/NO-GO document exists	Pass
6	Decision is GO	Pass

Issues Found and Resolved

ARDA_API_KEY mismatch (blocking, fixed during validation)

The ARDA_API_KEY_DEMO GitHub org secret had a stale value. The backend rejected all API calls with 401, causing the auth error handler to redirect to sign-in (flashing loop).

Root cause: The GitHub org secret was out of sync with 1Password (op://Arda-DemoOAM/ARDA-API-KEY). The first GH Actions amm.yml run wrote the stale value to Secrets Manager, which propagated to the Amplify app.

Fix applied:

1. Updated Secrets Manager secret
2. Updated Amplify app env var (merge pattern)
3. Updated ARDA_API_KEY_DEMO GitHub org secret
4. Triggered rebuild (Amplify job 8)

Verification: Playwright spot check confirmed 0 console errors on Items, Order Queue, Receiving pages after fix. Compared with dev (has persistent 401s suppressed by mock mode) and prod (works correctly).

Tickets Created

Ticket	Description
arda-frontend-app#701	Auth error handling: eliminate flash redirect, add Sentry logging, distinguish user-auth vs backend-auth failures

Cutover Preconditions (all met)

#	Precondition	Status
1	infrastructure#428 merged	Done
2	AMPLIFY_GITHUB_ACCESSTOKEN GitHub secret updated	Done
3	ARDA_API_KEY_DEMO GitHub org secret updated	Done
4	Team notified via Slack #dev-team	Done