Why: Plan mode has to block writes, and confirmations dropped the argument preview.
Evidence: store, tools, runmgr, runtime, and server tests passed.
Impact: Empty mode keeps the profile lists. High-risk shell commands ask. There is no bypass-all mode.
Refs: feature/permission-hooks
Why: Plan mode has to block writes, and confirmations dropped the argument preview.
Evidence: store, tools, runmgr, runtime, and server tests passed.
Impact: Empty mode keeps the profile lists. High-risk shell commands ask. There is no bypass-all mode.
Refs: feature/permission-hooks
Why: Plan mode has to block writes, confirmations dropped the argument preview, and direct chat did not share its stop gate with squad members.
Evidence: GOWORK=off go test ./internal/store/ ./internal/tools/ ./internal/runmgr/ ./internal/runtime/ ./internal/server/ passed. Default mode still runs write_artifact; plan mode rejects it.
Impact: Empty permission mode keeps the profile allow, deny, and confirm lists. High-risk shell commands now ask. There is no bypass-all mode.
Refs: feature/permission-hooks
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Those three branches were replayed onto origin/main after the first pin.
Evidence: native 0a52d9f, squad beea97e, and core cf7df54 each contain origin/main.
Impact: The backend build uses the same commits that will be merged.
Refs: feature/permission-hooks
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit ebfa7677e4 into main2026-10-03 17:06:49 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: Plan mode has to block writes, and confirmations dropped the argument preview.
Evidence: store, tools, runmgr, runtime, and server tests passed.
Impact: Empty mode keeps the profile lists. High-risk shell commands ask. There is no bypass-all mode.
Refs: feature/permission-hooks