Skip to content

Phase 6: "What You Track" management home with first-class groups - #183

Merged
mapgie merged 18 commits into
mainfrom
claude/logging-redesign-phase-6
Aug 26, 2026
Merged

Phase 6: "What You Track" management home with first-class groups#183
mapgie merged 18 commits into
mainfrom
claude/logging-redesign-phase-6

Conversation

@mapgie

@mapgie mapgie commented Aug 25, 2026

Copy link
Copy Markdown
Owner

Summary

Phase 6 of the logging & category-system redesign: ManageCategoriesScreen is rebuilt to the row-4 mock as the "What You Track" home. A SegmentedToggle swaps in place between:

  • Grouped: one role-tinted card per group (roleContainerTint), header with colour dot + name + Edit, member categories as the familiar swipeable rows (colours resolved via effectiveColorToken, so inherit-categories adopt the group role live), an inline "Add category to this group" affordance, and a "New group" pill.
  • Ungrouped: loose categories on neutral surfaceVariant rows, each with an "Add to group" affordance, explainer copy, and a "New category" CTA. Category bubbles keep their own colour tokens (PLAN §8 decision 1: no grey wipe).

New flows, all on the Phase 2 repository API (no DB changes, schema stays v24):

  • Add-to-group sheet (category-centric): pick an existing group (with member counts), "New group…" jumps to group creation pre-filled with this category, and "Remove from group" unfiles. A "Use the group's colour" switch (default on, per the handover) sets colorToken = "inherit"; turning it off keeps the category's own colour. Footer copy states that past entries are kept.
  • Add-member sheet (group-centric, from the inline card affordance): ungrouped categories first, then members of other groups labelled with where they live; "New category…" opens the existing creation dialog pre-set to the group's default input type and files the category on creation.
  • Group editor dialog: name, in-theme colour role via RolePicker (new additive showFixedSection = false flag hides the hex track — a group's colorRole is never a hex), default input type chips, member list with per-row Remove (unfile), Move up/Move down (group reorder), and Delete with a confirmation explaining members are kept and unfiled, never deleted.

ManageCategoriesViewModel gains the groups Flow plus addGroup/updateGroup/moveGroup/deleteGroup/assignCategoryToGroup(category, groupId, adoptGroupColor)/unassignCategory, and addCategory gained an optional groupId.

Acceptance criteria (phase guide)

  • Create, rename, recolour (role), reorder, and delete groups; deleting a group unfiles its categories (never deletes them — repository-enforced, surfaced in the confirmation dialog)
  • File / unfile a category via the add-to-group sheet; an inherit-category adopts the group role live (effectiveColorToken on member rows)
  • Grouped and Ungrouped tabs both render correctly and swap in place
  • Every pre-existing management action is still reachable and works (see walk below)
  • a11y_check.py green (segmented = built-in radio semantics; rows/sheet actions = Role.Button; pickers = Role.RadioButton; adopt-colour switch = Role.Switch via SwitchRow)

Feature-preservation checklist

  • Archive/unarchive (swipe right, confirmations incl. "don't show again"), reorder (toolbar reorder mode keeps the flat drag list over global displayOrder), delete-with-history (swipe left + confirmation), system-category protection (swipe delete disabled, ViewModel guard)
  • Tracking modes still present and functional (separate tracking_modes screen via the Manage hub; untouched)
  • Quick-log config + Quick Log widget unaffected (separate manage_quick_log screen; untouched)
  • ManageCategoryValues still reachable (tap any category row in either tab, group cards, and the archived section); value CRUD + rename-with-history + seeded-value protection intact (screen untouched)
  • Category counts in the header ("N categories · M groups") reflect reality (active categories + groups, liveRegion = Polite)
  • Creation dialog unchanged in behaviour (icon grid, colour picker incl. custom hex, type chips, numeric range, toggles); Phase 7 rebuilds it
  • CI build green (this environment cannot build; a11y_check.py, wcag_check.py, and the semantics-import sweep all pass locally)
  • On-device walkthrough of the new flows

Deviations

  1. Reorder mode stays global: the toolbar reorder toggle shows the pre-redesign flat drag list over all active categories (global displayOrder preserved, per the guide's "simplest" recommendation). Groups reorder separately via Move up/down in the edit dialog.
  2. Unfile entry points: via the edit-group member list and the "Remove from group" row of the add-to-group sheet (the mock only shows filing).
  3. A category created from inside a group keeps the colour picked in the creation dialog rather than auto-inheriting; it is filed and type-preset. The adopt-colour switch is the explicit opt-in surface for "inherit".

Docs

PLAN.md §7 Phase 6 row marked Done with deviations; subsystem map 02 updated (management UI now exists); help dialog documents groups and the two views; changelog fragment what-you-track-groups.json (minor); LESSONS.md entry on snapshotting Compose state into locals before async completion callbacks.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg


Generated by Claude Code

claude added 17 commits August 25, 2026 00:50
Adds the redesign's only genuinely new table: a category group that owns
a colour role and a default input type. Fully additive; no UI changes.

- Group entity (table `groups`) + GroupDao; TrackingCategory gains a
  nullable groupId (no FK: deleting a group unfiles members instead of
  cascading). MIGRATION_23_24 creates the table and adds the column;
  existing rows keep groupId NULL and their colorToken, so nothing
  changes visually after migrating.
- Group CRUD, reorder, delete-with-unfile, and assign/unassign methods
  on TrackingRepository (new nullable groupDao constructor param, wired
  in GoFloApplication).
- Colour inheritance per PLAN.md section 5: new "inherit" colorToken
  sentinel resolved by TrackingCategory.effectiveColorToken(groups) to
  the group's colorRole, or neutral surfaceVariant when groupless.
  Deliberately not a CategoryColor entry so the Phase 1 role picker
  does not offer it. Existing tokens are untouched (no grey wipe;
  confirmed with owner against the handover's neutral-by-default).
- Migration test (Migration23To24Test): runs the real MIGRATION_23_24
  against a real SQLite v23 schema via sqlite-jdbc (test-only dep),
  routing execSQL through a reflection proxy, and asserts the exact
  schema Room expects plus data preservation. MigrationTestHelper is
  unusable here (no instrumented tests, exportSchema = false).
- PLAN.md section 7 progress log updated; subsystem map 02 updated for
  v24; changelog fragment (minor); LESSONS.md entry on JVM-side Room
  migration testing.

Verified: migration SQL executed against a seeded v23 schema in SQLite
(PRAGMA output matches the test's expected schema exactly);
a11y_check.py and wcag_check.py both clean.

Claude-Session: https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg

Co-authored-by: Claude <noreply@anthropic.com>
Adds the ~12 stateless, parameterised Compose primitives every later
redesign screen is assembled from, in ui/components/, previews only.
No existing screen is rewired; nothing is removed.

- SectionHeader: uppercase 11sp section label with right-aligned value
- ListCard / ListRow / HairlineDivider: hairline-outlined card of rows
- StepScale: discrete rising tap-steps; exposes to TalkBack as a single
  control ("Flow, Medium, 3 of 4") with per-step custom actions
- ChipToggle / ChipRow: tonal-fill + check selection chips (FilterChip)
- ToneHero: tonal hero container, Comfortaa word applied explicitly
- SegmentedToggle: single-choice segmented buttons, optional role tint
- RolePicker: 6 in-theme role pills + fixed-colour track, standalone
  (visuals mirrored from the Phase 1 inline picker; ManageCategories
  keeps its copy until a later phase rewires it)
- IconPicker: 48dp icon tile grid with radio semantics + display names
- SwitchRow: full-row toggle, Role.Switch + stateDescription, inner
  Switch has no click handler
- Timeline / TimelineEntry: timestamped multiple-per-day list with
  per-row overflow and an append row
- PrimarySaveBar: sticky 52dp pill with gradient fade
- MetricInput facade stub + MetricConfig/MetricValue value types
  (incl. YesNo/TimeOfDay variants ready for Phase 4)

Every primitive accents from a passed-in role Color (tonal container
fills derived via roleContainerTint, lerp toward surface); each carries
light, dark, and 200% font-scale previews through GoFloTheme so the
extended-roles CompositionLocal path is exercised. a11y_check.py and
wcag_check.py both clean. PLAN.md progress log updated; DB stays at 24.

Claude-Session: https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg
Co-authored-by: Claude <noreply@anthropic.com>
Completes the MetricInput facade so it renders every category input type,
and refactors LogCategoryScreen to render through it with behaviour parity:

- CategoryType gains YES_NO ("yes_no") and TIME ("time"). Both store their
  readings as plain value-label strings ("Yes"/"No"; 24-hour "HH:mm") in
  tracking_log_values per the owner's resolution of PLAN.md §8 decision #3:
  no new columns, no migration (DB stays at v24).
- MetricInput: whole-step rating scales (up to 10 steps) render as StepScale;
  decimal or wider ranges keep the parity slider including whole-number
  stepped behaviour, large readout, scale labels, min/max labels, and the
  unset-value hint. numeric_free keeps unit label + placeholder; increment
  keeps the never-below-zero counter (decrement disabled at 0); yes_no
  renders a role-tinted SegmentedToggle; time renders the new TimeField
  primitive (Material time picker, 24h).
- LogCategoryScreen: the inline per-type when is gone; every non-timed input
  renders via MetricInput. Timed increment stays screen-driven (per-tap
  immediate saves, no Save button) and now renders the Timeline primitive.
  Notes 500-char cap, save/update, delete, date selection, edit-existing,
  empty-catalog text, and "previously recorded (removed)" chips unchanged.
- LogCategoryViewModel: additive setSelectedValues; yes_no/time flow through
  selectedValues, so the existing else-branch save path persists them and
  the numeric_free empty-blocks-save / increment <=0-blocks-save rules are
  untouched.
- LogPeriodScreen: PinnedCategoryInput gains additive yes_no/time branches
  delegating to MetricInput (pre-existing branches untouched); additive
  LogPeriodViewModel.setPinnedSingleValue feeds the existing selection-set
  save path.
- TrackingCategory.isNumeric now enumerates the numeric types explicitly so
  yes_no/time chart as label categories in Stats instead of being fed into
  numeric chart math.
- Create flow: the two new types appear automatically in the New Category
  type chips; the unit field is now limited to the genuinely numeric types.
- Docs: PLAN.md §7 row + §8 #3 resolution, subsystem map 01 drift note,
  LESSONS.md entry on negation-defined classifications, changelog fragment
  (minor).

Claude-Session: https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg
Co-authored-by: Claude <noreply@anthropic.com>
The flow slider mapping (1 Spotting / 2 Light / 4 Heavy / else Medium),
the flow and symptom fan-out into the tracking system, the pinned-category
value rules, and the episode day-number helper move from private members of
LogPeriodViewModel into an internal PeriodDaySync object, so the unified day
screen (next commit) shares the exact same code instead of a copy that could
drift. LogPeriodViewModel delegates to it; behaviour is unchanged.

Also widens LogCategoryScreen's metricConfigFor and TimedIncrementTimeline
from private to internal for the same reuse.

Claude-Session: https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg
Co-authored-by: Claude <noreply@anthropic.com>
New LogScreen + LogViewModel compose the Phase 3/4 primitives into one
per-day surface behind the additive route log_day?date={date}:

- Off-period: the first tracked category leads as a ToneHero, flow is not
  rendered, and the footer is a quiet Period-started-today row (which flips
  the screen into its on-period arrangement before saving).
- On-period: the Flow group (StepScale, stepped slider, or chips per the
  category's mode, with the 1 Spotting / 2 Light / 4 Heavy / else Medium
  mapping) slots in at the top with the period dates card, pinned
  showInLogPeriod categories render in the flow context, and the footer is a
  filled status row with End/Undo.
- Between the two states everything is identical: symptoms chips with the
  inline Add dialog, tracked metrics organised by group (two or more members
  render as one ListCard of rows with the active row's input beneath; a group
  of one renders as its own open section), per-entry notes with the 500-char
  cap, previously-recorded chips, track-against-time, per-entry delete, and
  timed-increment timelines with per-tap saves.
- The title and every metric header open a switch sheet organised by group
  and tinted by role: from the title it switches day or jumps to a category;
  from a metric header it re-files the entered value under another category
  without losing it.
- Saving reuses the period screen's exact sequence via PeriodDaySync
  (episode continuation and boundary edits, episode meta, flow/symptom/pinned
  fan-out, widget and prediction-reminder refresh); off-period saves write
  only categories the user touched, using the category screen's per-type
  rules. Remove-day, delete-entire-period, disable-period-logging, and the
  unsaved-changes guard are all ported.

The LogPeriod and LogCategory routes stay registered and every existing
entry point still uses them; the only new entry is an opt-in preview row in
the calendar day sheet. Removal is Phase 8.

Claude-Session: https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg
Co-authored-by: Claude <noreply@anthropic.com>
Marks Phase 5 done in PLAN.md with its deviations, records the new screen
and the PeriodDaySync extraction in subsystem map 01, adds the minor-bump
changelog fragment, and adds a lesson on translating single-entry save
blocking into per-entry skip rules on a batch save surface.

Claude-Session: https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg
Co-authored-by: Claude <noreply@anthropic.com>
CI failed compileDebugKotlin on PR #180: role/selected/contentDescription/
customActions were assigned inside semantics{} blocks as this.role etc.
without importing the corresponding androidx.compose.ui.semantics extension
properties (importing the Role class does not cover the lowercase role
property). Adds the missing imports to IconPicker, ListCard, RolePicker,
StepScale, and Timeline, and extends the LESSONS.md shadowing entry with
the import requirement. Verified with a semantics-vs-imports sweep over
every main-source Kotlin file plus a11y_check.py.

Claude-Session: https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg

Co-authored-by: Claude <noreply@anthropic.com>
…meField

Brings in the phase-3 fix for unresolved semantics extension properties and
applies the same fix to TimeField.kt (Phase 4 file, missing the lowercase
androidx.compose.ui.semantics.role import), found by sweeping every
main-source file with the same checker.

Claude-Session: https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg

Co-authored-by: Claude <noreply@anthropic.com>
ManageCategoriesScreen becomes the Grouped/Ungrouped management home from
the row-4 mock: a SegmentedToggle swaps between role-tinted group cards
(colour dot + name + Edit, member rows resolved via effectiveColorToken,
inline "Add category to this group") and the neutral ungrouped list, each
row carrying an "Add to group" affordance.

- Add-to-group sheet: pick a group, jump to pre-filled group creation, or
  remove from the current group; a "Use the group's colour" switch sets the
  category's token to the "inherit" sentinel so it adopts and follows the
  group's role. Past entries are always kept.
- Group-centric add-member sheet lists ungrouped categories first, then
  members of other groups labelled with where they live, plus a New
  category row that pre-selects the group's default input type and files
  the category on creation.
- Group editor dialog: name, in-theme role via RolePicker (new additive
  showFixedSection flag hides the hex track: a group's role is never a
  hex), default input type, member unfiling, move up/down reorder, and
  delete with a confirmation explaining members are kept.
- ManageCategoriesViewModel gains the groups Flow and group CRUD /
  moveGroup / assign (with adopt-colour) / unassign on the Phase 2
  repository API. No DB changes (schema stays v24).
- Preserved unchanged: archive/unarchive and delete swipes with system
  protection, global drag reorder via the toolbar reorder mode, category
  creation dialog, ManageCategoryValues navigation, tracking modes and
  quick-log surfaces, archived section.
- Help dialog documents groups and the two views; PLAN.md §7 and map 02
  updated; changelog fragment (minor); LESSONS.md entry on snapshotting
  Compose state into locals before async completion callbacks.

Claude-Session: https://claude.ai/code/session_01PZJLynVBkgLtehJFXffnfg
Co-authored-by: Claude <noreply@anthropic.com>
…gn-phase-4

# Conflicts:
#	app/src/main/java/com/mapgie/goflo/ui/components/MetricInput.kt
#	docs/design/logging-redesign/PLAN.md
…gn-phase-5

# Conflicts:
#	LESSONS.md
#	app/src/main/java/com/mapgie/goflo/ui/screens/log/LogCategoryScreen.kt
#	docs/design/logging-redesign/PLAN.md
#	docs/design/logging-redesign/subsystem-maps/01-logging-screens.md
Base automatically changed from claude/logging-redesign-phase-5 to main August 26, 2026 13:06
@mapgie
mapgie marked this pull request as ready for review August 26, 2026 13:06
…gn-phase-6

# Conflicts:
#	docs/design/logging-redesign/PLAN.md
@mapgie
mapgie merged commit b533b85 into main Aug 26, 2026
4 checks passed
@mapgie
mapgie deleted the claude/logging-redesign-phase-6 branch August 26, 2026 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants