Test Agent Assist internally on Attik side

Objective

• Run structured internal testing of Agent Assist once the app is Attik-built and installable via TestFlight (ATT-1681), so defects and UX gaps are found before broader rollout or customer-facing promises.
• Produce enough confidence for leadership to green-light follow-on roadmap work.

Background

• May 15 feature sync (Chris): Near-term goal for the week was repos + Attik accounts + TestFlight + testing on Attik’s side—described as basically all the team needed for that handoff slice.
• This ticket is the validation step after code and accounts are under Attik control and a TestFlight build exists.
• Related ATT-1679, ATT-1680, ATT-1681.

Scope

QA execution

• Decision needed: target devices / OS versions, tester roster, and smoke vs regression depth; capture results in the tool the team already uses for release QA (Linear sub-tasks, TestFlight feedback, spreadsheet—Decision needed).

Product & support surfaces

• Decision needed: whether testing includes end-to-end flows against production Attik APIs vs staging, and how support will triage issues found (severity rubric, who owns mobile vs API).

Naming clarity (engineering)

• Agent Assist app (this epic) is separate from the agent-assist permission and report chat integration in attik-frontend / attik-backend (ReportAIAssistModal, reportChunk chat, AIChunk dataType: 'agent-assist'). Test plans should name which product is under test to avoid false bugs filed against the wrong codebase.

References

• Related: ATT-1679, ATT-1680, ATT-1681.
• Report agent-assist context (naming only): attik-frontend/src/app/client/reports/components/ReportAIAssistModal.tsx, attik-backend/src/routes/reportChunk.ts.