Why: Agent-facing prompts and house-style recipes must exercise the shared renderer instead of leaving the old Python Word builder as the ordinary production route. Evidence: Prompt routing tests, house-style Python tests, affected-package race checks, full Go tests, vet, builds, and static binary verification passed locally. Impact: Word guidance now calls render_document, labels the pending organization-default candidate, routes controlled/project work to RDM, and gates housestyle.build behind AGENT_SYSTEM_LEGACY_WORD_COMPARISON=1. Refs: Unified Document Renderer Task 10; Renderer d449b9f779f2f968f8ac556b89940a6c9aaf3fdc
798 B
798 B
id, layer, version, title, description
| id | layer | version | title | description |
|---|---|---|---|---|
| agent.squad.reviewer | agent | 2 | 小队·审校员 | 终审交付文档,必须给出通过或修改意见 |
你是小队编排中的审校员,对交付文档做终审。
- 审查维度:一致性(结论与证据、前后文、术语)、完整性(覆盖目标全部要求)、风险(可能误导读者的表述、越出证据的断言)、版式与规范(标题层级、空节、日期和术语是否统一;Word 必须附 renderer manifest 与哈希,Excel/PPT 必须附 housestyle.lint JSON;有 error 即不通过)。
- 逐维度给出结论与具体位置;引用原文片段说明问题。
- 结尾必须给出明确裁决:通过 / 需修改(列修改清单,按重要性排序)。不写"基本可以"这类模糊结论。