dev
1
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 Bailey DixonandClaude Opus 4.6
|
12204fddc0 |
fix(v0.4): close C4 + H5 voice intent TODOs, add install.sh --branch, test_android_read_screen
Three open TODOs from the v0.4 hand-off, plus an install.sh ergonomic
improvement that came up while planning on-device verification.
C4 — voice contact-name → phone resolution
- RealVoiceBridgeIntentHandler now resolves the spoken contact name to
a real phone number BEFORE dispatching /send_sms, instead of passing
the raw name (which the phone-side regex check rejected, surfacing
as a user-visible error every time).
- New private helper resolveContactPhone() calls
HermesAccessibilityService.instance.actionExecutor.searchContacts(
contactName, limit=5) directly. Same code path as the /search_contacts
bridge route but invoked locally — no response-correlation plumbing
needed because both the voice handler and the accessibility service
are in the same process.
- searchContacts returns phones as a comma-joined string ("+1555..., +1555...")
per the C2 wire shape; the resolver splits on `,`, trims whitespace,
and takes the first non-blank entry.
- Wrapped in withContext(Dispatchers.IO) — ContactsContract queries
hit the on-device content provider and can block.
- If the resolver returns null (service unbound, contacts permission
missing, no matching contact, or matched contact has no phone), the
intent surfaces as a friendly spoken response ("I couldn't find a
contact called Sam.") instead of dispatching a broken envelope.
- The destructive-verb confirmation modal still fires on the
BridgeCommandHandler side, so the resolver is purely additive — it
doesn't bypass any safety gate.
H5 — voice app-name → package resolution
- Same shape as C4 but for /open_app. New resolveAppPackage() helper
calls service.packageManager.queryIntentActivities(ACTION_MAIN +
CATEGORY_LAUNCHER) and fuzzy-matches the spoken app name against
the launchable-app inventory.
- Three-tier match (case-insensitive, first hit wins):
1. Exact label match — "spotify" → "Spotify"
2. Prefix match — "chro" → "Chrome Beta"
3. Substring match — "google" → "Google Maps"
Order matters: tier 1 + 2 prevent accidental substring hits like
"messages" matching "Google Messages" instead of the literal
Messages app.
- Requires the <queries><intent action=MAIN category=LAUNCHER/></queries>
manifest declaration that landed in the previous commit (
|