ACP 权限闸门：非 read/search 权限改为显式确认，避免静默越权

• ACP-enabled workflows are in use and include at least one non-read operation.
• Operators know which actions are low-risk read vs high-risk side-effect writes.

1. Inventory ACP actions and tag each permission as read/search or side-effecting write.
2. Run a controlled write-action test and verify explicit permission prompt appears.
3. Update runbooks: require approval evidence for every non-read ACP action.
4. Review audit logs weekly for denied/approved patterns and tighten defaults.

• Human approval quality matters; weak review still permits risky writes.
• Custom ACP adapters may implement permission labels differently（需验证）.

This tip is aggregated from community/public sources and preserved with attribution.