10 Commits

Include renames

Author	SHA1	Message	Date
Jesse_ChenandCursor	8ed6118b9a	fix(web): persist uncertain birth time as a start/end clock window ... Users pick a clock range instead of a coarse period plus notes, so rectification and window consult scan that range instead of a leftover afternoon bucket. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-22 20:48:01 +08:00
Jesse_ChenandCursor	a6d4473ef0	feat(onboarding): write a question for every consultation domain and stop generating an unread greeting ... The home screen renders all ten domains from the consultation registry, but the Agent only ever wrote three of them; the other seven were static registry prompts dressed up as personalized starting points. The payload now has to cover every domain in registry order, validated as a set rather than per item, so a short or misordered answer is rejected whole instead of silently leaving cards on static copy. The greeting went the other way. Nothing has rendered it since the hero note was removed, so it leaves the schema, the prompt, and the client contract rather than costing tokens for text no one reads. Ten questions take much longer to generate than three, so the route, the server generation budget, and the client request deadline all grow together, and the cache version bump forces existing payloads to be regenerated once under the new shape. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-18 15:44:19 +08:00
Jesse_ChenandCursor	a12f57970b	fix(home): request the daily card on the same condition that renders it ... The daily starlanguage card sat on "正在结合你的星盘写今天的星语。" forever for every account whose birth time was usable. Its effect bailed out on birthTimeDisplayState(profile), which returns a value precisely when the birth time is candidate, accepted or confirmed, so the request went out only for accounts that had nothing to read. The guard predates the Agent rewrite and was masked by the written-in client fallback that rewrite deleted. It now gates on personalChartAvailable, the same fact the card uses to render personal content, and retries once before admitting that today has no card. The route stops letting one engine call take the whole card down silently: /api/chart fails into a named reason like the other four layers, and the engine and agent budgets leave room for a cold chart and an observed 30s generation inside the 60s ceiling. The home also had three greeting implementations. The hero heading drew from a static pool while the time-aware greeting lived elsewhere and the Agent's own greeting was overwritten client-side into a field nothing rendered. createStartGreeting now exposes its salutation and question halves, the hero uses both, and the served greeting reaches the hero note. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-18 12:00:53 +08:00
Jesse_Chen	f25aad526c	merge: synchronize remote main	2026-07-21 22:57:50 +08:00
732642856	a69e24461f	fix: stabilize e2e context and onboarding themes	2026-07-21 22:35:13 +08:00
Jesse_Chen	bfc6870614	feat: complete verifiable birth-time rectification flow	2026-07-21 22:16:18 +08:00
Jesse_Chen	308e5d532a	fix: scope onboarding fallback greeting	2026-07-19 21:59:43 +08:00
Jesse_Chen	5ee925cd1e	fix: bind onboarding greeting to profile	2026-07-19 21:50:52 +08:00
Jesse_Chen	28d58d4b6f	fix: reject stale onboarding recovery	2026-07-19 21:38:58 +08:00
Jesse_Chen	6a34a843ec	fix: recover slow personalized starters	2026-07-19 21:21:58 +08:00