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

Web Console: Requests, intent preview, authorization, and workflow initiation (Phase 2) #643

New Issue
Open
opened 2026-07-10 14:40:42 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-10 14:40:42 -05:00
Owner
Copy Link
Copy Source

Problem statement

Operators need to submit requests (start author/reviewer/merger/controller work) with intent preview, authorization checks, and safe workflow initiation without pasting prompts or bypassing allocator/leases.

User and operational impact

Manual prompt paste and unsafe self-selection of work continue; concurrent collisions remain likely.

Scope

  • Request model: desired role, issue/PR, intent summary.
  • Preview: capability check, lease availability, next-safe-action, prohibited actions.
  • Initiate only via allocator/sanctioned tools; record assignment + audit.
  • UI form + API behind RBAC (#633); dry-run default.

Explicit non-goals

  • No direct browser Gitea merge/approve.
  • No bypass of allocator exclusive ownership (#600/#613).
  • No auto-start from raw monitoring incidents.

Required implementation investigation

allocator_service.py, #600, #613, #434 gated actions, #633, #640 traffic view, #628, #631.

Proposed architecture or implementation direction

POST /api/v1/requests/preview and .../apply with confirmation; server calls allocator; returns assignment handoff reference.

Security and workflow-safety requirements

RBAC; fail closed; audit; head pinning for PR work; no silent lease steal.

Acceptance criteria

  1. Preview shows authorize/deny with reasons.
  2. Apply creates exclusive assignment or returns wait/blocked.
  3. Duplicate assign rejected.
  4. Tests for preview/apply/deny/collision.
  5. UI never shows full secrets; brief user messaging.

Required tests

Allocator integration tests with fakes; gated action tests.

Observability and audit requirements

Audit every preview apply; correlation id to assignment.

Dependencies and linkage

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Implement request preview/initiate after auth+traffic
NEXT_PROMPT: Author request initiation gates; PR; stop

Required final evidence

PR with APIs, UI, tests, docs.

Required final response and handoff expectations

Brief PR → reviewer.

## Problem statement Operators need to submit **requests** (start author/reviewer/merger/controller work) with **intent preview**, authorization checks, and safe **workflow initiation** without pasting prompts or bypassing allocator/leases. ## User and operational impact Manual prompt paste and unsafe self-selection of work continue; concurrent collisions remain likely. ## Scope * Request model: desired role, issue/PR, intent summary. * Preview: capability check, lease availability, next-safe-action, prohibited actions. * Initiate only via allocator/sanctioned tools; record assignment + audit. * UI form + API behind RBAC (#633); dry-run default. ## Explicit non-goals * No direct browser Gitea merge/approve. * No bypass of allocator exclusive ownership (#600/#613). * No auto-start from raw monitoring incidents. ## Required implementation investigation `allocator_service.py`, #600, #613, #434 gated actions, #633, #640 traffic view, #628, #631. ## Proposed architecture or implementation direction `POST /api/v1/requests/preview` and `.../apply` with confirmation; server calls allocator; returns assignment handoff reference. ## Security and workflow-safety requirements RBAC; fail closed; audit; head pinning for PR work; no silent lease steal. ## Acceptance criteria 1. Preview shows authorize/deny with reasons. 2. Apply creates exclusive assignment or returns wait/blocked. 3. Duplicate assign rejected. 4. Tests for preview/apply/deny/collision. 5. UI never shows full secrets; brief user messaging. ## Required tests Allocator integration tests with fakes; gated action tests. ## Observability and audit requirements Audit every preview apply; correlation id to assignment. ## Dependencies and linkage * Parent: #631 · Depends: #633, #640 · Related: #600, #613, #628, #434 ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Implement request preview/initiate after auth+traffic NEXT_PROMPT: Author request initiation gates; PR; stop ``` ## Required final evidence PR with APIs, UI, tests, docs. ## Required final response and handoff expectations Brief PR → reviewer.
jcwalker3 added the type:featurestatus:readyworkflow-hardeningdashboard labels 2026-07-10 14:40:43 -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 dashboard 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#643