# Jyotisha Web Design System

This file adapts the full visual analysis in `CLAUDE_DESIGN.md` to the shipped Jyotisha application. `CLAUDE_DESIGN.md` remains the upstream reference; this file is the implementation contract.

## 读者版年运与正文投影（2026-09-25）

年主、Muntha 星座、年度上升与返照时刻分别来自对应年度的真实计算字段，不从年主对象猜补。两种口径不一致时并列注明，不合成单一结论；本地结果不等于完成外部验证。姓名缺失不显示空行，五要素字段使用中文列名。

Bhava Bala 保留完整十二宫力量表；Score / Weight 等领域表头不单独触发整表删除。内部表连同紧邻说明段移除，标题留下，避免后续正常表归错章节。PL9 审计词和长英文段过滤只用于报告正文，聊天导出与安全图盘沿用既有安全规则。不增加入口、等待动画、布局或颜色。

## 报告核对层与独立附录（2026-09-23）

个人报告保留原 Markdown 阅读、目录隔离与 memo 边界；文后独立渲染服务端分盘和事实表。分盘复用 VedicChartSvg 与 chart-grid/chart-card，不使用 float 或负 margin。事实表默认折叠、可键盘展开，横向溢出仅在表格区域滚动，缺数据不补写。Sade Sati 明确缺三轮日期。09-24 reader-actions D2 撤下操作区「下载原始附录」入口；相关组件、路由和 helper 因删除权限阻塞暂留源码，不当作完成清理。不接普通下载 fallback、不增加 spinner。旧缓存不升级、不重算；没有结构化层就不显示占位盘。文案遵守 VOICE：不把可计算写成已验证。

事实表用中文列名和领域行列呈现，不把引擎路径当行名。主运、分运与小运、SAV 与 BAV、年度位置与 Saham 分为同组子表；缺失的年度行星位置明确说明，不用本命盘替代。机器溯源路径保留在数据中、不渲染。打印或保存 PDF 前自动展开此核对层全部折叠组，完成或取消后恢复原状态；打印解除表格横向滚动裁剪、重复表头，宽 BAV 表仍保留十二星座列。不新增打印入口或等待动画。

## 校正跨午夜日期与采用（2026-09-20）

复用现有时段选择卡追问一次午夜前/后；不知道或跳过保留填报当天凌晨与深夜两段，不补白昼或次日。选项用中文钟点，继续遵守题卡禁止暴露数字钟点的现有校验，不新增入口、状态或等待动画。

区间交付卡按实际日期序号显示分段；跨申报日明确「前一天 / 后一天」，候选列同时给实际日期与钟点，说明「采用后，排盘使用这一日期和时间；原填报日期保留。」图表库默认显示当前采用的有效日期；原申报日期仍独立保存，不猜补历史结果。沿用原按钮、只读门与代表分钟免责声明，不把采用写成唯一分钟确认。文案已对照 VOICE 的服务端数字来源、短句与采用不等于确认原则。

本命上升的分段展示给出完整本地日历日期与钟点，避免同一个钟点被误读为同一天；历史缺日期的结果仍显示 HH:MM，不猜补。沿用既有布局与颜色，不增加入口、状态或动画。

## 校正历史结果身份只读（2026-09-20）

历史打开、刷新与比较返回的结果若无法核实为当前算法及策略，消息区顶部复用 `rectification-pending-note`、`role="status"` 显示「按旧算法产出。当前暂不能核实结果，请先查看，暂不能选择或采用。」保留原历史内容和来源，不出现强制重算入口；关闭旧结果选项、候选采用及普通输入，输入提示为「当前结果仅供查看」。可信当前身份已知但与旧结果不同，非终止会话可显式点「重新比较」，复用既有发送链路；身份未知时无此入口，服务端再次探测失败也不能重算。此状态不等同 Case 已结束，不显示误导的结束提示或额外「再次校正」按钮。真正终止的历史仍沿用原结束操作。服务端独立核验所有结果写入，不以界面禁用代替权限。无新颜色、加载动画或 Home 状态。

## 普通对话寒暄轮（2026-09-20）

服务端标记 `responseKind: smalltalk` 的回复仅展示正文与既有头像/消息操作，不展示思考面板、活动步骤、已完成步骤或技法证据；刷新后的历史也遵循此规则。分类尚未确定、且没有任何真实 activity/thinking/timeline 时，保留消息位置，不虚构「正在分析」或步骤，不另加 spinner。咨询收到真实活动后恢复既有呈现。完成后读取服务端账户余额，寒暄预留点数原额退回，净点数不变；不增加 Home 状态。

## 1. Atmosphere & Identity

Jyotisha feels like a private reading room: warm, editorial, grounded, and quiet enough for reflective conversation. The signature is a pale parchment canvas, translucent warm-gray navigation, fine neutral hairlines, and restrained deep-brown accents. Serif display type gives astrological guidance the gravity of a considered essay rather than a generic chatbot.

## 2. Color

### Palette

| Role | Token | Value | Usage |
|---|---|---:|---|
| Canvas | `--color-canvas` | `#fbfaf7` | Main reading surface, inputs, light controls |
| Page floor | `--color-canvas-soft` | `#f3f2ee` | App background and quiet secondary bands |
| Warm surface | `--color-canvas-muted` | `#ebe9e3` | Cards, user messages, table headings |
| Strong neutral | `--color-canvas-strong` | `#e1ded6` | Pressed and emphasized neutral surfaces |
| Sidebar glass | `--color-sidebar` | `rgba(235, 233, 227, .86)` | Desktop navigation only |
| Sidebar solid | `--color-sidebar-solid` | `#ebe9e3` | Mobile drawer, and any reduced-transparency surface |
| Selected surface | `--color-selected` | `rgba(255, 255, 255, .62)` | Current navigation and raised light rows |
| Ink | `--color-ink` | `#1d1d1f` | Headlines and primary text |
| Body | `--color-ink-strong` | `#32322f` | Strong body copy |
| Secondary text | `--color-ink-secondary` | `#5f5f59` | Supporting copy and labels, section headings |
| Tertiary text | `--color-ink-tertiary` | `#6a6963` | Hints, metadata, empty-state copy |
| Primary action (text rank) | `--color-action` | `#a9583e` | Links, tinted labels, icons — anything the user reads |
| Primary action (fill rank) | `--color-action-strong` | `#cc785c` | Button and avatar fills, the active session rail, rings, carets |
| Primary soft | `--color-action-soft` | `#f7ece5` | Editorial emphasis without a dark block |
| Primary active | `--color-action-hover` | `#8f4630` | Hover and pressed action |
| Dark punctuation | `--color-surface-dark` | `#1d1d1f` | Compact primary buttons and user-authored emphasis only |
| On dark | `--color-on-dark` | `#fbfaf7` | Text on compact dark controls |
| Hairline | `--color-border` | `#d8d6cf` | Default separators and controls |
| Strong hairline | `--color-border-strong` | `#b8b5ad` | Inputs and higher-contrast dividers |
| Success | `--color-success` | `#28633e` | Available and completed states |
| Warning | `--color-warning` | `#b07b22` | Caution states |
| Error | `--color-danger` | `#9a2f2f` | Errors and destructive actions |
| Accessible focus | `--color-focus` | `#cc785c` | Keyboard focus and input focus |

The personal report reuses the product palette. `--report-*` tokens exist so
print can pin a light sheet independently of the screen theme; they are the
canvas, hairline, and action colors, not a second visual identity. Nothing
outside `.personal-report-*` and `.report-center-*` may use them.

| Role | Token | Value | Usage |
|---|---|---:|---|
| Report paper | `--report-paper` | `#fbfaf7` | Same as `--color-canvas`; the reading sheet |
| Report rule | `--report-rule` | `#d8d6cf` | Same as `--color-border`; rules inside the sheet |
| Report accent | `--report-accent` | `#85432f` | **Deliberately not the app accent.** Kept at the old deep brown; see the note below. |

Rules: neutrals stay warm; the action color is scarce; roughly ninety percent of the interface remains light. Dark ink is punctuation, never a page-scale surface. No raw color may appear in UI styles outside these tokens and their documented alpha mixes.

### Where the action color appears

The accent has **two ranks**, because one hex cannot do both jobs. Claude coral
`#cc785c` measures **3.14:1** against the `#fbfaf7` canvas — fine for a fill or a
border, not for text. And 53 of the 62 accent call sites are `color:`, including
the markdown links inside assistant answers.

- `--color-action` (`#a9583e`) is the **text and icon rank**: 4.85:1 on canvas.
  It is the same coral darkened, not the old brown returning.
- `--color-action-strong` (`#cc785c`) is the **fill rank**, where the 3:1
  non-text threshold applies: button and avatar fills, the send/stop control, the
  2px active-session rail, the focus ring, the typing caret, checked radios.

One known gap, accepted by the product owner: white on `#cc785c` is **3.28:1**,
below AA for normal text. It sits on `.button-primary` and the two avatar
circles. claude.ai ships the same value, and "looks like Claude" was the stated
goal. Body text is unaffected — that is what `--color-action` protects.

Scarce is still a budget. The sidebar spends it in exactly three places, and a
fourth needs a reason:

1. `新建对话` — the one high-signal action in the nav, as tinted text and icon on
   a transparent row (`--color-action`, deepening to `--color-action-hover`).
   Never a filled block: a full-width terracotta surface would break the
   ninety-percent-light rule.
2. The 2px bar on the active session (`--sidebar-ring`, which follows
   `--color-focus`).
3. The profile initial's circle (`--color-action-strong`), which only renders
   when the account has no uploaded avatar.

2 and 3 both disappear on a new account with an avatar — no sessions, no
initial — which is how the sidebar ended up with no accent pixel at all. Item 1
is what guarantees the nav still has a visual anchor in that state. `我的报告`
and every section label stay neutral on purpose; giving them color too would
flatten the hierarchy the accent exists to create.

**The report is not on this system.** `--report-accent` stays `#85432f` while the
app moved to coral. The report is a printed-paper surface, not app chrome; coral
reads washed out on the cream sheet. The two palettes are now independent on
purpose — do not "fix" the mismatch.

The glass surface assumes a light backdrop. The mobile drawer floats above the
scrim instead, so the translucency darkened it to `#E3E1DC` and flattened the
warmth; the drawer takes `--color-sidebar-solid` and drops `backdrop-filter`.

Hierarchy inside the nav comes from ink rank, not hue: section headings sit on
`--color-ink-secondary`, their body and empty-state copy on
`--color-ink-tertiary`. Both used to share tertiary, which is why the nav read
as one flat grey. Empty sections name the next step in that same neutral copy
rather than adding a second tinted call to action.

### Dark theme

The dark theme is a role-preserving restatement of the palette, not an inversion.
Every themeable token is redefined; `frontend/tests/dark-theme-contract.test.ts`
fails if one is missed.

Three states, the standard pattern: with no attribute the page follows the OS
through `prefers-color-scheme`; `data-theme="dark"` or `data-theme="light"` on the
root element pins a choice and wins in both directions. Plain CSS cannot share a
declaration list, so the dark palette is written twice — once inside the media
query, once under the attribute — and a contract test asserts the two copies stay
identical.

| Role | Light | Dark | Why it is not an inversion |
|---|---|---|---|
| Page floor | `#f3f2ee` | `#1a1a19` | On light, raised surfaces step *down* in lightness; on dark they step *up*. The floor is the darkest surface in dark mode, the second-lightest in light mode. |
| Reading surface | `#fbfaf7` | `#262624` | Warm, never neutral black. A cool grey would change the product's identity rather than its brightness. |
| Warm card | `#ebe9e3` | `#30302d` | One step above the reading surface in both themes, by opposite directions. |
| Primary action | `#a9583e` | `#d78064` | Two ranks on light (text `#a9583e`, fill `#cc785c`) collapse to one on dark: `#d78064` already reads on `#262624`, where the light values do not. |
| Action hover | `#8f4630` | `#e59273` | Hover darkens on light and lightens on dark. |
| Dark punctuation | `#1d1d1f` | `#f2f0ea` | A dark block on a light page becomes a light block on a dark page; the token name describes the light-theme value, the role is "highest-contrast block". |
| Semantic hues | `#9a2f2f` / `#28633e` / `#b07b22` | `#e08573` / `#74b189` / `#d8a758` | Lifted for contrast; their `-muted` pairs stop being pale washes and become dark tints of the same hue. |
| Scrim | `rgba(29,29,31,.34)` | `rgba(0,0,0,.58)` | A scrim has to darken a surface that is already dark. |
| Shadow | low alpha | ~5× alpha | Without a light ground to fall on, a soft shadow registers as nothing. |

Contrast is asserted, not assumed: eight inks (ink, ink-strong, ink-secondary,
ink-tertiary, action, danger, success, warning) must all clear 4.5:1 against
four dark surfaces (canvas-soft, canvas, canvas-muted, sidebar-solid). The four
neutral surfaces must increase in lightness in floor → canvas → muted → strong
order. Adding a text or surface token means adding it to that 32-pair matrix;
checking only the reading surface is not enough.

**Surfaces that do not follow the theme, on purpose:**

- The payment QR keeps literal white in both themes. Scanners need the light
  modules to actually be light.
- `@media print` keeps white paper.
- The admin is antd + Refine and stays light. Re-skinning `admin.css` alone would
  give a dark shell around light antd components, which reads as broken; doing it
  properly means switching antd to `theme.darkAlgorithm` as well, and that is a
  separate change.

**The control** is a radio group inside the account menu (avatar → 外观), so it
keeps menu semantics: arrow keys reach it and the current choice is announced.
Three options, matching the three states — 浅色, 深色, 跟随系统. Picking one does
not close the menu, so the change is visible where it was made.

"跟随系统" **removes** `data-theme` rather than writing a third value; the media
query has nothing to match otherwise. The choice is stored under `jyotisha-theme`
and re-applied by a synchronous script at the top of `<head>` — it must not be
deferred, or every load flashes the other theme before hydration. Blocked storage
degrades to following the OS. The preference is per-device, not per-account, and
is read through an external store so a change in one tab reaches the others.

## 3. Typography

### Font stacks

- Display: `var(--font-inter, Inter), -apple-system, BlinkMacSystemFont, "Segoe UI", "PingFang SC", "Microsoft YaHei", sans-serif` — the same stack as body. Display rank comes from **weight and tracking, not family**: display and title rules run at weight 500 against body's 400.
  The old value led with `"Tiempos Headline", "Songti SC", STSong, …, serif`. Tiempos Headline is an Anthropic licensed face this app has never loaded (no `@font-face`, nothing in `public/`, `layout.tsx` vendors only Inter), so in production every CJK heading fell through to **Songti SC on Apple and SimSun on Windows** — 20 rules wide, including the `h2`/`h3` inside assistant answers. See BUG-737.
  A Latin-serif-first stack (`"Newsreader", "PingFang SC", …`) was measured and rejected: the Newsreader latin variable subset is 132 KB — 2.7× the entire Inter file — to serif one wordmark, and it splits a mixed heading such as “D10 事业盘怎么读” into two scripts, which reads as a font-loading failure. **CJK never takes a serif here.**
- Body/UI: `var(--font-inter, Inter), -apple-system, BlinkMacSystemFont, "Segoe UI", "PingFang SC", "Microsoft YaHei", sans-serif`. Inter is loaded with `next/font/local` from `src/app/fonts/InterVariable-latin.woff2` (`display: "swap"`, CSS variable `--font-inter`) so Windows/Linux no longer silently fall back past a never-requested Inter, and image builds do not call fonts.googleapis.com. `StyreneB` was removed from the head of this stack for the same reason as Tiempos: it never loaded, so it was dead configuration that made the stack look intentional.
- Code/data: `"JetBrains Mono", "SFMono-Regular", Consolas, monospace`, exposed as `--font-mono`.
- Root boundary pages (`error.tsx`, `not-found.tsx`, `forbidden.tsx`, `global-error.tsx`) sit in the shared root layout segment and must not import `globals.css` — importing it would drag the chat stylesheet onto every admin route. They therefore cannot read `--font-mono` or any token, and inline their own values: a system stack for body text and `ui-monospace, SFMono-Regular, Menlo, monospace` for code. Keep those literals in step with the stacks above by hand.

