[Debt] Migrate Committee WebUI to the interface pattern language #2

Closed
opened 2026-08-03 08:08:41 +02:00 by zemion · 1 comment
Owner

Context

This is the bounded govoplan-committee work package for the platform interface pattern-language rollout.

Current generated inventory boundary:

  • Routes: /committee
  • Contributed surfaces: committee.navigation, committee.workspace

The issue owns only module-provided UI. Shared primitives remain in Core; optional integrations must continue to use declared contracts and capabilities.

Scope

Audit the listed routes and contributed surfaces, classify each by the canonical archetypes in govoplan/docs/INTERFACE_PATTERN_LANGUAGE.md, and migrate deviations without redesigning unrelated behavior.

Acceptance Criteria

  • Inventory the module's routes, panels, dialogs, tables, workflows, and destructive actions and record their archetype and consequence class.
  • Use shared Core components and tokens for equivalent controls, status, dialogs, loading, empty, error, stale, offline, partial, and permission states.
  • Explain disabled or unavailable actions with actor, reason, required action, and destination where applicable.
  • Add stable contextual Docs links for routes, fields, blockers, and consequential actions.
  • Preserve optional-module boundaries; no private imports from sibling modules.
  • Verify keyboard order, focus handling, responsive behavior, localization, privacy-safe rendering, and destructive confirmation behavior.
  • Update the module's user/admin DocumentationTopic contributions and focused regression tests.
  • Record completion evidence in the rollout matrix under govoplan/docs/INTERFACE_SURFACE_INVENTORY.md.

Verification

Run the module's targeted backend/WebUI tests, the manifest-shape check, and the consolidated focused check when shared contracts or optional integrations change.

## Context This is the bounded `govoplan-committee` work package for the platform interface pattern-language rollout. - Platform pattern contract: [GovOPlaN #11](https://git.add-ideas.de/GovOPlaN/govoplan/issues/11) Current generated inventory boundary: - Routes: `/committee` - Contributed surfaces: `committee.navigation`, `committee.workspace` The issue owns only module-provided UI. Shared primitives remain in Core; optional integrations must continue to use declared contracts and capabilities. ## Scope Audit the listed routes and contributed surfaces, classify each by the canonical archetypes in `govoplan/docs/INTERFACE_PATTERN_LANGUAGE.md`, and migrate deviations without redesigning unrelated behavior. ## Acceptance Criteria - [ ] Inventory the module's routes, panels, dialogs, tables, workflows, and destructive actions and record their archetype and consequence class. - [ ] Use shared Core components and tokens for equivalent controls, status, dialogs, loading, empty, error, stale, offline, partial, and permission states. - [ ] Explain disabled or unavailable actions with actor, reason, required action, and destination where applicable. - [ ] Add stable contextual Docs links for routes, fields, blockers, and consequential actions. - [ ] Preserve optional-module boundaries; no private imports from sibling modules. - [ ] Verify keyboard order, focus handling, responsive behavior, localization, privacy-safe rendering, and destructive confirmation behavior. - [ ] Update the module's user/admin `DocumentationTopic` contributions and focused regression tests. - [ ] Record completion evidence in the rollout matrix under `govoplan/docs/INTERFACE_SURFACE_INVENTORY.md`. ## Verification Run the module's targeted backend/WebUI tests, the manifest-shape check, and the consolidated focused check when shared contracts or optional integrations change.
Author
Owner

Codex State: done

Summary

  • Committee interface-pattern migration completed and pushed in e64af30. The governed workspace now registers EN/DE translations, contextual route/field/consequence help, permission and lifecycle blockers, locale-aware dates, guarded record and ballot drafts, and confirmations for lifecycle transitions and ballot finalization. The surface/archetype inventory and consequence semantics are recorded in docs/INTERFACE_PATTERN_MIGRATION.md and in meta commit f4f9836.

Verification

  • 10 Committee backend/interface/migration tests pass; manifest registry validates 65/65 modules; Core structural i18n, theme, and interface-pattern checks pass; Access + Organizations + Committee production build passes bundle budgets; git diff --check passes.
## Codex State: done ### Summary - Committee interface-pattern migration completed and pushed in e64af30. The governed workspace now registers EN/DE translations, contextual route/field/consequence help, permission and lifecycle blockers, locale-aware dates, guarded record and ballot drafts, and confirmations for lifecycle transitions and ballot finalization. The surface/archetype inventory and consequence semantics are recorded in docs/INTERFACE_PATTERN_MIGRATION.md and in meta commit f4f9836. ### Verification - `10 Committee backend/interface/migration tests pass; manifest registry validates 65/65 modules; Core structural i18n, theme, and interface-pattern checks pass; Access + Organizations + Committee production build passes bundle budgets; git diff --check passes.`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-committee#2