Butkhuzi Live Cutover Window

Exact Env Change Used

Live API seam change in services/api/.env:

• before: Butkhuzi traffic fell back through TENDERS_SERVICE_URL=http://localhost:4020
• after: BUTKHUZI_SERVICE_URL=http://localhost:4024

The resulting live gateway seam is:

• BUTKHUZI_SERVICE_URL=http://localhost:4024
• TENDERS_SERVICE_URL=http://localhost:4020

Cutover Start Steps

1. Verified live API health on http://localhost:4001/api/v1/health.
2. Verified old colocated Butkhuzi host health on http://localhost:4020/health.
3. Started extracted svc-butkhuzi on canonical target http://localhost:4024.
4. Verified extracted runtime health on http://localhost:4024/health.
5. Updated services/api/.env to set BUTKHUZI_SERVICE_URL=http://localhost:4024.
6. Restarted the live API on :4001 so the env-only seam change took effect.

Smoke Checks Run

Immediately after cutover on the live gateway:

• GET /api/v1/butkhuzi/norms?page=1&pageSize=1
• GET /api/v1/butkhuzi/suggest?query=SNIP&limit=2
• GET /api/v1/butkhuzi/search?query=SNIP&page=1&pageSize=2
• POST /api/v1/butkhuzi/upsert without bearer token
• POST /api/v1/butkhuzi/chunks/rebuild with dev impersonation bearer token and {"sourceKey":"SNIP"}

Post-cutover health checks:

• GET http://localhost:4001/api/v1/health
• GET http://localhost:4020/health
• GET http://localhost:4024/health

Observations

• Gateway route shape stayed unchanged.
• Auth behavior stayed unchanged.
• Status codes and response bodies matched the Sprint 78 rehearsal expectations.
• Old host remained available on :4020 as rollback target during the window.
• Extracted runtime remained healthy on :4024.

Cutover Outcome

• The cutover remained in place.
• Rollback was not needed.

Stop / Rollback Steps If Needed Later

1. Change services/api/.env so Butkhuzi traffic points back to http://localhost:4020:
   • either remove BUTKHUZI_SERVICE_URL
   • or set BUTKHUZI_SERVICE_URL=http://localhost:4020
2. Restart the live API on :4001.
3. Re-run the Butkhuzi smoke checks on the live gateway.