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

Web UI: Live PR and issue queue dashboard #429

New Issue
Closed
opened 2026-07-07 12:21:01 -05:00 by jcwalker3 · 2 comments
jcwalker3 commented 2026-07-07 12:21:01 -05:00
Owner
Copy Link
Copy Source

Problem statement

Queue state is spread across gitea_list_prs, gitea_list_issues, and manual Gitea browsing. Operators need one read-only dashboard for open work.

Scope

Show live Gitea queue state in the web UI:

  • open PR list with mergeability and linkage
  • open issue list with claim/status signals
  • classification badges for blocked, in-review, claimed, duplicate, stale
  • pagination metadata surfaced

Acceptance criteria

  • Lists open PRs with: number, title, branch, head SHA, mergeable state, linked issue (when detectable)
  • Lists open issues with: number, title, labels/status, claim/status:in-progress if present, linked PR if available
  • Classifies items as blocked, in-review, claimed, duplicate, stale when evidence exists
  • MVP is read-only (no claim/review/merge buttons)
  • Pagination proof is surfaced in the UI (page size, count, has-more/final-page indicator)

Non-goals

  • Performing claims, comments, reviews, or merges from the dashboard
  • Replacing Gitea as system of record
  • Hiding pagination limitations

Relation to tracker

Child of tracker #425. Implements one slice of the MCP Control Plane internal web UI. Does not duplicate backend policy already enforced by MCP tools/workflows.

Dependencies

Depends on #426. Uses Gitea read APIs or existing MCP read tools server-side.

Notes

Related backend: #194, #202, #340 (pagination/trust gates). UI must not claim empty queue without pagination proof.

## Problem statement Queue state is spread across `gitea_list_prs`, `gitea_list_issues`, and manual Gitea browsing. Operators need one read-only dashboard for open work. ## Scope Show live Gitea queue state in the web UI: - open PR list with mergeability and linkage - open issue list with claim/status signals - classification badges for blocked, in-review, claimed, duplicate, stale - pagination metadata surfaced ## Acceptance criteria - Lists open PRs with: number, title, branch, head SHA, mergeable state, linked issue (when detectable) - Lists open issues with: number, title, labels/status, claim/`status:in-progress` if present, linked PR if available - Classifies items as blocked, in-review, claimed, duplicate, stale when evidence exists - MVP is read-only (no claim/review/merge buttons) - Pagination proof is surfaced in the UI (page size, count, has-more/final-page indicator) ## Non-goals - Performing claims, comments, reviews, or merges from the dashboard - Replacing Gitea as system of record - Hiding pagination limitations ## Relation to tracker Child of tracker #425. Implements one slice of the MCP Control Plane internal web UI. Does not duplicate backend policy already enforced by MCP tools/workflows. ## Dependencies Depends on #426. Uses Gitea read APIs or existing MCP read tools server-side. ## Notes Related backend: #194, #202, #340 (pagination/trust gates). UI must not claim empty queue without pagination proof.
jcwalker3 added the status:in-progress label 2026-07-07 12:53:16 -05:00
jcwalker3 commented 2026-07-07 12:53:16 -05:00
Author
Owner
Copy Link
Copy Source

Issue claim heartbeat

<!-- gitea-issue-claim-heartbeat:v1 --> **Issue claim heartbeat** - kind: claim - issue: #429 - branch: pending - phase: claimed - profile: prgs-author - pr: none - blocker: none - next_action: create worktree and begin implementation
jcwalker3 commented 2026-07-07 12:56:33 -05:00
Author
Owner
Copy Link
Copy Source

Issue claim heartbeat

<!-- gitea-issue-claim-heartbeat:v1 --> **Issue claim heartbeat** - kind: claim - issue: #429 - branch: feat/issue-429-queue-dashboard - phase: claimed - profile: prgs-author - pr: none - blocker: none - next_action: create worktree and begin implementation
sysadmin removed the status:in-progress label 2026-07-07 14:13:29 -05:00
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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