6 Commits

Include renames

Author	SHA1	Message	Date
Jesse_ChenandCursor	649ba32034	fix(home): send starter cards instead of filling the composer ... Clicking today's reading or a topic card should open a consultation and wait for the model, not leave the question in the input box. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-21 22:02:40 +08:00
Jesse_ChenandCursor	6a0394aa57	fix(web): update consult source contracts for the declared-window path ... BUG-341 added a third agentic consultation stream and renamed the homepage draft entrypoint, but the exact-count contracts still described two paths, so staging validate failed before publish. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-21 17:59:07 +08:00
Jesse_ChenandCursor	d434aa48ab	test(consult): lock the restoreOnFailure composer draft contract ... BUG-306 changed the persist-failure restore guard. Keep the source-level slice aligned so the staging quality gate still passes. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-19 20:37:09 +08:00
Jesse_ChenandCursor	188cff99ec	fix(consult): replay an unstarted consultation after refresh ... Sending cleared the draft and stored a request id before the server reserved usage, so a refresh left a sent question with no agent run. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-18 17:35:15 +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_ChenandCursor	e8d201dd9a	perf(chat): isolate the composer, split heavy chunks, fix dead tokens ... Second batch from the staging UX audit (BUG-248..253). - css: expose the 32 palette tokens through @theme. Seven utilities including text-ink, text-danger and text-warning compiled to no CSS at all, so 30 call sites had been silently inert (BUG-248) - chat: move the composer into its own component behind a draft store, so a keystroke no longer re-renders a 2723-line component, and persist the draft across reloads (BUG-249) - chat: load gsap, react-markdown and thinking-orbs on demand. First Load JS for / drops 549.5 kB to 476.3 kB gzipped (BUG-250) - chat: route the five in-app destinations through router.push, and keep the five auth redirects and the bootstrap retry as hard loads on purpose (BUG-251) - a11y: announce reply completion, and move the live region out of the aria-busy subtree that was likely suppressing even the start announcement (BUG-252) - docs: give the 27 collided bug ids unique numbers and repair their inbound references; require search rather than a full read of a 3690-line file (BUG-253) Verified: tsc, eslint, next build, and 1592 assertions across the 199 non-database test files. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-17 14:16:05 +08:00