[mcp][preflight] Propagate explicit org/repo through all author mutation call sites #735

Closed
opened 2026-07-17 22:41:24 -05:00 by jcwalker3 · 0 comments
Owner

Problem

Native prgs-author mutations targeting Scaled-Tech-Consulting/Gitea-Tools fail anti-stomp preflight with wrong_repo because explicit org/repo coordinates are not propagated through every mutation call site.

Observed during create_issue:

  • Explicit target: Scaled-Tech-Consulting/Gitea-Tools
  • Incorrect resolved target: Scaled-Tech-Consulting/Timesheet
  • Mutation stage: preflight_purity
  • Blocker: wrong_repo
  • Performed: false
  • Retryable: false

Issue #733 fixed this forwarding for reconciler delete_branch only. Author mutations remain affected, blocking autonomous issue creation and PR workflows.

Acceptance criteria

  • Inventory every author mutation call to verify_preflight_purity and related workspace/anti-stomp gates.
  • Forward explicit org/repo through create_issue, lock_issue, mark_issue, issue comments, commit/push, create_pr, and other author mutations.
  • Use a shared repository-context contract rather than independent call-site fixes where practical.
  • Do not change REMOTES["prgs"]["repo"] as a workaround.
  • Keep missing, inconsistent, substituted, or unauthorized coordinates fail-closed.
  • Add cross-repository tests where prgs defaults to Timesheet while the explicit target is Gitea-Tools.
  • Verify native create_issue, issue locking, commit/push, and create_pr end to end.
  • Preserve branches-only, identity, capability, anti-stomp, and repository-binding gates.
  • Clean up the temporary branches/chore-tmp-create-issue-pytest-runner worktree only after proving it is clean and contains no unique work.

Readiness proof

After merge and MCP restart, use native prgs-author to create the pending pytest-runner issue without operator intervention.

## Problem Native prgs-author mutations targeting Scaled-Tech-Consulting/Gitea-Tools fail anti-stomp preflight with wrong_repo because explicit org/repo coordinates are not propagated through every mutation call site. Observed during create_issue: - Explicit target: Scaled-Tech-Consulting/Gitea-Tools - Incorrect resolved target: Scaled-Tech-Consulting/Timesheet - Mutation stage: preflight_purity - Blocker: wrong_repo - Performed: false - Retryable: false Issue #733 fixed this forwarding for reconciler delete_branch only. Author mutations remain affected, blocking autonomous issue creation and PR workflows. ## Acceptance criteria - Inventory every author mutation call to verify_preflight_purity and related workspace/anti-stomp gates. - Forward explicit org/repo through create_issue, lock_issue, mark_issue, issue comments, commit/push, create_pr, and other author mutations. - Use a shared repository-context contract rather than independent call-site fixes where practical. - Do not change REMOTES["prgs"]["repo"] as a workaround. - Keep missing, inconsistent, substituted, or unauthorized coordinates fail-closed. - Add cross-repository tests where prgs defaults to Timesheet while the explicit target is Gitea-Tools. - Verify native create_issue, issue locking, commit/push, and create_pr end to end. - Preserve branches-only, identity, capability, anti-stomp, and repository-binding gates. - Clean up the temporary branches/chore-tmp-create-issue-pytest-runner worktree only after proving it is clean and contains no unique work. ## Readiness proof After merge and MCP restart, use native prgs-author to create the pending pytest-runner issue without operator intervention.
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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