|
28935
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/content-placeholder-navigation
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"886b077616eca50ded1e35a076d0a7759b24a0ab","Message":"test: verify the content slot navigation and factual dialog round\n\nSeven isolated gates and pnpm check pass at sha256:cdf13599…; evidence in reports/content-slot-navigation-2026-09-10 and acceptance-artifacts/content-slot-navigation-2026-09-10.\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-10T01:41:08-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...886b077616eca50ded1e35a076d0a7759b24a0ab","Len":0}...
|
1789029869
|
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
|
|
20265
|
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
|
{"Commits":[{"Sha1":"67849d6aa {"Commits":[{"Sha1":"67849d6aad796878e6fd40b2e54307780b01442f","Message":"chore: 重跑三级门禁并绑定干净工作区证据\n\n上一提交的报告生成于 dirty 工作区（gitSha 指向父提交 7638e94、\nworktreeDirty=true），只能支撑「本地工作区通过」。此处在 a015400 的\n干净检出上重跑三级门禁，让三份 latest 报告的 provenance 统一绑定\n该提交且 worktreeDirty=false——可支撑「提交 a015400 在本机干净工作区\n通过三级门禁」。\n\npnpm check ✅ 5/5\npnpm check:runtime ✅ 83 用例 / 0 失败（PG:55432/juhai_quotation_runtime_20260731d + Redis:6382）\npnpm check:ui ✅ 8 用例 / 0 失败（PG:55432/juhai_quotation_ui_20260731d + Redis:6382）\n\n仍不得外推为远端已发布或 CI 已通过：本分支未推送，无远端 run 证据（G14）。\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-07-31T06:16:25-07:00"},{"Sha1":"a015400b8aa901246315eb213d20354d6ded3133","Message":"fix: 打通契约构建链并补齐方案复核依据\n\n本提交包含两批改动。工作区里它们已交织到同一行/同一 hunk\n（package.json 的 check 串、next.config.ts 的 output），无法拆开单独提交。\n\n── 批次 A：本轮定位并修复（Claude 作业）────────────────────────────\n\n契约包 src/dist 漂移（C23）——P1「运行时到底读哪一份」的隐藏变体：\ntypecheck 与 contracts 单测读 src，两后端运行时经 package main 读 dist。\n`pnpm --filter` 不走 turbo 的 dependsOn ^build，dist 又被 gitignore，\n于是门禁全绿而运行时按旧契约行为。实测症状：dist 缺 versionNo →\nZod 静默 strip → 技术复核恒返 409 STALE_VERSION。\n负向验证：移走 dist 后 typecheck 立刻 TS2307，证明全新 clone/CI 上必红。\n- package.json: check 前置 build:contracts\n- scripts/check-{runtime,ui}-acceptance.mjs: 各加 contracts 构建步骤\n- .claude/launch.json: 四个配置均前置 contracts 构建\n- packages/contracts/package.json: 补 prepare；clean 补删 tsconfig.tsbuildinfo\n （composite 下留着 buildinfo 会让 clean+build 空 emit）\n\n方案表单默认路径不可用（C24）：\n「使用客户主联系人」value 为空串，contactId 契约是 uuid().optional()，\n空串不过校验，导致默认状态下表单永不可提交，错误还被汇总成一句\n指不到联系人的话。register 处归一为 undefined。\n\n客户方案复核依据面板：\n技术复核/经理批准需在同一屏看到客户需求、空间与工区、平面图、逐档配置清单。\n清单只渲染规格字段，刻意不展开 product 以免带出 standardPriceCents\n（角色权限单源里技术角色不继承报价域敏感读取）。缺图纸显式标注但不阻断。\n补填资料入口接上此前零消费者的 useUpdateSolution + PATCH /solutions/:id，\n仅在 DRAFT/NEEDS_INFORMATION/REVISION_REQUIRED 开放——修复「目标客群留空\n的方案走到 APPROVED 后永远发布不了且无处补填」的死路。\n\n契约类型补齐：SolutionProduct 增补 product/surveySpace 嵌套（服务端一直下发，\n此前类型比载荷窄）。\n\nE2E 回归锁：新增专打默认联系人路径的用例，兼测复核依据面板与价格红线。\n负向验证：撤回 contactId 修复 → check:ui 报红；还原 → 8 用例全绿。\n\n附带：next.config.ts 的 output 重复定义（TS2783，本轮之前即存在，\n导致 pnpm check 红）改为三元计算，行为等价；check-vm-deploy 的 standalone\n绊网相应收窄为「字面量或该正确三元」，不放宽成 /output:.*standalone/\n（负向验证：三元写反即红）。\n\n── 批次 B：进入本轮前工作区已有的未提交改动（非本轮作业）──────────\n\nVM 部署强化（Dockerfile/compose/vm-deploy.sh/check-vm-deploy.mjs、restore/\ndrill/rollback）、移动端导航 MobileNav、客户方案域后端与验收测试、\n角色权限与模块对接门禁、方案蓝图与验收记录等。这批未经逐项复核，\n如需单独审阅可 `git reset --soft HEAD~1` 后重新拆分。\n\n── 证据（本地工作区，2026-07-31，工作区 dirty）──────────────────\npnpm check ✅ 5/5\npnpm check:runtime ✅ 83 用例 / 0 失败（地板 79→83）\npnpm check:ui ✅ 8 用例 / 0 失败（地板 7→8）\nownTestCases 地板 90→91。未推送、无远端 CI 运行证据（G14 仍 OPEN）。\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-07-31T06:13:59-07:00"}],"HeadCommit":{"Sha1":"67849d6aad796878e6fd40b2e54307780b01442f","Message":"chore: 重跑三级门禁并绑定干净工作区证据\n\n上一提交的报告生成于 dirty 工作区（gitSha 指向父提交 7638e94、\nworktreeDirty=true），只能支撑「本地工作区通过」。此处在 a015400 的\n干净检出上重跑三级门禁，让三份 latest 报告的 provenance 统一绑定\n该提交且 worktreeDirty=false——可支撑「提交 a015400 在本机干净工作区\n通过三级门禁」。\n\npnpm check ✅ 5/5\npnpm check:runtime ✅ 83 用例 / 0 失败（PG:55432/juhai_quotation_runtime_20260731d + Redis:6382）\npnpm check:ui ✅ 8 用例 / 0 失败（PG:55432/juhai_quotation_ui_20260731d + Redis:6382）\n\n仍不得外推为远端已发布或 CI 已通过：本分支未推送，无远端 run 证据（G14）。\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-07-31T06:16:25-07:00"},"CompareURL":"luoanwu/juhai-quotation-system/compare/7638e946e8817308b94a23c028a18ac465c342c6...67849d6aad796878e6fd40b2e54307780b01442f","Len":2}...
|
1785504181
|
Edit
Delete
|
|
20266
|
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
|
{"Commits":[{"Sha1":"0d85a3de6 {"Commits":[{"Sha1":"0d85a3de6efbf4ca42ba1345bfbc66f9d1f9ac0d","Message":"docs: 按真实 CI 证据更正 C23 与 G14\n\n上一提交把一个未经正确验证的结论写进了治理真源，此处更正。\n\nC23 原文断言「全新 clone/CI 上 pnpm check 必红（contracts dist 不存在）」。\n该结论来自 `pnpm --filter \u003capp\u003e typecheck` 的负向测试，而它绕过 turbo；\nCI 实际走 `pnpm typecheck` → `turbo run typecheck`，而 turbo.json 的\ntypecheck/lint/test 均带 dependsOn ^build，contracts 会被自动构建。\nGitHub run 30603461723 的 static job 实际通过，证伪原结论。\nC23 仍然成立的部分：绕过 turbo 的调用路径（.claude/launch.json 直接\npnpm dev、check:ui 的 pnpm --filter build）确实会吃到陈旧 dist——本轮\n409 STALE_VERSION 即由此而来；clean 不删 tsconfig.tsbuildinfo 导致\nclean \u0026\u0026 build 空 emit 是独立真 bug。修复本身保留。\n\nG14 原记「尚无远端 CI 运行证据」已过时。实际已有 run 30603461723\n（push main fdf7b59，2026-07-31T04:10Z）：static ✅、runtime ❌\n`tests-floor: expected \u003e= 74, got 0`，整步仅 24s，真实 DB 测试没跑起来。\n地板断言拦住了这次「0 tests 假绿」，但根因未定位，需专项排查 CI 上\nturbo run test --force 为何产不出 vitest 报告。基线表 ci-gate 行同步\n改为「已有远端证据但为红盘」，仍 OPEN。\n\n另记：两个远端 main 不同步（origin 7638e94 / github fdf7b59），\nCI 只挂 github 侧，且只在 pull_request 或 push main 触发。\n\npnpm check ✅ 绿（含 check:governance-docs / check:docs-truth）。\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-07-31T06:30:18-07:00"}],"HeadCommit":{"Sha1":"0d85a3de6efbf4ca42ba1345bfbc66f9d1f9ac0d","Message":"docs: 按真实 CI 证据更正 C23 与 G14\n\n上一提交把一个未经正确验证的结论写进了治理真源，此处更正。\n\nC23 原文断言「全新 clone/CI 上 pnpm check 必红（contracts dist 不存在）」。\n该结论来自 `pnpm --filter \u003capp\u003e typecheck` 的负向测试，而它绕过 turbo；\nCI 实际走 `pnpm typecheck` → `turbo run typecheck`，而 turbo.json 的\ntypecheck/lint/test 均带 dependsOn ^build，contracts 会被自动构建。\nGitHub run 30603461723 的 static job 实际通过，证伪原结论。\nC23 仍然成立的部分：绕过 turbo 的调用路径（.claude/launch.json 直接\npnpm dev、check:ui 的 pnpm --filter build）确实会吃到陈旧 dist——本轮\n409 STALE_VERSION 即由此而来；clean 不删 tsconfig.tsbuildinfo 导致\nclean \u0026\u0026 build 空 emit 是独立真 bug。修复本身保留。\n\nG14 原记「尚无远端 CI 运行证据」已过时。实际已有 run 30603461723\n（push main fdf7b59，2026-07-31T04:10Z）：static ✅、runtime ❌\n`tests-floor: expected \u003e= 74, got 0`，整步仅 24s，真实 DB 测试没跑起来。\n地板断言拦住了这次「0 tests 假绿」，但根因未定位，需专项排查 CI 上\nturbo run test --force 为何产不出 vitest 报告。基线表 ci-gate 行同步\n改为「已有远端证据但为红盘」，仍 OPEN。\n\n另记：两个远端 main 不同步（origin 7638e94 / github fdf7b59），\nCI 只挂 github 侧，且只在 pull_request 或 push main 触发。\n\npnpm check ✅ 绿（含 check:governance-docs / check:docs-truth）。\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-07-31T06:30:18-07:00"},"CompareURL":"luoanwu/juhai-quotation-system/compare/67849d6aad796878e6fd40b2e54307780b01442f...0d85a3de6efbf4ca42ba1345bfbc66f9d1f9ac0d","Len":1}...
|
1785504640
|
Edit
Delete
|
|
20267
|
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
|
{"Commits":[{"Sha1":"de7d09aee {"Commits":[{"Sha1":"de7d09aee2a89208f006bc3ca829f289619a64b7","Message":"docs: 记录首份远端 CI 绿盘证据（PR #1 / run 30634897066）\n\nGitHub run 30634897066（PR #1，head 0d85a3d）两 job 全绿：\nstatic ✅；runtime 83 用例（contracts 31 / nestjs 26 / fastify 26）、\nUI 8 用例，与本地逐项一致，耗时 3m21s。这是本仓第一份远端绿盘证据。\n\n对照上一次 run 30603461723（push main fdf7b59）：runtime 失败于\ntests-floor「expected \u003e= 74, got 0」，整步仅 24s。\n\n刻意不把这次转绿归因到本轮任何一个提交：PR #1 含 7 个提交，除本轮 3 个外\n还有 4 个存量提交（283f1bf…7638e94），其中任一都可能是真正修好它的那个，\n且 7638e94 从未单独在 CI 上跑过。要归因需另构造对照 run。\n\nG14 仍 OPEN：绿盘只覆盖该 PR 分支，github main 最近一次 run 仍红；\n尚未用受控失败 PR 证明违规真被阻断，分支保护 / required checks 也未定位。\nci-gate 行同步改写，明确「不得宣称 PR 已被机器拦截」。\n\npnpm check ✅ 绿。\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-07-31T06:39:36-07:00"}],"HeadCommit":{"Sha1":"de7d09aee2a89208f006bc3ca829f289619a64b7","Message":"docs: 记录首份远端 CI 绿盘证据（PR #1 / run 30634897066）\n\nGitHub run 30634897066（PR #1，head 0d85a3d）两 job 全绿：\nstatic ✅；runtime 83 用例（contracts 31 / nestjs 26 / fastify 26）、\nUI 8 用例，与本地逐项一致，耗时 3m21s。这是本仓第一份远端绿盘证据。\n\n对照上一次 run 30603461723（push main fdf7b59）：runtime 失败于\ntests-floor「expected \u003e= 74, got 0」，整步仅 24s。\n\n刻意不把这次转绿归因到本轮任何一个提交：PR #1 含 7 个提交，除本轮 3 个外\n还有 4 个存量提交（283f1bf…7638e94），其中任一都可能是真正修好它的那个，\n且 7638e94 从未单独在 CI 上跑过。要归因需另构造对照 run。\n\nG14 仍 OPEN：绿盘只覆盖该 PR 分支，github main 最近一次 run 仍红；\n尚未用受控失败 PR 证明违规真被阻断，分支保护 / required checks 也未定位。\nci-gate 行同步改写，明确「不得宣称 PR 已被机器拦截」。\n\npnpm check ✅ 绿。\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-07-31T06:39:36-07:00"},"CompareURL":"luoanwu/juhai-quotation-system/compare/0d85a3de6efbf4ca42ba1345bfbc66f9d1f9ac0d...de7d09aee2a89208f006bc3ca829f289619a64b7","Len":1}...
|
1785505181
|
Edit
Delete
|
|
20272
|
5
|
17
|
5
|
72
|
0
|
0
|
refs/heads/fix/contracts-build-chain-and-review-pa refs/heads/fix/contracts-build-chain-and-review-panel...
|
0
|
|
1785507126
|
Edit
Delete
|
|
38821
|
16
|
5
|
16
|
125
|
0
|
0
|
refs/heads/fix/display-name-reads
|
0
|
|
1792208460
|
Edit
Delete
|
|
38822
|
16
|
5
|
16
|
125
|
0
|
0
|
refs/heads/fix/display-name-reads
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"63f1e0d5fd0dac58c74be467a927e4f5cab3ce06","Message":"fix: 补齐管理读接口的应用名称与成员姓名\n\n修复启用新应用候选仅显示代码的问题，并补齐原有姓名读取权限内的管理目录展示字段。\n\n实现内容：\n- 补齐应用候选、应用关系、管理员分配及程序身份的应用名称与相关名称搜索\n- 为成员准入、负责人、管理员候选和分配提供姓名及确认标记，保留独立代码字段\n- 保持用户组候选、业务授权候选和业务角色绑定的姓名最小披露边界，不改变权限判断、错误码与排序\n- 增加字段、搜索及权限边界回归测试，同步接口合同并提供九项建议的前端接入交接\n\n验证：\n- Java 25 执行 ./mvnw -B -ntp -pl iam-server -am verify -Dit.test=DisplayNameReadIT,ApplicationManagementIT,AuthorizationManagementIT,ManagementReadIT,ServicePrincipalIT,ManagedDisplayNamesIT -Dfailsafe.failIfNoSpecifiedTests=false：BUILD SUCCESS\n- 291 项单元测试、50 项集成测试通过，失败、错误和跳过均为 0；格式检查、编译、架构检查及后端打包通过\n- git diff --check 与暂存区差异检查通过，交接文档 10 个 JSON 示例解析有效\n- 未运行全部集成测试、性能对照、安全漏洞扫描或前端验收\n","AuthorEmail":"gamebyteyu@gmail.com","AuthorName":"starry","CommitterEmail":"gamebyteyu@gmail.com","CommitterName":"starry","Timestamp":"2026-10-16T02:02:27-07:00"},"CompareURL":"pengzhiyu/IAM/compare/main...63f1e0d5fd0dac58c74be467a927e4f5cab3ce06","Len":0}...
|
1792208460
|
Edit
Delete
|
|
38824
|
16
|
17
|
16
|
125
|
0
|
0
|
refs/heads/fix/display-name-reads
|
0
|
|
1792208480
|
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
|
|
29221
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/g34-write-chain-20260912
|
0
|
|
1789198827
|
Edit
Delete
|
|
29222
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/g34-write-chain-20260912
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"e9764103a19cefa8ecbc18c172a62f8c900a7b72","Message":"test(write-chain): verify the G34 round\n\nEight fingerprint-bound gates and the full static chain passed on the\nG34 source (sha256:948e6d92c0eb2e85171357e1cec9fea0e8b9264474cb8622d7887a9a2f86efa3) in an isolated stack: contracts unit tests, both\nbackends' real-DB regressions for slot reconciliation, detached-instance\nrejection, marker-based UNKNOWN isolation and composition lease expiry;\nthe models snapshot reports 5/8 host weights. Evidence:\nacceptance-artifacts/g34-write-chain-2026-09-12/.\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-12T00:38:23-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...e9764103a19cefa8ecbc18c172a62f8c900a7b72","Len":0}...
|
1789198827
|
Edit
Delete
|
|
29224
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/g34-write-chain-20260912
|
0
|
{"Commits":[{"Sha1":"98d37c240 {"Commits":[{"Sha1":"98d37c24042810f98d7817d37515bdd8d89e6570","Message":"docs(releases): record g34-write-chain1 deployment\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-12T00:45:14-07:00"}],"HeadCommit":{"Sha1":"98d37c24042810f98d7817d37515bdd8d89e6570","Message":"docs(releases): record g34-write-chain1 deployment\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-12T00:45:14-07:00"},"CompareURL":"luoanwu/image-generation/compare/e9764103a19cefa8ecbc18c172a62f8c900a7b72...98d37c24042810f98d7817d37515bdd8d89e6570","Len":1}...
|
1789199133
|
Edit
Delete
|
|
29229
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/g34-write-chain-20260912
|
0
|
{"Commits":[{"Sha1":"0ab42fc10 {"Commits":[{"Sha1":"0ab42fc10e7bd94db12fcd439a5410d0930ab7f7","Message":"docs(releases): record the g34-write-chain2 re-run of the same source\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-12T01:09:56-07:00"}],"HeadCommit":{"Sha1":"0ab42fc10e7bd94db12fcd439a5410d0930ab7f7","Message":"docs(releases): record the g34-write-chain2 re-run of the same source\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-12T01:09:56-07:00"},"CompareURL":"luoanwu/image-generation/compare/98d37c24042810f98d7817d37515bdd8d89e6570...0ab42fc10e7bd94db12fcd439a5410d0930ab7f7","Len":1}...
|
1789200877
|
Edit
Delete
|
|
29944
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/industry-trends-scroll-20260908
|
0
|
|
1789445321
|
Edit
Delete
|
|
29945
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/industry-trends-scroll-20260908
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"23d6fa9f7eddad6a89819e2ee6a664211c77a60c","Message":"fix(trends): allow vertical scrolling in the fixed workspace\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-08T11:49:34-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...23d6fa9f7eddad6a89819e2ee6a664211c77a60c","Len":0}...
|
1789445321
|
Edit
Delete
|
|
26499
|
5
|
5
|
5
|
13
|
0
|
0
|
refs/heads/fix/p0-batch-1
|
0
|
|
1787812620
|
Edit
Delete
|
|
26500
|
5
|
5
|
5
|
13
|
0
|
0
|
refs/heads/fix/p0-batch-1
|
0
|
{"Commits":[{"Sha1":"62baa5a01 {"Commits":[{"Sha1":"62baa5a01b492f05b25701859bebabf996f4f818","Message":"fix: 第二批P0修复——「一单不丢」读侧闭环\n\n- 重启回捞泵: PrinterService.recoverPersistedJobs 启动回捞30分钟窗口内\n 活跃任务(CREATED/QUEUED直接重放、中断PRINTING经fail→retry归一化、\n 重试耗尽入死信)；ACTION_RECOVER_JOBS意图供UI手动触发(只重放QUEUED\n 防重复出票)；防并发回捞+内存队列查重\n- 恢复按钮接真重放: QueueDetailActivity三处/MainActivity死信恢复改完DB后\n 触发回捞(此前只翻状态Toast成功、一张不打)；修doRecoverAll主线程DAO崩溃\n- PrintJobReconstructor补全: 新增PrintJob.Builder.restoreState()合法还原\n 入口(保真恢复状态/计数/版本/时间戳、不发创建事件)，读库路径由必NPE变可用\n- fail()放宽至CREATED/QUEUED/PRINTING全活跃态+JobStatus转移表同步:\n 上机前失败进入统一重试/死信轨道，删除onTaskFailed的2秒无限循环分支\n- MIGRATION_1_2确定性重建: 配置room.schemaLocation生成权威schema\n (schemas/2.json入库)，迁移按createSql逐字重建(旧增量迁移三处与实体\n 不符、v1升级必崩)\n- PrintContent携带真实printType(任务表print_type列不再恒0)；\n cancel SQL补DEAD_LETTER守卫；PrintTestActivity测试任务改协议形状JSON\n- 新增PrintJobLifecycleTest 8例(还原保真/fail放宽/回捞归一化)；\n 全量回归23/23绿(testProductionDebugUnitTest)\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-26T19:53:10-07:00"},{"Sha1":"4ef4540b46e231c51c14c50696c587f3343e2af1","Message":"docs: 业务全景梳理与核心体检治理方案 + CLAUDE.md纠偏\n\n- 打印业务全景梳理.md: 四模块考古定论、38单据业务地图、\n 四套协议兼容矩阵、真接线链路与假链路警示（全部file:line实证）\n- 业务核心体检与治理方案.md: 五条业务不变量评估、缺失/冲突/bug\n 全清单（含print_type=4三方三义、camelCase归零等）、四阶段治理\n 路线与ABC决策、第一批执行记录与第二批待办\n- CLAUDE.md纠偏: 删虚标覆盖率、核心文件索引改为真接线链路+\n 死代码警示、重试参数改真实值、假测试与flavor任务名坑位警示\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-26T18:49:14-07:00"},{"Sha1":"582ef48839dac15274b8568357603068ec0eabfd","Message":"fix: 首批P0修复——适配层snake_case/线程模型/持久化/CI真源\n\n真接线链路四大P0（详见《业务核心体检与治理方案.md》§4/§7）：\n- 适配层重写为线协议真key（祖本@SerializedName全snake_case），\n camelCase降级兼容；补映射printer_key/order_source/is_reprint等11字段；\n 交接款amount级联兜底——修\"真实报文下单据字段全部静默归零\"\n- 打印执行链三处observeOn(main)改IO线程，修NetworkOnMainThread必崩\n- 候选打印机不再按connection_status==1预筛，解除\"先打印成功才算在线\"自举死锁\n- save()十处裸调改persist真订阅+乐观锁差一修复，任务状态真正落库\n- processJob catch去掉非法job.fail()（状态不符二次抛异常吞原因）\n- Manifest补FOREGROUND_SERVICE_DATA_SYNC/POST_NOTIFICATIONS（targetSdk 34）\n- CI: testDebugUnitTest因flavor错配静默跳过redesign全部真测试，\n 改为显式双模块任务名；require_tests改true；wrapper 8.4→8.14.3\n- 新增金样本特征测试PrintJobOrderAdapterTest（7例，锁死字段归零回归）\n\n回归: :printer-redesign:testProductionDebugUnitTest 15/15 绿\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-26T18:48:58-07:00"},{"Sha1":"8f7d7999f6b1eddf141dea9eca0891ca7149e206","Message":"fix: 落盘2026-07-05会话的测试基建与安全修复\n\n- fixes/ 参考修复类纳入 test 源集（可编译运行、不进生产 APK）\n- 纯 JVM 下依赖 android org.json 的假跑测试改为诚实 @Ignore\n- Money.ofYuan 走 BigDecimal 精确换算，修浮点分转换误差\n- PrintJob.cancel 增加终态守卫，防死信任务被并发取消\n- docker-compose 密钥改环境变量注入 + .env.example 模板 + .gitignore 密钥规则\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-26T18:48:06-07:00"}],"HeadCommit":{"Sha1":"62baa5a01b492f05b25701859bebabf996f4f818","Message":"fix: 第二批P0修复——「一单不丢」读侧闭环\n\n- 重启回捞泵: PrinterService.recoverPersistedJobs 启动回捞30分钟窗口内\n 活跃任务(CREATED/QUEUED直接重放、中断PRINTING经fail→retry归一化、\n 重试耗尽入死信)；ACTION_RECOVER_JOBS意图供UI手动触发(只重放QUEUED\n 防重复出票)；防并发回捞+内存队列查重\n- 恢复按钮接真重放: QueueDetailActivity三处/MainActivity死信恢复改完DB后\n 触发回捞(此前只翻状态Toast成功、一张不打)；修doRecoverAll主线程DAO崩溃\n- PrintJobReconstructor补全: 新增PrintJob.Builder.restoreState()合法还原\n 入口(保真恢复状态/计数/版本/时间戳、不发创建事件)，读库路径由必NPE变可用\n- fail()放宽至CREATED/QUEUED/PRINTING全活跃态+JobStatus转移表同步:\n 上机前失败进入统一重试/死信轨道，删除onTaskFailed的2秒无限循环分支\n- MIGRATION_1_2确定性重建: 配置room.schemaLocation生成权威schema\n (schemas/2.json入库)，迁移按createSql逐字重建(旧增量迁移三处与实体\n 不符、v1升级必崩)\n- PrintContent携带真实printType(任务表print_type列不再恒0)；\n cancel SQL补DEAD_LETTER守卫；PrintTestActivity测试任务改协议形状JSON\n- 新增PrintJobLifecycleTest 8例(还原保真/fail放宽/回捞归一化)；\n 全量回归23/23绿(testProductionDebugUnitTest)\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-26T19:53:10-07:00"},"CompareURL":"luoanwu/printer-server/compare/6c80c00976d1c5ac4aaa5f76d10cf1e7b4f59448...62baa5a01b492f05b25701859bebabf996f4f818","Len":4}...
|
1787812620
|
Edit
Delete
|
|
32977
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/fix/rls-grant-manifest-20260926
|
0
|
|
1790422725
|
Edit
Delete
|
|
32978
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/fix/rls-grant-manifest-20260926
|
0
|
{"Commits":[{"Sha1":"27139913a {"Commits":[{"Sha1":"27139913af5566990baea2ab77d39c1e5025a161","Message":"chore(reports): 静态 30/30 与 check:runtime 924/0 同回绑 @ 4600532\n\nclean HEAD 4600532 上 check:runtime passed（924 tests / 0 failures、30/30 步、行为矩阵\n204/204、产品验收 274 例；PG 55470 digital_employee_os_acceptance_20260926，Redis 6404/3），\n预写的 924 与实测一致；随后同一 HEAD 上 pnpm check 30/30。42 份报告 provenance 均为\n4600532 / worktreeDirty=false。check:ui 与聚合外专项 runner 本轮未跑。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T04:38:21-07:00"},{"Sha1":"46005326da6b7b0580adc687ff130b123350cfb0","Message":"test(llm): MCP worker 链验收按实现实际版本 2.0.0 登记与绑定凭据\n\nbcdcdb6 把 platform.control-plane.query 静态实现升到 2.0.0（v2）并移除 1.0.0，\n两后端 llm.acceptance 的 MCP 七例仍以 1.0.0 登记工具与绑定凭据，POST /api/tools\n回 400，check:runtime 自该提交起在 nestjs-test 红（7 例）。该提交只跑了 tool-runtime\n单测，整轮真实库验收没有跑出来。\n\nassembleChain 增加可选 toolVersion（默认 1.0.0，其余用例不变），MCP 用例用 2.0.0。\n单独复跑两后端 MCP 组各 7/7。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T04:24:42-07:00"},{"Sha1":"c30d40f130dffe3c74b2681df6e67b21af202288","Message":"docs(治理): runtime 用例数预写 924（919 + 09-24 新增 5 例），快照锚点前移\n\n预写法省一轮 runtime：bcdcdb6 / 1a9313f 新增 employment-fact-consumer 配置 2×2 例与\nMCP 服务 profile 1 例；以本提交 clean HEAD 的 check:runtime 实测证实，预测错则改文档不改测试。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T04:18:07-07:00"},{"Sha1":"24e95d83f1020796a8449849b4ee7941b102d023","Message":"chore(reports): 静态 30/30 回绑 @ 35ebd59；快照锚点与静态证据新鲜度前移\n\n在 clean HEAD 35ebd59 上 pnpm check 30/30 通过（含新增 check:app-manifest、\nC257 后的 check:rls、tool-runtime 3.0.0 后的 kernel-packages / downstream），\n29 份报告 provenance 均为 35ebd59 / worktreeDirty=false。check:runtime、check:ui\n本轮未重跑，仍分别绑 ba482c2（09-23）与 568fb4d（09-20）。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T04:16:42-07:00"},{"Sha1":"35ebd59ea554e77cd8a5885e1b66b21acb05c42f","Message":"fix(kernel): tool-runtime 升 3.0.0 收口 bcdcdb6 的公开 API 变更；动态区用例数与快照锚点对齐\n\nbcdcdb6（09-24 受保护 MCP 接入）给 ControlPlaneMcpBinding 加了两个必填字段\nidentityAudience / identityTenantId，稳定包公开 API 变了却未升版、未更新锁，\nmain 上 pnpm check 自此停在 check:kernel-packages P7。新增必填输入字段是破坏性\n变更，按先例（1.5.0→2.0.0）升 major：kernel.packages.json / 包版本 3.0.0，\npnpm kernel-packages:lock 重建 API 锁（5/5 负探针有效），下游通用消费者 fixture\n未改源码即完成 6 包仓外安装 / 编译 / 运行时 import，kernel-downstream:lock 只动版本号。\n\n另清两处既有 docs-truth 漂移：own-test-cases / own-tests 按当前树实测 880 用例、\n114 文件（09-23 写的 875 当时成立，其后 MCP 接入等新增用例）；快照锚点前移到本提交父提交。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T04:12:06-07:00"}],"HeadCommit":{"Sha1":"27139913af5566990baea2ab77d39c1e5025a161","Message":"chore(reports): 静态 30/30 与 check:runtime 924/0 同回绑 @ 4600532\n\nclean HEAD 4600532 上 check:runtime passed（924 tests / 0 failures、30/30 步、行为矩阵\n204/204、产品验收 274 例；PG 55470 digital_employee_os_acceptance_20260926，Redis 6404/3），\n预写的 924 与实测一致；随后同一 HEAD 上 pnpm check 30/30。42 份报告 provenance 均为\n4600532 / worktreeDirty=false。check:ui 与聚合外专项 runner 本轮未跑。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T04:38:21-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/b26d51b926223ee7c225026b86701bf5121b2e04...27139913af5566990baea2ab77d39c1e5025a161","Len":7}...
|
1790422725
|
Edit
Delete
|
|
32989
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/fix/rls-grant-manifest-20260926
|
0
|
{"Commits":[{"Sha1":"160069e67 {"Commits":[{"Sha1":"160069e67a1b76c2b4abfa963fa5f08a36101714","Message":"chore(reports): 三级证据同回绑 @ 95e579c——静态 30/30、check:runtime 924/0、check:ui 33/33×2\n\nclean HEAD 95e579c 上：pnpm check 30/30；check:runtime passed（924 tests / 0 failures、30/30 步、\n行为矩阵 204/204、产品验收 274 例，juhai.hr 0.19.5 候选；PG 55470 digital_employee_os_acceptance_20260926c、\nRedis 6404/3）；check:ui passed（NestJS / Fastify 各 33/33；UI 库 digital_employee_os_ui_20260926g、Redis 6404/5）。\n45 份报告 provenance 均为 95e579c / worktreeDirty=false。\n\nCLAUDE.md：三级证据新鲜度行、ui-acceptance 基线行（每后端 33）与快照锚点前移；新增 C258（HR 0.19.x 装载后\nUI 未重跑、宿主层漂移连红五轮）与 C259（bcdcdb6 未升版、未跑整轮验收）。聚合外专项 runner 本轮未跑。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T07:09:25-07:00"},{"Sha1":"95e579c9d233d888991ecf28ab0033701b194c23","Message":"fix(ui-runner): 产品 spec 约定的主体名加 naming-ignore（check:naming 禁用词 operator）\n\nlocal-acceptance-operator 由已装载产品的验收 spec 约定，属对接外部契约的特例；按 check:naming 的\n逐行 naming-ignore 口径标注，注释改写为不含该词。仅注释与标注，runner 行为不变——\ncheck:runtime（924/0）与 check:ui（33/33×2）证据仍绑 9eea06b。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T06:50:35-07:00"},{"Sha1":"9eea06b6ec0a88d87a1f750803842b063c6ff7c2","Message":"fix(product): juhai.hr 0.19.5 候选——产品浏览器验收的审批一步由复核人完成\n\n用户裁决（2026-09-26）：产品 spec 让同一操作人自提自批，与 OS 宿主层「申请人不能审批自己的变更」\n冲突（后端不拦、界面是唯一防线），收口方式是改 spec 用复核人，不放宽宿主门闸。\n\n- products/juhai.hr/*（spec / runtime-suite / manifest）与 HR 仓分支\n fix/spec-reviewer-approval-20260926 逐字一致：spec 读可选 E2E_REVIEWER_TOKEN，审批一步切到\n local-acceptance-reviewer 会话、完成后切回操作人；未提供时行为不变（HR 宿主组合经 reviewApi\n 以复核人 token 审批）。复核人会话期间暂停控制台错误收集。版本 0.19.4 → 0.19.5。\n- kernel.products.json / lock 同步 0.19.5（kernel-products:lock，85/85 负探针）。\n- UI runner 签发复核人 token，只播种 workspace.read / personnel.read / change.transition /\n change.review 四项（与 HR harness 同组），经 E2E_REVIEWER_TOKEN 交给 spec。\n\n**候选状态**：HR 仓 0.19.5 的发布证据（bundle / 迁移运行时 / 分发 / 宿主验收）尚未重建，\nHR 分支未合入其 main；本提交先用 OS check:ui 验证方案。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T06:32:30-07:00"},{"Sha1":"6b83b3da9ca55ed21ca6f0661b969c75830d4b59","Message":"fix(ui-runner): 产品浏览器验收的 member 主体对齐 juhai.hr 0.19.x spec（local-acceptance-operator）\n\n0.19.x 的产品 spec 把会话主体与收尾撤权对象从 ui-member 改为 local-acceptance-operator，\nrunner 仍以 ui-member 签发 member token 并播种授权。前面各步照常通过（请求用 token 的 sub，\n授权挂在 ui-member 上），只在最后按新主体撤权时 DELETE /api/permissions/... 回 404。\ntoken sub 与授权播种改为同一常量。operations / dual-backend / fork-readiness /\nkernel-extensions 静态门通过。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T06:22:08-07:00"},{"Sha1":"d302f64384dd690874ca6417b3049b2f1130ff3c","Message":"fix(hr-host): 身份映射 / 任职证据 / 事实履历按 juhai.hr 0.19.x 隐私投影渲染\n\n0.19.x 服务端只回隐私投影：身份映射去掉 external_subject_id / verification_reference，改给\nexternal_subject_ref；任职证据去掉外部编号、HTTPS 地址与 SHA-256，改给 external_document_ref；\n事实履历快照收成 SUMMARY_V1 白名单。宿主层仍读旧字段——身份行只剩「provider · 」，产品浏览器\n验收在「ref:」断言处失败。\n\n按产品工作台同源口径：两类行显示 ref: + 引用前 12 位，履历行显示 fact_type · projection；\n类型定义同步收掉不再返回的字段，「替代」提示框不再以已不可得的外部编号作默认值。\nhost typecheck 通过。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T06:17:17-07:00"}],"HeadCommit":{"Sha1":"160069e67a1b76c2b4abfa963fa5f08a36101714","Message":"chore(reports): 三级证据同回绑 @ 95e579c——静态 30/30、check:runtime 924/0、check:ui 33/33×2\n\nclean HEAD 95e579c 上：pnpm check 30/30；check:runtime passed（924 tests / 0 failures、30/30 步、\n行为矩阵 204/204、产品验收 274 例，juhai.hr 0.19.5 候选；PG 55470 digital_employee_os_acceptance_20260926c、\nRedis 6404/3）；check:ui passed（NestJS / Fastify 各 33/33；UI 库 digital_employee_os_ui_20260926g、Redis 6404/5）。\n45 份报告 provenance 均为 95e579c / worktreeDirty=false。\n\nCLAUDE.md：三级证据新鲜度行、ui-acceptance 基线行（每后端 33）与快照锚点前移；新增 C258（HR 0.19.x 装载后\nUI 未重跑、宿主层漂移连红五轮）与 C259（bcdcdb6 未升版、未跑整轮验收）。聚合外专项 runner 本轮未跑。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T07:09:25-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/27139913af5566990baea2ab77d39c1e5025a161...160069e67a1b76c2b4abfa963fa5f08a36101714","Len":7}...
|
1790431783
|
Edit
Delete
|
|
32992
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/fix/rls-grant-manifest-20260926
|
0
|
{"Commits":[{"Sha1":"662b0863c {"Commits":[{"Sha1":"662b0863c55a404c7fa82e676133f2cfd315b034","Message":"chore(reports): 静态 30/30 与 check:ui 34/34×2 回绑 @ 44d89b4\n\nclean HEAD 44d89b4 上 check:ui passed（NestJS / Fastify 各 34/34，含 C18 企业应用区用例；UI 库\ndigital_employee_os_ui_20260926i、Redis 6404/5），随后同一 HEAD 上 pnpm check 30/30；32 份报告\nprovenance 均为 44d89b4 / worktreeDirty=false。check:runtime 仍绑 95e579c（其后改动只涉浏览器用例、\nrunner / mock 与文档，不在 runtime 覆盖面）。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T07:43:29-07:00"},{"Sha1":"44d89b4c91f6321b0160dab7b55d5b3bcc390fc4","Message":"docs(治理): C18 企业应用区 UI 用例入账——用例数 881、UI 基线 34/后端、C260，接缝台账 experience-shell 证据补浏览器用例\n\n首轮 check:ui 两后端各 34/34 通过，唯独收尾 docs-truth 复验因 own-test-cases 未预写（880 → 实测 881）\n把整轮降级为 failed；按 C231 纪律改文档不改测试后复跑。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T07:35:32-07:00"},{"Sha1":"cf6458dfdedcfa73577c89f81e1b1b310cefbc99","Message":"test(ui): C18 企业应用区浏览器验收——真实后端 + 来源应用 / 平台复核替身\n\nC18（DEC-044 消费侧）此前只有两后端 HTTP 验收，Shell「企业应用」区没有任何浏览器证据。\n\n- mock-llm-tool-provider 同时扮演来源应用 execution-control（GET 贡献清单，Bearer 校验）与平台\n enterprise-experience 复核（POST :review，可经 /experience/mode 切成 503）；四条贡献：可展示、\n STALE_DISPLAY_ONLY、BLOCKED、协议相对越界 deepLink。OS 后端是真实进程，不被替身。\n- runner 把 PLATFORM_EXPERIENCE_BASE_URL / TOKEN 与 EXPERIENCE_SOURCES 交给 API，两枚随机 token\n 只在 runner、mock、API 子进程之间传递。\n- 用例断言：只渲染两条（可展示 + 过期标记），href 为来源 origin + deepLink、新标签页且 noopener；\n BLOCKED 与越界入口不出现；平台复核 503 时整区不渲染（失败关闭、不拿旧结论冒充），恢复后重新出现。\n\nnaming / operations / dual-backend / fork-readiness / app-manifest / lint 通过。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T07:28:48-07:00"}],"HeadCommit":{"Sha1":"662b0863c55a404c7fa82e676133f2cfd315b034","Message":"chore(reports): 静态 30/30 与 check:ui 34/34×2 回绑 @ 44d89b4\n\nclean HEAD 44d89b4 上 check:ui passed（NestJS / Fastify 各 34/34，含 C18 企业应用区用例；UI 库\ndigital_employee_os_ui_20260926i、Redis 6404/5），随后同一 HEAD 上 pnpm check 30/30；32 份报告\nprovenance 均为 44d89b4 / worktreeDirty=false。check:runtime 仍绑 95e579c（其后改动只涉浏览器用例、\nrunner / mock 与文档，不在 runtime 覆盖面）。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T07:43:29-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/160069e67a1b76c2b4abfa963fa5f08a36101714...662b0863c55a404c7fa82e676133f2cfd315b034","Len":3}...
|
1790433823
|
Edit
Delete
|
|
32995
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/fix/rls-grant-manifest-20260926
|
0
|
{"Commits":[{"Sha1":"ba2eb4b48 {"Commits":[{"Sha1":"ba2eb4b48ece4515f3e5ed5cd01b4988ef9476f0","Message":"docs(治理): C259 裁决——MCP 工具 1.0.0 冻结实现不补回，登记为有意退役\n\n2026-09-26 用户裁决。1.0.0 对应的平台工具契约已收窄（五个工具 → 三个只读工具、endpoint 与 audience /\n业务租户与身份租户拆分），旧实现补回也调不通新平台。已绑定 1.0.0 的租户按失败关闭处理，由管理员登记并\n激活 2.0.0、重新装备与绑定凭据，不做自动迁移；C250 冻结先例仍适用于契约未变的工具升版。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T15:37:02-07:00"}],"HeadCommit":{"Sha1":"ba2eb4b48ece4515f3e5ed5cd01b4988ef9476f0","Message":"docs(治理): C259 裁决——MCP 工具 1.0.0 冻结实现不补回，登记为有意退役\n\n2026-09-26 用户裁决。1.0.0 对应的平台工具契约已收窄（五个工具 → 三个只读工具、endpoint 与 audience /\n业务租户与身份租户拆分），旧实现补回也调不通新平台。已绑定 1.0.0 的租户按失败关闭处理，由管理员登记并\n激活 2.0.0、重新装备与绑定凭据，不做自动迁移；C250 冻结先例仍适用于契约未变的工具升版。快照锚点前移。\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-26T15:37:02-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/662b0863c55a404c7fa82e676133f2cfd315b034...ba2eb4b48ece4515f3e5ed5cd01b4988ef9476f0","Len":1}...
|
1790462249
|
Edit
Delete
|
|
32999
|
5
|
17
|
5
|
76
|
0
|
0
|
refs/heads/fix/rls-grant-manifest-20260926
|
0
|
|
1790463182
|
Edit
Delete
|
|
29946
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-actions-20260912
|
0
|
|
1789445326
|
Edit
Delete
|
|
29947
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-actions-20260912
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"a5c6bc1f21ff9ee8c6740b20079b2278d5a0a306","Message":"docs(releases): record verified shijie step action deployment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-11T22:04:26-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...a5c6bc1f21ff9ee8c6740b20079b2278d5a0a306","Len":0}...
|
1789445326
|
Edit
Delete
|
|
29948
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-empty-source-sync-20260912
|
0
|
|
1789445331
|
Edit
Delete
|
|
29949
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-empty-source-sync-20260912
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"4fe8d343cc6b00bed830031e666cc0ac14cc276e","Message":"docs(releases): record live single-scene generation and visual refinement\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-11T19:40:03-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...4fe8d343cc6b00bed830031e666cc0ac14cc276e","Len":0}...
|
1789445331
|
Edit
Delete
|
|
29950
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-prop-ownership
|
0
|
|
1789445336
|
Edit
Delete
|
|
29951
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-prop-ownership
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"3760ee6c9c7c0daf89b2e5b507b083464b0bce62","Message":"test(shijie): record verified prop ownership release evidence\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-10T16:55:46-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...3760ee6c9c7c0daf89b2e5b507b083464b0bce62","Len":0}...
|
1789445336
|
Edit
Delete
|
|
29952
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-workflow-20260912
|
0
|
|
1789445341
|
Edit
Delete
|
|
29953
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-workflow-20260912
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"545c98c6ffe5270812c731aa0aa2f08ae1961ef7","Message":"docs(releases): record verified shijie workflow deployment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-11T21:19:54-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...545c98c6ffe5270812c731aa0aa2f08ae1961ef7","Len":0}...
|
1789445341
|
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
|
|
25165
|
5
|
5
|
5
|
72
|
0
|
0
|
refs/heads/fix/vm-prisma-runtime-path
|
0
|
|
1787540013
|
Edit
Delete
|
|
25166
|
5
|
5
|
5
|
72
|
0
|
0
|
refs/heads/fix/vm-prisma-runtime-path
|
0
|
{"Commits":[{"Sha1":"2de754507 {"Commits":[{"Sha1":"2de7545076ac90e4aa88e89cdf310f72ca9692ce","Message":"fix(vm): Prisma 生成物拷到运行时真正解析的位置——旧断言查的是拷贝目标而非读取路径\n\n`pnpm vm:up` 首次真跑起整栈，api-nestjs 容器启动即崩溃重启循环：\n`@prisma/client did not initialize yet. Please run \"prisma generate\"`。\n而构建期那条\"Prisma Client 必须在部署树里\"的断言是**绿的**。\n\n根因：`pnpm deploy` 把 @prisma/client 放进\n`node_modules/.pnpm/@prisma+client@\u003chash\u003e/node_modules/`，而 @prisma/client 是相对\n**自身**去找同级 `.prisma` 的——部署树顶层那份它根本不看。上一版把生成物拷到了顶层\n扁平路径，于是：\n- 运行时解析到 .pnpm 内嵌的那份，那是 @prisma/client **自带的桩**\n （`default.js` 第 43 行专门抛 \"did not initialize yet\"），没有 query engine；\n- 而断言 `test -d /runtime/\u003capp\u003e/node_modules/.prisma/client` 查的正是我刚拷过去的\n 顶层目录，\"往哪拷就查哪\"，必然通过。\n\n这是「断言检查的位置 ≠ 运行时读取的位置」，与 C23（typecheck 读 src、运行时读 dist）\n同型：不是断言写得弱，而是它锚在一条运行时不走的路径上。\n\n两处一起修：\n1. 拷贝目标改为 .pnpm 内嵌位置（顶层那份保留，覆盖 hoist 布局），glob 取不到即 fail。\n2. 断言改为**按运行时同一方式推导路径**（从 require.resolve('@prisma/client/package.json')\n 反推同级 .prisma），并断言 **query engine 二进制存在**——只 `test -d` 等于没查，\n 因为那个桩目录永远存在。\n\n负向测试（实跑）：去掉 .pnpm 拷贝那行后构建 EXIT=1，报\n`ERROR: no generated query engine at /runtime/api-nestjs/node_modules/.pnpm/@prisma+client@.../.prisma/client`\n——新断言会在构建期拦下这个 bug，而不是等容器启动才炸。\n\n证据（作用域＝本地工作区）：\n- pnpm vm:up 全流程通过：6 个服务全 healthy、migrate Exited(0)\n- 迁移真实应用到部署库（含 20260805120000_product_image_thumbnail /\n 20260807120000_quotation_void_and_restore）\n- 冒烟：Gateway + web + NestJS health passed；\n Write-chain smoke passed（create + read-back under a throwaway tenant）\n- 独立复核（不依赖脚本自述）：curl 网关 /api/health -\u003e ok(db=up,redis=up)、首页 200、\n 容器内 `new PrismaClient()` 实例化成功\n- pnpm check 22 项全绿 exit=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-17T17:36:43-07:00"}],"HeadCommit":{"Sha1":"2de7545076ac90e4aa88e89cdf310f72ca9692ce","Message":"fix(vm): Prisma 生成物拷到运行时真正解析的位置——旧断言查的是拷贝目标而非读取路径\n\n`pnpm vm:up` 首次真跑起整栈，api-nestjs 容器启动即崩溃重启循环：\n`@prisma/client did not initialize yet. Please run \"prisma generate\"`。\n而构建期那条\"Prisma Client 必须在部署树里\"的断言是**绿的**。\n\n根因：`pnpm deploy` 把 @prisma/client 放进\n`node_modules/.pnpm/@prisma+client@\u003chash\u003e/node_modules/`，而 @prisma/client 是相对\n**自身**去找同级 `.prisma` 的——部署树顶层那份它根本不看。上一版把生成物拷到了顶层\n扁平路径，于是：\n- 运行时解析到 .pnpm 内嵌的那份，那是 @prisma/client **自带的桩**\n （`default.js` 第 43 行专门抛 \"did not initialize yet\"），没有 query engine；\n- 而断言 `test -d /runtime/\u003capp\u003e/node_modules/.prisma/client` 查的正是我刚拷过去的\n 顶层目录，\"往哪拷就查哪\"，必然通过。\n\n这是「断言检查的位置 ≠ 运行时读取的位置」，与 C23（typecheck 读 src、运行时读 dist）\n同型：不是断言写得弱，而是它锚在一条运行时不走的路径上。\n\n两处一起修：\n1. 拷贝目标改为 .pnpm 内嵌位置（顶层那份保留，覆盖 hoist 布局），glob 取不到即 fail。\n2. 断言改为**按运行时同一方式推导路径**（从 require.resolve('@prisma/client/package.json')\n 反推同级 .prisma），并断言 **query engine 二进制存在**——只 `test -d` 等于没查，\n 因为那个桩目录永远存在。\n\n负向测试（实跑）：去掉 .pnpm 拷贝那行后构建 EXIT=1，报\n`ERROR: no generated query engine at /runtime/api-nestjs/node_modules/.pnpm/@prisma+client@.../.prisma/client`\n——新断言会在构建期拦下这个 bug，而不是等容器启动才炸。\n\n证据（作用域＝本地工作区）：\n- pnpm vm:up 全流程通过：6 个服务全 healthy、migrate Exited(0)\n- 迁移真实应用到部署库（含 20260805120000_product_image_thumbnail /\n 20260807120000_quotation_void_and_restore）\n- 冒烟：Gateway + web + NestJS health passed；\n Write-chain smoke passed（create + read-back under a throwaway tenant）\n- 独立复核（不依赖脚本自述）：curl 网关 /api/health -\u003e ok(db=up,redis=up)、首页 200、\n 容器内 `new PrismaClient()` 实例化成功\n- pnpm check 22 项全绿 exit=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-17T17:36:43-07:00"},"CompareURL":"luoanwu/juhai-quotation-system/compare/125c54d328d3da221b5d91c0a2dd0475712c6e96...2de7545076ac90e4aa88e89cdf310f72ca9692ce","Len":1}...
|
1787540013
|
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
|
|
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
|
|
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
|