### Scale

| Token | Size | Weight | Line height | Tracking | Usage |
|---|---:|---:|---:|---:|---|
| `--type-display-lg` | `48px` | 400 | 1.1 | `-1px` | Desktop page titles |
| `--type-display-md` | `36px` | 400 | 1.15 | `-.5px` | Dialog and mobile page titles |
| `--type-display-sm` | `28px` | 400 | 1.2 | `-.3px` | Section titles |
| `--type-title-lg` | `22px` | 500 | 1.3 | 0 | Prominent UI titles |
| `--type-title-md` | `18px` | 500 | 1.4 | 0 | Card and message headings |
| `--type-title-sm` | `16px` | 500 | 1.4 | 0 | List titles |
| `--type-body-md` | `16px` | 400 | 1.55 | 0 | Default reading text |
| `--type-body-sm` | `14px` | 400 | 1.55 | 0 | Compact UI text |
| `--type-caption` | `13px` | 500 | 1.4 | 0 | Labels and metadata |
| `--type-overline` | `12px` | 500 | 1.4 | `1.5px` | Eyebrows and badges |

Display headings use the serif stack at weight 400. Body copy never drops below 14px; 12–13px is reserved for short labels and metadata. No product UI text is smaller than `--type-overline` (12px). Product UI uses three font weights: 400 (display and body), 500 (UI titles, labels, buttons), and 600 (emphasis only). CJK text uses `text-wrap: pretty`; display text uses `text-wrap: balance`.

One documented exception: the thinking text inside a timeline step (`.consultation-run-timeline__thinking`) and the fallback thinking trace (`.message-thinking-body`) render at 13px. They are working notes shown on request inside a collapsed row, not reading copy; the answer itself never inherits that size.

## 4. Spacing & Layout

The base unit is 4px. Tokens are `--space-1: 4px`, `--space-2: 8px`, `--space-3: 12px`, `--space-4: 16px`, `--space-5: 20px`, `--space-6: 24px`, `--space-8: 32px`, `--space-10: 40px`, `--space-12: 48px`, `--space-16: 64px`, and `--space-24: 96px`. `--consult-think-answer-gap` is `var(--space-3)` (12px): it is the only gap between the thinking bar and the answer body. Both `.consultation-thinking-report` and `.message-stage-and-answer` use it; do not write a second value on either path.

Radii have two visual steps. Controls use 8px (`--radius-md`; `--radius-xs` and `--radius-sm` alias that value). Cards and sheets use 12px (`--radius-lg`; `--radius-xl` aliases it). Circles stay `50%`; pills stay `999px`.

