|
31121
|
10
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f897e9c04 {"Commits":[{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"}],"HeadCommit":{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"},"CompareURL":"vodtest/pc/compare/3a794261c6bc270385e7eb7ed870e8ec38b8902d...f897e9c044c0085de57de1a598692f9a5a54936c","Len":1}...
|
1789724731
|
Edit
Delete
|
|
31115
|
9
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f897e9c04 {"Commits":[{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"}],"HeadCommit":{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"},"CompareURL":"vodtest/pc/compare/3a794261c6bc270385e7eb7ed870e8ec38b8902d...f897e9c044c0085de57de1a598692f9a5a54936c","Len":1}...
|
1789724731
|
Edit
Delete
|
|
31120
|
8
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f897e9c04 {"Commits":[{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"}],"HeadCommit":{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"},"CompareURL":"vodtest/pc/compare/3a794261c6bc270385e7eb7ed870e8ec38b8902d...f897e9c044c0085de57de1a598692f9a5a54936c","Len":1}...
|
1789724731
|
Edit
Delete
|
|
31119
|
7
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f897e9c04 {"Commits":[{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"}],"HeadCommit":{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"},"CompareURL":"vodtest/pc/compare/3a794261c6bc270385e7eb7ed870e8ec38b8902d...f897e9c044c0085de57de1a598692f9a5a54936c","Len":1}...
|
1789724731
|
Edit
Delete
|
|
31118
|
4
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f897e9c04 {"Commits":[{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"}],"HeadCommit":{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"},"CompareURL":"vodtest/pc/compare/3a794261c6bc270385e7eb7ed870e8ec38b8902d...f897e9c044c0085de57de1a598692f9a5a54936c","Len":1}...
|
1789724731
|
Edit
Delete
|
|
31117
|
3
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f897e9c04 {"Commits":[{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"}],"HeadCommit":{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"},"CompareURL":"vodtest/pc/compare/3a794261c6bc270385e7eb7ed870e8ec38b8902d...f897e9c044c0085de57de1a598692f9a5a54936c","Len":1}...
|
1789724731
|
Edit
Delete
|
|
31116
|
1
|
5
|
11
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"f897e9c04 {"Commits":[{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"}],"HeadCommit":{"Sha1":"f897e9c044c0085de57de1a598692f9a5a54936c","Message":"团购管理包厢设置按钮显示\n","AuthorEmail":"1091045324@qq.com","AuthorName":"caihongyu","CommitterEmail":"1091045324@qq.com","CommitterName":"caihongyu","Timestamp":"2026-09-18T17:45:09+08:00"},"CompareURL":"vodtest/pc/compare/3a794261c6bc270385e7eb7ed870e8ec38b8902d...f897e9c044c0085de57de1a598692f9a5a54936c","Len":1}...
|
1789724731
|
Edit
Delete
|
|
31113
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"72c053ccb {"Commits":[{"Sha1":"72c053ccbb2b4effb1451b6b61e69faf9c313fd5","Message":"docs(治理): README 订正——「判定逻辑在 core」这句话此前对 L6 并不成立\n\n第 49 行写着「判定逻辑在 workspace-consistency-core.mjs，夹具用例 19/19」。前半句对\nL6 是假的（它的判定与文件系统读取缠在 IO 脚本里、测试零覆盖），后半句的 19 也早已陈旧。\n\nL6 的判定已于同日搬进 core 并补 8 条用例，这句话现在成立了；数字改为当前的 42，\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:39:56-07:00"}],"HeadCommit":{"Sha1":"72c053ccbb2b4effb1451b6b61e69faf9c313fd5","Message":"docs(治理): README 订正——「判定逻辑在 core」这句话此前对 L6 并不成立\n\n第 49 行写着「判定逻辑在 workspace-consistency-core.mjs，夹具用例 19/19」。前半句对\nL6 是假的（它的判定与文件系统读取缠在 IO 脚本里、测试零覆盖），后半句的 19 也早已陈旧。\n\nL6 的判定已于同日搬进 core 并补 8 条用例，这句话现在成立了；数字改为当前的 42，\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:39:56-07:00"},"CompareURL":"luoanwu/platform-governance/compare/7433af77e643c41f2ccb34fb8aebe363ec76e306...72c053ccbb2b4effb1451b6b61e69faf9c313fd5","Len":1}...
|
1789724399
|
Edit
Delete
|
|
31112
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"7433af77e {"Commits":[{"Sha1":"7433af77e643c41f2ccb34fb8aebe363ec76e306","Message":"test(治理): L6 的判定搬进 core 并补负向用例——它此前是唯一零覆盖的一条\n\n一致性门禁 L1—L5 / L7—L13 的判定都在 lib/workspace-consistency-core.mjs 里、各有负向\n用例，**唯独 L6（worktree 两侧 gitdir）与文件系统读取缠在 check-workspace-consistency.mjs\n里**，全量扫描确认 tests/ 里没有任何一条用例触达它。它「能工作」的唯一证据是恰好没在\n实数据上报错——而「没报错」与「判不出来」在外部看来一模一样。\n\n本轮只搬不改：IO 函数改为只收集事实，判定交给新的纯函数 evaluateWorktreeGitdirs。\n**判词逐字未变，改前改后门禁 --json 输出实测完全相同**（status / counts / issues 三者\n逐字相等，prunableWorktrees 仍为 5、L9 仍为 1）。\n\n补 8 条负向用例，覆盖两个方向的全部分支：\n 方向一 .git 为空 / 指向不存在的登记 / 登记反指不回来（含反指读不出时须写「(空)」）；\n 三种坏法互斥，前一种命中不再叠加后一种\n 方向二 gitdir 为空即红；目标还在就跳过（反指归方向一，不重复报）；\n **目标没了且旁边没有同名工作树 = prunable，只计数不报**——那是 git worktree\n prune 的日常；目标没了但工作树就在旁边 = 失联，判红且不计入 prunable\n\n顺带核实两条初测假阳性，记在这里免得再查一遍：L9 的判定其实在 core 里且有用例\n（composeProjectName / composeProjectCollisions），只是测试里不出现「L9」这个字面量；\nL0 与 L28 是正则误匹配（一个字符类、一处注释里的行号）。\n\n一致性门禁测试 34 → 42，治理层全量 389 → 401（395 过 / 6 跳 / 0 失败）；\n统一入口阻断性门禁 11/11。\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:39:16-07:00"},{"Sha1":"1e6a813a72945400129128947654df4ecdc8849d","Message":"docs(回灌): U-39 / U-40——发布物与源码同版本不同内容，且 provenance 无 gitSha\n\n新增 §2E 第 5 轮条目（基础基座 → 基础设施）。采集自 OS 执行「内核退回 pin 立项」B1\n（contracts exact pin @juhai/kernel@0.22.0）时对接已发布客户端包的实测。\n\nU-39 发布物与其源码同版本不同内容，peer 只是露出来的一角。已发布的\n @juhai/client-fact@1.0.0-rc.3 声明 peer @juhai/kernel: 0.16.1（发布物自证），而控制面仓\n 同版本源码声明 0.22.0——2026-09-17 框架同步只改了 runtime/clients/fact/package.json 未重发。\n 进一步拆开发布物：dist 里没有 Authorization 回查鉴权，源码 reader.ts:31 却发\n Bearer ${token}。消费侧对此完全不可见：pnpm 对未满足 peer 只打一行 WARN 就继续装。\n → 平台侧动作：重发 rc.4 携带正确 peer，发布前确认 dist 与源码同一提交。\n 基座侧已自保：新增 PEER_UNSATISFIED 判据 + 五字段登记（期限 2026-12-18）。\n\nU-40 本地旁路发布的发布物不可对账到提交。registry 上 rc.3 的 provenance.json 为\n runner:\"local\" / reports:[] / gitSha:\"\"——空字符串。任何消费者都无法验证装到的包出自哪次\n 提交，U-39 那种「同版本不同内容」因此无法被机器发现。这比 peer 错一版严重：peer 至少还有\n 一个可比的值，gitSha 为空是判据缺席。\n → 平台侧动作：发布物 provenance.json 必须带真实 gitSha，本地旁路也不得留空——旁路可以解除\n CI 身份检查，但不应连「这是哪次提交构建的」都放弃。\n\n两条均标 🔴 下层缺口，阻塞于平台发布列车（G-12 计费）。基座侧不停等：按立项 §6 三条出路\n裁为 ③（登记偏差 + 加判据），B2 / B3′ 继续推进。\n\n一致性门禁复跑：合计 1 条，仅 L9（8 仓共用 compose project api-nestjs），与本次改动无关——\n它正是 OS 在 framework-criteria.json 里登记为 missing 的框架 F14。\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:39:13-07:00"}],"HeadCommit":{"Sha1":"7433af77e643c41f2ccb34fb8aebe363ec76e306","Message":"test(治理): L6 的判定搬进 core 并补负向用例——它此前是唯一零覆盖的一条\n\n一致性门禁 L1—L5 / L7—L13 的判定都在 lib/workspace-consistency-core.mjs 里、各有负向\n用例，**唯独 L6（worktree 两侧 gitdir）与文件系统读取缠在 check-workspace-consistency.mjs\n里**，全量扫描确认 tests/ 里没有任何一条用例触达它。它「能工作」的唯一证据是恰好没在\n实数据上报错——而「没报错」与「判不出来」在外部看来一模一样。\n\n本轮只搬不改：IO 函数改为只收集事实，判定交给新的纯函数 evaluateWorktreeGitdirs。\n**判词逐字未变，改前改后门禁 --json 输出实测完全相同**（status / counts / issues 三者\n逐字相等，prunableWorktrees 仍为 5、L9 仍为 1）。\n\n补 8 条负向用例，覆盖两个方向的全部分支：\n 方向一 .git 为空 / 指向不存在的登记 / 登记反指不回来（含反指读不出时须写「(空)」）；\n 三种坏法互斥，前一种命中不再叠加后一种\n 方向二 gitdir 为空即红；目标还在就跳过（反指归方向一，不重复报）；\n **目标没了且旁边没有同名工作树 = prunable，只计数不报**——那是 git worktree\n prune 的日常；目标没了但工作树就在旁边 = 失联，判红且不计入 prunable\n\n顺带核实两条初测假阳性，记在这里免得再查一遍：L9 的判定其实在 core 里且有用例\n（composeProjectName / composeProjectCollisions），只是测试里不出现「L9」这个字面量；\nL0 与 L28 是正则误匹配（一个字符类、一处注释里的行号）。\n\n一致性门禁测试 34 → 42，治理层全量 389 → 401（395 过 / 6 跳 / 0 失败）；\n统一入口阻断性门禁 11/11。\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:39:16-07:00"},"CompareURL":"luoanwu/platform-governance/compare/6b045590e6ba93dd703453bc478b3b6c879491f3...7433af77e643c41f2ccb34fb8aebe363ec76e306","Len":2}...
|
1789724358
|
Edit
Delete
|
|
31111
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"3deb4ea37 {"Commits":[{"Sha1":"3deb4ea37b83c2e2977c9c2b8e8166c101002860","Message":"chore(reports): PEER_UNSATISFIED 判据的二十八份静态证据 回绑 @ 8e5c633，刷新快照锚点\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 8e5c633（声明落后 0，本提交自身使实测\n落后 1，在 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=8e5c633、worktreeDirty:false）。\n整轮 28 步全执行，前 27 步全绿，末步 check:kernel-admission 仍是那 8 处已知诚实红。\n\nplatform-dependency-provenance 报告新增一处 registered：PEER_UNSATISFIED（client-fact\nrc.3 的 peer 0.16.1 ↔ 本仓已解析 0.22.0），期限 2026-12-18。门禁整体仍绿——登记的作用是\n把「pnpm 只打 WARN、门禁零覆盖」变成「可见、有期限、到期转红」，不是让它消失。\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:38:50-07:00"},{"Sha1":"8e5c633cbfbc16afc61c95b8cfcecb90a2f1aa88","Message":"feat(governance): PEER_UNSATISFIED 判据——把 pnpm 只打 WARN 的跨包版本不一致变成可见可登记\n\nB1 pin @juhai/kernel@0.22.0 后 pnpm 报了一行 unmet peer 就继续装，**本仓原有门禁一条都\n抓不到**。按内核退回 pin 立项 §6 三条出路裁为 ③（登记偏差 + 加判据，不停等发布列车）。\n\n新判据 PEER_UNSATISFIED：lock 里 @juhai/* 之间声明的 peer 必须被已解析版本满足；\n未满足即红，可按既有五字段口径登记降级为 registered，过期转红。peer 指向本仓根本没装的\n包时不判（防过度判红）。自检从 7 条扩到 12 条，新增 5 条全覆盖上述分支。\n\n实测命中一条真问题，并顺带拆出更深的一层：\n\n- 已发布的 @juhai/client-fact@1.0.0-rc.3 声明 peer @juhai/kernel: 0.16.1（发布物自证），\n 而控制面仓里**同版本的源码**声明 0.22.0——2026-09-17 框架同步只改了 package.json 没重发\n- 把 registry 上的 rc.3 拆开看：dist 里**没有** Authorization 回查鉴权，而源码 reader.ts:31\n 发 Bearer ${token}。**同一个版本号，registry 与源码是两份不同的代码**\n- 该发布物 provenance.json 为 runner:\"local\" / reports:[] / **gitSha:\"\"**——空字符串。\n 任何消费者都无法验证装到的包出自哪次提交，上一条「同版本不同内容」因此无法被机器发现\n\n不兼容风险经 delta 分析可论证为极低：内核 v0.16.1 → v0.22.0 只改 health.ts(+126)、\nalert.ts(+53)、tenant.ts(+12) 三处纯增，client-fact 一个都不消费。故登记而非阻断，\n期限 2026-12-18，blockedBy 指向平台发布列车（G-12 计费阻塞）。\n\n为什么不选另两条路（立项 §6 已记）：② 退回 pin 0.16.1 的当前代价几乎为零——三处加固\n（replay cursor-unknown、WS 载荷上限、订阅数上限）**实测都已在 v0.16.1 里**，我上一轮说\n「退回等于放弃 6 个版本加固」是错的——但它是伪解，B2 要迁 alert/tenant、B3 要迁 health 时\npeer 冲突原样回来；① 等平台重发会把本仓进度挂在不可控的跨仓列车上，且若仍走本地旁路，\nprovenance 依旧无 gitSha，只解决 peer 不解决可对账性。\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:37:17-07:00"}],"HeadCommit":{"Sha1":"3deb4ea37b83c2e2977c9c2b8e8166c101002860","Message":"chore(reports): PEER_UNSATISFIED 判据的二十八份静态证据 回绑 @ 8e5c633，刷新快照锚点\n\n本批次最后一个提交，按 C241 同时刷新快照锚点到 8e5c633（声明落后 0，本提交自身使实测\n落后 1，在 +1 自指窗内）。\n\n二十八份 reports/*.latest.json 全部 clean 绑定（gitSha=8e5c633、worktreeDirty:false）。\n整轮 28 步全执行，前 27 步全绿，末步 check:kernel-admission 仍是那 8 处已知诚实红。\n\nplatform-dependency-provenance 报告新增一处 registered：PEER_UNSATISFIED（client-fact\nrc.3 的 peer 0.16.1 ↔ 本仓已解析 0.22.0），期限 2026-12-18。门禁整体仍绿——登记的作用是\n把「pnpm 只打 WARN、门禁零覆盖」变成「可见、有期限、到期转红」，不是让它消失。\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:38:50-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/fd3ba87ed111d9245012f0578178cccb4743ab20...3deb4ea37b83c2e2977c9c2b8e8166c101002860","Len":2}...
|
1789724335
|
Edit
Delete
|
|
31110
|
11
|
5
|
7
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"3a794261c {"Commits":[{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"}],"HeadCommit":{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"},"CompareURL":"vodtest/pc/compare/f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5...3a794261c6bc270385e7eb7ed870e8ec38b8902d","Len":1}...
|
1789724002
|
Edit
Delete
|
|
31109
|
10
|
5
|
7
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"3a794261c {"Commits":[{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"}],"HeadCommit":{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"},"CompareURL":"vodtest/pc/compare/f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5...3a794261c6bc270385e7eb7ed870e8ec38b8902d","Len":1}...
|
1789724002
|
Edit
Delete
|
|
31104
|
9
|
5
|
7
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"3a794261c {"Commits":[{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"}],"HeadCommit":{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"},"CompareURL":"vodtest/pc/compare/f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5...3a794261c6bc270385e7eb7ed870e8ec38b8902d","Len":1}...
|
1789724002
|
Edit
Delete
|
|
31108
|
8
|
5
|
7
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"3a794261c {"Commits":[{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"}],"HeadCommit":{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"},"CompareURL":"vodtest/pc/compare/f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5...3a794261c6bc270385e7eb7ed870e8ec38b8902d","Len":1}...
|
1789724002
|
Edit
Delete
|
|
31103
|
7
|
5
|
7
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"3a794261c {"Commits":[{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"}],"HeadCommit":{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"},"CompareURL":"vodtest/pc/compare/f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5...3a794261c6bc270385e7eb7ed870e8ec38b8902d","Len":1}...
|
1789724002
|
Edit
Delete
|
|
31107
|
4
|
5
|
7
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"3a794261c {"Commits":[{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"}],"HeadCommit":{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"},"CompareURL":"vodtest/pc/compare/f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5...3a794261c6bc270385e7eb7ed870e8ec38b8902d","Len":1}...
|
1789724002
|
Edit
Delete
|
|
31106
|
3
|
5
|
7
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"3a794261c {"Commits":[{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"}],"HeadCommit":{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"},"CompareURL":"vodtest/pc/compare/f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5...3a794261c6bc270385e7eb7ed870e8ec38b8902d","Len":1}...
|
1789724002
|
Edit
Delete
|
|
31105
|
1
|
5
|
7
|
18
|
0
|
0
|
refs/heads/pc-260915
|
0
|
{"Commits":[{"Sha1":"3a794261c {"Commits":[{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"}],"HeadCommit":{"Sha1":"3a794261c6bc270385e7eb7ed870e8ec38b8902d","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T17:33:15+08:00"},"CompareURL":"vodtest/pc/compare/f0a3ea0e395022ad8ffd30ff8eeb1bba490c9fa5...3a794261c6bc270385e7eb7ed870e8ec38b8902d","Len":1}...
|
1789724002
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|