|
30878
|
8
|
5
|
7
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"abbfcd78b {"Commits":[{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"}],"HeadCommit":{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"},"CompareURL":"vodtest/pay/compare/d17e203a06df00db27d10bdcc11393d2114e3a1a...abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Len":1}...
|
1789715761
|
Edit
Delete
|
|
30879
|
10
|
5
|
7
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"abbfcd78b {"Commits":[{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"}],"HeadCommit":{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"},"CompareURL":"vodtest/pay/compare/d17e203a06df00db27d10bdcc11393d2114e3a1a...abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Len":1}...
|
1789715761
|
Edit
Delete
|
|
30880
|
11
|
5
|
7
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"abbfcd78b {"Commits":[{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"}],"HeadCommit":{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"},"CompareURL":"vodtest/pay/compare/d17e203a06df00db27d10bdcc11393d2114e3a1a...abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Len":1}...
|
1789715761
|
Edit
Delete
|
|
30881
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6bf1e7d52 {"Commits":[{"Sha1":"6bf1e7d524a70a3ecd012c29ea6c627866c01c5c","Message":"docs(架构): 总架构配套图与口径订正——重画图 1 / 图 2，新增图 4 关系全景\n\n企业应用群总架构-2026-09-17.md 与图 3 已随 5b7a1c0 提交（暂存区被并行会话的\n提交扫走，不是有意合并进那个范围），本提交补齐其余部分。\n\n**图 1 / 图 2 重画。** 图 1 原写「基础设施（23 项）」、画着「四候选」框，应用名\n还是改名前的「嗨设首席」；图 2 把 OS 标成「Projection 未实现」、干线标成「持久\n投递待裁决」。四处都已被后续裁决推翻：四候选 2026-09-16 撤销（CHG-015）、Catalog\n现为 21 条，OS 投影 2026-09-14 已在 main，三条前置 DEC 全部批准。图 1 另加一条\n跨层治理带，把「平台治理不是第六层」画进图面。\n\n**新增图 4 现存关系全景。** 逐条查实全组的边：左半五类有边的关系，右半七条负\n结论。查证推翻了总架构初稿 §3.1 的一处判断——初稿用 grep '\"@juhai/…\"' 取依赖，\n同时命中了 name 字段，于是把报价的 @juhai/public-file 与智服的\n@juhai/service-contracts 当成「对下层消费」，实际两者都是该仓自己的 workspace 包。\n按带版本号的依赖项重取：四个业务应用对下层的跨仓包依赖为零，全组跨仓包依赖只有\nHR、OS、enterprise-platform 三个消费仓。\n\n由此改口径的另有两条：\n\n- 三项 module_e2（文件 / 通知 / 配置）在工单仓里是 @repo/* private 包，仓外零\n 消费者，只被本仓 api-fastify / api-nestjs 依赖——「已被业务应用消费」不成立，\n 三消费者规则的计数应从 0 算起\n- relationships.json 的 relationships 为 {}，关系在机器层面没有登记；图 4 的边\n 全部由 package.json / kernel.products.json / facts.json / runtime/modules.json\n 推导，今天没有门禁能发现某条关系消失\n\n**四份下游文档按活跃 Catalog 改齐：** 分层与装配模型（23→21、派生仓 3→0、1/23\n的分母；§3.1 是带日期快照，只加订正行不改写正文）、基础/CLAUDE.md 分层词表段、\n基础/README 头段（「已退役 15 个、现存 3 个」是 09-16 白天的中间态）、企业领域\n应用层 README（引的 platform-contracts 已于 2026-09-16 物理移除，事实数 1→11）。\n平台治理 README 收纳表随新增文件改计数（基础/ 根文件 63→65，根散文件 9→10）。\n\n复跑：工作区一致性门禁 L1—L13 只剩既有的 L9（8 个仓共用 compose project 名\napi-nestjs），L4 / L13 均为 0；治理层 npm test 378 项 0 失败；check-domain-layer\n13/13 条全在基线内、无新增。未动任何冻结物、审批记录与机器 Catalog。\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-18T00:20:28-07:00"}],"HeadCommit":{"Sha1":"6bf1e7d524a70a3ecd012c29ea6c627866c01c5c","Message":"docs(架构): 总架构配套图与口径订正——重画图 1 / 图 2，新增图 4 关系全景\n\n企业应用群总架构-2026-09-17.md 与图 3 已随 5b7a1c0 提交（暂存区被并行会话的\n提交扫走，不是有意合并进那个范围），本提交补齐其余部分。\n\n**图 1 / 图 2 重画。** 图 1 原写「基础设施（23 项）」、画着「四候选」框，应用名\n还是改名前的「嗨设首席」；图 2 把 OS 标成「Projection 未实现」、干线标成「持久\n投递待裁决」。四处都已被后续裁决推翻：四候选 2026-09-16 撤销（CHG-015）、Catalog\n现为 21 条，OS 投影 2026-09-14 已在 main，三条前置 DEC 全部批准。图 1 另加一条\n跨层治理带，把「平台治理不是第六层」画进图面。\n\n**新增图 4 现存关系全景。** 逐条查实全组的边：左半五类有边的关系，右半七条负\n结论。查证推翻了总架构初稿 §3.1 的一处判断——初稿用 grep '\"@juhai/…\"' 取依赖，\n同时命中了 name 字段，于是把报价的 @juhai/public-file 与智服的\n@juhai/service-contracts 当成「对下层消费」，实际两者都是该仓自己的 workspace 包。\n按带版本号的依赖项重取：四个业务应用对下层的跨仓包依赖为零，全组跨仓包依赖只有\nHR、OS、enterprise-platform 三个消费仓。\n\n由此改口径的另有两条：\n\n- 三项 module_e2（文件 / 通知 / 配置）在工单仓里是 @repo/* private 包，仓外零\n 消费者，只被本仓 api-fastify / api-nestjs 依赖——「已被业务应用消费」不成立，\n 三消费者规则的计数应从 0 算起\n- relationships.json 的 relationships 为 {}，关系在机器层面没有登记；图 4 的边\n 全部由 package.json / kernel.products.json / facts.json / runtime/modules.json\n 推导，今天没有门禁能发现某条关系消失\n\n**四份下游文档按活跃 Catalog 改齐：** 分层与装配模型（23→21、派生仓 3→0、1/23\n的分母；§3.1 是带日期快照，只加订正行不改写正文）、基础/CLAUDE.md 分层词表段、\n基础/README 头段（「已退役 15 个、现存 3 个」是 09-16 白天的中间态）、企业领域\n应用层 README（引的 platform-contracts 已于 2026-09-16 物理移除，事实数 1→11）。\n平台治理 README 收纳表随新增文件改计数（基础/ 根文件 63→65，根散文件 9→10）。\n\n复跑：工作区一致性门禁 L1—L13 只剩既有的 L9（8 个仓共用 compose project 名\napi-nestjs），L4 / L13 均为 0；治理层 npm test 378 项 0 失败；check-domain-layer\n13/13 条全在基线内、无新增。未动任何冻结物、审批记录与机器 Catalog。\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-18T00:20:28-07:00"},"CompareURL":"luoanwu/platform-governance/compare/650711d6cb4d48b6d77a3edea998d26d60f87567...6bf1e7d524a70a3ecd012c29ea6c627866c01c5c","Len":1}...
|
1789716065
|
Edit
Delete
|
|
30882
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"0abd15c28 {"Commits":[{"Sha1":"0abd15c28dd2b92c583289934db660363b202fd4","Message":"chore(reports): check:evidence 回绑 @ 34fresh\n\n37 份已登记、34 份新鲜、0 error；余 3 份过期为需真实容器重跑的验收报告\n（runtime-acceptance / mainline-acceptance / revocation-sla，warn 按设计）。\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-18T00:28:32-07:00"},{"Sha1":"a4b3d356f9d2f7a831198787a5b19194f4f763c8","Message":"chore(reports): 双后端差分验收重跑回绑 @ 746f323\n\n本轮把 conformance-differential 从「未登记的聚合报告」订正为登记条目后，它第一次\n被新鲜度门禁判为过期——触发者正是同轮改到的 check-conformance-differential.mjs，\n说明登记的作用域是对的。真实 DB + Redis 重跑：7 checkpoints × 2 backends，\n逐字段 0 differences。\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-18T00:28:10-07:00"},{"Sha1":"746f323c203531c4ced5f3ca60ea29a4c53c7c4d","Message":"chore(reports): 工作台两份快照回绑 @ adda76a\n\nrunbook §7 的订正落在运维快照作用域内（docs/runbook.md），经 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-18T00:27:33-07:00"},{"Sha1":"adda76acfd8fa046e1f2a320c15b5384b4ddef73","Message":"fix(runtime): 前置守卫失败不得覆盖验收报告，并补「一模块一库」检查\n\n按 docs/runbook.md §7 的配方逐字重跑 runtime 验收，当场复现两个缺陷。\n\n一、配方本身是错的。§7 只写了 DATABASE_URL 与 REDIS_URL，而七个模块的\nprisma/schema.prisma 各自写死 url = env(\"DATABASE_URL_\u003cMODULE\u003e\")。照它执行时，\n前两步 nestjs/fastify-migrate-deploy 会通过，第三步 migrate-status 才以\nPrisma P1012 \"Environment variable not found\" 失败——报错指向 wasm 校验，\n完全看不出是环境没配齐。§7 已补齐七个变量，并写明 prepare-mainline.mjs\n只供给主线验收要的 5 个（fact/permission/audit/owner/consumer），差的四个要自己建。\n\n二、更要紧的：那次失败把 runtime-acceptance.latest.json 覆盖成了 status:failed。\n775/775 那份真实结论就此丢失，靠 git checkout 才救回——差一点被当作真实回归提交上去。\n根因是三个 runner 都无条件 writeFileSync：前置守卫失败意味着**验收根本没跑**，\n此时写一份 failed 报告不是诚实，是用操作者的环境问题顶替代码的结论，\n并且顺手销毁了上一次真的跑过的证据。三个 runner 统一改为前置失败即退出、不碰报告：\n check-runtime-acceptance 实测：报告 sha256 前后一致\n check-ui-acceptance 实测：缺 REDIS_URL 时报告 sha256 前后一致\n check-conformance-differential 实测：同上\n\n新增 preflightModuleDatabases + requiredModuleDatabaseEnvNames，把缺失的七个\n变量在动任何东西之前一次列清。变量名**现取自各模块 prisma/schema.prisma**，\n不写死清单：模块增减自动跟上，也避免抄错 ai-gateway 那个没有下划线的\nDATABASE_URL_AIGATEWAY。该检查只接进 runtime 验收——UI 与差分验收跑的是\n两个 app，不走一模块一库。\n\npnpm 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-18T00:26:48-07:00"}],"HeadCommit":{"Sha1":"0abd15c28dd2b92c583289934db660363b202fd4","Message":"chore(reports): check:evidence 回绑 @ 34fresh\n\n37 份已登记、34 份新鲜、0 error；余 3 份过期为需真实容器重跑的验收报告\n（runtime-acceptance / mainline-acceptance / revocation-sla，warn 按设计）。\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-18T00:28:32-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/df678ac14f88628a7bc48ce3b53e248f1b257e8b...0abd15c28dd2b92c583289934db660363b202fd4","Len":4}...
|
1789716516
|
Edit
Delete
|
|
30883
|
16
|
5
|
16
|
86
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"4bb59f1fa {"Commits":[{"Sha1":"4bb59f1faa6737e1d679f5715a0c213b46e020a8","Message":"fix(logs): 优化双击选中并稳定查找框布局\n\n- 参考 VS Code 的文本边界规则，支持连续中文和中英数字整段双击选中\n- 跨查找高亮节点建立原生选区，保留复制、选区查找和横向滚动定位\n- 按查找框宽度预留计数区域，避免加载提示及匹配数量切换挤动按钮\n- 补充选词对照测试、离屏交互与逐帧布局回归，并更新日志帮助文档\n\n验证：\n- npm run typecheck\n- npx vitest run src/features/logs/logWordSelection.test.ts（5 项通过）\n- npm run check:knowledge\n- node scripts/test-log-viewer-browser.mjs --selection\n- node scripts/test-log-viewer-browser.mjs --find\n","AuthorEmail":"228834386@qq.com","AuthorName":"starry","CommitterEmail":"228834386@qq.com","CommitterName":"starry","Timestamp":"2026-09-18T14:59:03+08:00"},{"Sha1":"6ffe247b3198442b9a270c16b88e866f7560deb6","Message":"fix(logs): 支持查找框调宽并取消匹配总量截断\n\n- 移除查找栏左侧收缩图标，增加左右拖拽调宽、边界限制及双击复原\n- 自动续查到全文结束，支持同一行从原始列继续搜索，不丢失两万项之后的命中\n- 使用分块数字坐标保存结果，仅为可见行生成高亮，避免每页复制全部结果\n- 优先定位当前阅读位置附近的命中，支持文件底部查找与完整首尾循环\n- 同步帮助文档及回归夹具\n\n验证：\n- npm run build（包含 typecheck）\n- 77 项日志相关测试\n- 查找栏离屏测试：拖拽、24050 项全文计数、底部定位与首尾循环\n- 原有日志滚动离屏回归\n- npm run check:knowledge\n- git diff --check\n\n实际操作台视觉和拖拽手感保留人工验收。\n","AuthorEmail":"228834386@qq.com","AuthorName":"starry","CommitterEmail":"228834386@qq.com","CommitterName":"starry","Timestamp":"2026-09-18T13:41:38+08:00"},{"Sha1":"931d1e3cd2263189b2c0eb592436c8b69ad455d0","Message":"feat(logs): 对齐 VS Code 查找栏并移除文件列表搜索\n\n- 删除日志文件列表搜索框及其过滤状态，保留快速打开和全局搜索\n- 按参考图实现正文右上角紧凑查找栏，支持大小写、全字、正则、选区与键盘导航\n- 自动续查并按具体出现次数计数和定位，限制缓存并明确展示未完整计数\n- 隔离正则线程并支持超时取消，限制长行摘要大小，同步使用说明\n\n验证：\n- npm run typecheck\n- npm run build\n- 73 项日志相关测试\n- 查找栏与原有日志滚动离屏夹具通过\n- npm run check:knowledge\n- git diff --check\n\n实际操作台视觉与交互保留人工验收。\n","AuthorEmail":"228834386@qq.com","AuthorName":"starry","CommitterEmail":"228834386@qq.com","CommitterName":"starry","Timestamp":"2026-09-18T13:27:49+08:00"},{"Sha1":"d94c0aa3b7d46e66054a2a7da708b46e7f69e597","Message":"perf(logs): 增加双向预读与视口缓存\n\n减少定位日志末尾后反向滚动时的短暂加载占位：\n- 围绕可见原行号提前读取上下缓冲，优先滚动方向和可见缺块\n- 按原行号合并重叠正文，按距离淘汰并限制缓存行数及正文大小\n- 后台预读独立于前台读取，不触发全局忙碌状态或修改滚动位置\n- 切换文件和前台跳转取消旧预读，忽略迟到响应\n- 补充长行小块、反向滚动和迟到响应隔离的回归测试与验收说明\n\n验证：\n- 20 项相关单元测试通过\n- 7 组 Electron 离屏合成场景通过，120 毫秒延迟下逐帧检查反向滚动无加载闪烁和位置跳动\n- npm run typecheck、npm run build 通过\n- 未启动正式操作台或连接设备，实际日志体验仍需人工复测\n","AuthorEmail":"228834386@qq.com","AuthorName":"starry","CommitterEmail":"228834386@qq.com","CommitterName":"starry","Timestamp":"2026-09-18T12:22:20+08:00"},{"Sha1":"dfa031600cf28cd8993766c88159a013c5bec41a","Message":"fix(logs): 修复正文布局并恢复连续滚动\n\n修复新增导航条抢占正文高度，以及后台读取块变成界面行数限制的问题：\n- 日志正文使用纵向弹性布局，警告和导航按内容占高，小文件贴顶显示\n- 普通查看按文件总行数连续虚拟滚动，缺失正文按需读取并缓存最近四块\n- 保留过滤结果分页和阅读位置，防止未加载范围被静默复制为残缺内容\n- 增加 24 MiB 样本、缓存边界及独立 Electron 离屏组件回归测试\n\n验证：\n- 14 项相关单元测试通过\n- 离屏测试覆盖三行文件、窄窗口、跨 2000 行、末尾、功能及文件切换、过滤切换\n- npm run typecheck、npm run build、npm run check:knowledge 通过\n- 使用合成数据验证，未连接设备或启动正式操作台\n","AuthorEmail":"228834386@qq.com","AuthorName":"starry","CommitterEmail":"228834386@qq.com","CommitterName":"starry","Timestamp":"2026-09-18T12:00:12+08:00"}],"HeadCommit":{"Sha1":"4bb59f1faa6737e1d679f5715a0c213b46e020a8","Message":"fix(logs): 优化双击选中并稳定查找框布局\n\n- 参考 VS Code 的文本边界规则，支持连续中文和中英数字整段双击选中\n- 跨查找高亮节点建立原生选区，保留复制、选区查找和横向滚动定位\n- 按查找框宽度预留计数区域，避免加载提示及匹配数量切换挤动按钮\n- 补充选词对照测试、离屏交互与逐帧布局回归，并更新日志帮助文档\n\n验证：\n- npm run typecheck\n- npx vitest run src/features/logs/logWordSelection.test.ts（5 项通过）\n- npm run check:knowledge\n- node scripts/test-log-viewer-browser.mjs --selection\n- node scripts/test-log-viewer-browser.mjs --find\n","AuthorEmail":"228834386@qq.com","AuthorName":"starry","CommitterEmail":"228834386@qq.com","CommitterName":"starry","Timestamp":"2026-09-18T14:59:03+08:00"},"CompareURL":"pengzhiyu/JuhaiOpsDesk/compare/c6fbf67a98ba850b052b6d6585e7354718024ebc...4bb59f1faa6737e1d679f5715a0c213b46e020a8","Len":8}...
|
1789716533
|
Edit
Delete
|
|
30884
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"44686cc39 {"Commits":[{"Sha1":"44686cc39752ceb9b94fbfed9169b6fe0a2d6ea3","Message":"docs(计划): 登记两轮治理改动——未登记报告纳入机器记账、验收 runner 前置失败不得销毁证据\n\n§8 增两条当日记录：\n\n一、`check:evidence` 的未登记类此前只由 info 级 `SCOPE_UNDECLARED` 记着，处置口径\n写在 `evidence-scopes.json` 的散文里、无人机器核对，48 份报告里 13 份在此（27%）。\n已按例外机制的同一纪律搬成 `undeclared` 逐条登记，三条新规则判红两端。顺带订正\n「聚合报告」类的两处误归类，`runtime-governance` 与 `conformance-differential`\n转入正式登记（35 → 37）。\n\n二、为重跑被注释提交打过期的验收报告，照 runbook §7 逐字执行，复现两个缺陷：\n配方缺七个 `DATABASE_URL_\u003cMODULE\u003e`；三个验收 runner 在前置守卫失败时仍无条件写\n报告，把 775/775 覆盖成 failed。后者是证据完整性问题，三处已统一修并各自实测。\n\n三份需真实容器的验收报告仍未重跑，理由写在条目里：其设计中的保鲜路径是 CI。\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-18T00:29:15-07:00"}],"HeadCommit":{"Sha1":"44686cc39752ceb9b94fbfed9169b6fe0a2d6ea3","Message":"docs(计划): 登记两轮治理改动——未登记报告纳入机器记账、验收 runner 前置失败不得销毁证据\n\n§8 增两条当日记录：\n\n一、`check:evidence` 的未登记类此前只由 info 级 `SCOPE_UNDECLARED` 记着，处置口径\n写在 `evidence-scopes.json` 的散文里、无人机器核对，48 份报告里 13 份在此（27%）。\n已按例外机制的同一纪律搬成 `undeclared` 逐条登记，三条新规则判红两端。顺带订正\n「聚合报告」类的两处误归类，`runtime-governance` 与 `conformance-differential`\n转入正式登记（35 → 37）。\n\n二、为重跑被注释提交打过期的验收报告，照 runbook §7 逐字执行，复现两个缺陷：\n配方缺七个 `DATABASE_URL_\u003cMODULE\u003e`；三个验收 runner 在前置守卫失败时仍无条件写\n报告，把 775/775 覆盖成 failed。后者是证据完整性问题，三处已统一修并各自实测。\n\n三份需真实容器的验收报告仍未重跑，理由写在条目里：其设计中的保鲜路径是 CI。\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-18T00:29:15-07:00"},"CompareURL":"luoanwu/platform-governance/compare/6bf1e7d524a70a3ecd012c29ea6c627866c01c5c...44686cc39752ceb9b94fbfed9169b6fe0a2d6ea3","Len":1}...
|
1789716558
|
Edit
Delete
|
|
30885
|
1
|
5
|
1
|
32
|
0
|
0
|
refs/heads/master
|
1
|
{"Commits":[{"Sha1":"af3b43796 {"Commits":[{"Sha1":"af3b43796d8d81d8d606ba414acbf90a1a96004f","Message":"111\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:30:22+08:00"}],"HeadCommit":{"Sha1":"af3b43796d8d81d8d606ba414acbf90a1a96004f","Message":"111\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:30:22+08:00"},"CompareURL":"zhangjunnan/zhouhui/compare/ba4f01d0aae9a8ed29ec88d08b763c7959832095...af3b43796d8d81d8d606ba414acbf90a1a96004f","Len":1}...
|
1789716627
|
Edit
Delete
|
|
30886
|
8
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"82bea1818 {"Commits":[{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"}],"HeadCommit":{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"},"CompareURL":"vodtest/app/compare/47173e953bbf0fa6909cd9a744f93e84b3af2605...82bea1818b4939b2669fa482282e55b08d09988a","Len":1}...
|
1789716685
|
Edit
Delete
|
|
30887
|
9
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"82bea1818 {"Commits":[{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"}],"HeadCommit":{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"},"CompareURL":"vodtest/app/compare/47173e953bbf0fa6909cd9a744f93e84b3af2605...82bea1818b4939b2669fa482282e55b08d09988a","Len":1}...
|
1789716685
|
Edit
Delete
|
|
30888
|
1
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"82bea1818 {"Commits":[{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"}],"HeadCommit":{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"},"CompareURL":"vodtest/app/compare/47173e953bbf0fa6909cd9a744f93e84b3af2605...82bea1818b4939b2669fa482282e55b08d09988a","Len":1}...
|
1789716685
|
Edit
Delete
|
|
30889
|
3
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"82bea1818 {"Commits":[{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"}],"HeadCommit":{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"},"CompareURL":"vodtest/app/compare/47173e953bbf0fa6909cd9a744f93e84b3af2605...82bea1818b4939b2669fa482282e55b08d09988a","Len":1}...
|
1789716685
|
Edit
Delete
|
|
30890
|
4
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"82bea1818 {"Commits":[{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"}],"HeadCommit":{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"},"CompareURL":"vodtest/app/compare/47173e953bbf0fa6909cd9a744f93e84b3af2605...82bea1818b4939b2669fa482282e55b08d09988a","Len":1}...
|
1789716685
|
Edit
Delete
|
|
30891
|
7
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"82bea1818 {"Commits":[{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"}],"HeadCommit":{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"},"CompareURL":"vodtest/app/compare/47173e953bbf0fa6909cd9a744f93e84b3af2605...82bea1818b4939b2669fa482282e55b08d09988a","Len":1}...
|
1789716685
|
Edit
Delete
|
|
30892
|
10
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"82bea1818 {"Commits":[{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"}],"HeadCommit":{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"},"CompareURL":"vodtest/app/compare/47173e953bbf0fa6909cd9a744f93e84b3af2605...82bea1818b4939b2669fa482282e55b08d09988a","Len":1}...
|
1789716685
|
Edit
Delete
|
|
30893
|
11
|
5
|
8
|
22
|
0
|
0
|
refs/heads/app-260915
|
0
|
{"Commits":[{"Sha1":"82bea1818 {"Commits":[{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"}],"HeadCommit":{"Sha1":"82bea1818b4939b2669fa482282e55b08d09988a","Message":"需求 安全巡检 16865\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T15:31:18+08:00"},"CompareURL":"vodtest/app/compare/47173e953bbf0fa6909cd9a744f93e84b3af2605...82bea1818b4939b2669fa482282e55b08d09988a","Len":1}...
|
1789716685
|
Edit
Delete
|
|
30894
|
10
|
5
|
10
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"8cbfa7786 {"Commits":[{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"}],"HeadCommit":{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},"CompareURL":"vodtest/pay/compare/abbfcd78b9cefeefd57d95482ca2e7aa2d550364...8cbfa778612d125de42478faa9465c00dad4dd23","Len":1}...
|
1789717754
|
Edit
Delete
|
|
30895
|
9
|
5
|
10
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"8cbfa7786 {"Commits":[{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"}],"HeadCommit":{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},"CompareURL":"vodtest/pay/compare/abbfcd78b9cefeefd57d95482ca2e7aa2d550364...8cbfa778612d125de42478faa9465c00dad4dd23","Len":1}...
|
1789717754
|
Edit
Delete
|
|
30896
|
1
|
5
|
10
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"8cbfa7786 {"Commits":[{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"}],"HeadCommit":{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},"CompareURL":"vodtest/pay/compare/abbfcd78b9cefeefd57d95482ca2e7aa2d550364...8cbfa778612d125de42478faa9465c00dad4dd23","Len":1}...
|
1789717754
|
Edit
Delete
|
|
30897
|
3
|
5
|
10
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"8cbfa7786 {"Commits":[{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"}],"HeadCommit":{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},"CompareURL":"vodtest/pay/compare/abbfcd78b9cefeefd57d95482ca2e7aa2d550364...8cbfa778612d125de42478faa9465c00dad4dd23","Len":1}...
|
1789717754
|
Edit
Delete
|
|
30898
|
4
|
5
|
10
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"8cbfa7786 {"Commits":[{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"}],"HeadCommit":{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},"CompareURL":"vodtest/pay/compare/abbfcd78b9cefeefd57d95482ca2e7aa2d550364...8cbfa778612d125de42478faa9465c00dad4dd23","Len":1}...
|
1789717754
|
Edit
Delete
|
|
30899
|
7
|
5
|
10
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"8cbfa7786 {"Commits":[{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"}],"HeadCommit":{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},"CompareURL":"vodtest/pay/compare/abbfcd78b9cefeefd57d95482ca2e7aa2d550364...8cbfa778612d125de42478faa9465c00dad4dd23","Len":1}...
|
1789717754
|
Edit
Delete
|
|
30900
|
8
|
5
|
10
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"8cbfa7786 {"Commits":[{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"}],"HeadCommit":{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},"CompareURL":"vodtest/pay/compare/abbfcd78b9cefeefd57d95482ca2e7aa2d550364...8cbfa778612d125de42478faa9465c00dad4dd23","Len":1}...
|
1789717754
|
Edit
Delete
|
|
30901
|
11
|
5
|
10
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"8cbfa7786 {"Commits":[{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"}],"HeadCommit":{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},"CompareURL":"vodtest/pay/compare/abbfcd78b9cefeefd57d95482ca2e7aa2d550364...8cbfa778612d125de42478faa9465c00dad4dd23","Len":1}...
|
1789717754
|
Edit
Delete
|
|
30902
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"34c5fecec {"Commits":[{"Sha1":"34c5fecec1074d5a01acd8b184e70c63c5ed947b","Message":"feat(governance): 报告登记门禁补 R7 / R8——让它去读登记里早就写着的 binding 口径\n\n治理层是给全工作区定证据纪律的那一层，却没对自己的报告用同一条。登记表里每条 latest\n都写着 `\"binding\": \"clean-head\"`，note 也写着「只在 clean HEAD 上提交」，但 R1—R6 里\n没有任何一条去读它——R4 只查 provenance.gitSha 存不存在。\n\n于是 `基础目录统一审计.latest.json` 绑在 589467e 且 worktreeDirty=true（当时 9 个脏\n文件）被提交了，一路绿灯。一份绑在脏树上的报告证明不了任何一个提交态，它既不对应\n589467e 的树，也不对应此后任何提交。已于 ad86507 在干净树上重跑回绑。\n\n R7 BINDING_NOT_CLEAN 声明 clean-head 却自称绑在脏树上，且该报告本身已提交\n R8 BINDING_OFF_HISTORY 绑定的 SHA 不在当前 HEAD 的历史上（换基 / 重写历史后遗留）\n\n两条都只对**登记已声明绑定口径**的条目判——不替没声明的条目另立规矩。R7 跳过报告\n自身未提交的情况：那是在途产物，也可能是并行会话正在跑的中间态（本工作区常有 2—3\n个会话同时写 reports/），判红只会误伤对方的回绑，与真源仓偏差 #34-B 同一口径。\nR8 取不到祖先关系时整条不判，非 git 环境退回原判据。缺 gitSha 的报告由 R4 单独报，\n不叠加成三条。\n\n登记门禁测试 8 → 13，治理层全量 383（377 过 / 6 跳 / 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-18T00:49:24-07:00"},{"Sha1":"ad86507edf7f52241c3918e8c634b804e8b81b58","Message":"chore(reports): 治理层四份 latest 回绑 @ 44686cc\n\n`基础目录统一审计.latest.json` 此前绑在 589467e 且 worktreeDirty=true（当时 9 个脏\n文件）并被提交——登记里写着 binding=clean-head、note 也写着「只在 clean HEAD 上提交」，\n但没有任何检查去读，于是这份证明不了任何提交态的报告一直挂在顶层。\n\n`pnpm run audit` 一次编排写三份，加上它触发的 check-gate-consumption 共四份，本轮一并\n在干净树上重跑回绑（governanceProvenance 忽略 latest 报告自身，故并行会话在途的报告\n不影响绑定判定）。四份现均为 44686cc / dirty=false。\n\n结论未变：审计仍 BLOCKED（FACT_DECISIONS_PENDING_OR_UNKNOWN、\nASSET_EVIDENCE_REVIEW_REQUIRED），assets 去掉 ageHours 后逐字相同。\n\n另记一笔：`门禁消费.latest.json` 相对它自己的输入 `门禁消费登记.json` 已经陈旧——\n登记表里 C-13 / C-14 那段 2026-09-18 的文字早已提交，报告却停在旧文本，无人察觉。\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-18T00:47:30-07:00"}],"HeadCommit":{"Sha1":"34c5fecec1074d5a01acd8b184e70c63c5ed947b","Message":"feat(governance): 报告登记门禁补 R7 / R8——让它去读登记里早就写着的 binding 口径\n\n治理层是给全工作区定证据纪律的那一层，却没对自己的报告用同一条。登记表里每条 latest\n都写着 `\"binding\": \"clean-head\"`，note 也写着「只在 clean HEAD 上提交」，但 R1—R6 里\n没有任何一条去读它——R4 只查 provenance.gitSha 存不存在。\n\n于是 `基础目录统一审计.latest.json` 绑在 589467e 且 worktreeDirty=true（当时 9 个脏\n文件）被提交了，一路绿灯。一份绑在脏树上的报告证明不了任何一个提交态，它既不对应\n589467e 的树，也不对应此后任何提交。已于 ad86507 在干净树上重跑回绑。\n\n R7 BINDING_NOT_CLEAN 声明 clean-head 却自称绑在脏树上，且该报告本身已提交\n R8 BINDING_OFF_HISTORY 绑定的 SHA 不在当前 HEAD 的历史上（换基 / 重写历史后遗留）\n\n两条都只对**登记已声明绑定口径**的条目判——不替没声明的条目另立规矩。R7 跳过报告\n自身未提交的情况：那是在途产物，也可能是并行会话正在跑的中间态（本工作区常有 2—3\n个会话同时写 reports/），判红只会误伤对方的回绑，与真源仓偏差 #34-B 同一口径。\nR8 取不到祖先关系时整条不判，非 git 环境退回原判据。缺 gitSha 的报告由 R4 单独报，\n不叠加成三条。\n\n登记门禁测试 8 → 13，治理层全量 383（377 过 / 6 跳 / 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-18T00:49:24-07:00"},"CompareURL":"luoanwu/platform-governance/compare/44686cc39752ceb9b94fbfed9169b6fe0a2d6ea3...34c5fecec1074d5a01acd8b184e70c63c5ed947b","Len":2}...
|
1789717791
|
Edit
Delete
|
|
30903
|
1
|
5
|
1
|
32
|
0
|
0
|
refs/heads/master
|
1
|
{"Commits":[{"Sha1":"5cdc3d972 {"Commits":[{"Sha1":"5cdc3d972cb45c1157c30007fd2839ee432e3455","Message":"111\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:49:46+08:00"}],"HeadCommit":{"Sha1":"5cdc3d972cb45c1157c30007fd2839ee432e3455","Message":"111\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:49:46+08:00"},"CompareURL":"zhangjunnan/zhouhui/compare/af3b43796d8d81d8d606ba414acbf90a1a96004f...5cdc3d972cb45c1157c30007fd2839ee432e3455","Len":1}...
|
1789717791
|
Edit
Delete
|
|
30904
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"f4540e69b {"Commits":[{"Sha1":"f4540e69b1656232b677571584d3bd6ad57217be","Message":"docs(架构): 总架构增 §3.8——基座的装载 / 调用两个方向与接入能力归属\n\n起因是一次实际误读：`c433d57` 被当成「另一个 OS 产品」。它是数字员工OS 仓的提交\nSHA（2026-09-14），由 base-framework-os-product/os.upstream.json 连同 protocol\n1.3.0 钉住，用途是让「上游 OS 走动了」以 O0-SHA 显式变红。与基座并列的不是它，\n是 base-framework-os-product 这个仓——示例产品扩展加两道 OS 门禁，2026-09-10\n随 G26 自框架仓移出以保框架零依赖。误读本身说明这几件事在文档里没写清，本节补上。\n\n**两个方向。** PNG 给基座的定语「理解、编排、调用、执行」对应两个方向相反的接口：\n装载（OS → 应用）已有协议（KERNEL_EXTENSION_PROTOCOL_VERSION = 1.3.0，定义在 OS\n仓 packages/contracts/src/product-manifest.ts），真装 1 个；调用（应用 → OS）基本\n空白——协议草案 §4 已给出 ProductActivationIntent / ToolIntentReceipt 并写明「OS\n应提供、产品不再自建」，2026-09-18 复核 OS 仓 apps/ 下仍无 product-activations\n路由，智服已在自己仓内造了一套。两个方向归属不同，混谈会把落点找错。\n\n**接入形态实测已分叉成五种：** product.manifest.json（示例 / 设备云 / 知识云）、\nmanifest.json（HR，另有 ddl-authority / distribution / readiness 三个独有文件且无\npackage.json）、manifest.ts（工单，另有 kernel.products.entry.json）。只有示例与\n设备云带 os-host 测试配置。\n\n**为什么「每个应用继承一份」今天做不到**（两条方向相反的硬事实）：OS 的包是\n@repo/* 仓内作用域名（@repo/contracts@1.16.0，与工单仓同名包撞名），外仓依赖不了，\n只能照抄；而协议 §2.1 又反向禁止产品导入宿主私有 @repo/*，宿主能力一律由组合根\n注入、产品契约要自包含。由此划边界：可继承的是契约 / Schema / 校验器 / 门禁，不可\n继承的是宿主运行时——搞混会废掉 §2.1 的 fail-closed import 扫描。\n\n**四个落点按依赖方向逐个判定：** 协议与 SDK 由基座以 @juhai/ 发布（合法，阻碍是\n@repo/* 命名）；分发通道归基础设施（合法，DEC-031 已批准，缺口是契约包 pin 无门禁\n——HR 与 OS 停在 rc.1、源仓已 rc.3，不像 kernel 有 L12 守着）；脚手架归框架（合法\n但受零依赖限制，只能给目录形状）；**把装载协议搬进基础设施不合法**——基础设施要\n编码基座契约即反向依赖，撞图 1 的唯一硬约束。本节只判合法性，不选落点。\n\n另记一条门禁抓不到的过期陈述：协议草案 §4 写「DEC-006 / 007 pending 期间」，两条\n实际都已 approved；L10 只抓「等 / 待 / 尚未裁决」措辞，这句不在模式内。该文是\nDEC-009 材料，处置留给 OS Owner，本次未动。\n\n需走 DEC / CHG 的两件已列入 §9 不裁决清单：装载协议是否切出改名发布、走哪条通道、\n谁做 Owner；草案 §4 两个契约由基座实现的排期。\n\n门禁复跑：L3 / L4 / L10 / L13 均为 0，仍只剩既有的 L9；新增的两条跨层链接\n（os.upstream.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-18T00:54:12-07:00"}],"HeadCommit":{"Sha1":"f4540e69b1656232b677571584d3bd6ad57217be","Message":"docs(架构): 总架构增 §3.8——基座的装载 / 调用两个方向与接入能力归属\n\n起因是一次实际误读：`c433d57` 被当成「另一个 OS 产品」。它是数字员工OS 仓的提交\nSHA（2026-09-14），由 base-framework-os-product/os.upstream.json 连同 protocol\n1.3.0 钉住，用途是让「上游 OS 走动了」以 O0-SHA 显式变红。与基座并列的不是它，\n是 base-framework-os-product 这个仓——示例产品扩展加两道 OS 门禁，2026-09-10\n随 G26 自框架仓移出以保框架零依赖。误读本身说明这几件事在文档里没写清，本节补上。\n\n**两个方向。** PNG 给基座的定语「理解、编排、调用、执行」对应两个方向相反的接口：\n装载（OS → 应用）已有协议（KERNEL_EXTENSION_PROTOCOL_VERSION = 1.3.0，定义在 OS\n仓 packages/contracts/src/product-manifest.ts），真装 1 个；调用（应用 → OS）基本\n空白——协议草案 §4 已给出 ProductActivationIntent / ToolIntentReceipt 并写明「OS\n应提供、产品不再自建」，2026-09-18 复核 OS 仓 apps/ 下仍无 product-activations\n路由，智服已在自己仓内造了一套。两个方向归属不同，混谈会把落点找错。\n\n**接入形态实测已分叉成五种：** product.manifest.json（示例 / 设备云 / 知识云）、\nmanifest.json（HR，另有 ddl-authority / distribution / readiness 三个独有文件且无\npackage.json）、manifest.ts（工单，另有 kernel.products.entry.json）。只有示例与\n设备云带 os-host 测试配置。\n\n**为什么「每个应用继承一份」今天做不到**（两条方向相反的硬事实）：OS 的包是\n@repo/* 仓内作用域名（@repo/contracts@1.16.0，与工单仓同名包撞名），外仓依赖不了，\n只能照抄；而协议 §2.1 又反向禁止产品导入宿主私有 @repo/*，宿主能力一律由组合根\n注入、产品契约要自包含。由此划边界：可继承的是契约 / Schema / 校验器 / 门禁，不可\n继承的是宿主运行时——搞混会废掉 §2.1 的 fail-closed import 扫描。\n\n**四个落点按依赖方向逐个判定：** 协议与 SDK 由基座以 @juhai/ 发布（合法，阻碍是\n@repo/* 命名）；分发通道归基础设施（合法，DEC-031 已批准，缺口是契约包 pin 无门禁\n——HR 与 OS 停在 rc.1、源仓已 rc.3，不像 kernel 有 L12 守着）；脚手架归框架（合法\n但受零依赖限制，只能给目录形状）；**把装载协议搬进基础设施不合法**——基础设施要\n编码基座契约即反向依赖，撞图 1 的唯一硬约束。本节只判合法性，不选落点。\n\n另记一条门禁抓不到的过期陈述：协议草案 §4 写「DEC-006 / 007 pending 期间」，两条\n实际都已 approved；L10 只抓「等 / 待 / 尚未裁决」措辞，这句不在模式内。该文是\nDEC-009 材料，处置留给 OS Owner，本次未动。\n\n需走 DEC / CHG 的两件已列入 §9 不裁决清单：装载协议是否切出改名发布、走哪条通道、\n谁做 Owner；草案 §4 两个契约由基座实现的排期。\n\n门禁复跑：L3 / L4 / L10 / L13 均为 0，仍只剩既有的 L9；新增的两条跨层链接\n（os.upstream.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-18T00:54:12-07:00"},"CompareURL":"luoanwu/platform-governance/compare/34c5fecec1074d5a01acd8b184e70c63c5ed947b...f4540e69b1656232b677571584d3bd6ad57217be","Len":1}...
|
1789718060
|
Edit
Delete
|
|
30905
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ea965ed90 {"Commits":[{"Sha1":"ea965ed902a9807d07d7d89fc173668804c6294c","Message":"chore(reports): 内核准入门禁首轮 8 处诚实红 回绑 @ ee6d5a9\n\nclean 绑定（worktreeDirty:false）——工作区里三份 reports/ui-*.latest.json 的改动\n早于本批次，且 report-provenance 按设计忽略 latest 报告，不影响本次绑定。\n\nK4 七处（声明为 true，evidenceSources 无机器回执）：\n- kernel.digital-employee-core.industryIndependent ← 只有 scripts/check-kernel-boundaries.mjs\n- kernel.digital-employee-core.crossProductRequired ← 只有下游夹具 .ts\n- kernel.digital-employee-core.dualBackendGoverned ← 一份 ADR + 两个脚本\n- pack.generative-ai 的 industryIndependent / dualBackendGoverned ← 源码文件与目录\n- pack.enterprise-fact-consumer 的两项同上\n\nK3 一处：tests/kernel-downstream-fixture/src/index.ts 只有命名空间导入。\n\n未一并修 evidenceSources。改指某份已存在的报告能立刻转绿，但只有当那份报告确实判过\n该条时才是真修：dual-backend-parity 是全仓级判定、不按组件出结论，改指它等于把自证\n换个地方做。哪份报告承接哪一条属 Owner 裁定，不随本次实现一并决定。\n\nK5 观测（不计红）：跨产品具名消费面 5 个符号——ProductManifestInput、\nProductManifestComposition、ProductRuntimeContractCatalog、\nProductDataContractImplementation、ProductEventContractImplementation，\n全部来自 product-manifest.ts；33/38 个模块零跨产品消费，含 tenant.ts 的 65 个导出与\ntool.ts 的 99 个。该数字只作边界收缩决策的输入，不构成「应移出 CORE」的判定。\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-18T00:52:16-07:00"},{"Sha1":"ee6d5a98aa6d372d2fc2ea81f328d55cc15511f9","Message":"feat(governance): 内核准入证据门禁 K1—K5，判据从声明下沉到导出清单与证据形态\n\nkernel.boundaries.json 的 admissionEvidence 是四个手写 true，evidenceSources\n只列了路径，没有「该判据确实被机器判过」的回执。实测两处后果：\n\n- CORE 声明 crossProductRequired: true，其证据源 tests/kernel-downstream-fixture/\n src/index.ts 是 10 个 import * as + 判非空 + 一个 typeof === \"function\" 的\n 命名空间冒烟测试——28 个契约模块全空它也照样通过。它能证明包可安装可加载，\n 不能证明任何一个模块跨产品必需\n- 归属粒度是文件：owns.contractModules 是文件名清单，于是\n packages/contracts/src/tenant.ts 一个 1075 行 / 65 导出的文件，把租户策略、\n JWT 验签、自建权限、work 域业务判定四类一起带进了 CORE\n\n手法同 check:platform-provenance（那一条把判据从 package.json 的声明下沉到\npnpm-lock.yaml 的解析结果）。五条判据：\n\n K1 EXPORT_LOCK_DRIFT 组件所辖契约模块的直接导出集合须与\n kernel.exports.lock.json 一致。只认直接声明，\n barrel 的再导出不算拥有——否则 index.ts 会「拥有」全仓\n K2 EXPORT_OWNERSHIP_AMBIGUOUS 同一导出名不得被两个组件同时拥有。拆分契约模块时\n 最容易「复制一份留在原处」，这条守住它\n K3 EVIDENCE_NAMESPACE_ONLY crossProductRequired 的证据源若只有命名空间导入、\n 无任何具名导入，按构造无法证明符号级必需性\n K4 EVIDENCE_NOT_BACKED 声明为 true 的每项须至少有一份机器回执\n （reports/*.json 或 *.lock.json）。脚本路径与文档路径\n 不是回执：只证明文件存在，不证明该判据被判过。\n 声明为 false 的项不要求回执\n K5 CROSS_PRODUCT_UNCONSUMED observed，不计红。CORE 模块未被产品消费不等于不该在\n CORE（OS 自己的两个后端在用）；把观测项当红盘会逼出\n 「为了绿而乱改归属」的反向激励\n\n自检 pnpm check:kernel-admission:self-test 共 10 条，含 1 条基线正例与 2 条防过度\n判红（声明 false 不因无回执计红、零跨产品消费只出 observed）——对照组是为了防\n「只会红的假门禁」。\n\n锁基线 38 个模块 / 779 个导出（CORE 30 + generative-ai 7 + fact-consumer 1）。\n首次签发只固化「现在是什么」，不代表归属正确。\n\ncheck-all 末位注册，理由同 check:platform-provenance：本门禁自引入起即为已知诚实红，\nfail-fast 语义下排前面会让其余门禁全部不执行。pnpm check 因此从 27 步变 28 步且末步红，\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-18T00:52:01-07:00"}],"HeadCommit":{"Sha1":"ea965ed902a9807d07d7d89fc173668804c6294c","Message":"chore(reports): 内核准入门禁首轮 8 处诚实红 回绑 @ ee6d5a9\n\nclean 绑定（worktreeDirty:false）——工作区里三份 reports/ui-*.latest.json 的改动\n早于本批次，且 report-provenance 按设计忽略 latest 报告，不影响本次绑定。\n\nK4 七处（声明为 true，evidenceSources 无机器回执）：\n- kernel.digital-employee-core.industryIndependent ← 只有 scripts/check-kernel-boundaries.mjs\n- kernel.digital-employee-core.crossProductRequired ← 只有下游夹具 .ts\n- kernel.digital-employee-core.dualBackendGoverned ← 一份 ADR + 两个脚本\n- pack.generative-ai 的 industryIndependent / dualBackendGoverned ← 源码文件与目录\n- pack.enterprise-fact-consumer 的两项同上\n\nK3 一处：tests/kernel-downstream-fixture/src/index.ts 只有命名空间导入。\n\n未一并修 evidenceSources。改指某份已存在的报告能立刻转绿，但只有当那份报告确实判过\n该条时才是真修：dual-backend-parity 是全仓级判定、不按组件出结论，改指它等于把自证\n换个地方做。哪份报告承接哪一条属 Owner 裁定，不随本次实现一并决定。\n\nK5 观测（不计红）：跨产品具名消费面 5 个符号——ProductManifestInput、\nProductManifestComposition、ProductRuntimeContractCatalog、\nProductDataContractImplementation、ProductEventContractImplementation，\n全部来自 product-manifest.ts；33/38 个模块零跨产品消费，含 tenant.ts 的 65 个导出与\ntool.ts 的 99 个。该数字只作边界收缩决策的输入，不构成「应移出 CORE」的判定。\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-18T00:52:16-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/c433d57b4aae2249bd19a085d1c520bf6baedf55...ea965ed902a9807d07d7d89fc173668804c6294c","Len":2}...
|
1789718112
|
Edit
Delete
|
|
30906
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6fb129d40 {"Commits":[{"Sha1":"6fb129d40fb9e160af6f70871eb8881ff5eef743","Message":"chore(reports): 门禁消费回绑 @ 69784be\n\nR9 落地后第一条真实命中：69784be 改了 scripts/ 下两个文件，而 scripts/ 正是这份报告\n声明的输入之一（它拿 门禁消费登记.json 对盘受控脚本，读的是脚本内容不只是文件名）。\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-18T00:55:46-07:00"},{"Sha1":"69784be6b04c850ae1f2ea0b948344f9627738cf","Message":"feat(governance): 报告登记门禁补 R9 / R10——绑定干净不等于结论还成立\n\nR7 / R8 守的是绑定本身（不脏、在历史上）。这一轮补另一半：**一份绑得干干净净的报告，\n结论仍可能早已被推翻**。2026-09-18 实测 `门禁消费.latest.json` 相对它自己的输入\n`门禁消费登记.json` 已经陈旧——登记表改了并提交了，报告停在旧文本，R1—R8 一条都不响。\n\n R9 LATEST_STALE 登记声明了 inputs，绑定 SHA → HEAD 之间这些输入有变更\n R10 INPUTS_UNACCOUNTED latest 既没声明 inputs、也没写明为什么判不了\n\n判据与真源仓 check:evidence 同口径：不看「落后几个提交」，看**该报告自己覆盖的输入**\n动没动。同目录的 latest 报告不算输入，它们是产物。\n\n四份 latest 逐条给出口径，禁止留空白：\n 门禁消费 inputs：门禁消费登记.json + scripts/（它正是拿登记表对盘受控脚本）\n 基础目录统一审计 判不了——读其它仓的 HEAD / 工作树 / 验收报告，全在治理仓历史之外，\n 且 ageHours 每跑一次都变，本仓任何提交都决定不了它是否仍成立\n 延后op 判不了一半——决议材料在本仓，活跃 Catalog 在嵌套独立仓（治理仓忽略该\n 目录，git diff 看不见）。只声明能判的一半会给出假绿，比不判更坏\n 门禁运行 判不了——编排产物，写 inputs 只能写成 scripts/ 这种筐，真源仓\n evidence-scopes 的同一条纪律禁止为覆盖率造模糊作用域\n\n集成用例改为只在真实登记上断言**结构类**规则。仓纪律 5 要求两次提交（实现，然后在它\n的干净树上回绑），必然存在一个提交报告是陈旧的——那是纪律规定的流程，不是缺陷；在\n单测里断言它为零等于让 pnpm test 在自家流程的中间一步必红。「待回绑」四条由阻断性\n门禁 check:reports 把关。该用例原本就已按同一理由排除 LATEST_WITHOUT_PROVENANCE，\n本轮只是把这一类补全。\n\n登记门禁测试 13 → 19，治理层全量 389（383 过 / 6 跳 / 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-18T00:55:24-07:00"}],"HeadCommit":{"Sha1":"6fb129d40fb9e160af6f70871eb8881ff5eef743","Message":"chore(reports): 门禁消费回绑 @ 69784be\n\nR9 落地后第一条真实命中：69784be 改了 scripts/ 下两个文件，而 scripts/ 正是这份报告\n声明的输入之一（它拿 门禁消费登记.json 对盘受控脚本，读的是脚本内容不只是文件名）。\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-18T00:55:46-07:00"},"CompareURL":"luoanwu/platform-governance/compare/f4540e69b1656232b677571584d3bd6ad57217be...6fb129d40fb9e160af6f70871eb8881ff5eef743","Len":2}...
|
1789718149
|
Edit
Delete
|
|
30907
|
1
|
7
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718159
|
Edit
Delete
|
|
30908
|
9
|
7
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718159
|
Edit
Delete
|
|
30909
|
3
|
7
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718159
|
Edit
Delete
|
|
30910
|
4
|
7
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718159
|
Edit
Delete
|
|
30911
|
7
|
7
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718159
|
Edit
Delete
|
|
30912
|
8
|
7
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718159
|
Edit
Delete
|
|
30913
|
10
|
7
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718159
|
Edit
Delete
|
|
30914
|
11
|
7
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718159
|
Edit
Delete
|
|
30915
|
1
|
11
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718168
|
Edit
Delete
|
|
30916
|
9
|
11
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718168
|
Edit
Delete
|
|
30917
|
3
|
11
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718168
|
Edit
Delete
|
|
30918
|
4
|
11
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718168
|
Edit
Delete
|
|
30919
|
7
|
11
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718168
|
Edit
Delete
|
|
30920
|
8
|
11
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718168
|
Edit
Delete
|
|
30921
|
10
|
11
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718168
|
Edit
Delete
|
|
30922
|
11
|
11
|
1
|
21
|
0
|
0
|
|
0
|
339|需求 麦霸直播间不判断配置
|
1789718168
|
Edit
Delete
|
|
30923
|
1
|
5
|
1
|
21
|
0
|
0
|
refs/heads/pay
|
0
|
{"Commits":[{"Sha1":"c7a2cce63 {"Commits":[{"Sha1":"c7a2cce630214b956a213c074cdadefd93c15f49","Message":"Merge pull request '需求 麦霸直播间不判断配置' (#339) from pay-260915 into pay\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pay/pulls/339\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:56:05+08:00"},{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"},{"Sha1":"d17e203a06df00db27d10bdcc11393d2114e3a1a","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:05:23+08:00"},{"Sha1":"94a6e44e5a10dc0fe4428fd5baf9337298a01a3f","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T14:24:09+08:00"}],"HeadCommit":{"Sha1":"c7a2cce630214b956a213c074cdadefd93c15f49","Message":"Merge pull request '需求 麦霸直播间不判断配置' (#339) from pay-260915 into pay\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pay/pulls/339\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:56:05+08:00"},"CompareURL":"vodtest/pay/compare/c79d1363141bc69c3ee7eb13efd73b627239806b...c7a2cce630214b956a213c074cdadefd93c15f49","Len":160}...
|
1789718168
|
Edit
Delete
|
|
30924
|
9
|
5
|
1
|
21
|
0
|
0
|
refs/heads/pay
|
0
|
{"Commits":[{"Sha1":"c7a2cce63 {"Commits":[{"Sha1":"c7a2cce630214b956a213c074cdadefd93c15f49","Message":"Merge pull request '需求 麦霸直播间不判断配置' (#339) from pay-260915 into pay\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pay/pulls/339\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:56:05+08:00"},{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"},{"Sha1":"d17e203a06df00db27d10bdcc11393d2114e3a1a","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:05:23+08:00"},{"Sha1":"94a6e44e5a10dc0fe4428fd5baf9337298a01a3f","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T14:24:09+08:00"}],"HeadCommit":{"Sha1":"c7a2cce630214b956a213c074cdadefd93c15f49","Message":"Merge pull request '需求 麦霸直播间不判断配置' (#339) from pay-260915 into pay\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pay/pulls/339\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:56:05+08:00"},"CompareURL":"vodtest/pay/compare/c79d1363141bc69c3ee7eb13efd73b627239806b...c7a2cce630214b956a213c074cdadefd93c15f49","Len":160}...
|
1789718168
|
Edit
Delete
|
|
30925
|
3
|
5
|
1
|
21
|
0
|
0
|
refs/heads/pay
|
0
|
{"Commits":[{"Sha1":"c7a2cce63 {"Commits":[{"Sha1":"c7a2cce630214b956a213c074cdadefd93c15f49","Message":"Merge pull request '需求 麦霸直播间不判断配置' (#339) from pay-260915 into pay\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pay/pulls/339\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:56:05+08:00"},{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"},{"Sha1":"d17e203a06df00db27d10bdcc11393d2114e3a1a","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:05:23+08:00"},{"Sha1":"94a6e44e5a10dc0fe4428fd5baf9337298a01a3f","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T14:24:09+08:00"}],"HeadCommit":{"Sha1":"c7a2cce630214b956a213c074cdadefd93c15f49","Message":"Merge pull request '需求 麦霸直播间不判断配置' (#339) from pay-260915 into pay\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pay/pulls/339\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:56:05+08:00"},"CompareURL":"vodtest/pay/compare/c79d1363141bc69c3ee7eb13efd73b627239806b...c7a2cce630214b956a213c074cdadefd93c15f49","Len":160}...
|
1789718168
|
Edit
Delete
|
|
30926
|
4
|
5
|
1
|
21
|
0
|
0
|
refs/heads/pay
|
0
|
{"Commits":[{"Sha1":"c7a2cce63 {"Commits":[{"Sha1":"c7a2cce630214b956a213c074cdadefd93c15f49","Message":"Merge pull request '需求 麦霸直播间不判断配置' (#339) from pay-260915 into pay\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pay/pulls/339\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:56:05+08:00"},{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"},{"Sha1":"d17e203a06df00db27d10bdcc11393d2114e3a1a","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:05:23+08:00"},{"Sha1":"94a6e44e5a10dc0fe4428fd5baf9337298a01a3f","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T14:24:09+08:00"}],"HeadCommit":{"Sha1":"c7a2cce630214b956a213c074cdadefd93c15f49","Message":"Merge pull request '需求 麦霸直播间不判断配置' (#339) from pay-260915 into pay\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pay/pulls/339\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:56:05+08:00"},"CompareURL":"vodtest/pay/compare/c79d1363141bc69c3ee7eb13efd73b627239806b...c7a2cce630214b956a213c074cdadefd93c15f49","Len":160}...
|
1789718168
|
Edit
Delete
|
|
30927
|
7
|
5
|
1
|
21
|
0
|
0
|
refs/heads/pay
|
0
|
{"Commits":[{"Sha1":"c7a2cce63 {"Commits":[{"Sha1":"c7a2cce630214b956a213c074cdadefd93c15f49","Message":"Merge pull request '需求 麦霸直播间不判断配置' (#339) from pay-260915 into pay\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pay/pulls/339\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:56:05+08:00"},{"Sha1":"8cbfa778612d125de42478faa9465c00dad4dd23","Message":"团购券预订退款-取消核销\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-09-18T15:49:04+08:00"},{"Sha1":"abbfcd78b9cefeefd57d95482ca2e7aa2d550364","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:15:54+08:00"},{"Sha1":"d17e203a06df00db27d10bdcc11393d2114e3a1a","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T15:05:23+08:00"},{"Sha1":"94a6e44e5a10dc0fe4428fd5baf9337298a01a3f","Message":"1\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T14:24:09+08:00"}],"HeadCommit":{"Sha1":"c7a2cce630214b956a213c074cdadefd93c15f49","Message":"Merge pull request '需求 麦霸直播间不判断配置' (#339) from pay-260915 into pay\n\nReviewed-on: https://gitea.g-hi.com/vodtest/pay/pulls/339\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-18T15:56:05+08:00"},"CompareURL":"vodtest/pay/compare/c79d1363141bc69c3ee7eb13efd73b627239806b...c7a2cce630214b956a213c074cdadefd93c15f49","Len":160}...
|
1789718168
|
Edit
Delete
|