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

Tracker: MCP Control Plane web UI #425

New Issue
Closed
opened 2026-07-07 12:20:59 -05:00 by jcwalker3 · 1 comment
jcwalker3 commented 2026-07-07 12:20:59 -05:00
Owner
Copy Link
Copy Source

Problem statement

Operators currently rely on scattered prompts, MCP tools, CLI scripts, and ad-hoc terminal inspection to onboard projects, copy canonical workflow prompts, inspect Gitea queue state, verify runtime health, audit LLM final reports, and understand worktree/lease/collision risk. There is no durable internal web surface that exposes this operational picture while keeping Gitea, MCP tools, workflows, and schemas as the source of truth.

Purpose

Track child issues for building an internal-only web UI that exposes:

  • project onboarding and registry
  • prompt library derived from canonical skills/workflows
  • live PR and issue queue state
  • MCP runtime health and stale-runtime detection
  • report audit paste/review tooling
  • worktree and branch hygiene visibility
  • lease and collision visibility
  • gated-action framework (read-only MVP first)
  • auth/deployment boundary documentation
  • test coverage and CI checks

Source of truth remains: Gitea issues/PRs, MCP capability gates, canonical workflow files under skills/llm-project-workflow/, and project schemas — not duplicated policy inside the UI.

Child issues

  • #426 — Web UI: Create internal server skeleton
  • #427 — Web UI: Project registry and onboarding model
  • #428 — Web UI: Prompt library from canonical workflows
  • #429 — Web UI: Live PR and issue queue dashboard
  • #430 — Web UI: Runtime health and stale MCP detection
  • #431 — Web UI: Report audit paste tool
  • #432 — Web UI: Worktree and branch hygiene dashboard
  • #433 — Web UI: Lease and collision visibility
  • #434 — Web UI: Gated action framework
  • #435 — Web UI: Auth and deployment boundary
  • #436 — Web UI: Test coverage and CI checks

Acceptance criteria (tracker)

  • All child issues exist and are linked from this tracker
  • Each child issue is independently implementable with clear non-goals
  • MVP remains read-only except where gated-action framework explicitly prepares future writes
  • No secrets stored in frontend or UI config
  • UI reads from canonical workflows/schemas/APIs rather than inventing parallel policy

Non-goals

  • Public internet deployment without access controls
  • Replacing Gitea, MCP servers, or canonical workflow files as policy source
  • Enabling ungated review/merge/comment/create/delete from the browser in MVP
  • Building a general-purpose issue/PR editor

Related work (not duplicates)

Dependencies

  • Child server skeleton is the foundation for most UI issues
  • Gitea read APIs / existing MCP read tools supply queue and registry data
  • Canonical workflows under skills/llm-project-workflow/workflows/ supply prompt library content
## Problem statement Operators currently rely on scattered prompts, MCP tools, CLI scripts, and ad-hoc terminal inspection to onboard projects, copy canonical workflow prompts, inspect Gitea queue state, verify runtime health, audit LLM final reports, and understand worktree/lease/collision risk. There is no durable internal web surface that exposes this operational picture while keeping Gitea, MCP tools, workflows, and schemas as the source of truth. ## Purpose Track child issues for building an **internal-only** web UI that exposes: - project onboarding and registry - prompt library derived from canonical skills/workflows - live PR and issue queue state - MCP runtime health and stale-runtime detection - report audit paste/review tooling - worktree and branch hygiene visibility - lease and collision visibility - gated-action framework (read-only MVP first) - auth/deployment boundary documentation - test coverage and CI checks **Source of truth remains:** Gitea issues/PRs, MCP capability gates, canonical workflow files under `skills/llm-project-workflow/`, and project schemas — not duplicated policy inside the UI. ## Child issues - #426 — Web UI: Create internal server skeleton - #427 — Web UI: Project registry and onboarding model - #428 — Web UI: Prompt library from canonical workflows - #429 — Web UI: Live PR and issue queue dashboard - #430 — Web UI: Runtime health and stale MCP detection - #431 — Web UI: Report audit paste tool - #432 — Web UI: Worktree and branch hygiene dashboard - #433 — Web UI: Lease and collision visibility - #434 — Web UI: Gated action framework - #435 — Web UI: Auth and deployment boundary - #436 — Web UI: Test coverage and CI checks ## Acceptance criteria (tracker) - [ ] All child issues exist and are linked from this tracker - [ ] Each child issue is independently implementable with clear non-goals - [ ] MVP remains read-only except where gated-action framework explicitly prepares future writes - [ ] No secrets stored in frontend or UI config - [ ] UI reads from canonical workflows/schemas/APIs rather than inventing parallel policy ## Non-goals - Public internet deployment without access controls - Replacing Gitea, MCP servers, or canonical workflow files as policy source - Enabling ungated review/merge/comment/create/delete from the browser in MVP - Building a general-purpose issue/PR editor ## Related work (not duplicates) - Backend worktree cleanup: #401, #404 - Issue/PR leases backend: #267, #268, #407 - MCP hot reload/runtime: #420 - Final-report validator: #327 and follow-ons - MCP Control Plane operator guide tooling (server-side, not web UI) ## Dependencies - Child server skeleton is the foundation for most UI issues - Gitea read APIs / existing MCP read tools supply queue and registry data - Canonical workflows under `skills/llm-project-workflow/workflows/` supply prompt library content
sysadmin commented 2026-07-09 16:08:37 -05:00
Owner
Copy Link
Copy Source

