Locality dating method

[zliobaite]

When the dating method in the locality tab is changed (e.g. from time unit to composite) the previous entries of age disappear.

[karilint]

[
{
"id": "T1",
"title": "Reproduce and map destructive age-field reset flow",
"summary": "Document the exact form state transitions when switching locality dating method and identify all fields currently reset.",
"app": "frontend",
"files_touched": [
"frontend/src/components/Locality/Tabs/AgeTab.tsx"
],
"migrations": false,
"permissions": [
"No permission model changes",
"Applies to users already allowed to edit localities"
],
"acceptance_criteria": [
"Confirmed reproduction path from time_unit to composite (and reverse) where entered age values are lost",
"Field inventory for min/max ages, bases, and fractions is documented for implementation"
],
"test_plan": [
"Manual reproduction in locality edit flow",
"Capture before/after state transitions in test notes"
],
"estimate_hours": 1.0,
"priority": "high"
},
{
"id": "T2",
"title": "Implement method-aware draft preservation in locality Age tab",
"summary": "Refactor date method change handling to preserve and restore per-method age inputs instead of clearing all fields.",
"app": "frontend",
"files_touched": [
"frontend/src/components/Locality/Tabs/AgeTab.tsx",
"frontend/src/components/DetailView/Context/DetailContext.tsx"
],
"migrations": false,
"permissions": [
"No new auth rules",
"Uses existing locality edit authorization"
],
"acceptance_criteria": [
"Switching dating method does not erase previously entered age values for that method",
"Returning to a previously selected method restores its prior values",
"Readonly/disabled state behavior remains consistent with current UX rules"
],
"test_plan": [
"React Testing Library test for method toggle value retention",
"Manual check of disabled fields across all method combinations"
],
"estimate_hours": 4.0,
"priority": "high"
},
{
"id": "T3",
"title": "Ensure validator compatibility with preserved hidden values",
"summary": "Confirm validation only enforces required fields relevant to active dating method while tolerating preserved non-active method values.",
"app": "frontend",
"files_touched": [
"frontend/src/shared/validators/locality.ts"
],
"migrations": false,
"permissions": [
"No permission changes"
],
"acceptance_criteria": [
"Active method required-field rules still trigger correctly",
"Preserved fields from non-active methods do not cause invalid save failures"
],
"test_plan": [
"Unit tests for validator scenarios: time_unit, absolute, composite",
"Negative test for invalid composite combinations"
],
"estimate_hours": 2.0,
"priority": "high"
},
{
"id": "T4",
"title": "Add regression tests for age persistence workflow",
"summary": "Add targeted tests that fail on current behavior and pass after fix for method switching and value restoration.",
"app": "frontend",
"files_touched": [
"frontend/src/components/Locality/Tabs/AgeTab.test.tsx",
"frontend/src/components/DetailView/common/editingComponents.test.tsx"
],
"migrations": false,
"permissions": [
"N/A (test-only)"
],
"acceptance_criteria": [
"Test demonstrates min/max age and basis values persist across method toggles",
"Test coverage includes at least one composite↔time_unit round-trip"
],
"test_plan": [
"Run frontend unit tests for new and existing age-related test suites",
"Verify no regressions in DetailView tests"
],
"estimate_hours": 2.5,
"priority": "high"
},
{
"id": "T5",
"title": "QA verification and release documentation",
"summary": "Execute lint/type/test checks and document behavior change for release notes.",
"app": "frontend",
"files_touched": [
"README.md",
"CHANGELOG.md"
],
"migrations": false,
"permissions": [
"No permission changes"
],
"acceptance_criteria": [
"Lint and type-check pass for frontend scope",
"Release note clearly describes preserved age-entry behavior on method change"
],
"test_plan": [
"Run npm run lint:frontend",
"Run npm run tsc:frontend",
"Run relevant Jest tests"
],
"estimate_hours": 1.0,
"priority": "medium"
}
]

[karilint]

Switching between dating methods (Time unit, Absolute, Composite) in the Locality Age tab was clearing previously entered age values, forcing users to re-enter data when exploring different dating approaches.

Changes
Age draft persistence: AgeTab now maintains method-specific state (ageDraftsByMethod) that preserves min_age, max_age, and basis field selections per dating method. Switching methods saves current values and restores previously entered values for the target method.

Scoped validation: Validation logic refactored to evaluate required basis fields only against the active dating method. For composite mode, validation enforces that one row uses time_unit basis while the other uses absolute basis, determined by which fields are populated.

Test coverage: Added regression tests for method round-trip scenarios and fraction-based age recalculation.