Web Console: Application shell evolution (Phase 1) #638

Open
opened 2026-07-10 14:39:33 -05:00 by jcwalker3 · 1 comment
Owner

Problem statement

MVP shell (#426) provides basic layout and nav for early pages. The expanded console needs a shell that navigates Phase 1 surfaces (health, traffic, runtime/sessions, inventory, timeline entry points), shows environment/mode badges, and remains read-only-safe.

User and operational impact

Operators lack a coherent home for new views; nav drifts from epic #631 capabilities.

Scope

  • Evolve webui/layout.py and home page for console v2 IA (#632).
  • Nav groups: Health, Traffic, Runtime/Sessions, Projects, Inventory, Timeline, Policy (placeholder), Insights (placeholder).
  • Environment badge (local/dev), mode badge (read-only), link to docs.
  • Keep Starlette HTML MVP stack unless architecture ADR chooses otherwise.
  • No privileged action buttons in Phase 1 shell.

Explicit non-goals

  • No SPA rewrite unless ADR requires it.
  • No Phase 2 action controls.
  • No auth UI beyond stub/status if #633 not ready (degrade gracefully).

Required implementation investigation

webui/layout.py, app.py routes, #426, #632, #631, docs/webui-local-dev.md.

Proposed architecture or implementation direction

Extend shared layout partials; route table driven from a single nav config module; stub pages for not-yet-implemented children.

Security and workflow-safety requirements

No secrets in HTML; read-only posture visible; no hidden write forms.

Acceptance criteria

  1. Nav covers Phase 1 primary destinations and stubs later phases.
  2. Home summarizes console purpose and links MVP legacy pages.
  3. Mode/environment badges present.
  4. Tests for layout/nav presence (extend skeleton tests).
  5. Docs updated for new routes.

Required tests

Skeleton/nav tests; ensure 404 stubs for incomplete routes if used.

Observability and audit requirements

N/A beyond existing health link.

Dependencies and linkage

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Evolve application shell/nav for Phase 1
NEXT_PROMPT: Author shell only; PR; stop

Required final evidence

PR with layout/nav, tests, docs.

Required final response and handoff expectations

Brief PR → reviewer.

## Problem statement MVP shell (#426) provides basic layout and nav for early pages. The expanded console needs a shell that navigates Phase 1 surfaces (health, traffic, runtime/sessions, inventory, timeline entry points), shows environment/mode badges, and remains read-only-safe. ## User and operational impact Operators lack a coherent home for new views; nav drifts from epic #631 capabilities. ## Scope * Evolve `webui/layout.py` and home page for console v2 IA (#632). * Nav groups: Health, Traffic, Runtime/Sessions, Projects, Inventory, Timeline, Policy (placeholder), Insights (placeholder). * Environment badge (local/dev), mode badge (read-only), link to docs. * Keep Starlette HTML MVP stack unless architecture ADR chooses otherwise. * No privileged action buttons in Phase 1 shell. ## Explicit non-goals * No SPA rewrite unless ADR requires it. * No Phase 2 action controls. * No auth UI beyond stub/status if #633 not ready (degrade gracefully). ## Required implementation investigation `webui/layout.py`, `app.py` routes, #426, #632, #631, docs/webui-local-dev.md. ## Proposed architecture or implementation direction Extend shared layout partials; route table driven from a single nav config module; stub pages for not-yet-implemented children. ## Security and workflow-safety requirements No secrets in HTML; read-only posture visible; no hidden write forms. ## Acceptance criteria 1. Nav covers Phase 1 primary destinations and stubs later phases. 2. Home summarizes console purpose and links MVP legacy pages. 3. Mode/environment badges present. 4. Tests for layout/nav presence (extend skeleton tests). 5. Docs updated for new routes. ## Required tests Skeleton/nav tests; ensure 404 stubs for incomplete routes if used. ## Observability and audit requirements N/A beyond existing health link. ## Dependencies and linkage * Parent: #631 · Extends: #426 · Soft-depends: #632 ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Evolve application shell/nav for Phase 1 NEXT_PROMPT: Author shell only; PR; stop ``` ## Required final evidence PR with layout/nav, tests, docs. ## Required final response and handoff expectations Brief PR → reviewer.
jcwalker3 added the type:featurestatus:readyworkflow-hardeningdashboard labels 2026-07-10 14:39:33 -05:00
Author
Owner

Canonical Issue State

STATE:
ready-for-author

WHO_IS_NEXT:
author

NEXT_ACTION:
Evolve web-console application shell/navigation; link #652 #653 Phase 1

NEXT_PROMPT:

AUTHOR prgs Gitea-Tools. Implement #638. Vision #652 · Roadmap #653 Phase 1 · Umbrella #631 · Extends #426. Lock; branches/; PR; stop. Closing ≠ vision complete.

WHAT_HAPPENED:
Linked to #652/#653. Not recreated.

WHY:
Initial batch linkage.

RELATED_ISSUES:
#652 #653 #631 #426 #632

RELATED_PRS:
none

BLOCKERS:
none

VALIDATION:
existing retained

LAST_UPDATED_BY:
jcwalker3 / prgs-author / author / 2026-07-10

## Canonical Issue State STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Evolve web-console application shell/navigation; link #652 #653 Phase 1 NEXT_PROMPT: ```text AUTHOR prgs Gitea-Tools. Implement #638. Vision #652 · Roadmap #653 Phase 1 · Umbrella #631 · Extends #426. Lock; branches/; PR; stop. Closing ≠ vision complete. ``` WHAT_HAPPENED: Linked to #652/#653. Not recreated. WHY: Initial batch linkage. RELATED_ISSUES: #652 #653 #631 #426 #632 RELATED_PRS: none BLOCKERS: none VALIDATION: existing retained LAST_UPDATED_BY: jcwalker3 / prgs-author / author / 2026-07-10
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#638