Thread worktree_path through gitea_create_issue and fail closed on invalid/stable-checkout workspace #450

Closed
opened 2026-07-07 13:40:59 -05:00 by jcwalker3 · 1 comment
Owner

Follow-up hardening for #274 branches-only guard.

gitea_create_issue must thread worktree_path into verify_preflight_purity and fail closed when the resolved mutation workspace is the stable control checkout or an invalid/non-repo branches path.

Acceptance:

  • Stable control checkout rejected with clear RuntimeError
  • Missing/wrong-repo worktree paths fail closed
  • Valid branches/ worktree allowed
  • Focused tests in tests/test_create_issue_workspace_guard.py pass
Follow-up hardening for #274 branches-only guard. `gitea_create_issue` must thread `worktree_path` into `verify_preflight_purity` and fail closed when the resolved mutation workspace is the stable control checkout or an invalid/non-repo branches path. Acceptance: - Stable control checkout rejected with clear RuntimeError - Missing/wrong-repo worktree paths fail closed - Valid branches/ worktree allowed - Focused tests in tests/test_create_issue_workspace_guard.py pass
jcwalker3 added the status:in-progress label 2026-07-07 13:41:30 -05:00
Author
Owner

Issue claim heartbeat

<!-- gitea-issue-claim-heartbeat:v1 --> **Issue claim heartbeat** - kind: claim - issue: #450 - branch: feat/issue-450-create-issue-worktree-guard - 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-07 13:51:02 -05:00
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#450