feat: add daily home and vitals dashboard prototypes

docs/execution-support.md

@@ -2,7 +2,8 @@
 
 The shared sidebar opens `/support` (連絡) and `/journal` (記録), alongside
 リーダー and Twitter Lite. These are UI-only prototypes with fictional contacts
-and in-memory state. Reloading or leaving the route resets the prototype state.
+and in-memory state. Reloading resets the prototype state. Tasks, communication status, outcomes, and
+journal entries are shared between routes for the current browser session.
 No messages, calendar events, medical records, or Rensheng pages are written.
 
 ## Reference and scope
@@ -32,3 +33,32 @@ dose, weight-target, or treatment recommendations.
 The UI uses existing shadcn Base UI components and neutral theme tokens.
 Shared account management continues to use the existing connection system;
 the new communication and journal prototypes do not consume those accounts.
+
+## Daily home
+
+`/` presents a greeting, a large input, and a flexible plan grouped as
+「まずこれ」「いつものこと」「余裕があれば」. There are no fixed time slots.
+Tasks can be reordered, completed, deferred, restored, or followed as routine
+steps. Communications can be reviewed directly in a home dialog; changes also
+appear in `/support`. Journal entries and corrections appear on the home, and
+reader samples open for reading. Twitter Lite remains a separate work surface.
+
+The input currently uses a deterministic Japanese mock interpreter, not an LLM.
+It proposes typed actions for task creation/status/reordering, routine steps,
+contact reply/review or deferral, notes/weight/medication records, and navigation.
+Confirming a proposal dispatches the corresponding operation. Unknown or
+ambiguous input does not change state. Message sending still goes through the
+existing simulated review UI; this prototype performs no external send.
+
+Examples: 「買い物を追加」「朝の支度をあとで」「青木さんに返信」
+「メモ：次は資料の2ページ目から」「体重は65.2kg」「リーダーを開く」.
+
+The interaction reference is [Tiimo visual planning](https://www.tiimoapp.com/product/visual-planning),
+reviewed on 2026-09-28: combined routines and tasks, flexible reordering, small
+steps, and natural-language planning. Unlike its timed scheduling options, this
+prototype deliberately keeps the day free of precise times as requested.
+
+The home greeting includes a short prose brief derived from current task and
+communication state. Completed or deferred items leave the brief; the next
+contact opens directly from the text. A current resumption note takes precedence
+over the optional-task suggestion. This is local templated copy, not an LLM report.

docs/research-decks.md

@@ -2,7 +2,7 @@
 
 ## Workspace
 
-Both `/` and `/deck` render the research workspace. A collapsible shadcn/ui
+`/deck` renders the research workspace; `/` is the integrated daily home. A collapsible shadcn/ui
 sidebar based on `sidebar-09` shares its navigation rail with the article reader
 at `/inbox`. Within Twitter Lite, it switches between research chat and deck management.
 Deck management switches decks and adds columns. The avatar at the bottom of the

docs/vitals-preview.md

@@ -0,0 +1,18 @@
+# Vitals reference preview
+
+`/vitals` recreates the Body and Environment screenshots attached to
+[Alan Shiflett’s post](https://x.com/AlanShiflett/status/2103524300158366183).
+The shared sidebar opens it as バイタル. Body categories and history, environment
+metric details, chart period/series selection, and simulated climate controls
+are interactive. Other screenshot navigation entries open a preview explanation.
+
+All scores, classifications, dates, readings, and connection indicators are
+reference/demo values, not the user's health or device data. No clinical
+assessment, data sync, or device command is performed. Obscured reference text
+remains a visual placeholder, not inferred medical content.
+
+`public/vitals/body-reference.jpg` is the post's second public image, retained
+as the anatomy illustration source and clipped in CSS. Source media:
+https://pbs.twimg.com/media/HTE4JWFWUAAnPBt.jpg
+The rest of the interface is HTML/CSS with SVG data charts. Reference-specific
+colors are scoped to `--vital-*` tokens in `vitals.css`.