| content |
{"Commits":[{"Sha1":"b94f71f09 {"Commits":[{"Sha1":"b94f71f09dc50f1a267a97bd72bdc2417fa41014","Message":"docs(governance): 沉淀反向断言剧场与 2026-07-28 全量对抗验收结论\n\n两节新增经验（经验库约定最新置顶，同步 最后更新 → 2026-07-28）：\n\n1. 反向断言剧场：事件常量漂移让「真派发」consumer 测试静默空转。\n 真派发 ≠ 真命中——架构上确实捕获并调用了 handler，但事件类型\n 打不中路由表，0===0 的断言掩盖哑火。含幂等测试非空前置断言铁律、\n 常量取值范式与 `_created` 去重分支陷阱（不能只替换字符串）。\n\n2. 全量对抗验收实测：leads 主链运行态对抗探测全通过，但\n governance-gate（stale=46）与 baseline-reconcile（7 VALUE_DRIFT，\n 其中 4 处来自最新报告）双双报红。运行态扎实 ≠ 工作区级可放行，\n 两层必须分开陈述；禁止上调 ceiling 洗绿。\n\n对应代码修复见 f0f7ca8627。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-28T17:47:57-07:00"},{"Sha1":"f0f7ca86271a2530ef901fe3b4472100452a02f3","Message":"test(hr): 修复因事件常量漂移而空转的消费者幂等测试\n\nhr.consumer 的路由键从 HR_ATTENDANCE_EVENTS.LEAVE_SUBMITTED\n('hr_leave_submitted') 改为 HR_EVENTS.LEAVE_REQUEST_CREATED\n('leave_request_created') 后，本测试仍硬编码旧字面量，导致\neventHandlers 查不到 handler、静默零副作用，测试退化为空转。\nproducer (leave.service.ts:612) 与 consumer 已对齐，生产代码无需改动。\n\n- 事件类型改从 HR_EVENTS 常量取值，后续重命名将直接编译失败而非静默失效\n- occurredAt 去重语义改用非 _created 事件验证：isEventProcessed 对\n `_created` 结尾事件按 eventType:entityId 去重（忽略 occurredAt），\n 用 created 事件断言「不同 occurredAt 都生效」在语义上必然失败\n- 两个用例补 afterFirst \u003e 0 防空转断言，杜绝 0 === 0 的假通过\n- 新增用例固定 _created 分支按 entityId 去重的语义\n\nbackend test:run: 653 files / 8945 tests 全通过（此前 2 failed）\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-28T17:40:14-07:00"},{"Sha1":"e756bd9203bbaacc6fc41c2f89f50259eeaf7e5d","Message":"Refactor governance workflows and frontend contracts\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-21T08:15:12-07:00"},{"Sha1":"33a0e20a1f45a68e6f951709fcf06742557cecba","Message":"Harden IM member boundaries and streamline governance guidance\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-21T04:01:44-07:00"},{"Sha1":"5f2d2c14951aaf1c46ad7d55b7152fe70e66395c","Message":"Improve governance workflows and frontend contract alignment\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-21T03:36:40-07:00"}],"HeadCommit":{"Sha1":"b94f71f09dc50f1a267a97bd72bdc2417fa41014","Message":"docs(governance): 沉淀反向断言剧场与 2026-07-28 全量对抗验收结论\n\n两节新增经验（经验库约定最新置顶，同步 最后更新 → 2026-07-28）：\n\n1. 反向断言剧场：事件常量漂移让「真派发」consumer 测试静默空转。\n 真派发 ≠ 真命中——架构上确实捕获并调用了 handler，但事件类型\n 打不中路由表，0===0 的断言掩盖哑火。含幂等测试非空前置断言铁律、\n 常量取值范式与 `_created` 去重分支陷阱（不能只替换字符串）。\n\n2. 全量对抗验收实测：leads 主链运行态对抗探测全通过，但\n governance-gate（stale=46）与 baseline-reconcile（7 VALUE_DRIFT，\n 其中 4 处来自最新报告）双双报红。运行态扎实 ≠ 工作区级可放行，\n 两层必须分开陈述；禁止上调 ceiling 洗绿。\n\n对应代码修复见 f0f7ca8627。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-28T17:47:57-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/c4f0c2eabbf729ae2f7cc6de2eda4416f0e7b3bb...b94f71f09dc50f1a267a97bd72bdc2417fa41014","Len":7}... |