Emergency Instructions screen (reduced scope)

Description

What someone needs to know if the patient is suddenly not there — with a scope
that is deliberately narrower than the paper journal's. Static profile.

The reduced scope is the point of the ticket, so read
0006 first.

Fields

• Pets — who they are and what they need
• First contact — name, relationship, phone
• Second contact — name, relationship, phone
• Notes

Excluded, per 0006: the security alarm code, and exact key / wallet / purse
locations. 0006's reasoning is that these are home-security data travelling in
a medical journal — the same device-compromise exposure as everything else, for
a benefit the app does not need to provide. A "where to find my things" free-text
box that invites the same content is the same problem wearing a different label.

Acceptance Criteria

• Single-record profile, edited in place
• Persists to the encrypted local database and survives a relaunch
• No alarm code field, no key/wallet/purse location field, and no free-text prompt that solicits them
• Relationship to #35's emergency contacts settled — reuse or separate, recorded in the PR
• WCAG-aligned; copy neutral per 0004
• Covered by unit tests

Additional Info and Resources

• 0006, including Paul's note that these two categories are the ones he would genuinely leave open for later — so exclude them now, but do not build a schema that makes adding them expensive
• The first/second contacts here overlap #35. Duplicating them is a data-entry burden; linking them is a relational feature the storage layer does not have. Worth raising

QA

• Fill in, relaunch, confirm persistence
• Read every prompt and confirm none of them invites an alarm code or a key location
• VoiceOver/TalkBack through the screen

Read docs/decisions/0006-excluded-field-safety-boundary.md first, then review issue #35 and the existing profile and encrypted-database entry points. Confirm how the contact relationship will be handled before implementing the single-record screen. Done means relaunch persistence, unit coverage, excluded prompts, and a VoiceOver/TalkBack pass.