Mobile/PWA intent capture pass

[jjalangtry]

Parent epic: #69

Dependencies:

• Implement New Intent floating capture button #76 Implement New Intent floating capture button
• Build Intent Pane #79 Build Intent Pane
• Build universal human approval queue #82 Build universal human approval queue

Plan order:

• Issue 19 of 20

---

Goal:

Make the 0.9.0 loop usable from phone without native app work.

Scope:

• Responsive New Intent capture.
• Mobile voice capture/transcription.
• Use Lab86 Voice as inspiration for mobile voice-agent rendering,
  picture-in-picture, transcript display, and capture ergonomics.
• Mobile intent pane.
• Mobile approval cards.
• Add-to-home-screen/PWA checks if applicable.

Acceptance criteria:

• User can capture a voice intent from phone.
• User can answer questions and approve/reject actions on phone.
• UI does not require desktop task-board interactions.
• Native app is not required for 0.9.0.

---

Source plan: docs/albatross-0.9-epic.md.

---

---

Albatross development contract

UI work for this issue must follow docs/albatross-development-contract.md.

If this issue designs or materially changes UI, all of these must be true before implementation:

1. The UI component is not generated directly by ChatGPT/Codex.
2. A Claude Code sub-agent is spawned with a full-context Opus prompt, e.g. claude -p "{prompt}" --model opus.
3. The Claude prompt names the UI, where to design it, acceptance criteria, allowed files, and requires Mobbin plus browser-based research for comparable UIs, UX flows, and animations before building.
4. Do not use tiny prompts, no-tool prompts, or lightweight model fallbacks for Albatross UI implementation. Let the full Opus/tool-enabled run complete unless it clearly errors.

Every issue increment must:

• Push the increment to a PR from the Albatross branch/worktree to staging.
• Add this issue to the PR summary.
• Include Resolves Mobile/PWA intent capture pass #88 or Closes Mobile/PWA intent capture pass #88 in the PR references.
• Move the project item to In review.
• Request a CodeRabbit review on the increment.
• Loop on review comments until resolved, marking PR comments as resolved as they are addressed.
• Keep tests green; tests cannot regress.
• Add or update focused tests for every behavior, state, data, routing, UI contract, or regression risk touched.
• Move the project item to Done only after the accepted/merged increment.

[jjalangtry]

Deferring to a later epic per Jakob (2026-07-03): desktop capture, PiP, areas, and projects took this round. Mobile/PWA intent capture gets its own pass.