[EdbertChan]

Summary

Sometimes the agent hands the user a command to run without trying it first. The command can then fail on its first line, and the user pays twice.

This adds a standing rule. Try the first step yourself. Hand it back only for a password, a browser login, hardware, or a system approval dialog.

A missing tool is not a blocker. Install it.

Review Claim

Approve a rule that requires trying a step before handing it to the user, and limits handoffs to steps only the user can do.

Review Lane

behavior

Review Unit

corpus-lesson

Safety Invariant

It adds one rule line and changes no code. Removing the line restores the previous behavior.

Slice Rationale

The rule is a different kind of file from the hook switch and the planning guide, so it ships on its own.

Non-goals

• No new hook or check; the hook switch ships separately.
• No change to the existing rule about writing a handoff as a single script line.

Measured

none: this adds a rule line; there is no number to measure

Test Plan

Test Plan

• python3 scripts/ci/check_no_dated_provenance.py --base origin/main printed ok no dated provenance
• python3 scripts/ci/check_codify_has_code.py --base origin/main printed ok codify-has-code
• python3 engine/skills/make-pr/scripts/rule_scope_check.py --base origin/main printed ok no incident-scoped rules
• python3 engine/skills/make-pr/scripts/preflight.py --base origin/main --dry-run printed unit corpus-lesson: 1 file(s) and ok preflight passed
• Not run: a live session that follows the rule. Blocker: the rule loads only after install, in a new session

Revert Plan

Revert Plan

• Safe to revert? Yes
• Revert command: git revert <sha>
• Post-revert steps: None
• Data migration? No

🤖 Generated with Claude Code

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 52d6b17f-9f96-476a-92ec-872b5c9092b8)

[mergify]

Queued — the merge queue status continues in this comment ↓.

[EdbertChan]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-12 20:05 UTC · Rule: admin-bypass · triggered by @EdbertChan with the @mergifyio queue command
• ❌ Checks failed — 2026-10-12 20:24 UTC · on draft merge queue: checking #1332 + #1354 + #1358 + #1359 together on main (2f93d6c) #1361
• ✂️ Bisecting to identify the failing PR (round 1/1)
• ✅ Checks passed · on draft merge queue: checking #1358 + #1359 + #1336 together on main (76f7a53) #1366
• ✅ Merged — 2026-10-12 22:58 UTC · at b6dadd3c653884edac75ba7ddd6ce1414d7ced40 · squash

This pull request spent 2 hours 53 minutes 17 seconds in the queue, including 1 hour 42 minutes 19 seconds running CI.

Required conditions to merge

• check-success = lint
• check-success = test
• check-success = validate