3 Commits

Include renames

Author	SHA1	Message	Date
jcwalker3andClaude Opus 4.8 (1M context) <[email protected]>	a09c485fc0	fix(scope): wire author bootstrap scope into workflow scope guard (Closes #941) ... PR #926 (#892) taught create_issue_bootstrap.bootstrap_permits_control_checkout to accept task_scope=author_issue_bootstrap and wired that canonical decision into the #274 branches-only enforcer and the #604 anti-stomp preflight. A third enforcement path was left unwired. workflow_scope_guard kept its own copy of the clean-root author decision, gated on create_issue_bootstrap.is_create_issue_task -- a task-name allowlist that never contained bootstrap_author_issue_worktree. The real call path gitea_bootstrap_author_issue_worktree -> verify_preflight_purity -> _enforce_issue_scope_guard -> workflow_scope_guard.assess_production_mutation_guards therefore raised ProductionGuardError(missing_issue_worktree) before assess_author_issue_bootstrap was ever consulted, leaving the #892 deadlock partially present and blocking issue #931. Changes: * workflow_scope_guard.assess_root_source_mutation accepts the server-derived bootstrap_assessment and, for the clean-root author case, consults the canonical bootstrap_permits_control_checkout decision instead of a local task-name allowlist. The create_issue arm is unchanged. * workflow_scope_guard.assess_production_mutation_guards forwards the evidence. * _enforce_issue_scope_guard accepts and threads the same assessment the #274 and #604 guards already consume, so all three judge identical evidence, and waives the pre-ownership issue-lock requirement for the bootstrap task via that same canonical decision rather than a second task-name allowlist. * verify_preflight_purity passes the once-computed assessment at both sites. The waiver cannot widen: the predicate fails closed on missing, malformed, cross-scope, dirty, drifted, or wrongly bound evidence, so ordinary author source and test mutation from the control checkout stays forbidden and the #274/#604/#618/#683 protections are unchanged. Regression: tests/test_issue_941_scope_guard_bootstrap_wiring.py drives the real enforcer rather than the authorization helper in isolation, which is why #892's own predicate tests passed while the live bootstrap stayed blocked. Closes #941 Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>	2026-07-26 05:00:09 -05:00
sysadmin	e349839fd7	fix(mcp): allow create_issue from clean control checkout (#749) ... Provide a narrow phase-scoped bootstrap so gitea_create_issue can run from a clean canonical control checkout when no issue number—and therefore no issue-backed worktree—can exist yet. Dirty roots, non-base branches, base races, foreign workspaces, and all post-creation author mutations remain fail-closed under the ordinary branches-only guard. Closes #749.	2026-07-18 16:19:04 -04:00
sysadmin	d302602567	feat(guard): harden workflow against unattributed root WIP and pytest-disabled production guards (Closes #683) ... Add shared workflow_scope_guard with typed blockers (blocker_kind + exact_next_action) and force-on production enforcement under pytest. Wire root/branches/scope checks through verify_preflight_purity and mutation entrypoints (create_issue, comment_issue) without adopting the rejected 300a4ca patterns (test-mode early-return, porcelain *.py filter). Regression suite covers out-of-scope issue ownership, root diagnostic edits, worktree bind success path, force-on under pytest, porcelain integrity, monkeypatch resistance, real entrypoint fail-closed proof, and durable failure recording.	2026-07-12 13:15:58 -04:00