heypi's headline feature is approvals, but nothing requires approval by default

What this changes for operators

• The docs are explicit: approval does not make every tool call require approval. Tool confirmation does that. Out of the box the only automatic gate is the bash approval.command() classifier (blocks destructive, asks on risky, allows low-risk); every other tool runs without a human gate until you wire approval/confirm per tool. An operator who adopts heypi for its approvals must author them; the default is not a human-in-the-loop posture.
• The companion 'audit trail' is typed trace events surfaced in the admin panel -- which is itself disabled by default and binds loopback. To actually get the reviewable record the marketing promises, you must enable and operate the admin panel (or read heypi events).
• Before deploying, decide which tools must gate on a named approver and wire them; do not assume the framework's headline posture is its default.