4 Commits

Include renames

Author	SHA1	Message	Date
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