| content |
{"Commits":[{"Sha1":"b60cc18d6 {"Commits":[{"Sha1":"b60cc18d640a6561ccdd0fa798753d1f6476bad5","Message":"chore(reports): runtime 静态门禁链整批回绑 @ 7fc7f02\n\n在 7fc7f02 的干净 detached worktree 里跑完整 `pnpm --dir runtime check`\n（先 install --frozen-lockfile + prisma:generate，否则 api-nestjs#build 会以\n@prisma/client 缺导出成员一类的 TS 错误失败）：turbo 31/31，聚合\nruntime/reports/governance.latest.json status=passed，15 项违规指标全 0——\n其中 reportProvenanceViolations=0，正是此前单跑一道门禁做不到的那一条。\n\n18 份静态子报告现在同绑 7fc7f02 / worktreeDirty=false，15 份共用同一 runId\n（permission-catalog 与 platform-ops-definitions 沿用各自的 sync 脚本 runId，与改动前一致）。\n\n三份高等级真跑证据按原样保留、未被覆盖：runtime-acceptance @ 08c3788、\nui-acceptance @ 1b23285、conformance-differential @ 08c3788。\n\nCo-Authored-By: Claude Opus 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-18T15:48:28-07:00"},{"Sha1":"57023cdc23442303c3336e86a433638d16c29452","Message":"docs(治理): 订正两处版本声明——内核 pin 落后六个 minor，contracts 落后两个 RC\n\n两处都是带来源标注、看起来可核对的事实，实际都已漂：\n\n- 内核 pin 写 `@juhai/kernel@0.16.1`，实际 `runtime/pnpm-lock.yaml` 解析到 `0.22.0`\n （tarball 确在 Gitea `luoanwu`，来源描述本身没错），12 个 package.json 声明一致。\n- contracts 写 `1.0.0-rc.1`。2026-09-18 向 Gitea Registry 实查：`@juhai/contracts` 的\n rc.0 / rc.1 / rc.2 / rc.3 四版俱在，与 `contracts/package.json` 的 rc.3 一致；\n `@juhai/governance` 同为四版，`@juhai/client-fact` 为 rc.2 / rc.3。\n\n顺带把发布通道写进去，避免下一个人把 rc.3 当成走过发布门禁的版本：rc.2 与 rc.3 都经\n本地旁路通道发出（rc.2 见 docs/G-12本地旁路发布记录-2026-09-13.md，源 eb3cf2c，\nprovenance.json 如实写 runner:\"local\"）。按 G-12 划的边界，这两版可称「已发布、可被\nexact pin 消费」，不得称「经过发布门禁验证」。\n\n**rc.3 在仓内没有对应的发布记录文档**（G-12 只记到 rc.2，而 runtime/clients/README.md\n与两份清单都已按「rc.3 已发布」在引用它）——本次只把缺口标注出来，补记录另做。\n\n这两处此前无人守：治理层 L13 只守「治理层自己的」裁决数 / 平台项目数 / 收纳表文件数，\n不覆盖真源仓 CLAUDE.md 的版本 pin。改 pin 时须手动回来改这两行。\n\nCo-Authored-By: Claude Opus 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-18T15:48:19-07:00"},{"Sha1":"7fc7f02c88c9768be49c80096b80962a6d6624ad","Message":"docs(治理): runtime 动态区回灌两级验收 SHA——报告已跑到 08c3788 / 1b23285，动态区还停在 765300b\n\ncheck:docs-truth 的 freshness-sha-runtime / freshness-sha-ui 两条在 HEAD 上就是红的：\nruntime-acceptance 与 ui-acceptance 已分别重跑并绑定 08c3788 / 1b23285，而动态区仍声明\n765300b，连带隔离栈与端口也是上一轮的（ms23-ci :55485 / :56395 db10、web :3157）。\n\n按两份报告逐字回灌：775 tests / 0 failures、5 用例 / 0 失败、tenantRlsEnforced=1、\n验收库 enterprise_platform_acceptance_20260918（PG :55471）+ Redis :56380 db7、\nweb :3120 / api :3222。删掉「框架同步后首跑」——那是 765300b 那一轮的上下文，\n08c3788 已是其后的再跑。\n\nCo-Authored-By: Claude Opus 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-18T15:47:25-07:00"},{"Sha1":"772b253623b14f66b8cd1bfddd60901348d5ca9b","Message":"chore(reports): release-manifest / sbom / naming / fork-readiness 四份回绑 @ 04d02d6\n\n四份都是真过期（与上一轮 module-imports 不同——那份实为已新鲜、误判后我撤回未提交）：\n\n release-manifest 作用域内 reports/image-digest.json 与 stack/compose.yaml 变更\n sbom 作用域内 reports/image-digest.json 变更，即它描述的是旧镜像\n naming runtime/apps/workbench 四个源文件变更\n fork-readiness 同上\n\n生成方式同 de532d4：主工作区常驻并行会话在途文件、拿不到干净树，按偏差 #34-A 裁决\n「不放宽 worktreeDirty 判据，改为换个干净的地方生成报告」，在 HEAD 开 worktree\n（落在 企业控制面/.worktrees/，workspaceRelative 套件要向上找 workspace.json）跑门禁\n再带回。release-manifest 与 sbom 的生成器在零依赖的 governance/ 下，无需 install；\nnaming 与 fork-readiness 需要已安装的私有内核包，故在检出内 pnpm --dir runtime install。\n\n四份结论逐项与旧版对照，无一劣化：\n\n release-manifest status 仍 partial，缺项仍 6 条；只有镜像绑定那条的 sha 随之更新\n （d8f0920 ≠ b202dde → 05e3826 ≠ 04d02d6），runtime 镜像仍未在 HEAD 重建\n sbom coverage 仍 partial、268 包不变；ref 由 fe418667 更新为 c0869934，\n 即它现在描述的是当前登记的镜像而不是旧的那个。连带重出\n reports/sbom.spdx.json，其 sha256 与报告记录实算一致（ecc5e62e…）\n naming violations 0 不变\n fork-readiness violations [] / forkReadinessViolations 0 不变\n\n四份 provenance 均绑 04d02d6、worktreeDirty=false，与提交时主仓 HEAD 一致。\n\nCo-Authored-By: Claude Opus 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-18T15:46:46-07:00"}],"HeadCommit":{"Sha1":"b60cc18d640a6561ccdd0fa798753d1f6476bad5","Message":"chore(reports): runtime 静态门禁链整批回绑 @ 7fc7f02\n\n在 7fc7f02 的干净 detached worktree 里跑完整 `pnpm --dir runtime check`\n（先 install --frozen-lockfile + prisma:generate，否则 api-nestjs#build 会以\n@prisma/client 缺导出成员一类的 TS 错误失败）：turbo 31/31，聚合\nruntime/reports/governance.latest.json status=passed，15 项违规指标全 0——\n其中 reportProvenanceViolations=0，正是此前单跑一道门禁做不到的那一条。\n\n18 份静态子报告现在同绑 7fc7f02 / worktreeDirty=false，15 份共用同一 runId\n（permission-catalog 与 platform-ops-definitions 沿用各自的 sync 脚本 runId，与改动前一致）。\n\n三份高等级真跑证据按原样保留、未被覆盖：runtime-acceptance @ 08c3788、\nui-acceptance @ 1b23285、conformance-differential @ 08c3788。\n\nCo-Authored-By: Claude Opus 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-18T15:48:28-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/04d02d611af85737ed1ee7ae7d6644b6dedb51ad...b60cc18d640a6561ccdd0fa798753d1f6476bad5","Len":4}... |