Power of Health Care screen

Description

Who is legally empowered to make health care decisions for the patient if they
cannot. Static profile — there is normally one, occasionally a named alternate.

This ticket needs scoping before it needs a developer. Nothing in the ADRs
defines it, and it sits close enough to #45 (Advanced Directives) that the split
between them is unclear: both are about legal documents and who holds them.
Settle that first.

Fields — need confirming, nothing in the repo specifies this screen

• Agent name
• Relationship
• Phone
• Alternate agent name, relationship, phone
• Where the document is kept
• Notes

Acceptance Criteria

• Scope agreed with the product owner, including the boundary against #45, before any code
• Single-record profile, edited in place
• Persists to the encrypted local database and survives a relaunch
• Holds who and where, not the document contents
• WCAG-aligned; copy neutral per 0004
• Covered by unit tests

Additional Info and Resources

• Follows the same "who has access and where located, not the contents" principle #45 states explicitly — that principle should probably cover both, which is part of what needs settling
• Same open question as #34: the repository layer does not cover single-record profiles

QA

• Fill in, relaunch, confirm persistence
• Confirm no field invites pasting the document itself
• VoiceOver/TalkBack through the screen

Start by reading the ADRs and comparing this issue with #45 and #34; the repository does not define the single-record profile boundary. Confirm the product-owner scope, including the fields and distinction from Advanced Directives, before identifying implementation work. Done means the scope and acceptance criteria are agreed and recorded; no code should begin until then.