P2 release gate — adversarial Android lifecycle, security, resource and cross-platform parity matrix #178

Open
opened 2026-08-22 21:56:23 +00:00 by lost-rob0t · 0 comments
lost-rob0t commented 2026-08-22 21:56:23 +00:00 (Migrated from github.com)

Parent epic: #152
Depends on: #177, #175

Goal

Automate the Android-specific proof gate before real-device acceptance.

Matrix

  • app/activity/process recreation in important states;
  • background/foreground transitions;
  • network loss/switch/reconnect storms;
  • daemon restart mid-turn/mid-action;
  • wrong/unknown/revoked keys and server pin;
  • malformed/oversized ZARA/1 messages;
  • stale/duplicate events/actions after reconnect;
  • capability permission revoked after advertisement;
  • wrong target principal/device/session;
  • URI/intent argument abuse;
  • clipboard/audio/private data absent from logs;
  • mic permission/audio focus/route failure;
  • voice input/output backpressure and cancellation;
  • embedded Prolog repeated init/query/teardown and resource bounds;
  • Linux vs Android shared semantic corpus parity;
  • programmable-command parity and deletion/revocation;
  • APK scan for private keys/provider secrets/test credentials;
  • bounded memory/thread/native-resource growth in repeated profile.

Automation

Use JVM/native/emulator/local-daemon fixtures as appropriate and one non-interactive Android release script/task integrated with CI. Do not require a real microphone/device for this issue; that is #179.

Acceptance

Automated Android build/protocol/Prolog/semantic/device/voice matrices are green with bounded resources and no cross-principal/action leakage at exact head.

Parent epic: #152 Depends on: #177, #175 ## Goal Automate the Android-specific proof gate before real-device acceptance. ## Matrix - app/activity/process recreation in important states; - background/foreground transitions; - network loss/switch/reconnect storms; - daemon restart mid-turn/mid-action; - wrong/unknown/revoked keys and server pin; - malformed/oversized ZARA/1 messages; - stale/duplicate events/actions after reconnect; - capability permission revoked after advertisement; - wrong target principal/device/session; - URI/intent argument abuse; - clipboard/audio/private data absent from logs; - mic permission/audio focus/route failure; - voice input/output backpressure and cancellation; - embedded Prolog repeated init/query/teardown and resource bounds; - Linux vs Android shared semantic corpus parity; - programmable-command parity and deletion/revocation; - APK scan for private keys/provider secrets/test credentials; - bounded memory/thread/native-resource growth in repeated profile. ## Automation Use JVM/native/emulator/local-daemon fixtures as appropriate and one non-interactive Android release script/task integrated with CI. Do not require a real microphone/device for this issue; that is #179. ## Acceptance Automated Android build/protocol/Prolog/semantic/device/voice matrices are green with bounded resources and no cross-principal/action leakage at exact head.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/zara#178
No description provided.