Unified app — go-live sign-off

Overview: unified-app-summary.md

Use this after code milestones M1–M9 are merged locally. No database migration is required for the unified frontend cutover.

Pre-flight

Step	Command / action	Pass criteria
Env	Copy Admin/.env.example → production CI/host vars	REACT_APP_LINK = production API
RBAC catalog	npm run sync:rbac (if paths changed)	Admin rbacCatalog.generated.js updated
Build	npm run build:admin	Prebuild API URL check + exit 0
Backend deploy	Deploy/restart Backend (includes M6 task-list/history)	/healthz 200

Automated verification

Run from repo root with Backend and Admin (dev or production URL via env):

# Staging / production (both URLs required):
SMOKE_API_BASE=https://api.beentara.com ADMIN_URL=https://beentara.com npm run verify:unified-staging

# Or individually:
npm run smoke:unified-workspace -- https://api.beentara.com
ADMIN_URL=https://beentara.com npm run unified-app:smoke
# set UNIFIED_STAFF_* in qa-tests/.env for staff login probes

One-shot (local, both services up):

npm run verify:unified-cutover

If Backend is still starting:

npm run verify:unified-cutover:wait

Manual sign-off

#	Tester	Date	Notes
Staff login on beentara.com /login (Staff tab)
Dashboard shortcuts match staff permissions
Denied route → toast + /dashboard
Owner admin → full menu + SaaS routes
teams.beentara.com serves same app (post-DNS)
teams.beentara.com — no separate staff artifact (M22: staff/UI removed from repo)

Details: unified-app-browser-qa.md, unified-app-cutover.md.

Rollback

Redeploy previous Admin/build only. Rollback archive (if needed): Beentara-staff-ui-archive-*.zip from local backup. Backend routes remain backward compatible with legacy staff API aliases.

Reference docs

Doc	Purpose
unified-app-migration.md	Milestone history
unified-app-cutover.md	DNS, deploy, decommission
api-consolidation.md	M6 API surface
unified-app-browser-qa.md	Playwright + manual UI QA
staff-ui-retirement.md	After go-live: stop deploying teams app