ui/_docs/03_implementation/deploy_cycle4_report.md

Cycle 4 Step 16 — Deploy Report

Date: 2026-05-13 Cycle: 4 (autodev existing-code Step 16) Mode chosen: real cutover (option A in the cycle-4 deploy gate — "Push to ui/ dev only") Outcome: ui/ dev pushed; stage/prod cutover deferred to a later turn; admin/ dev NOT pushed; cross-workspace AZ-513 still un-implemented.

What was actually deployed

Repo	Branch	Commits pushed	Pipeline triggered
ui/	dev (09449bd..8737491)	4	Woodpecker dev build for ui/
admin/	—	0	none

Commits pushed to ui/ origin/dev

8737491 [AZ-512] Cycle 4 Steps 12-15: test-spec sync + docs + sec + perf
ecacfa8 [AZ-512] Admin class inline edit form + PATCH wiring (cy4 batch 16)
ef56d9c [AZ-512] chore: reactivate for cycle 4 (Option B path)
eef3bdf [AZ-509][AZ-510][AZ-511] Cycle 3 closure: deploy + retro + state

The cycle-3 closure commit eef3bdf was locally ahead since cycle 3's deploy step (deferred at the cycle-3 push-scope gate), and gets pushed now alongside cycle-4's three commits as a single fast-forward.

What was NOT done (deferred / pending)

ID	Item	Reason	Owner
D-CY4-STAGE	ui/ dev → stage → push origin/stage	User chose option A (dev-only) at the cycle-4 deploy gate. Stage cutover deferred. Will compound with cycle-3 stage deferral — when stage cutover lands, it will ship cycles 3 + 4 simultaneously.	User
D-CY4-MAIN	ui/ stage → main → push origin/main (prod cutover)	Same reason. Devices will not auto-pull cycle-3 + cycle-4 changes until this completes.	User
D-CY4-AZ513-IMPL	Implementation of AZ-513 (admin/ POST + PATCH + DELETE /classes routes)	Cross-workspace dependency: admin/ workspace must implement before AZ-512 is functionally usable in any environment. Filed in Jira (AZ-513, parent epic AZ-509, Blocks AZ-512). UI ships with MSW-stubbed tests under user-authorized Option B — the live PATCH endpoint does not exist server-side yet, so the deployed ui/ dev build will surface admin.classes.updateFailed on real edits.	admin/ team
D-CY4-ADMIN-PUSH	admin/ dev push origin/dev	User did not select option C at the cycle-4 deploy gate. The AZ-513 task spec sits locally on admin/ dev (since cycle 3).	User

Carry-forward from cycles 2 and 3

Cycle 2's deploy_planning_sync_cycle2.md deferred 3 items to leftovers in _docs/_process_leftovers/2026-05-12_az-498-deploy-and-key-revocations.md. Cycle 3 did not close any of them. Cycle 4 also did not close them:

ID (origin)	Item	Status as of 2026-05-13 (cycle 4 close)
L-AZ-498-DEPLOY	UI tile-swap prod cutover	Still deferred — cross-workspace satellite-provider gate unchanged. Will compound with cycle-3 + cycle-4 stage/prod deferrals when finally promoted.
L-AZ-499-OWM-REVOKE	OpenWeatherMap key revocation at owm dashboard	Still pending — manual third-party action; owner: user.
L-AZ-501-GOOGLE-REVOKE	Google Geocode key revocation at Google Cloud Console	Still pending — manual third-party action; owner: user.
L-AZ-512-ADMIN-PREREQ	AZ-513 implementation + ship in admin/ workspace	Re-opened cycle 4 under user-authorized Option B. UI implementation now landed; gate stays open until admin/ AZ-513 ships AND deploys.

These leftovers need a status sweep at the start of the next /autodev invocation per tracker.mdc Leftovers Mechanism.

Cycle-4 deployment-doc deltas (NOT written this cycle)

In strict autodev terms, Step 16 in this cycle was a real cutover (option A), not a planning sync. The cycle-2 pattern of patching _docs/02_document/deployment/* was therefore skipped here because:

• AZ-512 introduced no changes to Dockerfile, .woodpecker/, env vars, or nginx.conf (verified inline during Step 14 security audit; the cycle-4 delta security_report_cycle4_delta.md enumerates the changed files).
• AZ-512's only wire-shape change is one new HTTP method on an existing URL (PATCH /api/admin/classes/{id} — already routed to admin/ by nginx.conf since cycle 2 because DELETE /api/admin/classes/{id} was already proxied through the same route block).
• No new env vars, no new container, no new exposed port.

If a future cycle adds env vars, infra changes, or new services, the cycle-2 planning-sync pattern (update environment_strategy.md, ci_cd_pipeline.md, containerization.md, observability.md) should be applied.

Verification

• git push origin dev for ui/ returned 09449bd..8737491 dev -> dev (4 commits, fast-forward).
• git status -sb for ui/ confirms dev and origin/dev are synced post-push (no [ahead N]).
• Functional test suite green pre-push (243 passed, 13 quarantined skips, 0 failed — see test-output/summary.csv and test-output/fast-report.xml). Up +12 vs cycle 3 from the new tests/admin_class_edit.test.tsx suite.
• Static perf NFT-PERF-01 green pre-push (291 332 B gzipped vs ≤ 2 097 152 B threshold — see test-output/performance-summary.txt and _docs/06_metrics/perf_2026-05-13_cycle4.md).
• Security cycle-4 delta verdict PASS_WITH_WARNINGS pre-push (see _docs/05_security/security_report_cycle4_delta.md).
• No nginx/Docker/CI config changes in cycle 4.
• Cross-workspace deploy gate (AZ-513) explicitly acknowledged and re-recorded in this report and in the leftover entry. The deployed UI on ui/ dev will return admin.classes.updateFailed on real PATCH attempts until admin/ AZ-513 ships — by design under user-authorized Option B.

Cycle-3 → cycle-4 push-scope progression

Cycle 3 deploy gate: user picked option A (ui/ dev only). Cycle 4 deploy gate: user picked option A again (ui/ dev only). The same trade-off applies — stage/prod cutover is being collected for a single later promotion. Two consecutive cycles of dev-only pushes means the eventual stage promotion will batch AZ-510 + AZ-511 + AZ-512 deltas into one stage build, with the additional gate that AZ-513 must have shipped in admin/ by that time (otherwise the AZ-512 edit feature renders but cannot complete saves).

Auto-chain

→ Step 17 (Retrospective) for cycle 4.