GB-M0 — Hardware Feasibility - #3
Draft
PNHD wants to merge 7 commits into
Draft
Conversation
Owner
Author
|
M0 tracking update:
Pinned R4 research snapshot: Keep PR draft and do not merge while critical hardware gates remain pending. |
This was referenced Aug 11, 2026
Adds the iOS GATT inventory, Watch6 SDP-resolved RFCOMM probe, bounded/redacted reports, hardware runbook, and explicit HARDWARE_REQUIRED gate without sending protocol commands.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Tracking PR for
GB-M0 — Hardware Feasibility.This PR starts with project contracts/research and will collect implementation incrementally behind real-hardware gates.
Workstreams
GB-M0-R1— iPhone ↔ Watch6 BLE Transport PoC — READY / highest implementation priorityGB-M0-R4— Buds2 Pro Transport Critical Spike — Phase A research verified; hardware probes pendingGB-M0-R2— ANCS notification bridge — blocked by R1 shared scaffold for implementationGB-M0-R3— Health sensor → HealthKit minimum path — blocked by R1 shared scaffold for end-to-end implementationR4 verified baseline
Pinned upstream research snapshot:
timschneeb/GalaxyBudsClient@dce4735d76cd16abb818cdd96bf458efd4abef47First SM-R510 RFCOMM candidate service UUID:
2e73a4ad-332d-41fc-90e2-16bef06523f2No Buds transport capability is accepted until physical iPhone/Watch/Buds tests pass.
Acceptance authority
Real iPhone 17e + Galaxy Watch6 + Galaxy Buds2 Pro evidence overrides emulator/mock/software-only claims.
Merge policy
DO NOT MERGE while M0 transport gates remain hardware-pending. Keep this PR draft until explicitly reviewed.