Plan the redesigned GovTool site architecture

## Outcome

The new information architecture and frontend plan align GovTool with governance data, profiles, feeds, and future participation features.

## Scope

- Map current and target information architecture
- Define navigation, page responsibilities, and frontend bundle boundaries
- Align screens with Governance API contracts and data states
- Produce responsive, accessible UX flows and an implementation sequence

## Acceptance criteria

- [ ] Scope is decomposed into independently deliverable child issues.
- [ ] Architecture and API decisions are linked from this issue.
- [ ] Test, documentation, observability, rollout, and failure behavior are defined where applicable.
- [ ] Epic exit criteria are verified before closure.

## Planning note

This is a 2026 GovTool revamp work item. Its child features and tasks should be added as the scope is refined.

No files, tests, or entry points are named; start by reviewing the current GovTool information architecture and Governance API contracts. Break the revamp into child issues covering navigation, page responsibilities, bundle boundaries, responsive accessible flows, and implementation sequencing. Done means the listed acceptance criteria and epic exit checks are verified.

Written by the indexing model from the issue text.