Regenerate api.ts for the LocalDate+DatePrecision RelationshipDTO /
RelationshipUpsertRequest and the new PUT, then migrate every caller:
- RelationshipDateField (mirrors PersonLifeDateField: DAY/MONTH/YEAR, 44px
targets, labelled, semantic dark-mode tokens, relation_* i18n keys).
- AddRelationshipForm is now upsert-capable: an optional `relationship` prop
pre-fills type, person, both dates+precision and notes; posts to
?/updateRelationship (else ?/addRelationship); the submit control disables and
shows a progress spinner while a request is in flight (REQ-019); notes textarea
(<=2000).
- RelationshipChip gains an accessible Edit affordance (canWrite + onEdit);
StammbaumCard wires it, formats the date range via formatRelationshipDateRange,
and sorts by fromDate. PersonRelationshipsCard (read view) shows the date range
and notes; no dates -> no date line.
- persons/[id]/edit/+page.server.ts: updateRelationship action (PUT) + the
addRelationship action reshaped to date+precision+notes (empty date omits
precision for coherence).
- Genealogy callers fixed for the dropped year fields: familyForest spouse-order
and StammbaumConnectors ended-edge dashing now key off fromDate/toDate.
- i18n relation_* form keys in de/en/es.
REQ-004, REQ-014, REQ-015, REQ-016, REQ-019
Refs #837
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
PersonEditForm.svelte gains a G 0…G 6 select inside the {#if isPerson}
block. min-h-[44px] meets WCAG 2.5.8 / dual-audience touch target.
generationStr is initialised via $state(untrack(...)) so prop reruns
never reset an in-progress edit (same pattern as selectedType).
Both /persons/[id]/edit and /persons/new form actions read the field
without the conditional-spread idiom — generation always lands in the
PUT/POST body. G 0 is a valid family-tree-root value the spread would
silently drop, and an empty option sends null so a human can clear the
field back to "unset".
i18n adds person_label_generation / person_option_generation_unset /
person_hint_generation in de/en/es. Drops the dead stammbaum_generations
key (zero callsites after the filter-chip removal in the spec).
Tests: dropdown render + hydration in the component, generation=0/3/null
arriving in the API body in the server actions.
Refs #689
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
