- Shipped
- October 18, 2026 at 7:28 AM UTC
- Author
- Kamo
- Commit
- 9d10e6c
IoT SP11 (master §6.14, §10 SP11-D2): physical actions through the Tool Plane's iot_ pack are charter-approved per class. AiActionClass appends OPERATE_DEVICE (COMFORT/EQUIPMENT functions, automation toggles) and OPERATE_SECURITY_DEVICE (SECURITY functions, automations with a SECURITY action, CRITICAL/MAJOR alarm acknowledgements) after JOIN_MEETING, both APPROVE_BEFORE: an unnamed class resolves to its default, so every charter asks a person until it says otherwise. CharterSection.APPROVAL holds 24 (one per class). Every resolved charter gains the two classes, so every charter stamp moves once (CharterStampTest's legacy golden moves, as JOIN_MEETING's did). AiAutonomyModeTest's draft-kind pin fails on origin/main as well, untouched here.