- Chat reading width: 760px for the welcome/composer and 900px for long answers. Both chat surfaces share the 900px transcript width; the rectification session no longer narrows it to 720px.
- Admin content width: 1200px, centered.
- Desktop shell: 288px sidebar plus flexible reading panel.
- Layout breakpoints: mobile below 768px, tablet 768–1023px, desktop 1024px and above. These three decide the shell — sidebar mode, grid columns, drawer versus rail. CSS `@media` width cuts must follow `sidebarViewportForWidth` in `frontend/src/lib/sidebar-state.ts` (768 / 1024), not the other way around. The allowlist lives as a comment at the top of `globals.css` and is locked by `frontend/tests/viewport-breakpoint-contract.test.ts`.
- Allowed `@media` widths: 480 (small phone), 640/641 (content grids: membership, rectification candidates, intake card), 767/768 (mobile/tablet), 860 (report TOC, content width of the third column), 1023/1024 (tablet/desktop). Do not add a new width without updating that list and the contract test in the same change.
- All full-height surfaces use `100dvh`, but never as the only declaration. A `dvh` length is dropped whole by an engine that does not know the unit, and a `height` that vanishes falls back to the content height — which is how the settings dialog started resizing per pane (BUG-698). Write the plain `vh` value as the base and upgrade inside `@supports (height: 1dvh)`. Do **not** use the duplicate-declaration form `height: 100vh; height: 100dvh;`: Lightning CSS (Tailwind v4's minifier) collapses duplicate declarations of one property and keeps only the last, so the fallback never reaches the browser. Locked by `frontend/tests/viewport-unit-fallback-contract.test.ts`. Touch targets: on a coarse pointer the hit is 44×44; the visual control may stay smaller. Message-action icons stay 26×26; a fine pointer keeps the 27×34 overlay, a coarse pointer opens gap and bottom margin to 20px so a 44×44 overlay does not eat the next button or the follow-up pills. Locked by `frontend/tests/touch-target-contract.test.ts`.

## 5. Components

### Brand mark

- **Structure:** image-backed mark plus serif wordmark.
- **Variants:** light canvas, dark sidebar.
- **States:** static; never animated.
- **Accessibility:** decorative image is hidden when adjacent text names the product.

### Button

- **Implementation:** report surfaces and the billing pane use `@/components/ui/button`. Login, onboarding, and birth-time dialogs still use `.button-primary` / `.button-secondary`, which share the same 44px height, 8px radius, and action tokens. Those CSS classes stay until those surfaces can move without growing `page.tsx`.
- **Variants:** ink primary, cream secondary, text, circular icon, deep-brown emphasis.
- **Spacing:** 44px minimum height; radii 8px for standard and full radius for icon-only.
- **States:** default, hover, active, focus-visible, disabled, loading.
- **Motion:** 120ms transform/color; active translates by 1px or scales to .98.

### Input and composer

- **Structure:** a column, not a row — warm canvas field on top, the composer's own bottom row beneath it. The row carries the model picker on the left and the send/stop control on the right, with the character count inline beside it.
- **No strip below the composer.** `.composer-footer` used to sit under the field at a permanent `min-height: 44px`, holding the model picker and a count that only appears near the cap — so most of the time it was 44px of empty chrome on every screen. The row is inside the box now and only renders what it has.
- **States:** default, hover, focus with deep-brown ring, disabled only for structural reasons (readonly, session loading, onboarding, the other surface open, **a rectification session whose surface is not yet open**), invalid. Generating does not disable the textarea; the send control becomes stop. On a rectification session the ordinary composer is only a disabled field with placeholder「正在打开生时校正…」; if opening failed, a「重新打开生时校正」button sits above it. No spinner.
- **Queue:** one pending card (`.composer-queue`) sits above the field while an answer is in flight. Copy: “已排队，回答结束后发出”, plus the text and a 44px “撤回”. A second Enter appends to the same card with a newline. Successful settlement sends it; stop, failure, or recovery puts the text back in the field. The send button is disabled while a card is waiting. No spinner.
- **Accessibility:** persistent label where practical; composer has an explicit accessible label.
- **One composer:** the rectification surface renders the same `ChatComposer` as the main chat; there is no second composer. A surface that owns its own draft passes it as `value`; the main chat reads the draft store. Both count down from the same 500-character ceiling through `CharacterRemaining`, which the composer renders inline and only once `characterRemainingVisible()` is true — it no longer has a permanent container. Controls that belong to the composer go through the `toolbar` slot; nothing is stacked below it.

### Answer start anchor

Both chat surfaces pin a new turn at its head instead of following the last streamed token.

- **Head:** the user row of this turn. When this turn has no user row (rectification choice tap, opening, auto-continue) the head is the new assistant row.
- **Pin:** on send (and on those rectification new-turn entries) the scroller places that row at the top with a `space-4` gap and then holds still while the reply grows downward.
- **Spacer:** the last assistant row's `min-height` is `calc(var(--conversation-viewport) - var(--latest-turn-head-height))`, both variables written onto the scroller by `useConversationScrollAnchor`. Not sticky, and `.conversation`'s `padding-bottom` is unchanged. The spacer lasts until the next send; switching sessions clears it.
- **History:** opening another session still lands on the newest content once.
- **Jump to latest:** if the growing turn (or the reader scrolling) leaves more than 96px below the fold, the shared chip appears; pressing it sticks to the bottom for the rest of the turn.

### Jump to latest

- **Structure:** one pill button (`JumpToLatestButton`) with a down arrow and the label “跳到最新”, shared by both chat surfaces.
- **Placement:** hangs off the composer wrap's top edge (`.jump-to-latest`, absolute, `bottom: 100%`) so it never reflows the transcript or the composer. It occupies a 56px band above the composer — the 44px target plus the `space-3` the overlay holds under itself — and the transcript has to reserve that band **plus** one more `space-3` below its last item, or the last tappable row reads as covered and its centre is where the chip's only `pointer-events: auto` area sits (BUG-919). On the rectification surface that reservation is `.message-list { padding-bottom: calc(var(--rectification-jump-clearance) + var(--space-3)) }`, and `.conversation` carries the matching `scroll-padding-block-end`. Full non-overlap at every scroll position would cost `conversationAnchorThreshold` (96px) on top of the band, i.e. 152px of trailing void; that was rejected — the chip only appears once the reader has scrolled up past that threshold.
- **Visibility:** shown when the last turn extends more than 96px below the fold — either because the reader scrolled up, or because this turn grew past the viewport while pinned at its head — and hidden again once they return to the bottom or press it. Sending a question pins the turn head; pressing the control re-anchors to the bottom.
- **Surface:** canvas fill, hairline border, `--shadow-elevated`; hover uses the warm card surface. No utility-class shadows.
- **Accessibility:** a real button in document order with a visible label matching its accessible name, 44px target, and the focus ring; the icon is decorative.

### Ayanamsa preference

The self-profile editor in 星盘资料 (`ChartLibraryPanel`) owns the ayanamsa radios. Personal 个人资料 stays account basics only.

- **Structure:** four 44px stacked radios reused from `.theme-preference-option`, plus a caption under the group. Raman is marked 默认. Each option has a one-line description; selected rows show the same `Check` as the theme panel.
- **Values:** `raman` (default) / `lahiri` / `kp` / `true_pushya`. Copy lives in `frontend/src/lib/ayanamsa.ts`.
- **Hint:** “之后的咨询、报告、星盘库和每日星语会按新岁差算。生时校正目前仍固定按 Raman，之后的版本才会跟着这项设置走。”
- **Placement:** after `ProfileFields` on the self-profile form only. Not on other-chart save, not on `page.tsx`.
- **States:** default, hover, selected (`aria-checked` only), keyboard focus. Switching does not clear a confirmed birth minute.

### Rectification surface

The birth-time rectification session is the consultation transcript plus a house board; questions live inside the assistant message that asked them. It shares every waiting vocabulary with the consultation surface; nothing here spins or says "loading" after the reveal.

- **Reveal:** the surface mounts once per session/Case binding. Opening a Case (homepage card, sidebar row, deep link or refresh) reads the turns and the snapshot in one Case request before the switch, under the same 4-second budget as the home reveal (`RECTIFICATION_OPEN_HYDRATE_TIMEOUT_MS` is `BOOTSTRAP_PREPARE_TIMEOUT_MS`); a session selected at bootstrap is hydrated during the prepare phase. The entry shows a static note meanwhile (card footer “正在打开…”, sidebar row “打开中”, `cursor: progress`) and the previous view stays put. Turns and snapshot are initial state; anything that arrives later is a prop or state update, never a remount. A late or failed read still reveals, with the composer notice “校正记录没有完全加载，可以继续”.
- **States** — what the transcript's trailing entry and the composer show:

| State | Trailing entry | Composer |
|---|---|---|
| `opening` | live row “正在读取你的出生资料，准备第一个问题…”, then tool labels | enabled (typing queues), stop visible |
| `empty` | “这段校正还没有开始。” and one primary action “开始提问” | enabled |
| `question-live` | the asking message carries the embedded card or the spoken stem. An active spoken or choice focus without `asked_turn_id` hangs on the last assistant message, same avatar column | enabled, placeholder points at the card |
| `question-gap`, persisted question | only when no assistant message can carry the prompt; a host question row (`data-testid="persisted-question"`) | enabled, placeholder “请回答上面的问题…” |
| `question-gap`, retries left | one timeline live row “正在准备下一个问题…”, refetching on a 2s timer up to two retries | enabled |
| `question-gap`, retries spent | “没有拿到下一个问题。” and a 44px “接着问” | enabled |
| `question-gap`, collect waiting | no “没有拿到下一个问题”; the last assistant line already has the precise gap. Never while the latest assistant message still carries an unanswerable tap question — that is the repair exit below (BUG-917) | enabled, placeholder “再说一件带年月的事” |
| `question-gap`, dead card on the last message | the latest assistant message carries a tap question with no answer and no live card (its focus was superseded, or GET has no card): the card is not drawn at all, and the gap is the repair exit “没有拿到下一个问题。” + “接着问”. A greyed, unclickable A/B/C/D never appears next to the collect-wait placeholder | enabled, generic placeholder |
| `question-gap`, delivered | no current question, or the current question is a dead choice card, and the session already delivered a range (`completed_with_range` / `provisional_range` / adopt outcomes, or `tied_first`); range card or range line plus an exit note. Never “没有拿到下一个问题。” | enabled |
| `verified_idle` | one closing line `postAdoptVerifyDone` under the still-visible range card (same assistant column); no spinner, no reload | enabled |
| `choice-pending` | the answered card (`data-selected` fill, a top row “正在记录…”) and the same live row from “正在记录本次选择…” through the follow-up turn | enabled (typing queues), stop visible |
| `candidates` | one range-delivery card titled “目前范围 …（对照了 N 件经历）”, a caption under the title. The card appears once every collect line has been asked (refresh, guided windows, the skip retry, the seven targeted kinds) or the reader said there is nothing more to add. The precision gate (range ≤ 10 minutes, top-two gap > 3 points, no exact tie) is reported as `precision_gate_met` but never gates the card on its own: meeting it skips no remaining line, and failing it adds no marker to the card once there is nothing left to ask. No free-text invite. Optional “再答两道参考题微调排序” only when unused D9/D10 remain; if those were already asked and the top two are still within one point, a line “这两分钟按现有信息分不开，参考题已经用过.”; then up to three compare columns (highest posterior first; “更像这个” adopts); a closed “查看验证报告” fold. On a normal convergence, unused style questions are asked before this card. Exhausted and closed-ceiling exits still deliver the card if a style question cannot be rendered, once the precision gate or the “nothing more” stop is met. | enabled |
| `guided-collect` | a named yes/no card then an entry card. A window whose boundary track carries a domain (D9 / D10 Narayana) asks “YYYY 年 M 到 M 月之间，有没有<那一类事>？”; every other window asks openly — “YYYY 年 M 到 M 月之间，有没有什么事，比如<two or three still-open kinds>？” — and one window is asked once, whatever label it carries. The entry card is seven type chips (an open window defaults to the first still-open kind) plus a month-granularity date picker (day optional, years from birth year to this year); submitting writes “YYYY 年 M 月（D 日），<领域标签>方面有一件事”, never the question’s example list. Composer stays enabled. | enabled (typing still records), stop visible |
| `adopting` | “正在采用 HH:MM…” through the follow-up turn | enabled (typing queues), stop visible |
| `confirmed` | “已确认校正时间：HH:MM” | enabled |
| `readonly` | “该校正已结束，只能查看历史。” and “再次校正” | disabled |
| stopped | the row settles with what streamed; a grey caption “已停止，已生成的内容保留；本次不会扣点。” under the body, never `role="alert"` | enabled |

- **Rules:** a follow-up turn continues on the live row already in place; `busy` never drops in the middle of a chain. No copy may ask the reader to wait for the server; a gap is a live row with retries, then a repair button. A hydration that timed out is the same gap. A 402 shows “校正点数不足，正在前往兑换…” for 600ms before the page leaves.
- **Board:** before any candidate exists the header clock shows the declared birth minute and the body names it by source — “出生记录时间 HH:MM”, “你填的大概时间 HH:MM”, or “你给的时间段” — then “回答几个问题后，这里会显示宫位随时间的变化.”; the column narrows to `minmax(16rem, 18rem)` (`is-board-empty`) and widens once a result arrives. No house table is invented for the declared time; the snapshot API does not provide one. The range card may add a caption comparing the declared clock to the current range (“与你填的大概时间相差 N 分钟”, or a hospital-record offset with no preference).
- **Accessibility:** the sidebar opening note sets `aria-busy`; the live row is the timeline row (`role="status"` shimmer label); the repair and start actions are real 44px buttons.

### Birth time intake

- **Structure:** birth date, then three radio rows for “你对这个时间有多确定”——医院记录精确到分钟、家人记得大概时间、只知道时段或完全不知道。家人那档再给四个范围按钮（差不多准 / 前后半小时 / 前后一小时 / 前后两小时 = ±15/30/60/120）。存量 `family_exact` 档案显示成「差不多准」。之后只露出该档需要的钟点、时段或线索字段。
- **Surface:** choice rows use the warm canvas and hairline system; the selected row uses `--color-action-soft` with a deep-brown border, never a dark promotional card.
- **States:** no source selected, source selected, source-specific details incomplete, ready to continue, assessing, rectifying, candidate saved, confirmed.
- **Copy:** labels describe what the user actually knows. “完全不清楚” starts rectification from remembered events and compares declared periods before any minute grid; it does not defer correction. Candidate results explicitly distinguish a reported time, a candidate range, and an active chart time.
- **Accessibility:** native radio inputs remain focusable, every conditional field has a persistent label, status text uses live regions, and the complete flow is keyboard operable.
- **Motion:** source-dependent fields enter with the existing 180ms opacity/vertical reveal; reduced-motion removes the translation.
- **Life-event evidence:** after deterministic questionnaire completion, render three structured event rows by default and allow up to six. Each row uses a domain select, a precision select, and a matching year/month/day control; free-form descriptions are not part of scoring.
- **Candidate result:** keep the reported range, candidate interval, and active-time status visually separate. Delivery shows one range card: title “目前范围 HH:MM–HH:MM（对照了 N 件经历）”, a caption “还能再收窄：如果记得 …” under the title while collect lines remain open, up to three compare columns (time, relative likelihood, D9/D10/nakshatra traits, event-fit counts, next-12-month windows, “更像这个”), and the representative-minute boundary. When the top two columns are within 3 percentage points and the seven collect lines are closed, the card body (not the caption) invites one more dated event of any kind, with examples outside those lines. Collect copy “现在还剩 HH:MM–HH:MM 里 N 个候选” uses the same `credible_range` as the timeline “目前范围”, not the first/last active candidate minute. An eight-method report sits in a closed `<details>` fold. Support numbers stay on the house board. Low confidence keeps evidence editing open; medium offers save or add evidence; high uses a separate confirmation action and never labels a column as the true birth time.
- **Evidence accessibility:** every row keeps visible labels, validation errors use live regions, add/remove controls retain 44px targets, and scoring/confirmation loading states disable duplicate submission without hiding the existing evidence.
- **One-question guide:** the guided journey renders only the persisted `nextAction` and one server-selected question. A deterministic question is visible immediately; Agent wording may replace it without changing the question identity, domain, precision request, progress, or permissions. The composer explicitly permits an approximate year. Spoken collect does not render skip chips; typing 「没有」 still declines the domain and 「记不清」 still skips it. Stop on spoken collect is not a composer button: `CHOICE_STOP_LABEL` (“先这样，先看当前范围”) stays on choice cards, and generating turns keep “停止回答”. The readonly range line is a status sentence, not a stop control. Discriminator cards fold “为什么问这题” under the stem. Hovering or selecting an option does not reveal an `answer_impact` time line. The method sentence (`vargaSentence`) lives in the expanded activity timeline, not in the spoken bubble. The composer has no `rectification-step-state` status sentence and no `rectification-composer-meta`.
- **Draft review:** natural-language answers become one inline review card. The evidence domain is read-only and uses its Chinese label; precision controls which exact year, month, or day input is available. Incomplete drafts keep edit and skip paths visible, while confirmation is disabled until the structured date is valid. Status and errors use polite or assertive live regions without clearing the persisted journey.
- **Scoring and retry:** `score_pending` is a quiet progress surface with cancellable bounded polling and no manual compare control. `retry_scoring` preserves the confirmed evidence and exposes one explicit retry action. Refresh and device changes resume from the persisted action rather than inferring progress from copy.
- **Guided candidate states:** low confidence presents the saved candidate range and either another evidence question or a safe finish; medium confidence can save the range but never apply a representative minute; high confidence names both “候选时间” and “当前排盘使用时间” before explicit confirmation; ready states that the current chart time changed while the original report remains preserved. No state calls a candidate the true birth minute.
- **Guided responsive/accessibility contract:** body copy remains at least 14px, labels at least 12px, and all controls at least 44px. Focus is always visible, the composer is keyboard operable, semantic Chinese phrases remain together at 390px, and reduced-motion removes entrance translation while retaining state changes.

### Birth place picker

- **Composition:** three cascading Base UI Selects — province, city, district — over the bundled China administrative dataset. There is no free-text search and no overseas provider in this surface.
- **Level collapsing:** a level that offers no choice is not rendered. Municipalities and special administrative regions skip the repeated city level; prefecture cities without districts complete at the city; a province with neither lower level completes at the province.
- **Unsure escape hatch:** any city that has districts leads its district list with “不确定，用市区中心”, so browsing never dead-ends. A stored empty district resumes as that choice.
- **Precision copy:** the picker states that county-level precision is enough for a chart, so a village or township birth is not treated as missing data.
- **Value:** administrative codes, the node centre coordinate, and the IANA zone are all persisted. Coordinates come from the dataset; the zone is resolved once per chosen place through the chart engine rather than per keystroke.
- **States:** nothing chosen, partially chosen, resolving the zone, resolved, and zone service unavailable with an explicit retry. An unresolved zone is never reported upward as a usable birth place.
- **Saved profiles:** mounting an already-saved place neither refetches nor reports a change, so opening the profile dialog cannot look like a location edit. Changing the birth date does invalidate the stored offset and resolves the zone again.
- **Accessibility:** every level keeps a visible label, an explicit trigger name, and the 44px target from the select recipe; status text uses a polite live region.

### Birth date picker

- **Composition:** shadcn outline Button trigger, Base UI Popover, and a single-select React DayPicker Calendar.
- **Range:** local dates from 1900-01-01 through today; future dates are disabled. Month and year dropdowns provide direct navigation, with newest years first.
- **Value:** display Chinese long dates while emitting the existing `YYYY-MM-DD` profile value without UTC conversion.
- **States:** empty, open, selected, focus-visible, disabled confirmed profile, and unavailable date.
- **Accessibility:** visible label, explicit trigger naming, 44px targets, keyboard calendar navigation, focus return, and collision-safe popup positioning.

### Model selector

- **Structure:** a compact text trigger sits below the composer and opens an upward popover aligned to its left edge. The trigger shows only the active model name; each option shows only its model name and radio selection state.
- **Width:** the popover is capped at 180px with viewport collision protection.
- **Surface:** canvas trigger with no card treatment; the popover uses the elevated canvas recipe, warm hairlines, and one selected-surface row. The action color is reserved for the selected indicator and focus ring.
- **States:** closed, open, hover, focus-visible, selected, disabled, and unavailable catalog. Selecting a model closes the popover and only affects later messages in the current conversation.
- **Accessibility:** the trigger and every option meet the 44px touch target; options are a native radio group, with a small roving-focus fallback so Tab, arrow keys, Space, and screen readers consistently expose the selected model inside the popover.
- **Motion:** the popup enters over 120ms with opacity and a 4px vertical translation; reduced-motion removes the translation.

### Chat header

- One line, 46px on desktop. Sidebar trigger, session title, and the credit pill. It was 68px and carried a second line reading `分析对象：{盘名}`.
- Ordinary consultation: the person is a quiet button beside the title (`.chat-profile-picker-trigger`, still `.chat-header-chart`). The accessible name is `当前星盘：{人物名}`; the visible text is only the current person's name. Click, Enter, and Space open a popover. `aria-expanded` and `aria-controls` point at that popover. Escape, an outside click, and a successful choice close it and return focus to the button with `preventScroll: true`; focus must not move the chat panel or transcript. The button and each row are at least 44px. The popover uses the elevated canvas, warm hairline, and the same 120ms opacity-plus-4px motion as the model selector; reduced motion drops the translation.
- Before the first message the list selects a person and updates that empty session's binding. Self is the visible default. After the first message the current person stays selected; another person offers only `新建会话并使用此人物` and does not rebind the old session. That action waits until the current request ends.
- Loading reads `人物列表还在读`. Failure reads `人物列表暂时读不出来` with `重试`. When the people API itself fails, the popover reads `暂时读不到其他人` and lists only the signed-in person; history stays on that person and the page does not drop into the recoverable error screen. An incomplete row reads `这份资料还不完整` and cannot be chosen. A deleted person reads `资料已删除 · {名字}`; the old session stays readable and sending is blocked. None of these states use a spinner.
- Rectification, reports, and daily horoscope do not get this control. Their quiet note, when present, remains the static `.chat-header-chart` span and still drops out below 768px. The consultation button stays on narrow screens and ellipsizes so the header remains one line.
- With the composer strip gone as well, the two pieces of permanent chrome went from 68 + 148 to 46 + 124 px.
- On viewports ≤767px the header row is 52px plus the safe-area inset. The credit pill and the rectification 「当前盘面」 chip share one size: 40px visual height, 14px tabular type, the same radius and padding, no 64px min-width. The 44px touch target is the transparent `::before` ring.
- Window-level scroll is reset by `ViewportScrollLock` after the on-screen keyboard closes, so the header cannot be left above the screen.

### Navigation item

- **Structure:** title is the session name. Rectification titles show the result: `生时校正 · HH:MM` when a time is confirmed (confirmed wins over accepted) or only accepted, `生时校正 · HH:MM–HH:MM` (en dash) when only `candidate_range` is a clock pair, otherwise `生时校正`. Daily rhythm stays `今日节奏 · M月D日`. Subtitle is always `M月D日 HH:MM` in Asia/Shanghai from `updated_at` (last activity), plus ` · <chart name>` when the chart is not the account holder. Same-day duplicates are not uniquified with wall-clock `HH:MM`. Display, sort, grouping, and cursor all use `updated_at`.
- **States:** default, hover, current, focus, disabled.
- **Hierarchy:** section labels stay tertiary; session titles and primary actions use ink so history rows do not collapse into the same gray as “收藏对话 / 历史对话”. History groups use the overline token for “今天 / 昨天 / 最近 7 天 / 最近 30 天 / 更早”. When the chart is not the account holder, a secondary line shows the chart name under the title. A session title is named when it is created; opening a stored session must not rename it. `updatedAt` advances only on conversation activity, including rectification turns, choice, adopt, and stop. Opening, refresh, and metadata PATCH do not bump it. A `?c=` that is not on the loaded page is looked up with `GET /api/sessions/{id}` before anyone may say it was deleted. Locked by `frontend/tests/session-open-preserves-identity.test.ts` and `frontend/tests/session-lookup-unlisted.test.ts`.
- **Request behavior:** existing sessions remain selectable for reading while a request is active; creating or sending another request stays locked until the active request settles.
- **Surface:** translucent warm-gray sidebar. Current and hover fill the whole `.session-row` — title and the ⋯ share one chip. The menu trigger has no canvas of its own.

### Sidebar shell

- **Composition:** provider, fixed header, one scroll-owning content region, fixed footer, trigger, rail, and flexible chat inset. `/`、`/chart`、`/ephemeris`、`/reports` share one `(app)` layout: one `SessionListProvider` and one `SidebarProvider`. The session list is fetched once per tab; walking between those four pages does not remount the sidebar or refetch `/api/sessions`.
- **Home registers shell controls** (new chat, select session, rename, pin, share, delete, account menu). The other three pages leave `controls` unset, so rows are links to `/?c=<id>`.
- **Trigger placement:** the single visible collapse/expand trigger sits beside the active session title in the chat header. The sidebar brand row has no duplicate trigger.
- **Desktop:** 288px expanded by default at 1024px and above; 64px collapsed icon rail.
- **Tablet:** 64px collapsed by default from 768px through 1023px; 240px when expanded.
- **Mobile:** no icon rail; an off-canvas drawer uses `min(86vw, 320px)` and closes through its scrim or Escape.
- **Collapsed content:** logo, new-chat action, the page actions, one history expansion action, and account avatar. Individual sessions do not become indistinguishable repeated icons.
- **Expanded content:** the header actions (new chat, 星盘, 星历, 我的报告), then **one flat list** under a single 「最近」 heading: pinned sessions as the first labelled group, then history grouped by recency.
  It used to be three stacked sections — a 星盘列表 chip grid and two `<details>` wrappers for 收藏对话 / 历史对话 — so the nav carried two collapse affordances before the first session row, and neither had anything worth collapsing. The chip grid went entirely: every chip, and the add button beside it, opened the same chart-library dialog that the account menu already offers, so a list of names provided no navigation. Chart data is managed from one place now (account menu → 星盘资料).
  The list sits at the nav's own gutter rather than indenting past a heading icon, because there is no longer a heading to align to. Actions and session rows share 18px icons, caption/body type, and ink/muted tokens; the 「收藏」 group label carries a 13px accent star as an inline marker, not a heading icon. Empty untitled sessions stay off the history list. Pin is favorite. Session row menu is rename, pin, share, and delete — not archive. The history list loads 40 rows at a time and silently appends the next page at the bottom.
- **Empty state:** one message, not one per section. 「暂无对话，点上方「新建对话」开始」 shows only when there is nothing at all; with no pins the 收藏 group simply does not render, so nothing says 「还没有收藏」 about a section that is not on screen.
- **Scroll ownership:** header and footer remain fixed; `SidebarContent` is the sole sidebar scroll owner.
- **Scrollbar:** `SidebarContent`, ordinary session `.conversation`, and the rectification house board use a quiet overlay scrollbar: transparent track, no `scrollbar-gutter`, and a 4px warm thumb mixed from `--color-ink`. The thumb stays transparent until hover or keyboard focus inside the scroller, then uses `color-mix(in srgb, var(--color-ink) 26%, transparent)`; thumb hover uses 40%. Increased contrast keeps the thumb visible; forced colors restore the system scrollbar.
- **Motion:** Sidebar state changes are immediate on desktop, tablet, and mobile. The 44px trigger keeps one stable 18px sidebar glyph and never enters an intermediate scale or opacity state.
- **Accessibility:** Command/Control+B shortcut outside editable controls, contextual trigger labels, 44px targets, focus return, collapsed-only tooltips, reduced-motion, reduced-transparency, and increased-contrast support.
- **State:** the desktop and tablet collapse state is remembered per browser under the `sidebar_state` localStorage key, so collapsing on `/` survives the walk to `/chart` and back. Nothing is stored until someone actually toggles it; with nothing stored the breakpoint defaults stand. The mobile drawer stays session-local and is never remembered — reopening it on every navigation is not a preference anyone set. localStorage rather than the shadcn `sidebar_state` cookie because `/`, `/chart` and `/ephemeris` are static routes and a server-read cookie would opt all three out of static rendering; the stored value is therefore applied in the same post-mount effect that already applied the breakpoint default, and costs no frame that default did not already cost.

### Message

- **Variants:** assistant editorial text on canvas; user text on warm card surface; streaming; error. Streaming uses a timeline of completed steps plus the current step; the thinking body expands while streaming, collapses when answer text appears, and is stored with the assistant message.
- **Identity:** neither role carries an avatar. The assistant reply is plain editorial text starting at the column edge; the user's turn is a right-aligned tinted bubble. The 32px Jyotisha logo used to sit beside every assistant message — at one avatar per turn it became the most repeated element in a long transcript, and it pushed the reply 44px in from the column the user reads down. `--assistant-content-inset` is `0px` now, so the follow-up chips and the run timeline line up with the reply text itself rather than with a mark that is gone.
- **Typography:** assistant body `--type-body-md` (16px) with serif subheadings; user body 14px.
- **Tables:** three-column technique audit tables keep 状态 on one line. Below 768px they stack each row as title + status, then the note, instead of squeezing 已执行 into a vertical glyph column.
- **Follow-up:** the latest settled consultation answer may offer two or three grounded next questions under that answer. Clicking one sends it in the current session. The composer never hosts suggestion chips. If the answer does not support a grounded continuation, nothing is shown.
- **Motion:** a new row enters once, through the GSAP tween in `chat-message-row.tsx` at the 160ms Message duration; there is no CSS entrance keyframe beside it. The trailing assistant reply is one component (`LatestAssistantEntry`) from its first streamed token through settlement, so settling never remounts it and never replays the entrance.

#### Streaming states

Every assistant reply moves through the same states on both chat surfaces, and each state has exactly one visual. The step timeline (`ConsultationRunTimeline`) is the only activity surface. Consultation thinking is complete `think.step` items (v1 `thinking.delta` still renders for one release). Rectification never shows thinking text: provider reasoning is dropped at the public boundary.

| State | When | Visible | Transition in |
|---|---|---|---|
| `queued` | request sent, no server event yet | timeline open with one live row “正在处理…” (spinner + shimmer label), summary “正在分析” | row enters with the message |
| `loading-method` | `skill.started` | live method row | label swap, 120ms fade |
| `calculating` | `tool.started` / chart activity | live calculate row; completed rows above it show the check marker | label swap, 120ms fade |
| `thinking` | `think.plan` / `think.step` (and v1 `thinking.section` / `thinking.delta`) | live think row; complete step text inside the row | label swap, 120ms fade |
| `composing` | first `answer.delta` | live write row; answer text below the timeline, released per frame | answer paragraphs appear as text, no per-token animation |
| `settled` | `run.completed` | summary becomes “已完成 N 步”, timeline collapses in place unless the reader opened or closed it themselves; actions and follow-ups appear | 180ms height transition, 120ms label fade |
| `stopped` | the reader pressed stop | whatever streamed stays; a grey caption under the body says the run stopped and was not billed | none |
| `failed` | `run.failed`, network loss | whatever was received stays in place; the message carries no inline banner — the notice goes to the composer notice / error line | none |

Text release is paced, not animated: the frame buffer commits at most once per animation frame and reveals `max(2, ⌈backlog ÷ 12⌉)` characters per frame, so a burst catches up in about twelve frames and a slow model never reads as stalled. The reader's own toggle on the timeline always wins over the state default. Under `prefers-reduced-motion: reduce` the collapse and the label fade are instant; the pacing stays, because it is content arrival rather than decoration.

### Secondary page shell

`/chart`, `/ephemeris`, `/reports` and `/reports/[reportId]` share the chat
shell. Each used to own a full-screen layout — a `*-shell` root, a `*-topbar`
with one 「返回对话」 link, and a `*-hero` with a page-sized h1 — three copies of
one skeleton, none of them carrying the sidebar.

- **Composition:** `app/(app)/layout.tsx` = `SessionListProvider` →
  `SidebarProvider` → `AppSidebar` → `SidebarInset.chat-panel.secondary-panel`
  (home registers its own inset class). `/chart`, `/ephemeris` and `/reports`
  share `SecondaryPageShell`: the same 46px `SecondaryHeader` (sidebar trigger,
  page name, a reserved note slot so a late birth line cannot collapse the row,
  up to two actions) and a `.secondary-page` body that always fills the
  remaining viewport. Waiting copy is centered in that cell; swapping in the
  tall content does not change the shell height. No spinner or 「正在加载」;
  skeletons are limited to the chart-page plot positions (§15, 2026-09-24). First-screen data for the three pages lives in a module-level
  cache; a second visit paints the last result immediately and refreshes in
  the background. Sidebar `pointerenter` / `pointerdown` prefetches that data
  (`<Link>` only prefetches JS). A tab that outlived a deploy compares
  `NEXT_PUBLIC_GIT_COMMIT` with `/api/health` `.deployment.gitCommit` on
  visibility and before navigation; a mismatch uses `window.location.assign`,
  a match keeps the client router.
- **Separate data and shell subscriptions.** `SessionListProvider` owns both,
  but Home reads only the session/account context and its stable registrar.
  Only AppShell subscribes to shell registration; it passes the original
  `children` through unchanged. Registering fresh controls/rows must not render
  their producer again: that feedback loop can starve client navigation.
  Business changes still publish current callbacks; Home unmount clears them.
- **One sidebar component, two modes.** `AppSidebar` is the only sidebar in the
  product. `/` passes `controls`; the secondary layout does not, and without it
  the same markup renders read-only. There used to be a second component for
  these pages, and two components meant two shapes: its rows had no
  `.session-main`, so they lost the 44px minimum, the row padding and the 2px
  current-item marker, while `.session-row` still reserved a 44px column for a
  menu button it never rendered.
- **What read-only drops — exactly three things.** The per-row menu trigger (and
  with it the reserved column, via `.session-row[data-readonly="true"]`), the
  footer chevron, and the account menu behind it. Everything else is the same
  element, the same class and the same size: brand row, 新建对话, the three page
  actions, the flat 「最近」 list, the 56px `.profile-trigger`. Rows are links to
  `/?c=<uuid>`; the footer is a link to `/`. Renaming, pinning, archiving and
  deleting stay on `/`, backed by `Home()`'s optimistic-update and rollback
  layer, which is far more than these four routes need.
- **New chat is not a home link.** The read-only 新建对话 action links to
  `/?new=1`; Home consumes that intent before activation and opens a fresh local
  consultation. It clears `new`, any `c`, and the login-return stub. Before the
  first question there is no saved session, no `?c=`, and no new history row.
  The first question uses the existing persistence flow. A reserved older
  consultation keeps recovering in the background without taking over this
  explicit new-chat landing or leaving its startup recovery notice there.
  The account footer
  still links to `/`, and a bare-home refresh keeps its existing landing rule.
  The same action and mobile drawer-close behavior are retained; no extra
  button, copy, loading state, or visual treatment is introduced.
- **Leaving the chat is a navigation, not a reload.** 星盘 / 星历 / 我的报告 are
  `AppLink` on every page, including `/`, where they used to be a full document
  load that threw away the React tree, the session list and the account. Only
  `/login` stays a hard exit, and `persistLoginSessionReturn()` still stashes the
  `?c=` before any of them. After a deploy, a stale tab's next `AppLink` is the
  hard exit: `window.location.assign`, not a silent client-router no-op.
- **Loading:** the sidebar renders its nav immediately and fills the list when
  `/api/sessions` returns. While that is in flight the list area carries static
  copy — never a skeleton, per the unified-loading ruling. A list read in the
  last 60 seconds is reused from memory and shown in the first frame; the entry
  is keyed by account, never persisted, dropped on any session write on `/` and
  on any 401.
- **Signed out:** the sidebar degrades to brand, nav, a 「登录后可以看到你的对话」
  line, and a 去登录 footer. It never renders an error state of its own.
- **Page name:** lives in the header, so none of these pages carries an `h1` any
  more. A page's own reassurance copy (the chart page's cost-and-speed eyebrow,
  for one) stays in the body; it is content, not chrome.

