Web Console: System-health dashboard (Phase 1) #639

New Issue

2026-07-10T14:39:46-05:00

jcwalker3 commented

2026-07-10 14:39:46 -05:00

Problem statement

Operators need a system-health dashboard showing readiness, version, uptime, dependency status, and stale-runtime signals using the Phase 1 system-health API — without offering restart controls yet.

User and operational impact

Runtime issues are discovered late via failed LLM sessions rather than a clear operator surface.

Scope

HTML dashboard consuming system-health API (#634).
Cards: overall readiness, version/uptime, dependencies, MCP namespaces, stale-runtime warning.
Link to runtime/session view and docs for sanctioned recovery (not pkill — #630).
Read-only; refresh guidance only.

Explicit non-goals

No restart/reload buttons (Phase 2).
No manual process kill guidance.

Required implementation investigation

#634 API, runtime_views.py, #430, #638 shell, #631.

Proposed architecture or implementation direction

Server-rendered page from health DTO; optional auto-refresh meta; clear degraded states.

Security and workflow-safety requirements

Redacted dependency details; no secrets; do not claim mutation-safe when stale.

Acceptance criteria

Dashboard renders health DTO fields.
Degraded dependencies visible.
Stale-runtime prominently warned.
Tests for render with healthy/degraded fixtures.
Nav entry from shell.

Required tests

View render tests with fixture health payloads.

Observability and audit requirements

Read-only view.

Dependencies and linkage

Parent: #631 · Depends: #634 · Soft: #638 · Related: #430, #610, Block manual MCP daemon process killing as workflow recovery (#630)

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Build system-health dashboard on #634 API
NEXT_PROMPT: Author dashboard UI only after/with #634; PR; stop

Required final evidence

PR with page, tests, screenshots optional in PR body.

Required final response and handoff expectations

Brief PR → reviewer.

## Problem statement Operators need a **system-health dashboard** showing readiness, version, uptime, dependency status, and stale-runtime signals using the Phase 1 system-health API — without offering restart controls yet. ## User and operational impact Runtime issues are discovered late via failed LLM sessions rather than a clear operator surface. ## Scope * HTML dashboard consuming system-health API (#634). * Cards: overall readiness, version/uptime, dependencies, MCP namespaces, stale-runtime warning. * Link to runtime/session view and docs for sanctioned recovery (not pkill — #630). * Read-only; refresh guidance only. ## Explicit non-goals * No restart/reload buttons (Phase 2). * No manual process kill guidance. ## Required implementation investigation #634 API, `runtime_views.py`, #430, #638 shell, #631. ## Proposed architecture or implementation direction Server-rendered page from health DTO; optional auto-refresh meta; clear degraded states. ## Security and workflow-safety requirements Redacted dependency details; no secrets; do not claim mutation-safe when stale. ## Acceptance criteria 1. Dashboard renders health DTO fields. 2. Degraded dependencies visible. 3. Stale-runtime prominently warned. 4. Tests for render with healthy/degraded fixtures. 5. Nav entry from shell. ## Required tests View render tests with fixture health payloads. ## Observability and audit requirements Read-only view. ## Dependencies and linkage * Parent: #631 · Depends: #634 · Soft: #638 · Related: #430, #610, #630 ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Build system-health dashboard on #634 API NEXT_PROMPT: Author dashboard UI only after/with #634; PR; stop ``` ## Required final evidence PR with page, tests, screenshots optional in PR body. ## Required final response and handoff expectations Brief PR → reviewer.

jcwalker3 added the type:feature status:ready workflow-hardening dashboard mcp-health labels 2026-07-10 14:39:46 -05:00

jcwalker3 referenced this issue

2026-07-10 14:42:49 -05:00

Epic: MCP Control Plane Web Console #631

jcwalker3 referenced this issue

2026-07-10 14:48:05 -05:00

Roadmap: MCP Control Plane Web Console (phased delivery) #653

jcwalker3 referenced this issue

2026-07-10 14:49:07 -05:00

Web Console: Read-only system-health API (Phase 1) #634

jcwalker3 commented

2026-07-10 14:49:41 -05:00

Canonical Issue State

STATE:
ready-for-author

WHO_IS_NEXT:
author

NEXT_ACTION:
Build system-health dashboard on #634; link #652 #653 Phase 1

NEXT_PROMPT:

AUTHOR prgs Gitea-Tools. Implement #639. Vision #652 · Roadmap #653 Phase 1 · Depends #634. Lock; branches/; PR; stop. Closing ≠ vision complete.

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

WHY:
Initial batch linkage.

RELATED_ISSUES:
#652 #653 #631 #634 #430 #638

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: Build system-health dashboard on #634; link #652 #653 Phase 1 NEXT_PROMPT: ```text AUTHOR prgs Gitea-Tools. Implement #639. Vision #652 · Roadmap #653 Phase 1 · Depends #634. Lock; branches/; PR; stop. Closing ≠ vision complete. ``` WHAT_HAPPENED: Linked to #652/#653. Not recreated. WHY: Initial batch linkage. RELATED_ISSUES: #652 #653 #631 #634 #430 #638 RELATED_PRS: none BLOCKERS: none VALIDATION: existing retained LAST_UPDATED_BY: jcwalker3 / prgs-author / author / 2026-07-10

Sign in to join this conversation.

Branches Tags

master

fix/issue-709-decision-lock-cross-profile

fix/issue-695-native-transport-quarantine

fix/issue-698-report-validator-schema

fix/issue-702-stale-binding-lease-recovery

fix/issue-699-structured-auth-mcp-errors

fix/issue-695-native-quarantine-v2

fix/issue-693-review-decision-lock-recovery

fix/issue-691-obsolete-reviewer-lease-cleanup

feat/issue-687-reconciler-branch-delete

fix/issue-683-workflow-guard-hardening

chore/issue-681-preserve-review-session-wip

feat/issue-604-anti-stomp-preflight

feat/issue-606-sentry-observability

fix/issue-671-block-stable-branch-push

fix/issue-675-residual-preflight-remediation

fix/issue-673-remediate-regressions-part2

fix/issue-673-remediate-regressions

feat/issue-603-lifecycle-labels

fix/issue-627-set-issue-labels-pagination

feat/issue-601-first-class-leases

feat/issue-612-incident-bridge

feat/issue-600-controller-allocator-api

fix/issue-620-head-scoped-review-locks

feat/issue-613-allocator-db-substrate

docs/mcp-stable-control-runtime-policy

feat/issue-609-prepared-review-verdict-resume

feat/issue-610-live-remote-parity

feat/issue-503-reviewer-active-worktree

feat/issue-470-preflight-contract

feat/issue-440-lock-recovery

feat/issue-440-branch-recovery

feat/issue-458-queue-fail-closed-copy

feat/issue-400-early-duplicate-work-gate

feat/issue-308-reconcile-inventory-pagination

feat/issue-308-reconcile-pagination-proof

docs/issue-261-agent-temp-artifact-cleanup

feat/issue-262-map-commit-files

fix/infra-stop-conflict-marker-false-positive

feat/issue-139-role-aware-task-routing

feat/issue-188-continuation-selection-wall

feat/issue-189-continuation-mode-proofs

feat/issue-232-refresh-wiki-proof-heads

feat/issue-210-block-workspace-edits

feat/issue-204-exact-issue-lock

docs/issue-80-label-taxonomy

docs/issue-79-safety-boundary-updates

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

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