Repository navigation
docs(skills): record the iOS 27 hardware testing findings - #103
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #103 +/- ##
=======================================
Coverage 69.47% 69.47%
=======================================
Files 14 14
Lines 3240 3240
=======================================
Hits 2251 2251
Misses 989 989 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Status updated from the July "still flaky" note to what hardware testing on 2026-09-27 measured: the remaining fault is the Pi to iPhone leg at session startup (#102). Adds a test-rig check for the Continuity relay false alarm, the per-hop audio probe method, and the controller's 16 kHz RTP clock finding. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds a triage row and a failure-archaeology entry for the 2026-09-27 test calls that went silent both ways. The cause was the MacBook relaying the call through the Home-app iPhone, not the server. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Test calls answered on a Mac that relays through the Home-app iPhone go silent once the live view opens. A Twilio-to-itself call with inline TwiML gives a scripted, recorded visitor without a second phone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reference said ringback plays while the doorbell rings unanswered. The call is in fact answered as soon as the TwiML returns, and the Pi's ringback disguises that. Records why ringback outlasts an answer on the PSTN and why its end is the visitor's cue to speak. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
atdr
force-pushed
the
docs/skills-after-ios27-testing
branch
from
September 27, 2026 19:25
16fb6cd to
3a4a8e8
Compare
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
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.
Summary
Records what hardware testing of #88, #89, #95 and #96 on 2026-09-27 established, in the four repo skills it touches. Docs only, independent of the stack.
Why
The two-way audio campaign skill still said "still flaky sometimes" from July, and pointed at the iPhone → intercom direction. Today's per-hop measurement showed that on iOS 26 audio had been reliable apart from startup, and that the residue is the Pi → iPhone leg at session start (#102). It also cost most of an afternoon to discover that a whole class of "silent both ways" failures was the test rig, not the server. Both are worth having written down before the next person, or agent, reaches for the campaign.
Changes
intercom-two-way-audio-campaign: status narrowed to Caller audio drops out in the HomeKit live view (Pi → iPhone leg) #102; new Phase 0a to rule out the test rig (MacBook answering via Continuity through the Home-app iPhone); the per-hop audio probe as the Phase 0 instrument, with a warning never to leave it enabled; the ~3 s ffIn startup silence and burst as known Gate 2 behaviour; the controller's 16 kHz Opus RTP clock recorded as harmless on the return path.intercom-debugging-playbook: a triage row for "silent both ways from the moment the live view opens" and a failure-archaeology entry for the Continuity false alarm. Prettier re-padded the tables, which is most of the line count.intercom-testing-and-validation: the far end of a test call must not be the Home-app iPhone, and a single-phone Twilio self-test call recipe (Twilio calls the intercom number from itself with inline TwiML, recorded dual-channel).telephony-audio-reference: answer supervision (why ringing can outlast an answer on the PSTN) and a correction: the call is answered as soon as/twimlreturns<Connect><Stream>, so the Pi's ringback is a deliberate disguise rather than ringing on an unanswered call. Notes that the end of ringback is the visitor's cue to speak, which is why Caller audio drops out in the HomeKit live view (Pi → iPhone leg) #102's startup window loses their first words.Test Plan
prettier --check .claude/skillspasses.🤖 Generated with Claude Code