### Personal report centre

- **Structure:** inside the app shell, not a page of its own. The name 「我的报告」 sits in the 46px header with 「生成完整报告」 as the header's one action; the body is supporting copy, the overview line, then the **row list** of reports.
  It used to be a standalone full-screen route with a `report-center-shell` root, a `report-center-topbar` holding one 「返回对话」 link, and a `report-center-hero` with a page-sized h1 — the sidebar vanished the moment you opened it, and the only way back was that link.
- **Row list, not a card grid:** `.report-center-list` is one column of `.report-center-row`, hairline-separated by a 1px grid gap over a `--color-border` ground so each boundary is a single rule rather than two touching borders. A card grid costs one scan per card; past five or six reports the reader is looking for state, and a single column puts every status chip on the same x. D12.
- **Row anatomy:** status chip, then the title at `--type-title-md`/500, then the meta line (creation time · depth · themes) at `--type-caption` with `tabular-nums`, then — for a ready report — its stored card summary, or for a failed one the failure reason. Actions sit right-aligned on the same row and wrap under the body at the global 767px cut.
- **Status chip:** a caption pill with a 5px `currentColor` dot and a text label. Ready uses `--color-success`, generating `--color-warning`, failed `--color-danger`; each background mixes the same token at 12%. No spinner. Ready rows use `--report-paper`; all other rows use `--color-canvas`.
- **Meta honesty:** the row says only what `GET /api/reports` returns. It carries no section or chart count, so the row does not claim one; inventing 「9 节 · 22 张盘」 on the client would be a made-up number (VOICE.md 第 2 条). If the endpoint ever projects per-section progress, it belongs on the generating row's note line.
- **Surface:** `--color-canvas-soft` floor; completed rows are paper, other rows canvas, with a warm hairline and `--radius-lg` on the list as a whole. No drop shadow.
- **Metadata and deletion:** full Chinese date · localized depth · localized themes; unknown IDs remain readable verbatim. Every row has a 44px top-right `⋯` menu containing only 「删除」. It opens the row-local 「确定删除这份报告？」 with 删除 / 取消, never `window.confirm`. Failure stays in that row; success removes it and invalidates list cache. In-flight GET responses cannot resurrect a deleted row.
- **Width:** 900px centered, matching long-form chat reading. Rows stack at the global 767px cut.
- **Actions:** “生成完整报告” is the one filled action. A ready row keeps only “查看报告”; export is selected inside the reader so the list does not duplicate that action. Generating copy is one-step (“正在生成报告，大约 10–30 秒”); there is no chapter-count progress. A failed row states the reason in place and offers no second generate entry — the header already has one. Card summary is a deterministic excerpt of the Markdown 「摘要」 section, stored on the cover document at generation time.
- **States:** loading, empty, populated, generating, ready, failed, unauthorized, list error. First-screen loading uses `SecondaryPageShell` waiting copy 「报告列表还没拿到。」 — never a spinner, skeleton, or 「正在加载」. Export is local to the ready reader's drawer and never starts a second writing flow or fetch. Download failures remain in the open drawer; only success closes it and emits a toast. A missing Markdown appendix is an old report: the detail page asks the reader to regenerate.
- **Accessibility:** generate, refresh, and row actions are 44px. The generating row's chip is a live region; a failed export is an alert.

### Personal report reader

- **分块导出对话框 (2026-09-24):** native modal `<dialog>`, bottom-aligned below 860px and centered at ≥860px, app colours only. Desktop is viewport-centered (`inset: 0; margin: auto`) regardless of sidebar state, width `min(720px, 92vw)`, max-height 80vh, with full `--radius-lg` corners. Its flex panel is capped at `calc(80vh - 2px)` to reserve the dialog border; desktop rules follow the narrow-screen dvh upgrade so 70dvh cannot override them. Below 860px the content-column offset, bottom alignment and at most 70vh/70dvh remain unchanged. Header and single export footer stay visible; the block list scrolls, two columns at the existing 860px breakpoint. Escape, backdrop or 关闭 dismisses; focus returns without scrolling. All controls have 44px targets. No spinner, clipboard or extra fetch.
- **Export selection:** default 常用 selects every body block from the single outline's lossless source slices (lead = 摘要); 全部分盘 and 仅核对表 replace the selection. Manual toggles clear preset highlighting. 全选 / 取消全选 works across all groups; zero selected disables export. Counts are actual Unicode code points in serialized block text, including SVG markup, not approximate prose counts.
- **Export content:** full body alone remains byte-identical to the retired ordinary Markdown export. Selected chart/table blocks append new content; selecting all groups is not byte-identical to body-only. D13 requires safe SVG in each chart, reusing the projected engine SVG or the existing hook-free Vedic drawing; offline fallback uses readable monochrome glyphs/legend and presentation attributes. No chart JSON fences or internal audit fields. Fact-table labels/precision/subtables match the reader. Full body uses the historical filename; excerpt adds `-节选`. The existing downloader appends `.md`.

- **Structure:** inside the app shell, like every other secondary page — `/reports/[reportId]` was the last standalone full-screen route, and opening a report used to drop the reader out of the app entirely. 「个人报告」 sits in the 46px header; below it the reader owns its own scroll boundary, carrying the sticky screen chrome (back and the export icon button) and then the longform Markdown body beside a persistent TOC rail. Every phase — loading, generating, timed-out, and each error — renders inside the same shell, so the way back is always the rail. The five-chapter writer document is storage-only and is not rendered. Reports without Markdown show “旧版本报告，请重新生成”.
- **TOC rail:** a persistent right-hand column built from the outline's own `##`/`###` ids — no second slugger, and nothing that touches the chart-grid rehype pass. It is sticky under the report's own action bar, highlights the section in view via `IntersectionObserver`, and marks it with `aria-current="location"` plus a 2px `--color-action` bar. Placement is explicit (`grid-column: 2`) rather than DOM-ordered, so the narrow-screen drawer can stay first in the source. Below 860px the rail is gone and what remains is the collapsed 「目录」 drawer.
- **Paper stays paper:** the rail reads in the app palette because it is chrome. `--report-paper` / `--report-rule` / `--report-accent` are the document's own, deliberately out of step with the app accent, and nothing in this surface puts them on chrome or takes chrome colour onto the page. D11, continuing D3.
- **Surface:** page floor `--color-canvas-soft`; the Markdown article is a `--color-canvas` sheet with a hairline and `--radius-lg`. Print flattens the sheet, hides chrome and the TOC, and pins the light palette.
- **Print inside the shell:** printing takes the whole document, so the reader ships a second `media="print"` stylesheet that hides the sidebar and the 46px header **and unlocks them**: `.chat-app` / `.chat-panel` are `height: 100%; overflow: hidden`, which would otherwise clip a nine-section report to one page. It lives on the component rather than in `globals.css` so it exists only while the reader is mounted and no other surface has to know about it. The `@page` rule is unchanged.
- **Typography:** Markdown `h2` uses `--type-display-sm` serif at weight 400. `h3` uses `--type-title-md` sans at weight 500. Body is `--type-body-md` at 1.65. Honesty labels (`blocked` / `conflict` / `parameter_sensitive`) stay visible; the reading-nav and quality-matrix sections are not collapsed.
- **Charts:** a rehype pass groups each `####` chart heading (optional note paragraph, then the `jyotish-chart` fence) into `.personal-report-chart-card` and consecutive cards into the existing `.personal-report-chart-grid`. A lone card uses `is-single`. The grid is two columns; print and the 760px breakpoint stay one column. Do not float chart headings or figures, and do not use negative margins to fake columns. Occupants are one-character Chinese names plus integer degree (`日 12°`), with `逆` after the name when retrograde (`土逆 3°`). House corners show rasi numbers 1–12. Chart JSON fences are stripped from the `.md` download. Markdown still uses `react-markdown` + `remark-gfm`, `skipHtml`, and no `rehype-raw`. The article tree is memoized; TOC highlight state lives in `ReportToc`, not in `PersonalReportMarkdownView`.
- **Accent:** headings stay ink. Dark ink is never a page-scale rule or card edge.
- **Tables:** wide Markdown tables sit in `overflow-x: auto` wrappers; print unwraps them.
- **Width:** 1120px for the reader chrome; the article takes `minmax(0, 1fr)` and the TOC rail `minmax(11rem, 15rem)` to its right. The TOC collapses into a drawer below 860px.
- **States:** loading, generating, timed-out, unauthorized, not-found, failed, invalid, network-error, markdown-ready, legacy-unavailable. Waiting uses `InlineSpinner` and one-step copy.
- **Accessibility:** the action bar has only 返回报告中心 and a 44×44 Download icon button (`aria-label="导出报告"`, native tooltip「导出」). No raw-appendix or print button, and old `#export` links no longer auto-open a dialog. Browser Ctrl+P keeps the existing print styles and beforeprint/afterprint fact-table expansion/restoration. Generating copy uses `role="status"`. Markdown is rendered with `react-markdown` + `remark-gfm`, `skipHtml`, and no `rehype-raw`.

### Starter home

The empty state is the composer. It used to be a bordered hero card at
`clamp(34px, 5vw, 52px)` plus two 132px product cards — roughly 800px of content
sitting on top of the input, so the primary action was the last thing on the
page. Three parts now, in reading order:

- **Greeting** (`.starter-greeting-block`): one line, no subtitle — a single h1
  at `clamp(24px, 2.8vw, 30px)`, weight 500, `line-height: 1.25`, centred. The
  salutation line above the question is gone; so is the question, which is the
  composer placeholder's job now («想聊什么都可以»). The line is drawn per visit
  from three pools — daypart (morning / noon / afternoon / evening / late-night),
  weekday (Mon, Fri, Sat, Sun only), and returning (accounts that already have a
  session) — concatenated in that order and indexed by one random seed, with the
  `{名字}` entries dropped when no name is set. It lives in the conversation area
  with `align-content: end`, so it sits directly above the composer rather than
  floating in the middle of the row.
- **Composer**: unchanged, and *in the same DOM position it occupies during a
  live session*. Nothing remounts when the first message lands, so an in-flight
  draft, focus, or queued card survives the transition. Its width is
  `--session-column-width` in both states — the empty-state composer used to be
  1040px against the session's 760px, so the input visibly narrowed the moment
  a conversation started.
- **Entry pills** (`.starter-entry`): the two product entrances, rendered inside
  `.composer-wrap` *below* the composer. The visual pill is 36px tall
  (`min-height: 36px`). The transparent hit area is the `::after` box with
  `inset: -4px`, so the touch target is 44px. One word each, accent icon 15px.
  Below them one line merges the daily trend with the rectification hint, and
  an accuracy-boundary line appears when no natal minute is available.

- **States, measured:**
  - Default border is `1px solid var(--starter-entry-border)`, and that token is
    `color-mix(in srgb, var(--color-border) 62%, transparent)`. It is not
    `--color-border-strong` and not `--color-action`. A `1px` shadow uses
    `color-mix(in srgb, var(--color-ink) 4%, transparent)`.
  - Hover (`@media (hover: hover)` only) darkens the border to
    `color-mix(in srgb, var(--color-border-strong) 45%, var(--color-border))`.
    It does not switch the border to `--color-action` and does not tint the fill.
  - Pressed (`:active`) keeps the soft border, drops the shadow, and fills with
    `color-mix(in srgb, var(--color-canvas-soft) 80%, var(--color-canvas))`.
  - Focus-visible is a `3px` outline at
    `color-mix(in srgb, var(--color-focus) 80%, transparent)` with
    `outline-offset: 2px`. That ring is wider and more opaque than the 1px
    default border.
  - Disabled uses the shared `button:disabled` opacity. `data-opening="true"`
    sets `cursor: progress` and adds no spinner and no “正在加载” copy.
  - `prefers-reduced-motion: reduce` already collapses transition duration to
    `.01ms` on `*`. Do not add a loop animation here.
  - At the existing `max-width: 480px` cut, the row and each pill are
    `max-width: 100%` so the label and 15px icon stay inside the row. This
    overflow guard uses the published small-phone breakpoint, not a separate
    375px cut. The 44px hit area does not shrink.
- **Copy:** chat history titles daily readings as “8月22日 · 今日节奏”, typed natal
  questions as “事业 · …”, and rectification as “8月21日 · 生时校正”. Clicking the
  daily pill starts a consultation session immediately; it does not place the
  question in the composer. Private model instructions are selected by a closed
  entrypoint identifier and expanded only on the server. There is no
  “从一个主题开始” grid; leftover `guided_topic` values in stored sessions still
  pin domains when replayed.
- **Rectification hint** keeps three server-driven branches — an unfinished case,
  a finished one that can be redone (`rectificationCardAction === "restart"`),
  and a first run. The branch comes from the entry summary, never the session
  list.
- **Responsive:** the pill row wraps and stays centred; there is no
  phone-specific layout, because there is no fixed-height card to collapse.
- **Accessibility:** each pill is one native button with a descriptive accessible
  name (the full action label, not the one-word face). The daily hint keeps
  `role="status"` while the trend is still arriving.

### Account popover

- **Structure:** identity header, then 个人资料 / 通用设置 / 账户与点数 (with the current balance), theme preference, divider, and logout. 星盘档案不在这个菜单里，它是侧栏导航页 `/people`。
- **Surface:** 280px elevated canvas popover anchored above the sidebar account trigger; warm hairline, existing elevated shadow, no nested cards.
- **States:** closed, open, hover, focus-visible, and logout confirmation.
- **Accessibility:** `aria-expanded`, `aria-controls`, menu semantics, 44px rows, outside-click and Escape dismissal, and focus return.
- **Billing:** the 账户与点数 row opens the settings dialog on the billing pane. It does not leave the homepage.

### Settings dialog

- **Placement:** the overlay and the onboarding paywall portal to `document.body`. `SidebarInset` stays `inert` while a dialog is open (the BUG-744~746 focus contract); the dialog itself must not sit inside that subtree (BUG-968). Closing still uses the existing overlay click, the header button, and the window-level Escape listener.
- **Structure:** one fixed chrome for three panes — 个人资料, 账户与点数, 通用设置. The chart archive is no longer a pane; `?settings=chart` leaves for `/people`. Left nav is 200px, has a hairline boundary, and does not scroll; the title bar stays put; only the right-hand content pane scrolls. The pane menu uses icon + label rows without a trailing chevron because these controls switch content inside the same dialog. Logout stays a separate 400px confirmation.
- **Width / height:** desktop `width: min(100vw - 32px, 880px)`, with `height: min(84vh, 640px)` as the base and `min(84dvh, 640px)` applied inside `@supports (height: 1dvh)`. The right content pane uses 32px horizontal and bottom inset on desktop. All four panes share one class (`.settings-modal`), so switching panes cannot change the frame. At ≤767px the dialog is full-screen with four equal tabs along the top and 16px content inset.
- **Pane menu states:** default is transparent with secondary ink; hover is a 55% wash of `--color-canvas-muted` keeping secondary ink; current is the solid muted surface with primary ink. No accent bar, no trailing navigation chevron, and no weight change — hierarchy here comes from ink rank and surface, matching “Hierarchy inside the nav comes from ink rank, not hue”. The sidebar's 2px `--sidebar-ring` on the active session is deliberately **not** changed to match; the two surfaces read differently on purpose until that is revisited.
- **Content width:** the 880px frame now gives the content pane a deliberate inset instead of leaving controls against the divider. Form panes (个人资料, 通用设置) cap their children at 560px and stay left aligned (`.settings-dialog-content--form > *`); list panes (星盘资料, 账户与点数) stay full-bleed within the inset so tables and card grids keep their columns. The cap sits on the children of the scroll container only — never on `.settings-modal` or `.account-settings-shell` — so it cannot make the frame resize between panes (BUG-554 / BUG-698).
- **Personal profile:** one row of avatar editing (56px preview, eight palettes, 换一个形象) plus nickname and login email. The header uses the product-level “设置” eyebrow above the current pane title; there is no duplicate 管理星盘资料 button.
- **Chart archive (`/people`):** a static secondary page beside 星盘 / 星历 / 我的报告. Self is the first row and cannot be deleted. Each other row is a name plus birth facts, with no relationship field. Detail shows the reported time and the chart time separately, then place and ayanamsa. Shortcuts are 和 TA 对话, 看星盘, 生成报告, and 和我合盘. Adding a sixth person is disabled with 「最多保存 5 个人的星盘」. Delete confirms with the session and report counts before the server removes them together. There is no 「设为默认」 and no 「当前默认」 badge.
- **Subject switcher:** the same control sits beside the title on chat, chart, ephemeris, reports, and the archive. It is not in the sidebar header. Choosing someone in a chat that already has messages switches the current person and opens an empty chat. An empty chat rebinds in place. The list shows at most five people.
- **States:** open, pane switch, list / self / other / add, saving, success, and error.

### Billing pane

- **Structure:** summary line (balance · membership / expiry), then tabs 会员套餐 / 点数包 / 兑换码 / 订单记录.
- **Plan card states:** exactly two, and they are mutually exclusive. `.is-current` (当前套餐) draws the `--color-action` border; `.is-recommended` (推荐, the monthly plan) draws the `--color-border-strong` border on the plain canvas. A card that is both takes 当前套餐 — its own action is 续费, not 立即购买 — so borders and fills can never stack. The badge in the card header says the same word. Mobile ordering (月卡 first below 640px) keys off `[data-plan-alias="monthly"]`, i.e. the plan's identity, not its state, so it survives the card becoming the current plan.
- **`?plan=` deep link:** names its target in copy, not in a third border layer. A `.membership-plan-note` line above the grid reads 「你从「年度会员」的链接过来的，就在下面。」, and the card takes `ref` / `tabIndex` / `aria-current` for the scroll and focus target only. It names the plan by the card's own title rather than a position: below 640px the monthly card takes `order: -1`, so an ordinal would point at the wrong card. Scrolling alone is not wayfinding here — at desktop widths all three cards are already in view, so a link that only scrolled pointed at nothing.
- **Actions:** recommended-plan purchase is `Button` default. Other plan and credit buys use `Button` outline. Cashier still opens with `window.open` in a new tab. Paying copy is 跳转收银台…; pending copy is 等待支付结果. Redeem is an inline form on its tab, not a nested dialog.
- **Deep links:** `/?settings=billing&source=…[&plan=…][&tab=…]` open this pane on `/` and are then stripped. `/membership` and `/membership/orders` redirect here. `&plan=` does **not** repaint the card (that used to be a third border plus an outline on top of the two states); it scrolls the card into view and focuses it, and nothing else.
- **Waiting:** the summary renders from the in-memory account. Package cards stay empty until `/api/payment/packages` arrives. No spinner, skeleton, or 「正在加载」.

### Logout dialog

- **Structure:** confirmation title and explanation, cancel action, and destructive confirm action.
- **Width:** 400px desktop maximum.
- **States:** open, signing out, and error.

### Admin panel and data table

The admin is **not** built from this design system. It runs on antd + Refine, and
`src/app/admin/admin.css` only re-skins antd to sit near the product palette
(warm floor, hairline borders, the same body font). Admin routes deliberately do
not load `globals.css` — that isolation keeps the 33 KB chat stylesheet off every
admin page — so nothing here inherits the tokens above.

- **Structure:** antd `Layout` with sider, header and content, wrapped in
  `.admin-app-shell`; tables, cards, tags and statistics are antd components.
- **Own classes:** only `.admin-app-shell`, `.admin-loading` and `.admin-text-list`.
  Anything else must be an `.ant-*` override inside `admin.css`.
- **Colors:** `admin.css` writes literal hex because it cannot see the tokens. Those
  literals must stay in sync with the palette above by hand; this is the one
  sanctioned exception to the no-raw-color rule.
- **Content width:** 1200px centred, set by antd layout, not by `.admin-scroll`.
- **Loading:** antd `<Spin>`, outside the waiting vocabulary in section 9.

## 6. Motion & Interaction

`--ease-out` is `cubic-bezier(.22, 1, .36, 1)` and is the only easing curve in the
system.

| Type | Duration | Easing | Usage |
|---|---:|---|---|
| Micro | 120ms | ease-out / `--ease-out` | Button, row, popover and tooltip feedback |
| Standard | 180ms | `--ease-out` | Dialogs, onboarding cards, auth steps |
| Message | 160ms | `--ease-out` | A message row entering the transcript |
| Thinking collapse | 180ms | `--ease-out` | The step timeline opening or closing in place (`grid-template-rows` 0fr ↔ 1fr) |
| Timeline label swap | 120ms | ease-out | “正在分析” → “已完成 N 步”, and a live row's label changing |
| Text reveal | per-frame release, not a duration | none | Streamed answer and thinking text; see Streaming states |
| Sheet | 280ms | `--ease-out` | Rectification sheet rising from the bottom |
| Spatial | Instant | None | Sidebar state changes and mobile drawer |

Looping animation is covered separately in section 9.

Only `transform`, `opacity`, and color/filter transitions animate. Reduced-motion disables non-essential animation. Motion communicates state; decorative looping is limited to an active loading state.

## 7. Depth & Surface

Strategy: warm tonal shifts, restrained translucency, and fine hairlines. Most depth comes from the page floor, main canvas, warm cards, and selected white glass. Standard UI uses no drop shadow. Modal, popover, floating-control and raised-sheet depth use one restrained two-stage token: `--shadow-elevated: 0 1px 2px rgba(29, 29, 31, .07), 0 12px 28px -16px rgba(29, 29, 31, .18)`. A second, quieter token, `--shadow-soft: 0 1px 2px rgba(29, 29, 31, .06), 0 8px 20px -18px rgba(29, 29, 31, .2)`, belongs to surfaces inside the reading column — the conversational narrative card, the composer field within a session and the auth mode tab. Floating controls and overlays (jump to latest, popovers, sheets) always take `--shadow-elevated`. Interactive rings use `0 0 0 1px` or the focus ring; no generic card shadows, no utility-class shadows, no atmospheric gradients. When transparency is reduced, frosted surfaces fall back to opaque warm neutrals.

## 8. Agent wording and accuracy boundary

The Birth-Time Guide Agent controls wording only: it may choose a safe tone or extract a reviewable
draft, but it cannot select evidence domains, change `nextAction`, rank candidates, set confidence,
or grant save/apply permissions. Those decisions remain in the deterministic, versioned journey
state machine and its server-side scorer.

`confidence` is an internal, versioned safety gate for this product flow. It is not an external oracle,
clinical claim, or proof from calibrated real cases. Until matching external-engine parity and real-
case validation are complete, low and medium results never apply a minute, and high results still
require explicit confirmation of the matching representative time. Journey telemetry is limited to
metric name, phase, and optional confidence; it never records messages, dates, coordinates, case IDs,
or user IDs.

## 9. 等待与加载

等待按语义分为以下类别。同类必须共用同一套实现；不要为新入口再写一套旋转或呼吸。2026-09-24 决策仅为星盘页盘位增加骨架例外，首页、侧栏、星历、报告与表格区不适用。

| 类别 | 语义 | 组件 / 样式 | 时长 | `prefers-reduced-motion: reduce` |
| --- | --- | --- | ---: | --- |
| 整页 / 整块阻塞 | 首页揭幕前的两阶段载入（载入账户 → 准备对话）、生时评估浮层 | `AppLoadingIndicator`（轨道环 `app-loading-orbit`） | 1.4s linear | 全局 `*` 规则把循环收成一帧；不要改它的 DOM |
| 行内 / 局部等待 | 出生地解析、两个会话面时间线的 live 步、兜底活动面板的 live 行、个人报告列表与详情 | `InlineSpinner`（`inline-spin`） | 0.8s linear | `animation: none`，收成静止圆点，不要半圈圆弧 |
| 盘位骨架（仅星盘页） | D1 / 非 D1 分盘 / 西洋盘尚未返回 | `VedicChartSvg skeleton` / `WesternWheelSvg skeleton`；统一 `.chart-page-skeleton` | 2.4s ease-in-out，opacity 0.35 ↔ 0.6 | 停止动画，opacity 0.5 |
| 流式生成中 | 引导语打字、时间线 summary 与 live 行的文案 | `onboarding-caret` / `agent-activity-shimmer` | 700ms steps / 1.6s linear | 保持现有全局降级 |

Agent 的 live 标记只有 `InlineSpinner` 一种。曾经并存的 canvas 小球（`thinking-orbs`）已移除，不得再引入第二种 live 标记。

校正面的所有等待复用行内等待：进入前的 hydration 在揭幕之前完成，进入后唯一的等待形态是时间线 live 行（含「正在准备下一个问题…」这一条独立 live 行）。区间交付卡只挂在最新那条采用旁白下面，不得留在更早的采集/区分题下。有未答的采集或选择题时卡仍在，「更像这个」置灰并写「先答完上面这道，再选时间」，不得整卡消失。卡上至多三列并排，相同性格句只写一次，点「更像这个」即采用该列分钟，按钮显示「正在采用…」或「已采用」。采用过程中整张卡留在原处，不得因 `busy` 卸掉。采用后前事核对结束走 `verified_idle`：一行收尾文案跟在卡片下面、与助手列对齐，没有 live 行、没有重载、没有采用状态条。卡片与右栏细则见 §11、§12。

首页只揭幕一次。揭幕前的加载屏先并行取账户 / 会话、模型目录和咨询状态，再等待 lookup、会话详情等依赖数据全部到齐；不设 8 秒硬超时，超过 `HOME_BOOTSTRAP_SLOW_MS = 20_000` 才进入现有全屏错误屏。错误屏的「重试」只取消旧请求、重载 provider 并局部重跑 bootstrap，不调用 `location.reload()`。揭幕后不得再出现任何阻塞等待或组件级 spinner：今日星语未到显示静态文案「今天的星语还没写出来。」（不带 `aria-busy`），校正卡用无摘要文案，内容到达后静默替换。登录后的空首页只剩问候语、今日星语卡、生时校正卡和输入框，没有主题卡。切换到消息尚未缓存的会话时消息区留白并只给 `sr-only` 文案，不转圈；揭幕后按侧栏顺序后台预取最近 5 条会话（`SESSION_PREFETCH_COUNT`）让常见切换零等待。轨道环消失后不得再换一套动效继续等。

### 首屏死屏兜底

首页揭幕前的轨道环是纯 CSS。客户端 bundle 没执行、关键 chunk 没加载或没解析成功时，应用层 20 秒云端慢网错误屏不会发生，轨道会一直转，交给独立的首屏兜底脚本处理。

根 layout 里有一段与 bundle 无关的内联经典脚本。它只在同时满足这两条时换掉 `.app-loading-content`：页面上仍有 `.app-loading`，且 `<html data-hydrated>` 不是 `"1"`。时限是 25 秒，大于应用层 20 秒慢网阈值并留出余量，正常揭幕不会闪出这一屏。应用揭幕（`hydrated` 为真）后，现有首页装配 hook 写下 `data-hydrated="1"`。

出现时复用 `.app-loading-error` 的卡片，不新增第二套转圈、骨架或自动刷新。

| 位置 | 文案 |
| --- | --- |
| 标题 | 这个页面没能加载完 |
| 正文 | 网络中断或浏览器版本过旧都会这样。可以重新加载试一次；如果反复出现，请在 Safari 设置里清除本站数据，或把系统升级到 iOS 16.4 以上。 |
| 唯一动作 | 「重新加载」，只在点击时 `location.reload()` |

接口超时仍是原来的「暂时无法进入 Jyotisha / 连接云端服务超时」，不要把脚本没跑起来写成云端慢。

### 报告生成等待态

个人报告要写几分钟，属于"等到有实质进度可报"的一类，因此在上表三类之外单独规定：**只有准备阶段用 `InlineSpinner`，进入写作阶段后换成分章进度，不再转圈。**

三个阶段跟随 worker 自己的 phase 阶梯（`queued` / `loading_context` / `generating_report` → `section:<id>` → `persisting_report`）：

| 阶段 | 屏幕上 | 文案 |
| --- | --- | --- |
| 准备 | `InlineSpinner` | 正在准备你的星盘证据 |
| 写作 | 分章进度条 + 章节清单，无 spinner | 已完成 N / M 章 |
| 收尾 | `InlineSpinner` | 正在整理成文 |

硬规定：

- **进度条按章分格，一格一章，不画百分比。** job 的 percent 在 0→30 和 90→100 是瞬间跳变，只有中段跟随真实工作量；画成线性条等于演出后端没做的动作。格数恒等于章数，条与清单不可能互相矛盾。
- **不做时间插值，不显示预计剩余时间。** 界面上没有任何按定时器推进的东西；后端没动，屏幕就不动。章节耗时被重试放大到两倍以上，报不准比不报更伤。
- **正在写的那一章由行状态判定，不由 phase 名判定。** `section:<id>` 命名的是刚写完的那一章；且章节列表按 `section_id` 字典序返回，不是写作顺序，所以"已完成数 + 1"也会指错。唯一正确的判据是 `pending` 且已被认领。
- **停滞满 90 秒**（`REPORT_PROGRESS_STALL_MS`）当前章文案改为「用时较长，仍在写」。不写第几次尝试——`attemptCount` 不出服务端。
- **写作失败的章仍然计入完成数**，进度条照常前进；走到头不等于全部成功，收尾按 `summarizePersonalReportFailure()` 的白名单文案说明。
- 可显示的只有章节名与章节状态（用户交付物的结构）。`attemptCount`、原始错误码、lease、job id、payload 一律不出服务端——与 BUG-043 的边界一致：那条禁止的是把后台评分状态渲染成用户要管理的面板，本处是只读等待屏上的交付物结构。

Admin 的 antd `<Spin>` 是独立设计系统，不在此表。

## 10. 生时校正常驻时间轴

校正是最长的流程，唯一能表达「正在收敛」的量是范围宽度。它此前只以范围变化句的形式散在消息流里，滚上去就看不见。时间轴把这个量变成常驻形态。

**它是一条只读的横条，钉在校正对话上方，回答「我在哪、还有多宽」；「选哪一分钟」仍然只由交付卡回答。**

### 三条硬规定

**一、它是 `.rectification-workspace__chat` 的第一个 grid 行，不是 `position: sticky`。** 该容器现在是三行：`var(--rectification-timeline-height) minmax(0, 1fr) auto`。条位于滚动容器 `.conversation` **之外**，因此 `scrollHeight` 不变，`use-conversation-scroll-anchor` 的贴底距离仍然精确，它的 `ResizeObserver`（只观察滚动容器的直接子元素）也永远看不到这条。**该 hook 不因本组件改动一行**，校正面不得出现第二套滚动跟随。若改成滚动容器内的 sticky 子元素，还会撞上 BUG-218/252 的老问题：容器留了 `padding-bottom` 时，sticky 子元素被内容盒夹住，永远贴不到可视底边。

**二、条高固定，从首次渲染起就占位。** 这是正确性要求，不是视觉偏好：条在滚动容器外，高度一变就改 `clientHeight`，而没有任何观察者会因此重新跟随——贴底的读者会看着内容悄悄滑出视野底部且无法恢复。同理，Case 未就绪时渲染**等高的空骨架**（`data-state="pending"`），不得用 spinner、不得用「正在加载」文案、不得让条晚一步挂载。桌面 64px，767px 以下 56px；56px 等于既有的 `--rectification-jump-clearance`（44px 触控尺寸 + `space-3`），不新造常数。

读数和轴的水平内边距在桌面对齐助手列：`space-8 + --assistant-content-inset`，与 `.message-list` 沟槽和头像让位相同。**767px 以下只取 `space-4`，不加头像缩进**（BUG-918）：条不在消息列里，手机上对齐头像列买不到任何可见收益，而那 44px 每侧要吃掉 375px 里的 88px，读数因此被裁。底边发丝线和背景仍拉满聊天列，不把条做成第二条滚动容器。

**三、条上只有两个元素**：轴本体（区间带 + 候选标记 + 刻度）与一行读数。手机上读数四项、一行排完：

`05:07–05:09 · 3 分钟 · 代表分钟 05:08 · 已答 6 题`

**读数只增宽，不增高。** 条高仍是硬规定二的 64 / 56px，`.rectification-timeline__readout` 因此是 `flex-wrap: nowrap` + `white-space: nowrap`；真放不下时由条本身的 `overflow: hidden` 裁掉尾部，四项里「已答 N 题」排最后、最先被裁——它是背景信息，区间和代表分钟不是。

**一行是有宽度预算的，767px 以下必须按 375px 算，不是「应该放得下」。** BUG-918 的实证：13px 下四项 + 头像缩进已超 375px，第四项被自身 `text-overflow: ellipsis` 显示成「已…」。因此 compact 段（`@media (max-width: 767px)`，与 `.is-compact` 的 768px 断点同源）做三件事：`padding-inline` 去掉头像缩进、读数 `column-gap` 收到 `space-2`、`.rectification-timeline__dated` `display: none`。按逐字保守估宽，手机上四项 + 3×8px 间隙约 292px，375px 可用 343px、390px 可用 358px；320px 只余约 −4px，靠条自身 `overflow: hidden` 兜底。**再往条上加一项，先重算这笔预算，不是直接追加一个 span。** 组件永远无条件渲染全部 span，隐藏只在 CSS 里发生，轴的 `aria-label` 仍由全部标签拼成，读屏软件不因视口宽度丢内容。

**「已对照 N 件」在手机上不在可见行里，桌面上目前仍在——这是一处未裁决的口径冲突。** 下面的禁列表写明这一项归交付卡、不上条，而它后来（cfb41daf）被加到了条上且没有改本文件。BUG-918 只把它在手机上移出可见行；桌面是否也撤掉需要产品裁决，见 `docs/BUG_HISTORY.md` BUG-918。

**代表分钟上条是 D10（2026-09-16）的产品决定，推翻了「条上只有区间」的原设计。** 理由是窄屏：`.is-compact` 下右栏盘面整体变成默认关闭的 overlay，代表分钟此前只在 `.rectification-board__clock` 出现，于是用户最该一直看着的那个数字恰恰看不见。条上的取值必须与盘面标题行**同一次调用**——`workingRectificationTime(result)`，由 `rectification-agentic-chat.tsx` 算一次、两处共用，不允许第二条推导路径。已采用时写「已采用 HH:MM」，否则写「代表分钟 HH:MM」；**采用不是确认**，完整边界句仍只在交付 / 采用旁白里出现一次，条上不写、也不得暗示某一分钟已确认。

**条上不得出现收窄进度（「已从 30 分钟收到 7 分钟」）。** 开场窗口确实在线上，但没有任何投影把这个对比作为字段给出，而 VOICE.md 第 2 条要求进度数字来自服务端。前端自己减还会算错：轴是**当前**窗口且会放宽（BUG-572），相减会把一次放宽报成进度。这句话继续由服务端拼进旁白。缺的字段见 `BLOCKED.md`。

以下一律不得加回来——每一条都是被明确砍掉的：

| 不得出现 | 理由 |
| --- | --- |
| 范围变化句 | 服务端已写进落库助手消息，BUG-588 防复发要求它在那里；条上再写=同句同屏两次 |
| 收窄进度（「已从 N 分钟收到 M 分钟」） | 无服务端字段；前端相减会把放宽报成收窄。见上 |
| 「仍在范围内 N / 已排除 N」计数与图例 | 实心=在内、空心=已排除，答完第一题即自明；图例是过度提示的典型形态 |
| 阶段标签（时段 / 分钟） | `block_scan` / `minute` 是后台词汇，贴近 BUG-043 红线 |
| 「已对照 N 件经历」 | 仍归交付卡；卡上是人话「N 件里 M 件对得上」。它和条上的「已答 N 题」不是同一个量：后者是服务端 `inference_state.answered_probe_count`，问了几道答了几道，不是经历吻合数 |
| 「时间轴只读」注脚 | 在解释一个不存在的东西；没有元素看起来可点，就不需要声明不可点 |
| 预计剩余时间、定时器插值动画 | 与报告进度条同一条原则：不得演出后端没做的动作 |

**条上每个数字都必须是服务端投影里已有的字段。** 区间来自 `credible_range`，代表分钟来自上面那一次调用，已答题数来自 `answered_probe_count`；投影没给计数就整项不显示，不得补一个 `已答 0 题`。

### 轴与标记

- **轴 = 当前搜索窗口（`candidate_range`），不是开场窗口。** 开场窗口不是定值（±15 / ±30 / ±60 / ±120 / 整天），且放宽会顶穿它（BUG-572：±15 → ±30 → ±60 → ±120）。窗口变化时轴重新对到新窗口，区间带与标记用 CSS transition 过渡到新位置（`prefers-reduced-motion` 由全局 `*` 规则收成一帧）。窗口不变时轴稳定，收窄照样读得出来。
- **候选标记一律等大，只分在范围内 / 已排除。** 不得按 `relativeSupport` / `probability_percent` 分级（尺寸、深浅、粗细都不行）：BUG-560 状态是 blocked，候选间相对支持度 7–9 分（满分 100），校准显示分钟级几乎无区分力，分级显示等于用视觉编码放大统计上不显著的差异。被排除的点留在原地变空心、不消失——用户由此看见自己刚才那一答排掉了哪几分钟。
- **时段阶段（`block_scan`）不画分钟点**，区间带覆盖整个窗口。那一刻确实什么都还没排除，写「24 小时」是事实而非占位。
- 新日期契约按实际日期与相对序号排列；`late_night` 未知/跳过是同一申报日凌晨与深夜两段，不能因末端钟点较小就展开为次日，亦不能填平白昼间隙。历史仅钟点契约保持只读旧呈现，不猜补或重标日期。
- 条上不得出现 `rectification-step-state` 类名（BUG-575 防复发）。

## 11. 区间交付卡

交付对象是区间里并排的候选分钟，不是支持度数字，也不是逐行空差异。

**相同的句子只写一次。** 两列或三列共有的 D9 / D10 / 月宿性格句提到卡片顶部（「三个时间的事业盘都在巨蟹座：做事以照顾人为主」）。列内只留有差别的句子；某列没有差别句就不显示性格块，不写「同上」。单列不提升共享句。

每列 = 时间 + 相对可能性 + 至多三行 + 「更像这个」。列内不再有 `<h3>`。经历对照由服务端拼成一行：「8 件经历里 7 件对得上，最不合的是 2024 年 5 月那段感情」。未来窗一行：「下一个值得留意的时段：2027 年 3 月前后（事业）」；算过但没有窗写「未来一年没有明显的时段」；`by_time` 缺键写灰字「这一分钟还没对照」，不得回退成 `0 · 0 · 0` 或把「没算」说成「没有窗」。用户可见文案不得出现「强相关 / 有关联 / 弱关联」。

卡顶保留范围与经历数；卡底边界句保留；「查看验证报告」默认收起。不预标「排盘用」。卡上没有「再答两道参考题」入口。风格参考题只在出卡前收集，出卡即结算。`tie_break_available` 仍由服务端决定要不要先问，不再驱动任何按钮。点「更像这个」走现有 accept RPC。采用过程中整张卡留在原处；已采用列按钮禁用。有活题时「更像这个」置灰。收尾句跟卡片同一列。

**出生记录与范围冲突时换措辞，不换形状。** 医院记录的那一分钟落在目前范围外时（`record_conflict`），来源小字写满三层：默认仍按记录排盘、经历指向另一段时间差 N 分钟、两条路都可以走；每列按钮从「更像这个」改成「改用校正结果」，按钮下方补一行同为 `--type-caption` 的灰字「选它之后，排盘会从出生记录时间 hh:mm 换成 hh:mm」（`.rectification-range-delivery__switch-note`，与来源小字同字号同行高）。不新增按钮、不加确认弹窗、不改列数与间距；记录落在范围内或来源是「大概时间 / 时间段」时，卡片与今天完全一致。已采用的那一列不再显示这行小字。

引擎 `event_dasha_ledger_by_time` / `prospective_windows_by_time` 的键是引擎 `candidate_times` 去重全集（上限 64），不是引擎分数前三。卡片仍只投影后验前三。若上一轮 64 分钟对照超过 3 秒，下一轮可以把推断层仍有效的分钟作为 `column_times` 传入。

## 12. 校正右栏盘面

右栏回答「当前按哪一分钟在看盘」，不回答「选哪一分钟」。顶部不加任何新说明文字。

**本命宫位改北印星盘。** 用 `VedicChartSvg` 渲染代表分钟的 `house_table`。宫位表退到星盘下方的 `<details>`（读屏与复制仍可用）。换分钟时只高亮变化的宫（`changedHouses` / `lagnaChanged`），不做动画。星盘组件在校正面 `dynamic()` 分包里，不进首页首屏。

**盘里只放彩色行星符号（2026-09-18）。** 此前宫内画的是「水 19°」「罗逆 29°」这类显示文本，一宫三颗星就叠成三行、字号被压到 8。现在宫内只画符号，度数 / 星宿 / 逆行下沉到星盘页的行星表（§15）。星盘页、校正右栏、我的报告三处共用同一个 `VedicChartSvg`，所以三处同时生效；行星表只在星盘页。

| 元素 | 画法 |
| --- | --- |
| 行星 | ☉ 日 · ☽ 月 · ☿ 水 · ♀ 金 · ♂ 火 · ♃ 木 · ♄ 土 · ☊ 罗 · ☋ 计，每颗一个颜色 |
| 排布 | 一宫内横排，每行最多 3 个，第 4 颗起第二行；`MAX_RENDERED_OCCUPANTS` 仍是 6，第 7 颗起收成 `+N` |
| 逆行 | 符号正下方一道同色短横线，不再写「逆」字 |
| 上升 | 第 1 宫加一个上升色粗体小标 `As`。北印度盘第 1 宫恒为上升宫，这个标记来自几何不来自数据，也不占 `+N` 名额 |
| 图例 | 盘下方两行：九个符号各跟一个汉字，末尾「横线=逆行」。只在盘里有星时出现，出现时 viewBox 高度从 400 变 452 |

颜色 token 在 `globals.css` 的 `:root` 与两个深色块各定义一份，**只用于认星，不表示吉凶**——罗计共用一个中性灰正是这个意思：

`--color-planet-sun` / `-moon` / `-mars` / `-mercury` / `-jupiter` / `-venus` / `-saturn` / `-node` / `-ascendant`。

颜色挂在 `is-sun`…`is-node` / `is-ascendant` 修饰类上，不用行内 `style`——报告文档的标记合同禁止渲染结果里出现 `style=`，星盘不做例外。

符号字体是 vendored 的 9 字形 Noto Sans Symbols 子集（OFL，1.5 KB，`src/app/fonts/NotoSansSymbols-planets.woff2`，来源写在 `SOURCE.txt`），经 `next/font/local` 挂成 `--font-planet-glyphs`；字体栈是 `var(--font-planet-glyphs), "Apple Symbols", "Segoe UI Symbol", "Noto Sans Symbols", serif`。构建镜像不能联网，所以必须自带，和 Inter 同一条理由。♀ ♂ 后面跟 U+FE0E，否则 iOS 会画成表情。

`aria-label` 与宫位 `<details>` 表仍读 `occupants` 显示字符串，读屏拿到的还是「水 19°」这种完整信息；符号只改看的那一层。

**折叠块只有两段（D10，2026-09-16）。** 此前盘面从上到下并排五个 `<details className="technique-audit">`，一屏扫下去全是折叠头，看不出哪个该点。现在收敛成两段，星盘本身不折叠：

| 段 | 装什么 |
| --- | --- |
| **候选分钟** · N 个时刻 | 「换升时刻」（段内组标题 + 逐分钟 LayerChips 列表）、「次级候选」子折叠（原「显示层」） |
| **参数与口径** | 「本命宫位表」、「唯一分钟确认门」、「本轮技法」、「两段本命上升」、「经历与大运对照」（含双轨一致性那句）、「交界节奏」 |

**这是换归属，不是删内容。** 六块一条不少，每块保留自己原来的渲染条件——确认门与技法表仍跟着 `table` 走，此前没有星盘时它们本来就不出现，现在也一样。所有引擎串仍逐一经过 `engineMeaningToDisplayCopy()`。逐分钟行的 `is-changed` / `is-working` / 「当前时间」 / 「已更新」标记一律不变。

两段都默认收起，且都是真 `<summary>`——嵌套多了一层，键盘可达性因此只能靠 `<summary>` 保证，不得把任何一块改成挂 `onClick` 的 `div`。盘面内 `.technique-audit` 的分隔线仍是全局关掉的，段内节奏由 `.rectification-board .technique-audit > *` 的 `margin-top` 给。

## 13. 回答的两层可见性

本命类聊天回答默认只展开口语层。从第一个 ATX H2（合同上是 `## 统一参数与原始结构`，切点按任意 H2，以便模型漂移时仍能折）起的全部章节装进 `<details className="answer-detail">`，默认收起。骨架仍完整生成、入库、可复制、可导出；折叠只改默认可见性。

- **口语层：** 第一个 H2 之前的全部内容，直接画在 `.message-markdown`。无 H2 的闲聊和 onboarding 打字机消息整篇留在这一层，不出现折叠块。
- **折叠层：** `<summary>` 主标「完整分析」；副标用 `<small>` 写章节名，取 `headings` 前三个（`统一参数与原始结构` 写成「统一参数」，`技法审计表` 写成「技法审计」），多于三个补「等 N 节」。不要只写「展开」。
- **技法审计：** 正文里已经有审计表时不另折一份；只有事件行、正文没有表时，`TechniqueAuditDisclosure` 跟在折叠块内部。没有 H2 时仍留在回答底部原位。
- **流式：** 折叠块保持收起，不渲染 children，副标写「正在写…」。不得出现 spinner / 骨架 / 「正在加载」。流式结束后再解析报告 markdown。口语层在流式期间仍走 `StreamingMarkdown`。
- **个人报告页**走 `personal-report-document-view.tsx`，不经过本组件。
- **窄屏表格：** 三列表（技法审计）继续卡片化。四列及以上（Yoga、统一参数）在 `.conversation` 里横向滚动，右缘用 canvas 渐隐提示还可滑；`.conversation` 自身 `overflow-x: hidden`，页面不得出现横向滚动条。个人报告表格不走这套规则。
- **表单输入 16px：** 全局 `input` / `select` 用 `--type-body-md`（16px）。iOS Safari 对小于 16px 的字段聚焦时会整页放大且不缩回。`.otp-input` 仍是 20px，`.composer textarea` 仍是 16px。

### Chat body lists

Three product rules for assistant markdown in `.message-markdown` (BUG-962 / 963 / 964). Personal-report markdown (`personal-report-markdown-view`) is a different surface and is not restyled here.

- **Lists have markers.** `.message-markdown ul.markdown-list` is `list-style-type: disc`; `ol.markdown-list` is `decimal`. `::marker` uses `--color-ink-secondary`, not ink. Tailwind v4 preflight zeros `ul, ol { list-style }`; this surface must restore it. Keep `display: grid` — markers render with grid.
- **Prose is not auto-promoted to lists.** `promoteDefinitionLists` still lifts consecutive short `term：body` blocks (BUG-356: parallel transit / advice items). A block promotes only when every one of these holds, and still only for ≥2 consecutive blocks: the term has no sentence-end punctuation (`。！？；!?;`) and no newlines; the body is a single sentence (no sentence-end, or exactly one at the end); the body is ≤ 40 characters; fences and existing lists are skipped. Spoken four-heading prose with a colon inside a long paragraph stays paragraphs.
- **Thinking-bar-to-body spacing is one token.** `--consult-think-answer-gap` (`var(--space-3)` = 12px) is the gap on both `.consultation-thinking-report` and `.message-stage-and-answer`. In conversation scope, `.message-markdown > *:first-child { margin-top: 0 }` so an opening `h2` does not add `--space-8` on top of that gap. Conversation `.markdown-list` item gap is `--space-2` (8px).

## 14. 断点

宽度切点只允许出现在 `globals.css` 顶部注释的白名单里。壳层切点以 `sidebarViewportForWidth` 为准：小于 768 移动，小于 1024 平板，否则桌面。组件级栅格（会员方案卡、校正候选）用 640/641。校正独立问题块（`.rectification-message-question.is-standalone`）与助手正文共用 `--assistant-content-inset`。报告目录在 860 塌成抽屉，因为那是第三栏的内容宽度，不是设备宽度。

禁止再引入 900 / 720 / 760 / 639 / 620 / 430 这类与壳层或彼此错位的切点。新切点必须先改白名单和 `viewport-breakpoint-contract.test.ts`。

## 15. 只读星盘页

独立 route `/chart`，不进 `page.tsx`。外壳先画、主盘先到、其余 tab 按需。不扣点、不调模型。盘面从现有路径复用 `VedicChartSvg`，不搬家。

`/chart` 是静态壳：首字节不取决于引擎。进页只请求 `/api/chart`。分盘（`/api/varga_full`）、大运 Chara（`/api/dasha/chara`）、西洋（`/api/western`）、七政（`/api/qizheng`）在用户点到对应 tab / 非 D1 chip 时才请求。未点的 tab 不发请求。

### 结构

页名「星盘」与出生资料一行在 `SecondaryHeader` 的 46px 顶栏里（§ Secondary page shell）。顶栏之下第一件东西是 Tab 行。不写眉标，不写「打开即有」、不写「主盘直接算 · 分盘按需 · 不消耗点数」，也不承诺打开速度。等待外壳和失败页只有原因/等待句。

五个 Tab 按体系分：**星盘 / 基础信息 / 大运 / 西洋盘 / 七政四余**，画成**一条下划线式 Tab 行**：无边框、无卡面，当前项 2px 下划线 + 主文字色，整行一条 1px 底线。行内 `flex-wrap: nowrap` 且自身横向滚动，所以 375px 下它仍是一行，不折行、不换成第二排——底线画在滚动容器自己的 border 上，不会跟着内容滚走。五个等重的药丸按钮会读成五个可按的东西，Tab 行读成「一个控件 + 一个当前位置」。

分盘 chip（D1–D30）只出现在印度「星盘」Tab 内部，不得把西洋盘或七政四余做成第 13 个 chip。chip 比 Tab **低一级**：无描边、无卡面、caption 字号、三级文字色，当前项只有一块浅底。它是一个 Tab 内部的筛选器，不是第二层导航。Tab 与 chip 的触摸目标仍是 44px。

侧栏在「新建对话」之后、「我的报告」之前加「星盘」「星历」两个入口；折叠轨（64px）仍用既有 `report-nav-button` 图标行，当前项用白玻璃面 + 2px 深棕标记，不新造选中态。星历入口指向 `/ephemeris`（由另一单交付，合入前 404 是预期）。

### 排盘参数表

参数是**一张键值表**（`.chart-page-params-table`），八行：出生时间（含校正状态）、出生地（含经纬）、岁差、交点、上升、月宿、当前大运、引擎。左列标签 caption 字号三级色，右列值主文字色。表下方紧跟 `view.vedic.boundary` 那一句准确性边界句——边界句限定的就是这张表，两者不能分开。

**不再按断点复制参数。** 原本同一组参数有三种画法：中宫叠一张 `.chart-page-center-card`（手机两行、桌面六行），盘下方再来一张 `.chart-page-params-below` 重复那六行，由 media query 三选一。同样的事实画三遍、靠断点开关，改一处要改三处。键值表让每个字段只出现一次，`.chart-page-center-card` / `-compact` / `-extra` / `.chart-page-params-below` / `.chart-page-boundary-desktop` 五个类连同它们的 767/768 开关块一并删除，由 `chart-page-view.test.tsx` 守着不许回来。

桌面（≥1024）盘面与参数表左右并排，行星表是跨两列的整行——它的列宽需要完整版心。

盘内 SVG 文字用 CSS 提到 16px viewBox 单位，使约 318px 盘宽下实际像素不低于 12px。Tab、分盘 chip 均 44px。

### 星盘档案与当前人物（2026-09-25修复）

标题旁的人物切换仍是当前阅读/对话上下文，不替换户主资料，也不是「设为默认」。上次选择可同步预读，但账户与服务端目录绑定完成前，星盘、星历、报告和新建对话不发默认本人的首屏请求；目录暂时失败应可恢复，不假登出，不先闪别人的内容。档案增删改后切换器重新取目录；同一人物不重复广播切换。会话列表更新合并metadata，保留已加载消息、深链与分页外对话；可见列表仅属于当前人物，换账户不保留旧数据。

档案数量仍本人加最多四个他人，无关系字段，本人不可删除。表单添加/编辑标题必须与操作一致。删除确认只显示服务端成功取得的对话/报告数；查询失败时显示「暂时查不到这个人的对话数量，稍后再试」，禁用确认，不能显示0冒充已知。服务端成功后才移除档案并刷新目录；删除当前人物才回到本人。删除未交付报告释放预留点数，已交付/已结算不退，不用客户端猜测退款结果。

「和TA对话」新会话绑定选中的人物；「和我合盘」中的我保持本人，新会话显式绑定本人但不改变全局选择。普通新建深链用已绑定的当前人物。今日星语的可用性与缓存指纹取当前人物，不能由户主是否有分钟压掉他人的卡片。星历暖进只复用同账户/同人物缓存，首次失败仍显示可重试的静态错误句，不新增spinner、骨架或「正在加载」。跨scope迟到响应不得覆盖当前视图或分页游标。

上述为实现约束；登录页面、窄屏和慢网交互仍按真人清单待验，不以组件探针代替。

### 星盘档案页布局（2026-09-26，BUG-1039）

`/people` 上一轮只有类名、没有一条样式。布局按原型定稿，断点只用星盘页已有的 1024：

- **小于 1024px：列表 → 详情。** 同一路由里用 `.people-archive[data-view]` 切换，只显示一栏。点人时压一条 `?person=<id>` 历史记录，浏览器返回和详情顶部的「‹ 返回」走同一条路回到列表；刷新详情地址直接打开那个人。桌面点人不压历史。
- **1024px 及以上：两栏。** 左列表（18–22rem），右详情；「‹ 返回」隐藏。右栏正在看的那一行用中性浅底（`is-open`），强调色只给当前人物。
- **列表行**（`.people-archive-row`，最小 64px）：40px 圆形首字头像（本人写「我」）+ 名字（本人后跟灰底「本人」标签）+ 一行等宽 `tabular-nums` 的「出生日期 · 排盘时间 · 城市」+ 行尾「›」。资料不完整时这一行写「这份资料还不完整」。**当前人物**（`is-current`，与顶栏「当前星盘」同一个人）是 `--color-action-strong` 描边 + `--color-action-soft` 底。
- **添加**：虚线卡片「＋ 添加一个人」（48px，`--color-border-strong` 虚线，文字 `--color-action`），下面小字「还可以保存 N 个人」，N 仍是 `MAX_SAVED_SUBJECTS - 人数`；到顶时换成原来的限额句并禁用。
- **详情卡**：头部 48px 头像 + 名字 +「本人 · 出生地」（他人只写出生地）；两格时间卡「填报时间」「排盘时间」，等宽大号数字。只有采用或确认了**校正结果**（状态 accepted / confirmed **且**有校正案例）时，排盘卡换成 `--color-success` 描边 + `--color-success-muted` 底，标签写「排盘时间 · 已校正」——旧资料读回时的 `confirmed` 兜底不算。下面是出生日期与岁差（显示「Raman（默认）」这类设置里的名字，不露小写键），再下面三个等宽快捷入口「和 TA 对话 / 看星盘 / 生成报告」（图标用侧栏同款 lucide）。他人另有「和我合盘」与「编辑」；本人底部灰字「本人不能删除」。
- **删除只在编辑视图底部**，单独一张卡，删除确认、用量计数、查询失败句全部沿用。
- **头像颜色**：本人用 `--color-action-strong` + `--color-on-dark`（同账户首字圆）；其他人按 id 稳定地取四个元素色 `--color-element-fire / earth / air / water` 之一，字用 `--color-ink`。不新造色值。

### 行星表

三张 `.chart-page-planet-table`（印度盘宿度、西洋相位、七政十一曜）**每一张**都包在 `.chart-page-planet-table-wrap` 里：`min-width: 0` + `overflow-x: auto`。375px 下表格在自己的盒子里横滚，页面不横滚。`min-width: 0` 和 overflow 一样是必需的——grid item 默认按内容定宽，少了它表格会把页面撑宽而不是滚动。印度盘那张从四列扩到八列后 `min-width` 由 `26rem` 提到 `34rem`。

**印度盘行星表的八列（2026-09-18）。** 盘里不再写的东西全部落在这里：

| 列 | 内容 |
| --- | --- |
| 行星 | 上色符号 + 中文名 + 灰色缩写（Su/Mo/Ma/Me/Ju/Ve/Sa/Ra/Ke，上升 As） |
| 黄道经度 | 星座 + 度°分′。不四舍五入到整度——29°59′ 与 0°01′ 差一个星座 |
| 速度 | 顺 / 逆 |
| 宫位 | N 宫 |
| 星宿 | 引擎返回的星宿名。**没有中文宿名表就不造一个**：印度 27 宿与中国二十八宿不是同一套，硬对上去是编事实 |
| 宿主 | 星宿主的上色符号，居中 |
| pada | 1–4，居中 |
| 状态 | 尊贵 / 庙旺等，原样保留，只是挪到最后一列 |

第一行是上升。上升是盘点不是星体，引擎不返回它的星宿 / pada / 宿主，这三格写「—」而不是填一个看起来合理的值。数字列 `tabular-nums`，符号列与宿主列居中。

本轮不新增第二层页签：星盘页已有五个 Tab，参照里「宫位 / 大运 / 星力 / 瑜伽」等页签的内容后续另立单。

### 三套坐标系

每一套必须在自己的 Tab 里写明自己是什么，并显式点名不能互相换算、也不能叠成「双重印证」：

- 印度盘：恒星黄道，岁差用资料里选的那一套。
- 西洋盘：回归黄道，宫位 Placidus；右栏第一张是边界卡。端点未上线时 Tab 仍在，渲染静态说明，整页不失败。
- 七政四余：宿度自角宿初度起算。必须同时出现计都派别与庙旺未闭合。端点未上线时同样只渲染静态说明。

「传统象征」是词条，不得写成运势。页面上不另写「词条式释义，不是对你个人的判断」——行星卡本身已经是度数、星宿、D9，没有判断句。大运 Tab 底部固定：「只有两条同时指向同一段时间才算证据，单轨命中要降一级来看。」Chara 的正式名称是 **Chara Dasha（kn_rao 变体）**，不要写成 Narayana。

0 年大运照实显示，不改引擎。某段 Chara 的 `duration_years` 为 0 时，这一段标注「0 年」，起止落在同一天，不占时间轴，也不展开子运；子运区写「本段时长为 0，不展开」。前一段的结束日就是下一段的开始日。

### 大运 Tab（2026-09-25）

每条轨道自上而下是「现在」卡、时间条、可折叠大运列表。≥1024 时 Vimshottari 在左、Chara 在右；更窄则上下排。底部仍是那句双轨说明。

「现在」卡三行：大运、小运、小运剩余 N 个月。月份按排盘所用的 `asOf` 到当前小运结束日的整月数，结束日当天不往下减。没有落入的时段写「未落入已返回的时段」，没有小运写「—」。

时间条只画时长大于 0 的段，宽度按时长。当前段用主文字色内描边，一条竖线标 `asOf`。两端是 `YYYY.MM`。0 年段不进这条轴。段色轮换现有的浅底 token（`--color-action-soft`、`--color-success-muted`、`--color-canvas-strong`、`--color-danger-muted`、`--color-selected`、`--color-canvas-muted`），不新造一套色。

列表用原生 `<details>` / `<summary>`。只有当前段带 `open`。子运一行是「名称 · YYYY.MM – YYYY.MM」，日期 `tabular-nums` 靠右，当前子运用主文字色。`summary` 与子运行高 44px。未展开的子运列表用 `details:not([open]) > ul { display: none }` 收起。0 年段不是 `<details>`，文字用 `--color-ink-tertiary`，只写「0 年」和「本段时长为 0，不展开」。

### 西洋盘 Tab（2026-09-25）

盘 `viewBox` 是 `0 0 520 520`，容器 `width: 100%`、`max-width: 520px`、水平居中。三圈：外圈星座、中圈行星、内圈宫位号。骨架模式只画这三圈和 12 条星座分割线，不画星座名、行星、宫位号、相位。

星座环按元素填色，token 在 `:root` 与两套暗色里各一份：

| token | 亮色 | 暗色 | 星座 |
| --- | --- | --- | --- |
| `--color-element-fire` | `#f4d3c3` | `#5a3a32` | 白羊、狮子、射手 |
| `--color-element-earth` | `#e7dfc6` | `#4a4636` | 金牛、处女、摩羯 |
| `--color-element-air` | `#d5e2f2` | `#2e3c4e` | 双子、天秤、水瓶 |
| `--color-element-water` | `#d3e6e8` | `#2a4448` | 巨蟹、天蝎、双鱼 |

星座名用 `--color-ink`。这四个填色不是通用文字底，三级字和强调色不铺在上面。相位：合 / 六分 / 三分用 `--color-success`，刑 / 冲用 `--color-danger`。组件里不写死色值。

行星标的是符号加星座内整度，逆行再加 ℞。字号 19（viewBox 单位），375px 页面扣掉两侧各 16px 后，343px 实际盘宽下约 12.53px；不能用屏幕宽代替盘宽验收。标签以 `central` 基线居中，符号字框按本地 Noto Symbols 的高 em 框保守留到 2.2em，普通文字为 1.4em。相邻显示角至少 11°，在两层半径（188 与 136）内找最近空位；ASC / MC 是固定锚点，星座名与宫位号也是障碍，行星让位而不缩字。真实位置在星座环内缘留刻度，并用细线连到显示位置。引导线和刻度不接收指针事件。透明命中圆 r=34，在 343px 盘宽下直径约 44.85px；任一圆不得吞掉其他行星的中心；全部命中圆先画，全部可见行星文字后画，文字点选直接归属自身，透明圆保持唯一键盘按钮，文字层对读屏隐藏。真实浏览器需用 `getExtentOfChar` + `elementFromPoint` 逐字符验证，不只检查标签中心。宫位号保持宫头到下一宫头的中点角度，默认半径84；字框拥挤时只径向换层（108、60、132、36），不改变真实宫头或文字大小。1 / 4 / 7 / 10 宫头加粗。ASC、MC 写在盘内；不再画盘外的「升」。`view.western` 没有 MC 字段，MC 用第 10 宫头。

相位线一直画着。点行星或行星位置表的一行，只留下该星和它的相位，其余变淡；再点取消。相位表同步只列该星。右栏顺序：要点 chips（上升、太阳、月亮、元素最多、星群）→ 行星位置表 → 主要相位表 → 口径说明。星群是同一星座里至少 3 颗行星，由现有 `planets` 数出来，不是新字段。表用 `.chart-page-western-table`，不继承 `min-width: 34rem`，外包 `.chart-page-western-table-wrap`（`min-width: 0`、`overflow-x: auto`）。断点仍是 1024。

### 等待态

2026-09-24 产品决策有限推翻 09-18 方案一（BUG-716 / 966）：`SecondaryPageShell` 标题、note 槽与撑满内容区不变，主盘未到时正常渲染 body 和禁用的 Tab 行；仅 D1、非 D1 分盘与西洋盘位置显示既有 SVG 空模型的骨架与原等待句。骨架无星体、度数、星座标签，几何不得复制；容器 `aria-busy=true`，装饰盘对读屏隐藏。中性 token、opacity 0.35 ↔ 0.6 / 2.4s ease-in-out，减弱动态效果时静止 0.5；不旋转、不扫光。大运、七政表格仍为静态句，首页、侧栏、星历、报告不适用此例外。首次请求（含预取）和按需层均有 25 秒客户端期限；失败移除骨架，再点该 Tab/chip 清失败并重试。401 先显式呈现登录句再跳转。同一会话再次进入直接用模块缓存，不重放等待句。出生资料保存成功后，缓存按账户和资料指纹换键，旧盘不得留在页上冒充新的日期或时间。

| 时刻 | 文案 |
| --- | --- |
| 外壳已出、主盘未到 | 北印度空盘骨架 + 这一张盘还没拿到。 |
| 已点西洋，尚未返回 | 西洋空盘骨架 + 这一栏还没拿到。 |
| 已点大运 / 七政，尚未返回 | 静态句：这一栏还没拿到。 |
| 已点非 D1 分盘，分盘包还没返回 | 北印度空盘骨架 + 这一分盘还没拿到。 |
| 客户端超时 | 这张盘等了太久没有回来，再打开一次试试。 |
| 分盘 / 按需层失败 | 按原因显示既有失败句；不留等待句或骨架 |
| 引擎 429 | 算盘的服务正忙，稍等几秒再打开就好。 |
| 其它主盘计算失败 | 这张盘算不出来，我们已经记录下来了。 |
| 资料读不出来 | 星盘资料这会儿读不出来，我们已经记录下来了。 |
| 已采用的时间缺时区 | 已采用的出生时间缺了排盘要用的时区，这张盘先不能算。我们已经记录下来了。 |
| 时区没有对上 | 出生地的时区没有对上，这张盘先不能算。我们已经记录下来了。 |
| 结果格式对不上 | 星盘结果的格式对不上，我们已经记录下来了。 |
| 还没有出生资料 | 标题「还没有星盘资料」+ 原句 + 主按钮「去填写出生资料」 |
| 资料读不出来 / 已采用时间缺时区 / 时区没有对上 | 各自的原句 + 同一个「去填写出生资料」；不加「还没有星盘资料」 |

资料类这四句的按钮链到 `/people`。旧的 `?settings=chart` 也改去 `/people`，不再打开设置。标题用 `--type-title-md`，整块居中，按钮是主按钮。引擎忙、超时和坏结果不加这个按钮。解析 `?settings=` 只在 `settings-url.ts`；`?settings=billing` 仍只开账户与点数。

## 16. 星历页

独立 route `/ephemeris`。不扣点、不调模型。页面挂在 `app/(secondary)` 共享外壳上（§ Secondary page shell）：页名「星历」在 46px 顶栏里，顶栏不放按钮；`.ephemeris-body` 是唯一滚动的东西。

- **结构：** 日期条；今日五要素；当日行运；未来九十天；底部提问提示卡。顺序固定。页尾不另写定性句。
- **日期条：** 居中的 `‹ 日期 ›`——日期是主语，两枚 44px 箭头按钮是它的把手。箭头字形 `aria-hidden`，可访问名仍是「前一天」「后一天」，读屏不丢方向。**「今天」只在非今日时出现**，作为日期下方一枚文字按钮；在今日时它整个不渲染，而不是渲染成一枚禁用按钮——灰掉的按钮仍要被读、仍要被 Tab 跳过。原本三个并排等宽按钮把「前一天 / 今天 / 后一天」读成三个平级动作，日期本身反而被挤出了这一组。
- **三段同一套卡片：** 五要素 / 行运 / 未来九十天三个 `.ephemeris-section` 各是一张卡（1px 描边 + `--radius-lg` + `--color-canvas`），卡内是行。原本三段的**内容**各自画框而**段落**不画框，于是三段看起来是三种不同的东西。框归段落，段内只有行。
- 切到未缓存的日期时，日期条和布局留下，五要素、行运立刻换成「这一天的五要素还没拿到。」「这一天的行运还没拿到。」事件区写「换座和停滞还在取。」，这时不用「还没接上」。没有 spinner、骨架或「正在加载」。请求失败时，三段都写「这一天的星历没取到，点日期再试一次。」再点这一天的日期，或在失败时点左右箭头，就重试这一天；日历仍可改去别的日期。旧日期的响应，包括进页时刷新的今天，不得盖住正在看的另一天。
- **五要素（2026-09-26 可读性改版）：** `dl` 网格保留：桌面五格一行（星期、月相日、月宿含第几足、瑜伽、迦那），格子是段落卡内的浅底块。767px 以下收成五行：左列标签固定 5.5rem、不加字距，行距收紧到 `--space-2`。
  - **先中文、后梵文。** 主行中文，副行 12px 三级色写引擎原名（`lang="sa-Latn"`）。中文名只来自 `src/lib/panchanga-names-zh.ts`，该表逐字抄自任务书附表，不自行翻译、不增删；匹配忽略大小写、空格、连字符，别名只有 Garija/Gara、Dwitiya/Dvitiya、Shashthi/Shashti。表里查不到的名字原样显示梵文、不出副行，并在控制台记一次 `panchanga_name_zh_missing`。星期接口里本来就是中文，不出副行。接口字段不变：`factor.value` 仍是引擎名，中文在视图层投影。§15 行星表「没有中文宿名表就不造一个」仍只管星盘页；星历这张表是产品在任务书里给定的。
  - **吉 / 中 / 凶是行右侧的彩色小标签**（`.ephemeris-quality`）：吉 `--color-success`、凶 `--color-danger`、中 `--color-warning`，底是同色 `color-mix(… 12%, transparent)`。只照搬引擎标签，不写成建议。
  - **卡片顶部当日总评 + 计数。** 一句 `{月相短语}，{整体}{Vishti 追加}。`，按固定规则拼（`panchangaDaySummary`，纯函数，不调模型）：Purnima「满月之日」、Amavasya「新月之日」、其余白分「月亮渐盈」、黑分「月亮渐亏」；吉 ≥ 4「整体吉」、3「整体偏吉」、2「吉凶参半」、≤ 1「整体偏凶」，中不计入；迦那为 Vishti 时追加「；迦那落在毗湿提，重要的事避开」。下面两枚计数标签「N 吉」「M 凶」。五要素或其中任一吉凶缺项时，总评和计数都不出，只显示已有行。
  - 卡片下固定一行岁差说明，按资料实际岁差填名：「五要素按 Lahiri 岁差算，和星盘页的 {Raman / KP / True Pushya} 不同。」资料就是 Lahiri 时写「和星盘页相同」，读不到资料岁差时只写前半句。行运段不加这句。
- **当日行运（2026-09-26）：** 每行是一个 `li`：左 1.75rem 彩色行星符号（复用 `--color-planet-*`，与星盘页行星表同色、同字体栈）+「{行星} 在 {星座}」+ 副行「落你的第 N 宫」（仅 `natalRelativeAvailable` 为真时）与逆行时的「逆行」+ 右侧等宽度数（度°分′，`tabular-nums`）。桌面与手机同一行式，不再有表头和 `data-label` 堆叠。没有本命上升时副行不写宫位，段首写「还没有本命上升，先不写落在你的第几宫。」
- **未来九十天：** 按日期升序只写事实（「某星 进入 某座」「某星 停滞转顺 · 度数」）。`/api/ephemeris_events` 未上线时整段静态说明：「换座和停滞还没接上。这一页其余部分不受影响。」不得让整页失败。
- **出口（2026-09-26 挪位）：** 「带这天去提问」不在顶栏了。页面最底部一张浅色提示卡 `.ephemeris-ask-card`（`--color-action-soft` 底、`--radius-lg`、宽度与段落卡一致）：左侧「想问这一天适不适合做某件事？」，右侧主按钮「带这天去提问」（44px），行为不变——把当前日期预填进对话草稿并回到 `/`。窄屏时问句自己折行，按钮不变宽。不写「这一页是天象本身，不是对你的判断。」
- **等待：** 揭幕后不得再出现 spinner / 骨架 / 「正在加载」。首屏未到时 `SecondaryPageShell` 写「这一天的星历还没拿到。」，居中在已撑满的内容区里。未登录是静态「请先登录」加去登录，不是转圈。同一会话再次进入直接用模块缓存。
- **文案：** 不得写运势结论，不得把三套坐标系换算或叠加。当日总评只来自上面的固定规则。不另印「这是天象本身」这类边界说明。