# Audit Brief

- Task ID: 20260831-105824-plan-code-ui-audit
- Orchestrator: build
- Repository: /Users/shane/dev/voice-ios
- Primary plan: /Users/shane/dev/voice-ios/PLAN.md
- Original contract: /Users/shane/dev/voice-ios/UPDATE_PATH.md
- Reference projects: /Users/shane/dev/hope-voice-api and /Users/shane/dev/hope_companion

## Objective

Determine whether the documented iOS implementation is actually complete, identify and fix confirmed defects, and create an evidence-based UI/UX redesign specification that incorporates the square Hope visual element.

## In Scope

- Swift and SwiftUI source, project configuration, resources, docs, and repository test coverage.
- PLAN.md claims versus UPDATE_PATH.md requirements and exit criteria.
- LiveKit connection lifecycle, stale callbacks, task/transcript/control protocols, media reconciliation, TLS behavior, persistence, error handling, accessibility, and user flow.
- Current simulator build/runtime behavior where available.
- Visual and interaction analysis of current UI and Hope reference assets/code.

## Out of Scope

- Unrequested server-side changes.
- Claiming real-device behavior without real-device evidence.
- Reverting unrelated user or agent changes.
- Committing .artifacts or product changes unless explicitly requested.

## Constraints

- Build is orchestration-only and must not implement product code.
- All product code/config/test changes must be made by the coder agent.
- Reviewer must not edit implementation files.
- Prefer minimal, evidence-backed fixes.
- Use XcodeBuildMCP for Apple build/run/test work after loading its skill and checking session defaults.
- Preserve existing design-system patterns unless the UI specification deliberately proposes a later redesign.

## Acceptance Criteria

1. Produce a requirements matrix for PLAN.md/UPDATE_PATH.md with evidence and unresolved qualification gaps.
2. Report review findings ordered by severity with file/line references and reproduction or reasoning.
3. Inspect current UI and locate/analyze the square Hope reference element.
4. Produce a detailed but implementable UI update specification covering hierarchy, navigation, states, components, visual language, accessibility, and rollout.
5. Route confirmed fixes to coder; coder verifies and writes implementation.md.
6. Independently review fixes and repeat until approved or concretely blocked.
7. Record exact build/test/simulator verification and avoid overstating device-only behavior.

## Required Deliverables

- review.md from reviewer.
- ui-ux-spec.md from the UI/UX review agent.
- implementation.md from coder if code changes are needed.
- Updated manifest.md with final evidence and risks.