Console Completeness Audit — 2026-05-06 UTC

Status: Static QA pass (Phase 1+3 of the test plan) Scope: console.raxx.app and raxx-console-staging.herokuapp.com — code-side analysis only Why static: Live UI/UX click-through is blocked by absence of a CF Access service token allowlisted on console.raxx.app's CF Access app (#680). UI verification deferred until that lands.

Executive summary

The "console completeness" pain has a measurable shape. Three findings:

1. Code internally consistent. All 94 url_for(...) references in templates resolve to actual routes. No broken nav links. No phantom endpoints.
2. The visible nav today is much smaller than the shipped surface. 11 nav entries are wired in base.html, but 9 of them are gated behind flags that default to OFF, plus role checks. With current prod flag state (console_flag_promotions=OFF per memory), the operator's actual top nav is likely Dashboard / Issues / Sign out — plus Secrets if their role is superadmin. The other 8 nav entries exist in code but are hidden until each flag is individually promoted to on in prod.
3. Five pages have no nav entry even when every flag is on. These are the "shipped but invisible" surfaces — features whose only entry point is the URL itself or a click-through from another deep page.

The "completeness" gap is 80% flag-state (correctly-built feature gated off in prod) and 20% nav-debt (truly orphaned URLs).

Numbers

The 11 nav entries and their gates

Reading console/app/templates/base.html lines 1051–1149, the nav block has these entries (when the operator is authed):

Default state of those flags (from backend_v2/api/feature_flags.yaml)

Per memory project_console_flag_toggle.md (operator-locked), console_flag_promotions is currently OFF in both staging and prod. If the other defaults haven't been individually promoted, the live nav is Dashboard + Issues + Sign out, possibly plus Secrets and Status.

This is not a bug in any single feature. This is the cumulative effect of every feature being built behind a flag and most of those flags never being promoted to on in prod after their soak.

The 5 truly orphaned pages

These have no nav entry and no url_for() reference from any other template. They exist in code as routes, render real HTML, but there's no path to reach them other than typing the URL.

Verdict: #1, #2, #3 are real UX bugs. #4 and #5 are arguably acceptable depending on the auth/billing flows.

Other observations

Code-quality positives

• All 94 template url_for() calls resolve to live routes. Zero phantom endpoints.
• Nav is properly role-gated and flag-gated — defense in depth, not just visual hiding.
• The auth + billing + customers panels all decline gracefully when flags or roles are missing.

Self-referential bootstrap trap (already-known, worth restating)

• flag_console_flag_promotions = OFF → Feature Flags UI returns 404.
• To turn it ON via UI, you'd use the very Feature Flags UI that's hidden by it being OFF.
• First flip must use heroku config:set FLAG_CONSOLE_FLAG_PROMOTIONS=on -a raxx-console-prod directly, per memory feedback_bootstrap_via_heroku.md. Same applies to console_nav_v2 if also OFF.

Possible RBAC observation (not verified — needs UI access)

• 8 of 11 nav entries require ops, superadmin, or specific RBAC roles.
• If the operator's current admin record lacks one or more roles (e.g. console-billing-read), the corresponding nav entries stay hidden even with the flag ON.
• Worth verifying once we have UI access: which roles is the operator's account assigned to?

Possible redundancy in the Promotions vs Flags nav

• Both flags.flags_index (/console/flags) and flags.promotions_queue (/console/flags/promotions) appear as separate top-nav entries gated by the same flag + same role.
• May be intentional — Flags is the live state, Promotions is the queue. Worth confirming the UX intent.

What this audit could NOT cover

UI verification is deferred until #680 lands. I could not check:

• Whether each page actually renders correctly in a browser
• Whether modals + HTMX fragments load + dismiss properly
• Whether real-time tile pulse/breathing-line/build-strip animations look right
• Whether the deploy modal opens, dispatches, and shows progress
• Whether form submissions actually persist to the DB
• Whether flag promotions actually write to console_flag_promotions and propagate to Heroku
• Whether the navigation order matches the user's mental model
• Mobile breakpoints, accessibility, dark-mode contrast

When #680 lands and a CF Access service token is allowlisted on console.raxx.app, those checks become a single Playwright sweep.

Recommendations

In priority order, ranked by user-visible impact:

1. Audit prod flag state. Run heroku config -a raxx-console-prod | grep FLAG_ (operator action; I'm not authorized) and decide which flags should be ON for everyday operator use. Most-likely candidates to turn on now: FLAG_CONSOLE_NAV_V2, FLAG_CONSOLE_FLAG_PROMOTIONS, FLAG_CONSOLE_CLAUDE_MENU. The first one alone unlocks Security + Status nav entries.

2. File card: nav entry for /console/deploy-freeze. Single-line addition to base.html. Operator already noted this gap in chat today. Likely belongs under the Ops dropdown.

3. File card: nav-tab for /console/customers/<id>/tickets. Should be a tab on the customer detail page (next to Audit, Danger Zone). Discoverable when looking at a specific customer.

4. File card: /console/admins/online placement. Either Security sub-nav or Ops dropdown. Pick one.

5. Provision CF Access service token for console.raxx.app (#680). Without this, every future agent QA pass is gated on you running Playwright manually. 5 min in CF dashboard.

6. (Optional) Audit the bootstrap trap. Document explicitly that console_flag_promotions and console_nav_v2 are bootstrap-only flips via heroku config:set. Update the runbook for whoever onboards next.

Test plan when UI access lands

When #680 closes and a CF Access service token is allowlisted on console.raxx.app:

Phase 1 — reachability (~30 min): - Playwright loads each of the 22 user-facing pages - Captures HTTP status, full-page screenshot - Pass = HTTP 200 + page renders without console errors

Phase 2 — function spot-check (~1-2 hr): - Dashboard tile hover popover (after PR #1263 landed) - Build-strip animation states (if PR #1264 implementation lands) - Deploy modal open/close (no actual dispatch) - Flag promotion mark + approve flow (no actual promote) - Secret rotate modal v2 open (no actual rotate) - Customer detail tab navigation - Mobile breakpoint at 375px

Phase 3 — staging vs prod diff: - Run Phase 1+2 on both, diff screenshots - Identifies drift between the two envs

Phase 4 — gap remediation: - Each "missing from UI" → file as a card with the exact gap - Quick wins (single-line nav adds) ship as small PRs

Appendix: full route inventory

Source-of-truth: console/app/blueprints/*.py. All 56 GET routes:

Audit run by: Claude Code session, 2026-05-06 UTC Phase 2 (UI click-through): deferred until #680 (CF Access service token for console)