Jyotisha

2,942 Commits 77 Branches 0 Tags

3 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	84eb23152a	feat(rectification): remove the rectification regenerate button and endpoint (BUG-1056) T2 of TASK-rectification-grounding-20260927 (product decision P1). The rectification 「重试（重新生成）」 was a blind agent.generate rewrite that persisted unchecked text (invented range / fit rate reproduced). Removed: the regenerate route, regenerate-turn.ts, the regeneration agent and its read-only tool set, the client regenerate action/state and the regenerating/canRegenerate props. ChatMessageActions renders the regenerate button only when onRegenerate is passed; ordinary consultation is unchanged. The DB function regenerate_agentic_rectification_turn is kept (AGENTS §7.6, retire in a later round). DESIGN.md / VOICE.md updated; source-contract tests follow with 原值/新值/原因 notes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8	2026-09-27 03:28:27 +08:00
jesse-ux	9da42c99d2	fix(rectification): keep tied-first from delivering while probes remain (BUG-683/684) Independent Staging Quality Gate / validate (push) Successful in 13m48s Details Independent Staging Quality Gate / publish (push) Successful in 2m6s Details tied_first is only terminal when there is no dated probe and targeted collect is exhausted. An unnarrowed opening window cannot announce adopt. Delivered dead choice cards take the delivered gap instead of the repair copy.	2026-09-14 17:06:51 +08:00

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

84eb23152a

feat(rectification): remove the rectification regenerate button and endpoint (BUG-1056)

T2 of TASK-rectification-grounding-20260927 (product decision P1).
The rectification 「重试（重新生成）」 was a blind agent.generate rewrite that
persisted unchecked text (invented range / fit rate reproduced). Removed:
the regenerate route, regenerate-turn.ts, the regeneration agent and its
read-only tool set, the client regenerate action/state and the
regenerating/canRegenerate props. ChatMessageActions renders the regenerate
button only when onRegenerate is passed; ordinary consultation is unchanged.
The DB function regenerate_agentic_rectification_turn is kept (AGENTS §7.6,
retire in a later round). DESIGN.md / VOICE.md updated; source-contract
tests follow with 原值/新值/原因 notes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8

2026-09-27 03:28:27 +08:00

jesse-ux

9da42c99d2

fix(rectification): keep tied-first from delivering while probes remain (BUG-683/684)

Independent Staging Quality Gate / validate (push) Successful in 13m48s

Details

Independent Staging Quality Gate / publish (push) Successful in 2m6s

Details

tied_first is only terminal when there is no dated probe and targeted collect is exhausted. An unnarrowed opening window cannot announce adopt. Delivered dead choice cards take the delivered gap instead of the repair copy.

2026-09-14 17:06:51 +08:00