7. Frontend: Administrative Console integration

[BryanttV]

Description

• Frontend migration: replace the static role/permission arrays currently hardcoded in the Console with calls to the Task 5/6 APIs.
• Dynamic rendering: the UI must be able to render labels, descriptions, and permission groupings (by resource) without knowing in advance how many or which roles exist.
• Visual compatibility: ensure the redesign doesn't break the current experience for core roles (same groupings, same labels admins already know).
• Key requirement's acid test: install a new module with a contributed role and confirm it appears in the Console's listing and assignment flow without any frontend change or release — this is literally the epic's success criterion.
• Loading/error state handling: what does the UI show if the metadata API fails or returns an invalid definition?

Concrete deliverable: the Admin Console is 100% data-driven from the AuthZ APIs, validated with at least one contributed test role.