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

Fix MCP remote default repo mismatch for prgs #530

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

Problem:
During PR #527 / issue #515 routing, bare remote=prgs resolved to the wrong repository, apparently an absence-categories app with PR #1 base main, instead of Scaled-Tech-Consulting/Gitea-Tools. This caused false 404s when looking up PR #527 and issue #515.

Observed correct repository:

  • Local git remote prgs = https://gitea.prgs.cc/Scaled-Tech-Consulting/Gitea-Tools.git
  • Correct MCP calls require explicit:
    • org=Scaled-Tech-Consulting
    • repo=Gitea-Tools

Risk:
LLM sessions may falsely conclude issues/PRs do not exist, create duplicates, skip reviews, or mutate the wrong repository if MCP defaults disagree with the local git remote.

Required behavior:

  1. MCP remote resolution must agree with the local git remote when operating inside a Gitea-Tools worktree.
  2. If a bare remote name resolves ambiguously or to a repo different from the local git remote, the tool must block and require explicit org/repo.
  3. False 404s caused by repo mismatch should include a diagnostic hint showing the resolved repo.
  4. Workflow docs and canonical prompts should require explicit org/repo until the bug is fixed.

Acceptance criteria:

  • Add regression coverage for remote=prgs resolving to the wrong repo.
  • Add a guard that detects mismatch between local git remote URL and MCP resolved org/repo.
  • Add tests proving PR/issue lookup cannot silently query a different repository.
  • Update reviewer/author/merger handoff templates to include explicit org/repo fields.
Problem: During PR #527 / issue #515 routing, bare `remote=prgs` resolved to the wrong repository, apparently an absence-categories app with PR #1 base `main`, instead of `Scaled-Tech-Consulting/Gitea-Tools`. This caused false 404s when looking up PR #527 and issue #515. Observed correct repository: - Local git remote `prgs` = `https://gitea.prgs.cc/Scaled-Tech-Consulting/Gitea-Tools.git` - Correct MCP calls require explicit: - `org=Scaled-Tech-Consulting` - `repo=Gitea-Tools` Risk: LLM sessions may falsely conclude issues/PRs do not exist, create duplicates, skip reviews, or mutate the wrong repository if MCP defaults disagree with the local git remote. Required behavior: 1. MCP remote resolution must agree with the local git remote when operating inside a Gitea-Tools worktree. 2. If a bare remote name resolves ambiguously or to a repo different from the local git remote, the tool must block and require explicit org/repo. 3. False 404s caused by repo mismatch should include a diagnostic hint showing the resolved repo. 4. Workflow docs and canonical prompts should require explicit org/repo until the bug is fixed. Acceptance criteria: - Add regression coverage for `remote=prgs` resolving to the wrong repo. - Add a guard that detects mismatch between local git remote URL and MCP resolved org/repo. - Add tests proving PR/issue lookup cannot silently query a different repository. - Update reviewer/author/merger handoff templates to include explicit org/repo fields.
jcwalker3 added the status:in-progress label 2026-07-08 14:34:55 -05:00
jcwalker3 commented 2026-07-08 14:34:55 -05:00
Author
Owner
Copy Link
Copy Source

Issue claim heartbeat

<!-- gitea-issue-claim-heartbeat:v1 --> **Issue claim heartbeat** - kind: claim - issue: #530 - branch: fix/issue-530-remote-repo-mismatch - 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-08 21:07:04 -05:00
jcwalker3 commented 2026-07-09 12:15:34 -05:00
Author
Owner
Copy Link
Copy Source

Canonical Issue State

STATE: regressed-follow-up-filed
WHO_IS_NEXT: author
NEXT_ACTION: implement follow-up for control-plane guide schema/local alignment
NEXT_PROMPT:

See the new follow-up issue filed for mcp_get_control_plane_guide org/repo schema gap after #530.

WHAT_HAPPENED: Live controller triage hit #530 guard on mcp_get_control_plane_guide(remote=prgs); remediation demanded org/repo but the guide schema lacked those parameters.
WHY: #530 guard is correct for mutations; guide bootstrap was left unusable.
RELATED_PRS: #555
BLOCKERS: none (follow-up tracks residual)
VALIDATION: reproduced mcp_get_control_plane_guide(remote=prgs) -> Timesheet vs Gitea-Tools mismatch with impossible recovery
LAST_UPDATED_BY: jcwalker3 (prgs-author)

## Canonical Issue State STATE: regressed-follow-up-filed WHO_IS_NEXT: author NEXT_ACTION: implement follow-up for control-plane guide schema/local alignment NEXT_PROMPT: ```text See the new follow-up issue filed for mcp_get_control_plane_guide org/repo schema gap after #530. ``` WHAT_HAPPENED: Live controller triage hit #530 guard on mcp_get_control_plane_guide(remote=prgs); remediation demanded org/repo but the guide schema lacked those parameters. WHY: #530 guard is correct for mutations; guide bootstrap was left unusable. RELATED_PRS: #555 BLOCKERS: none (follow-up tracks residual) VALIDATION: reproduced mcp_get_control_plane_guide(remote=prgs) -> Timesheet vs Gitea-Tools mismatch with impossible recovery LAST_UPDATED_BY: jcwalker3 (prgs-author)
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#530