Caregiver/Emergency Contacts — add/edit/delete list

Description

The first Phase 1 vertical slice, chosen in
0008 because it is the simplest
true instance of the repeatable-entry pattern: four plain text fields, no
excluded-field reasoning, no derived values, no conditional logic.

This ticket and #49 are the same piece of work and are tracked together as
#118, which has the fuller specification. Work #118. This one exists as the
Phase 1 backlog entry and should be closed with it.

Fields

Name, relationship, phone, email. (From 0008 directly.)

Acceptance Criteria

• Add, edit and delete work end to end against the encrypted local database
• Built on the generic component from #49, not hardcoded to these four fields
• Ships migration 1 — MIGRATIONS is currently empty, so this is the first table in the app
• Sits behind the biometric unlock shell
• WCAG-aligned; one task per screen, next step obvious
• Covered by unit tests

Additional Info and Resources

• Duplicate of / superseded by #118 — see there for full criteria and QA
• Output feeds the "Keep with me" screen (#48) later; keep that in mind for the data shape, but do not build it here

QA

• See #118.

Start with superseding issue #118, which contains the fuller specification and QA guidance; use docs/decisions/0008-first-vertical-slice.md and issue #49 for the original context. Confirm the migration, encrypted local database, biometric shell, accessibility, and unit-test requirements there; this issue should be closed in favor of #118 rather than implemented independently.