Scaled-Tech-Consulting/Gitea-Tools
4
0
Fork 0
Code Issues 110 Pull Requests 12 Actions Packages Projects Releases Wiki Activity

feat(workflow): add native author workflow loading for work-issue mode #873

New Issue
Open
opened 2026-07-24 02:00:23 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-24 02:00:23 -05:00
Owner
Copy Link
Copy Source

Problem

An authenticated prgs-author session cannot establish canonical author workflow-load proof for issue work or conflict remediation. The available loader returned the reviewer workflow even when the requested task was work-issue.

Reproduction

  1. Start a fresh gitea-author / prgs-author session.
  2. Complete identity and runtime-parity preflight.
  3. Request the canonical author workflow for work-issue.
  4. Observe that the returned workflow is review-merge-pr.md with task mode review-merge-pr.

Expected behavior

An author session must have a sanctioned native capability that returns:

  • workflow source:
    skills/llm-project-workflow/workflows/work-issue.md
  • task mode:
    work-issue
  • valid workflow-load proof scoped to the author role and current session.

Reviewer sessions must continue receiving review-merge-pr.md.

Acceptance criteria

  1. A native MCP loader supports the author work-issue workflow.
  2. Routing is role-aware and fail-closed.
  3. Author sessions receive work-issue.md.
  4. Reviewer sessions continue receiving review-merge-pr.md.
  5. Unsupported task modes and role/task mismatches are rejected clearly.
  6. Workflow-load proof records the selected source, task mode, role, profile, and session.
  7. MCP tool registration and schemas expose the supported author path.
  8. Focused tests cover author loading, reviewer loading, invalid modes, role mismatches, proof generation, and MCP registration.
  9. Runtime/restart documentation identifies whether namespaces must be restarted after deployment.
  10. A fresh standalone author session verifies the corrected behavior after the fix reaches live master.

Investigation note

The exact implementation cause is intentionally unasserted. Determine it through the sanctioned author workflow during implementation. Do not rely on the earlier controller session’s direct filesystem inspection as proof.

### Problem An authenticated `prgs-author` session cannot establish canonical author workflow-load proof for issue work or conflict remediation. The available loader returned the reviewer workflow even when the requested task was `work-issue`. ### Reproduction 1. Start a fresh `gitea-author / prgs-author` session. 2. Complete identity and runtime-parity preflight. 3. Request the canonical author workflow for `work-issue`. 4. Observe that the returned workflow is `review-merge-pr.md` with task mode `review-merge-pr`. ### Expected behavior An author session must have a sanctioned native capability that returns: * workflow source: `skills/llm-project-workflow/workflows/work-issue.md` * task mode: `work-issue` * valid workflow-load proof scoped to the author role and current session. Reviewer sessions must continue receiving `review-merge-pr.md`. ### Acceptance criteria 1. A native MCP loader supports the author `work-issue` workflow. 2. Routing is role-aware and fail-closed. 3. Author sessions receive `work-issue.md`. 4. Reviewer sessions continue receiving `review-merge-pr.md`. 5. Unsupported task modes and role/task mismatches are rejected clearly. 6. Workflow-load proof records the selected source, task mode, role, profile, and session. 7. MCP tool registration and schemas expose the supported author path. 8. Focused tests cover author loading, reviewer loading, invalid modes, role mismatches, proof generation, and MCP registration. 9. Runtime/restart documentation identifies whether namespaces must be restarted after deployment. 10. A fresh standalone author session verifies the corrected behavior after the fix reaches live master. ### Investigation note The exact implementation cause is intentionally unasserted. Determine it through the sanctioned author workflow during implementation. Do not rely on the earlier controller session’s direct filesystem inspection as proof.
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
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 jwalker superadmin sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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