Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 73 Pull Requests 9 Actions Packages Projects Releases Wiki Activity

Web Console: Restart status, impact preview, and approval controls #667

New Issue
Open
opened 2026-07-10 15:33:12 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-10 15:33:12 -05:00
Owner
Copy Link
Copy Source

Problem statement

#642 covers sanctioned restart UI stubs at a high level. Operators still need console surfaces for restart status, impact preview, drain progress, approval, and break-glass driven by the #655 coordinator substrate—not ad-hoc kill buttons.

Operational impact

Without console integration, governance stays CLI-only and underused; vision #652 maintenance controls incomplete.

Scope

  • Extend #642 / webui gated actions:
    • Impact preview view (from #658)
    • Drain status and progress
    • Controller approval workflow
    • Restart class selection (#663)
    • Break-glass UI with required fields (#664)
    • Post-restart reconcile status (#662)
  • Read-only status available before Phase 2 write gates fully land.
  • Never expose raw pkill.

Non-goals

  • Implementing coordinator backend (consume APIs).
  • Full HA topology UI.

Required implementation investigation

#642 #655 #658–#665 #633 #634 #631 #652 #653; webui gated_actions.

Proposed implementation direction

/runtime/restart console pages + API proxies to coordinator; RBAC from #633.

Security / workflow-safety

RBAC; confirmations; audit display; no secrets.

Failure behavior

Backend deny shown clearly; no client-side bypass.

Acceptance criteria

  1. Impact preview renderable from coordinator DTO.
  2. Approval/break-glass only for privileged roles.
  3. Drain/reconcile status visible.
  4. Tests for views/gates.
  5. Links #652 #653 #655 #642.

Required tests

View tests with fixture impact/drain DTOs; role deny.

Observability and audit

UI actions create same audits as API.

Dependencies

Rollout

Status views first; write approval after backend gates green.

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Implement console restart status/approval UX consuming #655 APIs
NEXT_PROMPT: Author console restart UI under #655/#642; PR; stop

Required proof

UI + tests + screenshots optional.

Required final response and handoff

Brief PR → reviewer.

## Problem statement #642 covers sanctioned restart UI stubs at a high level. Operators still need console surfaces for **restart status, impact preview, drain progress, approval, and break-glass** driven by the #655 coordinator substrate—not ad-hoc kill buttons. ## Operational impact Without console integration, governance stays CLI-only and underused; vision #652 maintenance controls incomplete. ## Scope * Extend #642 / webui gated actions: * Impact preview view (from #658) * Drain status and progress * Controller approval workflow * Restart class selection (#663) * Break-glass UI with required fields (#664) * Post-restart reconcile status (#662) * Read-only status available before Phase 2 write gates fully land. * Never expose raw pkill. ## Non-goals * Implementing coordinator backend (consume APIs). * Full HA topology UI. ## Required implementation investigation #642 #655 #658–#665 #633 #634 #631 #652 #653; webui gated_actions. ## Proposed implementation direction `/runtime/restart` console pages + API proxies to coordinator; RBAC from #633. ## Security / workflow-safety RBAC; confirmations; audit display; no secrets. ## Failure behavior Backend deny shown clearly; no client-side bypass. ## Acceptance criteria 1. Impact preview renderable from coordinator DTO. 2. Approval/break-glass only for privileged roles. 3. Drain/reconcile status visible. 4. Tests for views/gates. 5. Links #652 #653 #655 #642. ## Required tests View tests with fixture impact/drain DTOs; role deny. ## Observability and audit UI actions create same audits as API. ## Dependencies * Parent **#655** · Extends **#642** · Soft-depends **#658–#665** **#633** · Vision **#652** · Roadmap **#653** · Console **#631** ## Rollout Status views first; write approval after backend gates green. ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Implement console restart status/approval UX consuming #655 APIs NEXT_PROMPT: Author console restart UI under #655/#642; PR; stop ``` ## Required proof UI + tests + screenshots optional. ## Required final response and handoff Brief PR → reviewer.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels dashboard mcp-health safety status:ready type:feature workflow-hardening
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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