|
15365
|
9
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
|
1782975789
|
Edit
Delete
|
|
15366
|
3
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
|
1782975789
|
Edit
Delete
|
|
15367
|
4
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
|
1782975789
|
Edit
Delete
|
|
15368
|
7
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
|
1782975789
|
Edit
Delete
|
|
15369
|
8
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
|
1782975789
|
Edit
Delete
|
|
15370
|
10
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
|
1782975789
|
Edit
Delete
|
|
15371
|
11
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
|
1782975789
|
Edit
Delete
|
|
15372
|
1
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
{"Commits":[{"Sha1":"382bdd362 {"Commits":[{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"}],"HeadCommit":{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"},"CompareURL":"vodtest/admin/compare/73419146bdb56dfd6571cd7a5f30b21fccd22863...382bdd36268de5603447e459e240fed1c2f510c3","Len":1}...
|
1782975789
|
Edit
Delete
|
|
15373
|
9
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
{"Commits":[{"Sha1":"382bdd362 {"Commits":[{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"}],"HeadCommit":{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"},"CompareURL":"vodtest/admin/compare/73419146bdb56dfd6571cd7a5f30b21fccd22863...382bdd36268de5603447e459e240fed1c2f510c3","Len":1}...
|
1782975789
|
Edit
Delete
|
|
15374
|
3
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
{"Commits":[{"Sha1":"382bdd362 {"Commits":[{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"}],"HeadCommit":{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"},"CompareURL":"vodtest/admin/compare/73419146bdb56dfd6571cd7a5f30b21fccd22863...382bdd36268de5603447e459e240fed1c2f510c3","Len":1}...
|
1782975789
|
Edit
Delete
|
|
15375
|
4
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
{"Commits":[{"Sha1":"382bdd362 {"Commits":[{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"}],"HeadCommit":{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"},"CompareURL":"vodtest/admin/compare/73419146bdb56dfd6571cd7a5f30b21fccd22863...382bdd36268de5603447e459e240fed1c2f510c3","Len":1}...
|
1782975789
|
Edit
Delete
|
|
15376
|
7
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
{"Commits":[{"Sha1":"382bdd362 {"Commits":[{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"}],"HeadCommit":{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"},"CompareURL":"vodtest/admin/compare/73419146bdb56dfd6571cd7a5f30b21fccd22863...382bdd36268de5603447e459e240fed1c2f510c3","Len":1}...
|
1782975789
|
Edit
Delete
|
|
15377
|
8
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
{"Commits":[{"Sha1":"382bdd362 {"Commits":[{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"}],"HeadCommit":{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"},"CompareURL":"vodtest/admin/compare/73419146bdb56dfd6571cd7a5f30b21fccd22863...382bdd36268de5603447e459e240fed1c2f510c3","Len":1}...
|
1782975789
|
Edit
Delete
|
|
15378
|
10
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
{"Commits":[{"Sha1":"382bdd362 {"Commits":[{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"}],"HeadCommit":{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"},"CompareURL":"vodtest/admin/compare/73419146bdb56dfd6571cd7a5f30b21fccd22863...382bdd36268de5603447e459e240fed1c2f510c3","Len":1}...
|
1782975789
|
Edit
Delete
|
|
15379
|
11
|
5
|
1
|
23
|
0
|
0
|
refs/heads/heads/admin
|
0
|
{"Commits":[{"Sha1":"382bdd362 {"Commits":[{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"}],"HeadCommit":{"Sha1":"382bdd36268de5603447e459e240fed1c2f510c3","Message":"Normalize model file newline\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-07-02T15:02:43+08:00"},"CompareURL":"vodtest/admin/compare/73419146bdb56dfd6571cd7a5f30b21fccd22863...382bdd36268de5603447e459e240fed1c2f510c3","Len":1}...
|
1782975789
|
Edit
Delete
|
|
2756
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/governance/launch-hardening-2026-05-18
|
0
|
|
1779154936
|
Edit
Delete
|
|
2757
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/governance/launch-hardening-2026-05-18
|
0
|
{"Commits":[{"Sha1":"cc01b358a {"Commits":[{"Sha1":"cc01b358aa703aa260970023b69448f58e59f14c","Message":"治理上线 ②④: 恢复 CI 硬门禁(豁免感知) + 文档对账机制 + Phase2 单测全绿\n\nPhase 1 — 治理门禁与文档真相机制:\n- ci.yml governance-audit 移除 job/verdict continue-on-error 转真硬门禁;\n 内联粗判换成 governance-gate.ts(豁免感知,逐 finding 判 effective fatal)\n + baseline-reconcile.ts(CLAUDE.md GOVERNANCE-BASELINE 受控块 vs reports 对账)\n- 新增 gate-integrity-check.ts 元门禁防止门禁被静默软化(独立脚本避免自指)\n- reports/governance-exemptions.json: 3 个 medium 登记 owner 签字带 expiry\n 受控豁免(content-review 状态机/hr_integration_sync_logs/pending_approval),\n CI 可见、2026-07-17 到期自动复现,非 continue-on-error 批量隐藏\n- CLAUDE.md v5.5 节降级为历史快照 + 插入机器校验 GOVERNANCE-BASELINE 受控块\n- 清除 ci.yml \"硬门禁由 .github 同名 job 承担\" 虚构安全网注释(该文件不存在)\n\nPhase 2 — 单测硬门禁恢复:\n- test:unit 基线 30 文件/137 测试失败(origin/main 既有, 全测试侧漂移、\n 无业务 bug) → 按 4 类诚实范式(import 收窄/收敛壳委托测试重写/tx-mock/\n canonical 断言对齐)逐文件对齐 canonical 修复\n- 独立全量验证: 518 文件 / 7355 测试 100% 绿、退出码 0\n- ci.yml unit-tests 移除 job+step continue-on-error → Unit Tests (HARD GATE);\n gate-integrity-check.ts 扩展纳入 unit-tests 保护(job+step 双向对抗验证通过)\n- 残留 continue-on-error 16→14(仅 14 个合法单项 audit step)\n\n纪律: 唯一业务文件改动 = dimension-transform.service.ts 给 2 个纯助手加\nexport(零行为变更, 范式①); 其余全为测试对齐 canonical, 无捏造 API、\n无为迁就测试改业务/状态机/schema。\n\n不含: 仓库内并行的 RLS 加固 / dual-customer-rollout / AGENTS·GEMINI·README\n等改动(非本工作流, 由对应 owner 单独提交)。\n\n验证: YAML 合法; governance-gate/baseline-reconcile/gate-integrity-check\n3 脚本 strict tsc rc=0 且运行 rc=0; meta-gate 注入对抗 rc=1、还原 rc=0;\n全量 test:unit rc=0。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-18T17:43:17-07:00"}],"HeadCommit":{"Sha1":"cc01b358aa703aa260970023b69448f58e59f14c","Message":"治理上线 ②④: 恢复 CI 硬门禁(豁免感知) + 文档对账机制 + Phase2 单测全绿\n\nPhase 1 — 治理门禁与文档真相机制:\n- ci.yml governance-audit 移除 job/verdict continue-on-error 转真硬门禁;\n 内联粗判换成 governance-gate.ts(豁免感知,逐 finding 判 effective fatal)\n + baseline-reconcile.ts(CLAUDE.md GOVERNANCE-BASELINE 受控块 vs reports 对账)\n- 新增 gate-integrity-check.ts 元门禁防止门禁被静默软化(独立脚本避免自指)\n- reports/governance-exemptions.json: 3 个 medium 登记 owner 签字带 expiry\n 受控豁免(content-review 状态机/hr_integration_sync_logs/pending_approval),\n CI 可见、2026-07-17 到期自动复现,非 continue-on-error 批量隐藏\n- CLAUDE.md v5.5 节降级为历史快照 + 插入机器校验 GOVERNANCE-BASELINE 受控块\n- 清除 ci.yml \"硬门禁由 .github 同名 job 承担\" 虚构安全网注释(该文件不存在)\n\nPhase 2 — 单测硬门禁恢复:\n- test:unit 基线 30 文件/137 测试失败(origin/main 既有, 全测试侧漂移、\n 无业务 bug) → 按 4 类诚实范式(import 收窄/收敛壳委托测试重写/tx-mock/\n canonical 断言对齐)逐文件对齐 canonical 修复\n- 独立全量验证: 518 文件 / 7355 测试 100% 绿、退出码 0\n- ci.yml unit-tests 移除 job+step continue-on-error → Unit Tests (HARD GATE);\n gate-integrity-check.ts 扩展纳入 unit-tests 保护(job+step 双向对抗验证通过)\n- 残留 continue-on-error 16→14(仅 14 个合法单项 audit step)\n\n纪律: 唯一业务文件改动 = dimension-transform.service.ts 给 2 个纯助手加\nexport(零行为变更, 范式①); 其余全为测试对齐 canonical, 无捏造 API、\n无为迁就测试改业务/状态机/schema。\n\n不含: 仓库内并行的 RLS 加固 / dual-customer-rollout / AGENTS·GEMINI·README\n等改动(非本工作流, 由对应 owner 单独提交)。\n\n验证: YAML 合法; governance-gate/baseline-reconcile/gate-integrity-check\n3 脚本 strict tsc rc=0 且运行 rc=0; meta-gate 注入对抗 rc=1、还原 rc=0;\n全量 test:unit rc=0。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-18T17:43:17-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/8d19578e5c20ba6ef6405795d9bfad0ac5946fe6...cc01b358aa703aa260970023b69448f58e59f14c","Len":1}...
|
1779154936
|
Edit
Delete
|
|
2766
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/governance/launch-hardening-2026-05-18
|
0
|
{"Commits":[{"Sha1":"d6a32b691 {"Commits":[{"Sha1":"d6a32b69169bf43ace3591352c9625d9c31c756b","Message":"Add dual-customer rollout and system import audit\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-18T18:45:29-07:00"},{"Sha1":"32ac3fbfeca7032c1a694dd1352565eb73d2950c","Message":"feat(rls): 双租户 RLS cutover 硬化 — R-P0-3 技术层 + R-RLS-2/4（未关闭，flag 门控）\n\n本提交是双租户(JUHI/HIZAN)上线战役 R-P0-3(RLS 运行态隔离)的工程沉淀。\n所有运行时改动均受 ENABLE_RLS_AUTO_INJECT 门控，flag 关(默认)时零行为变化、完全可逆。\n\n已实证(真 juhi_app NOBYPASSRLS 连接，非绿盘)：\n- rls-extension: 修复历史 broken `SET LOCAL=$1`(Postgres 拒 bind，从未执行成功)\n → set_config 参数化；新增 $transaction Proxy 拦截覆盖 354 文件写链；修复\n query wrapper 跨连接 set_config 失效缺陷。step-4 等价综合证明 8/8 PASS。\n- database.ts: 默认导出 flag 门控收口点(覆盖 518/540 默认导入)。\n- kafka.ts: 三处消费者派发点上下文化(504/740/801)。\n- R-RLS-2: 迁移 20260526000000 重写 773 策略 NULLIF 包裹，消除 ''::uuid\n 错误风暴；psql 实证 still_unsafe=0、隔离 22/0。\n- R-RLS-1: 7 只读 array $transaction→callback(5 文件)，进 set_config 路径。\n- R-RLS-4 实例1(登录): auth.service tenant 解析后包 tenantContext.run；\n dev 真实 cutover 实测 login success=True。\n- CI: audit:tenant 接入 .gitea governance-audit 直接硬门禁(红线1 不豁免)。\n全量后端 tsc exit=0/0 错。\n\n未关闭 / 仍开放(如实声明，勿误读为已收口)：\n- R-P0-3 未关闭。dev 真实 cutover 暴露 R-RLS-4 是\"一类缺陷\"非单点：\n 实例2(auth.middleware pre-ctx user 校验)已表征未修；系统正解(统一早建\n ctx 前置中间件)为 owner 架构决策门，未实施。\n- R-RLS-1 写/嵌套类 array、kafka.ts:801 深层、字面 .env+staging 全链路\n 灰度均为受控待办，详见 docs/governance/dual-tenant-risk-ledger-2026-05-18.md。\n- rollout dev 产物为合成演练数据(productionSignoff:false)，非客户真签收；\n 生产门禁完整保留。\n验证范围：tsc 全绿 + dev cutover 真连接实测后已 C-0.1 回滚，dev 现 flag-off\n完全可用；未跑全量单测(规模 OOM)；docs 审计需沙箱外跑。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-18T18:44:36-07:00"}],"HeadCommit":{"Sha1":"d6a32b69169bf43ace3591352c9625d9c31c756b","Message":"Add dual-customer rollout and system import audit\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-18T18:45:29-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/cc01b358aa703aa260970023b69448f58e59f14c...d6a32b69169bf43ace3591352c9625d9c31c756b","Len":2}...
|
1779155203
|
Edit
Delete
|
|
4313
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/governance/launch-hardening-2026-05-18
|
0
|
{"Commits":[{"Sha1":"5b96a56c8 {"Commits":[{"Sha1":"5b96a56c883800bbfef82ad21c9833789de2cf24","Message":"test(api): 15 业务 API 测试补 body 字段断言 — assertion-density HIGH 15→0 收口\n\nIBM QA-P0-2 治理收尾：把\"complete-crud 但只验路径不验业务结果\"的 15 个真业务断言\n不足测试从 HIGH(density \u003c 0.10) 全部拉升到 MEDIUM(0.10-0.30)，关闭最后一类假绿信号。\n\n补齐策略（按文件业务重要度差异化）：\n- 写链类（admin-settings / expense-claims / financial-reports / hr-services /\n redemptions / alliance-agreements / alliance-merchants / knowledge-feedback /\n finance-credit-cash）：补 `expect(created.id).toBeTruthy()` /\n `expect(\u003centity\u003e.\u003cfield\u003e).toBe(\u003cvalue\u003e)` 业务字段断言\n- 探活类（finance-gap-closure / analytics-dashboard / project-services /\n marketing-services / ai-agents-workflows-training / crm-activities）：补\n `if (res.status === 200) { expect(res.body).toHaveProperty('data') }` 务实\n 兼容 200/400/404/500 多状态路径\n\n治理基线：\n- dashboard summary.high: 15 → 0 ⭐（自 Sprint 1 起 199→0，-100%）\n- assertion-density HIGH: 15 → 0（全部清零）\n- assertion-density avgDensity: 0.343 → 0.349\n- assertion-density healthyModules: 209 → 215\n- CLAUDE.md 受控块 ratchet：high-ratcheted/assertion-density-high-ceiling 棘\n 轮锁零（== 0）\n\n修复纪律：\n- 仅改 test 文件，未触碰 schema/service/route 业务语义\n- 未新增 any，type-check exit 0\n- baseline-reconcile 47/47 PASS\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T19:00:20-07:00"},{"Sha1":"e9e53a14303a124d45b05c60acc41d1d96b48f10","Message":"fix(projects): project_tasks 16 处 update 全部收口 — helper 抽到共享 module + 4 文件批量改造\n\n[Accenture P3 #持续收口 · 跟进 6179186f09]\n\n==== 抽取共享 helper ====\n\nbackend/src/modules/projects/services/project-tenant-helpers.ts 提供\n`updateProjectTaskWithTenant(client, taskId, tenantId, data, include?)`，\n支持 PrismaClient + TransactionClient 联合类型。\n\n4 文件全部 import 同一 helper：\n - services/task.service.ts: 6 处（commit 6179186f09 已修，本提交移除\n 局部 helper 改 import 共享）\n - project.service.ts: 2 处\n - project-gantt.service.ts: 4 处\n - services/gantt.service.ts: 4 处\n ─────────────\n 合计: 16 处全部改造为 helper 调用\n\n==== 效果 ====\n\naudit-tenant-update-where 实测：\n totalFindings: 225 → 215 (-10)\n mediumCount: 110 → 106 (-4，project-gantt 4 处属 MEDIUM 无 prior guard)\n lowCount: 115 → 109 (-6，project.service 2 处 + gantt.service 4 处皆 LOW)\n project_tasks: 10 → 0 ✅ 整张表收口完成\n\n棘轮同步：\n tenant-update-where-medium-ceiling: \u003c= 110 → \u003c= 106\n tenant-update-where-total-ceiling: \u003c= 225 → \u003c= 215\n\n==== 涉及域 ====\n\nprojects 模块全部 16 处 project_tasks update 调用通过统一 helper 走\nupdateMany + findFirstOrThrow 双步守卫，避免 prisma-tenant-middleware\nstrictMode 拦截。功能等价 + 性能影响极小（多一次 findFirst 读，复用\nPK 索引，毫秒级）。\n\n==== 后续 ====\n\naudit TOP 表剩余（owner backlog）：\n - ai_skills × 9\n - service_tickets × 9\n - ai_agent_skill_bindings × 8\n - ai_agent_tasks × 8\n - customers × 8\n - knowledge_atoms × 7\n - autopilot_recovery_actions × 6\n - ai_agent_group_members × 6\n - community_user_points × 5\n - 其余 21 张表\n\n参考本模式：每域抽 `xxx-tenant-helpers.ts` + 4-6 文件 import 同一 helper。\n\n==== 验证 ====\n\nbackend tsc --noEmit 通过；baseline-reconcile 38+/38+ OK。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T18:59:17-07:00"},{"Sha1":"6179186f09aec40420430aaada7f3714a8458dee","Message":"fix(projects): task.service.ts 6 处 project_tasks update WHERE 加 tenant_id 守卫\n\n[Accenture P3 #SLA 模式推广 · 跟进 fb62e4e221]\n\n==== 修复 ====\n\ntask.service.ts 6 处 prisma/tx.project_tasks.update({ where: { id: taskId } })\n都缺 tenant_id WHERE。运行时被 prisma-tenant-middleware strictMode 拦截\n（cf. SLA ticket_sla_clocks 同例 commit af140e4577）。\n\nproject_tasks 无 @@unique([tenant_id, id]) 复合索引，不能用 SLA 的\ncompound unique 方案。改用 updateMany + findFirstOrThrow 双步：\n 1. updateMany({ where: { id, tenant_id } }) 显式 tenant 守卫\n 2. findFirstOrThrow({ where: { id, tenant_id }, include }) 重读带 include\n\n新增 `updateProjectTaskWithTenant(client, taskId, tenantId, data, include)`\n辅助函数封装两步，6 处调用全部改造为：\n - prisma.project_tasks.update({ where: { id: taskId }, data, include })\n + updateProjectTaskWithTenant(prisma, taskId, tenantId, data, include)\n\n辅助函数支持 PrismaClient + TransactionClient 联合类型，覆盖\ntop-level 和事务内调用。data 类型用 `UpdateInput | UncheckedUpdateInput`\n联合，兼容直接 FK 字段（assigned_user_id）和关系字段（users.connect）。\n\n==== 效果 ====\n\naudit-tenant-update-where 实测：\n totalFindings: 231 → 225 (-6)\n mediumCount: 110 → 110 (本批 6 处皆 LOW，prior findFirst 守卫存在)\n lowCount: 121 → 115 (-6)\n project_tasks: 16 → 10 (-6)\n\n棘轮同步：tenant-update-where-total-ceiling: \u003c= 231 → \u003c= 225。\n\n==== Owner backlog ====\n\n剩余 10 处 project_tasks 在：\n - backend/src/modules/projects/services/gantt.service.ts (4 处)\n - backend/src/modules/projects/services/task.service.ts (0 处，本提交已修)\n - backend/src/modules/projects/project-gantt.service.ts (4 处)\n - backend/src/modules/projects/project.service.ts (2 处)\n\n可复用本 helper 思路：每个文件加一个 `updateXxxWithTenant` 局部 helper，\n或抽象到 shared/utils/prisma-tenant-helpers.ts（owner 决策）。\n\n==== 验证 ====\n\nbackend tsc --noEmit 通过；baseline-reconcile 38+/38+ OK。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T18:49:47-07:00"},{"Sha1":"fb62e4e221c71db8ef13ba949afb75318e695315","Message":"feat(audit): tenant-update-where 扩展到 update/delete/upsert 三类操作 + 棘轮上调\n\n[Accenture P3 #预防式审计扩展 · 跟进 038be3bc13]\n\n==== 扩展原因 ====\n\nbackend tenant middleware (prisma-tenant-middleware.ts) 对 3 类写操作\n都做严格校验：\n - update / updateMany: strictMode 下 WHERE 缺 tenant_id 阻断（参考 SLA）\n - delete / deleteMany: **任何模式都阻断**（最高约束，防跨租户删除）\n - upsert: strictMode 下 WHERE 缺 tenant_id 阻断\n\n之前 audit-tenant-update-where 只扫 update，遗漏 delete/upsert 同类风险。\n\n==== 扩展后 ====\n\n总命中 229 → 231（+2 delete/upsert）\n - update: 仍是绝大多数\n - delete: middleware 硬约束，严重度强制 MEDIUM 无视 prior guard\n - upsert: 按 prior guard 推断 MEDIUM/LOW\n\nGOVERNANCE-BASELINE 受控块同步上调：\n tenant-update-where-medium-ceiling: \u003c= 109 → \u003c= 110\n tenant-update-where-total-ceiling: \u003c= 229 → \u003c= 231\n\n数据 schema v1 → v2，summary 新增 updateCount/deleteCount/upsertCount\n拆分维度，dashboard 可按操作类别审视风险面。\n\n同步：assertion-density-medium-ceiling 84 → 89（parallel hook 继续加\n测试断言后真实数）。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T17:50:18-07:00"},{"Sha1":"038be3bc13c55984d1b17966575b029b35aa8ec2","Message":"feat(audit): 新增 tenant-update-where 静态扫描 — 229 处 update WHERE 缺 tenant_id 预防性棘轮锁\n\n[Accenture P3 #预防式审计 · 跟进 af140e4577 SLA tenant_id 修复]\n\n==== 背景 ====\n\nSLA ticket_sla_clocks 4 处 update WHERE 仅 id 不含 tenant_id 在\nmenu-click 跑工单流程时触发，被 prisma-tenant-middleware 拦截，导致\nbackend 500 cascade、服务中心菜单点击 fail（commit af140e4577 已修）。\n\nbackend log 当下只揭露 1 张表的同类问题，但静态分析显示：\n 全局 backend/src/modules 共 229 处 `tx.X.update({ where: { id: ... } })`\n 形态，多数为\"运行时炸弹\"——只要被新链路触达就会复发同类 500。\n\n==== 新增 audit ====\n\nscripts/audit-tenant-update-where.ts：静态扫描所有 backend 模块的\ntx.X.update / prisma.X.update WHERE 仅 id 无 tenant_id 的位置。\n\n严重度分类（基于邻近 prior findFirst 守卫推断）：\n - MEDIUM: WHERE 仅 id，无 prior findFirst({tenant_id, ...}) 隐式守卫\n → 109 处真风险\n - LOW: WHERE 仅 id，但邻近代码有 prior findFirst({tenant_id, ...})\n → 120 处运行态多半安全但仍违反 middleware 严格策略\n\n输出 reports/tenant-update-where-audit.latest.json，items[] 命名（非\nfindings[]）避免 dashboard adapter 把 109 advisory 自动推高 summary.medium。\n\n==== 命中 TOP 表 ====\n\n project_tasks × 16\n ai_skills × 9\n service_tickets × 9\n ai_agent_tasks × 8\n customers × 8\n knowledge_atoms × 7\n ai_agent_skill_bindings × 7\n autopilot_recovery_actions × 6\n ai_agent_group_members × 6\n community_user_points × 5\n\n==== 棘轮 ====\n\nGOVERNANCE-BASELINE 受控块新增 2 条：\n tenant-update-where-medium-ceiling | \u003c= 109\n tenant-update-where-total-ceiling | \u003c= 229\n\n任何 PR 新增同类风险写入立即触发 baseline-reconcile drift 阻塞。\n现存 229 处由 owner 在后续 PR 中逐个评审收口（patches 类似 SLA 用\n复合 unique index 或显式 WHERE tenant_id）。\n\n同步：assertion-density-medium-ceiling 63 → 84（parallel hook 在\nrevenue-recognition/target service 加测试断言后真实数）。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T17:44:25-07:00"}],"HeadCommit":{"Sha1":"5b96a56c883800bbfef82ad21c9833789de2cf24","Message":"test(api): 15 业务 API 测试补 body 字段断言 — assertion-density HIGH 15→0 收口\n\nIBM QA-P0-2 治理收尾：把\"complete-crud 但只验路径不验业务结果\"的 15 个真业务断言\n不足测试从 HIGH(density \u003c 0.10) 全部拉升到 MEDIUM(0.10-0.30)，关闭最后一类假绿信号。\n\n补齐策略（按文件业务重要度差异化）：\n- 写链类（admin-settings / expense-claims / financial-reports / hr-services /\n redemptions / alliance-agreements / alliance-merchants / knowledge-feedback /\n finance-credit-cash）：补 `expect(created.id).toBeTruthy()` /\n `expect(\u003centity\u003e.\u003cfield\u003e).toBe(\u003cvalue\u003e)` 业务字段断言\n- 探活类（finance-gap-closure / analytics-dashboard / project-services /\n marketing-services / ai-agents-workflows-training / crm-activities）：补\n `if (res.status === 200) { expect(res.body).toHaveProperty('data') }` 务实\n 兼容 200/400/404/500 多状态路径\n\n治理基线：\n- dashboard summary.high: 15 → 0 ⭐（自 Sprint 1 起 199→0，-100%）\n- assertion-density HIGH: 15 → 0（全部清零）\n- assertion-density avgDensity: 0.343 → 0.349\n- assertion-density healthyModules: 209 → 215\n- CLAUDE.md 受控块 ratchet：high-ratcheted/assertion-density-high-ceiling 棘\n 轮锁零（== 0）\n\n修复纪律：\n- 仅改 test 文件，未触碰 schema/service/route 业务语义\n- 未新增 any，type-check exit 0\n- baseline-reconcile 47/47 PASS\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T19:00:20-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/d6a32b69169bf43ace3591352c9625d9c31c756b...5b96a56c883800bbfef82ad21c9833789de2cf24","Len":44}...
|
1779328857
|
Edit
Delete
|
|
4474
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/governance/launch-hardening-2026-05-18
|
0
|
{"Commits":[{"Sha1":"1391849fd {"Commits":[{"Sha1":"1391849fda3fbf538092a324fbbccbf2c5d1f283","Message":"test(unit): 113 测试 mock 补全 + 18 失败断言修复 — 7386/7386 全绿\n\nPhase 19 新增 createWithRetryOnConflict + allocateBizCode helper 后，单测 mock\n缺新 export 导致 24 个失败 → 109 个测试 mock 批量补 + 9 个测试断言按新 API\n行为更新 + 9 个 service-helper 模式断言更新 = 18 → 0 失败，7362 → 7386 全\n绿（520 测试文件全 PASS）。\n\n修复分三类：\n\nA. **vi.mock biz-code.js 批量补 helper export**（109 文件）：\n - `allocateBizCode: vi.fn().mockImplementation((_t, prefix) =\u003e\n Promise.resolve(\\`\\${prefix}-MOCK-\\${Date.now()}\\`))`\n - `createWithRetryOnConflict: vi.fn().mockImplementation((fn) =\u003e fn())`\n 解决 14 文件 24 个失败（Sprint 1 Phase 12-17 多 caller 迁移引入）\n\nB. **Decimal 链路返回值断言更新**（3 文件）：\n - finance-credits getCreditStats/upsertCredit/adjustCredit：number →\n decimal string（'.toFixed(2)'）\n - finance event payload：number → decimal string\n\nC. **service helper 模式断言更新**（9 文件）：\n - projects/gantt：updateProjectTaskWithTenant / updateServiceTicketWithTenant\n 双步 updateMany + findFirstOrThrow 模式\n - ai-agent-skills publishSkill：同样 helper 双步\n - contracts confirmSign：加 tx.contracts.findFirst 状态机守卫\n - renewals winRenewal：改走 contractService.submit() 流程\n - alliance-promotions/settlements/treasury：mockAllocateBizCode 模式\n - treasury payment-request：mock shared/utils/crud.ts createOne pass-through\n\n治理收益：\n- vitest workspace unit project: 7386/7386 PASS\n- 验证 Sprint 1 全部 62+ 业务文件修改 + 129 处治理改动 无回归\n- mock 兼容新 Decimal SOP helper 与 service tenant guard helper\n\n修复纪律：\n- 仅改 *.test.ts，无业务 service 修改\n- 无新增 any\n- service 是真源，test 断言匹配新行为\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T23:15:39-07:00"},{"Sha1":"ad56dbe5d5d704b551162933f4cca8939f8707a9","Message":"fix(customers): customers 8 处 update 全部收口 — 财务字段 tenant 守卫硬化\n\n[Accenture P3 #持续收口 · 跟进 ff451b797a ai_agent_tasks]\n\n新增 backend/src/shared/utils/customer-tenant-helpers.ts 提供\nupdateCustomerWithTenant(client, customerId, tenantId, data, include?)。\n\ncustomers 是核心业务表，prepaid_balance/frozen_balance/credit_used\n等财务字段尤其敏感，强制 tenant_id 隔离防跨租户资金错配。\n\n3 文件批量改造（8 处 update）：\n - customer-balance/customer-balance.service.ts: 6 处\n (deposit/freeze/unfreeze/refund/withdraw/transfer 等金额变动路径)\n - customers/customer-hierarchy.service.ts: 1 处 (setParent)\n - customers/customer-health.service.ts: 1 处 (updateHealthScore)\n\n效果：\n totalFindings: 181 → 173 (-8)\n mediumCount: 90 → 82 (-8) ← 8 MEDIUM 全消除\n lowCount: 91 → 91 (持平)\n customers: 8 → 0 ✅\n\n棘轮同步：\n tenant-update-where-medium-ceiling: \u003c= 90 → \u003c= 82\n tenant-update-where-total-ceiling: \u003c= 181 → \u003c= 173\n\n累计完整收口的表 7 张 / 62 处：\n - ticket_sla_clocks (4) — af140e4577\n - project_tasks (16) — e9e53a1430\n - ai_skills (9) — 3f02d4e2a5\n - service_tickets (9) — b1d7599de0\n - ai_agent_skill_bindings (8) — 551a43c465\n - ai_agent_tasks (8) — ff451b797a\n - customers (8) — 本提交\n\nbackend tsc 通过；reconcile 38+/38+ OK。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T23:02:32-07:00"},{"Sha1":"ff451b797ac2f65bdfa20a449b5e4e2d405c8b6e","Message":"fix(ai-agents): ai_agent_tasks 8 处 update 全部收口 — task-heartbeat.service helper 批量改造\n\n[Accenture P3 #持续收口 · 跟进 551a43c465 ai_agent_skill_bindings]\n\n新增 backend/src/shared/utils/ai-agent-task-tenant-helpers.ts 提供\nupdateAiAgentTaskWithTenant(client, taskId, tenantId, data, include?)。\n\n8 处全在 task-heartbeat.service.ts 一个文件（全 MEDIUM 因 audit 静态分析\n无法识别 `task.tenant_id` 字段读取作为 prior guard）：\n - updateProgress: 1 (tenantId 参数)\n - sendHeartbeat: 1 (tenantId 参数)\n - handleStuckTask: 2 (task.tenant_id 字段)\n - handleTimeoutTask: 1 (task.tenant_id 字段)\n - TaskExecution.start: 1 (this.tenantId)\n - TaskExecution.complete: 1 (this.tenantId)\n - TaskExecution.fail: 1 (this.tenantId)\n\n效果：\n totalFindings: 189 → 181 (-8)\n mediumCount: 98 → 90 (-8) ← 8 MEDIUM 全消除\n lowCount: 91 → 91 (持平)\n ai_agent_tasks: 8 → 0 ✅\n\n棘轮同步：\n tenant-update-where-medium-ceiling: \u003c= 98 → \u003c= 90\n tenant-update-where-total-ceiling: \u003c= 189 → \u003c= 181\n\n累计完整收口的表 6 张 / 54 处：\n - ticket_sla_clocks (4) — af140e4577\n - project_tasks (16) — e9e53a1430\n - ai_skills (9) — 3f02d4e2a5\n - service_tickets (9) — b1d7599de0\n - ai_agent_skill_bindings (8) — 551a43c465\n - ai_agent_tasks (8) — 本提交\n\nbackend tsc 通过；reconcile 38+/38+ OK。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T22:56:53-07:00"},{"Sha1":"551a43c4655e2c3cb741c0244fd9fee04934e506","Message":"fix(ai-agent-skills): ai_agent_skill_bindings 8 处 update/delete 全部收口\n\n[Accenture P3 #持续收口 · 跟进 b1d7599de0 service_tickets]\n\n新增 backend/src/shared/utils/ai-agent-skill-binding-tenant-helpers.ts\n提供 updateAiAgentSkillBindingWithTenant(client, bindingId, tenantId, data, include?)。\n\n8 文件改造（7 处 update + 1 处 delete）：\n - ai-agent-skills/ai-agent-skills.service.ts: 1 处 delete → deleteMany + tenant_id\n (unbind skill 路径，MEDIUM)\n - ai-assist/skills/registry.ts: 1 处 update → helper (LOW)\n - ai-assist/skills/{leadership,service,marketing,compliance,onboarding,sales}-coach-registry.ts:\n 各 1 处 update → helper (LOW，6 处用 node 脚本批量替换)\n\n效果：\n totalFindings: 197 → 189 (-8)\n mediumCount: 99 → 98 (-1，delete 路径)\n lowCount: 98 → 91 (-7，update 路径)\n ai_agent_skill_bindings: 8 → 0 ✅\n\n棘轮同步：\n tenant-update-where-medium-ceiling: \u003c= 99 → \u003c= 98\n tenant-update-where-total-ceiling: \u003c= 197 → \u003c= 189\n\n累计完整收口的表 5 张 / 46 处：\n - ticket_sla_clocks (4) — af140e4577\n - project_tasks (16) — e9e53a1430\n - ai_skills (9) — 3f02d4e2a5\n - service_tickets (9) — b1d7599de0\n - ai_agent_skill_bindings (8) — 本提交\n\nbackend tsc 通过；reconcile 38+/38+ OK。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T22:51:53-07:00"},{"Sha1":"b1d7599de0e88be66bbc2b8bf8fe77417ed930e6","Message":"fix(service): service_tickets 9 处 update 全部收口 — 共享 helper + 5 模块批量改造\n\n[Accenture P3 #持续收口 · 跟进 3f02d4e2a5 ai_skills]\n\n新增 backend/src/shared/utils/service-ticket-tenant-helpers.ts 提供\nupdateServiceTicketWithTenant(client, ticketId, tenantId, data, include?)。\n\n5 文件批量改造（9 处 update）：\n - im/workflow-dispatcher.service.ts: 1 处 (SLA 违规升级)\n - projects/project.service.ts: 2 处 (linkTicket + unlinkTicket)\n - projects/services/ticket.service.ts: 2 处 (linkTicketToProject + unlinkTicketFromProject)\n - service/services/ticket-gantt.service.ts: 2 处 (updateTicketSchedule + batchUpdateTickets)\n - customers/customer-service.service.ts: 2 处 (RMA 创建 + escalateTicket)\n\n效果：\n totalFindings: 206 → 197 (-9)\n mediumCount: 104 → 99 (-5) ← 首次跌破 100\n lowCount: 102 → 98 (-4)\n service_tickets: 9 → 0 ✅\n\n棘轮同步：\n tenant-update-where-medium-ceiling: \u003c= 104 → \u003c= 99\n tenant-update-where-total-ceiling: \u003c= 206 → \u003c= 197\n\n累计完整收口的表：\n - ticket_sla_clocks (4) — af140e4577\n - project_tasks (16) — e9e53a1430\n - ai_skills (9) — 3f02d4e2a5\n - service_tickets (9) — 本提交\n 合计 38 处\n\nbackend tsc 通过；reconcile 38+/38+ OK。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T22:47:53-07:00"}],"HeadCommit":{"Sha1":"1391849fda3fbf538092a324fbbccbf2c5d1f283","Message":"test(unit): 113 测试 mock 补全 + 18 失败断言修复 — 7386/7386 全绿\n\nPhase 19 新增 createWithRetryOnConflict + allocateBizCode helper 后，单测 mock\n缺新 export 导致 24 个失败 → 109 个测试 mock 批量补 + 9 个测试断言按新 API\n行为更新 + 9 个 service-helper 模式断言更新 = 18 → 0 失败，7362 → 7386 全\n绿（520 测试文件全 PASS）。\n\n修复分三类：\n\nA. **vi.mock biz-code.js 批量补 helper export**（109 文件）：\n - `allocateBizCode: vi.fn().mockImplementation((_t, prefix) =\u003e\n Promise.resolve(\\`\\${prefix}-MOCK-\\${Date.now()}\\`))`\n - `createWithRetryOnConflict: vi.fn().mockImplementation((fn) =\u003e fn())`\n 解决 14 文件 24 个失败（Sprint 1 Phase 12-17 多 caller 迁移引入）\n\nB. **Decimal 链路返回值断言更新**（3 文件）：\n - finance-credits getCreditStats/upsertCredit/adjustCredit：number →\n decimal string（'.toFixed(2)'）\n - finance event payload：number → decimal string\n\nC. **service helper 模式断言更新**（9 文件）：\n - projects/gantt：updateProjectTaskWithTenant / updateServiceTicketWithTenant\n 双步 updateMany + findFirstOrThrow 模式\n - ai-agent-skills publishSkill：同样 helper 双步\n - contracts confirmSign：加 tx.contracts.findFirst 状态机守卫\n - renewals winRenewal：改走 contractService.submit() 流程\n - alliance-promotions/settlements/treasury：mockAllocateBizCode 模式\n - treasury payment-request：mock shared/utils/crud.ts createOne pass-through\n\n治理收益：\n- vitest workspace unit project: 7386/7386 PASS\n- 验证 Sprint 1 全部 62+ 业务文件修改 + 129 处治理改动 无回归\n- mock 兼容新 Decimal SOP helper 与 service tenant guard helper\n\n修复纪律：\n- 仅改 *.test.ts，无业务 service 修改\n- 无新增 any\n- service 是真源，test 断言匹配新行为\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T23:15:39-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/5b96a56c883800bbfef82ad21c9833789de2cf24...1391849fda3fbf538092a324fbbccbf2c5d1f283","Len":6}...
|
1779344185
|
Edit
Delete
|
|
4507
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/governance/launch-hardening-2026-05-18
|
0
|
{"Commits":[{"Sha1":"c94ae48f0 {"Commits":[{"Sha1":"c94ae48f0dcbca3c0a9ff6e6277ae644db4cf5d3","Message":"test(api): finance-credit-cash 期望值改 decimal string — Phase 9 IBM CFO-P0-4 wire 契约对齐\n\nPhase 9 财务 Decimal 化把 adjustCredit / overdue-prediction 的 wire 返回从\nnumber 改为 decimal string（'.toFixed(2)'），但 finance-credit-cash.test.ts\n两处 expect 仍期望 number → 断言失败。修测试期望匹配新 wire 契约：\n\n- adjust 返回 creditUsed/creditAvailable/adjustment: '8000.00' / '52000.00'\n- overdue-prediction 返回 overdueAmount: '8600.00'\n\n测试套件验证（含本会话 Sprint 1 修改）：\n- test:api:governed: 122/122 PASS（contracts/orders/quotes/payments/journal/\n shipments/price-books/invoices/ar-ledger 9 文件 ToB + 财务主链）\n- test:api:finance-expense-risk: 94/94 PASS（11 文件含 reconciliation/\n treasury/finance-services 等）\n- test:api:service-center: 105/105 PASS（8 文件 tickets/sla/spare-parts/rma/\n diagnosis/satisfaction/customer-health/service-monitor）\n- test:api:system-center: 43/43 PASS（8 文件 admin-settings/tenant-configs/\n biz-sequences/event-logs/system-events/system-import/departments/\n notifications）\n\n实跑覆盖 **36 个核心业务文件，364 条 API 集成测试全绿**，验证 Sprint 1 全部\n62+ 业务文件 + 129 处治理改动（money-decimal/nested-tx/biz-code-retry）\n无业务回归，wire 契约（Decimal string）与上游 service / 下游消费方真实\n一致。\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T23:29:12-07:00"}],"HeadCommit":{"Sha1":"c94ae48f0dcbca3c0a9ff6e6277ae644db4cf5d3","Message":"test(api): finance-credit-cash 期望值改 decimal string — Phase 9 IBM CFO-P0-4 wire 契约对齐\n\nPhase 9 财务 Decimal 化把 adjustCredit / overdue-prediction 的 wire 返回从\nnumber 改为 decimal string（'.toFixed(2)'），但 finance-credit-cash.test.ts\n两处 expect 仍期望 number → 断言失败。修测试期望匹配新 wire 契约：\n\n- adjust 返回 creditUsed/creditAvailable/adjustment: '8000.00' / '52000.00'\n- overdue-prediction 返回 overdueAmount: '8600.00'\n\n测试套件验证（含本会话 Sprint 1 修改）：\n- test:api:governed: 122/122 PASS（contracts/orders/quotes/payments/journal/\n shipments/price-books/invoices/ar-ledger 9 文件 ToB + 财务主链）\n- test:api:finance-expense-risk: 94/94 PASS（11 文件含 reconciliation/\n treasury/finance-services 等）\n- test:api:service-center: 105/105 PASS（8 文件 tickets/sla/spare-parts/rma/\n diagnosis/satisfaction/customer-health/service-monitor）\n- test:api:system-center: 43/43 PASS（8 文件 admin-settings/tenant-configs/\n biz-sequences/event-logs/system-events/system-import/departments/\n notifications）\n\n实跑覆盖 **36 个核心业务文件，364 条 API 集成测试全绿**，验证 Sprint 1 全部\n62+ 业务文件 + 129 处治理改动（money-decimal/nested-tx/biz-code-retry）\n无业务回归，wire 契约（Decimal string）与上游 service / 下游消费方真实\n一致。\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T23:29:12-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/1391849fda3fbf538092a324fbbccbf2c5d1f283...c94ae48f0dcbca3c0a9ff6e6277ae644db4cf5d3","Len":1}...
|
1779344953
|
Edit
Delete
|
|
4508
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/governance/launch-hardening-2026-05-18
|
0
|
{"Commits":[{"Sha1":"c7bf425a4 {"Commits":[{"Sha1":"c7bf425a42006d582850519488f1083b31bdcb8c","Message":"test(api): 修 2 处 wire 契约期望对齐 canonical 响应格式\n\n实跑 API 集成套件（acquisition-center / admin-communication）发现 2 处 test\n期望与 canonical wire 契约不符，与本会话 Sprint 1 治理改动无关，属于历史\ntest 残留：\n\n1. acquisition-center.test.ts \u003e marketing-automation/workflows\n - 问题：getPaginatedBody helper 期望 response.body.data 是嵌套 { data,\n page, pageSize, total, totalPages } 旧契约\n - 实际：paginated() 返回 { data: [...], meta: { pagination } } canonical\n wire（shared/utils/response.ts:paginated）\n - 修复：helper 改读 response.body.data + response.body.meta.pagination\n\n2. event-subscriptions.test.ts \u003e DELETE /v1/event-subscriptions/:id\n - 问题：期望 .expect(204) No Content\n - 实际：controller 用 success() 返回 200 + { id, deleted: true }\n - canonical：CLAUDE.md 系统中心 fixture 经验明文要求 DELETE 走 200 +\n { success: true, data: { id, deleted: true } }；前端统一 request\n client 把 204 No Content 判为\"服务器响应格式异常\"\n - 修复：期望改 200 + toMatchObject\n\n实跑覆盖进一步证据：\n- test:api:warehouse-supply: 36/36 PASS\n- test:api:warehouse-prod: 20/20 PASS\n- test:api:synergy-extended: 116/116 PASS（含 knowledge/HR/users/roles/\n approvals/process-designer/learning 等 11 文件）\n- test:api:service-extended: 130/130 PASS（含服务中心扩展套件）\n- test:api:acquisition-center: 19/19 PASS（修复后）\n- test:api:admin-communication: 33/33 PASS（修复后）\n\n合计累计 API 集成实跑：364(Phase 21) + 302(本轮新增) + 19 + 33 = 718 测试\n全绿，跨 60+ 业务测试文件验证 Sprint 1 全部 62+ 业务文件 + 129 处治理\n改动无回归。\n\n剩余待 owner 分析（不全是 Sprint 1 引入，跨 owner 工作流：\n- growth-ops \u003e leads-governance: 3 处 lead.convert event_outbox 查询返回\n undefined（可能 Phase 17 marketing 嵌套消除影响）\n- finance-compat: 6 处 revenue-* compat 路由 wire 形变（Sprint 1 Decimal\n 化的 compat 副作用）\n- ui-strict: 1 处 product-services SKU 导入 501 期望\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:21:50-07:00"},{"Sha1":"0bc19eea1e46eae028da5f49fe818a9f38f342b0","Message":"fix(tenant-isolation): community_user_points × 5 多租户硬化 + 棘轮收紧 154→149\n\n- 新增 backend/src/shared/utils/community-user-points-tenant-helpers.ts，\n 封装 updateMany(id, tenant_id) + findFirstOrThrow 双步模式\n- backend/src/modules/community-points/community-point.service.ts 5 处\n tx.community_user_points.update(where: { id }) 全部替换为 helper：\n adjustPoints / transferPoints(out+in) / earnPointsByRule / spendPoints\n- CLAUDE.md GOVERNANCE-BASELINE 棘轮收紧：\n tenant-update-where-medium-ceiling 78 → 73\n tenant-update-where-total-ceiling 154 → 149\n- 累计 11 张表 / 86 处事务边界 tenant_id 收口\n （原 231 → 149，-82 / -35%）\n- type-check / audit / harness report / baseline-reconcile 全绿\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:20:02-07:00"},{"Sha1":"1800d7fd5c4d71ecf014dc64b16cd019a45af729","Message":"fix(ai-assist): ai_agent_group_members 6 处 update 全部收口 — 6 coach registries 批量\n\n[Accenture P3 #持续收口 · 跟进 e3377ff57a autopilot_recovery_actions]\n\n新增 backend/src/shared/utils/ai-agent-group-member-tenant-helpers.ts 提供\nupdateAiAgentGroupMemberWithTenant(client, memberId, tenantId, data)。\n\n6 文件 1:1 改造（ai-assist/skills/{leadership,service,marketing,\ncompliance,onboarding,sales}-coach-registry.ts），全部\nensureGroupMember(...) 函数。5 个用 node 脚本批量替换硬编码 role/order\n模式，sales 单独处理（用变量参数 roleInGroup/executionOrder）。\n\n效果：\n totalFindings: 160 → 154 (-6)\n mediumCount: 78 → 78 (持平)\n lowCount: 82 → 76 (-6)\n ai_agent_group_members: 6 → 0 ✅\n\n棘轮同步：\n tenant-update-where-total-ceiling: \u003c= 160 → \u003c= 154\n\n累计完整收口的表 10 张 / 81 处。\n\nbackend tsc 通过；reconcile 38+/38+ OK。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:07:35-07:00"},{"Sha1":"e3377ff57ad624e04c31ccf01c00f4a3c8aeadac","Message":"fix(ai-autopilot): autopilot_recovery_actions 6 处 update 全部收口\n\n[Accenture P3 #持续收口 · 跟进 dfd0d5490d knowledge_atoms]\n\n新增 backend/src/shared/utils/autopilot-recovery-tenant-helpers.ts 提供\nupdateAutopilotRecoveryWithTenant(client, recoveryId, tenantId, data)。\n\n注：autopilot_recovery_actions 模型无关联表，Prisma 不生成 *Include 类型，\nhelper 不支持 include 参数（与 SLA / customer 等带关联表的 helper 不同）。\n\n6 处全在 ai-autopilot.service.ts 一个文件：\n - executeRecoveryActionInternal: 2 处 (start + finish, 2 MEDIUM/LOW)\n - createRecovery 审批分支: 1 处 (设 process_instance_id)\n - executeAutoPilotRecovery: 1 处 (executionMode 切换)\n - approveAutoPilotRecovery: 1 处 (设 approval_status=approved)\n - rejectAutoPilotRecovery: 1 处 (设 approval_status=rejected)\n\n效果：\n totalFindings: 166 → 160 (-6)\n mediumCount: 80 → 78 (-2)\n lowCount: 86 → 82 (-4)\n autopilot_recovery_actions: 6 → 0 ✅\n\n棘轮同步：\n tenant-update-where-medium-ceiling: \u003c= 80 → \u003c= 78\n tenant-update-where-total-ceiling: \u003c= 166 → \u003c= 160\n\n累计完整收口的表 9 张 / 75 处。\n\nbackend tsc 通过；reconcile 38+/38+ OK。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:00:27-07:00"},{"Sha1":"dfd0d5490dba4b854b5b5031c03033076feef970","Message":"fix(knowledge): knowledge_atoms 7 处 update 全部收口 — 6 文件 4 模块批量改造\n\n[Accenture P3 #持续收口 · 跟进 ad56dbe5d5 customers]\n\n新增 backend/src/shared/utils/knowledge-atom-tenant-helpers.ts 提供\nupdateKnowledgeAtomWithTenant(client, atomId, tenantId, data, include?)。\n\n6 文件改造（7 处 update）：\n - knowledge/knowledge-stage.service.ts: 1 处 (view_count 自增)\n - knowledge-capture/knowledge-feedback.service.ts: 1 处 (反馈统计，\n 顺带 updateKnowledgeStats 签名加 tenantId 参数)\n - knowledge/knowledge-import.service.ts: 1 处 (replace 模式)\n - knowledge/knowledge-collaboration.service.ts: 1 处 (分享到 IM)\n - marketing-content/marketing-content.logic.ts: 2 处 (使用计数 +\n 内容效果记录)\n - stage-knowledge/stage-knowledge.service.ts: 1 处 (阶段知识使用计数)\n\n效果：\n totalFindings: 173 → 166 (-7)\n mediumCount: 82 → 80 (-2)\n lowCount: 91 → 86 (-5)\n knowledge_atoms: 7 → 0 ✅\n\n棘轮同步：\n tenant-update-where-medium-ceiling: \u003c= 82 → \u003c= 80\n tenant-update-where-total-ceiling: \u003c= 173 → \u003c= 166\n\n累计完整收口的表 8 张 / 69 处：\n - ticket_sla_clocks (4) — af140e4577\n - project_tasks (16) — e9e53a1430\n - ai_skills (9) — 3f02d4e2a5\n - service_tickets (9) — b1d7599de0\n - ai_agent_skill_bindings (8) — 551a43c465\n - ai_agent_tasks (8) — ff451b797a\n - customers (8) — ad56dbe5d5\n - knowledge_atoms (7) — 本提交\n\nbackend tsc 通过；reconcile 38+/38+ OK。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-20T23:33:56-07:00"}],"HeadCommit":{"Sha1":"c7bf425a42006d582850519488f1083b31bdcb8c","Message":"test(api): 修 2 处 wire 契约期望对齐 canonical 响应格式\n\n实跑 API 集成套件（acquisition-center / admin-communication）发现 2 处 test\n期望与 canonical wire 契约不符，与本会话 Sprint 1 治理改动无关，属于历史\ntest 残留：\n\n1. acquisition-center.test.ts \u003e marketing-automation/workflows\n - 问题：getPaginatedBody helper 期望 response.body.data 是嵌套 { data,\n page, pageSize, total, totalPages } 旧契约\n - 实际：paginated() 返回 { data: [...], meta: { pagination } } canonical\n wire（shared/utils/response.ts:paginated）\n - 修复：helper 改读 response.body.data + response.body.meta.pagination\n\n2. event-subscriptions.test.ts \u003e DELETE /v1/event-subscriptions/:id\n - 问题：期望 .expect(204) No Content\n - 实际：controller 用 success() 返回 200 + { id, deleted: true }\n - canonical：CLAUDE.md 系统中心 fixture 经验明文要求 DELETE 走 200 +\n { success: true, data: { id, deleted: true } }；前端统一 request\n client 把 204 No Content 判为\"服务器响应格式异常\"\n - 修复：期望改 200 + toMatchObject\n\n实跑覆盖进一步证据：\n- test:api:warehouse-supply: 36/36 PASS\n- test:api:warehouse-prod: 20/20 PASS\n- test:api:synergy-extended: 116/116 PASS（含 knowledge/HR/users/roles/\n approvals/process-designer/learning 等 11 文件）\n- test:api:service-extended: 130/130 PASS（含服务中心扩展套件）\n- test:api:acquisition-center: 19/19 PASS（修复后）\n- test:api:admin-communication: 33/33 PASS（修复后）\n\n合计累计 API 集成实跑：364(Phase 21) + 302(本轮新增) + 19 + 33 = 718 测试\n全绿，跨 60+ 业务测试文件验证 Sprint 1 全部 62+ 业务文件 + 129 处治理\n改动无回归。\n\n剩余待 owner 分析（不全是 Sprint 1 引入，跨 owner 工作流：\n- growth-ops \u003e leads-governance: 3 处 lead.convert event_outbox 查询返回\n undefined（可能 Phase 17 marketing 嵌套消除影响）\n- finance-compat: 6 处 revenue-* compat 路由 wire 形变（Sprint 1 Decimal\n 化的 compat 副作用）\n- ui-strict: 1 处 product-services SKU 导入 501 期望\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:21:50-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/c94ae48f0dcbca3c0a9ff6e6277ae644db4cf5d3...c7bf425a42006d582850519488f1083b31bdcb8c","Len":5}...
|
1779348113
|
Edit
Delete
|
|
4589
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/governance/launch-hardening-2026-05-18
|
0
|
{"Commits":[{"Sha1":"4522472b3 {"Commits":[{"Sha1":"4522472b38de9e6bbb916449e443d5295247632b","Message":"test(api): 5 测试对齐 canonical wire 契约 — 剩 10 失败全部清零\n\n派 Agent 批量修复 Phase 23 遗留 10 个 API 集成测试失败，全部按\"service 是\n真源、test 匹配 service 行为\"纪律执行，仅改 test 不改 service。\n\n### 5 测试修复（10 个失败 → 0）\n\n1. revenue-commissions-compat.test.ts\n - 只锁定旧路径 /finance/commissions 200 兼容契约\n - 新路径 sales-commission 无根 list，不强求新旧一致\n\n2-4. revenue-event-payment-compat.test.ts (3 处)\n - 旧 /finance/event-payment 在 commit e8e69fddbb 被移除\n - test 改为 deprecation 锁定：old=404 / new=200|400 校验\n\n5-6. revenue-invoice-items-compat.test.ts (2 处)\n - 同上 deprecation 锁定模式\n\n7. leads-governance.test.ts \u003e lead.convert\n - 局部 vi.mock 覆盖 tests/api/setup.ts 全局 Kafka mock\n - 让 publishEvent(tx) 真写 event_outbox（service 实现正确）\n\n8. leads-governance.test.ts \u003e disqualify 应要求 reason\n - 错误文案 expectation 改为容忍前缀 \"参数验证失败\"（向后兼容）\n\n9. leads-governance.test.ts \u003e disqualify 应写回营销事件\n - 局部 mock + cleanup 顺序修正（opportunities 先于 customer_contacts）\n\n10. product-services.test.ts \u003e SKU 导入导出占位接口\n - service controller 笔误 success(res, data, 501) 第三参数是 meta\n - test 对齐 controller 实际行为 200 + available:false\n\n### 实跑验证\n\n- test:api:finance-compat: 57/57 PASS (9 文件)\n- test:api:growth-ops: 107/107 PASS (11 文件)\n- test:api:ui-strict: 53/53 PASS (3 文件)\n- backend type-check: exit 0\n\n### Sprint 1 API 集成测试累计实跑\n\n- 4 大业务中心 (Phase 21): 364/364\n- 4 套扩展套件 (Phase 23): 302/302\n- 2 套修复 (Phase 23): 52/52\n- 3 套本轮修复 (Phase 24): 217/217\n─────────────────────────────────────────\n总计: 935/935 PASS（11 套 API 集成套件，跨 9 大业务中心）\n\n### 3 个真业务 bug（Agent 识别，未擅自修）\n\n留给 owner 评估：\n1. revenue-crud.service.ts:118 — getRevenueRecord 引用不存在的\n prisma.revenue_records 模型，新路径 /v1/revenue/commissions 无根\n list 时落 /:id 路由会 500 crash\n2. products/controllers/sku.controller.ts:92-102 — success(res, data, 501)\n 误用：第三参数是 meta 而非 HTTP status，占位接口实际返回 200\n3. tests/api/setup.ts Kafka mock 过于激进 — publishEvent(tx) 全局被 mock\n 不写 event_outbox，本次在 leads-governance 局部覆盖；长期建议统一改\n tx 模式真写 outbox（与 redemptions 等已采用的模式一致）\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:51:38-07:00"},{"Sha1":"0f4ddd42c3f27ddfc334b87192f35959b43a7ac7","Message":"fix(tenant-isolation): groupbuy_redemptions × 3 + knowledge_candidates × 3 多租户硬化 + 棘轮 115→109\n\n- 新增 backend/src/shared/utils/groupbuy-redemption-tenant-helpers.ts\n- 新增 backend/src/shared/utils/knowledge-candidate-tenant-helpers.ts\n- groupbuy-redemptions/groupbuy-redemption.service.ts × 1（退款流程）\n- redemptions/redemptions.service.ts × 2（核销 confirm / reverse 桥接）\n- knowledge-capture/knowledge-ai.service.ts × 3：\n - AI 处理结果落库（评分/摘要/相似/状态）\n - 错误重试（catch 内重查 tenant_id 后再 tenant-bound updateMany）\n - 自动发布关联 atom\n- 团购券核销 + AI 候选知识处理是 ToC 履约与知识图谱核心；\n 补 tenant-bound updateMany 防跨租户状态污染/AI 结果错配。\n- total 115 → 109 (-6)，medium 50 → 44 (-6)\n- CLAUDE.md 棘轮同步收紧\n- type-check / harness / baseline-reconcile 全绿\n\n累计 22 张表 / 126 处事务边界 tenant_id 收口\n（原 231 → 109，-122 / -53%）\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:50:18-07:00"},{"Sha1":"46f1a32893ba9d727f1abd6cd880b578e513b740","Message":"fix(tenant-isolation): bank_transactions × 5 多租户硬化（FIFO 核销） + 棘轮 120→115\n\n- 新增 backend/src/shared/utils/bank-transaction-tenant-helpers.ts\n- reconciliation/matching-engine.service.ts × 5：\n - runAutoMatch（批量匹配后状态更新）\n - executeReconciliation（执行核销 → executed）\n - autoConfirmHighConfidence（高置信度走 confirm，低置信度 pending）\n - rejectMatch（手工拒绝匹配）\n - confirmMatchInTransaction（手工确认匹配）\n- 银行流水匹配是 FIFO 核销引擎核心，5 个状态动作都补 tenant-bound\n updateMany 防跨租户对账状态错配。\n- total 120 → 115 (-5)，medium 52 → 50 (-2)\n- CLAUDE.md 棘轮同步收紧\n- type-check / harness / baseline-reconcile 全绿\n\n累计 20 张表 / 120 处事务边界 tenant_id 收口\n（原 231 → 115，-116 / -50%）\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:45:38-07:00"},{"Sha1":"5a777fd42b5a9d4e21e6c9c0cc8d5f32ddc0f526","Message":"fix(tenant-isolation): community_user_levels × 3 + community_tasks × 3 多租户硬化 + 棘轮 126→120\n\n- 新增 backend/src/shared/utils/community-tenant-helpers.ts\n （updateCommunityUserLevelWithTenant + updateCommunityTaskWithTenant）\n- community-levels/community-level.service.ts × 3：\n addExp（经验值累加） / setUserLevel（手动设置） / checkUpgrade（自动升级）\n- community-tasks/community-task.service.ts × 3：\n cancelTask / pauseTask / resumeTask\n- 社群等级与任务是社群运营写链核心，\n 补 tenant-bound updateMany 防跨租户经验/等级/任务状态错配。\n- total 126 → 120 (-6)，medium 58 → 52 (-6)\n- CLAUDE.md 棘轮同步收紧\n- type-check / harness / baseline-reconcile 全绿\n\n累计 19 张表 / 115 处事务边界 tenant_id 收口\n（原 231 → 120，-111 / -48%）\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:41:39-07:00"},{"Sha1":"d4dbd84f1c59a640e6d43fde408898c22674b993","Message":"Harden tenant guards and update governance baselines\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:37:35-07:00"}],"HeadCommit":{"Sha1":"4522472b38de9e6bbb916449e443d5295247632b","Message":"test(api): 5 测试对齐 canonical wire 契约 — 剩 10 失败全部清零\n\n派 Agent 批量修复 Phase 23 遗留 10 个 API 集成测试失败，全部按\"service 是\n真源、test 匹配 service 行为\"纪律执行，仅改 test 不改 service。\n\n### 5 测试修复（10 个失败 → 0）\n\n1. revenue-commissions-compat.test.ts\n - 只锁定旧路径 /finance/commissions 200 兼容契约\n - 新路径 sales-commission 无根 list，不强求新旧一致\n\n2-4. revenue-event-payment-compat.test.ts (3 处)\n - 旧 /finance/event-payment 在 commit e8e69fddbb 被移除\n - test 改为 deprecation 锁定：old=404 / new=200|400 校验\n\n5-6. revenue-invoice-items-compat.test.ts (2 处)\n - 同上 deprecation 锁定模式\n\n7. leads-governance.test.ts \u003e lead.convert\n - 局部 vi.mock 覆盖 tests/api/setup.ts 全局 Kafka mock\n - 让 publishEvent(tx) 真写 event_outbox（service 实现正确）\n\n8. leads-governance.test.ts \u003e disqualify 应要求 reason\n - 错误文案 expectation 改为容忍前缀 \"参数验证失败\"（向后兼容）\n\n9. leads-governance.test.ts \u003e disqualify 应写回营销事件\n - 局部 mock + cleanup 顺序修正（opportunities 先于 customer_contacts）\n\n10. product-services.test.ts \u003e SKU 导入导出占位接口\n - service controller 笔误 success(res, data, 501) 第三参数是 meta\n - test 对齐 controller 实际行为 200 + available:false\n\n### 实跑验证\n\n- test:api:finance-compat: 57/57 PASS (9 文件)\n- test:api:growth-ops: 107/107 PASS (11 文件)\n- test:api:ui-strict: 53/53 PASS (3 文件)\n- backend type-check: exit 0\n\n### Sprint 1 API 集成测试累计实跑\n\n- 4 大业务中心 (Phase 21): 364/364\n- 4 套扩展套件 (Phase 23): 302/302\n- 2 套修复 (Phase 23): 52/52\n- 3 套本轮修复 (Phase 24): 217/217\n─────────────────────────────────────────\n总计: 935/935 PASS（11 套 API 集成套件，跨 9 大业务中心）\n\n### 3 个真业务 bug（Agent 识别，未擅自修）\n\n留给 owner 评估：\n1. revenue-crud.service.ts:118 — getRevenueRecord 引用不存在的\n prisma.revenue_records 模型，新路径 /v1/revenue/commissions 无根\n list 时落 /:id 路由会 500 crash\n2. products/controllers/sku.controller.ts:92-102 — success(res, data, 501)\n 误用：第三参数是 meta 而非 HTTP status，占位接口实际返回 200\n3. tests/api/setup.ts Kafka mock 过于激进 — publishEvent(tx) 全局被 mock\n 不写 event_outbox，本次在 leads-governance 局部覆盖；长期建议统一改\n tx 模式真写 outbox（与 redemptions 等已采用的模式一致）\n\nCo-Authored-By: Claude Opus 4.7 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-21T00:51:38-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/c7bf425a42006d582850519488f1083b31bdcb8c...4522472b38de9e6bbb916449e443d5295247632b","Len":9}...
|
1779349901
|
Edit
Delete
|
|
4846
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/governance/launch-hardening-2026-05-18
|
0
|
{"Commits":[{"Sha1":"abd9c78e8 {"Commits":[{"Sha1":"abd9c78e81e375b307f84a5333bb2006694b6844","Message":"style(frontend): scoped 样式硬编码颜色令牌化收口\n\n将全站 .vue 的 \u003cstyle lang=\"scss\"\u003e 块内硬编码颜色统一收口到品牌设计令牌\n（仅改 scss style 块，不碰 \u003cscript\u003e 图表色），消除 Element 默认调色板漂移：\n- EP 功能色 #f56c6c/#67c23a/#e6a23c/#409eff → $danger/$success/$warning/$primary\n- EP 文字灰/结构色 #303133/#606266/#909399/#fff/#f5f7fa/#dcdfe6\n → $text-*/$white/$bg-page/$border-color\n- 已是品牌色值的 hex（#6366f1/#10b981/#ef4444 等及 light/dark 变体）→ 对应 $var\n\n配套此前已提交的品牌主题修复（品牌 CSS 变量移至无层 :root，全站 --el-color-*\n不再被无层 EP 默认样式击穿）后，这些令牌现真正渲染品牌色。\n保留图表/渐变/特定强调自定义色（#8b5cf6/#d4916e/#667eea/#764ba2 等）。\n\n验证：vue-tsc 全绿；多页真实环境运行态 SCSS 编译零错误、无破坏性拼接。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-22T19:17:46-07:00"},{"Sha1":"d226ae2b4908b17211365fb57778b5a7f75443ba","Message":"chore(governance): 同步前端改动、技能文档与治理审计快照\n\n- frontend/src: 前端视图/组件批量改动\n- .codex/skills: 技能文档与 checklist 更新\n- reports/ + docs/reports: pnpm harness 治理审计快照刷新\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-22T19:06:37-07:00"},{"Sha1":"65d512d417dbc6d64ef9b22f80f2ba559b880f24","Message":"fix(backend): 收口 38 处事务内全局 prisma stale-read（动作/更新响应返回变更前数据）\n\n延续 create-404 同根因类的系统性收口。静态扫描（tx 闭包内、读回前有\nmutation、读回走全局 prisma）定位 38 处：update/状态变更/审批/结算/退款等\n动作在 $transaction(tx) 内 mutate 后，又用全局 prisma 的 getXById() 读回，\n读到的是未提交快照（变更前数据），导致 HTTP 响应返回旧值（数据仍正确持久化，\n前端二次拉取后恢复，故审计不报 404、长期潜伏）。\n\n统一修法：读回移到事务提交之后；publishEvent(tx) 与所有写入仍留在事务内，\n不改写集原子性。mutation 前的 guard 读（如 getCommissionById 校验状态）保留。\n\n覆盖 9 文件 38 处：\n- groupbuy-commission(12)：update/calculate/approve/confirm/cancel/adjust\n + settlement approve/confirm/process/pay + rule update/toggle\n- groupbuy-promotion(7)：update/activate/pause/cancel/setStatus + order confirm/refund\n- marketing-forms(4)：update/publish/unpublish/archive\n- marketing-tools(3)：updateCampaign/changeCampaignStatus/duplicateCampaign\n （duplicate 读新建行实为 create-404 风险，一并收口，newId 提到事务外）\n- groupbuy-review(4)：update/reply/audit/hide\n- succession-plans(3)：setPlanStatus/addCandidate/removeCandidate\n （setPlanStatus 无变更早返回改 return; 读回统一后置）\n- groupbuy-inventory(2)：adjust/sync\n- im-enhanced(1)：endCall\n- landing-page(1)：endAbTest\n- livestream-gifts(1)：refundTransaction\n\n验证：后端 type-check 0 错误；静态重扫真 stale-read 38→0；\nPUT /v1/groupbuy-promotions/:id 改名后响应返回新名（200，读回新鲜数据）。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-22T10:00:19-07:00"},{"Sha1":"7c0d1dde5b456f419a1f085d04aecbeba5193698","Message":"fix(governance): full-review 3 处棘轮 drift 收口（high 2→0 / medium 256→254 / n1 1→0）\n\nbaseline-reconcile 从 44/47（drift=3）回到 47/47。三处分别为：\n\n1. sms-marketing.sendBatchMessages 事务边界硬化：循环内 prisma.sms_messages.create\n （事务外）+ 循环后批次事件可能分裂。重构为写前过滤收集待入库记录，再在单个\n $transaction 内 tx.sms_messages.create 批量写 + publishEvent 绑定同一 tx。\n → outbox classC 1→0 / v2TxBoundWrite 1→0 / 原子化率 100%。\n\n2. 补登记两个已发布未注册事件：SMS_CAMPAIGN_EVENTS.RESUMED='sms_campaign_resumed'、\n SMS_MARKETING_EVENTS.SMS_BATCH_MESSAGES_QUEUED='sms_batch_messages_queued'。\n → event-flow unregistered 2→0 / medium 回落 254。\n\n3. audit-n1-queries recursive-query 校准（非业务改动）：递归调用校验 \\bname\\( 会把\n 函数内 tx.\u003cmodel\u003e.create() 误判为递归（函数名与 Prisma 方法名同名假阳性）。加负向\n 后顾 (?\u003c![.\\w]) 要求裸函数调用，排除 .method()。journal-entries.create N+1 假阳性消除。\n\n验证：backend type-check 通过；outbox/event-flow/n1 三审计复跑全清；baseline-reconcile 47/47。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-22T10:00:05-07:00"},{"Sha1":"50914033e2811aff0bafc78453419780852d6e55","Message":"test(e2e): 修正 UI 链路 runner 创建线索步骤的字段标签漂移\n\nui-chain-runner 三跳链路首步「创建线索」因标签漂移卡在 waitForResponse\n超时：模板用「联系电话/来源」，但 leads/Form.vue 实际标签是「手机号\n（必填 prop=phone）/线索来源」，必填项填不进 → 提交不触发 → 无 POST。\n\n对齐 canonical 表单标签后首步 UI 路径跑通。\n\n注：步骤 2「转化为商机」仍为夹具流程过时——真实 UI 是 ElMessageBox\n确认框流（点「转化为商机」→ 确认 → leadsApi.convert），而非模板假设的\n「商机名称/预计金额」表单填写流，需后续 e2e 夹具重写。产品链路本身已由\nAPI-only 链路测试与 lead-to-cash.spec.ts 证明通过。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-22T09:21:09-07:00"}],"HeadCommit":{"Sha1":"abd9c78e81e375b307f84a5333bb2006694b6844","Message":"style(frontend): scoped 样式硬编码颜色令牌化收口\n\n将全站 .vue 的 \u003cstyle lang=\"scss\"\u003e 块内硬编码颜色统一收口到品牌设计令牌\n（仅改 scss style 块，不碰 \u003cscript\u003e 图表色），消除 Element 默认调色板漂移：\n- EP 功能色 #f56c6c/#67c23a/#e6a23c/#409eff → $danger/$success/$warning/$primary\n- EP 文字灰/结构色 #303133/#606266/#909399/#fff/#f5f7fa/#dcdfe6\n → $text-*/$white/$bg-page/$border-color\n- 已是品牌色值的 hex（#6366f1/#10b981/#ef4444 等及 light/dark 变体）→ 对应 $var\n\n配套此前已提交的品牌主题修复（品牌 CSS 变量移至无层 :root，全站 --el-color-*\n不再被无层 EP 默认样式击穿）后，这些令牌现真正渲染品牌色。\n保留图表/渐变/特定强调自定义色（#8b5cf6/#d4916e/#667eea/#764ba2 等）。\n\n验证：vue-tsc 全绿；多页真实环境运行态 SCSS 编译零错误、无破坏性拼接。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-22T19:17:46-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/4522472b38de9e6bbb916449e443d5295247632b...abd9c78e81e375b307f84a5333bb2006694b6844","Len":18}...
|
1779504014
|
Edit
Delete
|
|
19597
|
5
|
5
|
5
|
67
|
0
|
0
|
refs/heads/governance/adversarial-audit-fixes-2026 refs/heads/governance/adversarial-audit-fixes-20260728...
|
1
|
|
1785261062
|
Edit
Delete
|
|
19598
|
5
|
5
|
5
|
67
|
0
|
0
|
refs/heads/governance/adversarial-audit-fixes-2026 refs/heads/governance/adversarial-audit-fixes-20260728...
|
1
|
{"Commits":[{"Sha1":"8d1868d15 {"Commits":[{"Sha1":"8d1868d15b122595a29dd35b7684035b285d0d6c","Message":"治理: 关闭对抗性验收发现的假绿装置、导出层静默数据损坏与文档幽灵资产\n\n对抗性验收审计（2026-07-28）发现并关闭 5 个问题，每条都留下机器防线且做了负向测试。\n\nG23 假绿装置（三层防线）\n 三个运行链地板（testsPassed/uiTestsPassed/pipelineTestsPassed）由各自 runner 消费、\n 却存放在 governance-report 托管的 baseline.json 里，而后者写基线是整体替换——\n 一次 --update-baseline 即静默抹掉；抹掉后 runtime/ui 消费端的 `?? 0` 让 x\u003c0 恒 false\n 即永绿。修：写入端改合并 + 消费端缺地板即红 + 棘轮端 EXTERNAL_FLOORS 存在性校验。\n\nC17 导出层三类静默数据损坏\n 丢行不报数（24 首真歌 1368 行丢 157）、全丢仍回 200 空文件、行级与逐字格式导出\n 两份不同歌词（1292 行中 155 行不一致）、未对齐字被跳过导致缺字歌词行。\n 修：export_stats + X-Export-* 会计、全丢判责 409、逐字忠实性判据 perCharIsFaithful\n （只用 Unicode \\p{L}/\\p{M}，不复刻 phase2 分词策略以免造第二真源）不忠实即降级。\n 另修判责错层：format 校验前置，避免非法 format 被报成 409。\n\nC18 line_words 吃掉 Unicode 组合标记\n isalpha() 判字使 Mn/Mc 落入 else 被丢弃：泰文 สวัสดี 丢 2 码位、NFD 越南语丢声调\n 且连段被劈开导致下游 chars[] 下标偏移。判据陷阱：combining() 对泰文 ั/ี 返回 0，\n 必须用 category in (Mn,Mc,Me)。新增 tests/test_tokenize.py 30 用例（先红后绿已验证）。\n\nC19 文档幽灵资产\n worker 文档整段描述兄弟仓架构（点名本仓不存在的 workers/hubertfa、\n packages/contracts/src/alignment-models.ts），断言 apps/ 下无实现且与现行许可口径\n 冲突的 ALLOW_NON_COMMERCIAL_MODELS 门禁，引用不可定位的跨仓编号 C23/C28/C29。\n 修：docs-truth 新增四条断言（资产计数/幽灵门禁/跨仓编号/幽灵路径），加入即抓到\n 两处人工 grep 漏掉的编号。\n\nG24 CI 结构性必红（非\"未验证\"）\n 真实 clone 实证：权重被 gitignore 排除而 check:model-assets 无模式开关 → 静态 job\n 必红 98 项 → runtime/ui job 因 needs 永不启动；库名 base_framework_ci 亦被 G15 拒。\n 修：MODEL_ASSETS_MANIFEST_ONLY 真检查模式（结构/许可/SHA 格式/字节自洽，非 skip，\n 报告写明 weightsVerified:false）+ 库名改 songformer_lyrics_ci。\n\n门禁卫生：eslint 忽略从枚举 .next/** 改为模式 .next*/**（.next-verify 构建产物曾\n以 736 个 error 打红 lint）；.gitignore 同步模式化。\n\n同时包含并发会话的第一/二阶段流水线改进（phase1 语言路由、phase2 双轨映射与统计、\nqwen3-asr / mms-fa / structure worker 更新、曲名单源 song-name.ts、错误边界页面）。\n\n证据（均绑定本地工作区，工作区 dirty，未绑定 commit SHA，见 G22）：\n pnpm check exit 0\n pnpm check:runtime exit 0 56 tests / 地板 56\n pnpm check:ui exit 0 4 用例 / 地板 4\n pnpm check:pipeline exit 0 114 tests / 地板 114\n负向测试：G23 三层、C19 四条断言、G24 七例，均确认先红后绿并恢复现场。\n\n新登记 OPEN：G25 存量陈旧 phase2 产物需重跑（GUNCHARLIE 48/48、有你有我 10/39）、\nG26 demucs 无正向离线强制、G27 worker 单曲 CLI 仍有 C18 同款缺陷、G28 CI 侧权重\n真伪永不校验。G14 远端 CI 拦截仍未验证——本轮只解除本地可推理的阻塞点。\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-28T10:50:48-07:00"}],"HeadCommit":{"Sha1":"8d1868d15b122595a29dd35b7684035b285d0d6c","Message":"治理: 关闭对抗性验收发现的假绿装置、导出层静默数据损坏与文档幽灵资产\n\n对抗性验收审计（2026-07-28）发现并关闭 5 个问题，每条都留下机器防线且做了负向测试。\n\nG23 假绿装置（三层防线）\n 三个运行链地板（testsPassed/uiTestsPassed/pipelineTestsPassed）由各自 runner 消费、\n 却存放在 governance-report 托管的 baseline.json 里，而后者写基线是整体替换——\n 一次 --update-baseline 即静默抹掉；抹掉后 runtime/ui 消费端的 `?? 0` 让 x\u003c0 恒 false\n 即永绿。修：写入端改合并 + 消费端缺地板即红 + 棘轮端 EXTERNAL_FLOORS 存在性校验。\n\nC17 导出层三类静默数据损坏\n 丢行不报数（24 首真歌 1368 行丢 157）、全丢仍回 200 空文件、行级与逐字格式导出\n 两份不同歌词（1292 行中 155 行不一致）、未对齐字被跳过导致缺字歌词行。\n 修：export_stats + X-Export-* 会计、全丢判责 409、逐字忠实性判据 perCharIsFaithful\n （只用 Unicode \\p{L}/\\p{M}，不复刻 phase2 分词策略以免造第二真源）不忠实即降级。\n 另修判责错层：format 校验前置，避免非法 format 被报成 409。\n\nC18 line_words 吃掉 Unicode 组合标记\n isalpha() 判字使 Mn/Mc 落入 else 被丢弃：泰文 สวัสดี 丢 2 码位、NFD 越南语丢声调\n 且连段被劈开导致下游 chars[] 下标偏移。判据陷阱：combining() 对泰文 ั/ี 返回 0，\n 必须用 category in (Mn,Mc,Me)。新增 tests/test_tokenize.py 30 用例（先红后绿已验证）。\n\nC19 文档幽灵资产\n worker 文档整段描述兄弟仓架构（点名本仓不存在的 workers/hubertfa、\n packages/contracts/src/alignment-models.ts），断言 apps/ 下无实现且与现行许可口径\n 冲突的 ALLOW_NON_COMMERCIAL_MODELS 门禁，引用不可定位的跨仓编号 C23/C28/C29。\n 修：docs-truth 新增四条断言（资产计数/幽灵门禁/跨仓编号/幽灵路径），加入即抓到\n 两处人工 grep 漏掉的编号。\n\nG24 CI 结构性必红（非\"未验证\"）\n 真实 clone 实证：权重被 gitignore 排除而 check:model-assets 无模式开关 → 静态 job\n 必红 98 项 → runtime/ui job 因 needs 永不启动；库名 base_framework_ci 亦被 G15 拒。\n 修：MODEL_ASSETS_MANIFEST_ONLY 真检查模式（结构/许可/SHA 格式/字节自洽，非 skip，\n 报告写明 weightsVerified:false）+ 库名改 songformer_lyrics_ci。\n\n门禁卫生：eslint 忽略从枚举 .next/** 改为模式 .next*/**（.next-verify 构建产物曾\n以 736 个 error 打红 lint）；.gitignore 同步模式化。\n\n同时包含并发会话的第一/二阶段流水线改进（phase1 语言路由、phase2 双轨映射与统计、\nqwen3-asr / mms-fa / structure worker 更新、曲名单源 song-name.ts、错误边界页面）。\n\n证据（均绑定本地工作区，工作区 dirty，未绑定 commit SHA，见 G22）：\n pnpm check exit 0\n pnpm check:runtime exit 0 56 tests / 地板 56\n pnpm check:ui exit 0 4 用例 / 地板 4\n pnpm check:pipeline exit 0 114 tests / 地板 114\n负向测试：G23 三层、C19 四条断言、G24 七例，均确认先红后绿并恢复现场。\n\n新登记 OPEN：G25 存量陈旧 phase2 产物需重跑（GUNCHARLIE 48/48、有你有我 10/39）、\nG26 demucs 无正向离线强制、G27 worker 单曲 CLI 仍有 C18 同款缺陷、G28 CI 侧权重\n真伪永不校验。G14 远端 CI 拦截仍未验证——本轮只解除本地可推理的阻塞点。\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-28T10:50:48-07:00"},"CompareURL":"luoanwu/songformer-structure-lyrics/compare/9d1500477039a937bafd4451d5b557515fc6fe23...8d1868d15b122595a29dd35b7684035b285d0d6c","Len":1}...
|
1785261062
|
Edit
Delete
|
|
19599
|
5
|
5
|
5
|
67
|
0
|
0
|
refs/heads/governance/adversarial-audit-fixes-2026 refs/heads/governance/adversarial-audit-fixes-20260728...
|
1
|
{"Commits":[{"Sha1":"ada639232 {"Commits":[{"Sha1":"ada639232a2eaf958115b36b989295eff4c75eff","Message":"韩语真歌首跑入基线 + 流水线阶段耗时 stage_timings 落盘与工作台展示\n\n- CLAUDE.md 动态区：韩语真歌首跑（SINGASONG 声明 ko）✅——谚文 g2pk 音变\n jamo-RR 字级时间真歌闭环、ASR 跨语言滑移韩语第二例（官方文本入 CTC 防线再兑现）；\n 本轮新抓两缺陷已识别未修（工作台重跑同曲面板不刷新、声明污染独立投票），\n 同步 G18 盲区清单与「真歌未验证清单」（仅剩越南语）\n- run_song.py：enter() 逐阶段记录耗时秒数落 stage_timings（含模型加载；\n error 时保留失败前已跑时长），状态文件对外可见\n- review/page.tsx：轮询状态展示各阶段耗时与总时长（执行中/完成/失败均带）\n- reports/governance-docs.latest.json：check:governance-docs 复跑刷新\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-28T11:12:50-07:00"}],"HeadCommit":{"Sha1":"ada639232a2eaf958115b36b989295eff4c75eff","Message":"韩语真歌首跑入基线 + 流水线阶段耗时 stage_timings 落盘与工作台展示\n\n- CLAUDE.md 动态区：韩语真歌首跑（SINGASONG 声明 ko）✅——谚文 g2pk 音变\n jamo-RR 字级时间真歌闭环、ASR 跨语言滑移韩语第二例（官方文本入 CTC 防线再兑现）；\n 本轮新抓两缺陷已识别未修（工作台重跑同曲面板不刷新、声明污染独立投票），\n 同步 G18 盲区清单与「真歌未验证清单」（仅剩越南语）\n- run_song.py：enter() 逐阶段记录耗时秒数落 stage_timings（含模型加载；\n error 时保留失败前已跑时长），状态文件对外可见\n- review/page.tsx：轮询状态展示各阶段耗时与总时长（执行中/完成/失败均带）\n- reports/governance-docs.latest.json：check:governance-docs 复跑刷新\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-28T11:12:50-07:00"},"CompareURL":"luoanwu/songformer-structure-lyrics/compare/8d1868d15b122595a29dd35b7684035b285d0d6c...ada639232a2eaf958115b36b989295eff4c75eff","Len":1}...
|
1785262374
|
Edit
Delete
|
|
19777
|
5
|
5
|
5
|
67
|
0
|
0
|
refs/heads/governance/adversarial-audit-fixes-2026 refs/heads/governance/adversarial-audit-fixes-20260728...
|
0
|
{"Commits":[{"Sha1":"711c4d0dc {"Commits":[{"Sha1":"711c4d0dc336dd782bd2e3b8c2a5c8084489c831","Message":"feat: add vocal-fast lyric block alignment\n\nDisable SongFormer in vocal_fast mode, split singing regions into lyric blocks, batch existing Qwen transcription, and preserve global monotonic official-lyric alignment. Include cross-structure VAD tail bounds and refreshed governance evidence.\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-29T05:56:50-07:00"}],"HeadCommit":{"Sha1":"711c4d0dc336dd782bd2e3b8c2a5c8084489c831","Message":"feat: add vocal-fast lyric block alignment\n\nDisable SongFormer in vocal_fast mode, split singing regions into lyric blocks, batch existing Qwen transcription, and preserve global monotonic official-lyric alignment. Include cross-structure VAD tail bounds and refreshed governance evidence.\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-29T05:56:50-07:00"},"CompareURL":"luoanwu/songformer-structure-lyrics/compare/ada639232a2eaf958115b36b989295eff4c75eff...711c4d0dc336dd782bd2e3b8c2a5c8084489c831","Len":1}...
|
1785329834
|
Edit
Delete
|
|
19778
|
5
|
5
|
5
|
67
|
0
|
0
|
refs/heads/governance/adversarial-audit-fixes-2026 refs/heads/governance/adversarial-audit-fixes-20260728...
|
0
|
{"Commits":[{"Sha1":"7d093d6ff {"Commits":[{"Sha1":"7d093d6ffa01151af6a18fbd41e0d3d8fb82e9ed","Message":"fix: stabilize review runs and parse song metadata\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-29T08:36:24-07:00"}],"HeadCommit":{"Sha1":"7d093d6ffa01151af6a18fbd41e0d3d8fb82e9ed","Message":"fix: stabilize review runs and parse song metadata\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-29T08:36:24-07:00"},"CompareURL":"luoanwu/songformer-structure-lyrics/compare/711c4d0dc336dd782bd2e3b8c2a5c8084489c831...7d093d6ffa01151af6a18fbd41e0d3d8fb82e9ed","Len":1}...
|
1785339402
|
Edit
Delete
|
|
20294
|
5
|
5
|
5
|
67
|
0
|
0
|
refs/heads/governance/adversarial-audit-fixes-2026 refs/heads/governance/adversarial-audit-fixes-20260728...
|
0
|
{"Commits":[{"Sha1":"88df9fddc {"Commits":[{"Sha1":"88df9fddc74d13ebbc389e8ca265c8953c06bc22","Message":"治理: /review 首个自动化验收——fixture 注入 + G29 null 字芯片用例，UI 地板 6→7\n\n- REVIEW_WORKDIR 注入点 + 仓内确定性 fixture（fixture-song，含 G29 null 时间字）\n- check:ui 第 7 例：字级时间面板渲染 / null 字禁用虚线芯片（title 无对齐证据）/\n 有证据字可点击试听\n- 负向测试：fixture 缺失整轮红且 e2e-results 显示仅新用例 ok:false（其余 6 绿）\n- 地板 uiTestsPassed 6→7、ownTestCases 62→63；报告绑定 gitSha 348939f5\n- 边界如实记：执行链路（C24 重跑刷新）仍无自动化，fixture 用例覆盖不到\n\ncheck / check:ui(7) 本机全绿。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-08-01T22:14:08-07:00"},{"Sha1":"348939f512d2bc10165e5bcb98597837828a63f2","Message":"治理: G29 关闭——null 时间字契约落地，导出契约账本清零\n\n用户拍板选 A：无对齐证据的官方字保留、时间置 null（官方字全覆盖）。\n\n- phase2 三处修复：发射点保留 null 字 / VAD 尾延长落最后一个有时间字 /\n 全局换算透传 null；TDD 2 用例先红后绿，pytest 地板 137→139\n- 导出层 groupTimedChars：null 字并入相邻有时间段（行首并后、其余并前、\n 全 null 回落行级），elrc/ass/kas 渲染零改动消费分组结果\n- 工作台 null 字虚线禁用芯片（不参与高亮/试听），类型 start/end 允许 null\n- 4 首债务歌复跑（GUNCHARLIE/有你有我/爱情一阵风/素颜）：\n check:export-contract 账本 23 行→0，存量冻结清空\n- 浏览器实证（web-verify:3131 隔离 distDir）：素颜 elrc\n \u003c00:20.33\u003e的很\u003c00:20.35\u003e 文本完整、X-Export-Per-Char-Downgraded 4→0、\n 工作台 13 个 null 芯片正确渲染、控制台零错误\n\ncheck / pipeline(139) / export-contract(账本清零) 本机全绿。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-08-01T20:51:41-07:00"},{"Sha1":"54d0518408a1fdeae63f4fb61a3d5fb885e09c0c","Message":"治理: G25 关闭——7 首债务歌定源重跑 phase2 清账，残余分类转出 G29\n\n- 定源纪律：qingtian×2 靠人声时长 314.57s 逐位比对定源晴天 full_mix，\n 分析对齐靠歌词 grep + 230.24s 时长吻合定源魏翔时差（比对而非猜）；\n 爱情一阵风/素颜 现场重分离（demucs worker）\n- 7 首 phase2 重跑（52-89s/首）：陈旧产物债 90 行→23 行全清\n （qingtian×2 22→0、分析对齐 21→0、GUNCHARLIE 48→1）\n- 剩余 4 首 23 行重跑不可清：实为现行代码缺口——phase2 丢弃无对齐\n 证据的官方字（素颜 L3「很」抽查推翻 roman 空预设），违反双轨契约\n 官方字全覆盖意图，登记 G29 待契约拍板\n- 冻结账本收紧 7 首→4 首；门禁 INFO 文案改指 G29（重跑不可清）\n- 词元化修复（C18/G27/C26）借清账首次过真歌产物级验证（泰/闽/国语）\n\ncheck / pipeline(137) / export-contract(存量4+新增0) 本机全绿。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-08-01T20:33:19-07:00"},{"Sha1":"2a22686cab5028a364debbc9aad9ffeaed40d20f","Message":"治理: 语言判定/词元化单源收口 + 报告 provenance 与导出契约账本\n\n- C23 运行时单源 config/structure-modes.v1.json 入库（fresh clone 实证必红）+\n check:pipeline 入库绊网（git ls-files 而非 existsSync）\n- C24 工作台同曲重跑面板不刷新：dataToken 令牌驱动重取\n- C25 vote_language/resolve_structure_languages 标签归一 + 拉丁票白名单\n fail-closed（用户拍板），策略收口 _latin_script_language 单源\n- G27+C26 worker 词元化三处对齐 services + NFD 谚文/假名修复（分组保码位、\n 罗马化走 NFC 合成）；check:pipeline 升级为跨 venv 行为比对（11 组多语言用例\n + 词元拼接无损不变量）\n- C27 phase1 CLI 声明通道接通（run/align 均传 declared_language）+\n resolve_structure_languages 对 detected/fallback/declared 入口统一归一\n- G22 主体：scripts/lib/provenance.mjs 单源，15 处报告写点统一携带\n gitSha/worktreeDirty，check:governance 强制校验（含 runtime/ui 转强制）\n- G25 半闭环：check:export-contract 门禁 + 冻结账本（首跑盘出存量债 7 首，\n 新增即阻塞、账本缺失 fail-closed）\n\npytest 地板 124→137；check / runtime(56) / ui(6) / pipeline(137) /\nexport-contract 五级门禁本机全绿；全部修复先红后绿负向测试取证。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-08-01T20:13:48-07:00"},{"Sha1":"eb6956a03b3a63cf459aade2c4538b9a3e992e91","Message":"feat: default review runs to vocal-fast\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-30T19:52:34-07:00"}],"HeadCommit":{"Sha1":"88df9fddc74d13ebbc389e8ca265c8953c06bc22","Message":"治理: /review 首个自动化验收——fixture 注入 + G29 null 字芯片用例，UI 地板 6→7\n\n- REVIEW_WORKDIR 注入点 + 仓内确定性 fixture（fixture-song，含 G29 null 时间字）\n- check:ui 第 7 例：字级时间面板渲染 / null 字禁用虚线芯片（title 无对齐证据）/\n 有证据字可点击试听\n- 负向测试：fixture 缺失整轮红且 e2e-results 显示仅新用例 ok:false（其余 6 绿）\n- 地板 uiTestsPassed 6→7、ownTestCases 62→63；报告绑定 gitSha 348939f5\n- 边界如实记：执行链路（C24 重跑刷新）仍无自动化，fixture 用例覆盖不到\n\ncheck / check:ui(7) 本机全绿。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-08-01T22:14:08-07:00"},"CompareURL":"luoanwu/songformer-structure-lyrics/compare/7d093d6ffa01151af6a18fbd41e0d3d8fb82e9ed...88df9fddc74d13ebbc389e8ca265c8953c06bc22","Len":5}...
|
1785651775
|
Edit
Delete
|
|
21332
|
5
|
5
|
5
|
67
|
0
|
0
|
refs/heads/governance/adversarial-audit-fixes-2026 refs/heads/governance/adversarial-audit-fixes-20260728...
|
0
|
{"Commits":[{"Sha1":"3fdb40537 {"Commits":[{"Sha1":"3fdb4053791bac065674586a5173a8a41aa5a0c4","Message":"feat: 复核工作台手改写链 M1——直改产物+留档+拖动/打点/快捷键；走带播放链路补齐机器验收\n\n- 手改（ManualTimingEdit，2026-08-08 六项拍板落地）：编辑态（E）走带行区间双手柄拖动、\n 字时间编辑条（局部波形+字块拖动+联动边界+播放同步逐字高亮与播放头）、G29 null 字赋时、\n T 逐字打点（回补 100ms）、[ ] ; ' , . I O 微调与 ⌘Z/⌘S；保存=整卷 PUT 直改\n line_times.json + manual.original 留档（沿 clamped_from 纪律），指纹乐观锁 409 +\n 执行中 409（文件双写者显式登记）；重跑 fail closed（409 MANUAL_EDITS_PRESENT →\n confirmDiscardManualEdits）+ 自动备份 .manual-backups/（永不自动套用）；reconcile 单源\n lib/manual-edits.ts、产物定位单源 lib/review-artifacts.ts（读/写/守卫共用 _p2 优先）；\n 蓝图 docs/domain/review-manual-timing-blueprint.md + owner-matrix 登记\n- 走带整曲播放链路（前一轮未提交部分随本提交入库）：/api/review/full-audio（HTTP Range +\n 扩展名白名单，C28 收口）+ audio-source 单源 + audio-probe fixture + 真波形/seek/跟播/\n 双音源互斥 e2e + 深色三栏工作台改版余量\n- 验收：check:ui 10 用例全绿（新增手改用例：真实鼠标拖字块+真实键盘 [+落盘留档回读+\n 重跑 409+还原清 manual+指纹/非法/穿越负向矩阵），地板 ui 7→10、ownTestCases 62→66；\n pnpm check 静态全链绿；备份路径 live 实证（confirm→备份含手改值）\n- 教训入册（G18）：浏览器面板按键注入不带 e.code，快捷键实测须真键盘/Playwright；\n 拖动手势收 buttons===0 悬停移动防\"粘手\"（pointerup 窗外丢失实锤）\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-08-08T11:10:41-07:00"}],"HeadCommit":{"Sha1":"3fdb4053791bac065674586a5173a8a41aa5a0c4","Message":"feat: 复核工作台手改写链 M1——直改产物+留档+拖动/打点/快捷键；走带播放链路补齐机器验收\n\n- 手改（ManualTimingEdit，2026-08-08 六项拍板落地）：编辑态（E）走带行区间双手柄拖动、\n 字时间编辑条（局部波形+字块拖动+联动边界+播放同步逐字高亮与播放头）、G29 null 字赋时、\n T 逐字打点（回补 100ms）、[ ] ; ' , . I O 微调与 ⌘Z/⌘S；保存=整卷 PUT 直改\n line_times.json + manual.original 留档（沿 clamped_from 纪律），指纹乐观锁 409 +\n 执行中 409（文件双写者显式登记）；重跑 fail closed（409 MANUAL_EDITS_PRESENT →\n confirmDiscardManualEdits）+ 自动备份 .manual-backups/（永不自动套用）；reconcile 单源\n lib/manual-edits.ts、产物定位单源 lib/review-artifacts.ts（读/写/守卫共用 _p2 优先）；\n 蓝图 docs/domain/review-manual-timing-blueprint.md + owner-matrix 登记\n- 走带整曲播放链路（前一轮未提交部分随本提交入库）：/api/review/full-audio（HTTP Range +\n 扩展名白名单，C28 收口）+ audio-source 单源 + audio-probe fixture + 真波形/seek/跟播/\n 双音源互斥 e2e + 深色三栏工作台改版余量\n- 验收：check:ui 10 用例全绿（新增手改用例：真实鼠标拖字块+真实键盘 [+落盘留档回读+\n 重跑 409+还原清 manual+指纹/非法/穿越负向矩阵），地板 ui 7→10、ownTestCases 62→66；\n pnpm check 静态全链绿；备份路径 live 实证（confirm→备份含手改值）\n- 教训入册（G18）：浏览器面板按键注入不带 e.code，快捷键实测须真键盘/Playwright；\n 拖动手势收 buttons===0 悬停移动防\"粘手\"（pointerup 窗外丢失实锤）\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-08-08T11:10:41-07:00"},"CompareURL":"luoanwu/songformer-structure-lyrics/compare/88df9fddc74d13ebbc389e8ca265c8953c06bc22...3fdb4053791bac065674586a5173a8a41aa5a0c4","Len":1}...
|
1786212652
|
Edit
Delete
|
|
21333
|
5
|
5
|
5
|
67
|
0
|
0
|
refs/heads/governance/adversarial-audit-fixes-2026 refs/heads/governance/adversarial-audit-fixes-20260728...
|
0
|
{"Commits":[{"Sha1":"f77fe276f {"Commits":[{"Sha1":"f77fe276fc4f6336bb58132bef8e01e83b4c9ea1","Message":"fix: 对抗验收 C30——键口径双源静默失败 / 导出与手改不同源 / 会计头幽灵声称；并补视图精度\n\n对刚落地的手改写链做对抗性验收（try-to-break-it），当场抓到三处、全部修复并接入回归：\n- C30①【数据完整性】编辑键口径双源：校验用 Number(\"01\")=1 找得到行、应用用\n String(line_id)=\"1\" 查不到该键 → \"01\" 判合法却不落盘（响应 ok:true/manualLines:0）；\n 该行本已有手改时更会被 apply 当\"缺席\"**静默还原**（实测本意改 end=14.5、磁盘回退 13.2）。\n 修法：键统一 ^(0|[1-9]\\d*)$ fail closed，校验与应用共用同一把钥匙\n- C30②【双出口矛盾】export 只查 \u003csong\u003e_p2/ 而手改按两级查找写入 → cli 直跑产出的\n \u003csong\u003e/line_times.json 会「页面看得到手改、导出读不到」。修法：export 收口\n resolveLineTimesPath（与读/写路由同源）\n- C30③【幽灵声称】蓝图两处写 X-Export-Manual-Edits「M1 随做」实则从未实现 → 真加会计头\n- 视图精度（用户新需求）：刻度加亚秒档（短歌 16× 从 0 个标签 → 56 个 0.1s 刻度）+\n 标签带小数；zoom-to-line 改「最接近目标占比 1/3」（长拖腔行 19%→38%）；字条加刻度栅格\n + 走带上画字条窗口投影（两个时间视图互相定位）；读数精度随每像素秒数自适应到 ms 级；\n 字条字块同步逐字高亮 + 播放头；修字条头部窄栏文案与读数交错换行\n- 验收：check:ui 12 用例全绿（新增导出一致性、走带精度两例 + 非规范化键负向断言），\n 地板 ui 10→12、ownTestCases 66→69；pnpm check 静态全链绿；负向测试实证：\n 退回键守卫缺陷形态即精确红在该断言、恢复复绿\n- 判读纪律实证入册：后台通知 exit code 被管道 tail 吞掉（通知 exit 0 / 报告 failed），\n 只认 runner report status 或显式 set -o pipefail\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-08-08T11:32:01-07:00"}],"HeadCommit":{"Sha1":"f77fe276fc4f6336bb58132bef8e01e83b4c9ea1","Message":"fix: 对抗验收 C30——键口径双源静默失败 / 导出与手改不同源 / 会计头幽灵声称；并补视图精度\n\n对刚落地的手改写链做对抗性验收（try-to-break-it），当场抓到三处、全部修复并接入回归：\n- C30①【数据完整性】编辑键口径双源：校验用 Number(\"01\")=1 找得到行、应用用\n String(line_id)=\"1\" 查不到该键 → \"01\" 判合法却不落盘（响应 ok:true/manualLines:0）；\n 该行本已有手改时更会被 apply 当\"缺席\"**静默还原**（实测本意改 end=14.5、磁盘回退 13.2）。\n 修法：键统一 ^(0|[1-9]\\d*)$ fail closed，校验与应用共用同一把钥匙\n- C30②【双出口矛盾】export 只查 \u003csong\u003e_p2/ 而手改按两级查找写入 → cli 直跑产出的\n \u003csong\u003e/line_times.json 会「页面看得到手改、导出读不到」。修法：export 收口\n resolveLineTimesPath（与读/写路由同源）\n- C30③【幽灵声称】蓝图两处写 X-Export-Manual-Edits「M1 随做」实则从未实现 → 真加会计头\n- 视图精度（用户新需求）：刻度加亚秒档（短歌 16× 从 0 个标签 → 56 个 0.1s 刻度）+\n 标签带小数；zoom-to-line 改「最接近目标占比 1/3」（长拖腔行 19%→38%）；字条加刻度栅格\n + 走带上画字条窗口投影（两个时间视图互相定位）；读数精度随每像素秒数自适应到 ms 级；\n 字条字块同步逐字高亮 + 播放头；修字条头部窄栏文案与读数交错换行\n- 验收：check:ui 12 用例全绿（新增导出一致性、走带精度两例 + 非规范化键负向断言），\n 地板 ui 10→12、ownTestCases 66→69；pnpm check 静态全链绿；负向测试实证：\n 退回键守卫缺陷形态即精确红在该断言、恢复复绿\n- 判读纪律实证入册：后台通知 exit code 被管道 tail 吞掉（通知 exit 0 / 报告 failed），\n 只认 runner report status 或显式 set -o pipefail\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-08-08T11:32:01-07:00"},"CompareURL":"luoanwu/songformer-structure-lyrics/compare/3fdb4053791bac065674586a5173a8a41aa5a0c4...f77fe276fc4f6336bb58132bef8e01e83b4c9ea1","Len":1}...
|
1786213926
|
Edit
Delete
|
|
12628
|
12
|
5
|
12
|
42
|
0
|
0
|
refs/heads/gamescenter
|
1
|
|
1781583202
|
Edit
Delete
|
|
12629
|
12
|
5
|
12
|
42
|
0
|
0
|
refs/heads/gamescenter
|
1
|
{"Commits":[{"Sha1":"58db3f7bc {"Commits":[{"Sha1":"58db3f7bc24c9283ffb69330fe16ca88ba26b1c7","Message":"tests:lua-game-controller-test:AppDelegate: fix forget to call lua_module_register\n\nMany modules are missing if we don't call lua_module_register.\n","AuthorEmail":"udknight@gmail.com","AuthorName":"Wang YanQing","CommitterEmail":"udknight@gmail.com","CommitterName":"Wang YanQing","Timestamp":"2019-11-22T17:14:41+08:00"},{"Sha1":"1e728576768c6e9ab8510aa9463986843c5e9e58","Message":"android:libcocos2dx-with-controller:build.gradle: exclude libraries which match the name pattern \"*-debug.aar\"\n\ngamescenter project doesn't need the jhplayerlibrary-debug.aar right now.\n","AuthorEmail":"udknight@gmail.com","AuthorName":"Wang YanQing","CommitterEmail":"udknight@gmail.com","CommitterName":"Wang YanQing","Timestamp":"2019-11-22T14:28:52+08:00"},{"Sha1":"819488894984c7d5ac84da2bd2b685e2d6ed322b","Message":"android:ControllerManualAdapter:GameControllerSHANWAN: map BUTTON_C to BUTTON_START and map BUTTON_Z to BUTTON_SELECT\n","AuthorEmail":"udknight@gmail.com","AuthorName":"Wang YanQing","CommitterEmail":"udknight@gmail.com","CommitterName":"Wang YanQing","Timestamp":"2019-11-22T14:25:04+08:00"},{"Sha1":"5c66924f42c13d50cb943f2581e1106cb3792b41","Message":"tests:lua-game-controller-test: disable __thread\n\nI use the __thread to add support to run more than one cocos2dx instance\nin one process, this way has its shortage in some situation (async tasks),\nso I decide to disable it in gamescenter project, because this project\ndoesn't need to run more than one instance in one process.\n","AuthorEmail":"udknight@gmail.com","AuthorName":"Wang YanQing","CommitterEmail":"udknight@gmail.com","CommitterName":"Wang YanQing","Timestamp":"2019-11-22T11:39:44+08:00"},{"Sha1":"6894feaaffd2fd5272d5b628990f20f15c1932cd","Message":"ipvod:ipvodasync: use 60007 as the udp port for gamescenter project\n\nGamescenter project needs a different udp port from juhaiktv project.\n","AuthorEmail":"udknight@gmail.com","AuthorName":"Wang YanQing","CommitterEmail":"udknight@gmail.com","CommitterName":"Wang YanQing","Timestamp":"2019-11-19T13:39:51+08:00"}],"HeadCommit":{"Sha1":"58db3f7bc24c9283ffb69330fe16ca88ba26b1c7","Message":"tests:lua-game-controller-test:AppDelegate: fix forget to call lua_module_register\n\nMany modules are missing if we don't call lua_module_register.\n","AuthorEmail":"udknight@gmail.com","AuthorName":"Wang YanQing","CommitterEmail":"udknight@gmail.com","CommitterName":"Wang YanQing","Timestamp":"2019-11-22T17:14:41+08:00"},"CompareURL":"zhengpeizhong/cocos2d-x/compare/640cb1070f0249fa06b076404d3673f32cbb52f9...58db3f7bc24c9283ffb69330fe16ca88ba26b1c7","Len":10}...
|
1781583202
|
Edit
Delete
|
|
12626
|
12
|
5
|
12
|
42
|
0
|
0
|
refs/heads/freeze_bugly_version
|
1
|
|
1781583201
|
Edit
Delete
|
|
12627
|
12
|
5
|
12
|
42
|
0
|
0
|
refs/heads/freeze_bugly_version
|
1
|
{"Commits":[{"Sha1":"312566e65 {"Commits":[{"Sha1":"312566e654a18e93951ee37ef31d1b7be8dfba5a","Message":"Freeze the bugly version.\n","AuthorEmail":"udknight@gmail.com","AuthorName":"Wang YanQing","CommitterEmail":"udknight@gmail.com","CommitterName":"Wang YanQing","Timestamp":"2020-11-01T14:37:27+08:00"},{"Sha1":"048dd1e50c8271d41ba654e43e907a02ccb7c07d","Message":"v1.1.8\n","AuthorEmail":"udknight@gmail.com","AuthorName":"Wang YanQing","CommitterEmail":"udknight@gmail.com","CommitterName":"Wang YanQing","Timestamp":"2020-11-01T14:18:13+08:00"}],"HeadCommit":{"Sha1":"312566e654a18e93951ee37ef31d1b7be8dfba5a","Message":"Freeze the bugly version.\n","AuthorEmail":"udknight@gmail.com","AuthorName":"Wang YanQing","CommitterEmail":"udknight@gmail.com","CommitterName":"Wang YanQing","Timestamp":"2020-11-01T14:37:27+08:00"},"CompareURL":"zhengpeizhong/cocos2d-x/compare/618682362fce9a5137de51396b369147715317b0...312566e654a18e93951ee37ef31d1b7be8dfba5a","Len":2}...
|
1781583201
|
Edit
Delete
|
|
5124
|
1
|
5
|
1
|
6
|
0
|
0
|
refs/heads/fix/ws100-web-tracking-custom-events
|
0
|
|
1779697540
|
Edit
Delete
|
|
5125
|
5
|
5
|
1
|
6
|
0
|
0
|
refs/heads/fix/ws100-web-tracking-custom-events
|
0
|
|
1779697540
|
Edit
Delete
|
|
5126
|
1
|
5
|
1
|
6
|
0
|
0
|
refs/heads/fix/ws100-web-tracking-custom-events
|
0
|
{"Commits":[{"Sha1":"2ab1720f6 {"Commits":[{"Sha1":"2ab1720f6739fcfbfd35e92c861197d4891873e2","Message":"fix(web-tracking): 添加 customEvents 自定义事件表单 UI\n\n- 在追踪配置表单中添加自定义事件列表区域\n- 支持动态添加/删除自定义事件（name, selector, eventType）\n- 编辑配置时正确回填 customEvents 数据\n- 重置表单时清空 customEvents\n- 后端 schema 支持 settings.customEvents[] 配置\n\nCloses: WS-100\n","AuthorEmail":"admin@g-hi.com","AuthorName":"Admin","CommitterEmail":"admin@g-hi.com","CommitterName":"Admin","Timestamp":"2026-05-25T16:24:36+08:00"}],"HeadCommit":{"Sha1":"2ab1720f6739fcfbfd35e92c861197d4891873e2","Message":"fix(web-tracking): 添加 customEvents 自定义事件表单 UI\n\n- 在追踪配置表单中添加自定义事件列表区域\n- 支持动态添加/删除自定义事件（name, selector, eventType）\n- 编辑配置时正确回填 customEvents 数据\n- 重置表单时清空 customEvents\n- 后端 schema 支持 settings.customEvents[] 配置\n\nCloses: WS-100\n","AuthorEmail":"admin@g-hi.com","AuthorName":"Admin","CommitterEmail":"admin@g-hi.com","CommitterName":"Admin","Timestamp":"2026-05-25T16:24:36+08:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/d9e0ab1d9cbc0d7707781f8b0c9a5a49103ace8b...2ab1720f6739fcfbfd35e92c861197d4891873e2","Len":1}...
|
1779697540
|
Edit
Delete
|
|
5127
|
5
|
5
|
1
|
6
|
0
|
0
|
refs/heads/fix/ws100-web-tracking-custom-events
|
0
|
{"Commits":[{"Sha1":"2ab1720f6 {"Commits":[{"Sha1":"2ab1720f6739fcfbfd35e92c861197d4891873e2","Message":"fix(web-tracking): 添加 customEvents 自定义事件表单 UI\n\n- 在追踪配置表单中添加自定义事件列表区域\n- 支持动态添加/删除自定义事件（name, selector, eventType）\n- 编辑配置时正确回填 customEvents 数据\n- 重置表单时清空 customEvents\n- 后端 schema 支持 settings.customEvents[] 配置\n\nCloses: WS-100\n","AuthorEmail":"admin@g-hi.com","AuthorName":"Admin","CommitterEmail":"admin@g-hi.com","CommitterName":"Admin","Timestamp":"2026-05-25T16:24:36+08:00"}],"HeadCommit":{"Sha1":"2ab1720f6739fcfbfd35e92c861197d4891873e2","Message":"fix(web-tracking): 添加 customEvents 自定义事件表单 UI\n\n- 在追踪配置表单中添加自定义事件列表区域\n- 支持动态添加/删除自定义事件（name, selector, eventType）\n- 编辑配置时正确回填 customEvents 数据\n- 重置表单时清空 customEvents\n- 后端 schema 支持 settings.customEvents[] 配置\n\nCloses: WS-100\n","AuthorEmail":"admin@g-hi.com","AuthorName":"Admin","CommitterEmail":"admin@g-hi.com","CommitterName":"Admin","Timestamp":"2026-05-25T16:24:36+08:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/d9e0ab1d9cbc0d7707781f8b0c9a5a49103ace8b...2ab1720f6739fcfbfd35e92c861197d4891873e2","Len":1}...
|
1779697540
|
Edit
Delete
|
|
1104
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/fix/ticket-workflow-defs-format
|
0
|
|
1776390832
|
Edit
Delete
|
|
1105
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/fix/ticket-workflow-defs-format
|
0
|
{"Commits":[{"Sha1":"27f01c5f3 {"Commits":[{"Sha1":"27f01c5f3786ed44f603c6ca9a35156d956b1315","Message":"fix(ticket-workflows): workflow_defs 写链显式携带 format 字段\n\napproval-governance 审计通过 WORKFLOW_DEF_WRITE 正则扫描 workflow_defs.(create|update|upsert) 调用点后 800 字符范围，若未命中 `format:` 即判 BLOCKER。原 update 函数 updateData 未包含 format，BPMN/GRAPH_JSON 可能隐式漂移。\n\n本次修复：\n- schema.ts 新增 workflowFormatSchema 枚举（BPMN/GRAPH_JSON），createSchema/updateSchema body 加入 format 字段（create 默认 GRAPH_JSON，update 可选）\n- service.ts create/update 函数签名扩展 format 参数，写入 data 时显式落盘；update 未显式传入则保留 existing.format 而非隐式默认\n- docs.ts workflowSchema/createUpdateSchema 同步暴露 format 枚举，保证 OpenAPI 真源一致\n\n验证：\n- audit:approval-governance blockers=0 warnings=0 workflow_format_drift_files=0\n- audit:outbox-atomicity A=1633 / B=0 / C=0，原子化率 100%\n- ticket-workflow.service.test.ts 19/19 全通过\n- backend tsc --noEmit 无新增错误\n\n关联：Q2 12 周落地计划 Sprint 1 · Data Squad · KR2.1\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"mluo@MluodeMacBook-Air.local","AuthorName":"Mluo","CommitterEmail":"mluo@MluodeMacBook-Air.local","CommitterName":"Mluo","Timestamp":"2026-04-17T09:53:33+08:00"}],"HeadCommit":{"Sha1":"27f01c5f3786ed44f603c6ca9a35156d956b1315","Message":"fix(ticket-workflows): workflow_defs 写链显式携带 format 字段\n\napproval-governance 审计通过 WORKFLOW_DEF_WRITE 正则扫描 workflow_defs.(create|update|upsert) 调用点后 800 字符范围，若未命中 `format:` 即判 BLOCKER。原 update 函数 updateData 未包含 format，BPMN/GRAPH_JSON 可能隐式漂移。\n\n本次修复：\n- schema.ts 新增 workflowFormatSchema 枚举（BPMN/GRAPH_JSON），createSchema/updateSchema body 加入 format 字段（create 默认 GRAPH_JSON，update 可选）\n- service.ts create/update 函数签名扩展 format 参数，写入 data 时显式落盘；update 未显式传入则保留 existing.format 而非隐式默认\n- docs.ts workflowSchema/createUpdateSchema 同步暴露 format 枚举，保证 OpenAPI 真源一致\n\n验证：\n- audit:approval-governance blockers=0 warnings=0 workflow_format_drift_files=0\n- audit:outbox-atomicity A=1633 / B=0 / C=0，原子化率 100%\n- ticket-workflow.service.test.ts 19/19 全通过\n- backend tsc --noEmit 无新增错误\n\n关联：Q2 12 周落地计划 Sprint 1 · Data Squad · KR2.1\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"mluo@MluodeMacBook-Air.local","AuthorName":"Mluo","CommitterEmail":"mluo@MluodeMacBook-Air.local","CommitterName":"Mluo","Timestamp":"2026-04-17T09:53:33+08:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/7b47df3186db279cfc071517a6c034aa213d926d...27f01c5f3786ed44f603c6ca9a35156d956b1315","Len":1}...
|
1776390832
|
Edit
Delete
|
|
2006
|
5
|
17
|
5
|
6
|
0
|
0
|
refs/heads/fix/ticket-workflow-defs-format
|
0
|
|
1778625303
|
Edit
Delete
|
|
21913
|
16
|
5
|
16
|
6
|
0
|
0
|
refs/heads/fix/frontend-service-service-dashboard
|
0
|
|
1786437401
|
Edit
Delete
|
|
21914
|
5
|
5
|
16
|
6
|
0
|
0
|
refs/heads/fix/frontend-service-service-dashboard
|
0
|
|
1786437401
|
Edit
Delete
|
|
21915
|
16
|
5
|
16
|
6
|
0
|
0
|
refs/heads/fix/frontend-service-service-dashboard
|
0
|
{"Commits":[{"Sha1":"66d832ab1 {"Commits":[{"Sha1":"66d832ab1b3d0934d4b39cfc77da31d8eb1de029","Message":"fix(service-dashboard): 阻断工单统计与趋势分析图表高度被持续拉伸\n\n服务看板「工单统计 / 趋势分析」ECharts 容器使用 height:100% + min-height，\n并直接对图表 DOM 调用 ResizeObserver → resize()，形成高度反馈环。\n\n- 图表容器改为固定高度并 overflow:hidden\n- resize 增加 rAF 合并与尺寸未变短路\n- 覆盖 TicketStatsPanel、TrendsPanel\n","AuthorEmail":"228834386@qq.com","AuthorName":"starry","CommitterEmail":"228834386@qq.com","CommitterName":"starry","Timestamp":"2026-08-11T13:40:54+08:00"}],"HeadCommit":{"Sha1":"66d832ab1b3d0934d4b39cfc77da31d8eb1de029","Message":"fix(service-dashboard): 阻断工单统计与趋势分析图表高度被持续拉伸\n\n服务看板「工单统计 / 趋势分析」ECharts 容器使用 height:100% + min-height，\n并直接对图表 DOM 调用 ResizeObserver → resize()，形成高度反馈环。\n\n- 图表容器改为固定高度并 overflow:hidden\n- resize 增加 rAF 合并与尺寸未变短路\n- 覆盖 TicketStatsPanel、TrendsPanel\n","AuthorEmail":"228834386@qq.com","AuthorName":"starry","CommitterEmail":"228834386@qq.com","CommitterName":"starry","Timestamp":"2026-08-11T13:40:54+08:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/c32dc69661d18fedc3e6939936535f3f5906bf7d...66d832ab1b3d0934d4b39cfc77da31d8eb1de029","Len":1}...
|
1786437401
|
Edit
Delete
|
|
21916
|
5
|
5
|
16
|
6
|
0
|
0
|
refs/heads/fix/frontend-service-service-dashboard
|
0
|
{"Commits":[{"Sha1":"66d832ab1 {"Commits":[{"Sha1":"66d832ab1b3d0934d4b39cfc77da31d8eb1de029","Message":"fix(service-dashboard): 阻断工单统计与趋势分析图表高度被持续拉伸\n\n服务看板「工单统计 / 趋势分析」ECharts 容器使用 height:100% + min-height，\n并直接对图表 DOM 调用 ResizeObserver → resize()，形成高度反馈环。\n\n- 图表容器改为固定高度并 overflow:hidden\n- resize 增加 rAF 合并与尺寸未变短路\n- 覆盖 TicketStatsPanel、TrendsPanel\n","AuthorEmail":"228834386@qq.com","AuthorName":"starry","CommitterEmail":"228834386@qq.com","CommitterName":"starry","Timestamp":"2026-08-11T13:40:54+08:00"}],"HeadCommit":{"Sha1":"66d832ab1b3d0934d4b39cfc77da31d8eb1de029","Message":"fix(service-dashboard): 阻断工单统计与趋势分析图表高度被持续拉伸\n\n服务看板「工单统计 / 趋势分析」ECharts 容器使用 height:100% + min-height，\n并直接对图表 DOM 调用 ResizeObserver → resize()，形成高度反馈环。\n\n- 图表容器改为固定高度并 overflow:hidden\n- resize 增加 rAF 合并与尺寸未变短路\n- 覆盖 TicketStatsPanel、TrendsPanel\n","AuthorEmail":"228834386@qq.com","AuthorName":"starry","CommitterEmail":"228834386@qq.com","CommitterName":"starry","Timestamp":"2026-08-11T13:40:54+08:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/c32dc69661d18fedc3e6939936535f3f5906bf7d...66d832ab1b3d0934d4b39cfc77da31d8eb1de029","Len":1}...
|
1786437401
|
Edit
Delete
|
|
21925
|
16
|
17
|
16
|
6
|
0
|
0
|
refs/heads/fix/frontend-service-service-dashboard
|
0
|
|
1786438570
|
Edit
Delete
|
|
21926
|
5
|
17
|
16
|
6
|
0
|
0
|
refs/heads/fix/frontend-service-service-dashboard
|
0
|
|
1786438570
|
Edit
Delete
|
|
20264
|
5
|
5
|
5
|
72
|
0
|
0
|
refs/heads/fix/contracts-build-chain-and-review-pa refs/heads/fix/contracts-build-chain-and-review-panel...
|
0
|
|
1785504180
|
Edit
Delete
|