5 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	fc811d2c39	refactor(home): drop the redundant hero note and move the birth-time boundary to the topics ... The hero carried three lines saying the same thing: a salutation, a question, and an Agent greeting that repeated both. Removing the third line would also have removed the only place where accounts without a usable birth minute are told that unsupported claims will be disclosed, so that sentence moves to the topic section subheading, where the reader is about to pick a question. The starter loading copy claimed three starting points while the page renders every domain in the registry, only three of which the Agent writes. 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_ChenandCursor	f6715ee4bf	feat(home): write the daily card with the Agent and vary the starter heading ... The daily starlanguage card claimed to be personal but was a four-card rotation picked by hashing the date and birth place, with the same pool duplicated as a client fallback. It now collects chart, Vimshottari and Narayana dasha, D9/D10 and today's transits, hands that evidence to a dedicated Agent, and keeps the result per account per day in process. A failed generation says so instead of printing generic advice. The starter heading is drawn from a pool on each visit, and the rectification card drops its fine print. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-17 22:27:49 +08:00
Jesse_Chen	308e5d532a	fix: scope onboarding fallback greeting	2026-07-19 21:59:43 +08:00