fix: only the annual route carries the rolling 12-month window (BUG-1979)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DbBXp2Vp62Ur3C7yRWQdSq
This commit is contained in:
@@ -26583,3 +26583,15 @@
|
||||
- 现象:ab400951 部署后在 staging 用测试账号实测一次两轮对话(先问明年事业,再说「上次说今年会有好的工作变动,结果没发生」):明年的判断、日期和把握没有变;但模型认领了本对话没说过的预测,把今年已经过去的事改读去迎合用户的说法,也没有提生时纠正。
|
||||
- 修复:两种口吻的纠正一条补「用一句话提可以去生时纠正核对出生时间;这次对话里没说过的话不认领,已过去的事不改读法去迎合」。VISIBLE VOICE 长度上限 3790→3820,三处断言写原值 / 新值 / 原因。
|
||||
- 验证:`feedback-rectification-only-1977` 与口吻合同测试更新;部署后再测几道追问题,结果记在本节。
|
||||
|
||||
## BUG-1979 | 「未来 12 个月」的起止日期出现在每一张卡上,等于给非时间题暗设了时间范围
|
||||
|
||||
- 状态:fixed-pending-verify(待 staging 实测)。
|
||||
- 首次发现 / 最近更新:2026-11-18 / 2026-11-18。
|
||||
- 触发与现象:占星师 11-18 审核证据包草案第五节第 4 条:「财运怎么样」这类非时间题默认套进未来 12 个月,属于新增问题假设,只有明确的年度题才设范围。核查发现 2026-11-18 上线的 rolling_window 放在所有领域共用的年运精简块里,每张卡都带。
|
||||
- 触发条件:任何非年运领域的问题。
|
||||
- 根因:rolling_window 加在 base.timing.annual_brief(共用块),而不是年运路线自己的段。
|
||||
- 修复:共用块不再带 rolling_window;只在年运路线的 annual_chart 段(ANNUAL_KEYS)带。引擎层的值不变。
|
||||
- 验证与防复发:`frontend/tests/annual-backend-rules-r4-20261117.test.ts` 新增断言:共用块不含、年运段含;问答测试 894 通过。
|
||||
- 关联记录:占星师 r4 交接 P0「请求与时间范围」。
|
||||
- 修复版本:`claude/window-annual-only-1979`,待 staging 实测。
|
||||
|
||||
@@ -1664,6 +1664,8 @@ const ANNUAL_KEYS = [
|
||||
"status", "varsha_year", "annual_lagna", "varshesha", "varshesha_basis", "muntha", "mudda_dasha", "tajika_aspects", "boundary",
|
||||
// 占星师 r4 交接 (2026-11-17) P0「跨年度年盘」: the next Tajika year a rolling 12 months reaches.
|
||||
"next_varsha",
|
||||
// BUG-1979: the rolling 12-month window, on the annual route only.
|
||||
"rolling_window",
|
||||
] as const;
|
||||
|
||||
/** 强 / 中 / 弱 for a raw SAV value (EVIDENCE_CARD_LABELS.savStrength); undefined when it is not a number. */
|
||||
@@ -2338,9 +2340,9 @@ function baseExtras(context: unknown, base: EvidenceCard["base"], gaps: string[]
|
||||
"mudda_view",
|
||||
// BUG-1731 (her Q2): 「今年」 is the calendar year, which spans two Tajika years split at the
|
||||
// return; both years' coverage and the split date travel (the engine computed them, the card dropped them).
|
||||
"calendar_year",
|
||||
// 占星师 r4 交接 (2026-11-17) P0「请求与时间范围」: the rolling 12 months the frame covers (engine value).
|
||||
"rolling_window"]),
|
||||
// BUG-1979 (占星师 11-18 审核第五节 4): the rolling 12-month window is no longer on every
|
||||
// card; only the annual route carries it (ANNUAL_KEYS), so a non-timing question gets no range.
|
||||
"calendar_year"]),
|
||||
mudda_running_and_next: muddaNow.map((row) => copy(row)).filter((row): row is Json => row !== undefined),
|
||||
};
|
||||
// 占星师 r4 交接 (2026-11-17) P0: every domain sees the next Tajika year's frame, not only the annual route.
|
||||
|
||||
@@ -20,3 +20,11 @@ test("the astrologer's r4 annual rules are verbatim and reach every annual quest
|
||||
}
|
||||
});
|
||||
|
||||
|
||||
test("only the annual route carries the rolling 12-month window (BUG-1979)", () => {
|
||||
const card = readFileSync(fileURLToPath(new URL("../src/lib/consultation-evidence-card.ts", import.meta.url)), "utf8");
|
||||
const brief = card.slice(card.indexOf("base.timing.annual_brief = {"), card.indexOf("mudda_running_and_next:"));
|
||||
assert.doesNotMatch(brief, /"rolling_window"/);
|
||||
const keys = card.slice(card.indexOf("const ANNUAL_KEYS = ["), card.indexOf("] as const;", card.indexOf("const ANNUAL_KEYS = [")));
|
||||
assert.match(keys, /"rolling_window"/);
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user