Feature: Auto-approve routine breakpoints based on historical patterns

[rogelsm]

Summary

Routine breakpoints (prerequisite checks, installation verifications) are always approved and add manual overhead without decision value. The SDK could learn from approval history and auto-approve predictable breakpoints.

Motivation

From cross-run retrospect of 25 runs:

• 12+ prerequisite check breakpoints were always approved
• Installation verification breakpoints (3 occurrences) always approved
• These add ~20 seconds of human wait time each with no decision value
• Only design review and PR submission breakpoints provided meaningful steering

Suggested Approach

1. Track breakpoint approval history per breakpoint type/tag
2. After N consecutive approvals of the same pattern, offer auto-approval
3. User profile integration: respect breakpointTolerance and alwaysBreakOn settings
4. Tags-based rules: auto-approve prerequisites tag after 3 approvals
5. Never auto-approve: destructive, deploy, or custom alwaysBreakOn tags

Breakpoint Categories

Category	Frequency	Always Approved	Auto-Approve Candidate
Prerequisite checks	12	Yes	✅
Installation verification	3	Yes	✅
Design review	6	No	❌
Final review/contribute	4	No	❌

---

Identified during cross-run retrospect analysis of 25 babysitter runs