|
31046
|
11
|
5
|
1
|
18
|
0
|
0
|
refs/heads/pc-261020
|
0
|
|
1789718620
|
Edit
Delete
|
|
31054
|
11
|
5
|
1
|
18
|
0
|
0
|
refs/heads/pc-261020
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"a9e17e07df844a597a4e7aef47c08235a41d3d49","Message":"Merge pull request '11111' (#223) from pc-260818 into pc\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pc/pulls/223\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-15T09:38:55+08:00"},"CompareURL":"vodtest/pc/compare/pc...a9e17e07df844a597a4e7aef47c08235a41d3d49","Len":0}...
|
1789718620
|
Edit
Delete
|
|
31055
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"2d4b55254 {"Commits":[{"Sha1":"2d4b55254cd0b38f4ae1750038d4a6d9e2ebb30a","Message":"chore(reports): check:gate-flow 回绑 @ 574cfb7\n\n45 个脚本、33 个有消费入口、12 个流外且全部具名（门禁 4 / 工具 8）、0 违规。\n并行会话正在本仓改 Dockerfile 与底座，主工作区非干净树——经 reports:rebind 在\nHEAD 的干净检出里生成，未触及对方在途文件。\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-18T01:09:55-07:00"},{"Sha1":"f3ae97f3460699338d08efe3dd60ea69a3d49fa4","Message":"feat(stack,runtime): dev 常驻运行时接上受控执行面与统一服务目录快照（CHG-018 条件 A 的目标环境半边）\n\ncompose 的 runtime 服务此前没有 PLATFORM_OPS_ENABLED / _CLIENT_IDS / _ADMIN_SUBJECTS，也没有\nPLATFORM_CATALOG_SNAPSHOT_PATH：OPS-1 的命令面在 dev 容器里根本不存在（定义 executable=false），\n/api/platform/catalog 的 snapshot 恒为 unavailable。仓内验收过的两个面没有任何一条路径到达运行环境，\nOPS-1 记录里「目标环境验收留阶段 ②」说的就是这一段。\n\n- stack/compose.yaml：四个键全部空默认值——不配置 = 不开命令面，而不是开着没人管\n- stack/overlays/dev.yaml：reports/workbench-catalog-snapshot.latest.json 只读挂到\n /srv/runtime/catalog-snapshot.json，快照绑的是它自己的 gitSha，不是本进程\n- runtime/Dockerfile：ENV PLATFORM_SOURCE_SHA=${SOURCE_SHA}，与 OCI revision 标签同源；\n 缺它时目录读面只能报 source_sha_status=unknown，不从文件系统猜\n- docs/runbook.md：§2 环境表补两行，并写明改这四个键必须重建容器（restart 带不上新环境）\n\n本提交只改配置与镜像环境变量；镜像重建、容器切换与探针结果另行取证提交。\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-18T01:09:52-07:00"},{"Sha1":"574cfb754278102c1588009c4af3a66dc2201777","Message":"feat(governance): 补 check:gate-flow——每个门禁的失败信号有谁在看？\n\n治理层 2026-09-14 就为自己建了 `门禁消费登记.json` 逐条回答这个问题，并写明了病因：\n一个门禁若既不在统一流内、也不在任何 CI 链里，它就停在「永远红」或「永远绿」，\n两种都不再携带信息。本仓一直没问过这个问题。\n\n实测：根 package.json 44 个脚本里 12 个既不在 `pnpm check` 链、CI 也不调用。\n多数是工具与开发者聚合入口（已逐条核实其组成部分确被消费），但其中三个是真门禁：\n\n image:smoke CI 的 image job 构建镜像、生成 SBOM、签名，**却从不启动它一次**。\n 而开发计划把这六项冒烟写成 D-1 的退出条件。更要紧的是\n `image-smoke.latest.json` 在 evidence-scopes 的未登记账里写着\n 「待其下一次真实运行后登记」——而没有任何东西会触发那次运行，\n 于是那条搁置根本没有出口。本轮把它写成带复核期的具名条件。\n promotion:check DEC-024 / DEC-026 的晋级判据，事件驱动，硬接进 check 链只会恒绿\n check:deployed 活体核验，CI runner 上没有长驻底座，接进去等于加一个恒定跳过\n\n三个各有理由，但理由此前只散在 CLAUDE.md / README 的散文里，没有一条有复核期。\n\n**消费关系一律自动推导，不接受声明。** 治理层那套让登记表自报 consumption 再用 G3\n去源码里证伪；本仓直接从 check 链的递归展开与两份 CI 工作流现取——声明会撒谎，\n推导不会。CI 有几处绕开 pnpm 直接 `node governance/build-image.mjs`，因此除按名匹配\n外还按脚本里出现的 .mjs 路径匹配（用例钉住这两条与正则转义）。\n`governance/gate-flow.json` 因此只装推不出来的那些：随接线逐条变少（F2 会拦下\n已被消费却还留着的腐烂登记），也不能无声变多（F1 拦下任何新出现的未说明脚本）。\n\nF4 守的是日期不是条件：接入条件多半含人的判断（「Secret 到位后」「首次晋级时」），\n不可能机器化；能机器化的是必须有人按期回来看一眼。同形判据已在治理层\ngate-registry-core 的 G6 与 domain-layer-baseline 的 B4 上验证过：缓期不是豁免。\n\n已串进 `pnpm check`（放 check:evidence 之前，纯静态先跑先报），报告登记进\nevidence-scopes（severity=error，作用域逐条对应它实际读的文件），并加入\nreports:rebind 的零依赖清单——本仓常有并行会话，脏树上拿不到干净绑定。\n\n治理测试 283 → 298。当前：45 个脚本，33 个有消费入口，12 个流外且全部具名\n（门禁 4 / 工具 8）。\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-18T01:09:11-07:00"}],"HeadCommit":{"Sha1":"2d4b55254cd0b38f4ae1750038d4a6d9e2ebb30a","Message":"chore(reports): check:gate-flow 回绑 @ 574cfb7\n\n45 个脚本、33 个有消费入口、12 个流外且全部具名（门禁 4 / 工具 8）、0 违规。\n并行会话正在本仓改 Dockerfile 与底座，主工作区非干净树——经 reports:rebind 在\nHEAD 的干净检出里生成，未触及对方在途文件。\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-18T01:09:55-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/0abd15c28dd2b92c583289934db660363b202fd4...2d4b55254cd0b38f4ae1750038d4a6d9e2ebb30a","Len":3}...
|
1789719017
|
Edit
Delete
|
|
31056
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"392f0fde4 {"Commits":[{"Sha1":"392f0fde46813c5d061762b8985c74948f6bb088","Message":"docs(计划): 登记 check:gate-flow——真源仓补上「每个门禁的失败信号有谁在看」\n\n治理层 2026-09-14 已为自己建了门禁消费登记并写明病因，真源仓一直没问过这个问题。\n实测 44 个脚本里 12 个既不在 check 链、CI 也不调用，其中三个是真门禁；最实的一处是\nCI 的 image job 构建、生成 SBOM、签名镜像却从不启动它一次，而那六项冒烟正是 D-1 的\n退出条件——且 image-smoke 报告在未登记账里的搁置因此没有出口。\n\n消费关系自动推导不接受声明，登记表只装推不出来的那些，随接线变少、不能无声变多。\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-18T01:10:55-07:00"}],"HeadCommit":{"Sha1":"392f0fde46813c5d061762b8985c74948f6bb088","Message":"docs(计划): 登记 check:gate-flow——真源仓补上「每个门禁的失败信号有谁在看」\n\n治理层 2026-09-14 已为自己建了门禁消费登记并写明病因，真源仓一直没问过这个问题。\n实测 44 个脚本里 12 个既不在 check 链、CI 也不调用，其中三个是真门禁；最实的一处是\nCI 的 image job 构建、生成 SBOM、签名镜像却从不启动它一次，而那六项冒烟正是 D-1 的\n退出条件——且 image-smoke 报告在未登记账里的搁置因此没有出口。\n\n消费关系自动推导不接受声明，登记表只装推不出来的那些，随接线变少、不能无声变多。\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-18T01:10:55-07:00"},"CompareURL":"luoanwu/platform-governance/compare/f0d1f11ac7747e845e2781e441cf35bf86717dd5...392f0fde46813c5d061762b8985c74948f6bb088","Len":1}...
|
1789719058
|
Edit
Delete
|
|
31059
|
1
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"b95bc8ca6 {"Commits":[{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"}],"HeadCommit":{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"},"CompareURL":"vodtest/app/compare/82bea1818b4939b2669fa482282e55b08d09988a...b95bc8ca61a1eee32824ca00934dcd4561260235","Len":1}...
|
1789719063
|
Edit
Delete
|
|
31060
|
3
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"b95bc8ca6 {"Commits":[{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"}],"HeadCommit":{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"},"CompareURL":"vodtest/app/compare/82bea1818b4939b2669fa482282e55b08d09988a...b95bc8ca61a1eee32824ca00934dcd4561260235","Len":1}...
|
1789719063
|
Edit
Delete
|
|
31061
|
4
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"b95bc8ca6 {"Commits":[{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"}],"HeadCommit":{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"},"CompareURL":"vodtest/app/compare/82bea1818b4939b2669fa482282e55b08d09988a...b95bc8ca61a1eee32824ca00934dcd4561260235","Len":1}...
|
1789719063
|
Edit
Delete
|
|
31062
|
7
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"b95bc8ca6 {"Commits":[{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"}],"HeadCommit":{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"},"CompareURL":"vodtest/app/compare/82bea1818b4939b2669fa482282e55b08d09988a...b95bc8ca61a1eee32824ca00934dcd4561260235","Len":1}...
|
1789719063
|
Edit
Delete
|
|
31057
|
8
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"b95bc8ca6 {"Commits":[{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"}],"HeadCommit":{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"},"CompareURL":"vodtest/app/compare/82bea1818b4939b2669fa482282e55b08d09988a...b95bc8ca61a1eee32824ca00934dcd4561260235","Len":1}...
|
1789719063
|
Edit
Delete
|
|
31058
|
9
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"b95bc8ca6 {"Commits":[{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"}],"HeadCommit":{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"},"CompareURL":"vodtest/app/compare/82bea1818b4939b2669fa482282e55b08d09988a...b95bc8ca61a1eee32824ca00934dcd4561260235","Len":1}...
|
1789719063
|
Edit
Delete
|
|
31063
|
10
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"b95bc8ca6 {"Commits":[{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"}],"HeadCommit":{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"},"CompareURL":"vodtest/app/compare/82bea1818b4939b2669fa482282e55b08d09988a...b95bc8ca61a1eee32824ca00934dcd4561260235","Len":1}...
|
1789719063
|
Edit
Delete
|
|
31064
|
11
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"b95bc8ca6 {"Commits":[{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"}],"HeadCommit":{"Sha1":"b95bc8ca61a1eee32824ca00934dcd4561260235","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T16:10:58+08:00"},"CompareURL":"vodtest/app/compare/82bea1818b4939b2669fa482282e55b08d09988a...b95bc8ca61a1eee32824ca00934dcd4561260235","Len":1}...
|
1789719063
|
Edit
Delete
|
|
31065
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"832f9b2e5 {"Commits":[{"Sha1":"832f9b2e5ab646a48adbf37b80db1d41092f2f7e","Message":"chore(reports): tenant.ts 拆分第三步的十三份静态门禁证据 回绑 @ a0a9f1a\n\n十三份全部 clean 绑定（worktreeDirty:false）：naming / schema-sync / validation-source /\ncontract-consumers / dual-backend-parity / kernel-boundaries / kernel-packages /\nkernel-downstream / kernel-extensions / statemachine-write-guard / list-bounds /\nfork-readiness 十二绿；kernel-admission 仍是引入时那 8 处（K3 一处 + K4 七处），\n与三步拆分前逐条一致——全程未引入新红，也未消除旧红。\n\n三步各自撞到的门禁都如实红过再修，没有一处是先改门禁再做变更：\n第一步 K1（导出归属漂移）；第二步 K1 + kernel-packages P7（公开面变更须伴随版本上调）\n+ kernel-downstream D1（下游安装版本随之重签）；第三步同上两处 P7 / D1。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T01:12:22-07:00"},{"Sha1":"a0a9f1aa5d77ac7d1c9b74a3e445a323a205f5b6","Message":"refactor(contracts): tenant.ts 拆分第三步——自建权限改名 authorization.ts，tenant 之名腾空\n\n第一步迁出 work 域判定、第二步迁出自建身份之后，tenant.ts 剩下的 22 个导出整体就是\n「自建权限」一类。因此第三步不是搬符号，是给文件正名。\n\n packages/contracts/src/tenant.ts → packages/contracts/src/authorization.ts\n\n改名本身的价值不只是可读性：OS 的 tenant.ts 与框架 @juhai/kernel 的同名文件**共有导出 0 个**，\n框架那份是租户解析策略（normalizeTenantId / tenantIdFromClaims / decideTenantResolution /\nresolveAuthMode / AUTH_MODES），OS 一个都没有。两个同名不同义的文件是「形似而神不同」漂移\n最典型的载体。改名之后 tenant.ts 这个名字腾空，留给内核退回 pin 时由 @juhai/kernel 提供的\n真正租户原语——顺带补上 OS 现在缺的 tenantId 形状与长度校验（当前主口径是无上限的\nz.string().min(1)，另有两处 .max(128) 与 employment-projection.ts 的 ^ten_.+$，三套并存）。\n\n同步改动：\n\n- 六处 import 改指：identity.ts / outcome.ts / task.ts / index.ts / kernel.ts / contracts.test.ts。\n- check-dual-backend-parity.mjs 的 C52 两条断言（权限目录与角色默认值、ALLOW/DENY 优先级）\n 改指 authorization.ts。C52 没有专用负向探针，但 expectSource 对缺失文件计 missing file\n 违规（fail-closed），门禁绿即证明两条断言在新路径上真实命中，不是指向不存在文件的假绿。\n- kernel.boundaries.json：CORE 的 contractModules 由 tenant.ts 改为 authorization.ts。\n- check-kernel-admission.mjs 头部叙述里的 tenant.ts 改为历史表述，不再指向已不存在的路径。\n- @repo/contracts 1.17.0 → 1.18.0（根与 kernel 两个 barrel 的 export 行都变了，P7 要求公开面\n 变更伴随版本上调）；kernel.packages.lock.json / kernel.downstream.lock.json /\n kernel.exports.lock.json 三把锁随之重签。\n\n本步**未**把自建权限移出 @repo/contracts/kernel 子路径。按同一套理由（铁律三：平台拥有规则）\n它和自建身份一样不属于跨产品必需的内核契约，但从已声明的稳定子路径上摘除符号是**破坏性\n收窄**，应单独裁定并走主版本号，不随改名夹带。实测当前 kernel 子路径的唯一消费者是下游夹具\n的命名空间导入，产品侧零具名消费——真要摘，成本主要在版本语义而非调用方。\n\n三步累计：tenant.ts 1075 行 / 65 导出 → authorization.ts 273 行 / 22 导出\n+ identity.ts 818 行 / 23 导出 + task.ts / outcome.ts 各收 3 / 1 个 + 17 个降私有。\n\n验证：@repo/contracts 24 文件 312/312（三步前后四次逐次一致，行为中性）；typecheck 13/13；\nnaming / schema / validation / contract-consumers / dual-backend / kernel-boundaries /\nkernel-packages / kernel-downstream / kernel-extensions / write-guard / list-bounds /\nfork-readiness 十二门全绿；kernel-admission 仍是引入时那 8 处，未引入新红。\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-18T01:11:37-07:00"},{"Sha1":"d7c932b537561ae02bcc860d506fea7c1d878b30","Message":"chore(reports): tenant.ts 拆分第二步的十份静态门禁证据 回绑 @ 439c6f7\n\n十份全部 clean 绑定（worktreeDirty:false）：naming / schema-sync / validation-source /\ncontract-consumers / dual-backend-parity / kernel-boundaries / kernel-packages /\nkernel-downstream / kernel-extensions 九绿；kernel-admission 仍是引入时那 8 处\n（K3 一处 + K4 七处），与两步拆分前逐条一致——未引入新红，也未消除旧红。\n\n本步中 kernel-packages 的 P7 与 kernel-downstream 的 D1 都如实报过红：前者要求根 barrel\n新增导出必须伴随版本上调（@repo/contracts 1.16.0 → 1.17.0），后者要求下游夹具的安装版本\n随之重签。两处都是设计内的「变更即复核」，不是绕过。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T01:08:09-07:00"},{"Sha1":"439c6f7e34f48f718f18479aa1dd2e9a9e3fcfe1","Message":"refactor(contracts): tenant.ts 拆分第二步——自建身份迁出 identity.ts\n\n框架 @juhai/kernel 的 tenant.ts 在 0.4.0—0.7.0 之间把边界写死为「本文件只做策略，\n不做验签」：验签需要密钥/JWKS，而契约包被 web 直接 import，密钥语义不能泄漏进浏览器包。\nOS 分叉于框架 0.1.0，没见过这条边界，于是策略、验签、自建权限、work 域判定四类长进了\n同一个文件。第一步已迁出 work 域判定，本步迁出身份一类。\n\n packages/contracts/src/identity.ts（新增，818 行 / 23 导出）\n 验签原语（注入式，契约包自身不 import node:crypto）、JWKS 密钥库、\n 浏览器身份与会话、OIDC PKCE 三组 schema、启动姿态门、实时连接过期、\n 鉴权入口 resolveTenantAuth，以及 token 解码/比对等私有管道\n\n packages/contracts/src/tenant.ts（273 行 / 22 导出，原 1042 行 / 44 导出）\n 只剩自建权限一类：角色与权限词汇表、ALLOW/DENY 判定、授权 DTO、审计载荷\n\n两处归属判断值得记下：\n\n- bindAuditActorSubject / AuditActorBinding 一并迁入 identity.ts。它绑定的是**已验签的\n sub**，属身份来源而非授权判定；留在 tenant.ts 会让授权侧反向依赖 TenantAuthPosture，\n identity ↔ tenant 成环。\n- roleFromClaim 留在 tenant.ts 并升为导出。它是角色词汇表的一部分（claim → 合法角色），\n 两侧都要用；反过来把它搬进 identity 会让 resolveEffectiveRole 反向依赖，同样成环。\n\n依赖方向单向：identity → tenant（借 TENANT_ROLES / TenantRole / roleFromClaim），\ntenant 不反向依赖 identity。切分前已用脚本枚举 75 个顶层声明的引用图逐条验证无反向边。\n\nidentity.ts **不进 @repo/contracts/kernel 子路径**，只经根 barrel 导出：自建身份不是跨产品\n必需的内核契约，后续应换成企业 IdP 的 client-identity。\n\n同步改动：\n\n- check-dual-backend-parity.mjs 三处按路径钉在 tenant.ts 的断言改指 identity.ts——\n C51（启动姿态判定与断言）、C181（实时过期策略）、C73（已验签 sub 的审计主体绑定）。\n 改完用门禁自带负向探针验活：DUAL_BACKEND_NEGATIVE_PROBE=missing-realtime-auth-expiry\n 与 =missing-audit-actor-binding 均如期转红，断言不是改成了指向不存在文件的假绿。\n C52 两条仍在 tenant.ts（权限目录与 ALLOW/DENY 优先级未动）。\n- kernel.boundaries.json：identity.ts 登记进 CORE 的 contractModules（30 → 31）。\n- @repo/contracts 1.16.0 → 1.17.0。check:kernel-packages 的 P7 要求公开面变更必须伴随\n 版本上调；根 barrel 新增一行 export * 是加法变更，取次版本。kernel.packages.json 与\n kernel.packages.lock.json / kernel.downstream.lock.json 随之重签（后者只改版本号一行）。\n\n顺带修正上一笔提交里的说法，方向不变但更准确：check:kernel-packages 的 apiDigest 只哈希\nrequiredExports 入口的 .d.ts，而入口就是 barrel——它看得见「根 barrel 多了一行 export *」，\n看不见任何具体符号的增删。上一步降私有 17 个符号它全绿，正是这个原因。\n\n验证：@repo/contracts 24 文件 312/312（三次拆分前后逐次一致，行为中性）；typecheck 13/13；\nnaming / schema / validation / contract-consumers / dual-backend / kernel-boundaries /\nkernel-packages / kernel-downstream / kernel-extensions 九门全绿；kernel-admission 仍是\n引入时那 8 处（K3 一处 + K4 七处），未引入新红。kernel.exports.lock.json 重签为\n39 个模块 / 763 个导出。\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-18T01:07:27-07:00"}],"HeadCommit":{"Sha1":"832f9b2e5ab646a48adbf37b80db1d41092f2f7e","Message":"chore(reports): tenant.ts 拆分第三步的十三份静态门禁证据 回绑 @ a0a9f1a\n\n十三份全部 clean 绑定（worktreeDirty:false）：naming / schema-sync / validation-source /\ncontract-consumers / dual-backend-parity / kernel-boundaries / kernel-packages /\nkernel-downstream / kernel-extensions / statemachine-write-guard / list-bounds /\nfork-readiness 十二绿；kernel-admission 仍是引入时那 8 处（K3 一处 + K4 七处），\n与三步拆分前逐条一致——全程未引入新红，也未消除旧红。\n\n三步各自撞到的门禁都如实红过再修，没有一处是先改门禁再做变更：\n第一步 K1（导出归属漂移）；第二步 K1 + kernel-packages P7（公开面变更须伴随版本上调）\n+ kernel-downstream D1（下游安装版本随之重签）；第三步同上两处 P7 / D1。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T01:12:22-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/614681e6e78d0385bbf043ef964bd444d8e5958b...832f9b2e5ab646a48adbf37b80db1d41092f2f7e","Len":4}...
|
1789719150
|
Edit
Delete
|
|
31066
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ed4a869bd {"Commits":[{"Sha1":"ed4a869bde4de3243013e74e7f48454e053bd2fa","Message":"docs(框架): 提 FR-7——governance.rules 的 mode 与 ADR-0010 状态的耦合没有执行者\n\nADR-0010 正文写着「在本 ADR 仍为 Proposed 时，mode 固定为 observe」。这句话是整份\n17 条规则注册表**是建议还是约束**的唯一依据。2026-09-18 逐行走读实测：没有任何东西\n在执行它。\n\n governance.rules.schema.json 只把 mode 约束成枚举，管形状不管该是哪个\n check-governance-rules.mjs 校验了 profile 入口、例外到期、enforced 规则须有\n owner、依赖成环等多项，唯独从不判 mode——全文只在\n 成功行里把它打印出来\n generate-governance-status.mjs 按正则读了 ADR 状态，但只回显进报告，不参与判定\n\n两个方向的失效都是静默的：把 mode 翻成 enforced 而 ADR 仍 Proposed 会全绿；ADR 受理\n之后 mode 一直留在 observe 也全绿，17 条规则就此永远停在诊断态，既无提示也无复核期。\n这是「搁置没有出口」，而且落在治理模型的核心开关上。另有一处降级：decisionStatus\n取不到时静默退回 \"Unknown\" 并照常回显，ADR 标题改一个字就会让这条读取无声失效。\n\n请求逐字落实 ADR 已写的那句，不新增政策；不改 schema、不改任何规则的 severity 或\nenforcement、不改 mode 当前取值——今天跑起来仍全绿，只在有人动 mode 或动 ADR 状态时\n才说话。\n\n**本仓未做任何本地修正**：governance.rules.json、其 schema、check-governance-rules.mjs\n与 ADR-0010 四者在 enterprise-platform/runtime/ 下与框架仓逐字相同，本仓改它等于分叉\n框架治理核心，下次同步必冲突。这与 FR-6 的处置不同——那条本仓已本地修正是因为它只在\n本仓恒红，而这条改的是框架给所有派生仓的判据。\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-18T01:18:22-07:00"}],"HeadCommit":{"Sha1":"ed4a869bde4de3243013e74e7f48454e053bd2fa","Message":"docs(框架): 提 FR-7——governance.rules 的 mode 与 ADR-0010 状态的耦合没有执行者\n\nADR-0010 正文写着「在本 ADR 仍为 Proposed 时，mode 固定为 observe」。这句话是整份\n17 条规则注册表**是建议还是约束**的唯一依据。2026-09-18 逐行走读实测：没有任何东西\n在执行它。\n\n governance.rules.schema.json 只把 mode 约束成枚举，管形状不管该是哪个\n check-governance-rules.mjs 校验了 profile 入口、例外到期、enforced 规则须有\n owner、依赖成环等多项，唯独从不判 mode——全文只在\n 成功行里把它打印出来\n generate-governance-status.mjs 按正则读了 ADR 状态，但只回显进报告，不参与判定\n\n两个方向的失效都是静默的：把 mode 翻成 enforced 而 ADR 仍 Proposed 会全绿；ADR 受理\n之后 mode 一直留在 observe 也全绿，17 条规则就此永远停在诊断态，既无提示也无复核期。\n这是「搁置没有出口」，而且落在治理模型的核心开关上。另有一处降级：decisionStatus\n取不到时静默退回 \"Unknown\" 并照常回显，ADR 标题改一个字就会让这条读取无声失效。\n\n请求逐字落实 ADR 已写的那句，不新增政策；不改 schema、不改任何规则的 severity 或\nenforcement、不改 mode 当前取值——今天跑起来仍全绿，只在有人动 mode 或动 ADR 状态时\n才说话。\n\n**本仓未做任何本地修正**：governance.rules.json、其 schema、check-governance-rules.mjs\n与 ADR-0010 四者在 enterprise-platform/runtime/ 下与框架仓逐字相同，本仓改它等于分叉\n框架治理核心，下次同步必冲突。这与 FR-6 的处置不同——那条本仓已本地修正是因为它只在\n本仓恒红，而这条改的是框架给所有派生仓的判据。\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-18T01:18:22-07:00"},"CompareURL":"luoanwu/platform-governance/compare/392f0fde46813c5d061762b8985c74948f6bb088...ed4a869bde4de3243013e74e7f48454e053bd2fa","Len":1}...
|
1789719506
|
Edit
Delete
|
|
31067
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1e6f71d84 {"Commits":[{"Sha1":"1e6f71d846a9ad3bcbd04a3f2b5fdb3f69ca1884","Message":"chore(reports): check:gate-flow 回绑 @ 5003319\n\n剥注释后判定结果不变：45 个脚本、33 个有消费入口、12 个流外且全部具名、0 违规。\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-18T01:20:03-07:00"},{"Sha1":"5003319dcea673584371b081f59f4e347a33c4ae","Message":"fix(governance): check:gate-flow 先剥 CI 注释再匹配——否则它会亲手把自己的发现消音\n\n推导层原本直接在 CI 原文上按名匹配。工作流里本来就有\n`# static → 私有包认证 … + 根 pnpm check（含 runtime 静态门禁）` 这样的说明行，\n它没被误判纯属侥幸：`check` 后面跟的是中文括号，不是空白。只要有人写下\n「待 Secret 后加 pnpm image:smoke 这一步」，不剥注释就会把这个门禁**最实的那条发现**\n判成已被消费，随后 F2 还会反过来要求删掉那条登记。\n\n剥注释的代价是可能漏判（shell 里 `#` 之后的真命令被切掉），而漏判只会多要一条登记、\n逼人看一眼，是安全的那一侧。\n\n同时把两条刻意的保守取舍写进文件头，并在登记表 note 里记下测量结论，免得被\"优化\"掉：\n\n一、**不扫脚本正文**。消费确实可能发生在脚本内部，但天真地按名扫正文更糟——实测\n本仓 `lib/gate-flow-core.mjs` 自己的注释里就写着 image:smoke / promotion:check /\ncheck:deployed 三个名字，扫正文会把这个门禁要报的三条发现全部判成已消费。\n\n二、**扫描面只有根 package.json，这是量过之后的决定**。另外三个 pnpm 根逐个测过，\n没有真空缺：runtime 的 check:conformance:differential 被 check-runtime-acceptance\n的 plan 数组 spawn；check-runtime-governance 与 generate-governance-status 被 profile\n运行器与 governance-report 调用；check:kernel / :production / :conformance 是框架给的\nprofile 分组、其成分检查已逐条在 runtime 的 check 链里；identity 的\ncheck:dual-backend-behavior 被该仓 check-runtime-acceptance 调用。这些消费全在脚本\n正文内部，要判它们就得解析 spawn 的实参数组，而那正是第一条否掉的方向。\n\ngate-flow 测试 15 → 18，治理测试 298 → 301。判定结果不变：45 个脚本 / 33 有消费入口 /\n12 流外且全部具名。\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-18T01:19:48-07:00"},{"Sha1":"dbc608b892652e920970ea5368a57a02263d9915","Message":"chore(reports): 工作台两份快照回绑 @ b1c2c0d\n\n本轮部署证据落进运维快照作用域（image-digest / image-smoke / deployed-runtime / runtime-up），\n经 reports:rebind 在 HEAD 的干净检出里重跑，两份同源快照一并带回。\n\n顺带实测：dev overlay 把目录快照按路径只读挂进容器，rebind 带回新文件后\nGET /api/platform/catalog 立刻报出新的 snapshot.provenance.gitSha=b1c2c0d，无需重建容器。\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-18T01:19:18-07:00"},{"Sha1":"b1c2c0dc197166f41437f03707ad0a1bd11448c1","Message":"chore(reports): dev 重新部署证据回绑 @ d8f0920 / 759e559\n\n- image-digest：干净检出构建的 d8f09205c8a5（worktreeDirty=false，contextMode=head）\n- image-smoke：6/6（scope 单 profile、Redis 逻辑库 15、:53009）\n- pg-dump.2026-09-18：切换前七个模块库快照上传 MinIO\n- runtime-up.2026-09-18：22 条读面探针 + 4 条受控执行探针 + 3 条非 canonical 对照，\n 8 条 findings（4 修 4 留裁决），可观测三后端切换后仍有信号\n- deployed-runtime：passed / IMAGE_SOURCE_EQUIVALENT\n\nprovenance.worktreeDirty=true：本工作区有并行会话 WIP，运行面记录只绑定本地；\n镜像证据独立绑定干净检出（image.worktreeDirty=false）。\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-18T01:18:59-07:00"},{"Sha1":"709cd94cfc5cd138b5539053554ef1b4d4dcd4ff","Message":"docs(部署): dev 常驻运行时重新部署与三个运行面取证记录（2026-09-18）\n\ncheck:deployed 从 BUILT_IMAGE_SOURCE_BEHIND 转 passed 的完整过程：四个部署缺口、\n一个被吞掉的真实缺陷、受控执行面的 dev 验收，以及六条仍未闭环的事实。\n作用域只到本机 dev，不外推目标环境签收。\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-18T01:18:52-07:00"}],"HeadCommit":{"Sha1":"1e6f71d846a9ad3bcbd04a3f2b5fdb3f69ca1884","Message":"chore(reports): check:gate-flow 回绑 @ 5003319\n\n剥注释后判定结果不变：45 个脚本、33 个有消费入口、12 个流外且全部具名、0 违规。\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-18T01:20:03-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/2d4b55254cd0b38f4ae1750038d4a6d9e2ebb30a...1e6f71d846a9ad3bcbd04a3f2b5fdb3f69ca1884","Len":7}...
|
1789719607
|
Edit
Delete
|
|
31068
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"dcd1c1486 {"Commits":[{"Sha1":"dcd1c1486e63a7f67a0c548158823764a0b58b21","Message":"chore(reports): 整轮 pnpm check 二十八份证据 回绑 @ 1994f3c，刷新快照锚点\n\n本批次最后一个提交，按 C241 纪律同时刷新 CLAUDE.md 的快照基准提交锚点到 1994f3c\n（声明落后 0，本提交自身使实测落后 1，落在 C19 式 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=1994f3c、worktreeDirty:false）。\n整轮 28 步全部执行，前 27 步全绿，末步 check:kernel-admission 红 8 处——该门禁引入时即\n登记的已知诚实红（K3 一处：crossProductRequired 的证据源是命名空间冒烟测试；\nK4 七处：三个组件的 admissionEvidence 声明为 true 却无机器回执），链尾位置正是为了不连带\n抹掉前 27 步的证据。\n\n与上一次整轮绿盘（23d1b7a @ 6396f7f，27/27）相比，本轮是 28 步：新增的第 28 步\ncheck:kernel-admission 自身就是本批次引入的。因此「27/27 全绿」与「28 步 27 绿」不是退步，\n是多了一条此前不存在的判据，并且它一上来就报出了真实缺口。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次（check:ui 不在静态链内，本轮未跑），\n未提交也未还原。\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-18T01:21:28-07:00"},{"Sha1":"1994f3c74ee90e08df7f1b03afff9dd570fee87d","Message":"docs(治理): 整轮 pnpm check 暴露的三处文档漂移——下游锁、边界数字、快照锚点\n\n本批次六个提交推送时没有刷新文档真相，整轮 pnpm check 的 check:docs-truth 如实报红 4 条\n（第 2 条是第 1 条的负向探针连带）。逐条修：\n\n- docs/product-extension-guide.md 的「当前下游兼容锁」行仍写 @repo/contracts@1.16.0，\n 实际已随两次公开面变更升到 1.18.0。该行要求与 kernel.downstream.lock.json **逐字**匹配。\n- CLAUDE.md 内核边界数字 142/142 → 143/143 受管面：identity.ts 迁入 CORE 的 contractModules\n 多了一个受管面。242/242 源码文件与 7/7 负向探针未变。\n （C152 那条历史教训行里的 136/136 是当时的实测记录，属历史事实，不改。）\n- 快照基准提交锚点 070b944 落后 HEAD 10 提交——其中 8 个是本批次的，另 2 个\n （23d1b7a / c433d57）在本批次之前就已漏刷。锚点随批次最后一个提交刷新，故不在本提交里改。\n\n整轮实测（28 步全部执行）：前 27 步全绿——check:platform / naming / schema / validation /\ncontract-consumers / dual-backend / write-guard / list-bounds / fork-readiness /\nkernel-boundaries / kernel-packages / kernel-downstream / kernel-extensions /\nproduct-migrations / product-acceptance / agent-adapters / report-lock / operations /\nllm-eval / rls / migrations / governance-docs / docs-truth / governance / lint（5/5）/\ntypecheck（13/13）/ platform-provenance；末步 check:kernel-admission 红 8 处，\n是该门禁引入时即登记的已知诚实红（K3 一处 + K4 七处），位置在链尾正是为了不连带抹掉\n前 27 步的证据。\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-18T01:19:40-07:00"}],"HeadCommit":{"Sha1":"dcd1c1486e63a7f67a0c548158823764a0b58b21","Message":"chore(reports): 整轮 pnpm check 二十八份证据 回绑 @ 1994f3c，刷新快照锚点\n\n本批次最后一个提交，按 C241 纪律同时刷新 CLAUDE.md 的快照基准提交锚点到 1994f3c\n（声明落后 0，本提交自身使实测落后 1，落在 C19 式 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=1994f3c、worktreeDirty:false）。\n整轮 28 步全部执行，前 27 步全绿，末步 check:kernel-admission 红 8 处——该门禁引入时即\n登记的已知诚实红（K3 一处：crossProductRequired 的证据源是命名空间冒烟测试；\nK4 七处：三个组件的 admissionEvidence 声明为 true 却无机器回执），链尾位置正是为了不连带\n抹掉前 27 步的证据。\n\n与上一次整轮绿盘（23d1b7a @ 6396f7f，27/27）相比，本轮是 28 步：新增的第 28 步\ncheck:kernel-admission 自身就是本批次引入的。因此「27/27 全绿」与「28 步 27 绿」不是退步，\n是多了一条此前不存在的判据，并且它一上来就报出了真实缺口。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次（check:ui 不在静态链内，本轮未跑），\n未提交也未还原。\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-18T01:21:28-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/832f9b2e5ab646a48adbf37b80db1d41092f2f7e...dcd1c1486e63a7f67a0c548158823764a0b58b21","Len":2}...
|
1789719706
|
Edit
Delete
|
|
31069
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"58a896f8a {"Commits":[{"Sha1":"58a896f8a4030c0d72fa3b631d8f823f144d1650","Message":"docs(计划): 登记 FR-7 与 gate-flow 推导修正，并订正跨目录待办的 FR 清单\n\n跨目录待办原写「余 FR-6 待受理」，漏了 FR-2 / FR-3——两条 2026-09-12 提出、09-18 复核\n仍成立并补了新证据。现改为四条：FR-2 / FR-3 / FR-6 / FR-7。\n\nFR-7：governance.rules.json 的 mode 与 ADR-0010 状态的耦合没有执行者。ADR 写着「仍为\nProposed 时 mode 固定为 observe」，而 schema 只管枚举、check-governance-rules 只打印\n不判、generate-governance-status 只回显。翻成 enforced 没人拦，ADR 受理后留在 observe\n也没人报，17 条规则会永远停在诊断态。本仓未做本地修正：那四个文件与框架逐字相同。\n\n同轮修了 check:gate-flow 的一处真缺陷：推导在 CI 原文上按名匹配，而工作流里本就有\n带 `pnpm check` 的说明行，没被误判纯属侥幸。已改为先剥注释再匹配。\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-18T01:22:21-07:00"}],"HeadCommit":{"Sha1":"58a896f8a4030c0d72fa3b631d8f823f144d1650","Message":"docs(计划): 登记 FR-7 与 gate-flow 推导修正，并订正跨目录待办的 FR 清单\n\n跨目录待办原写「余 FR-6 待受理」，漏了 FR-2 / FR-3——两条 2026-09-12 提出、09-18 复核\n仍成立并补了新证据。现改为四条：FR-2 / FR-3 / FR-6 / FR-7。\n\nFR-7：governance.rules.json 的 mode 与 ADR-0010 状态的耦合没有执行者。ADR 写着「仍为\nProposed 时 mode 固定为 observe」，而 schema 只管枚举、check-governance-rules 只打印\n不判、generate-governance-status 只回显。翻成 enforced 没人拦，ADR 受理后留在 observe\n也没人报，17 条规则会永远停在诊断态。本仓未做本地修正：那四个文件与框架逐字相同。\n\n同轮修了 check:gate-flow 的一处真缺陷：推导在 CI 原文上按名匹配，而工作流里本就有\n带 `pnpm check` 的说明行，没被误判纯属侥幸。已改为先剥注释再匹配。\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-18T01:22:21-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ed4a869bde4de3243013e74e7f48454e053bd2fa...58a896f8a4030c0d72fa3b631d8f823f144d1650","Len":1}...
|
1789719743
|
Edit
Delete
|
|
31070
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1c8523a92 {"Commits":[{"Sha1":"1c8523a92bf32cb7257642251ad57e7a03ebf161","Message":"chore(reports): runtime 验收在 clean HEAD 首次绑定 回绑 @ dcd1c14，刷新证据新鲜度与快照锚点\n\ntenant.ts 三步拆分的运行态复验。结果与拆分前基线**逐项持平**，行为中性在运行态得到证实：\n\n testsPassed 733（基线 733，地板 683）\n behaviorParityCases 204（地板 204，violations 0）\n 87 项指标零违规——迁移 deploy/status、七包串行测试、双管道竞争验收、行为矩阵、\n auth-startup、db-credential-separation（8 负例 + 2 进程隔离）、tracing（4 服务）、\n dependency-resilience（14 故障 + 14 恢复 + 半开 4）、capacity（480 请求 p95 20.0ms）、\n write-capacity（40 链路终态 + 80 派发）、multi-instance（4 进程）、\n 产品扩展 / 迁移 / SQL 运行时与产品验收（258 正 + 124 负）\n\n**首次在 clean HEAD 上绑定**：13 份运行态报告的 provenance 全部 gitSha=dcd1c14、\nworktreeDirty:false。此前那份（2026-09-14）绑的是 6396f7f 且工作区 dirty，按仓规矩只能\n绑定本地、不能作阶段门证据。\n\n基座刻意隔离，不沿用上次配置：\n- 新建独立验收库 digital_employee_os_acceptance_20260918 @127.0.0.1:55470（按 Owner 决定保留，\n 与工作区 enterprise_platform_acceptance_* 的带日期惯例一致，便于回查）\n- 新起专用 Redis 容器（redis://127.0.0.1:6404/3）——上次用的 6404 实例已不存在\n- 不用 digital_employee_os_dev_nestjs：那是 dev 库，跑验收会被测试数据反复清洗\n- 理由是 G15/O1：本机 41 个容器多仓共用端口，且实测另有并行会话正在跑 enterprise-platform\n 的 api-nestjs。上次 runtime 长期假红的根因正是共用逻辑库导致三处订阅端收不到信封\n\nCLAUDE.md 证据新鲜度两行同步刷新（三级分开陈述，不互相冒充）：\n- 真实 DB：2026-09-14 🟡（dirty）→ 2026-09-18 ✅（clean dcd1c14）\n- 静态链：2026-09-14 ✅ 27/27 → 2026-09-18 🟡（clean 1994f3c 上 28 步全执行、前 27 绿，\n 末步 check:kernel-admission 诚实红 8 处）。「27/27」与「28 步 27 绿」不是退步，是多了一条\n 此前不存在的判据，且它一上来就报出真实缺口——该说明已写进文档行内，防止后来者误读为回归。\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 dcd1c14（声明落后 0，本提交自身使实测落后 1，\n落在 +1 自指窗内）。推送前已跑 check:docs-truth:assert 自检通过。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次（check:ui 不在 runtime 链内，未跑），\n未提交也未还原。\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-18T01:34:51-07:00"}],"HeadCommit":{"Sha1":"1c8523a92bf32cb7257642251ad57e7a03ebf161","Message":"chore(reports): runtime 验收在 clean HEAD 首次绑定 回绑 @ dcd1c14，刷新证据新鲜度与快照锚点\n\ntenant.ts 三步拆分的运行态复验。结果与拆分前基线**逐项持平**，行为中性在运行态得到证实：\n\n testsPassed 733（基线 733，地板 683）\n behaviorParityCases 204（地板 204，violations 0）\n 87 项指标零违规——迁移 deploy/status、七包串行测试、双管道竞争验收、行为矩阵、\n auth-startup、db-credential-separation（8 负例 + 2 进程隔离）、tracing（4 服务）、\n dependency-resilience（14 故障 + 14 恢复 + 半开 4）、capacity（480 请求 p95 20.0ms）、\n write-capacity（40 链路终态 + 80 派发）、multi-instance（4 进程）、\n 产品扩展 / 迁移 / SQL 运行时与产品验收（258 正 + 124 负）\n\n**首次在 clean HEAD 上绑定**：13 份运行态报告的 provenance 全部 gitSha=dcd1c14、\nworktreeDirty:false。此前那份（2026-09-14）绑的是 6396f7f 且工作区 dirty，按仓规矩只能\n绑定本地、不能作阶段门证据。\n\n基座刻意隔离，不沿用上次配置：\n- 新建独立验收库 digital_employee_os_acceptance_20260918 @127.0.0.1:55470（按 Owner 决定保留，\n 与工作区 enterprise_platform_acceptance_* 的带日期惯例一致，便于回查）\n- 新起专用 Redis 容器（redis://127.0.0.1:6404/3）——上次用的 6404 实例已不存在\n- 不用 digital_employee_os_dev_nestjs：那是 dev 库，跑验收会被测试数据反复清洗\n- 理由是 G15/O1：本机 41 个容器多仓共用端口，且实测另有并行会话正在跑 enterprise-platform\n 的 api-nestjs。上次 runtime 长期假红的根因正是共用逻辑库导致三处订阅端收不到信封\n\nCLAUDE.md 证据新鲜度两行同步刷新（三级分开陈述，不互相冒充）：\n- 真实 DB：2026-09-14 🟡（dirty）→ 2026-09-18 ✅（clean dcd1c14）\n- 静态链：2026-09-14 ✅ 27/27 → 2026-09-18 🟡（clean 1994f3c 上 28 步全执行、前 27 绿，\n 末步 check:kernel-admission 诚实红 8 处）。「27/27」与「28 步 27 绿」不是退步，是多了一条\n 此前不存在的判据，且它一上来就报出真实缺口——该说明已写进文档行内，防止后来者误读为回归。\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 dcd1c14（声明落后 0，本提交自身使实测落后 1，\n落在 +1 自指窗内）。推送前已跑 check:docs-truth:assert 自检通过。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次（check:ui 不在 runtime 链内，未跑），\n未提交也未还原。\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-18T01:34:51-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/dcd1c1486e63a7f67a0c548158823764a0b58b21...1c8523a92bf32cb7257642251ad57e7a03ebf161","Len":1}...
|
1789720501
|
Edit
Delete
|
|
31071
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"8f5cd7985 {"Commits":[{"Sha1":"8f5cd7985999b41d324ba9c2216daf1ad49ca002","Message":"chore(reports): G-3 二十八份静态门禁证据 回绑 @ b7585cf，刷新快照锚点\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 b7585cf（声明落后 0，本提交自身使实测\n落后 1，在 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=b7585cf、worktreeDirty:false）。\n整轮 28 步全执行，前 27 步全绿，末步 check:kernel-admission 仍是引入时那 8 处已知诚实红。\n\nfork-readiness 报告新增 frameworkCriteriaCoverage 字段：交叉核对 verified（从\n工程基础框架/base-framework 读到 14 条判据号）、declared 14、registeredMissing 3；\nmetrics 新增 frameworkCriteriaDeclared / frameworkCriteriaRegisteredMissing 两项，\n使「框架判据覆盖率」第一次成为可回归的机器数字，而不是读脚本才知道。\n\ncheck:rls 在角色名改为派生后复跑仍绿（67 张租户表 × tenant/system 双策略）。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T01:44:35-07:00"},{"Sha1":"b7585cfab7b8130271fea714f464f5117db3733f","Message":"feat(governance): fork-readiness 补齐框架判据覆盖——号段分家、F9/F12 落地、缺席不得静默\n\nG-3。本仓 check:fork-readiness 的 F1—F7 与框架逐条对应，**F8 起分叉**：本仓 F8 是自造的\n「验收 runner 自含 contracts 构建」，框架 F8 是「可执行迁移技能」——同号不同义。后果有两层：\n跨仓说「F8 红了」会指向两个判据；更要命的是同号**掩盖了框架 F8—F14 七条长期静默缺失**，\n而其中 F11 正是「内核退回 @juhai/kernel pin」的门禁前提。\n\n一、号段分家。自造判据一律 D 号段，F 号段只留给框架。原 F8 → D1。\n\n二、两条框架判据直接落地（落地优于登记）：\n\n F9 工作区包内不得存在嵌套 lockfile —— 实测仅根一份，落地即绿\n F12 租户 RLS 组角色名必须派生自 package.json name —— **实体缺陷已修**：\n scripts/check-rls.mjs 此前把 digital_employee_os_tenant / _system 写死在 5 处\n （2 处字符串 + 3 处正则模板）。值虽然是对的，但派生仓会拿**源项目**的角色名去校验\n 自己的策略，而这个断言存在的唯一目的就是证明策略绑在本仓的角色上——\n 它会在最需要生效的场景（移植后）静默失效，与 F3 同型。改为由 package.json name 派生，\n 并加 F12 断言守住不回潮。check:rls 仍绿（67 张租户表 × 双策略）。\n\n三、缺席不得静默：新增覆盖登记 framework-criteria.json + D2—D4。\n\n D2 框架 14 条判据必须逐条登记，未登记即红；status 只能是\n implemented / implemented-elsewhere / not-applicable / missing\n D3 登记为 missing 须 reason/registeredAt/expiresAt/blockedBy/replacementPlan 五字段齐全\n 且未过期（同 platform-dependency-deviations 口径：半份登记不算登记，过期不再豁免）\n D4 登记为 implemented 必须指向本脚本真实存在的判据号——防「空口宣称已实现」，\n 与 kernel.boundaries.json 的 admissionEvidence 自证同型\n\n 门禁在框架检出可达时**交叉核对判据号快照**（实测从\n 工程基础框架/base-framework 读到 14 条，与登记表逐条吻合 → verified）；不可达显式 SKIPPED\n 而非静默通过；BASE_FRAMEWORK_ROOT 显式指定却解析不到即红，不回落到工作区布局\n （首版写成了静默回落，实活探测发现后改为 fail-closed）。\n\n当前覆盖（实测）：implemented 9（F1—F7、F9、F12）· implemented-elsewhere 1（F10 由\nkernel-boundaries + kernel-admission 两把锁承接，粒度严于框架）· not-applicable 1（F13 本仓\n已剥离示例域）· **missing 3**：\n F8 无迁移技能路由、无 reports/framework-migration.latest.json，frameworkVersion 全仓零命中\n F11 契约包可依赖形态——**内核退回 pin 的门禁前提**\n F14 apps/api-nestjs/docker-compose.yml 无顶层 name，即工作区 L9「27 仓共用 project\n api-nestjs」的本仓实证；deploy/production/compose.yml 默认值 deos-production 也不等于\n 包名派生身份\n三条均登记至 2026-12-18，报为 registered 警告不阻断——但期限到即转红。\n\n自检 pnpm check:fork-readiness:self-test 11 条（含 2 条基线正例）；另做两次实活验证：\n删掉 F14 登记 → D2 红；BASE_FRAMEWORK_ROOT 指错 → D2 红。\n\nCLAUDE.md 同步：号段纪律段、判据表 +6 行、基线表行口径、C69 两处历史引用改「D1（原 F8）」。\n整轮 pnpm check 复跑：28 步全执行，仅末步 check:kernel-admission 已知 8 处红。\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-18T01:40:25-07:00"}],"HeadCommit":{"Sha1":"8f5cd7985999b41d324ba9c2216daf1ad49ca002","Message":"chore(reports): G-3 二十八份静态门禁证据 回绑 @ b7585cf，刷新快照锚点\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 b7585cf（声明落后 0，本提交自身使实测\n落后 1，在 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=b7585cf、worktreeDirty:false）。\n整轮 28 步全执行，前 27 步全绿，末步 check:kernel-admission 仍是引入时那 8 处已知诚实红。\n\nfork-readiness 报告新增 frameworkCriteriaCoverage 字段：交叉核对 verified（从\n工程基础框架/base-framework 读到 14 条判据号）、declared 14、registeredMissing 3；\nmetrics 新增 frameworkCriteriaDeclared / frameworkCriteriaRegisteredMissing 两项，\n使「框架判据覆盖率」第一次成为可回归的机器数字，而不是读脚本才知道。\n\ncheck:rls 在角色名改为派生后复跑仍绿（67 张租户表 × tenant/system 双策略）。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T01:44:35-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/1c8523a92bf32cb7257642251ad57e7a03ebf161...8f5cd7985999b41d324ba9c2216daf1ad49ca002","Len":2}...
|
1789721078
|
Edit
Delete
|
|
31074
|
1
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"04592d02c {"Commits":[{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"}],"HeadCommit":{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"},"CompareURL":"vodtest/pc/compare/1647ded9e2361ad7cb8a2e0a373639c166d5b994...04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Len":1}...
|
1789721503
|
Edit
Delete
|
|
31075
|
3
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"04592d02c {"Commits":[{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"}],"HeadCommit":{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"},"CompareURL":"vodtest/pc/compare/1647ded9e2361ad7cb8a2e0a373639c166d5b994...04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Len":1}...
|
1789721503
|
Edit
Delete
|
|
31076
|
4
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"04592d02c {"Commits":[{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"}],"HeadCommit":{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"},"CompareURL":"vodtest/pc/compare/1647ded9e2361ad7cb8a2e0a373639c166d5b994...04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Len":1}...
|
1789721503
|
Edit
Delete
|
|
31077
|
7
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"04592d02c {"Commits":[{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"}],"HeadCommit":{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"},"CompareURL":"vodtest/pc/compare/1647ded9e2361ad7cb8a2e0a373639c166d5b994...04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Len":1}...
|
1789721503
|
Edit
Delete
|
|
31078
|
8
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"04592d02c {"Commits":[{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"}],"HeadCommit":{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"},"CompareURL":"vodtest/pc/compare/1647ded9e2361ad7cb8a2e0a373639c166d5b994...04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Len":1}...
|
1789721503
|
Edit
Delete
|
|
31073
|
9
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"04592d02c {"Commits":[{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"}],"HeadCommit":{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"},"CompareURL":"vodtest/pc/compare/1647ded9e2361ad7cb8a2e0a373639c166d5b994...04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Len":1}...
|
1789721503
|
Edit
Delete
|
|
31079
|
10
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"04592d02c {"Commits":[{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"}],"HeadCommit":{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"},"CompareURL":"vodtest/pc/compare/1647ded9e2361ad7cb8a2e0a373639c166d5b994...04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Len":1}...
|
1789721503
|
Edit
Delete
|
|
31072
|
11
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"04592d02c {"Commits":[{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"}],"HeadCommit":{"Sha1":"04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:51:18+08:00"},"CompareURL":"vodtest/pc/compare/1647ded9e2361ad7cb8a2e0a373639c166d5b994...04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd","Len":1}...
|
1789721503
|
Edit
Delete
|
|
31080
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d5323e2b1 {"Commits":[{"Sha1":"d5323e2b149e012cd3340f330a860c232d285738","Message":"docs(计划): 登记 check:ci-mirror——两条 CI 通道「只差四处必须同步改」此前没有执行者\n\nCLAUDE.md 与镜像文件自己的头注释都写着这条规则，而实测没有任何东西在比对它们。\n规范化后两份 461 行逐行相同，文件层面的差异恰好三类，据此立了 M1—M3 三条判据。\n\n值得有执行者的理由：镜像里那行 GOV_REPORT_RUNNER 是证据来源标注的唯一保证，\n不显式覆盖，这条通道产出的报告会冒充 github-actions 并被 verify-candidate 接受。\n\n顺带查出一处真实漂移但不替人裁决：头注释宣称的差异③「fork 判定改用 gitea.* 上下文」\n在文件里根本不存在。若 act_runner 不如实填充 pull_request.head.repo.full_name，\nQ12-A 的 fork 守卫在这条通道上就是失效的。归 SRE / 框架 Owner，该通道从未启用。\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-18T01:52:23-07:00"}],"HeadCommit":{"Sha1":"d5323e2b149e012cd3340f330a860c232d285738","Message":"docs(计划): 登记 check:ci-mirror——两条 CI 通道「只差四处必须同步改」此前没有执行者\n\nCLAUDE.md 与镜像文件自己的头注释都写着这条规则，而实测没有任何东西在比对它们。\n规范化后两份 461 行逐行相同，文件层面的差异恰好三类，据此立了 M1—M3 三条判据。\n\n值得有执行者的理由：镜像里那行 GOV_REPORT_RUNNER 是证据来源标注的唯一保证，\n不显式覆盖，这条通道产出的报告会冒充 github-actions 并被 verify-candidate 接受。\n\n顺带查出一处真实漂移但不替人裁决：头注释宣称的差异③「fork 判定改用 gitea.* 上下文」\n在文件里根本不存在。若 act_runner 不如实填充 pull_request.head.repo.full_name，\nQ12-A 的 fork 守卫在这条通道上就是失效的。归 SRE / 框架 Owner，该通道从未启用。\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-18T01:52:23-07:00"},"CompareURL":"luoanwu/platform-governance/compare/58a896f8a4030c0d72fa3b631d8f823f144d1650...d5323e2b149e012cd3340f330a860c232d285738","Len":1}...
|
1789721547
|
Edit
Delete
|
|
31083
|
1
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f0a3ea0e3 {"Commits":[{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"}],"HeadCommit":{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"},"CompareURL":"vodtest/pc/compare/04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd...f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Len":1}...
|
1789721572
|
Edit
Delete
|
|
31084
|
3
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f0a3ea0e3 {"Commits":[{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"}],"HeadCommit":{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"},"CompareURL":"vodtest/pc/compare/04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd...f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Len":1}...
|
1789721572
|
Edit
Delete
|
|
31085
|
4
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f0a3ea0e3 {"Commits":[{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"}],"HeadCommit":{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"},"CompareURL":"vodtest/pc/compare/04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd...f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Len":1}...
|
1789721572
|
Edit
Delete
|
|
31086
|
7
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f0a3ea0e3 {"Commits":[{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"}],"HeadCommit":{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"},"CompareURL":"vodtest/pc/compare/04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd...f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Len":1}...
|
1789721572
|
Edit
Delete
|
|
31087
|
8
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f0a3ea0e3 {"Commits":[{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"}],"HeadCommit":{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"},"CompareURL":"vodtest/pc/compare/04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd...f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Len":1}...
|
1789721572
|
Edit
Delete
|
|
31082
|
9
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f0a3ea0e3 {"Commits":[{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"}],"HeadCommit":{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"},"CompareURL":"vodtest/pc/compare/04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd...f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Len":1}...
|
1789721572
|
Edit
Delete
|
|
31088
|
10
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f0a3ea0e3 {"Commits":[{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"}],"HeadCommit":{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"},"CompareURL":"vodtest/pc/compare/04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd...f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Len":1}...
|
1789721572
|
Edit
Delete
|
|
31081
|
11
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f0a3ea0e3 {"Commits":[{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"}],"HeadCommit":{"Sha1":"f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Message":"设置小程序内容修改\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:52:44+08:00"},"CompareURL":"vodtest/pc/compare/04592d02cb8607dbc3f8c8a3b7aeb9441034c4dd...f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5","Len":1}...
|
1789721572
|
Edit
Delete
|
|
31089
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"117a379da {"Commits":[{"Sha1":"117a379da5e5d31ea07d5b61eb2dcdfce479d5db","Message":"chore(reports): 内核退回 pin 立项的二十八份静态证据 回绑 @ 65b0b33，刷新快照锚点\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 65b0b33（声明落后 0，本提交自身使实测\n落后 1，在 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=65b0b33、worktreeDirty:false）。\n整轮 28 步全执行，前 27 步全绿，末步 check:kernel-admission 仍是那 8 处已知诚实红。\n\n本批次只立项、不动代码：内核仍是仓内 0.1.0 拷贝，F8 / F11 仍登记为 missing（期限\n2026-12-18 未变），replacementPlan 改为指向立项书。fork-readiness 的\nframeworkCriteriaCoverage 保持 declared 14 / registeredMissing 3 / 交叉核对 verified。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T01:52:57-07:00"},{"Sha1":"65b0b33923bcebdf42aed903963afe2ce4c0a2e1","Message":"docs(planning): 内核退回 pin 立项——硬前提已验证，真正要判断的只有四个模块\n\nframework-criteria.json 里 F8 / F11 两条 missing 都指向同一件事：本仓持有一份框架 0.1.0 的\n内核拷贝，既不受任何来源门禁约束，也无法表达「落后几代」。本立项把它改为 exact pin\n@juhai/kernel。\n\n硬前提今天全部满足（实测）：\n- @juhai/kernel 在 registry 上有 0.16.0 / 0.16.1 / 0.22.0；本仓 .npmrc 已声明 @juhai:registry\n- migration:plan --mode sync 实测 0.1.0 → 0.22.0 共 139 冲突，落在 packages/contracts 的只有 5 处\n- tenant.ts 三步拆分后 tenant 之名已腾空，同名不同义只剩 rls.ts 一处\n\n十五个内核模块四分类（按导出名集合求交）：\n 直接 pin 5 statemachine 100% · replay 100% · realtime-stats 100% · realtime-command 90% · subscription 81%\n 需合并 3 realtime 57% · job 28% · health 25%\n 同名不相干 1 rls.ts ↔ 框架 tenant-rls.ts，重合 0%\n 净迁入 6 replay-buffer · tenant · api-error · request-context · platform-ports · alert\n\n**真正要做判断的只有 4 个模块**，其余是白拿或补齐。净迁入里 platform-ports（31 导出）\n是关键：写链前经权限端口决策 + 成功写入同事务 audit.append、生产未设 PLATFORM_PORTS_MODE\n即 fail-closed——本仓分叉于框架 0.1.0、从未见过这组端口，才各自造了一套 permission/audit。\n迁入后自建实现塞进本地实现位，将来换控制面 client 时接口不变：错层资产的迁移从「大手术」\n降为「接插座」。\n\n路径选 ②（pin）不选 ①（继续 sync）：① 每次框架发版都要三方合并内核，而本仓已积压 22 个\n版本 / 139 冲突——那正是脱轨的形成机制；② 之后只需 bump 版本，且让内核来源进入\ncheck:platform-provenance 的判据面（今天内核是仓内源码，没有任何门禁能判定它是什么版本）。\n\n立项先挂一条待裁决：框架 F11 要求 pin 等于本仓 package.json.version（框架版本轴 = 内核\n版本轴），这对派生仓不成立——本仓 version 停在 0.1.0、0 个 tag。建议 A 案（本仓建版本轴，\nF11 改判「pin 等于迁移凭证里的 frameworkVersion」），顺带解掉缺失梳理 §4.4「产品仓只能按\ngitSha 钉 OS」；B 案（向框架提 FR 区分两种形态）可作回灌。\n\n分六批 B0—B5，逐批退出门写在 §5；风险五条写在 §6，其中 0.15.0 的作业 API 破坏性变更\n（job 重合仅 28%）与两套 RLS 二选一是最硬的两处。§7 显式登记本立项不做的事：不改自建\npermission/audit 的实现，替换另起一线且前置是控制面客户端发布**并有 CI 阶段门证据**。\n\n同步：framework-criteria.json 的 F8 / F11 replacementPlan 指向本立项；CLAUDE.md 可迁移性节\n加立项指针与要点。立项书内不做跨仓链接（c433d57 已清理过一轮仓外链接）。\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-18T01:51:25-07:00"}],"HeadCommit":{"Sha1":"117a379da5e5d31ea07d5b61eb2dcdfce479d5db","Message":"chore(reports): 内核退回 pin 立项的二十八份静态证据 回绑 @ 65b0b33，刷新快照锚点\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 65b0b33（声明落后 0，本提交自身使实测\n落后 1，在 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=65b0b33、worktreeDirty:false）。\n整轮 28 步全执行，前 27 步全绿，末步 check:kernel-admission 仍是那 8 处已知诚实红。\n\n本批次只立项、不动代码：内核仍是仓内 0.1.0 拷贝，F8 / F11 仍登记为 missing（期限\n2026-12-18 未变），replacementPlan 改为指向立项书。fork-readiness 的\nframeworkCriteriaCoverage 保持 declared 14 / registeredMissing 3 / 交叉核对 verified。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T01:52:57-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/8f5cd7985999b41d324ba9c2216daf1ad49ca002...117a379da5e5d31ea07d5b61eb2dcdfce479d5db","Len":2}...
|
1789721581
|
Edit
Delete
|
|
31092
|
1
|
5
|
11
|
23
|
0
|
0
|
refs/heads/admin-260915
|
0
|
{"Commits":[{"Sha1":"e38218cd2 {"Commits":[{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"}],"HeadCommit":{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"},"CompareURL":"vodtest/admin/compare/6ae1c8f25aeeb4516dfae1a019dc8dddb492ebf8...e38218cd25e98e7e652892a07e700718e8a508a4","Len":1}...
|
1789721872
|
Edit
Delete
|
|
31093
|
3
|
5
|
11
|
23
|
0
|
0
|
refs/heads/admin-260915
|
0
|
{"Commits":[{"Sha1":"e38218cd2 {"Commits":[{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"}],"HeadCommit":{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"},"CompareURL":"vodtest/admin/compare/6ae1c8f25aeeb4516dfae1a019dc8dddb492ebf8...e38218cd25e98e7e652892a07e700718e8a508a4","Len":1}...
|
1789721872
|
Edit
Delete
|
|
31094
|
4
|
5
|
11
|
23
|
0
|
0
|
refs/heads/admin-260915
|
0
|
{"Commits":[{"Sha1":"e38218cd2 {"Commits":[{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"}],"HeadCommit":{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"},"CompareURL":"vodtest/admin/compare/6ae1c8f25aeeb4516dfae1a019dc8dddb492ebf8...e38218cd25e98e7e652892a07e700718e8a508a4","Len":1}...
|
1789721872
|
Edit
Delete
|
|
31095
|
7
|
5
|
11
|
23
|
0
|
0
|
refs/heads/admin-260915
|
0
|
{"Commits":[{"Sha1":"e38218cd2 {"Commits":[{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"}],"HeadCommit":{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"},"CompareURL":"vodtest/admin/compare/6ae1c8f25aeeb4516dfae1a019dc8dddb492ebf8...e38218cd25e98e7e652892a07e700718e8a508a4","Len":1}...
|
1789721872
|
Edit
Delete
|
|
31096
|
8
|
5
|
11
|
23
|
0
|
0
|
refs/heads/admin-260915
|
0
|
{"Commits":[{"Sha1":"e38218cd2 {"Commits":[{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"}],"HeadCommit":{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"},"CompareURL":"vodtest/admin/compare/6ae1c8f25aeeb4516dfae1a019dc8dddb492ebf8...e38218cd25e98e7e652892a07e700718e8a508a4","Len":1}...
|
1789721872
|
Edit
Delete
|
|
31091
|
9
|
5
|
11
|
23
|
0
|
0
|
refs/heads/admin-260915
|
0
|
{"Commits":[{"Sha1":"e38218cd2 {"Commits":[{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"}],"HeadCommit":{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"},"CompareURL":"vodtest/admin/compare/6ae1c8f25aeeb4516dfae1a019dc8dddb492ebf8...e38218cd25e98e7e652892a07e700718e8a508a4","Len":1}...
|
1789721872
|
Edit
Delete
|
|
31097
|
10
|
5
|
11
|
23
|
0
|
0
|
refs/heads/admin-260915
|
0
|
{"Commits":[{"Sha1":"e38218cd2 {"Commits":[{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"}],"HeadCommit":{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"},"CompareURL":"vodtest/admin/compare/6ae1c8f25aeeb4516dfae1a019dc8dddb492ebf8...e38218cd25e98e7e652892a07e700718e8a508a4","Len":1}...
|
1789721872
|
Edit
Delete
|
|
31090
|
11
|
5
|
11
|
23
|
0
|
0
|
refs/heads/admin-260915
|
0
|
{"Commits":[{"Sha1":"e38218cd2 {"Commits":[{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"}],"HeadCommit":{"Sha1":"e38218cd25e98e7e652892a07e700718e8a508a4","Message":"客户满意度批量作废确定弹窗\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T16:57:43+08:00"},"CompareURL":"vodtest/admin/compare/6ae1c8f25aeeb4516dfae1a019dc8dddb492ebf8...e38218cd25e98e7e652892a07e700718e8a508a4","Len":1}...
|
1789721872
|
Edit
Delete
|
|
31098
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ee4bc0660 {"Commits":[{"Sha1":"ee4bc06608d88515f025c3a2dcffacb9f47c5417","Message":"chore(reports): B0 裁决的二十八份静态证据 回绑 @ 1f74faa，刷新快照锚点\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 1f74faa（声明落后 0，本提交自身使实测\n落后 1，在 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=1f74faa、worktreeDirty:false）。\n整轮 28 步全执行，前 27 步全绿，末步 check:kernel-admission 仍是那 8 处已知诚实红。\n\nB0 只落裁决未改代码，故 fork-readiness 的 frameworkCriteriaCoverage 不变：declared 14 /\nregisteredMissing 3（F8 / F11 / F14）/ 交叉核对 verified。F11 现挂 adjudication:\"B0\"，\n但按 B0 口径实现的 F11 断言要到 B5 才落——在那之前 F11 仍是诚实的 missing。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T01:58:16-07:00"},{"Sha1":"1f74faae838116a4d546b0edaf75f4fcba026cfc","Message":"docs(决策): B0 裁决 A2——F11 对派生仓改判为「pin == 凭证 source.frameworkVersion」\n\n内核退回 pin 立项 §4 挂的那条口径已裁。框架 F11 断言「@juhai/kernel 的 pin 必须等于本仓\npackage.json.version」（框架版本轴 = 内核版本轴），这条对框架自身成立，对本仓不成立：\n本仓 version 停在 0.1.0、0 个 tag，而根版本同时要服务「产品仓钉 OS」。\n\n**裁为 A2：本仓建立自己的版本轴；F11 迁入时改判为**\n\n contracts 对 @juhai/kernel 的 exact pin 必须等于\n reports/framework-migration.latest.json 的 source.frameworkVersion\n\n三条理由：\n- F11 的意图是「pin 与所同步的框架版本一致、落后几代可判定」，用凭证里的\n source.frameworkVersion 表达同样成立，且不强求派生仓与框架共用版本号\n- 若照框架原文把根版本设成 0.22.0，产品仓钉的「OS 版本」其实是框架版本，\n 缺失梳理 §4.4 不但没解决，还被永久占用\n- **该字段凭证里已经有**（record-migration.mjs 从源仓 package.json 读取），本口径\n 不需要新增任何东西——这是选 A2 而非提 FR 阻塞的关键\n\n**不照控制面先例的原因是形态不同。** 企业控制面走的是拆根：runtime/package.json 版本\n直接设为框架版本 0.22.0，故 F11 原文成立；仓根 0.1.0 与 contracts/ 1.0.0-rc.3 各留自己的\n版本。本仓是单 pnpm 根，用不了这个办法；改多根（立项 §4 的 A3）会牵动 turbo 布局、\n13 个 typecheck 任务与所有门禁的路径假设，不在这条线上做。\n\n**版本轴起点同批裁为「留到 B5 定」**：版本号要到 B5 签凭证、真正对外表达兼容范围时才\n用得上，那时内核换源的实际破坏面已清楚，定起点更有依据；现在定等于凭空拍。\n\n落点：framework-criteria.json 新增 adjudications.B0（含 assertion / rationale / precedent /\ndeferred / upstreamFeedback 五段），F11 挂 adjudication:\"B0\" 引用；立项书 §4 标已裁决、\n§5 的 B0 行标完成。CLAUDE.md 可迁移性节同步。\n\nB5 退出门顺带补两项：① 定版本轴起点（B0 顺延项）；② check:fork-readiness 按本裁决实现\nF11 断言时，同时加一条 adjudication 引用完整性判据——criteria.\u003cid\u003e.adjudication 指向的 key\n必须存在于 adjudications，防悬空引用，与 D4 防「空口宣称」同型。本批按立项 §5 不改代码，\n故该判据留到 B5 一并落。\n\n上游回灌（不阻塞）：可向框架提 FR，让 F11 区分「框架仓」与「派生仓」两种形态。\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-18T01:56:44-07:00"}],"HeadCommit":{"Sha1":"ee4bc06608d88515f025c3a2dcffacb9f47c5417","Message":"chore(reports): B0 裁决的二十八份静态证据 回绑 @ 1f74faa，刷新快照锚点\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 1f74faa（声明落后 0，本提交自身使实测\n落后 1，在 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=1f74faa、worktreeDirty:false）。\n整轮 28 步全执行，前 27 步全绿，末步 check:kernel-admission 仍是那 8 处已知诚实红。\n\nB0 只落裁决未改代码，故 fork-readiness 的 frameworkCriteriaCoverage 不变：declared 14 /\nregisteredMissing 3（F8 / F11 / F14）/ 交叉核对 verified。F11 现挂 adjudication:\"B0\"，\n但按 B0 口径实现的 F11 断言要到 B5 才落——在那之前 F11 仍是诚实的 missing。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T01:58:16-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/117a379da5e5d31ea07d5b61eb2dcdfce479d5db...ee4bc06608d88515f025c3a2dcffacb9f47c5417","Len":2}...
|
1789721899
|
Edit
Delete
|
|
31099
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6b045590e {"Commits":[{"Sha1":"6b045590e6ba93dd703453bc478b3b6c879491f3","Message":"docs(计划): 订正 contracts:check 的登记，并登记偏差 #37 / #38\n\n#38：真实 Catalog 的治理判定不在任何自动流里。contracts/scripts/check.mjs 只在\ncontracts check 里，链与 CI 用的都是 check:local。挡它在链外的历史理由（余 6 项待\nCHG-001）经实测已全部通过——又一次「条件早已满足而无人察觉」。\n\n#37：CHG-007 立的「闸门 blocked_by vs 溯源 decided_by」只应用在 facts 的一条事实上，\nrelationships 与 scopes 仍有 4 条阻断声明指向已批准的 DEC-002 / DEC-004，且当时没留\n探测器。改 Catalog 归 Catalog Owner，本轮只登记不改数据；也没给 linter 加探测器，\n因为给一道没人跑的门禁加规则是无用功，次序上要先解决 #38。\n\n同时订正前一轮把 contracts:check 登记成 tool 的错误，并记下本轮一次把并行会话文件\n卷进自己提交的操作事故与修正过程。\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-18T02:05:35-07:00"}],"HeadCommit":{"Sha1":"6b045590e6ba93dd703453bc478b3b6c879491f3","Message":"docs(计划): 订正 contracts:check 的登记，并登记偏差 #37 / #38\n\n#38：真实 Catalog 的治理判定不在任何自动流里。contracts/scripts/check.mjs 只在\ncontracts check 里，链与 CI 用的都是 check:local。挡它在链外的历史理由（余 6 项待\nCHG-001）经实测已全部通过——又一次「条件早已满足而无人察觉」。\n\n#37：CHG-007 立的「闸门 blocked_by vs 溯源 decided_by」只应用在 facts 的一条事实上，\nrelationships 与 scopes 仍有 4 条阻断声明指向已批准的 DEC-002 / DEC-004，且当时没留\n探测器。改 Catalog 归 Catalog Owner，本轮只登记不改数据；也没给 linter 加探测器，\n因为给一道没人跑的门禁加规则是无用功，次序上要先解决 #38。\n\n同时订正前一轮把 contracts:check 登记成 tool 的错误，并记下本轮一次把并行会话文件\n卷进自己提交的操作事故与修正过程。\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-18T02:05:35-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d5323e2b149e012cd3340f330a860c232d285738...6b045590e6ba93dd703453bc478b3b6c879491f3","Len":1}...
|
1789722339
|
Edit
Delete
|
|
31100
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"32ad69a15 {"Commits":[{"Sha1":"32ad69a15ceb55e1cbcb170d7fdd47897e50c01b","Message":"chore(reports): check:caddy 回绑 @ 426a7df\n\n干净检出（.worktrees/rebind-426a7df）重跑，worktreeDirty=false；\n两个 profile 各 0 违规，caddy validate 经 docker 两份都 passed（不是 skipped）。\n报告新增 workbench 段，其中 guardsDocumentNavigation=false 是登记事实：\n入口鉴权只挡带 Authorization 头的数据面，纯静态 SPA 的文档导航挡不住。\n\n主工作区有并行会话 WIP，本次只还原本任务改动的这一份报告。\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-18T02:05:49-07:00"},{"Sha1":"588e5ab9459d1df433f3a32b44a4afe589b6a9b7","Message":"chore(reports): check:gate-flow 回绑 @ aaf43ee\n\ncontracts:check 由 tool 订正为 gate 后重跑：46 个脚本、34 个有消费入口、\n12 个流外（门禁 5 / 工具 7）、0 违规。\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-18T02:04:43-07:00"},{"Sha1":"426a7df100b7b8c2c82179f2b184ed066f6ceba6","Message":"feat(stack,governance,workbench): 工作台同源托管与 /api/platform/* 入口鉴权（CHG-018 阶段 ②）\n\nCaddy 两个 profile 同步改：根路径托管工作台静态产物（产物未挂载时回原占位响应），\n/_next/* 先在产物里找文件、找不到才回身份 Web，@platform 块内对 /api/platform/*\n做 forward_auth → /t/{$PLATFORM_WORKBENCH_TENANT}/oidc/userinfo。租户空值即\n/t//oidc/userinfo → 上游 404 → 整段拒绝，不配置 = 不放行，与 PLATFORM_OPS_* 同纪律。\n\n入口只挡带 Authorization 头的数据面，挡不住文档导航：工作台是纯静态 SPA，令牌进\nsessionStorage 不进 cookie，浏览器发文档请求时网关手上没有可校验的凭据。要挡住静态壳\n就得有个发 cookie 的边缘会话组件，与 CHG-018 §5.1 已裁的形态相抵，须另起 CHG。这条\n边界写进 caddy-routes.json 的登记与报告的 guardsDocumentNavigation，不靠读代码猜。\n\n连带修好取数链路：三个读面的 accessToken 此前从没有调用方传过值（读面本来公开），\n入口挡上后工作台登录了也会永远 401。现改为必填形参；hooks 从 session store 取令牌，\n身份（不是令牌）进 queryKey，补水前不发请求，退出时清缓存。\n\ncheck:caddy 增 workbench 段与四条规则，两 profile 各 0 违规、caddy validate 经 docker\n两份都 passed；六条负向用例逐条先红后绿。另修一条已失效的旧夹具：UPSTREAM_MISSING 那条\n用 String.replace 只换第一处，forward_auth 引入同名变量后它再也换不到 reverse_proxy，\n改 replaceAll 并补一条「确实解绑了上游」的断言。\n\ndev 运行态取证与未闭环项（D-8 判责码语义、D-9 门禁守不住的绕过、D-10 issuer 不一致、\n带有效令牌的 200 分支未实测）见 docs/工作台同源托管与入口鉴权实现记录-2026-09-18.md。\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-18T02:04:42-07:00"},{"Sha1":"aaf43ee0442d5b4a5d36325a92c1ae5bbff3c76b","Message":"chore(reports): 工作台目录与运维快照回绑 @ 8a53c39\n\n在 8a53c39 的临时干净检出里重跑 `node governance/build-workbench-snapshots.mjs`\n（主工作树有并行会话的在途改动，就地跑只能产出 worktreeDirty=true 的绑定）。\n\n目录快照：schemaVersion 2，21 条 → stale 7 / not-in-manifest 14，conflicts 0。\n运维快照：schemaVersion 仍为 1，内容未变，只因生成脚本进了它的作用域而一并回绑。\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-18T02:04:29-07:00"},{"Sha1":"90f3b99b5976b58431097147662a1253b096840c","Message":"fix(governance): 订正 gate-flow 把 contracts:check 登记成 tool——它是一道有人写、没人跑的门禁\n\n昨天登记它时我写的是「role: tool，组成部分已被消费：check:local 在根 check 链与 CI\nstatic job 里」。**那是错的。** `contracts check` 比 `check:local` 多跑一个\n`scripts/check.mjs`，而那正是**对真实 Catalog 跑治理 linter** 的那一道：checkRegistry\n校验 8 份 Catalog、决议状态、应用清单、Fact 与权限命名、scopes 的阻断引用。\n`check:local` 只跑 schema-compatibility / impact-graph / check:generated / build / test。\n根链与 CI 用的都是 check:local，所以真实 Catalog 的治理判定**不在任何自动流里**，\n只有人手动敲 `pnpm contracts:check` 才会发生。\n\n技术原因不是疏忽：linter 需要工作区根（Catalog 的 directory / code_truth / evidence 与\n决议 source 都是相对工作区的路径），CI 只 checkout 本仓，接进根链会以\nWORKSPACE_ROOT_UNRESOLVED 退出 2——check:local 正是为此存在。\n\n**但挡它在链外的历史理由已经不成立。** CLAUDE.md 当前状态节写着「`check` 余 6 项\nPLATFORM_PROJECT_UNREGISTERED 待 CHG-001」，2026-09-18 实测**已全部通过**：\n17 draft apps / 168 governed entity / 11 draft fact / 9 permission resource /\n39 decisions（32 approved / 3 pending）/ 21 platform projects（19 in goal scope），\nschema 兼容 11/11 immutable，影响图 258 节点 297 边。又一次「条件早已满足而无人察觉」。\n\n已改为 role: gate，带 reason / wireInWhen / conditionReviewBy（2026-10-31）：剩下的\n只是工作区可达性，两条路二选一需裁决——给 CI 一条能取到工作区的 job（或把 linter 需要\n的工作区事实快照进本仓），或在工作区侧另起 workspace-only 链由治理层消费。\nCLAUDE.md 那句已划掉并补上实测与原因，免得下一个会话照着旧结论重走一遍。\n\n流外分布随之 4 门禁 / 8 工具 → 5 门禁 / 7 工具。\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-18T02:04:23-07:00"}],"HeadCommit":{"Sha1":"32ad69a15ceb55e1cbcb170d7fdd47897e50c01b","Message":"chore(reports): check:caddy 回绑 @ 426a7df\n\n干净检出（.worktrees/rebind-426a7df）重跑，worktreeDirty=false；\n两个 profile 各 0 违规，caddy validate 经 docker 两份都 passed（不是 skipped）。\n报告新增 workbench 段，其中 guardsDocumentNavigation=false 是登记事实：\n入口鉴权只挡带 Authorization 头的数据面，纯静态 SPA 的文档导航挡不住。\n\n主工作区有并行会话 WIP，本次只还原本任务改动的这一份报告。\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-18T02:05:49-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/1e6f71d846a9ad3bcbd04a3f2b5fdb3f69ca1884...32ad69a15ceb55e1cbcb170d7fdd47897e50c01b","Len":11}...
|
1789722432
|
Edit
Delete
|
|
31101
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"fd3ba87ed {"Commits":[{"Sha1":"fd3ba87ed111d9245012f0578178cccb4743ab20","Message":"chore(reports): B1 的二十八份静态证据 回绑 @ fb2fb1a，刷新快照锚点\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 fb2fb1a（声明落后 0，本提交自身使实测\n落后 1，在 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=fb2fb1a、worktreeDirty:false）。\n整轮 28 步全执行，前 27 步全绿，末步 check:kernel-admission 仍是那 8 处已知诚实红。\n\n本批次内两把锁各重签一次，都是「变更即复核」而非绕过：\n- kernel.exports.lock.json 763 → 755（statemachine 的 8 个导出归属转移给 @juhai/kernel）\n- check:kernel-downstream 的仓外夹具改为携带 scoped registry 后转绿；缺声明即 fail-closed\n 的分支已实活验证\n\n运行态未跑：B1 只动契约包的一个转发文件，contracts 312/312 与 typecheck 13/13 已覆盖；\n按仓规矩三级证据分开陈述，不用静态绿冒充运行态绿。runtime 报告仍绑在 dcd1c14，\n下次动到两后端（B3′ 采纳上游加固）时必须重跑。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T02:08:00-07:00"},{"Sha1":"fb2fb1a730a522c6210afc0223c84aaa6946194d","Message":"feat(contracts): B1 内核首次 exact pin @juhai/kernel@0.22.0，statemachine 改为转发\n\nB1 的目的是**验证机制**，不是搬最多的代码：装包、转发、门禁、锁四条链路全走一遍，\n用唯一可证明零行为变化的模块做载体。\n\n- packages/contracts exact pin @juhai/kernel@0.22.0（registry 上有 0.16.0/0.16.1/0.22.0）\n- statemachine.ts 改为**具名**转发 8 个符号。不用 `export * from \"@juhai/kernel\"`：\n 收口前本仓还留着 10 个未迁内核模块，整体 re-export 会与它们的同名导出冲突\n- 机制验证结果：typecheck 13/13 · contracts 312/312（statemachine.test.ts 打的就是转发后的\n 实现）· 整轮 28 步前 27 绿 · **check:platform-provenance 接受新 pin**（lock 解析到 Gitea\n registry tarball）· 所有权锁 763 → 755，8 个导出的归属转移给内核包\n\n**开工即修正一处自己的判断。** 上一轮我把五个模块叫「白拿」，依据只到导出名重合率。\n逐文件 diff 后：**只有 statemachine 逐字一致**（104 行 diff 0），其余四个实现都不同，\n且方向一致——框架领先、本仓落后，落后的正好是加固：\n\n replay 框架有 maxSeq + 「游标超前于现存最大 seq ⇒ 报缺口（cursor-unknown）」，\n 本仓没有 ⇒ 伪造/串号游标被静默判成「已追平」，客户端永远收不到补发；\n 框架同时修了契约文件内部自相矛盾的 dispatchedAt 注释\n realtime-command 框架有 REALTIME_WS_MAX_PAYLOAD_BYTES，本仓 WS 载荷无上限\n subscription 框架有 REALTIME_MAX_SUBSCRIPTION_IDS/_TYPES，本仓订阅列表无上限\n realtime-stats 本仓是严格超集（多 10 个死信域导出），采纳时要保留\n\n前两类偏 DoS 面。这四个不是「白拿」而是「采纳上游加固」，要改两后端并重跑运行态，\n已从 B1 移入 B3′。立项 §2 加了修正块、§5 改了批次表。\n\n**两处实测新增风险（立项 §6）：**\n\n一、跨层 peer 不一致。已发布的 @juhai/client-fact@1.0.0-rc.3 声明 peer @juhai/kernel: 0.16.1\n（lockfile 权威），而控制面仓里**同版本的源码**声明 0.22.0——控制面昨天做框架同步时改了\n源码却没重新发布。本仓 pin 0.22.0 后 pnpm install 报 unmet peer（警告，不阻断），\n**且现有门禁一条都抓不到**。三条出路（等平台重发 / 本仓退回 0.16.1 / 登记偏差并加 peer\n判据）本提交不代为决定，登记在立项 §6 等裁。\n\n二、pin 的下游代价，由 check:kernel-downstream 第一时间抓到：它在仓外装 contracts 以证明\n下游可消费，而仓外没有 .npmrc，@juhai/kernel 落到 npmjs.org 上 404。这不是门禁的毛病，\n是 pin 的真实代价——**任何消费方不配 @juhai scoped registry 就装不上**（框架 F11 原文同样\n这么声明）。处理：夹具复制仓内 .npmrc 的 scoped registry 行，把断言坐实为「配了 registry\n的消费者装得上」；并在「pin 了 @juhai/* 却无 registry 声明」时 **fail-closed**，绝不静默\n回落到公共 registry（实活验证：去掉声明即 D4 红）。新前提已写进接入手册，五个产品仓\n迁移时要同步配置。\n\n顺带一个可复用的性质：check:kernel-admission 的 K1 只计**直接声明**，所以每迁走一个模块，\n锁里的自有导出数就降一次——它天然成了这条线的进度计（763 → 755）。\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-18T02:06:23-07:00"}],"HeadCommit":{"Sha1":"fd3ba87ed111d9245012f0578178cccb4743ab20","Message":"chore(reports): B1 的二十八份静态证据 回绑 @ fb2fb1a，刷新快照锚点\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 fb2fb1a（声明落后 0，本提交自身使实测\n落后 1，在 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=fb2fb1a、worktreeDirty:false）。\n整轮 28 步全执行，前 27 步全绿，末步 check:kernel-admission 仍是那 8 处已知诚实红。\n\n本批次内两把锁各重签一次，都是「变更即复核」而非绕过：\n- kernel.exports.lock.json 763 → 755（statemachine 的 8 个导出归属转移给 @juhai/kernel）\n- check:kernel-downstream 的仓外夹具改为携带 scoped registry 后转绿；缺声明即 fail-closed\n 的分支已实活验证\n\n运行态未跑：B1 只动契约包的一个转发文件，contracts 312/312 与 typecheck 13/13 已覆盖；\n按仓规矩三级证据分开陈述，不用静态绿冒充运行态绿。runtime 报告仍绑在 dcd1c14，\n下次动到两后端（B3′ 采纳上游加固）时必须重跑。\n\n工作区内三份 reports/ui-*.latest.json 的改动早于本批次，未提交也未还原。\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-18T02:08:00-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/ee4bc06608d88515f025c3a2dcffacb9f47c5417...fd3ba87ed111d9245012f0578178cccb4743ab20","Len":2}...
|
1789722483
|
Edit
Delete
|
|
31102
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1b2328540 {"Commits":[{"Sha1":"1b2328540134f0118d2e3ed9abe10095e2ae4679","Message":"chore(reports): 工作台两份快照回绑 @ 956c7b6\n\ndocs/runbook.md 在 workbench-ops-snapshot 的作用域里（error 级），上一条 §7 补注把它打成\n过期；同时 bc44b4a 改了 build-workbench-snapshots.mjs，两份快照的作用域都被碰到。经\npnpm reports:rebind --gates workbench-snapshots 在 HEAD 干净检出里重跑带回，两份均绑\n956c7b6 / worktreeDirty=false / status=ok。\n\n只提交这两份报告；工作区其余在途改动属并行会话，未触碰。\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-18T02:15:12-07:00"},{"Sha1":"d9664ca9989ad3ea59399f95b6fcd56544170c52","Message":"chore(reports): check:module-imports 与 runtime-governance 回绑 @ bc44b4a\n\n两道门禁都在 bc44b4a 的临时干净检出里重跑（主工作树有并行会话的在途改动）：\ncheck:module-imports 扫 387 个源文件 0 处跨模块 import；runtime-governance 走读\napps/ 源码，tenant/outbox 五项接线指标均为 0。两份 provenance 均 worktreeDirty=false。\n\n两条限制写在这里，别把绑定当成这两道门禁现在是绿的：\n1. module-imports 的作用域含 governance/check-module-imports.mjs，该文件此刻仍是未提交\n 状态（并行会话在改），所以 check:evidence 仍会按 EVIDENCE_WORKTREE_CHANGED 记它，\n 要等那份改动落盘后再回绑一次。\n2. runtime-governance 是单跑一道，runId 与 runtime/reports 里同批的其余静态子报告不同。\n runtime 的 check:governance 要求静态子报告同一 SHA/dirty/runner/runId，重新对齐只能靠\n 一次完整的 pnpm --dir runtime check；本次只保证它自己的作用域新鲜度。\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-18T02:14:40-07:00"},{"Sha1":"956c7b6ad393ce44aa9aae0d647ae59fbc61ec56","Message":"docs(runbook): §7 补第四处「前置失败销毁好证据」——revocation-sla 由用例自己在 beforeAll 写 failed\n\n§7 现有那条 2026-09-18 警告说的是三个 runner（adda76a 已修前置守卫段）。同族还有第四处，\n且是唯一一处在测试代码里的：reports/revocation-sla.latest.json 的写入者不是 runner，而是\nruntime/test/e2e/revocation-sla.test.ts 自己（check-mainline.mjs 全文只写 mainline-acceptance）。\n\n要害在时机——该文件 beforeAll 的第一句（:68）就无条件写下 RUN_NOT_COMPLETED，下一句才做\nisolated() 库名校验（mainline-support.ts:11 要求 /platform_\u003ckind\u003e_(ms23|test|ci)）。先毁证据\n再校验前置，正是 adda76a 修掉的那个毛病。\n\n触发面不止 mainline:check：runtime/test 是工作区包 platform-tests，pnpm runtime:check:runtime\n第 5 步 turbo run test 就会跑到它。2026-09-18 实测：七个模块库建成 platform_\u003cm\u003e_acc0918 时\ne2e/chaos 整片以 MAINLINE_ISOLATED_DATABASE_REQUIRED 失败，该报告同时被清空。故「前置守卫段\n已修复、只有跑到一半才会写 failed」对本处不成立，本条一并写明救回方式。\n\n代码修复尚未做且本轮不做：runtime/test 正在三份验收报告的作用域里，重跑期间改它等于把刚跑出\n的绑定再作废一次。已登记在治理仓开发计划 §8 变更记录（2026-09-18）。\n\n本次只改本文件；工作区其余在途改动属并行会话，未触碰。\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-18T02:13:53-07:00"},{"Sha1":"bc44b4a3ccbdd4d16bd479c15f78c321a273e243","Message":"fix(governance): 工作台目录快照单列采纳形态，并按 Catalog 证据现算托管消费者数\n\n无运行时模块的 14 条 Catalog 条目此前被快照压成两类说法，两处都低报了 Catalog 已有的事实。\n\n一、form=adopted 的三条 P0（应用群网关 / 统一交付平台 / 集中观测平台）code_truth=null、\n无运行时模块，落进 none 分支后 note 写成「只保留历史设计引用，不可调用」。实际落点是本仓\n采纳的入口、collector 与发布/晋级门禁，evidence 里逐条登记（Caddyfile + check-caddy、\notel collector + check-otel、release-manifest + check-promotion），2026-09-16 经\nCHG-009 / 011 / 012 由 Owner 裁决改指采纳形态落点。新增 consumption.kind =\nadopted-infrastructure，判据取 Catalog 的 form，排在 code_truth 推断之前——这类能力本就\n不会有 runtime/modules 或契约包路径。当前 Catalog 下 none 归零。\n\n二、三条 module_e2 共用一句「迁出需三消费者 + G4 证据」，而 evidence 本就记着差别：\n公共文件 3 个、通知与 Webhook 3 个、配置与功能开关 1 个（与 contracts/README.md\n「配置平台尤其仍缺第二、第三消费者」一致）。hostedConsumerEvidence 按 evidence 里本仓之外的\n*acceptance*.json 依消费方仓去重计数，写进 consumption.consumers，note 按是否达到三消费者\n分开说。count \u003e= 3 只说明消费者验收证据齐，不代表 G4 已裁决。\n\n数据全部取自既有 Catalog 字段，不新设人工台账、不改 contracts/catalogs/、不动 Schema；\ndesign 只增透传的 form。consumption.kind 取值域扩了一个，枚举穷尽的消费者须回看，\nCATALOG_SCHEMA_VERSION 2 -\u003e 3，rules 两条措辞同步改。\n\n测试 8 -\u003e 9：真实输入用例断言三条采纳形态不落 none、三条托管条目的消费者数与 note 各不相同；\n新增一例专测消费者计数（同仓多份验收只算一个、本仓门禁产物不算、非 acceptance 不算）。\n篡改必红实测：短路 adopted 分支与阈值后 3 例转红。治理全量 323/323。\n\n报告回绑单独成提交，跟在本提交之后。\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-18T02:10:08-07:00"}],"HeadCommit":{"Sha1":"1b2328540134f0118d2e3ed9abe10095e2ae4679","Message":"chore(reports): 工作台两份快照回绑 @ 956c7b6\n\ndocs/runbook.md 在 workbench-ops-snapshot 的作用域里（error 级），上一条 §7 补注把它打成\n过期；同时 bc44b4a 改了 build-workbench-snapshots.mjs，两份快照的作用域都被碰到。经\npnpm reports:rebind --gates workbench-snapshots 在 HEAD 干净检出里重跑带回，两份均绑\n956c7b6 / worktreeDirty=false / status=ok。\n\n只提交这两份报告；工作区其余在途改动属并行会话，未触碰。\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-18T02:15:12-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/32ad69a15ceb55e1cbcb170d7fdd47897e50c01b...1b2328540134f0118d2e3ed9abe10095e2ae4679","Len":4}...
|
1789723947
|
Edit
Delete
|