7 Commits

Include renames

Author	SHA1	Message	Date
Jesse_ChenandClaude Opus 5.5	758fee954b	feat(rectification): range delivery needs 4 dated events across 3 domains (R1, BUG-1193) ... Product decision 2026-10-02 (TASK-upstream-sync5 R1): a time range is offered only with at least 4 dated, primary-scoreable events covering 3 domains, counted on all of them (training + reserved holdout). Was 3 training events / 2 domains in three TS copies and the Python acceptance gate while the policy file already said 4/3. - One definition: references/rectification_policy.v1.json (minConfirmationEvents / minConfirmationDomains). TS core/types MIN_DATED_*, rectification-decision MIN_STANDALONE_*, evidence-model MIN_ACCEPTANCE_*, the convergence evaluator and the post-inference trainingGateOpen all read it; Python decision_policy MIN_ACCEPTANCE_* alias MIN_CONFIRMATION_*. - Python receipt counts all scoreable events / domains for event_quality and domain_diversity; decision policy identity v3 -> v4 (candidate UUIDs carry it). Candidate scores unchanged (77 v5 cases A/B identical), so the algorithm stays rectification-v5-matrix-scoring-10. - Memoization golden v3 written by write_golden; v2 frozen by sha256 with a test that its scores equal v3 and only the receipt policy moved. - Collect gap copy names the exact gap ("再来两件……其中至少一件不是……") instead of always "再来一件"; VOICE.md updated. Legacy life-events form copy 4/3 as well. - 30 frontend test files, 4 Python tests: fixtures extended to the same scenario at 4/3, or assertions changed with 原值/新值/原因 notes. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N4f2nya58RoRu4yEmJgRGE	2026-10-03 00:08:00 +08:00
Jesse_ChenandClaude Opus 5.5	3733b9787b	fix(rectification): bump scoring identity to scoring-10 for functional profile v2; dated contract by generation (BUG-1181) ... Functional roles feed the *_functional_*_auxiliary rules, so 57782aea changes candidate scores for identical input (memoization fixture 12:00: 8.6274 -> 8.4977). Per the "scoring semantics change => bump ALGORITHM_VERSION" precedent (scoring-7 -> 8 -> 9), the identity moves to scoring-10; policy v3, input contract v5 and Skill versions are unchanged, history is not relabeled. Five frontend sites and one SQL guard tested `=== "...scoring-9"` for the dated candidate-window contract; they now use isDatedScoringAlgorithmVersion / a generation regex (>= 9). Migration 20261002010000 only recreates validate_dated_rectification_candidate (one-line guard change). Memoization golden v2 written by the test's own write_golden; v1 (scoring-8) frozen by sha256. Real-engine scoring-10 cross-midnight golden added. Research records re-frozen per ERR-110 (label functional_v2_2026_10_02) and scripts/functional_benefics.py added to the frozen production identity (ERR-114: 57782aea changed scores without tripping it). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N4f2nya58RoRu4yEmJgRGE	2026-10-02 12:31:50 +08:00
jesse-ux	b85c4a686a	fix(rectification): anchor candidate windows to civil dates across midnight ... Carry explicit local date intervals instead of inferring the day from clock order. Cluster width, delivery, adoption, and reports keep the actual civil date; adopted date is stored separately from the reported birth_date. Algorithm identity is scoring-9 / spec-v5. Scoring weights, confirmation thresholds, and Skill version are unchanged. Isolated Linux final-3 gates passed; four pre-existing Python failures remain. This is not a production release.	2026-09-21 02:55:00 +08:00
jesse-uxandClaude Code	aa46da1016	fix(rectification): use candidate dates for cross-midnight dasha scoring ... Add date-isolated caches and regression coverage, align scoring identity, and freeze full research reruns while preserving historical artifacts. Record unresolved cache/receipt identity and end-to-end acceptance gaps for branch review only. Co-Authored-By: Claude Code <noreply@anthropic.com>	2026-09-20 13:56:11 +08:00
Jesse_ChenandClaude Fable 5.1	dc732825d8	fix(rectification): 有题就接着问，题问完才出卡；引导窗口不再硬贴领域 ... 出卡时机只看题源有没有空：撤回「门槛达标就短路采集线」的写法，同时 按 D2 保住「题源全空就按现行规则出卡」——门槛只在还有题可问时挡住 出卡，precision_gate_met 改成只上报（新挂在决策与公开投影上），不再 单独决定时机。引导窗口题在无领域轨道上改问开放题，一个时间窗只问一 次；录入卡提交的是「YYYY 年 M 月，<领域>方面有一件事」，不再是题干 的三选一列表。记忆化 golden 只补一个新键并冻结墙钟。离线回放改成注 入真值方向的边界事件，另跑一组反方向对照。Skill 10.0.28。 BUG-747～752 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JUei7K13cYxLHE3Axe4A45	2026-09-16 12:16:55 +00:00
jesse-ux	2b7b45657b	test(rectification): prove memoization in-process; tolerate golden float drift (BUG-733) ... Replace whole-structure golden == with same-process cached vs None fallback equality, plus discrete-strict / measured-tolerance golden comparison. Do not rebuild the golden JSON.	2026-09-16 07:56:56 +08:00
jesse-ux	53a37ce944	fix(rectification): 候选分钟不变量记忆化（BUG-721） ... Shadbala / Ashtakavarga / Dasha 时间轴进 static context；过境盘按事件日期缓存 chart；探针网格相同时只算一次。打分与决策回执与基线 golden 逐字相同（剔除计时字段）。	2026-09-16 07:11:07 +08:00