Skip to content

feat(feedback): adopt merged upstream adapter capabilities - #127

Merged
joeblau merged 2 commits into
hig/roadmap-followupsfrom
hig/issue-70-adapters
Oct 19, 2026
Merged

joeblau merged 2 commits into
hig/roadmap-followupsfrom
hig/issue-70-adapters

Conversation

@joeblau

@joeblau joeblau commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

HIG feedback roots can now pass independent abort signals to the merged SFX engine, so cancel/mute/background/dispose stop that root’s voices while other roots and host-owned playback continue. The browser haptic adapter also accepts the merged canTriggerHaptic/triggerHaptic functions through an optional injected backend, probing current capability without a new eager import.

Stacked on #126 (hig/roadmap-followups); this diff contains only feedback adapters, focused integration/boundary tests, documentation and evidence. Refs #70.

Validation: full Node 22.22 check passed (174 web / 161 native tests, build/lint/types/docs); 23 focused tests include 11 cases against exact MIT upstream sources and actual released 0.1.0. SSR, clean packed consumers and the injectable haptic entry without React/SFX/Haptic peers pass. Source pins, licenses, hashes and logs are in tests/fixtures/upstream-feedback/ and evidence/feedback/issue-70/report.json.

Published SFX 0.1.0 ignores the extra signal and still cannot stop an active voice; published Haptic 0.1.0 lacks the imperative exports. Released adoption remains pending. iOS imperative haptics remain unavailable, browser vibration cancellation remains document-wide, and physical output/latency certification is unchanged. No dependencies/lock, coordinated candidate, release, deployment or device actuation changed. Remote CI is pending at draft creation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant