8 Commits

Include renames

Author	SHA1	Message	Date
Jesse_ChenandClaude Opus 5	62903b7a12	feat(ui): 空状态改成「问候 + 输入框 + 两枚入口 pill」 ... 此前空态是 hero 卡（h1 clamp 到 52px）加两张 min-height 228px 的产品卡， 输入框被压在约 800px 内容之下，主动作不是视觉焦点。 改法：问候拆成 StarterGreeting 留在对话区并底对齐，两个产品入口降级成 StarterEntries 渲染在 composer 之后。composer 本身一行未动——它在空态与 会话态是同一个 DOM 位置，首条消息落地时不重挂载，草稿/焦点/排队卡都不受影响。 顺带修掉：空态 composer 1040px、会话态 760px，发首条消息时输入框会当场 变窄一截。两态统一到 --session-column-width，并新增断言锁住。 校正入口保留三个服务端驱动的文案分支（我第一版收成了两个，是 rectification-agentic-entry 打红才发现）。 DESIGN.md：Product entrypoint card 整节重写为 Starter home；删掉 Suggestion card 死文档（它描述的主题卡样式正是本轮删除的 CSS）。 测试 3350 不变，fail 仍 31 且与基线双向零差异；/ 仍 Static； CSS gzip 41,096→41,044（−0.13%）。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0193vBv6w5MV2cifdTUu9H5P	2026-09-16 05:31:15 +00:00
Jesse_ChenandClaude Opus 5	66d9f59d84	feat(ui): 标题不再落宋体，强调色分阶换 coral，删输入框常驻底栏（BUG-737/738） ... BUG-737：--font-display 以两个从未加载的 Anthropic 授权字体开头 （Tiempos Headline / StyreneB：无 @font-face、public/ 无字体、layout.tsx 只 vendor 了 Inter），于是每个中文标题都掉到 Songti SC / SimSun——20 条 规则宽，含助手回答正文的 h2/h3。display 与 body 合并为同一条无衬线栈， 层级改由字重承担（33 条 display 规则 400→500）。 拉丁衬线方案实测否决：Newsreader 拉丁子集 132 KB（Inter 的 2.7 倍）， 只为给一个品牌字上衬线，且会把「D10 事业盘怎么读」劈成两种字形。 BUG-738：亮色 #85432f 与暗色 #d78064 不同源；--color-ring 在 @theme inline 里硬编码不跟随 :root。产品拍板换 Claude coral #cc785c， 但实测它作文字色只有 3.14:1，而 62 个调用点里 53 个是 color:。 按角色拆两阶：--color-action #a9583e（文字 4.85:1）、 --color-action-strong #cc785c（填充/导轨/焦点环，3:1 非文字阈值）。 --report-accent 刻意保持 #85432f（报告是纸面，不跟应用强调色）。 T1.3/T1.4：模型选择器进 ChatComposer 的 toolbar 插槽，删掉常驻 44px 的 .composer-footer；顶栏 68→46px，「分析对象：」改为标题旁静默 chip。 防复发：新增 font-stack-loadable-contract，断言字体栈里每个 family 要么 vendored 要么是系统字体，且 --font-display 不得触达任何 CJK 衬线。 测试 3346→3350，fail 仍 31 且清单与基线逐条一致；/ 仍 Static； CSS gzip 41,095→41,096（+0.002%）；快速门 pytest 段 798 passed / 0 failed。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0193vBv6w5MV2cifdTUu9H5P	2026-09-16 04:53:14 +00:00
Jesse_ChenandCursor	c9ec541164	fix(home): stop silent rectification open after login (BUG-599) ... Bare `/` was treating the latest history session as active, so a returning account could auto-open a failed rectification Case and left-align the starter home. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-09-09 10:47:47 +08:00
Jesse_ChenandClaude Fable 5.1	aff9d19343	fix(chat): keep the latest reply mounted through settlement and animate the timeline collapse ... The streaming and settled versions of the trailing assistant reply were two components, so settling unmounted one and mounted the other and the entrance tween replayed over text the reader was already on. One LatestAssistantEntry now owns that row under a single key, and the history list excludes it. The CSS entrance keyframe that doubled the GSAP tween is gone and the tween matches the documented 160ms. The step timeline no longer remounts on settle: it is a button-controlled disclosure with a 180ms grid-rows transition, the reader's own toggle wins over the live default, and an in-flight request with no events yet shows a queued row instead of an empty shell. BUG-474 BUG-475 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JUei7K13cYxLHE3Axe4A45	2026-09-02 04:29:01 +00:00
Jesse_ChenandCursor	8b8e5214f9	fix(web): keep onboarding and mobile natal board on one aligned overlay ... Put the compact board trigger in the chat header, keep the sheet above the composer on iOS, and align onboarding messages with the intake card on the session column. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-20 23:54:20 +08:00
Jesse_ChenandCursor	52f3c04b3b	refactor(chat): remove the post-answer suggestion chips and the table that fed them ... Measured use of the three chips above the composer was negligible. They were also not what they appeared to be: the server looked up a fixed triplet by session theme and passed it as metadata that overrode anything the model produced, so the same ten hardcoded sets served every user regardless of question or chart. That is a plausible reason nobody pressed them. Both copies of the per-theme table are gone, reply metadata narrows to the session title, and the two parse entry points collapse into one now that they return the same shape. The write schema still tolerates a suggestions field so a client on the previous bundle does not lose its message mid-deploy, and stored answers containing the legacy hidden block are still stripped rather than shown raw. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-18 15:44:19 +08:00
Jesse_Chen	0fd111d16b	fix(ui): align message motion and composer button radius with DESIGN.md; tolerate unreadable staging revision state ... - Message entry: 300/420ms power3.out -> Standard 180ms cubic-bezier(.22,1,.36,1) (DESIGN.md section 6); update the layout contract test to the shipped values. - Composer icon button: full radius instead of 8px (DESIGN.md section 5 Button). - Staging deploy workflow: fall back to container SHA discovery when .state/deployed-revision exists but is unreadable by the deploy user (Gitea pipeline writes it as root).	2026-08-14 09:13:57 +08:00
Jesse_Chen	200c39d22b	feat: refine session conversation UI	2026-07-22 18:04:56 +08:00