feat(webui): add read-only console restart status and impact controls (Closes #667) #911
Merged
sysadmin
merged 2 commits from 2026-07-25 17:34:12 -05:00
feat/issue-667-console-restart-controls into master
Labels
Clear labels
allocator
anti-stomp
architecture
bug
chore
codex
concurrency
contamination
control-plane
dashboard
database
design
documentation
enhancement
gitea
glitchtip
important
incident
incident-bridge
integration
jenkins
labels
leases
mcp
mcp-health
mcp-menu
multi-project
mutating
nice-to-have
observability
portability
preflight
protected-branch
queue
read-only
reconnect
recovery
refactor
release
reliability
resumable-review
reviewer
roadmap
safety
security
self-hosted
sentry
stale-runtime
status:blocked
status:in-progress
status:pr-open
status:ready
terminal-lock
testing
tracker
type:bug
type:feature
type:feature
type:guardrail
visibility
workflow
workflow-hardening
workflow-hardening
Controller-owned work allocator
Prevent concurrent LLM session stomping
Architecture / structural design
OpenAI Codex client / workflow session surface
Concurrent session safety
Workflow or session contamination incident
MCP control-plane coordination and allocation authority
MCP operational dashboard/queue view
Internal coordination storage (SQLite/Postgres)
Design / investigation, no implementation
Docs / runbooks
New feature or improvement
Gitea MCP workflow
GlitchTip integration
Operational or process incident requiring durable audit trail
Sentry-to-Gitea incident bridging
Integration testing
Jenkins integration
Label taxonomy management
Lease adopt/release/expire lifecycle
MCP server / tooling
MCP namespace and runtime health
MCP menu surface
Work spanning multiple monitoring projects or Gitea repos
Mutating action; requires gating
Observability, metrics, traces, error reporting
Cross-platform / portability
Shared preflight gates before mutation
Protected branch / stable-branch policy concern
Work queue visibility and allocation
Read-only, no mutation
MCP client reconnect/reload recovery path
Recovery paths for stale/foreign leases
Code refactor / restructure
Release / versioning
Reliability / failure handling
Persist and resume prepared review verdicts across sessions
Reviewer workflow tooling
Roadmap / umbrella issue
Safety rails and fail-closed mutation guards
Security / trust boundary
Self-hosted infrastructure integration
Sentry error monitoring integration
Stale backend daemon / runtime-vs-master parity failures
Issue is blocked
Issue is being worked on
Issue has an open pull request
Issue is ready for work
Terminal review lock (#332) path
Tests / test coverage
Issue tracker hygiene / meta
Bug or defect
Feature or enhancement
Feature or enhancement
Safety gate or guardrail
Workflow state visibility for LLMs/operators
Cross-tool workflow
LLM workflow coordination hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Scaled-Tech-Consulting/Gitea-Tools#911
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Adds read-only Web Console restart status, impact preview, drain progress, restart class matrix, and approval/break-glass control panels (
/runtime/restartand/api/v1/system/restart/status) consuming the #655 coordinator substrate.Key capabilities implemented:
restart_coordinator.evaluate_restart_impact. Fails closed if inventory is incomplete.drain_proof.verify_drain_proof) and post-restart reconcile status (post_restart_reconcile).RESTART_CLASS_POLICIES) with role-scoped capability badges ("You may request" / "You may execute").for_execution=Trueso phase-1 gating (phase_not_active) is honestly reported rather than showing misleading live controls.mode=ro, never executes writes or process kills, and renders safe HTML.Links
Closes #667
Extends #642
Parent #655
Vision #652
Roadmap #653
Console #631
Soft-depends #658 #659 #660 #661 #662 #663 #664 #633 #634
Verification
Ran
pytest tests/test_webui*.py— 542 passed cleanly (including 30 tests intests/test_webui_restart_console.py).[THREAD STATE LEDGER]
what is true now
PR #911 remains in open state against master, with head
9b8e315b49. The head now carries both the implementation commit and the documentation commit for #667.Server-side decision state: no review verdict of any kind is recorded on this PR at the current head.
Local verdict/state: implementation and documentation are both present on the remote head; the branch is a fast-forward of its prior remote head and of master at
9c69bfcd80.what changed
Branch
feat/issue-667-console-restart-controlsadvanced9a01543477->9b8e315b49as a fast-forward, with no history rewrite.9a01543—webui/restart_console.py,webui/restart_views.py,webui/app.py,webui/nav.py,tests/test_webui_restart_console.py9b8e315—docs/webui-restart-console.mdThe publish mutated no issue-lock record and touched no workflow lease. It verified the recorded issue-lock claimant, the clean worktree state, the fast-forward relationship, and the absence of a competing open PR before writing the remote head.
what is blocked
Blocker classification: no blocker
The earlier obstruction has cleared. Publication was previously withheld because the serving runtime had started at
76f293ebwhile master had advanced to9c69bfcd, so the mutation gate fail-closed with blocker_kind=runtime_reconnect_required. The runtime is now in parity at9c69bfcd80with mutation_safe true.who/what acts next
Next actor: reviewer
Required action: Review PR #911 at head
9b8e315b49and record a verdict through the review API.Do not do: Do not treat the head movement as a response to review feedback — no review feedback exists on this PR. Do not expect break-glass execution controls in this change; #664 has not landed and that panel deliberately renders an unavailable status.
Canonical Issue State
STATE: PR-open
WHO_IS_NEXT: reviewer
NEXT_ACTION: Review PR #911 at head
9b8e315b49, which carries both the implementation commit and the documentation commit.NEXT_PROMPT:
WHAT_HAPPENED: The documentation commit for this PR existed locally with no remote head. The branch has now been advanced
9a01543477->9b8e315b49as a fast-forward, sodocs/webui-restart-console.mdis on the PR head alongside the implementation.WHY: Publication was withheld earlier in the cycle because the serving runtime had started at
76f293ebwhile master had advanced to9c69bfcd, so the mutation gate fail-closed with blocker_kind=runtime_reconnect_required. The runtime is now in parity at9c69bfcd80with mutation_safe true, and the publish verified against the recorded issue-lock claimant before writing the remote head.RELATED_PRS: #911
BLOCKERS: none
VALIDATION: Full suite on this branch — 28 failed / 5292 passed / 6 skipped. Clean-master baseline at
76f293eb— 28 failed / 5262 passed / 6 skipped. Identical 28 failure signatures; the delta is the 30 tests this PR adds. Four safety properties were each mutation-tested by reverting the guard and observing the corresponding test fail before restoring it: (1) dropping for_execution=True from the authorization probes — 1 failed; (2) forcing inventory_complete True — 1 failed; (3) returning raw str(value) from _esc — 1 failed; (4) opening the control-plane DB read-write instead of mode=ro — 1 failed. The fourth case initially did not fail under mutation because the test pointed at a nested missing directory, so sqlite raised for path reasons rather than for the read-only mode; the fixture was corrected to a writable-parent path and the mutation then failed the test as intended. An earlier run on this branch reported 178 failures; that count is not attributable to this branch — --ignore and --deselect bisects and a clean re-run all returned the same 28-failure set, and the 178 was concurrent-workspace contamination during the run.LAST_UPDATED_BY: jcwalker3 (prgs-author)
Scope statement
This PR delivers the status-view half of #667 only, matching that issue's own stated rollout order of status views first. Break-glass (#664) has not landed, so the break-glass panel renders to operator-class roles as an explicit unavailable status naming the blocking issue, rather than being hidden or simulated.
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #911
issue: none
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 6699-02ac7ccebf5c
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/feat-issue-667-console-restart
phase: claimed
candidate_head:
9b8e315b49target_branch: master
target_branch_sha: none
last_activity: 2026-07-25T22:26:19Z
expires_at: 2026-07-25T22:36:19Z
blocker: none
adopted_at: 2026-07-25T22:34:05Z
adopted_by_identity: sysadmin
adopted_by_profile: prgs-merger
adopted_from_session_id: 6699-02ac7ccebf5c
adopted_from_profile: prgs-reviewer
adopted_from_reviewer_identity: sysadmin
adopted_from_comment_id: 16938
adoption_reason: merger-handoff-approved-head
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #911
issue: none
reviewer_identity: sysadmin
profile: prgs-merger
session_id: 6365-871556eabc81
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/feat-issue-667-console-restart
phase: adopted
candidate_head:
9b8e315b49target_branch: master
target_branch_sha: none
last_activity: 2026-07-25T22:34:05Z
expires_at: 2026-07-25T22:44:05Z
blocker: none