P2 human release gate — prove Zara Android on a real device with embedded Prolog, live voice and typed actions #179

New issue

Open

opened 2026-08-22 21:56:36 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-22 21:56:36 +00:00

(Migrated from github.com)

Parent epic: #152
Depends on: #178, #169; respect #134 daemon canonicality decision.

Goal

Run the final explicitly human-operated real-Android acceptance gate. Emulator/CI results cannot satisfy this issue by themselves.

Required real-device sequence

install exact candidate APK and report version/head;
generate/enroll device identity, pin server, connect to real zara-server;
typed text conversation and durable reconnect;
run local embedded-Prolog semantic self-test/corpus sample on device;
real mic voice turn -> server STT -> semantic/agent -> server TTS -> Android playback;
barge in while Zara speaks and prove immediate local stop + stale server cancellation;
set a timer -> How long? -> spoken duration multi-turn dialogue;
execute a safe Android local typed capability such as open URI/app or notification;
execute a server-side search/tool/service and prove it did not run as local device action;
create and invoke a programmable command by voice; parameterized command if practical;
background/foreground and network disconnect/reconnect;
client/server restart and conversation/command continuity;
revoke Android key and prove subsequent connection is denied;
second principal/client isolation check;
inspect diagnostics/logs for secrets/private audio leakage.

Guide/evidence

Use a generated checklist with exact phrases and expected visible/spoken/runtime outcomes. Record pass/fail, device/Android/app/server versions and safe latency summaries. Do not mark PASS automatically; human confirmation is authority.

Acceptance

All mandatory real-device scenarios are actually performed against the exact candidate and pass. Any failure becomes a focused blocker issue rather than being waived into the epic.

Parent epic: #152 Depends on: #178, #169; respect #134 daemon canonicality decision. ## Goal Run the final explicitly human-operated real-Android acceptance gate. Emulator/CI results cannot satisfy this issue by themselves. ## Required real-device sequence - install exact candidate APK and report version/head; - generate/enroll device identity, pin server, connect to real `zara-server`; - typed text conversation and durable reconnect; - run local embedded-Prolog semantic self-test/corpus sample on device; - real mic voice turn -> server STT -> semantic/agent -> server TTS -> Android playback; - barge in while Zara speaks and prove immediate local stop + stale server cancellation; - `set a timer` -> `How long?` -> spoken duration multi-turn dialogue; - execute a safe Android local typed capability such as open URI/app or notification; - execute a server-side search/tool/service and prove it did not run as local device action; - create and invoke a programmable command by voice; parameterized command if practical; - background/foreground and network disconnect/reconnect; - client/server restart and conversation/command continuity; - revoke Android key and prove subsequent connection is denied; - second principal/client isolation check; - inspect diagnostics/logs for secrets/private audio leakage. ## Guide/evidence Use a generated checklist with exact phrases and expected visible/spoken/runtime outcomes. Record pass/fail, device/Android/app/server versions and safe latency summaries. Do not mark PASS automatically; human confirmation is authority. ## Acceptance All mandatory real-device scenarios are actually performed against the exact candidate and pass. Any failure becomes a focused blocker issue rather than being waived into the epic.