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

Web Console: Workflow traffic-control view (Phase 1) #640

New Issue
Open
opened 2026-07-10 14:39:59 -05:00 by jcwalker3 · 1 comment
jcwalker3 commented 2026-07-10 14:39:59 -05:00
Owner
Copy Link
Copy Source

Problem statement

MVP queue (#429) lists PRs/issues but does not provide full traffic-control visibility: runnable vs blocked, dependency waits, exclusive ownership, next safe role, and concurrent-path status aligned with #628 orchestration goals.

User and operational impact

Operators and controllers cannot see “city traffic” of work: collisions, blocked intersections, or free lanes for independent work.

Scope

  • Traffic-control view combining queue snapshot + inventory leases + blocker classification.
  • Columns/sections: runnable, in-progress (leased), blocked (dependency), needs-controller, terminal-complete candidates.
  • Show next-safe role when known; never suggest blocked work as safe (#605 alignment).
  • Read-only Phase 1; no assignment mutations from browser.

Explicit non-goals

  • No allocator assign button yet (Phase 2/3).
  • No raw Sentry incidents as work items.
  • Do not replace MCP menu (#605); complement it.

Required implementation investigation

queue_loader.py, #429, #636 inventory, allocator_service, #605, #628, #603 labels, #631.

Proposed architecture or implementation direction

Server-side compose queue + inventory; traffic DTO; HTML view with clear state vocabulary matching workflow labels where possible.

Security and workflow-safety requirements

Fail closed on ambiguous ownership display; never invent leases; redact sensitive branch paths if required.

Acceptance criteria

  1. View distinguishes runnable / leased / blocked / controller-needed.
  2. Blocked items show blocker reason when known.
  3. Does not mark blocked items as safe.
  4. Tests with fixture queues and leases.
  5. Docs describe traffic semantics.

Required tests

Fixture-based render/API tests for state buckets.

Observability and audit requirements

Read-only.

Dependencies and linkage

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Implement traffic-control view
NEXT_PROMPT: Author traffic view; PR; stop

Required final evidence

PR with view, tests, docs.

Required final response and handoff expectations

Brief PR → reviewer.

## Problem statement MVP queue (#429) lists PRs/issues but does not provide full **traffic-control visibility**: runnable vs blocked, dependency waits, exclusive ownership, next safe role, and concurrent-path status aligned with #628 orchestration goals. ## User and operational impact Operators and controllers cannot see “city traffic” of work: collisions, blocked intersections, or free lanes for independent work. ## Scope * Traffic-control view combining queue snapshot + inventory leases + blocker classification. * Columns/sections: runnable, in-progress (leased), blocked (dependency), needs-controller, terminal-complete candidates. * Show next-safe role when known; never suggest blocked work as safe (#605 alignment). * Read-only Phase 1; no assignment mutations from browser. ## Explicit non-goals * No allocator assign button yet (Phase 2/3). * No raw Sentry incidents as work items. * Do not replace MCP menu (#605); complement it. ## Required implementation investigation `queue_loader.py`, #429, #636 inventory, allocator_service, #605, #628, #603 labels, #631. ## Proposed architecture or implementation direction Server-side compose queue + inventory; traffic DTO; HTML view with clear state vocabulary matching workflow labels where possible. ## Security and workflow-safety requirements Fail closed on ambiguous ownership display; never invent leases; redact sensitive branch paths if required. ## Acceptance criteria 1. View distinguishes runnable / leased / blocked / controller-needed. 2. Blocked items show blocker reason when known. 3. Does not mark blocked items as safe. 4. Tests with fixture queues and leases. 5. Docs describe traffic semantics. ## Required tests Fixture-based render/API tests for state buckets. ## Observability and audit requirements Read-only. ## Dependencies and linkage * Parent: #631 · Extends: #429 · Soft-depends: #636 · Related: #605, #628, #603 ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Implement traffic-control view NEXT_PROMPT: Author traffic view; PR; stop ``` ## Required final evidence PR with view, tests, docs. ## Required final response and handoff expectations Brief PR → reviewer.
jcwalker3 added the type:featurestatus:readyworkflow-hardeningdashboardqueue labels 2026-07-10 14:40:00 -05:00
jcwalker3 commented 2026-07-10 14:49:47 -05:00
Author
Owner
Copy Link
Copy Source

Canonical Issue State

STATE:
ready-for-author

WHO_IS_NEXT:
author

NEXT_ACTION:
Implement workflow queue/traffic-control view; link #652 #653 Phase 1

NEXT_PROMPT:

AUTHOR prgs Gitea-Tools. Implement #640. Vision #652 · Roadmap #653 Phase 1 · Soft-depends #636 · Extends #429 · Related #605 #628. Lock; branches/; PR; stop. Closing ≠ vision complete.

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

WHY:
Initial batch linkage.

RELATED_ISSUES:
#652 #653 #631 #636 #429 #605 #628

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: Implement workflow queue/traffic-control view; link #652 #653 Phase 1 NEXT_PROMPT: ```text AUTHOR prgs Gitea-Tools. Implement #640. Vision #652 · Roadmap #653 Phase 1 · Soft-depends #636 · Extends #429 · Related #605 #628. Lock; branches/; PR; stop. Closing ≠ vision complete. ``` WHAT_HAPPENED: Linked to #652/#653. Not recreated. WHY: Initial batch linkage. RELATED_ISSUES: #652 #653 #631 #636 #429 #605 #628 RELATED_PRS: none BLOCKERS: none VALIDATION: existing retained LAST_UPDATED_BY: jcwalker3 / prgs-author / author / 2026-07-10
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 queue 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#640