also looking at this
feat(ios): the speech pair closes the last deferral — ratchet 28 -> 26
#101
10 files
+1287
-573
| @@ -259,7 +259,14 @@ fn schedulePattern(items: []const std.json.Value) !usize { | ||
| 259 | 259 | /// "returned without error" means "UIKit accepted the call", never "the device |
| 260 | 260 | /// buzzed", which is the other half of why `haptic` has no success reply to |
| 261 | 261 | /// fabricate. |
| 262 | fn triggerHapticChecked(haptic_type: HapticType) !void { | |
| 262 | /// | |
| 263 | /// `pub` for one caller outside this file. `bridge_mobile_speech.zig` fires a | |
| 264 | /// light impact on start and on stop because `CraftApp.swift:2544` and `:2558` | |
| 265 | /// do — directly, bypassing the `config.enableHaptics` check the dispatcher | |
| 266 | /// applies to `case "haptic"` at `:537`. That bypass is the spec's, not a | |
| 267 | /// choice this module makes, and routing the speech path through the gated | |
| 268 | /// entry point would be the divergence rather than the fix. | |
| 269 | pub fn triggerHapticChecked(haptic_type: HapticType) !void { | |
| 263 | 270 | if (!builtin.target.os.tag.isDarwin()) return error.UnsupportedPlatform; |
| 264 | 271 | |
| 265 | 272 | switch (haptic_type) { |