Canonical Issue State

STATE: Complete but stale-open. All 11 child issues (#426–#436) are closed; the tracker itself remains open with unchecked tracker-level acceptance boxes.

WHO_IS_NEXT: author

NEXT_ACTION: Close #425 as complete (reviewer profile prgs-reviewer cannot close issues), or explicitly re-scope if any tracker-level deliverable beyond the closed children is still outstanding.

NEXT_PROMPT:

Close tracker issue #425 (MCP Control Plane web UI) on prgs / Scaled-Tech-Consulting/Gitea-Tools as complete. All 11 child issues #426–#436 are closed. Before closing, confirm no tracker-level acceptance item remains outstanding; if one does, comment the remaining scope instead of closing.

WHAT_HAPPENED: Reviewer audit of tracker #425. Verified every child issue against the closed-issue listing: #426 Server skeleton, #427 Project registry, #428 Prompt library, #429 Queue dashboard, #430 Runtime health / stale-MCP detection, #431 Report audit paste tool, #432 Worktree & branch hygiene, #433 Lease & collision visibility, #434 Gated action framework, #435 Auth & deployment boundary, #436 Test coverage & CI checks — all closed. Child-existence and linkage acceptance criteria are satisfied.

WHY: Tracker work is finished but the issue was left open, leaving stale queue state. Audit records completion and hands off closure to a role authorized to close.

RELATED_PRS: None for this audit (tracker issue, no associated PR).

BLOCKERS: None. Reviewer cannot close issues; closure requires author/controller profile.

VALIDATION: All 11 children confirmed state: closed via reviewer read of the closed-issue listing. No code review performed — this is a tracker, not a PR. No mutations this session prior to this comment.

LAST_UPDATED_BY: prgs-reviewer (sysadmin)

## Canonical Issue State STATE: Complete but stale-open. All 11 child issues (#426–#436) are closed; the tracker itself remains open with unchecked tracker-level acceptance boxes. WHO_IS_NEXT: author NEXT_ACTION: Close #425 as complete (reviewer profile `prgs-reviewer` cannot close issues), or explicitly re-scope if any tracker-level deliverable beyond the closed children is still outstanding. NEXT_PROMPT: ```text Close tracker issue #425 (MCP Control Plane web UI) on prgs / Scaled-Tech-Consulting/Gitea-Tools as complete. All 11 child issues #426–#436 are closed. Before closing, confirm no tracker-level acceptance item remains outstanding; if one does, comment the remaining scope instead of closing. ``` WHAT_HAPPENED: Reviewer audit of tracker #425. Verified every child issue against the closed-issue listing: #426 Server skeleton, #427 Project registry, #428 Prompt library, #429 Queue dashboard, #430 Runtime health / stale-MCP detection, #431 Report audit paste tool, #432 Worktree & branch hygiene, #433 Lease & collision visibility, #434 Gated action framework, #435 Auth & deployment boundary, #436 Test coverage & CI checks — all closed. Child-existence and linkage acceptance criteria are satisfied. WHY: Tracker work is finished but the issue was left open, leaving stale queue state. Audit records completion and hands off closure to a role authorized to close. RELATED_PRS: None for this audit (tracker issue, no associated PR). BLOCKERS: None. Reviewer cannot close issues; closure requires author/controller profile. VALIDATION: All 11 children confirmed `state: closed` via reviewer read of the closed-issue listing. No code review performed — this is a tracker, not a PR. No mutations this session prior to this comment. LAST_UPDATED_BY: prgs-reviewer (sysadmin)
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
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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