diff --git a/docs/BUG_HISTORY.md b/docs/BUG_HISTORY.md
index 05cbdbd74..73d11fa18 100644
--- a/docs/BUG_HISTORY.md
+++ b/docs/BUG_HISTORY.md
@@ -28819,3 +28819,22 @@
- 按占星师方案重做比较与提问流程另开。
- 关联记录:BUG-1971、BUG-1997、BUG-2115。
- 修复版本:`claude/rect-structure-only-2132`。
+
+## BUG-2133 | 问答回答和「判断依据」里引书名、作者、页码
+
+- 状态:fixed-pending-verify
+- 现象:问答回答的「判断依据」常写「B. V. Raman《How to Judge a Horoscope》第 2 卷 p.11 说:……」「据《BPHS》第 24 章」「按 Sanjay Rath 来源版」「木星在 PVR 表为功能凶星」「达 BPHS 最低要求」「(§§10.5–10.7)」;在已存的 558 份问答回答里,409 份的判断依据有这类引文,共 547 行。
+- 触发条件:证据卡带 classical_texts 时,系统提示要求「写书名和它的大意」,证据卡说明要求「cite them by book name in 「## 判断依据」」;问答的用词检查把书名当作正常内容保留,改写提示也写明「书名照原样保留」。
+- 根因:产品负责人 2026-11-21 决定问答也不引书名(与报告 BUG-2130 同一口径:带作者名的方法名只留在报告资料章节),此前的问答规则是 2026-11-16 定的「按书名引用」。
+- 修复:
+ - 写作规则:`frontend/src/mastra/product-voice.ts` 的判断依据规则改为 classical_texts 只写大意、前面写「传统说法:」,正文和判断依据都不引书名、作者、表号、章节和页码;`references/product_runtime_contract.md` 证据卡说明同步改写,并加产品公告 G-14。
+ - 检查:`frontend/src/lib/consultation-internal-words.ts` 的内部用词检查把出处(`citationSpans`)算作新的一类 `citation`;判断依据里带出处的行进入现有的一次改写,改写提示不再说「书名照原样保留」,改不干净的由词表按 `withoutChatCitations` 去掉。用户这一轮自己写的书名不算(`scanInternalWords(answer, { userText })`,路由传 `visibleQuestion`)。
+ - 显示:`parseJudgmentBasisItems` 和判断依据的 markdown 兜底都先过 `withoutChatCitations`,已存的回答也不再显示出处;「解读依据」末行的「资料库分析」判断(`answerUsedBookLibrary`)同时认「传统说法:」。
+ - 共用模块 `frontend/src/lib/report-citations.ts` 新增 `withoutBookCitations` / `withoutChatCitations` / `citationSpans`;`表` 后面跟日期(「双过境表 2027-02-05」)不再算表号,含日期的括号不会被当作出处删掉(报告侧同样受益);补了「Sanjay Rath 来源版」「PVR 表」(无编号)「BPHS 最低要求」三种写法。
+ - 证据包里落陷取消那一句(`frontend/src/lib/evidence-pack.ts`)去掉「按《Light on Life》规则」,与报告侧 BUG-2129 一致;规则编号 light_on_life_p295 留在后台。
+- 验证:新增 `frontend/tests/chat-no-citations-2133.test.ts`;`consult-internal-words-1948`、`consult-internal-words-and-al-relation-1970`、`evidence-pack-cancel-1987`、`consult-classical-texts-20261116` 按原值 / 新值 / 原因更新。已存的 558 份回答过显示层后,判断依据里带出处的行 547 → 0,非出处的数字(日期、度数、分值)一个不少。
+- 防复发:出处检查和显示清理共用 `report-citations.ts`;问答、报告、提问回答同一套词。
+- 未覆盖:回答正文的出处只靠规则和检查(检查只报告、不改正文),显示层只清理判断依据;已存回答里正文带出处的有 23 行。报告渲染侧 `scripts/report_render/opening_guide.py` 第 365 / 376 行仍写「按《Light on Life》的规则」(生时纠正窗口的范围)。
+- 关联记录:BUG-2130、BUG-2129、BUG-1948、BUG-2016、BUG-1926。
+- 修复版本:`claude/chat-no-citations-2133`。
+
diff --git a/frontend/src/app/api/consult/route.ts b/frontend/src/app/api/consult/route.ts
index bddf9a06a..65009e38b 100644
--- a/frontend/src/app/api/consult/route.ts
+++ b/frontend/src/app/api/consult/route.ts
@@ -1853,6 +1853,8 @@ export async function POST(request: Request) {
continueForMissingSection,
regenerateFactSentences: consultEntrypoint === "daily_starlanguage" ? undefined : regenerateFactSentences,
rewriteInternalWordLines: consultEntrypoint === "daily_starlanguage" ? undefined : rewriteInternalWordLines,
+ // BUG-2133: a book the user named in the question may be named back in the answer.
+ userText: visibleQuestion,
// BUG-1763: a missing audit table (professional) or missing audit evidence (both modes) fails acceptance.
acceptAnswer: (output: string) => (consultEntrypoint === "daily_starlanguage"
? null
diff --git a/frontend/src/components/chat-message-content.tsx b/frontend/src/components/chat-message-content.tsx
index ecf712305..6b2cb4e4d 100644
--- a/frontend/src/components/chat-message-content.tsx
+++ b/frontend/src/components/chat-message-content.tsx
@@ -8,6 +8,7 @@ import { ConsultChartDataFold } from "@/components/consult-chart-data";
import { ConsultJudgmentBasis } from "@/components/consult-judgment-basis";
import type { ConsultChartData } from "@/lib/consult-chart-data";
import { splitJudgmentBasis } from "@/lib/consult-judgment-basis";
+import { withoutChatCitations } from "@/lib/report-citations";
import {
answerUsedBookLibrary,
consultScopeLine,
@@ -183,7 +184,7 @@ export function ChatMessageContent({
{report ?
{reportBody}
: foldedAudit}
{judgment.basis ? (
-
+
) : null}
{!streaming && chartData ? : null}
diff --git a/frontend/src/lib/consult-answer-basis.ts b/frontend/src/lib/consult-answer-basis.ts
index ab1ca4d1e..c311d5519 100644
--- a/frontend/src/lib/consult-answer-basis.ts
+++ b/frontend/src/lib/consult-answer-basis.ts
@@ -40,9 +40,12 @@ export function consultScopeLine(usedLibrary: boolean): string {
return usedLibrary ? CONSULT_SCOPE_LINE_WITH_LIBRARY : CONSULT_SCOPE_LINE;
}
-/** A book cited in 「判断依据」 is the library's (classical_texts come only from it). */
+/**
+ * A book cited in 「判断依据」 is the library's (classical_texts come only from it).
+ * BUG-2133: answers no longer name the book; a classical passage is written after 「传统说法:」, which counts too.
+ */
export function answerUsedBookLibrary(judgmentBasis: string | null | undefined): boolean {
- return /《[^》\n]+》/.test(judgmentBasis ?? "");
+ return /《[^》\n]+》|传统说法[::]/.test(judgmentBasis ?? "");
}
/**
diff --git a/frontend/src/lib/consult-judgment-basis.ts b/frontend/src/lib/consult-judgment-basis.ts
index 83348a6bd..28c46f6ae 100644
--- a/frontend/src/lib/consult-judgment-basis.ts
+++ b/frontend/src/lib/consult-judgment-basis.ts
@@ -4,6 +4,8 @@
* judgment with the chart facts and the grade. The page shows the body and
* folds this section.
*/
+import { CLASSICAL_GIST_LEAD, withoutChatCitations } from "./report-citations.ts";
+
export const CONSULT_JUDGMENT_BASIS_TITLE = "判断依据";
const HEADING_RE = /^#{2,3}[ \t]*判断依据[ \t]*$/m;
@@ -146,7 +148,12 @@ export function parseJudgmentBasisItems(basis: string): JudgmentBasisItem[] | nu
rest = rest.slice(0, noteMatch.index);
}
}
- const facts = basisSentences(rest.replace(/\*\*|`/g, "")).map((text) => ({ text, book: text.includes("《") }));
+ // BUG-2133: shown without book titles, authors, tables, chapters and pages (stored answers too); a classical
+ // passage keeps its gist after 「传统说法:」 and is still marked as the book line.
+ const facts = basisSentences(withoutChatCitations(rest.replace(/\*\*|`/g, ""))).map((text) => ({
+ text,
+ book: text.includes("《") || text.startsWith(CLASSICAL_GIST_LEAD),
+ }));
items.push({ title: lead[1].replace(/[::]\s*$/, "").trim(), facts, grade, note });
}
return items;
diff --git a/frontend/src/lib/consultation-internal-words.ts b/frontend/src/lib/consultation-internal-words.ts
index 72eae70ba..518ddbeea 100644
--- a/frontend/src/lib/consultation-internal-words.ts
+++ b/frontend/src/lib/consultation-internal-words.ts
@@ -1,3 +1,4 @@
+import { CLASSICAL_GIST_LEAD, citationHits, citationSpans, withoutChatCitations } from "./report-citations.ts";
import { EVIDENCE_ID_PATTERN, EVIDENCE_ID_PREFIX, LOGICAL_KEY_PREFIX } from "./evidence-ids.ts";
import { splitJudgmentBasis } from "./consult-judgment-basis.ts";
import { FACT_STATUS_LABELS } from "./report-fact-table-display.ts";
@@ -150,7 +151,7 @@ const FRAGMENT_RE = new RegExp(
/** BUG-1970: a lowercase field name with a boolean value, as the card writes it (「combust: true」). */
const BOOLEAN_FRAGMENT_RE = /`?(? a.start - b.start);
+ // BUG-2133 (产品负责人 2026-11-21): book titles, authors, tables, chapters and pages are not shown with an
+ // answer either. A citation replaces any other hit inside it (「Raman」 is not also an English word).
+ const citations = citationSpans(text);
+ if (!citations.length) return hits.sort((a, b) => a.start - b.start);
+ return [
+ ...hits.filter((hit) => !citations.some((span) => hit.start < span.end && hit.end > span.start)),
+ ...citations.map((span) => ({ ...span, kind: "citation" as const })),
+ ].sort((a, b) => a.start - b.start);
}
/** BUG-2042: a line written in English is scanned for the English table only (never rewritten into Chinese). */
@@ -439,9 +447,12 @@ export type InternalWordScan = {
bodyTokens: string[];
};
-export function scanInternalWords(answer: string): InternalWordScan {
+export function scanInternalWords(answer: string, options: { userText?: string } = {}): InternalWordScan {
const { body, basis } = splitJudgmentBasis(answer);
- const bodyTokens = findInternalWords(body).map((hit) => hit.token);
+ // BUG-2133: a citation the user wrote in the question may be answered with its name.
+ const userText = options.userText ?? "";
+ const keep = (hit: InternalWordHit) => !(hit.kind === "citation" && userText.includes(hit.token));
+ const bodyTokens = findInternalWords(body).filter(keep).map((hit) => hit.token);
if (basis === null) return { units: [], bodyTokens };
const base = answer.lastIndexOf(basis);
const units: InternalWordUnit[] = [];
@@ -452,7 +463,7 @@ export function scanInternalWords(answer: string): InternalWordScan {
const english = !(latin > 80 && han < latin * 0.2);
for (const line of basis.split("\n")) {
// BUG-1972: English words are looked for in 「判断依据」 only; the body report is unchanged.
- const tokens = findInternalWords(line, { english, englishAnswer: !english }).map((hit) => hit.token);
+ const tokens = findInternalWords(line, { english, englishAnswer: !english }).filter(keep).map((hit) => hit.token);
if (tokens.length) units.push({ id: units.length + 1, start: base + cursor, end: base + cursor + line.length, text: line, tokens: [...new Set(tokens)] });
cursor += line.length + 1;
}
@@ -466,6 +477,10 @@ function wordMeanings(units: readonly InternalWordUnit[]): string[] {
for (const token of units.flatMap((unit) => unit.tokens)) {
if (seen.has(token)) continue;
seen.add(token);
+ if (citationHits(token).length) {
+ lines.push(`${token}:书名、作者、表号、章节或页码,去掉;这条传统说法只留它的大意,写成「${CLASSICAL_GIST_LEAD}……」`);
+ continue;
+ }
if (META_CLAUSE_RE.test(token) && !(token in INTERNAL_CHINESE_PHRASES) && !(token in BASIS_ONLY_WORDS)) {
lines.push(`${token}:写给作者的说明,连同它所在的半句一起去掉`);
continue;
@@ -519,7 +534,8 @@ export function internalWordRepairPrompt(units: readonly InternalWordUnit[]): st
return [
"下面几行来自一份星盘解读的「判断依据」,里面带着内部字段名或英文状态码,读的人看不懂。把每一行改写一遍:",
"- 只把列出的那几个词换成给出的中文说法;标着没有实际意思的,连同它所在的空括号或半句一起去掉。",
- "- 其余内容一个字不改:星、星座、宫、度数、日期、分盘和技法的名称、书名、行尾的等级标注都照原样保留。",
+ "- 其余内容一个字不改:星、星座、宫、度数、日期、分盘和技法的名称、行尾的等级标注都照原样保留。",
+ `- 书名、作者、表号、章节和页码一律去掉(BUG-2133);古书的说法只留大意,前面写「${CLASSICAL_GIST_LEAD}」。`,
"- 每行仍是一行,行首的「- **……**」照原样保留;不新增判断,不新增依据。",
"- 只输出 JSON 数组:[{\"id\": 1, \"text\": \"改写后的整行\"}],不要别的文字。",
"",
@@ -575,7 +591,8 @@ export function scrubInternalWords(line: string): string {
return `${before}${lead}${word}${tail}${after}`;
};
// BUG-1976: evidence ids go first, with the separators around them. BUG-2041: then copied writing instructions.
- let text = dropMetaClauses(dropEvidenceIds(line));
+ // BUG-2133: book leads become 「传统说法:」 and report-style citations go before the word table runs.
+ let text = withoutChatCitations(dropMetaClauses(dropEvidenceIds(line)));
for (const hit of findInternalWords(text).filter((item) => item.token.includes(": ")).reverse()) {
// A one-word key set to true names a chart term (「vargottama: true」 keeps 「vargottama」); any other
// fragment without a table row carries nothing for the reader.
@@ -588,6 +605,10 @@ export function scrubInternalWords(line: string): string {
text = splice(text, match.index, match.index + match[0].length, value ? `${INTERNAL_KEY_WORDS[match[1]!] ?? ""}${value}` : "");
}
for (const hit of findInternalWords(text, lineScanOptions(text)).reverse()) {
+ if (hit.kind === "citation") {
+ text = splice(text, hit.start, hit.end, "");
+ continue;
+ }
if (hit.kind === "evidence_id") {
// BUG-1976: an evidence id is dropped with the brackets or list separator around it.
text = splice(text, hit.start, hit.end, "");
diff --git a/frontend/src/lib/evidence-pack.ts b/frontend/src/lib/evidence-pack.ts
index fba0d2f39..5f45c75bd 100644
--- a/frontend/src/lib/evidence-pack.ts
+++ b/frontend/src/lib/evidence-pack.ts
@@ -238,7 +238,9 @@ export function cancellationSentence(edge: EvidenceEdge): string {
// BUG-2012(占星师 2026-11-19 第 3、12 条)。原值:「按落陷取消规则这一落陷已被取消…写成落陷但已被化解,
// 不写成弱」。新值:她给的统一说法:条件成立可以明确确认,但不等于入旺、困难不全部消失;取消只修饰
// 因落陷而来的不利判断,燃烧、其他受冲、功能凶性和该领域别的困难照旧。
- return `${name}本命${sign ? `在${sign}` : ""}落陷,按《Light on Life》规则,已满足落陷取消条件${conditions ? `:${conditions}` : ""}。`
+ // BUG-2133 原值「落陷,按《Light on Life》规则,已满足…」/ 新值「落陷,已满足…」/ 原因:产品负责人 2026-11-21 问答也不引书名
+ // (报告侧 BUG-2129 同样去掉了这个书名;规则编号 light_on_life_p295 留在后台)。
+ return `${name}本命${sign ? `在${sign}` : ""}落陷,已满足落陷取消条件${conditions ? `:${conditions}` : ""}。`
+ `这不等于${name}入旺,也不代表相关困难全部消失。`
// BUG-2030 原值「提到…时写成落陷、取消条件已满足」/ 新值:她 11-19 第二次答复给用户的说法 / 原因:规则口吻进了回答
+ `提到${name}时说成这一配置的不利影响有缓解因素,但不能据此认为困难全部消失;缓解只针对因落陷而来的那一项不利判断,${name}的落陷位置不变,`
diff --git a/frontend/src/lib/report-citations.ts b/frontend/src/lib/report-citations.ts
index 238ca77d6..d61041d74 100644
--- a/frontend/src/lib/report-citations.ts
+++ b/frontend/src/lib/report-citations.ts
@@ -8,7 +8,8 @@
* becomes 「传统划分」, 「Sanjay Rath 版」 becomes 「默认排法」, a parenthesis that only cites is dropped.
*/
-const TOKEN = String.raw`(?:p\.\s*\d|表\s*\d|Table\s*\d|第\s*\d+\s*[节章]|\bRath\b|\bPVR\b|\bBPHS\b|J\.S\.|原书|裁定|《)`;
+// BUG-2133: 「表」 then a date (「双过境表 2027-02-05」) is not a table number; a parenthesis holding a date stays.
+const TOKEN = String.raw`(?:p\.\s*\d|表\s*\d(?!\d{3}-)|Table\s*\d|第\s*\d+\s*[节章]|\bRath\b|\bPVR\b|\bBPHS\b|J\.S\.|原书|裁定|《)`;
const INNER = String.raw`(?:[^()()]|[((][^()()]*[))])`;
/** A parenthesis (one nested level allowed) that carries a citation: 「(默认;按原书 p.43 正文(第七轮裁定))」. */
const CITATION_PAREN = new RegExp(String.raw`\s*[((]${INNER}*?${TOKEN}${INNER}*[))]`, "gu");
@@ -16,11 +17,15 @@ const CITATION_PAREN = new RegExp(String.raw`\s*[((]${INNER}*?${TOKEN}${INNER}
const CITATION_LEAD = /([((])\s*(?:按\s*)?(?:PVR|Rath|BPHS)\s*表\s*\d+(?:\.\d+)?\s*[,,;;]\s*/gu;
const CITATION_TAIL = /\s*[,,;;]\s*(?:按\s*)?(?:PVR|Rath|BPHS)\s*表\s*\d+(?:\.\d+)?(?=\s*[))])/gu;
const CITATION_WORDS: ReadonlyArray = [
- [/Sanjay\s+Rath\s*版/gu, "默认排法"],
+ [/Sanjay\s+Rath\s*(?:来源)?版/gu, "默认排法"],
[/Rath\s*版/gu, "默认排法"],
[/Rath\s*规则/gu, "传统规则"],
[/按\s*PVR\s*表\s*\d+(?:\.\d+)?/gu, "按传统划分"],
[/PVR\s*表\s*\d+(?:\.\d+)?/gu, "传统划分"],
+ // BUG-2133: the same citations without a number, as chat answers wrote them.
+ [/在\s*PVR\s*表(?:里|中)?为/gu, "按传统划分为"],
+ [/PVR\s*表/gu, "传统划分"],
+ [/BPHS\s*(?=最低)/gu, ""],
[/BPHS\s*例外表/gu, "另一套具名划分"],
// 「移植上游 PVR 30.4 太阳角距版」 → 「太阳角距版」 (a source version number, not a table).
[/(?:移植上游\s*)?PVR\s*\d+(?:\.\d+)?\s*/gu, ""],
@@ -55,7 +60,7 @@ const DETECT: ReadonlyArray = [
["Parashara", /\bParashara\b|帕拉沙拉/u],
["Raman", /\bB\.?\s*V\.?\s*Raman\b|\bRaman\b(?=\s*[《((]|\s*(?:书|版|的书))/u],
["书名号", /《[^》]{1,40}》/u],
- ["表号", /(?:^|[^代外图列])表\s*\d+/u],
+ ["表号", /(?:^|[^代外图列])表\s*\d+(?!\d*-\d)/u],
["页码", /\bp{1,2}\.\s*\d+/u],
["章节号", /第\s*\d+\s*[节章]|§\s*\d+/u],
["PDF", /\bPDF\b/u],
@@ -67,3 +72,67 @@ export function citationHits(text: string): string[] {
/** BUG-2130: the clause every report writer and in-report answer gets (model-visible). */
export const NO_CITATION_RULE = "不引书名、作者、表号、章节和页码(例如 PVR、Rath、BPHS、《……》、表 30、p.50、第 44 节):用的是哪种方法,就用白话说它怎么分、怎么算,例如「功能吉凶按这张盘上升星座的传统划分」;材料里的 source、rule_source 和出处一类字段只供后台追溯,不写出来。";
+
+/**
+ * BUG-2133 (产品负责人 2026-11-21「问答也不引书名」): the lead a chat answer used for a classical passage —
+ * 「B. V. Raman《How to Judge a Horoscope》说:」「据《BPHS》第 24 章,」 — becomes 「传统说法:」, so the gist
+ * stays and the book, author, chapter and page go. A title alone at the end of a line is dropped.
+ */
+export const CLASSICAL_GIST_LEAD = "传统说法:";
+const BOOK_LEAD = new RegExp(
+ String.raw`(?:据|按照?|依据|根据|引|照)?\s*(?:[A-Z][A-Za-z.’'-]*(?:\s+[A-Z][A-Za-z.’'-]*){0,3}\s*)?《[^》\n]{1,80}》`
+ + String.raw`(?:\s*(?:第\s*\d+\s*[卷章节]|p{1,2}\.\s*\d+(?:\s*[-–]\s*\d+)?|ch\.\s*\d+|vol\.\s*\d+|§\s*\d+))*`
+ + String.raw`\s*(?:的说法|的意思|一书|里|中|上)?\s*(?:说|认为|提到|写道|指出|记载|讲|谈到)?\s*(?:[::,,]\s*)?`,
+ "gu",
+);
+
+/** 「Raman 第 2 卷 p.371:」「Raman 书……一节说」: an author lead with no book brackets. */
+const AUTHOR_LEAD = /(?:B\.\s*V\.\s*)?\bRaman\b\s*(?:原书|书)?\s*(?:第\s*[\d一二三四五六七八九十]+\s*卷\s*)?(?:p{1,2}\.\s*\d+(?:\s*[-–]\s*\d+)?\s*)?[::]?(?!\s*《)/gu;
+/** A volume or page left right after the lead: 「传统说法:第二卷 p.246「…」讲:」. */
+const LEAD_LOCATOR = /(传统说法:)\s*(?:第\s*[\d一二三四五六七八九十]+\s*卷\s*)?(?:p{1,2}\.\s*\d+(?:\s*[-–]\s*\d+)?\s*)?/gu;
+/** A volume and page reference standing alone in a chat line. */
+const LOCATOR = /(?:第\s*[\d一二三四五六七八九十]+\s*卷\s*)?p{1,2}\.\s*\d+(?:\s*[-–]\s*\d+)?|§{1,2}\s*\d+(?:\.\d+)?(?:\s*[-–]\s*\d+(?:\.\d+)?)?/gu;
+
+export function withoutBookCitations(text: string): string {
+ if (!text || !/《|Raman|p{1,2}\.\s*\d|§/u.test(text)) return text;
+ const leads = text.replace(AUTHOR_LEAD, (match, offset: number, whole: string) =>
+ /^\s*[;;,,、))]/u.test(whole.slice(offset + match.length)) ? "" : CLASSICAL_GIST_LEAD);
+ const out = leads.replace(BOOK_LEAD, (match, offset: number, whole: string) => {
+ const rest = whole.slice(offset + match.length);
+ // Nothing follows, or a separator does: the title was a reference, not the lead of a passage; drop it.
+ if (/^\s*[;;,,、))]/u.test(rest) || !/[一-鿿A-Za-z0-9]/u.test(rest.split(/[\n。]/u)[0] ?? "")) return "";
+ return CLASSICAL_GIST_LEAD;
+ });
+ return out
+ .replace(LEAD_LOCATOR, "$1")
+ .replace(LOCATOR, "")
+ .replace(/书?第\s*(\d+)\s*宫主在第\s*(\d+)\s*宫一节(?:说|讲)?/gu, "第 $1 宫主在第 $2 宫,")
+ .replace(/[((]\s*传统说法[::]\s*[))]/gu, "")
+ // A lead with nothing after it (the passage was only a reference): drop it with the separator.
+ .replace(/传统说法:\s*(?:[;;,,、]\s*|$)/gmu, "")
+ .replace(new RegExp(`(${CLASSICAL_GIST_LEAD})(?:\\s*${CLASSICAL_GIST_LEAD})+`, "gu"), "$1")
+ .replace(/[((][\s,,、;;::]*(?:见|参见|参看|引自|出自)?[\s,,、;;::]*[))]/gu, "")
+ // A reference dropped between two separators leaves one: 「罗睺;《…》第 2 卷;Shadbala」 → 「罗睺;Shadbala」.
+ .replace(/([;;,,、::])[ \t]*[;;,,、]/gu, "$1")
+ .replace(/[ \t]{2,}/gu, " ");
+}
+
+/** BUG-2133: a chat line (answer body or 「判断依据」) without book leads and without report-style citations. */
+export function withoutChatCitations(text: string): string {
+ return withoutCitations(withoutBookCitations(text));
+}
+
+/** BUG-2133: where citations sit in a line, for the chat wording check (same words as `citationHits`). */
+export function citationSpans(text: string): Array<{ start: number; end: number; token: string }> {
+ const spans: Array<{ start: number; end: number; token: string }> = [];
+ for (const [, pattern] of DETECT) {
+ for (const match of text.matchAll(new RegExp(pattern.source, `${pattern.flags.replace("g", "")}g`))) {
+ const start = match.index ?? 0;
+ const token = match[0].replace(/^[^《\w§第表]+/u, "");
+ const from = start + (match[0].length - token.length);
+ if (!token || spans.some((span) => from < span.end && from + token.length > span.start)) continue;
+ spans.push({ start: from, end: from + token.length, token });
+ }
+ }
+ return spans.sort((a, b) => a.start - b.start);
+}
diff --git a/frontend/src/lib/stream-agent-response.ts b/frontend/src/lib/stream-agent-response.ts
index e84dee8ee..02fc870b1 100644
--- a/frontend/src/lib/stream-agent-response.ts
+++ b/frontend/src/lib/stream-agent-response.ts
@@ -391,6 +391,8 @@ type StreamAgentResponseOptions = EventOptions & {
* from the word table; absent, the table alone is used. Never fails the answer.
*/
rewriteInternalWordLines?: (units: InternalWordUnit[], output: string) => Promise;
+ /** BUG-2133: the user's own words this turn; a citation they wrote is not flagged in the answer. */
+ userText?: string;
/**
* The answer is the text of the loop's step(s) that end without a tool call
* (BUG-1053). Set for routes whose loop has tools: a step's text is held
@@ -1167,7 +1169,7 @@ export function streamAgentResponse(options: StreamAgentResponseOptions) {
*/
async function guardInternalWords(controller: ReadableStreamDefaultController | undefined) {
try {
- const scan = scanInternalWords(fullOutput);
+ const scan = scanInternalWords(fullOutput, { userText: options.userText });
if (!scan.units.length && !scan.bodyTokens.length) return;
let result = { output: fullOutput, found: 0, rewritten: 0, tabled: 0, remaining: 0 };
if (scan.units.length) {
diff --git a/frontend/src/mastra/product-voice.ts b/frontend/src/mastra/product-voice.ts
index 86f112a36..f81cb0e37 100644
--- a/frontend/src/mastra/product-voice.ts
+++ b/frontend/src/mastra/product-voice.ts
@@ -76,7 +76,7 @@ export const productConversationVoice = `VISIBLE VOICE
- 写给不懂占星的人:${PLAIN_TERMS}
- 用词:说人直接说母亲、父亲、伴侣、孩子、上司,讲原因时也写「和母亲之间」「父亲对你」,称呼后面不接别的字来代指这段关系;规则和卡上的字眼不照搬进回答,同一个形容词不在几段里反复当结论用;不用含糊的比喻和半截话代替判断,一句话要说出谁、怎么样、结果是什么,读的人能照原意复述出来。正文不加括号标注,依据性质只写在判断依据里。讲时间直接说日子(到 2027 年 5 月前)和这段时间会怎样,不写大运、小运、细运、Narayana 这些名字,也不交代哪套算法算不算确认,这些只进「判断依据」。
- 用户在问题里划了范围(只看哪些、不看哪些)时照他划的写;路线要求必查的其他层只在后台看。没用的部分说一句原因,和补什么信息就能加进来。
-- 全文最后写「## 判断依据」:正文每个主要判断一条,「- **判断短句**:盘面依据。(依据性质)」。依据写实际位置(星、星座、宫、度数、分盘、大运或行运的起止),这一节可以写技法和分盘的标准名。括号里只从这几样里选适用的,几样并写时用「;」隔开:几种方法一致、只有一种方法支持、出生时间稍有出入就会变、相关分盘还没核实、不同方法对这段时间说法不同;会改变结论的条件、适用的时间范围和方法分歧写进同一个括号,说成「出生时间早几分钟,这一条要换」这样。括号里不写别的说明,不写字母等级和英文标签。没用来下结论的技法、候选格局、定不下的层不列。卡上有 classical_texts 时,相关的判断引一条,写书名和它的大意。这一节不写表格、参数、技法清单和内部字段名;不讲盘的回答不写这一节。
+- 全文最后写「## 判断依据」:正文每个主要判断一条,「- **判断短句**:盘面依据。(依据性质)」。依据写实际位置(星、星座、宫、度数、分盘、大运或行运的起止),这一节可以写技法和分盘的标准名。括号里只从这几样里选适用的,几样并写时用「;」隔开:几种方法一致、只有一种方法支持、出生时间稍有出入就会变、相关分盘还没核实、不同方法对这段时间说法不同;会改变结论的条件、适用的时间范围和方法分歧写进同一个括号,说成「出生时间早几分钟,这一条要换」这样。括号里不写别的说明,不写字母等级和英文标签。没用来下结论的技法、候选格局、定不下的层不列。卡上有 classical_texts 时,相关判断写一条「传统说法:大意」;全文不引书名、作者、表号、章节和页码。这一节不写表格、参数、技法清单和内部字段名;不讲盘的回答不写这一节。
- 写成段落,段落之间空一行;标题、分节和列表按本轮指令里的骨架写,骨架没要的,一般问题不用标题。用户要几条(「给三条」)、或有三个以上候选时间窗时用列表,每条先一句做法、再一句为什么适合你。首轮通常三到六段,讲清楚为止;同一件事只说一遍。讲时间时最多三件天象或运期变化,由近到远。
- 结尾给两三件能去做的具体事,跟着前面的判断走;问时间的按时间段给,每段写起止和做什么。
- 读心不是每次都有:盘面和用户的问法都指向同一件心事时,答完之后才用「可能」「多半」说一句;拿不准就不写,用户要客观时不读;读别人的心要有盘上依据。不把用户的问题改写成「你其实想要的是……」。
diff --git a/frontend/tests/chat-no-citations-2133.test.ts b/frontend/tests/chat-no-citations-2133.test.ts
new file mode 100644
index 000000000..3f45a733c
--- /dev/null
+++ b/frontend/tests/chat-no-citations-2133.test.ts
@@ -0,0 +1,80 @@
+/**
+ * BUG-2133 (产品负责人 2026-11-21「问答也不引书名」): chat answers and their 「判断依据」 name no books, authors,
+ * tables, chapters or pages — the same rule BUG-2130 set for reports. A classical passage keeps its gist after
+ * 「传统说法:」. Stored answers are cleaned on display; a book the user named in the question is not flagged.
+ */
+import assert from "node:assert/strict";
+import { readFileSync } from "node:fs";
+import test from "node:test";
+
+import { answerUsedBookLibrary } from "../src/lib/consult-answer-basis.ts";
+import { parseJudgmentBasisItems, splitJudgmentBasis } from "../src/lib/consult-judgment-basis.ts";
+import { internalWordRepairPrompt, scanInternalWords, scrubInternalWords } from "../src/lib/consultation-internal-words.ts";
+import { CLASSICAL_GIST_LEAD, citationHits, withoutChatCitations } from "../src/lib/report-citations.ts";
+
+const ANSWER = [
+ "你的事业靠长期积累。",
+ "",
+ "## 判断依据",
+ "",
+ "- **事业稳步上升**:第 10 宫主火星落第 4 宫。B. V. Raman《How to Judge a Horoscope》说:第十宫主落第四宫的人事业与家庭相连。(几种方法一致)",
+ "- **财运**:第 2 宫主落第 11 宫;据《BPHS》第 24 章,二宫主落十一宫财富增长。(只有一种方法支持)",
+ "- **婚姻**:金星落第 7 宫(见《How to Judge a Horoscope》)。",
+].join("\n");
+
+test("book leads become 「传统说法:」, references drop, everything else stays", () => {
+ const cases: ReadonlyArray = [
+ ["B. V. Raman《How to Judge a Horoscope》说:第十宫主落第四宫的人事业与家庭相连。", `${CLASSICAL_GIST_LEAD}第十宫主落第四宫的人事业与家庭相连。`],
+ ["据《BPHS》第 24 章,二宫主落十一宫财富增长。", `${CLASSICAL_GIST_LEAD}二宫主落十一宫财富增长。`],
+ ["照《Phaladeepika》的说法,七宫有吉星婚姻和顺。", `${CLASSICAL_GIST_LEAD}七宫有吉星婚姻和顺。`],
+ ["金星落第 7 宫(见《How to Judge a Horoscope》)。", "金星落第 7 宫。"],
+ ["罗睺;B. V. Raman《How to Judge a Horoscope》第 2 卷;Shadbala 7.81 Rupa", "罗睺;Shadbala 7.81 Rupa"],
+ ["Narayana(Rath 版)白羊座大运;功能吉凶按 PVR 表 30。", "Narayana 白羊座大运;功能吉凶按传统划分。"],
+ ];
+ for (const [before, after] of cases) assert.equal(withoutChatCitations(before), after, before);
+ for (const fine of ["上升巨蟹,月亮在第 3 宫。(只有一种方法支持)", "你的表现会被看见。", "Rather than wait, take the path."]) {
+ assert.equal(withoutChatCitations(fine), fine);
+ assert.deepEqual(citationHits(fine), []);
+ }
+});
+
+test("stored answers show 「判断依据」 without citations, and the scope line still knows the library was used", () => {
+ const { basis } = splitJudgmentBasis(ANSWER);
+ const items = parseJudgmentBasisItems(basis!)!;
+ const shown = items.flatMap((item) => item.facts.map((fact) => fact.text)).join("\n");
+ assert.doesNotMatch(shown, /《|Raman|BPHS|第 24 章/u);
+ assert.match(shown, /传统说法:第十宫主落第四宫的人事业与家庭相连/u);
+ assert.ok(items[0]!.facts.some((fact) => fact.book && fact.text.startsWith(CLASSICAL_GIST_LEAD)));
+ // The fallback markdown path is cleaned the same way.
+ assert.doesNotMatch(withoutChatCitations(basis!), /《|BPHS/u);
+ // Old answers (book in the stored text) and new answers (「传统说法:」) both count as using the library.
+ assert.equal(answerUsedBookLibrary(basis), true);
+ assert.equal(answerUsedBookLibrary(`- **事业**:${CLASSICAL_GIST_LEAD}第十宫主落第四宫。`), true);
+ assert.equal(answerUsedBookLibrary("- **事业**:第 10 宫主落第 4 宫。"), false);
+});
+
+test("the wording check finds citations in 「判断依据」, the rewrite drops them, the table removes what is left", () => {
+ const scan = scanInternalWords(ANSWER);
+ assert.equal(scan.units.length, 3);
+ assert.ok(scan.units[0]!.tokens.includes("《How to Judge a Horoscope》"));
+ const prompt = internalWordRepairPrompt(scan.units);
+ assert.doesNotMatch(prompt, /分盘和技法的名称、书名、/u);
+ assert.match(prompt, /书名、作者、表号、章节和页码一律去掉/u);
+ for (const unit of scan.units) assert.doesNotMatch(scrubInternalWords(unit.text), /《|Raman|BPHS|第 24 章/u, unit.text);
+ // A book the user named in the question may be named back.
+ const asked = scanInternalWords(ANSWER, { userText: "《How to Judge a Horoscope》里怎么说我的第十宫?" });
+ assert.ok(!asked.units.some((unit) => unit.tokens.includes("《How to Judge a Horoscope》")));
+ assert.ok(asked.units.some((unit) => unit.tokens.includes("BPHS")));
+});
+
+test("the chat rule and the card description no longer ask for book names", () => {
+ const voice = readFileSync(new URL("../src/mastra/product-voice.ts", import.meta.url), "utf8");
+ assert.doesNotMatch(voice, /写书名和它的大意/u);
+ assert.match(voice, /相关判断写一条「传统说法:大意」;全文不引书名、作者、表号、章节和页码/u);
+ const contract = readFileSync(new URL("../../references/product_runtime_contract.md", import.meta.url), "utf8");
+ assert.doesNotMatch(contract, /cite them by book name/u);
+ assert.match(contract, /give their gist in 「## 判断依据」 after 「传统说法:」 without book, author or page/u);
+ assert.match(contract, /产品公告 G-14(BUG-2133/u);
+ const pack = readFileSync(new URL("../src/lib/evidence-pack.ts", import.meta.url), "utf8");
+ assert.doesNotMatch(pack, /return `[^`]*《Light on Life》/u);
+});
diff --git a/frontend/tests/consult-classical-texts-20261116.test.ts b/frontend/tests/consult-classical-texts-20261116.test.ts
index 6e57d402f..92644cd7e 100644
--- a/frontend/tests/consult-classical-texts-20261116.test.ts
+++ b/frontend/tests/consult-classical-texts-20261116.test.ts
@@ -199,7 +199,10 @@ test("a house two domains share carries its passages once", () => {
test("the system prompt says what the passages are and how to use them, in one sentence", () => {
const contract = readFileSync(new URL("../../references/product_runtime_contract.md", import.meta.url), "utf8");
const sentence = "A domain section may carry classical_texts: B. V. Raman's general statements in How to Judge a Horoscope for the placements this chart has; "
- + "let them inform the judgment and cite them by book name in 「## 判断依据」, do not paste the English into the body, and do not treat them as verdicts on this chart.";
+ // 原值: "…let them inform the judgment and cite them by book name in 「## 判断依据」, …"
+ // 新值: give their gist after 「传统说法:」 without the book name, author or page
+ // 原因: BUG-2133,产品负责人 2026-11-21「问答也不引书名」(与报告 BUG-2130 同一口径)
+ + "let them inform the judgment and give their gist in 「## 判断依据」 after 「传统说法:」 without book, author or page, do not paste the English into the body, and do not treat them as verdicts on this chart.";
assert.equal(contract.split(sentence).length - 1, 1);
const line = contract.split("\n").find((item) => item.includes(sentence))!;
assert.ok(line.startsWith("The evidence card is the chart evidence for this answer."), "inside P-10");
diff --git a/frontend/tests/consult-condensed-checklist-20260927.test.ts b/frontend/tests/consult-condensed-checklist-20260927.test.ts
index 2fa8b3f5c..5ba078915 100644
--- a/frontend/tests/consult-condensed-checklist-20260927.test.ts
+++ b/frontend/tests/consult-condensed-checklist-20260927.test.ts
@@ -107,7 +107,8 @@ test("career significators stay strength and affliction, and the system prompt i
// 原值(11): 12_395 新值(11): 12_391 原因(11): BUG-1898(产品 2026-11-15):问题里的话只能切到深度解读,P-02 那句去掉「简单说说」,短 4 个字符
// 原值(12): 12_391 新值(12): 12_323 原因(12): 产品 2026-11-16 合并两种解读方式:P-02、P-03 改成只有一种回答(白话正文 + 判断依据),短 68 个字符
// 原值(13): 12_323 新值(13): 12_622 原因(13): BUG-1926(产品 2026-11-16 决定交付 Raman 原文):P-10 列卡上内容的那段加一句 classical_texts 的用法(原书的一般说法,帮助判断、在判断依据里按书名引用、正文不贴英文、不当判定),长 299 个字符,只说一次
- assert.equal(natal.length, 12_622);
+ // 原值(14): 12_622 新值(14): 12_658 原因(14): BUG-2133(产品负责人 2026-11-21「问答也不引书名」):P-10 那句 classical_texts 的用法从「在判断依据里按书名引用」改为「在判断依据里写在「传统说法:」后面,不写书名、作者和页码」
+ assert.equal(natal.length, 12_658);
});
test("career direction section only writes strength, resistance, timing and three events", () => {
@@ -139,7 +140,8 @@ test("career direction section only writes strength, resistance, timing and thre
// 原值(11): 12_395 新值(11): 12_391 原因(11): 同上一测试(BUG-1898)
// 原值(12): 12_391 新值(12): 12_323 原因(12): 同上一测试(产品 2026-11-16 合并两种解读方式)
// 原值(13): 12_323 新值(13): 12_622 原因(13): 同上一测试(BUG-1926,P-10 加一句 classical_texts 的用法)
- assert.equal(natal.length, 12_622);
+ // 原值(14): 12_622 新值(14): 12_658 原因(14): 同上一测试(BUG-2133,问答也不引书名)
+ assert.equal(natal.length, 12_658);
});
test("each condensed list is 5–8 lines", () => {
diff --git a/frontend/tests/consult-internal-words-1948.test.ts b/frontend/tests/consult-internal-words-1948.test.ts
index fcf51f441..62fcc378a 100644
--- a/frontend/tests/consult-internal-words-1948.test.ts
+++ b/frontend/tests/consult-internal-words-1948.test.ts
@@ -32,9 +32,13 @@ test("internal words are defined positively: identifiers and lone status words,
"D9 第 7 宫金牛,UL 天秤,A7 金牛,AK 土星,AmK 金星,DK 火星,SAV 30,Shadbala 7.81 Rupa",
"Vimshottari 罗睺大运 2012-10-21 至 2030-10-21;Narayana 主运天秤;KP Sub Lord 罗睺;Karakamsha 双鱼",
"Raja Yoga (Parivartana)、Neecha Bhanga、Sade Sati、Kantaka、Ashtama Shani、Vivah Saham、Yogi 点",
- "B. V. Raman《How to Judge a Horoscope》第 2 卷 p.11",
- "PVR 表 30;Placidus 宫头;Sanjay Rath 版;Significator C 为火星",
+ "Placidus 宫头;Significator C 为火星",
]) assert.deepEqual(tokens(fine), [], fine);
+ // 原值:「B. V. Raman《How to Judge a Horoscope》第 2 卷 p.11」「PVR 表 30;…;Sanjay Rath 版」都不算内部词
+ // 新值:书名、作者、表号、章节和页码算出处,会被找出来
+ // 原因:BUG-2133,产品负责人 2026-11-21「问答也不引书名」(与报告 BUG-2130 同一口径)
+ assert.deepEqual(tokens("B. V. Raman《How to Judge a Horoscope》第 2 卷 p.11"), ["B. V. Raman", "《How to Judge a Horoscope》", "p.11"]);
+ assert.deepEqual(tokens("PVR 表 30;Placidus 宫头;Sanjay Rath 版"), ["PVR", "表 30", "Rath"]);
// A status word inside an English quotation is part of the quotation.
assert.deepEqual(tokens("Raman:「one will earn money by his own effort; moderate success if supported by benefics」"), []);
assert.deepEqual(tokens("原书说 \"the native is blocked by enemies\""), []);
@@ -127,8 +131,11 @@ test("the table uses existing wording, drops what carries nothing, and leaves re
// BUG-2041 原值:括号里留下状态表的 computed 文字 / 新值:她给用户的说法 / 原因:分层规则(复测第十轮「被检测器检出,待核实,不作定论」)
assert.equal(scrubInternalWords(`另被判为传统格局(computed,${YOGA_STATUS_MAPPING.computed.text}),只用来说明结构稳`), "另被判为传统格局(这一点目前还不能明确判断),只用来说明结构稳");
assert.equal(scrubInternalWords("按卡上 method_status,Narayana 为单体系候选窗口"), ",Narayana 为参考窗口");
- const fine = "- **事业**:D10 第 10 宫金牛内有木星、罗睺;B. V. Raman《How to Judge a Horoscope》第 2 卷;Shadbala 7.81 Rupa。(明显,B)";
+ const fine = "- **事业**:D10 第 10 宫金牛内有木星、罗睺;Shadbala 7.81 Rupa。(明显,B)";
assert.equal(scrubInternalWords(fine), fine);
+ // 原值:带「B. V. Raman《How to Judge a Horoscope》第 2 卷」的行原样保留 / 新值:书名作为出处去掉,别的不动
+ // 原因:BUG-2133,产品负责人 2026-11-21「问答也不引书名」
+ assert.equal(scrubInternalWords("- **事业**:D10 第 10 宫金牛内有木星、罗睺;B. V. Raman《How to Judge a Horoscope》第 2 卷;Shadbala 7.81 Rupa。(明显,B)"), fine);
// The table itself holds no identifier.
for (const word of Object.values(INTERNAL_VALUE_WORDS)) assert.deepEqual(findInternalWords(word), [], word);
// BUG-2041 原值:computed 的替换词是状态表文字 / 新值:她给用户的说法 / 原因:分层规则
diff --git a/frontend/tests/consult-internal-words-and-al-relation-1970.test.ts b/frontend/tests/consult-internal-words-and-al-relation-1970.test.ts
index 4043dd560..e09dc9ebb 100644
--- a/frontend/tests/consult-internal-words-and-al-relation-1970.test.ts
+++ b/frontend/tests/consult-internal-words-and-al-relation-1970.test.ts
@@ -46,10 +46,13 @@ test("the rule states and boolean fragments map to existing wording or are dropp
assert.equal(scrubInternalWords("结构上 observation,水星 not_executed。"), "结构上,水星未执行。");
});
-test("quotations, technique names and book titles are not flagged", () => {
+// 原值:「quotations, technique names and book titles are not flagged」,书名、作者、页码都不算
+// 新值:书名、作者、表号、章节和页码算出处(BUG-2133);引文、技法名照旧不算
+// 原因:产品负责人 2026-11-21「问答也不引书名」
+test("quotations and technique names are not flagged; book titles, authors and pages are", () => {
+ assert.deepEqual(tokens("Raman 写 \"a Raja Yoga is formed when the lords combine\",见第 2 卷 p.11。"), ["p.11"]);
+ assert.deepEqual(tokens("B. V. Raman《How to Judge a Horoscope》第 2 卷:the planet is combust and weak."), ["B. V. Raman", "《How to Judge a Horoscope》"]);
for (const line of [
- "Raman 写 \"a Raja Yoga is formed when the lords combine\",见第 2 卷 p.11。",
- "B. V. Raman《How to Judge a Horoscope》第 2 卷:the planet is combust and weak.",
"D9、UL、A7、Shadbala、Narayana、Vimshottari、KP、Sasa Yoga、Gaja Kesari Yoga 都照名写。",
"the yoga stays disabled in the old text; observation of the Moon is classical.",
"Rupa 7.11,SAV 30,第 7 宫。",
diff --git a/frontend/tests/evidence-pack-cancel-1987.test.ts b/frontend/tests/evidence-pack-cancel-1987.test.ts
index e6a0e48bb..32f4e146b 100644
--- a/frontend/tests/evidence-pack-cancel-1987.test.ts
+++ b/frontend/tests/evidence-pack-cancel-1987.test.ts
@@ -37,7 +37,8 @@ const CHARTS: Record = {
// Latin the card's analysis lines may carry (consult-followups-1945.test.ts ALLOWED_LATIN).
// 原值:只有 D\d+ / A\d+ / AL / UL。新值:加上书名《Light on Life》。
// 原因:BUG-2012,占星师 2026-11-19 第 3 条给的统一说法以「按《Light on Life》规则」开头。
-const ALLOWED_LATIN = /\b(?:D\d+|A\d+|AL|UL)\b|《Light on Life》/g;
+// 原值:加上书名《Light on Life》。新值:去掉(句子不再写书名)。原因:BUG-2133,产品负责人 2026-11-21 问答也不引书名。
+const ALLOWED_LATIN = /\b(?:D\d+|A\d+|AL|UL)\b/g;
const FORBIDDEN_CLAIMS = /强|吉|Raja|王者/;
function checkProse(text: string) {
@@ -64,7 +65,9 @@ test("one sentence per Neecha Bhanga cancellation on the public charts and the s
// 原值:/按落陷取消规则这一落陷已被取消/、「写成落陷但已被化解,不写成弱」、/取消不改变它的落陷位置/
// 新值:她的统一说法:已满足落陷取消条件;不等于入旺,困难不全部消失;取消只针对因落陷而来的不利判断
// 原因:BUG-2012,占星师 2026-11-19 上线前答复第 3、12 条
- assert.match(text, /按《Light on Life》规则,已满足落陷取消条件:/, chart);
+ // 原值:/按《Light on Life》规则,已满足落陷取消条件:/ 新值:不写书名 原因:BUG-2133 问答也不引书名
+ assert.match(text, /落陷,已满足落陷取消条件:/, chart);
+ assert.doesNotMatch(text, /《|Light on Life/, chart);
assert.match(text, new RegExp(`这不等于${name}入旺,也不代表相关困难全部消失`), chart);
assert.doesNotMatch(text, /已被取消|已被化解/, chart);
for (const condition of edge.conditions ?? []) assert.ok(text.includes(condition), `${chart}: ${condition}`);
diff --git a/references/product_runtime_contract.md b/references/product_runtime_contract.md
index c5eb5039f..dd937bb98 100644
--- a/references/product_runtime_contract.md
+++ b/references/product_runtime_contract.md
@@ -109,8 +109,9 @@ Select consultation domains only through the single ordered domains array of run
The tool result's methodology field is the checklist for the routes that actually ran: first 通用读法 · 先看受冲 (read afflictions before dignities, and count the signals it lists against the card's own fields), then, every turn, the astrologer's full router, her interpretation status contract, her output contract (event-judgment skeleton §5 Output Contract and §6 Hard Stops) and her working order (ai-reading-workflow-prompt §0.4); then, for this question, her event-judgment entry (ai-reading-workflow-prompt §2.3) and the matching event-judgment branch, her transit output guide when the question asks for a time, and the sub-skills the route's techniques need (specialized-jyotish only as the paragraphs for the needed technique plus its own boundaries; a relative link inside a sub-skill is read with skill_read as skills//); then one list per domain. methodology.delivery says which of her files travelled, in which layer and why; delivering a file is not running its method. Use them to judge. The checklist is a list of things to check, not a list of paragraphs to write: run every item that bears on this question, never recite the checklists' wording to the user, and write the answer as VISIBLE VOICE says. Those sections are already delivered, so never spend a turn re-reading them; read a methodology.further_reading reference with skill_read only when the question needs something they do not cover. When methodology.domains_without_strict_checklist names a domain, it has no named checklist: follow the shared reading and the bound skill method, and do not imply a named strict route was followed.
The tool result always carries one top-level answer contract—status, evidence_contract, claim_cards, rectification—even when several domains ran. For a multi-domain plan that top level is the most restrictive merge of the executed domains, so obey it exactly as written; consultations carries each domain's own contract. Never treat an absent top-level field as permission to answer without a contract.
+
-The evidence card is the chart evidence for this answer. claim_cards holds it: natal_foundation (ascendant, the twelve house signs, planet placements with degrees, functional benefics/malefics with the houses each planet rules, and d9: the D9 lagna, each planet's D9 sign and dignity, Vargottama and major D1/D9 dignity reversals — use it to confirm or weaken a D1 promise), timing (the running Vimshottari mahadasha, antardasha and pratyantardasha with dates, the antardashas inside the mahadasha, the next mahadasha, the running and next Narayana sign; a years-ahead question also gets horizon and the periods after that) and domain (one section per executed domain: its vargas, houses with occupants, lords and sav_strength (Ashtakavarga 强/中/弱), focus planets and the layers that domain uses; the parents section also carries roles, which says which house, lords, significator, karaka and D12 house belong to the mother and which to the father — write about each person from that person's entries). The values are copied from this request's calculation; quote them as given. A value tagged parameter_sensitive (the annual Tajika chart) or observation_only (Punarphoo) is structure to weigh, not a verdict; an annual_chart whose status is 年盘未接入 means there is no annual chart this turn, so say so and never stand natal data in for it. The card also carries parameters (ayanamsa, node mode, house system), timing.dasha_systems (every running dasha with dates), timing.transits_detail, natal.yogas_detail, special_points, KP (Placidus cusps with sign / star / sub / sub-sub lords, significators and dasha-lord triggers) and, per domain, a route table that says which techniques are on_card, not_applicable, blocked or not_available_yet. KP is parameter_sensitive: use it conditionally as evidence, and where it differs from the whole-sign reading, write both. A domain section may carry classical_texts: B. V. Raman's general statements in How to Judge a Horoscope for the placements this chart has; let them inform the judgment and cite them by book name in 「## 判断依据」, do not paste the English into the body, and do not treat them as verdicts on this chart. Chara Dasha and anything else the card lacks come from read-consultation-evidence. The server calculated the full spectrum and keeps the rest; evidence_card.supplementable_sections names what else this calculation holds. When the question needs one of those sections (for example a varga the card does not carry, a Western layer, the yoga details, Chara Dasha, KP, Karakamsha, Argala, the dispositor chain, the D1/D9/D10 linkage, or the Moon transit for a month- or day-level question), call read-consultation-evidence at most three times, before writing answer text; it returns that section or unavailable, and it never calculates. Answer from the card, plus those lookups when you used them.
+The evidence card is the chart evidence for this answer. claim_cards holds it: natal_foundation (ascendant, the twelve house signs, planet placements with degrees, functional benefics/malefics with the houses each planet rules, and d9: the D9 lagna, each planet's D9 sign and dignity, Vargottama and major D1/D9 dignity reversals — use it to confirm or weaken a D1 promise), timing (the running Vimshottari mahadasha, antardasha and pratyantardasha with dates, the antardashas inside the mahadasha, the next mahadasha, the running and next Narayana sign; a years-ahead question also gets horizon and the periods after that) and domain (one section per executed domain: its vargas, houses with occupants, lords and sav_strength (Ashtakavarga 强/中/弱), focus planets and the layers that domain uses; the parents section also carries roles, which says which house, lords, significator, karaka and D12 house belong to the mother and which to the father — write about each person from that person's entries). The values are copied from this request's calculation; quote them as given. A value tagged parameter_sensitive (the annual Tajika chart) or observation_only (Punarphoo) is structure to weigh, not a verdict; an annual_chart whose status is 年盘未接入 means there is no annual chart this turn, so say so and never stand natal data in for it. The card also carries parameters (ayanamsa, node mode, house system), timing.dasha_systems (every running dasha with dates), timing.transits_detail, natal.yogas_detail, special_points, KP (Placidus cusps with sign / star / sub / sub-sub lords, significators and dasha-lord triggers) and, per domain, a route table that says which techniques are on_card, not_applicable, blocked or not_available_yet. KP is parameter_sensitive: use it conditionally as evidence, and where it differs from the whole-sign reading, write both. A domain section may carry classical_texts: B. V. Raman's general statements in How to Judge a Horoscope for the placements this chart has; let them inform the judgment and give their gist in 「## 判断依据」 after 「传统说法:」 without book, author or page, do not paste the English into the body, and do not treat them as verdicts on this chart. Chara Dasha and anything else the card lacks come from read-consultation-evidence. The server calculated the full spectrum and keeps the rest; evidence_card.supplementable_sections names what else this calculation holds. When the question needs one of those sections (for example a varga the card does not carry, a Western layer, the yoga details, Chara Dasha, KP, Karakamsha, Argala, the dispositor chain, the D1/D9/D10 linkage, or the Moon transit for a month- or day-level question), call read-consultation-evidence at most three times, before writing answer text; it returns that section or unavailable, and it never calculates. Answer from the card, plus those lookups when you used them.
{{MEVG_BLOCKED_POLICY}}