Plain My list, one palette, journal keeps entries in their week

[sarthakagrawal927]

Owner: "Please fix live. I want to start using it immediately. I don't want AI involved right now." This implements option A from the 2026-10-11 app UX audit, plus the journal fix. There is no AI anywhere in these flows.

What changed

• My list: one client component (my-list.tsx) is used for both signed-in and signed-out users. A storage adapter handles the differences: IndexedDB for signed-out, server actions for signed-in.
  • One add field with a gold "Add" button. It adds the text exactly as typed.
  • Status is To do / Doing / Lived, and that status is the only source of truth for "lived".
  • Each item has an optional target year, visibility (signed-in only, private by default), notes, and steps the user writes and can tick in any order.
  • Lived items appear in a compact list with their dates. Saved Bingo boards keep a quiet link list.
  • Removed: quest-chains.ts templates, locking, emoji, difficulty labels, the two-column layout, the control strip and the hero.
• Branding: the header, footer and titles say "Live" with the ring mark. "by Significant Hobbies" remains only as a footer link. The nav label is now "Journal".
• Palette: the field tints in globals.css now map to neutral surfaces. Gold is used only for the primary action and the active nav/segment. In DESIGN.md, the five-hue rule is replaced by a one-palette rule.
• Journal:
  • Entries are matched to weeks by the midpoint of their stored week. Switching between Monday and Sunday starts no longer detaches a saved entry.
  • Saving an existing entry updates its original key.
  • Added a ‹ › week chooser.
  • The week-start setting moves below the list, with an explanation.
  • The "N weeks" pill is removed.
  • Older daily notes sit in a collapsed list.
• Explore, Life in weeks and Life bingo: neutral palette and copy cleanup only.

Data safety

• No schema change and no migration.
• New steps are stored as UserQuest rows with type='bucket-step'.
• Notes use the existing description column.
• Legacy generated chain steps (bc-*) are filtered at read time:
  • completed ones show as checked and read-only;
  • active or abandoned ones are hidden;
  • nothing is rewritten or deleted.
• Local records keep unknown fields, and the existing permissive validators are unchanged. Weekly entry keys are never re-keyed.
• completeUserQuest no longer marks a bucket item done when a generated chain finishes. The chain no longer exists.
• Verified on a local D1 copy seeded with legacy-shaped rows: in-progress, public and done items, bc- steps (one completed, one active), weekly entries from August to October, daily journal entries, and a Bingo board. All of them load and display correctly.

Checks

biome, format, typecheck, 724 unit tests, unused, complexity, duplication, cycles and build all pass. Screenshots were taken at 390 and 1440 of My list, Journal, Explore, Life in weeks and Bingo, in empty, local-populated and signed-in states. None had horizontal overflow or console errors.

Codex drafted this change; Claude reviewed it, fixed issues and verified it.

🤖 Generated with Claude Code