Logging redesign Phase 5: unified LogScreen(date), period as a state of the day

[mapgie]

Phase 5: unified LogScreen(date)

One screen logs a day; a running period is a state of that day, not a separate destination. Fully additive: the LogPeriod and LogCategory routes stay registered, every existing entry point still uses them, and the only way into the new screen is an opt-in "Try the new day log (preview)" row in the calendar day sheet. Removal is Phase 8.

What's here

• ui/screens/log/LogScreen.kt + LogViewModel.kt (new): the unified day surface behind route log_day?date={date} (Screen.LogDay), composed from the Phase 3/4 primitives (SectionHeader, ListCard/ListRow, ToneHero, ChipRow, MetricInput, Timeline via TimedIncrementTimeline, PrimarySaveBar).
• ui/screens/log/PeriodDaySync.kt (new): the flow slider mapping, flow/symptom fan-out, pinned-value rules, and day-number helper extracted from LogPeriodViewModel's private members. LogPeriodViewModel now delegates to it (behaviour unchanged), and LogViewModel calls the same code, so the two surfaces cannot drift.
• Two states, one layout: off-period the first tracked category leads as a ToneHero (its own role colour; the DB default role is secondary) and the footer is a quiet "Period started today" hairline row; on-period the Flow group and period-dates card slot in at the top, pinned categories render in the flow context, and the footer becomes a filled primaryContainer status row ("Period ongoing", "Since <date>", End/Undo). Everything between is the same components in the same order.
• Grouped tracked-metric cards (Phase 2 data model, via TrackingRepository group methods): a group of 2+ categories renders as one ListCard of rows, tapping a row opens its input below the card; a group of one (and lone ungrouped categories) renders as its own open section; 2+ ungrouped categories share one "Tracking" card.
• Switch sheet, organised by group and tinted by role: opened from the screen title it switches day or jumps to a category; opened from a metric's header (the category name is a button) it re-files the entered value under the picked category, preserving the value (serialised through the same label rules a save would use, then hydrated into the target's input shape).
• Routing: Screen.LogDay + MainActivity registration; DayLogSheet gains an optional onOpenDayLog param (default null; existing callers unaffected) wired only from HomeScreen.

§3 Logging preservation checklist (each item: works on the old screens AND on the new one)

• Chip multi-select (default) — old untouched; new via MetricInput/ChipRow per category
• Stepped slider (numeric_slider) — old untouched; new via MetricInput (StepScale for whole ratings up to 10 steps, parity slider otherwise, per Phase 4)
• Free numeric with unit (numeric_free) — old untouched; new via MetricInput, empty input skips that category (the single-entry screen's "empty blocks save" translated per entry)
• Count stepper (increment) — old untouched; new via MetricInput, count of 0 skips (pinned-on-period keeps the period screen's save-including-0 rule)
• Timed increment, per-tap timestamp + timeline — old untouched; new renders the same internal TimedIncrementTimeline with per-tap saves and per-entry delete
• Yes/No and Time (Phase 4 types) — old untouched; new via MetricInput, stored as the same value-label strings
• "Previously recorded (removed from options)" chips — both
• Notes per log, 500-char cap — old untouched; new has per-entry notes ("Add note") saved with each log, plus the episode Notes field on-period
• Edit an existing log — both (new loads the day's entry per category and updates in place)
• Delete a log — both (per-entry "Delete entry" with confirmation; timed entries per row)
• Date selection — both (day switch from the Date row or the title sheet, reloading the selected day's stored values; guarded when unsaved changes exist)
• Period day: start/end dates, ongoing (null end) — both ("Started/Ended" rows, clear-end, open-ended explainer with the tolerance count)
• Flow slider or chips with the 1 Spotting / 2 Light / 4 Heavy / else Medium mapping — both (shared PeriodDaySync.flowLabelForSliderValue)
• Symptoms chips + inline Add via AddSymptomDialog writing to the value catalog — both (same dialog, same addValueToCategory path)
• Pinned showInLogPeriod categories in the flow context — both (new: rendered after Flow while on-period, in their normal group otherwise; saves keep computePinnedValues semantics incl. slider-min fallback and count 0)
• Episode/continuation: gap tolerance from prefs, episode day number, range vs open-ended — both (PeriodRepository.periodForDate, logPeriodDay/logPeriodRange/updateEpisode, day-past-stored-end extension rule preserved)
• "Remove this day" — both (confirmation copy preserved; tracking logs for the day kept)
• "Delete Entire Period" — both (episode + per-day tracking logs)
• "Disable period logging" — both (overflow menu)
• Unsaved-changes discard/save guard — both (same dialog; new also guards day switching)
• Save fan-out to the tracking system (syncFlowToTrackingLog, syncSymptomsToTrackingLog, pinned logs) — both, through the shared PeriodDaySync
• Widget refresh (GoFloWidget.updateAllWidgets) + reminder refresh (ReminderScheduler.refreshPredictionReminders) on period-affecting saves — both

Phase guide acceptance criteria

• Off-period day: hero + symptoms + tracked metrics + notes log and persist; "Period started today" starts one — needs device pass
• On-period day: flow leads, lead compresses, footer shows status + End; rest identical — needs device pass
• Period data appears in Stats / Flow / Symptoms / widget exactly as the old screen produced — same repository calls by inspection; needs device pass
• Header switcher re-files without losing the entered value (LogViewModel.refileEntry)
• Grouped multi-metric card: 2+ categories one card of rows; 1 renders the single-metric section
• TalkBack traversal top to bottom; StepScale reads as one control — layout order and StepScale's single-control semantics are as specified; needs device pass
• a11y_check.py green (run locally)
• wcag_check.py green (run locally; no colour values changed)
• Old LogPeriod / LogCategory routes still registered and reachable; nothing deleted
• CI build/tests — CI is the build check for this environment

Deviations (also recorded in PLAN.md §7)

1. Re-file trigger: the guide's "title-as-button" sheet exists, but on a whole-day surface the title sheet is day-switch + jump; the re-file action lives on each metric's own header (its name is the button), where "file THIS entry elsewhere" is unambiguous. Both open the same sheet, organised by group and tinted by role.
2. Day-level Notes bind to episode notes, so they render only while the day is on-period (there is no day-notes store off-period); per-log notes are editable per metric instead.
3. Untouched entries are skipped on off-period saves: no fabricated logs for ignored categories, and no rewriting of stored entries (which would re-stamp or clear loggedAt). Pinned categories keep the period screen's always-save fan-out while on-period.
4. allowMultiple (non-timed) categories always start a fresh entry on the day screen (matching LogCategoryViewModel's new-entry rule); editing one specific log among several same-day logs remains a LogCategory flow via the day sheet.
5. Entry-point flip (guide sub-PR 5d) deferred: calendar tap, FAB, and quick log keep opening the old screens; the preview row in DayLogSheet is the only new entry, so a broken new screen can never block logging.

Notes for Phase 6

• The switch sheet consumes groups via LogUiState.groups (TrackingRepository.getAllGroupsOnce) and renders group labels with Group.colorRole; category tints resolve through effectiveColorToken(groups), so "inherit" categories will follow group recolouring with no screen changes.
• TrackingSections already implements the "group of 2+ = one card, group of 1 = own section" rule the What You Track home will mirror.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg

---

Generated by Claude Code