|
30703
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ce042782a {"Commits":[{"Sha1":"ce042782a285d1d8a79e5c5a43636ea05f4868d3","Message":"feat(governance): 新增 check-deferred-ops 门禁——变更包延后 op 与活跃 Catalog 对账，并收口两条实际存在的坑\n\n起因：CHG-003 与 CHG-006 对同一条目同一字段（application-contract-registry.code_truth）各留一条 applyAfter op 且目标值不同，后者已由 CHG-013 于 2026-09-16 应用；delta 文件之间从不互相校验，谁按「把剩余延后 op 补完」执行，就会把已生效值回归成更粗的路径，且没有任何门禁会红。\n\n门禁（D1—D6，阻断性，进 run-foundation-gates）把每条 op 按 aspect（set 逐字段 + add_evidence 子集）与活跃 Catalog 对账：全部生效须登记 appliedBy、半生效须用 appliedBy.aspects 写明已落的一半、被取代须登记 withdrawn（缺 reason/authority/recordedAt 即红）、凭声明当已应用即红。11 例单测含逐规则负向；IO 层在真实材料与真实 Catalog 上跑。负向实测：去掉 withdrawn 即 exit 1。\n\n随之收口三处：\n- CHG-003 注册中心那条登记 withdrawn（依据决策批次 A-2 附条件），enterprise-idp 那条登记 appliedBy.aspects=[\"code_truth\"]——它是半应用，set 由 PF-07 阶段 1 实现提交 99c3f52（2026-09-12）直接改到位、三条 add_evidence 从未落；CHG-006 那条登记 appliedBy（CHG-013）。\n- check-new-platform-catalog-change-readiness 的 expectedFormalWithdrawn 收窄：原先连 decisions 总数与 pendingDecisions 一起钉死，而那两个数不是「撤销」决定的——CHG-002 按 A-2 登记 DEC-037—039 为 pending 后（36→39 / 0→3）该门禁与撤销无关地恒红。改为只断言撤销真正决定的项目数（21 / 19），四项不在册与四条 DEC rejected 由原有两个循环逐项断言（比总数更强）。八条自带负向用例仍全绿。\n- simulate-chg-007 在包已应用后不再因 tests.delta 锚点漂移崩溃，如实报 status=already-applied（formalMutated 仍 false）；护栏的冻结基线判定从钉死整行改为只认函数调用（004/005 加 --contracts=active 后那一行变成三元表达式，被误判成活跃基线）。\n\n治理层 365 例 358 通过，余 1 为报告登记数待本次报告入 git；阻断性门禁 10/10。开发计划 §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-17T16:14:54-07:00"},{"Sha1":"001e9af9cc570b2adb4ccdec0df1277d9b243730","Message":"docs(计划): PF-03 ⑤ 部分收口，偏差 #11 关闭（真源仓 41ca988）\n\n- §3 PF-03 行：⑤ 由「未做」改为「部分收口」，余项明确为 README 与\n CHANGELOG（后者自称「基础框架的版本轴」），退出条件改为三份文档正文\n 均不含框架仓状态声明\n- §6：偏差 #11 移入已关闭一行，附回灌内容与两道门禁结果\n- §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-17T16:14:50-07:00"}],"HeadCommit":{"Sha1":"ce042782a285d1d8a79e5c5a43636ea05f4868d3","Message":"feat(governance): 新增 check-deferred-ops 门禁——变更包延后 op 与活跃 Catalog 对账，并收口两条实际存在的坑\n\n起因：CHG-003 与 CHG-006 对同一条目同一字段（application-contract-registry.code_truth）各留一条 applyAfter op 且目标值不同，后者已由 CHG-013 于 2026-09-16 应用；delta 文件之间从不互相校验，谁按「把剩余延后 op 补完」执行，就会把已生效值回归成更粗的路径，且没有任何门禁会红。\n\n门禁（D1—D6，阻断性，进 run-foundation-gates）把每条 op 按 aspect（set 逐字段 + add_evidence 子集）与活跃 Catalog 对账：全部生效须登记 appliedBy、半生效须用 appliedBy.aspects 写明已落的一半、被取代须登记 withdrawn（缺 reason/authority/recordedAt 即红）、凭声明当已应用即红。11 例单测含逐规则负向；IO 层在真实材料与真实 Catalog 上跑。负向实测：去掉 withdrawn 即 exit 1。\n\n随之收口三处：\n- CHG-003 注册中心那条登记 withdrawn（依据决策批次 A-2 附条件），enterprise-idp 那条登记 appliedBy.aspects=[\"code_truth\"]——它是半应用，set 由 PF-07 阶段 1 实现提交 99c3f52（2026-09-12）直接改到位、三条 add_evidence 从未落；CHG-006 那条登记 appliedBy（CHG-013）。\n- check-new-platform-catalog-change-readiness 的 expectedFormalWithdrawn 收窄：原先连 decisions 总数与 pendingDecisions 一起钉死，而那两个数不是「撤销」决定的——CHG-002 按 A-2 登记 DEC-037—039 为 pending 后（36→39 / 0→3）该门禁与撤销无关地恒红。改为只断言撤销真正决定的项目数（21 / 19），四项不在册与四条 DEC rejected 由原有两个循环逐项断言（比总数更强）。八条自带负向用例仍全绿。\n- simulate-chg-007 在包已应用后不再因 tests.delta 锚点漂移崩溃，如实报 status=already-applied（formalMutated 仍 false）；护栏的冻结基线判定从钉死整行改为只认函数调用（004/005 加 --contracts=active 后那一行变成三元表达式，被误判成活跃基线）。\n\n治理层 365 例 358 通过，余 1 为报告登记数待本次报告入 git；阻断性门禁 10/10。开发计划 §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-17T16:14:54-07:00"},"CompareURL":"luoanwu/platform-governance/compare/589467ea0debc370a8800dc05cd744af7360cbbd...ce042782a285d1d8a79e5c5a43636ea05f4868d3","Len":2}...
|
1789686899
|
Edit
Delete
|
|
30704
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"460cfe907 {"Commits":[{"Sha1":"460cfe907dba69936a3bec815b177f2f96ba8790","Message":"feat(runtime): WB-1 工作台脚手架——runtime/apps/workbench 纯静态 SPA 与四页只读面\n\n按 CHG-018 §5.1 已裁技术栈建独立应用：Next.js output=export + React + TypeScript，\n无 SSR / API routes / middleware，产物 out/ 由 Caddy 托管（入口鉴权与部署注入属 SRE，未做）。\n\n- 四页：总览（运行时装配事实）、服务目录（构建期快照）、只读运行信息（模块与 health 探针）、登录（OIDC 公开客户端 Authorization Code + PKCE，带 state / nonce，令牌只入 sessionStorage 且只走 Authorization 头）\n- StateBlock 把缺接口 / 缺凭证 / 缺权限 / 依赖故障 / 响应不可解析 / 空数据分别成状态显示，不以模拟数据或空成功掩盖（§5.2）\n- 不静态 import 任何 @juhai/module-*，只经公开 HTTP 只读面取数；catalog / modules 响应形状在 features/platform/types.ts 作浏览器侧镜像并注明真源文件\n- 目录快照经 scripts/copy-snapshots.mjs 于构建期复制为静态资产；缺快照时页面显示「未随构建附带」而非空目录\n- 环境列固定 unknown、装载成功不渲染为健康、空 health 明示不等于业务健康\n- check:fork-readiness 的 F7 / F9 忽略表补 out（静态导出产物，与 dist / .next 同类）——本仓首个静态导出应用暴露的缺口\n\n本机验收（dev 服务 :3010，API 指向容器 127.0.0.1:53001）：服务目录页渲染真实快照 21 条目、\n快照来源显示绑定 6378b6f；总览与运行信息页因跨源被拦，如实显示依赖故障；登录页显示缺配置。\nruntime 静态门禁 31 项通过（含 workbench typecheck / lint）；check:naming、check:module-imports、\ncheck:fork-readiness 通过。目标环境验收未做：运行容器源码为 19150ae，早于目录读面与 OPS-1，\n/api/platform/catalog 与 /api/platform/ops/definitions 实测 404。\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-17T16:14:34-07:00"},{"Sha1":"41ca98813d6661f799d6cd4f8674fbc265a5cf6c","Message":"docs(runtime): PF-03 ⑤ 回灌——GOVERNANCE-BASELINE 表与发布快照不再冒充框架仓事实\n\n偏差 #11：runtime/CLAUDE.md 的动态区「证据新鲜度」已回灌为本仓事实（652 /\n7e26a50 / 2026-09-13），其下的 GOVERNANCE-BASELINE 表却仍写着框架仓的\n288 tests @ 17b8276 与 4 组合 UI，同一文件里两份真源打架——而该文件自己\n规定「判定治理状态只认动态区 + reports」。\n\n四行按 runtime-acceptance / ui-acceptance 两份报告回灌：\n\n- runtime-acceptance：288 @ 17b8276 → 652 @ 7e26a50，证据描述改本仓底座\n （PG :55471 / Redis :56380/7 / Redpanda :59093 + platform_identity_test）\n- tests-passing：288 → 652，地板改指 reports/baseline.json\n- tenant-rls：clean SHA 17b8276 → 7e26a50，去掉框架的「两后端各 6 例」\n- ui-acceptance：4 组合 × 11 用例 → 1 组合（nestjs × ws）5 用例，地板 11 → 5\n\n「发布状态快照」一段描述的是框架仓 base-framework 的两个远端与 CI run，\n随 scaffold 带入本仓，在此读起来像本仓状态：加归属标注并指向开发计划 §1\n仓与远端行，保留原文作版本轴溯源，不删。\n\ncheck:docs-truth 通过（动态区两行 SHA 断言未受影响）、check:governance-docs\n通过（AGENTS.md 符号链接一致）。\n\n报告未回绑：工作区有并行会话在途的 pnpm-lock / check-fork-readiness /\napps/workbench，拿不到干净树。作用域内四份报告（docs-truth、governance-docs、\nagent-adapters、dual-backend-parity，均 warn 级）待干净树的 chore(reports)。\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-17T16:14:02-07:00"}],"HeadCommit":{"Sha1":"460cfe907dba69936a3bec815b177f2f96ba8790","Message":"feat(runtime): WB-1 工作台脚手架——runtime/apps/workbench 纯静态 SPA 与四页只读面\n\n按 CHG-018 §5.1 已裁技术栈建独立应用：Next.js output=export + React + TypeScript，\n无 SSR / API routes / middleware，产物 out/ 由 Caddy 托管（入口鉴权与部署注入属 SRE，未做）。\n\n- 四页：总览（运行时装配事实）、服务目录（构建期快照）、只读运行信息（模块与 health 探针）、登录（OIDC 公开客户端 Authorization Code + PKCE，带 state / nonce，令牌只入 sessionStorage 且只走 Authorization 头）\n- StateBlock 把缺接口 / 缺凭证 / 缺权限 / 依赖故障 / 响应不可解析 / 空数据分别成状态显示，不以模拟数据或空成功掩盖（§5.2）\n- 不静态 import 任何 @juhai/module-*，只经公开 HTTP 只读面取数；catalog / modules 响应形状在 features/platform/types.ts 作浏览器侧镜像并注明真源文件\n- 目录快照经 scripts/copy-snapshots.mjs 于构建期复制为静态资产；缺快照时页面显示「未随构建附带」而非空目录\n- 环境列固定 unknown、装载成功不渲染为健康、空 health 明示不等于业务健康\n- check:fork-readiness 的 F7 / F9 忽略表补 out（静态导出产物，与 dist / .next 同类）——本仓首个静态导出应用暴露的缺口\n\n本机验收（dev 服务 :3010，API 指向容器 127.0.0.1:53001）：服务目录页渲染真实快照 21 条目、\n快照来源显示绑定 6378b6f；总览与运行信息页因跨源被拦，如实显示依赖故障；登录页显示缺配置。\nruntime 静态门禁 31 项通过（含 workbench typecheck / lint）；check:naming、check:module-imports、\ncheck:fork-readiness 通过。目标环境验收未做：运行容器源码为 19150ae，早于目录读面与 OPS-1，\n/api/platform/catalog 与 /api/platform/ops/definitions 实测 404。\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-17T16:14:34-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/361a0e418fa5c6c648f95625c7829a0c46a76cde...460cfe907dba69936a3bec815b177f2f96ba8790","Len":2}...
|
1789686902
|
Edit
Delete
|
|
30705
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"9a111b33b {"Commits":[{"Sha1":"9a111b33be8f5471c74e5c9310cb8acdc8fbdeb1","Message":"chore(reports): WB-1 脚手架后门禁回绑 @ 460cfe9\n\n仓根 pnpm check 在 clean 树上退出码 0：pins / modules / module-imports（409 源文件 0 跨模块 import）/\ncatalog / drift / fixtures 17 套件 189 例 / facts / migration-decs / caddy / otel / governance 265 测试 0 失败 /\ncontracts check:local / runtime 静态门禁 31 项（含 workbench typecheck 与 lint）/ evidence。\n\ncheck:evidence 仍 partial：36 份登记中 26 新鲜、9 过期、1 例外。9 份过期全部是需真实环境的验收类报告\n（port-conformance / runtime-acceptance / ui-acceptance / revocation-sla / mainline-acceptance /\nidentity-http / identity-ui / mainline-restore / mainline-candidate-regression），与本次新增前端无关。\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-17T16:15:35-07:00"}],"HeadCommit":{"Sha1":"9a111b33be8f5471c74e5c9310cb8acdc8fbdeb1","Message":"chore(reports): WB-1 脚手架后门禁回绑 @ 460cfe9\n\n仓根 pnpm check 在 clean 树上退出码 0：pins / modules / module-imports（409 源文件 0 跨模块 import）/\ncatalog / drift / fixtures 17 套件 189 例 / facts / migration-decs / caddy / otel / governance 265 测试 0 失败 /\ncontracts check:local / runtime 静态门禁 31 项（含 workbench typecheck 与 lint）/ evidence。\n\ncheck:evidence 仍 partial：36 份登记中 26 新鲜、9 过期、1 例外。9 份过期全部是需真实环境的验收类报告\n（port-conformance / runtime-acceptance / ui-acceptance / revocation-sla / mainline-acceptance /\nidentity-http / identity-ui / mainline-restore / mainline-candidate-regression），与本次新增前端无关。\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-17T16:15:35-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/460cfe907dba69936a3bec815b177f2f96ba8790...9a111b33be8f5471c74e5c9310cb8acdc8fbdeb1","Len":1}...
|
1789686947
|
Edit
Delete
|
|
30706
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"8dae61f91 {"Commits":[{"Sha1":"8dae61f91b56f708b1c76e66f07d98efa4828a36","Message":"docs(runtime): WB-1 工作台脚手架实现记录——本机验收范围、口径落点与未做项归属\n\n明确本记录不构成阶段 ② 验收：Caddy 托管 / 入口鉴权 / 快照与 PLATFORM_OPS_* 进部署 / 镜像注入\nPLATFORM_SOURCE_SHA / 目标环境四页验收 / 工作台制品入 Manifest 均未做，逐项标注归属。\n记录部署侧既知阻碍：容器镜像源码 19150ae 早于 8ced3d1 与 6378b6f，catalog 与 ops/definitions 实测 404。\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-17T16:16:11-07:00"}],"HeadCommit":{"Sha1":"8dae61f91b56f708b1c76e66f07d98efa4828a36","Message":"docs(runtime): WB-1 工作台脚手架实现记录——本机验收范围、口径落点与未做项归属\n\n明确本记录不构成阶段 ② 验收：Caddy 托管 / 入口鉴权 / 快照与 PLATFORM_OPS_* 进部署 / 镜像注入\nPLATFORM_SOURCE_SHA / 目标环境四页验收 / 工作台制品入 Manifest 均未做，逐项标注归属。\n记录部署侧既知阻碍：容器镜像源码 19150ae 早于 8ced3d1 与 6378b6f，catalog 与 ops/definitions 实测 404。\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-17T16:16:11-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/9a111b33be8f5471c74e5c9310cb8acdc8fbdeb1...8dae61f91b56f708b1c76e66f07d98efa4828a36","Len":1}...
|
1789686980
|
Edit
Delete
|
|
30707
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"06cdd6f0f {"Commits":[{"Sha1":"06cdd6f0fdfa799a55c0c78b11bdcb0601bcb0e7","Message":"chore(reports): 延后op 报告回绑 @ ce04278\n\n上一条提交里的报告绑的是其父提交；重跑后绑到真正包含 check-deferred-ops 的提交。8 条延后 op（已登记生效 2、已撤销 1）0 违规。\n\nworktreeDirty 仍为 true 且如实记录：工作树里有并行会话的在途文件（开发计划.md、workspace-consistency.test.mjs 与三份门禁运行产物），本会话无法在 clean 树上取证，故该报告只绑定本地工作区，不作为「clean HEAD 证据」引用。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:16:31-07:00"}],"HeadCommit":{"Sha1":"06cdd6f0fdfa799a55c0c78b11bdcb0601bcb0e7","Message":"chore(reports): 延后op 报告回绑 @ ce04278\n\n上一条提交里的报告绑的是其父提交；重跑后绑到真正包含 check-deferred-ops 的提交。8 条延后 op（已登记生效 2、已撤销 1）0 违规。\n\nworktreeDirty 仍为 true 且如实记录：工作树里有并行会话的在途文件（开发计划.md、workspace-consistency.test.mjs 与三份门禁运行产物），本会话无法在 clean 树上取证，故该报告只绑定本地工作区，不作为「clean HEAD 证据」引用。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:16:31-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ce042782a285d1d8a79e5c5a43636ea05f4868d3...06cdd6f0fdfa799a55c0c78b11bdcb0601bcb0e7","Len":1}...
|
1789686993
|
Edit
Delete
|
|
30708
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"22f145c7c {"Commits":[{"Sha1":"22f145c7cc1d26ac35b6ce4781f2c36621c17de7","Message":"chore(reports): 门禁运行 / 门禁消费 / 统一审计 / 延后op 回绑 @ 06cdd6f（clean 树）\n\n并行会话的在途文件落地后工作树转干净（非报告类脏文件 0），重跑取 clean 绑定：阻断性门禁 10/10 通过（含新增 check-deferred-ops），仅记录 3 道（workspace-consistency 3 条既有 + domain-layer 13 条，均不参与总账）；延后op 8 条 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-17T16:17:04-07:00"}],"HeadCommit":{"Sha1":"22f145c7cc1d26ac35b6ce4781f2c36621c17de7","Message":"chore(reports): 门禁运行 / 门禁消费 / 统一审计 / 延后op 回绑 @ 06cdd6f（clean 树）\n\n并行会话的在途文件落地后工作树转干净（非报告类脏文件 0），重跑取 clean 绑定：阻断性门禁 10/10 通过（含新增 check-deferred-ops），仅记录 3 道（workspace-consistency 3 条既有 + domain-layer 13 条，均不参与总账）；延后op 8 条 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-17T16:17:04-07:00"},"CompareURL":"luoanwu/platform-governance/compare/06cdd6f0fdfa799a55c0c78b11bdcb0601bcb0e7...22f145c7cc1d26ac35b6ce4781f2c36621c17de7","Len":1}...
|
1789687026
|
Edit
Delete
|
|
30709
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"96dbcd998 {"Commits":[{"Sha1":"96dbcd998453ba6720203ea63ab612caa4d34687","Message":"chore(reports): 延后op 回绑 @ 17b81dd（clean 树，worktreeDirty=false）\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:17:30-07:00"},{"Sha1":"17b81dde8df1c9c426b95261a8d7c1ad60054bd2","Message":"fix(governance): check-deferred-ops 改用治理层统一 provenance 口径\n\n原先自己数 `git status --porcelain` 行数判 worktreeDirty，把本轮要覆盖的 latest 报告也算成脏文件——字段随即恒为 true，一个永远为真的 provenance 字段没有信息量，也与真源仓 governance/lib/provenance.mjs、治理层 report-provenance.mjs 的既有口径（忽略本轮生成的 latest 报告）不一致。改为复用 governanceProvenance，一并得到 repository / dirtyPaths。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-17T16:17:30-07:00"}],"HeadCommit":{"Sha1":"96dbcd998453ba6720203ea63ab612caa4d34687","Message":"chore(reports): 延后op 回绑 @ 17b81dd（clean 树，worktreeDirty=false）\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:17:30-07:00"},"CompareURL":"luoanwu/platform-governance/compare/22f145c7cc1d26ac35b6ce4781f2c36621c17de7...96dbcd998453ba6720203ea63ab612caa4d34687","Len":2}...
|
1789687054
|
Edit
Delete
|
|
30710
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"25751af08 {"Commits":[{"Sha1":"25751af083e566216e1803734573cfdb8184e65b","Message":"docs(开发计划): §8 补「延后 op 门禁与两处收口」一行\n\n登记 check-deferred-ops 的建立、它当场抓出的两个真问题（CHG-003/006 同条目冲突的延后 op、CHG-003 enterprise-idp 的半应用）与随之收口的两处恒红/崩溃。一致性检查 L4 / L10 / L13 清零。\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-17T16:17:51-07:00"}],"HeadCommit":{"Sha1":"25751af083e566216e1803734573cfdb8184e65b","Message":"docs(开发计划): §8 补「延后 op 门禁与两处收口」一行\n\n登记 check-deferred-ops 的建立、它当场抓出的两个真问题（CHG-003/006 同条目冲突的延后 op、CHG-003 enterprise-idp 的半应用）与随之收口的两处恒红/崩溃。一致性检查 L4 / L10 / L13 清零。\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-17T16:17:51-07:00"},"CompareURL":"luoanwu/platform-governance/compare/96dbcd998453ba6720203ea63ab612caa4d34687...25751af083e566216e1803734573cfdb8184e65b","Len":1}...
|
1789687075
|
Edit
Delete
|
|
30711
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"15bce0f4b {"Commits":[{"Sha1":"15bce0f4b672fc7456786bc61d493b3ffc04e630","Message":"docs(平台治理): 收纳表随新增门禁改数——scripts 48→50、tests 32→33、reports 324→325（顶层 39→40）\n\ncheck-deferred-ops.mjs 与 lib/deferred-ops-core.mjs、deferred-ops.test.mjs、延后op.latest.json 四个新文件没同步收纳表，上一条提交（25751af）因此把 L13 三条漂移推了出去。本次补齐，L13 清零。\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-17T16:18:34-07:00"}],"HeadCommit":{"Sha1":"15bce0f4b672fc7456786bc61d493b3ffc04e630","Message":"docs(平台治理): 收纳表随新增门禁改数——scripts 48→50、tests 32→33、reports 324→325（顶层 39→40）\n\ncheck-deferred-ops.mjs 与 lib/deferred-ops-core.mjs、deferred-ops.test.mjs、延后op.latest.json 四个新文件没同步收纳表，上一条提交（25751af）因此把 L13 三条漂移推了出去。本次补齐，L13 清零。\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-17T16:18:34-07:00"},"CompareURL":"luoanwu/platform-governance/compare/25751af083e566216e1803734573cfdb8184e65b...15bce0f4b672fc7456786bc61d493b3ffc04e630","Len":1}...
|
1789687118
|
Edit
Delete
|
|
30712
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"a9e489b08 {"Commits":[{"Sha1":"a9e489b08d6d8dd510c9f63dd663b94037d5f9f4","Message":"docs(计划): PF-03 收口完成（真源仓 a084c5e，报告回绑 a7a19ec）\n\n- §3 PF-03 行改为「✅ 完成」，退出条件落为「三份文档均声明本目录身份与\n 版本轴归属、不含框架仓状态声明」\n- §5 ⑤ 移除已完成的「PF-03 ⑤ 文档回灌」\n- §8 增一行，含 check:evidence 仍 partial 的如实登记\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-17T16:19:27-07:00"}],"HeadCommit":{"Sha1":"a9e489b08d6d8dd510c9f63dd663b94037d5f9f4","Message":"docs(计划): PF-03 收口完成（真源仓 a084c5e，报告回绑 a7a19ec）\n\n- §3 PF-03 行改为「✅ 完成」，退出条件落为「三份文档均声明本目录身份与\n 版本轴归属、不含框架仓状态声明」\n- §5 ⑤ 移除已完成的「PF-03 ⑤ 文档回灌」\n- §8 增一行，含 check:evidence 仍 partial 的如实登记\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-17T16:19:27-07:00"},"CompareURL":"luoanwu/platform-governance/compare/15bce0f4b672fc7456786bc61d493b3ffc04e630...a9e489b08d6d8dd510c9f63dd663b94037d5f9f4","Len":1}...
|
1789687171
|
Edit
Delete
|
|
30713
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"a7a19ec54 {"Commits":[{"Sha1":"a7a19ec54a9f4ed81c770afa85a19125130e85a5","Message":"chore(reports): PF-03 ⑤ 回灌后静态门禁回绑 @ a084c5e\n\n干净树上重跑根 pnpm check（31 个 turbo 任务全过），26 份报告绑定\na084c5e / worktreeDirty=false。同时结清 41ca988 当时因并行会话在途、\n拿不到干净树而欠下的四份文档作用域报告（docs-truth、governance-docs、\nagent-adapters、dual-backend-parity）。\n\ncheck:evidence 仍为 partial：36 份已登记，26 新鲜 / 9 过期 / 1 例外。\n九条过期均为既有项，都需要真实环境重跑才能消除，不在本轮范围：\nport-conformance、runtime/ui-acceptance、revocation-sla、\nmainline-acceptance、mainline-restore、mainline-candidate-regression、\nidentity-http、identity-ui。\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-17T16:18:40-07:00"},{"Sha1":"a084c5e5f61f25a4f70efca3c42a763a1e7c9b8d","Message":"docs(runtime): PF-03 ⑤ 收口——README 与 CHANGELOG 声明本目录身份与版本轴归属\n\n承 41ca988。这两份随 scaffold 带入的框架文档不含错误的验收数字，问题是\n身份：读者落到 runtime/ 会以为自己在基础框架仓。\n\nREADME：\n- 标题由「基础框架 / Base Framework」改为「enterprise-platform/runtime\n （基础框架 v0.16.1 的 scaffold 实例）」，开篇说明下文绝大部分是框架原文\n 且仍准确，并划清三条界线——版本轴属框架、状态只认本仓报告与 CLAUDE.md\n 动态区、领取顺序在开发计划不设第二份\n- 目录结构补上此前完全缺失的本仓特有部分：modules/（kit + 七模块，\n modules.json + PLATFORM_PROFILES + 一模块一库）、clients/（@juhai/client-*）、\n test/（platform-tests），apps/ 补 workbench 与 api-nestjs 的平台装配点\n\nCHANGELOG：加一段说明这份轴属于框架、随 scaffold 带入，package.json 的\n0.16.1 读作「本运行时基于框架 0.16.1」而非平台版本；平台自己的发布轴是\nRelease Manifest、@juhai/* 包版本与开发计划 §2 的里程碑，平台侧新增能力\n不在此登记。\n\n框架原文的门禁、命令与 ADR 一律未动。check:docs-truth 与\ncheck:governance-docs 均通过（README 的信封形状与 api-fastify 定位断言\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-17T16:17:59-07:00"}],"HeadCommit":{"Sha1":"a7a19ec54a9f4ed81c770afa85a19125130e85a5","Message":"chore(reports): PF-03 ⑤ 回灌后静态门禁回绑 @ a084c5e\n\n干净树上重跑根 pnpm check（31 个 turbo 任务全过），26 份报告绑定\na084c5e / worktreeDirty=false。同时结清 41ca988 当时因并行会话在途、\n拿不到干净树而欠下的四份文档作用域报告（docs-truth、governance-docs、\nagent-adapters、dual-backend-parity）。\n\ncheck:evidence 仍为 partial：36 份已登记，26 新鲜 / 9 过期 / 1 例外。\n九条过期均为既有项，都需要真实环境重跑才能消除，不在本轮范围：\nport-conformance、runtime/ui-acceptance、revocation-sla、\nmainline-acceptance、mainline-restore、mainline-candidate-regression、\nidentity-http、identity-ui。\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-17T16:18:40-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/8dae61f91b56f708b1c76e66f07d98efa4828a36...a7a19ec54a9f4ed81c770afa85a19125130e85a5","Len":2}...
|
1789687171
|
Edit
Delete
|
|
30714
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"cfaef2fc8 {"Commits":[{"Sha1":"cfaef2fc83837096a19a0d330b709017c0f322dd","Message":"docs(计划): 登记偏差 #34——脏树绑定判据与作用域判据不一致，卡住报告回绑\n\n领取「九条过期证据里 port-conformance 是唯一纯本机项」后核出的机制缺口。\n\ncheck-evidence-freshness 对未提交输入已按作用域判（EVIDENCE_WORKTREE_CHANGED\n只在脏文件落进该报告 scope 才报），但 EVIDENCE_BOUND_DIRTY 仍取\nprovenance.worktreeDirty 这个仓级布尔（provenance.mjs 由全仓 git status 算，\n只排除 latest 报告自身）。\n\n实锤：pnpm check:port-conformance 重跑 41/41 passed，当时唯一脏文件是并行\n会话在改的 governance/check-catalog-drift.mjs 及其测试，不在该报告作用域\n（runtime/{modules,clients,packages} + 检查器 + lockfile）内，报告仍写\nworktreeDirty=true；提交后树一转干净即被判 error。因此本轮没有提交这次回绑，\n九份过期证据仍是九份。\n\n§6 增 #34 并给三个处置选项（维持现状 / 作用域化 / 折中声明式），标明待平台\n负责人裁、裁决前不得放宽也不得把脏绑报告当证据提交；§8 增一行。\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-17T16:21:58-07:00"}],"HeadCommit":{"Sha1":"cfaef2fc83837096a19a0d330b709017c0f322dd","Message":"docs(计划): 登记偏差 #34——脏树绑定判据与作用域判据不一致，卡住报告回绑\n\n领取「九条过期证据里 port-conformance 是唯一纯本机项」后核出的机制缺口。\n\ncheck-evidence-freshness 对未提交输入已按作用域判（EVIDENCE_WORKTREE_CHANGED\n只在脏文件落进该报告 scope 才报），但 EVIDENCE_BOUND_DIRTY 仍取\nprovenance.worktreeDirty 这个仓级布尔（provenance.mjs 由全仓 git status 算，\n只排除 latest 报告自身）。\n\n实锤：pnpm check:port-conformance 重跑 41/41 passed，当时唯一脏文件是并行\n会话在改的 governance/check-catalog-drift.mjs 及其测试，不在该报告作用域\n（runtime/{modules,clients,packages} + 检查器 + lockfile）内，报告仍写\nworktreeDirty=true；提交后树一转干净即被判 error。因此本轮没有提交这次回绑，\n九份过期证据仍是九份。\n\n§6 增 #34 并给三个处置选项（维持现状 / 作用域化 / 折中声明式），标明待平台\n负责人裁、裁决前不得放宽也不得把脏绑报告当证据提交；§8 增一行。\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-17T16:21:58-07:00"},"CompareURL":"luoanwu/platform-governance/compare/a9e489b08d6d8dd510c9f63dd663b94037d5f9f4...cfaef2fc83837096a19a0d330b709017c0f322dd","Len":1}...
|
1789687322
|
Edit
Delete
|
|
30715
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"bd625a1a1 {"Commits":[{"Sha1":"bd625a1a1535a34e265b11424a646618c543ffef","Message":"chore(reports): catalog:drift 升档后全量回绑 @ 8382c04（干净树）\n\n根 check 链 exit 0（catalog:drift 升档后 error 0 / drift 0 仍通过）、runtime 16 项静态门禁、工作台两份快照重生成。\n\n顺带清掉 7 条 EVIDENCE_BOUND_DIRTY：caddy / fixtures / facts / migration-decs / module-imports / catalog-reconciliation / otel 此前由 a7a19ec（PF-03 ⑤ 回绑）带进干净树时绑在脏树上，本次在干净树重跑后绑定 8382c04 / worktreeDirty=false。check:evidence 由 failed 回到 partial（新鲜 26 / 过期 9 / 无效 0），余 9 条过期均为需真实库或容器重跑的 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-17T16:22:31-07:00"},{"Sha1":"8382c0432e3c0cc2f2c6f379a2374d5f6e2cc9d1","Message":"feat(governance): catalog:drift 升档为阻断（决策批次 2026-09-16 C-12）\n\nC-12 的两个前置都已满足：A-2 已应用（CHG-002 于本轮落地），drift 已清零（error 0 / drift 0 / info 5 / unknown 0）。\n\n升档前的实况比\"能发现、不能阻断\"更弱：只有 `--strict` 才对 `error` 阻断，而根 `pnpm check` 从不传该开关、全仓也没有任何调用方传过——这道门禁装上之后一次都没拦过。现改为 `error` 与 `drift` 一律 exit 1，不再需要开关；`info`（authority≠E2 的刻意保留）与 `unknown`（独立克隆缺仓外资料）不阻断，独立克隆的失败关闭由 contracts check:local 与完整 check 承担。输出行的 ✓/✗ 同步按两档判。\n\n测试补 CLI 层四段：干净 exit 0、drift exit 1（升档前此处为 0）、error exit 1、工作区不可用只记 unknown 不阻断。check-catalog-drift 6/6。\n\n另修工作台运维快照：evidence 一档原样透传 check:evidence 的结论，passed / partial / failed 都是合法取值，此前允许集合漏了 failed——证据一过期就把快照测试打红，而不是让快照如实显示过期。规则行与测试同步补上，仍不含 available / healthy 这类会被误读成\"环境可用\"的词。governance 266/266。\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-17T16:21:32-07:00"}],"HeadCommit":{"Sha1":"bd625a1a1535a34e265b11424a646618c543ffef","Message":"chore(reports): catalog:drift 升档后全量回绑 @ 8382c04（干净树）\n\n根 check 链 exit 0（catalog:drift 升档后 error 0 / drift 0 仍通过）、runtime 16 项静态门禁、工作台两份快照重生成。\n\n顺带清掉 7 条 EVIDENCE_BOUND_DIRTY：caddy / fixtures / facts / migration-decs / module-imports / catalog-reconciliation / otel 此前由 a7a19ec（PF-03 ⑤ 回绑）带进干净树时绑在脏树上，本次在干净树重跑后绑定 8382c04 / worktreeDirty=false。check:evidence 由 failed 回到 partial（新鲜 26 / 过期 9 / 无效 0），余 9 条过期均为需真实库或容器重跑的 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-17T16:22:31-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/a7a19ec54a9f4ed81c770afa85a19125130e85a5...bd625a1a1535a34e265b11424a646618c543ffef","Len":2}...
|
1789687353
|
Edit
Delete
|
|
30716
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d991c4494 {"Commits":[{"Sha1":"d991c449457408aed0e9b98accb23feffdcc3d92","Message":"fix(governance): L8 补冻结物的显式豁免出口——审批记录条目写明，缺理由不放行\n\nL2 有 pragma 与 frozenInputs 两条出口，L8 一条也没有：冻结物改一字节即触发 L7 摘要不符，\n文件内的`一致性门禁豁免`标记对它无效，于是命中即永久噪声，与本门禁自己立的收敛原则\n（报出来的每一条都应当是能直接去改的）相反。\n\n出口改为由审批记录条目写明 consistencyExempt + consistencyExemptNote，缺 note 不放行；\n豁免以 frozenExempted 计数与 frozenExemptions 明细出现在 JSON 输出里，不静默。\n两个字段都不进 packageFingerprint（只取 path + sha256），登记前后指纹实测未变 1fdc2e1666c5。\n\n首条登记：新增基础应用MachineCatalog完整变更.patch。核验结论是误报——命中只 1 处、位于\ndiff 的上下文行（补丁并未引入），且处在一句陈述「旧断言写成了迁移双替换产物、等于没断言」的\n注释里，是对缺陷的描述而非被使用的路径。解除条件：变更包合并或撤回归档后随条目移除。\n\n验证：一致性门禁 3 → 2（余 L9 compose 撞名、L12 内核 pin 落后，均有既定归属）；\ntests/workspace-consistency.test.mjs 35/35；变更包就绪门禁与评审门禁 exit 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-17T16:22:29-07:00"}],"HeadCommit":{"Sha1":"d991c449457408aed0e9b98accb23feffdcc3d92","Message":"fix(governance): L8 补冻结物的显式豁免出口——审批记录条目写明，缺理由不放行\n\nL2 有 pragma 与 frozenInputs 两条出口，L8 一条也没有：冻结物改一字节即触发 L7 摘要不符，\n文件内的`一致性门禁豁免`标记对它无效，于是命中即永久噪声，与本门禁自己立的收敛原则\n（报出来的每一条都应当是能直接去改的）相反。\n\n出口改为由审批记录条目写明 consistencyExempt + consistencyExemptNote，缺 note 不放行；\n豁免以 frozenExempted 计数与 frozenExemptions 明细出现在 JSON 输出里，不静默。\n两个字段都不进 packageFingerprint（只取 path + sha256），登记前后指纹实测未变 1fdc2e1666c5。\n\n首条登记：新增基础应用MachineCatalog完整变更.patch。核验结论是误报——命中只 1 处、位于\ndiff 的上下文行（补丁并未引入），且处在一句陈述「旧断言写成了迁移双替换产物、等于没断言」的\n注释里，是对缺陷的描述而非被使用的路径。解除条件：变更包合并或撤回归档后随条目移除。\n\n验证：一致性门禁 3 → 2（余 L9 compose 撞名、L12 内核 pin 落后，均有既定归属）；\ntests/workspace-consistency.test.mjs 35/35；变更包就绪门禁与评审门禁 exit 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-17T16:22:29-07:00"},"CompareURL":"luoanwu/platform-governance/compare/cfaef2fc83837096a19a0d330b709017c0f322dd...d991c449457408aed0e9b98accb23feffdcc3d92","Len":1}...
|
1789687361
|
Edit
Delete
|
|
30717
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"bc850cd56 {"Commits":[{"Sha1":"bc850cd56895bf917bf6ec91b565f582e3dc601d","Message":"docs(决策): C-12 drift 升档已执行（真源仓 8382c04）\n\n决策批次 C-12 的两个前置（A-2 合并、drift 清零）均满足后执行升档：catalog:drift 的 error 与 drift 两档一律 exit 1，去掉从无调用方的 --strict 开关。逐条登记实况比原裁决所记更弱的那一点（此前连 error 都不阻断），并记 CLI 层四段负向。开发计划 §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-17T16:23:08-07:00"}],"HeadCommit":{"Sha1":"bc850cd56895bf917bf6ec91b565f582e3dc601d","Message":"docs(决策): C-12 drift 升档已执行（真源仓 8382c04）\n\n决策批次 C-12 的两个前置（A-2 合并、drift 清零）均满足后执行升档：catalog:drift 的 error 与 drift 两档一律 exit 1，去掉从无调用方的 --strict 开关。逐条登记实况比原裁决所记更弱的那一点（此前连 error 都不阻断），并记 CLI 层四段负向。开发计划 §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-17T16:23:08-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d991c449457408aed0e9b98accb23feffdcc3d92...bc850cd56895bf917bf6ec91b565f582e3dc601d","Len":1}...
|
1789687392
|
Edit
Delete
|
|
30718
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d5f1b641b {"Commits":[{"Sha1":"d5f1b641b05f0b3a351c8792b64d7215f3356d38","Message":"docs(计划): 偏差 #34 补第二个缺陷；登记 evidence-scopes 口径修正（真源仓 ac396a0）\n\nEVIDENCE_BOUND_DIRTY 读工作区里的报告文件，判定严重级所用的 currentTreeDirty\n却走 gitProvenance()，而后者显式排除 *.latest.json。并行会话正在跑门禁、只有\n报告文件脏时，门禁认定「当前树干净」，把 4 份尚未提交的在途报告判成 error 并\n输出「脏绑报告被提交了」——该断言在此情形下为假：那 4 份的 HEAD 版本干净绑定\n8382c04，只有工作区版本绑 bd625a1 + dirty。对比工作区版本与 HEAD 版本即可分辨，\n门禁不该断言它没有核实的事。两点同属一条规则，建议一并处置。\n\n§8 同时登记 evidence-scopes 口径说明补第五类（真源仓 ac396a0）。\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-17T16:25:08-07:00"}],"HeadCommit":{"Sha1":"d5f1b641b05f0b3a351c8792b64d7215f3356d38","Message":"docs(计划): 偏差 #34 补第二个缺陷；登记 evidence-scopes 口径修正（真源仓 ac396a0）\n\nEVIDENCE_BOUND_DIRTY 读工作区里的报告文件，判定严重级所用的 currentTreeDirty\n却走 gitProvenance()，而后者显式排除 *.latest.json。并行会话正在跑门禁、只有\n报告文件脏时，门禁认定「当前树干净」，把 4 份尚未提交的在途报告判成 error 并\n输出「脏绑报告被提交了」——该断言在此情形下为假：那 4 份的 HEAD 版本干净绑定\n8382c04，只有工作区版本绑 bd625a1 + dirty。对比工作区版本与 HEAD 版本即可分辨，\n门禁不该断言它没有核实的事。两点同属一条规则，建议一并处置。\n\n§8 同时登记 evidence-scopes 口径说明补第五类（真源仓 ac396a0）。\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-17T16:25:08-07:00"},"CompareURL":"luoanwu/platform-governance/compare/bc850cd56895bf917bf6ec91b565f582e3dc601d...d5f1b641b05f0b3a351c8792b64d7215f3356d38","Len":1}...
|
1789687511
|
Edit
Delete
|
|
30719
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ac396a0f2 {"Commits":[{"Sha1":"ac396a0f27fd673e02fc0c2f5887ea7f06b879b4","Message":"chore(governance): evidence-scopes 口径说明补第五类——有 provenance 但无生成脚本的一次性记录\n\n那段说明自 2026-09-15 起写「余 15 份未登记，都是有意不登」并逐类枚举，\n但今天实测是 16 份，且 client-identity 与 governance-truth-validation 两份\n不在任何一类里——说明本身成了过期声明，而它正是「为什么不登」的唯一依据。\n\n全仓搜索确认这两份没有生成脚本（与 caddy / workbench-snapshots 这类有\ngenerator 的登记项相反），属手工一次性记录：可以有合法 provenance，但不可\n重跑，登记后必然过期且只能靠例外掩盖。故新增第五类并写明：\n\n- 与 reports/stack-image-pins.latest.json 同因不同果——后者当年登记了，\n 于是只能挂一条带出口的例外；第五类因未登记而无需例外\n- 出口同样二选一：补生成脚本后转正式登记，或退役该报告\n- 在此之前它们只是记录，不得被引用为可重跑的机器证据\n\n计数改为带日期的复核快照。未新增或删除任何作用域登记，未改判据，未动文件\n其余格式（差异 1 行）。check:evidence 仍 partial（26 新鲜 / 9 过期 / 1 例外，\n与改前逐项相同）；governance 测试 266/266。\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-17T16:23:44-07:00"}],"HeadCommit":{"Sha1":"ac396a0f27fd673e02fc0c2f5887ea7f06b879b4","Message":"chore(governance): evidence-scopes 口径说明补第五类——有 provenance 但无生成脚本的一次性记录\n\n那段说明自 2026-09-15 起写「余 15 份未登记，都是有意不登」并逐类枚举，\n但今天实测是 16 份，且 client-identity 与 governance-truth-validation 两份\n不在任何一类里——说明本身成了过期声明，而它正是「为什么不登」的唯一依据。\n\n全仓搜索确认这两份没有生成脚本（与 caddy / workbench-snapshots 这类有\ngenerator 的登记项相反），属手工一次性记录：可以有合法 provenance，但不可\n重跑，登记后必然过期且只能靠例外掩盖。故新增第五类并写明：\n\n- 与 reports/stack-image-pins.latest.json 同因不同果——后者当年登记了，\n 于是只能挂一条带出口的例外；第五类因未登记而无需例外\n- 出口同样二选一：补生成脚本后转正式登记，或退役该报告\n- 在此之前它们只是记录，不得被引用为可重跑的机器证据\n\n计数改为带日期的复核快照。未新增或删除任何作用域登记，未改判据，未动文件\n其余格式（差异 1 行）。check:evidence 仍 partial（26 新鲜 / 9 过期 / 1 例外，\n与改前逐项相同）；governance 测试 266/266。\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-17T16:23:44-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/bd625a1a1535a34e265b11424a646618c543ffef...ac396a0f27fd673e02fc0c2f5887ea7f06b879b4","Len":1}...
|
1789687513
|
Edit
Delete
|
|
30720
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"0c5d0b09b {"Commits":[{"Sha1":"0c5d0b09bc2d1c4baddfd59b484c5fdcbe0917ab","Message":"fix(runtime): 框架残留 compose 补 project 名——退出 api-nestjs 撞名（C-13 / 一致性门禁 L9）\n\nruntime/apps/api-nestjs/docker-compose.yml 未声明顶层 name，docker compose 按目录名推导为\napi-nestjs，与工作区内另外 8 个仓的同名 compose 共用容器与具名卷（api-nestjs_pgdata /\nredisdata / miniodata）；后 up 的那个会复用前一个的数据。框架仓同名文件已写成\n`name: ${COMPOSE_PROJECT_NAME:-base-framework}`，本仓这份是更早版本的残留。\n\n按同一写法补上，默认值取本仓专属 enterprise-platform-runtime-dev（不沿用框架默认，否则\n改为与框架仓撞名）。本文件是框架默认 dev compose，其端口 5432 / 6379 与本仓实际底座\n（stack/compose.yaml，project enterprise-platform-stack）无关，改名不影响任何在跑的服务。\n\n一致性门禁 L9 参与仓 9 → 8；余 8 个仓在业务应用层与企业领域应用层，按 C-13 由各仓 Owner\n与 SRE 处置。三组卷现状：api-nestjs_* 与 enterprise-idp_* 共 5 个卷，所属容器均为\ncreated / exited 非运行态；C-13 要求的 pg_dump 尚未做（仓备份-2026-09-16/ 目前只有 4 个 git bundle）。\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-17T16:25:43-07:00"}],"HeadCommit":{"Sha1":"0c5d0b09bc2d1c4baddfd59b484c5fdcbe0917ab","Message":"fix(runtime): 框架残留 compose 补 project 名——退出 api-nestjs 撞名（C-13 / 一致性门禁 L9）\n\nruntime/apps/api-nestjs/docker-compose.yml 未声明顶层 name，docker compose 按目录名推导为\napi-nestjs，与工作区内另外 8 个仓的同名 compose 共用容器与具名卷（api-nestjs_pgdata /\nredisdata / miniodata）；后 up 的那个会复用前一个的数据。框架仓同名文件已写成\n`name: ${COMPOSE_PROJECT_NAME:-base-framework}`，本仓这份是更早版本的残留。\n\n按同一写法补上，默认值取本仓专属 enterprise-platform-runtime-dev（不沿用框架默认，否则\n改为与框架仓撞名）。本文件是框架默认 dev compose，其端口 5432 / 6379 与本仓实际底座\n（stack/compose.yaml，project enterprise-platform-stack）无关，改名不影响任何在跑的服务。\n\n一致性门禁 L9 参与仓 9 → 8；余 8 个仓在业务应用层与企业领域应用层，按 C-13 由各仓 Owner\n与 SRE 处置。三组卷现状：api-nestjs_* 与 enterprise-idp_* 共 5 个卷，所属容器均为\ncreated / exited 非运行态；C-13 要求的 pg_dump 尚未做（仓备份-2026-09-16/ 目前只有 4 个 git bundle）。\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-17T16:25:43-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/ac396a0f27fd673e02fc0c2f5887ea7f06b879b4...0c5d0b09bc2d1c4baddfd59b484c5fdcbe0917ab","Len":1}...
|
1789687572
|
Edit
Delete
|
|
30721
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1e0ea0813 {"Commits":[{"Sha1":"1e0ea08130bcbed848d075740bb4b5c44c1ffde4","Message":"chore(reports): 治理层门禁报告回绑 @ 6e0d7aa\n\n清树重跑 run-foundation-gates：阻断性 10/10 通过，仅记录 3\n（工作区一致性 2 条 L9 / L12、域分层 13 条，均不参与总账）。\n三份报告 worktreeDirty=false，绑定 6e0d7aa。\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-17T16:30:08-07:00"},{"Sha1":"6e0d7aa2570ce0046c8e1860044a8547f8567c23","Message":"docs(治理): L9 收口为「根因已闭、扩散无渠道」，登记 N-11 交派活\n\n核到底的结论是 L9 不该按「待修的缺陷」处理：\n\n- 模板根因早已关闭。框架 0.17.0（实现提交 313137b）给 compose 写了\n name: ${COMPOSE_PROJECT_NAME:-base-framework} 与 ${REDIS_PORT:-6379}，\n F14 在框架 pnpm check 链里守全仓每一份 compose，scaffold-derived.mjs\n 派生时重绑身份，变更请求文首已记「已受理并落地」。enterprise-platform\n 两份 compose 也已带身份。新建仓不再扩散该缺陷。\n- 但扩散没有发生，且没有渠道可走。回灌台账 §3 第 8 条指定的\n 框架新版本同步计划自述「同步波次事实上已无目标」（18 个派生仓已退役），\n 它也从不覆盖上层应用仓。L9 当日实测仍有 8 个应用仓共用 project\n api-nestjs，且这 8 个仓自己的门禁一个都不报：5 个带 F14 之前的旧版\n check-fork-readiness.mjs（文件内 F14 零命中），3 个没有该脚本——\n 它们的 pnpm check 在冲突状态下仍是绿的。\n- 台账原话「在模板修好前，任何两个仓不得同时 docker compose up」的前提\n 已不成立而风险未变，按实际判据改述为「上列 8 个仓两两之间不得同时 up」。\n\n治理层按回灌边界「不代业务应用仓提交」，不自行下手，本轮只落记录：\nC-15 与 §3 第 8 条加订正（append-only，不改写原文），新登记待裁决 N-11\n交目录负责人三选一，并写明 0.17.0 的 F14 是破坏性变更——改 project 名后\n首次 up 会建新空卷，旧卷 api-nestjs_* 的开发数据不跟着走，这正是 N-09\n当时搁置同步的那一条，选任一路线都要先答共用卷里的数据归谁。\n\nL9 保持红，不降级。\n\n证据：治理层 365 例 0 失败、阻断性门禁 10/10；工作区一致性仍 2 条\n（L9 / L12），无新增断链与措辞违规。报告在脏树上产出，不随本提交，\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-17T16:29:41-07:00"}],"HeadCommit":{"Sha1":"1e0ea08130bcbed848d075740bb4b5c44c1ffde4","Message":"chore(reports): 治理层门禁报告回绑 @ 6e0d7aa\n\n清树重跑 run-foundation-gates：阻断性 10/10 通过，仅记录 3\n（工作区一致性 2 条 L9 / L12、域分层 13 条，均不参与总账）。\n三份报告 worktreeDirty=false，绑定 6e0d7aa。\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-17T16:30:08-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d5f1b641b05f0b3a351c8792b64d7215f3356d38...1e0ea08130bcbed848d075740bb4b5c44c1ffde4","Len":2}...
|
1789687811
|
Edit
Delete
|
|
30722
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1645e7288 {"Commits":[{"Sha1":"1645e7288b484ab39a4e3ebb2da44678e9b9e300","Message":"docs(计划): 偏差 #34 已裁决并实现，移入已关闭（真源仓 e5cc39f / 4b067cd）\n\n目录负责人 2026-09-17 裁决：\n- A「干净检出生成报告」：不放宽 worktreeDirty，改为 pnpm reports:rebind 在\n HEAD 开 git worktree 跑零依赖门禁、只带回干净绑定的报告\n- B「修正断言」：EVIDENCE_BOUND_DIRTY 按报告文件自身是否未提交区分，在途\n 产物降 info 并如实描述，已提交的脏绑仍 error\n\n§6 中 #34 由开放表移入已关闭一行并附实现与证据；§8 增一行记录裁决与实现细节\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-17T16:33:10-07:00"}],"HeadCommit":{"Sha1":"1645e7288b484ab39a4e3ebb2da44678e9b9e300","Message":"docs(计划): 偏差 #34 已裁决并实现，移入已关闭（真源仓 e5cc39f / 4b067cd）\n\n目录负责人 2026-09-17 裁决：\n- A「干净检出生成报告」：不放宽 worktreeDirty，改为 pnpm reports:rebind 在\n HEAD 开 git worktree 跑零依赖门禁、只带回干净绑定的报告\n- B「修正断言」：EVIDENCE_BOUND_DIRTY 按报告文件自身是否未提交区分，在途\n 产物降 info 并如实描述，已提交的脏绑仍 error\n\n§6 中 #34 由开放表移入已关闭一行并附实现与证据；§8 增一行记录裁决与实现细节\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-17T16:33:10-07:00"},"CompareURL":"luoanwu/platform-governance/compare/1e0ea08130bcbed848d075740bb4b5c44c1ffde4...1645e7288b484ab39a4e3ebb2da44678e9b9e300","Len":1}...
|
1789687994
|
Edit
Delete
|
|
30723
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"4b067cd4a {"Commits":[{"Sha1":"4b067cd4a76bfced89f76e979cf7bd36d3521a91","Message":"chore(reports): otel 回绑 @ e5cc39f（首次用 pnpm reports:rebind 产出）\n\n在主工作区有并行会话未提交改动的情况下，经 HEAD 干净检出生成，\nprovenance 绑 e5cc39f / worktreeDirty=false——偏差 #34-A 裁决实现的首次实用。\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-17T16:32:14-07:00"},{"Sha1":"e5cc39f4dc74d56bce2b1861b15f8822ec3fdc3e","Message":"feat(governance): 偏差 #34 裁决实现——干净检出回绑工具 + 脏绑判定不再断言未核实的事\n\n2026-09-17 目录负责人裁决：A 走「干净 worktree 生成报告」（不动判据），\nB「修正断言」。\n\n#34-A｜新增 governance/rebind-reports.mjs（pnpm reports:rebind）\nprovenance.worktreeDirty 由全仓 git status 算，而 check:evidence 判过期是按\n每份报告自己的作用域算。口径不一致，导致只要仓里任何无关文件脏着就没法回绑\n任何报告——本工作区常有 2—3 个并行会话，干净窗口稀少，这是过期证据难清零的\n结构性成因。裁决不放宽 worktreeDirty，改为换个干净的地方生成：在 HEAD 开\ngit worktree 检出，在那里跑门禁，只把「绑 HEAD 且 dirty=false」的报告拷回。\n\n可行前提是 governance/ 零依赖（package.json 无 dependencies/devDependencies），\n临时检出不需要 pnpm install。实测：主工作区有 7 项未提交时，otel 报告仍绑到\n0c5d0b0 / dirty=false。\n\n三条护栏，都有负向用例：\n- 作用域内有未提交输入的门禁跳过（否则是拿 HEAD 的结论覆盖当前工作区）\n- 目标报告自己未提交的跳过（并行会话的在途产物，覆盖即销毁；--force 才 override）\n- 产出 provenance 不是干净 HEAD 绑定就不带回\n范围外的说清楚不假装：check:fixtures / check:port-conformance 与 runtime、\ncontracts 的检查需要构建产物，必须在装好依赖的检出里跑。\n\n顺带记一条坑：入口判定不能写 `import.meta.url === file://${argv[1]}`——本仓\n路径含中文，import.meta.url 是百分号编码的，比较永远不等，脚本会静默不做事。\n\n#34-B｜check-evidence-freshness 的 EVIDENCE_BOUND_DIRTY\n该分支读的是工作区里的报告文件，定级却用 currentTreeDirty，而后者走\ngitProvenance() 并显式排除 *.latest.json。于是并行会话跑门禁、只有报告文件脏\n时，当前树被算作干净，4 份未提交的在途报告被判 error 并输出「脏绑报告被提交\n了」——该断言为假（那 4 份的 HEAD 版本干净绑 8382c04）。现按报告文件自身是否\n未提交区分：在途产物降 info 并如实描述；确系已提交的脏绑仍是 error。判据未放宽，\n两条负向用例分别钉住这两侧。\n\ngovernance 测试 266 → 275。\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-17T16:32:04-07:00"}],"HeadCommit":{"Sha1":"4b067cd4a76bfced89f76e979cf7bd36d3521a91","Message":"chore(reports): otel 回绑 @ e5cc39f（首次用 pnpm reports:rebind 产出）\n\n在主工作区有并行会话未提交改动的情况下，经 HEAD 干净检出生成，\nprovenance 绑 e5cc39f / worktreeDirty=false——偏差 #34-A 裁决实现的首次实用。\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-17T16:32:14-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/0c5d0b09bc2d1c4baddfd59b484c5fdcbe0917ab...4b067cd4a76bfced89f76e979cf7bd36d3521a91","Len":2}...
|
1789687994
|
Edit
Delete
|
|
30724
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"eca16cecb {"Commits":[{"Sha1":"eca16cecb1b0e54e66d69268589ffa59c2fe6eff","Message":"chore(reports): 治理层门禁报告回绑 @ 3ca6a19\n\n清树重跑 run-foundation-gates：阻断性 11/11 通过（check-domain-layer 首次\n以阻断位计入，基线口径 0 阻断），仅记录 2（工作区一致性 L9 / L12）。\n三份报告 worktreeDirty=false，绑定 3ca6a19。\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-17T16:37:02-07:00"},{"Sha1":"3ca6a19355e099d1643d6f03eeb59ae360011615","Message":"feat(governance): 域分层门禁转阻断位，按基线只拦新增\n\n查 L9 派活路径时撞见一条静音：门禁消费登记里 check-domain-layer 的接入\n条件写的是「D5（CHG-007 合并）与 D9（两份契约副本收敛）清零后转阻断位」，\n2026-09-17 实测 D5 = 0、D9 = 0——条件早已满足而无人察觉。\n\n根因：check-gate-consumption 的 G4 只断言 wireInWhen 非空，从不校验它是否\n已成立。该登记本是为治「门禁失败信号无人看」而建的，流外出口是它唯一的\n豁免口，而豁免口自己没有到期判据——用来防静音的机制在自己身上静音了。\n\n处置不能是直接翻阻断位：余下 13 条全在上层应用仓，治理层按回灌边界不代其\n提交，接入即恒红，而恒红正是该登记要治的病。原条件后半句「其余各条按\nOwner 各自的节奏消」已写明正确形态，只是从没人把它实现成基线。故：\n\n- 新增 域分层基线.json：13 条存量逐条具名 Owner 与复核期（D2 权威倒挂 3 ·\n D4 无事实出口 3 · D6 未装入基座 3 · D7 同版本分叉 1 · D10 已装内容不可\n 追溯 1 · D11 门禁零负向探针 2），来源登记指回台账 U-24 / U-32 / U-34 /\n U-36 与 §3 第 2 条。\n- 新增 scripts/lib/domain-layer-baseline.mjs：B1 新增 / B2 存量恶化 /\n B3 基线腐烂或缺 Owner / B4 过复核期，四类任一非空即阻断。B3 与 B4 守的是\n 基线自己——修好了必须删条目，过了复核期必须复核，否则基线会腐烂成豁免清单。\n- check-domain-layer 退出码改基线口径，--no-baseline 仍看未过滤的全量\n （13 条，退出 1）；registry 里该条转 run-foundation-gates 阻断位。\n\n一处要点：棘轮只认单调变坏的量。D10 的 matched（命中源仓提交的文件数）与\nD11 的 probes（负向探针条数）都是越大越好，拿来当上限会把改进判成恶化、\n反过来把修复锁死；已在 findingCount 里排除并写明理由，现只有 D2 的 count\n做棘轮。这条有单测守着。\n\n顺带更正 check-workspace-consistency 那条已过期的基线文字：L8 已归零\n（并行会话登记了具名冻结豁免），L9 的「12 仓」按当日实测改为 8 个上层\n应用仓；其接入形态改写为照此先例走基线棘轮，不再用「全清零再接入」——\n否则又是一个可能长期悬空的流外出口。\n\n仍缺一道，已记台账 C-19：G4 至今不会因「wireInWhen 已成立」而判红，\n下一个流外出口还能同样悬空。\n\n证据：治理层 377 例 0 失败（新增 12 例负向）、阻断性门禁 11/11、\n工作区一致性仍 2 条（L9 / L12）。L13 当场抓出收纳表漂移，已随本提交改数\n（根文件 62→63、scripts 50→51、tests 33→34）。报告在脏树上产出，\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-17T16:36:39-07:00"}],"HeadCommit":{"Sha1":"eca16cecb1b0e54e66d69268589ffa59c2fe6eff","Message":"chore(reports): 治理层门禁报告回绑 @ 3ca6a19\n\n清树重跑 run-foundation-gates：阻断性 11/11 通过（check-domain-layer 首次\n以阻断位计入，基线口径 0 阻断），仅记录 2（工作区一致性 L9 / L12）。\n三份报告 worktreeDirty=false，绑定 3ca6a19。\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-17T16:37:02-07:00"},"CompareURL":"luoanwu/platform-governance/compare/1645e7288b484ab39a4e3ebb2da44678e9b9e300...eca16cecb1b0e54e66d69268589ffa59c2fe6eff","Len":2}...
|
1789688225
|
Edit
Delete
|
|
30725
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"693800cea {"Commits":[{"Sha1":"693800ceaf834b217a01466e19579af6a23925cf","Message":"chore(reports): 治理层门禁报告回绑 @ 87ec431\n\n清树重跑 run-foundation-gates：阻断性 11/11 通过，仅记录 2（工作区一致性\nL9 / L12）。三份报告 worktreeDirty=false，绑定 87ec431。\n\n（订正：本条信息初次写成「回绑 @ 9a5b3c0」，那是提交前预估的 SHA，实际\n实现提交是 87ec431。报告内容的绑定一直是对的，错的只是信息里的那串字。）\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-17T16:40:15-07:00"},{"Sha1":"87ec4315c77935405e16314c11789ddb6ae45e5a","Message":"feat(governance): G6 流外出口必须写复核期，缺失或过期即判红\n\n补上前一提交记为「仍缺一道」的缺口，不留登记而不建。\n\n根因：门禁消费登记的 G4 只断言 wireInWhen 非空，从不校验它是否已成立。\n流外出口是这份登记唯一的豁免口，而豁免口自己没有到期判据——用来防静音的\n机制在自己身上静音了。实锤就是前一提交处理的那条：check-domain-layer 的\n接入条件「D5 与 D9 清零」早已双双成立，G4 全绿，无人发现。\n\nG6 OUT_OF_FLOW_UNREVIEWED：流外条目必须写 conditionReviewBy（YYYY-MM-DD），\n缺失、格式不对或已过期即判红；当天不算过期；只对流外生效，阻断位条目每轮\n都在跑，不需要复核期。6 例负向覆盖这五种形态。\n\n守日期而不守条件是有意的：接入条件多半含人的判断（「框架同步波次扩散后」\n「再有派生仓开仓时」），机器判不了；能机器化的是「必须有人按期回来看一眼」。\n与同日落的域分层基线 B4 同形——缓期不是豁免。\n\n两条现存流外条目各自写了复核期与理由：\n- check-workspace-consistency 2026-10-31：L9 / L12 挂在活裁决 N-11 / C-14\n 上，六周内应有进展。\n- audit-platform-openings 2026-12-31：触发事件罕见，现存派生仓 0 个\n （派生仓状态.json 只剩 missing 1 + retired 18），不是六周尺度的事。\n\n台账 C-19 由「仍缺一道」改为已补，落点写明。\n\n证据：治理层 378 例 0 失败（新增 6 例负向）、阻断性门禁 11/11、\n工作区一致性仍 2 条（L9 / L12）。报告在脏树上产出，不随本提交。\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-17T16:40:01-07:00"}],"HeadCommit":{"Sha1":"693800ceaf834b217a01466e19579af6a23925cf","Message":"chore(reports): 治理层门禁报告回绑 @ 87ec431\n\n清树重跑 run-foundation-gates：阻断性 11/11 通过，仅记录 2（工作区一致性\nL9 / L12）。三份报告 worktreeDirty=false，绑定 87ec431。\n\n（订正：本条信息初次写成「回绑 @ 9a5b3c0」，那是提交前预估的 SHA，实际\n实现提交是 87ec431。报告内容的绑定一直是对的，错的只是信息里的那串字。）\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-17T16:40:15-07:00"},"CompareURL":"luoanwu/platform-governance/compare/eca16cecb1b0e54e66d69268589ffa59c2fe6eff...693800ceaf834b217a01466e19579af6a23925cf","Len":2}...
|
1789688425
|
Edit
Delete
|
|
30726
|
4
|
5
|
4
|
37
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"32321989a {"Commits":[{"Sha1":"32321989ae84e6ea9fb39d6c4a60f19d0b176b2a","Message":"docs: document current monitoring dashboard requirements\n","AuthorEmail":"584481098@qq.com","AuthorName":"laiqiaojie","CommitterEmail":"584481098@qq.com","CommitterName":"laiqiaojie","Timestamp":"2026-09-18T08:40:28+08:00"}],"HeadCommit":{"Sha1":"32321989ae84e6ea9fb39d6c4a60f19d0b176b2a","Message":"docs: document current monitoring dashboard requirements\n","AuthorEmail":"584481098@qq.com","AuthorName":"laiqiaojie","CommitterEmail":"584481098@qq.com","CommitterName":"laiqiaojie","Timestamp":"2026-09-18T08:40:28+08:00"},"CompareURL":"laiqiaojie/yuancheng-lianjie/compare/ff3ecada4ff774e981d2cb76d1565a7345b6d072...32321989ae84e6ea9fb39d6c4a60f19d0b176b2a","Len":1}...
|
1789692031
|
Edit
Delete
|
|
30727
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"689e924f3 {"Commits":[{"Sha1":"689e924f3db984f90ee13c2e0dd1a0082a70c1d3","Message":"docs(计划): 过期证据 9 → 8 且 error 清零；§1 证据行按 f9cb195 重采\n\n偏差 #34 裁决落地后的首轮清理：port-conformance 重绑、runtime 静态链四份\n重绑（WB-1 使 runtime/apps 变动而落进作用域）、工作台两份快照经\npnpm reports:rebind 重绑。check:evidence 由 failed 转 partial（27/8/1，0 error）。\n余 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-17T18:22:48-07:00"}],"HeadCommit":{"Sha1":"689e924f3db984f90ee13c2e0dd1a0082a70c1d3","Message":"docs(计划): 过期证据 9 → 8 且 error 清零；§1 证据行按 f9cb195 重采\n\n偏差 #34 裁决落地后的首轮清理：port-conformance 重绑、runtime 静态链四份\n重绑（WB-1 使 runtime/apps 变动而落进作用域）、工作台两份快照经\npnpm reports:rebind 重绑。check:evidence 由 failed 转 partial（27/8/1，0 error）。\n余 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-17T18:22:48-07:00"},"CompareURL":"luoanwu/platform-governance/compare/693800ceaf834b217a01466e19579af6a23925cf...689e924f3db984f90ee13c2e0dd1a0082a70c1d3","Len":1}...
|
1789694571
|
Edit
Delete
|
|
30728
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"f9cb19531 {"Commits":[{"Sha1":"f9cb195319422eac06bd2111e1034e956ebcafb0","Message":"chore(reports): 工作台两份快照回绑 @ e94ad17\n\n经 pnpm reports:rebind 的多报告路径产出，两份同绑同一提交。\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-17T18:22:33-07:00"},{"Sha1":"e94ad17db981932c5d0b08f2b99f2a786bdf36d7","Message":"feat(governance): rebind-reports 支持一个门禁多份报告，纳入工作台两份快照\n\nworkbench-catalog-snapshot 与 workbench-ops-snapshot 由同一个\nbuild-workbench-snapshots.mjs 产出，且它只 import node 内置与\ngovernance/lib/provenance.mjs——同样零依赖，本该在工具覆盖范围内。\n\n注册表 report:string → reports:string[]，三处判定与执行循环随之改为按份遍历。\n新增一条语义约束：同一门禁的多份报告要么全带回、要么一份都不带，否则两份会\n绑到不同提交，而它们描述的是同一次运行。两条负向用例分别钉住「任一份在途即\n整体跳过」与「任一份作用域有未提交输入即整体跳过」。\n\n实跑验证：两份快照同绑 aaf4836 / dirty=false。\ngovernance 测试 275 → 277。\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-17T18:22:24-07:00"},{"Sha1":"aaf483645e83337d5d0a8a50b95df678adf0fb76","Message":"chore(reports): 过期证据 13 → 8，全部 error 清零 @ 4b067cd\n\n按偏差 #34 裁决落地后的第一轮清理。源码树干净（仅并行会话的 4 份 latest\n报告未提交，worktreeDirty 本就排除 *.latest.json），故可就地重跑并绑定。\n\n- port-conformance：41/41 passed，由 defd9d7 重绑 4b067cd。这是 09-17 那次\n 「跑通了却因无关文件脏着而不能采信」的收口\n- runtime 静态链 31 任务全过：naming / dual-backend-parity / fork-readiness /\n migrations 四份此前因并行会话提交 WB-1、runtime/apps 多出 workbench 而落进\n 作用域，现已重绑\n- workbench 两份快照重新生成（catalog projects=21 mapped=7/7 conflicts=0；\n ops controlled_operations=recorded）\n\ncheck:evidence 由 failed 转 partial：27 新鲜 / 8 过期 / 1 例外，0 error。\n余下 8 份全部需要真实环境才能重跑，不是本机静态能解决的：\nruntime-acceptance、ui-acceptance、revocation-sla、mainline-acceptance、\nmainline-restore、mainline-candidate-regression、identity-http、identity-ui。\n\n未触碰并行会话在途的 caddy / facts / migration-decs / module-imports 四份。\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-17T18:21:25-07:00"}],"HeadCommit":{"Sha1":"f9cb195319422eac06bd2111e1034e956ebcafb0","Message":"chore(reports): 工作台两份快照回绑 @ e94ad17\n\n经 pnpm reports:rebind 的多报告路径产出，两份同绑同一提交。\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-17T18:22:33-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/4b067cd4a76bfced89f76e979cf7bd36d3521a91...f9cb195319422eac06bd2111e1034e956ebcafb0","Len":3}...
|
1789694573
|
Edit
Delete
|
|
30729
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"36e0423ef {"Commits":[{"Sha1":"36e0423efe0ddc105136d193bfb594efb9838d62","Message":"chore(reports): 全链回绑 @ 1af0f22，证据零过期零告警\n\n干净树重跑根 pnpm check。check:evidence：34 份已登记，**33 份新鲜 / 0 过期 /\n0 输入未提交 / 0 告警 / 1 例外**（stack-image-pins，其例外自带出口）。\n\n这是本轮治理完善的收口：从九份过期、error 级判定，到零过期零告警。\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-17T18:56:42-07:00"},{"Sha1":"1af0f2210a8ac041a26a97ff5f4965461398ebf1","Message":"feat(governance): 测试地板 652 → 775；动态区回灌今日三级验收\n\ncheck:docs-truth 抓出报告已刷新而动态区未跟上——正是今天修过的那类双真源\n漂移，这次由门禁自己拦住。\n\n- 动态区「真实 DB」：2026-09-13 / 7e26a50 / 652 → 2026-09-18 / 6108357 /\n 775，并写明隔离栈与「破坏性注入只认 ms23-ci 类专用工程」的边界\n- 动态区「浏览器」：2026-09-13 / 7e26a50 → 2026-09-18 / 003aadd，端口如实\n- 棘轮：testsPassed 652 → 775（本轮实测），ownTests 35 → 40、\n ownTestCases 185 → 212（静态 runner 自己抬的，它刻意不动其他 runner 的地板）\n\n棘轮只收紧不放宽：775 是今天真实跑出来的数，此后低于它即红。\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-17T18:56:07-07:00"},{"Sha1":"23281b8f814b350af20b95ab6a4176cdbaf25b0a","Message":"chore(governance): 退役两份无生成脚本的报告，过期证据归零\n\n2026-09-17 目录负责人裁决：两份都退役（删文件 + 撤登记，不留例外）。\n\n两份都是 09-12 手工拼的一次性记录，仓内没有任何脚本能产出它们，因此永远\n无法重跑、只会一直过期；而它们的结论现在都由自动化门禁产出并正确绑定：\n\n- identity-http（8 例）：逐条比对确认与 runtime/test/e2e/identity-profile.test.ts\n 同名，今日已在 check:runtime 的 775 例里跑过并绑 6108357。其自述的\n provenanceMethod 就写着「Post-run source inspection」，本就不是门禁产物\n- mainline-candidate-regression（155 例）：作用域即 governance/{lib,test} 与\n 两个检查器，结论由 node --test governance/test/*.test.mjs 产出，今日 277/277。\n 155 这个数字自 09-12 起无人维护，保留它只会让人以为另有一道独立的候选回归门禁\n\n退役前已核：release-manifest.mjs 与 build-workbench-snapshots.mjs 都不引用\n这两份；其余引用只在 09-12 的历史记录文档与生成式快照字段里，会随重跑更新。\n\nevidence-scopes 登记 36 → 34，note 补记本次裁决与口径（同 stack-image-pins\n例外里写的「倾向 ① 退役」）。\n\ncheck:evidence：33 新鲜 / **0 过期** / 1 例外（stack-image-pins，另有出口）。\ngovernance 测试 277/277。\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-17T18:54:10-07:00"},{"Sha1":"95d0ac8860038d4af6a3d15d4ca35ff0eff52749","Message":"chore(reports): 主线验收与恢复演练重跑通过 @ bc978a8\n\n在专用隔离栈 enterprise-platform-ms23-ci（PG :55485 / Redis :56395 /\nRedpanda :59105）上重跑，源库经 mainline:prepare 新建（platform_{fact,\npermission,audit,owner,consumer}_ci，全部非超级用户 / NOBYPASSRLS）。\n\n- mainline-acceptance passed，四套件 11 / 17 / 19 / 18：fact-read-http、\n fact-persistence、audit-tamper、mainline-revocation-chaos（含重复投递、\n 非连续乱序版本、毒消息 DLQ 与 broker 停机恢复）\n- mainline-restore passed，3 个库逐库 dump + 还原到新建 drill 库，表数\n 12 / 6 / …，逐库 SHA-256 一致；不删除、不重置源库与既往 drill\n- revocation-sla 随之刷新，仍 partial：invalidationPush 的 verdict 依旧是\n measured-with-harness-transport，生产传输未接线\n\n为什么换栈：恢复演练与 Redpanda 混沌用例的 allowlist 只认\nenterprise-platform-{ms23,ms23-ci,adversarial} 三个 compose 工程，\n共享的 ep-delivery 与 dev 常驻 stack 永远不匹配——这是故意的护栏，\n破坏性注入不得指向共享底座。dev 常驻栈全程未被触碰。\n\ncheck:evidence 过期 4 → 2，余下两份都没有生成脚本，另行处置。\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-17T18:50:15-07:00"},{"Sha1":"bc978a8a99636b34e0bc69b018ee6ce8bd6192b9","Message":"chore(reports): identity 模块 UI 验收重跑通过 @ 828f178\n\n真实统一 Next 前端 + identity profile + 专用 PostgreSQL/Redis，2 个浏览器级\n用例全绿，由 90cda56 重绑 828f178（作用域内此前累计 21 个文件变更）。\n端口 web :7352 / api :7353。\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-17T18:43:48-07:00"}],"HeadCommit":{"Sha1":"36e0423efe0ddc105136d193bfb594efb9838d62","Message":"chore(reports): 全链回绑 @ 1af0f22，证据零过期零告警\n\n干净树重跑根 pnpm check。check:evidence：34 份已登记，**33 份新鲜 / 0 过期 /\n0 输入未提交 / 0 告警 / 1 例外**（stack-image-pins，其例外自带出口）。\n\n这是本轮治理完善的收口：从九份过期、error 级判定，到零过期零告警。\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-17T18:56:42-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/f9cb195319422eac06bd2111e1034e956ebcafb0...36e0423efe0ddc105136d193bfb594efb9838d62","Len":8}...
|
1789696615
|
Edit
Delete
|
|
30730
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"e6d286b4f {"Commits":[{"Sha1":"e6d286b4f61d0227fa7f42cd0f5f40e624540dbf","Message":"docs: 修复退役报告导致的断链（一致性门禁 L4）\n\n09-12 的候选校验记录链向 reports/mainline-candidate-regression.latest.json，\n该报告已随 23281b8 退役，治理层一致性门禁 L4 随即报断链。改为文字说明：\n报告已退役、退役理由、结论现由 governance 测试产出（今 277/277），当时的\n154/0/1 保留为历史记录，不改写历史结论。\n\nL4 / L10 / L13 恢复 CLEAN。\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-17T18:58:04-07:00"}],"HeadCommit":{"Sha1":"e6d286b4f61d0227fa7f42cd0f5f40e624540dbf","Message":"docs: 修复退役报告导致的断链（一致性门禁 L4）\n\n09-12 的候选校验记录链向 reports/mainline-candidate-regression.latest.json，\n该报告已随 23281b8 退役，治理层一致性门禁 L4 随即报断链。改为文字说明：\n报告已退役、退役理由、结论现由 governance 测试产出（今 277/277），当时的\n154/0/1 保留为历史记录，不改写历史结论。\n\nL4 / L10 / L13 恢复 CLEAN。\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-17T18:58:04-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/36e0423efe0ddc105136d193bfb594efb9838d62...e6d286b4f61d0227fa7f42cd0f5f40e624540dbf","Len":1}...
|
1789696688
|
Edit
Delete
|
|
30731
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"150e625ed {"Commits":[{"Sha1":"150e625ed2a33300a3bc051fd4e60fa6e76a7947","Message":"docs(计划): 真实环境八份证据重跑通过，证据零过期（真源仓 36e0423）\n\n§1 证据新鲜度行与运行/UI 证据行按 2026-09-18 实测重采；§8 增一行。\n\n重跑：runtime-acceptance 775（地板 652 → 775）、ui-acceptance 5、\nmainline-acceptance 四套件 11/17/19/18、mainline-restore 3 库逐库 SHA-256\n一致、revocation-sla、identity-ui 2。退役（目录负责人裁决）：identity-http\n与 mainline-candidate-regression，两者仓内无生成脚本、永远无法重跑，结论\n已由自动化门禁覆盖。\n\ncheck:evidence：33 新鲜 / 0 过期 / 0 告警 / 1 例外。\n\n如实保留：invalidationPush 仍是 measured-with-harness-transport，生产传输\n未接线，不构成 MS-3 达成证据。\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-17T18:58:36-07:00"}],"HeadCommit":{"Sha1":"150e625ed2a33300a3bc051fd4e60fa6e76a7947","Message":"docs(计划): 真实环境八份证据重跑通过，证据零过期（真源仓 36e0423）\n\n§1 证据新鲜度行与运行/UI 证据行按 2026-09-18 实测重采；§8 增一行。\n\n重跑：runtime-acceptance 775（地板 652 → 775）、ui-acceptance 5、\nmainline-acceptance 四套件 11/17/19/18、mainline-restore 3 库逐库 SHA-256\n一致、revocation-sla、identity-ui 2。退役（目录负责人裁决）：identity-http\n与 mainline-candidate-regression，两者仓内无生成脚本、永远无法重跑，结论\n已由自动化门禁覆盖。\n\ncheck:evidence：33 新鲜 / 0 过期 / 0 告警 / 1 例外。\n\n如实保留：invalidationPush 仍是 measured-with-harness-transport，生产传输\n未接线，不构成 MS-3 达成证据。\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-17T18:58:36-07:00"},"CompareURL":"luoanwu/platform-governance/compare/689e924f3db984f90ee13c2e0dd1a0082a70c1d3...150e625ed2a33300a3bc051fd4e60fa6e76a7947","Len":1}...
|
1789696719
|
Edit
Delete
|
|
30732
|
8
|
5
|
8
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"c14db8f1a {"Commits":[{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"}],"HeadCommit":{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"},"CompareURL":"vodtest/pay/compare/8fb41e899e8648e9f6030654749d7e720747bac0...c14db8f1a9ec41d87a955d658f790551ba854f74","Len":1}...
|
1789696776
|
Edit
Delete
|
|
30733
|
9
|
5
|
8
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"c14db8f1a {"Commits":[{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"}],"HeadCommit":{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"},"CompareURL":"vodtest/pay/compare/8fb41e899e8648e9f6030654749d7e720747bac0...c14db8f1a9ec41d87a955d658f790551ba854f74","Len":1}...
|
1789696776
|
Edit
Delete
|
|
30734
|
1
|
5
|
8
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"c14db8f1a {"Commits":[{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"}],"HeadCommit":{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"},"CompareURL":"vodtest/pay/compare/8fb41e899e8648e9f6030654749d7e720747bac0...c14db8f1a9ec41d87a955d658f790551ba854f74","Len":1}...
|
1789696776
|
Edit
Delete
|
|
30735
|
3
|
5
|
8
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"c14db8f1a {"Commits":[{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"}],"HeadCommit":{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"},"CompareURL":"vodtest/pay/compare/8fb41e899e8648e9f6030654749d7e720747bac0...c14db8f1a9ec41d87a955d658f790551ba854f74","Len":1}...
|
1789696776
|
Edit
Delete
|
|
30736
|
4
|
5
|
8
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"c14db8f1a {"Commits":[{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"}],"HeadCommit":{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"},"CompareURL":"vodtest/pay/compare/8fb41e899e8648e9f6030654749d7e720747bac0...c14db8f1a9ec41d87a955d658f790551ba854f74","Len":1}...
|
1789696776
|
Edit
Delete
|
|
30737
|
7
|
5
|
8
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"c14db8f1a {"Commits":[{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"}],"HeadCommit":{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"},"CompareURL":"vodtest/pay/compare/8fb41e899e8648e9f6030654749d7e720747bac0...c14db8f1a9ec41d87a955d658f790551ba854f74","Len":1}...
|
1789696776
|
Edit
Delete
|
|
30738
|
10
|
5
|
8
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"c14db8f1a {"Commits":[{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"}],"HeadCommit":{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"},"CompareURL":"vodtest/pay/compare/8fb41e899e8648e9f6030654749d7e720747bac0...c14db8f1a9ec41d87a955d658f790551ba854f74","Len":1}...
|
1789696776
|
Edit
Delete
|
|
30739
|
11
|
5
|
8
|
21
|
0
|
0
|
refs/heads/pay-260915
|
0
|
{"Commits":[{"Sha1":"c14db8f1a {"Commits":[{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"}],"HeadCommit":{"Sha1":"c14db8f1a9ec41d87a955d658f790551ba854f74","Message":"需求 未成年人核验 16886\n","AuthorEmail":"developer.jeff.c@gmail.com","AuthorName":"chenjunfeng","CommitterEmail":"developer.jeff.c@gmail.com","CommitterName":"chenjunfeng","Timestamp":"2026-09-18T09:59:31+08:00"},"CompareURL":"vodtest/pay/compare/8fb41e899e8648e9f6030654749d7e720747bac0...c14db8f1a9ec41d87a955d658f790551ba854f74","Len":1}...
|
1789696776
|
Edit
Delete
|
|
30740
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"2dfbcb914 {"Commits":[{"Sha1":"2dfbcb9148a7beabb926462eebb82645e548c10a","Message":"chore(reports): 回绑 @ a9fd6e8，check:evidence 全绿\n\n33 份已登记全部新鲜，0 过期 / 0 未提交输入 / 0 例外 / 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-17T19:00:52-07:00"},{"Sha1":"a9fd6e826db77532ac3abfc149a9de822e40ea12","Message":"chore(governance): 退役 stack-image-pins，check:evidence 首次转 passed\n\n目录负责人裁决：按该报告自己的例外里写的「倾向 ① 退役」执行。\n\n它与今日退役的另两份同类：仓内无生成脚本（2026-09-14 全仓搜索确认），是\n一次性手工产物，永远无法重跑，只能靠例外掩盖。其结论「compose 12 个镜像\n是否全按 digest 锁定」已由 governance/release-manifest.mjs 的\nparseComposeImages 完整覆盖——实测同为 12 条、0 未锁，且未锁时进 missing，\n由真脚本产出、自动保鲜，严格优于被退役的手工快照。\n\n- evidence-scopes：entries 34 → 33，exceptions 1 → 0（自此为空）\n- check-evidence-freshness 的成因注释保留 2026-09-14 那条实锤（它正是本门禁\n 存在的理由），但标注该报告已退役，免得后人去找一个不存在的文件\n\ncheck:evidence：**passed**，33 新鲜 / 0 过期 / 0 输入未提交 / 0 例外。\n这是它第一次不是 partial。governance 测试 277/277。\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-17T19:00:17-07:00"}],"HeadCommit":{"Sha1":"2dfbcb9148a7beabb926462eebb82645e548c10a","Message":"chore(reports): 回绑 @ a9fd6e8，check:evidence 全绿\n\n33 份已登记全部新鲜，0 过期 / 0 未提交输入 / 0 例外 / 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-17T19:00:52-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/e6d286b4f61d0227fa7f42cd0f5f40e624540dbf...2dfbcb9148a7beabb926462eebb82645e548c10a","Len":2}...
|
1789696855
|
Edit
Delete
|
|
30741
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"a03bc2d77 {"Commits":[{"Sha1":"a03bc2d7789a81e0da6b79e51f2abb32fff2b906","Message":"docs(计划): stack-image-pins 退役，check:evidence 首次全绿（真源仓 a9fd6e8）\n\n第三份无生成脚本的手工记录按其例外自写的「倾向 ① 退役」执行。结论已由\nrelease-manifest 的 parseComposeImages 覆盖（同为 12 条 0 未锁，未锁进\nmissing，由真脚本产出自动保鲜）。evidence-scopes exceptions 自此为空。\n\n§1 证据行改为 passed（33 新鲜 / 0 过期 / 0 例外 / 0 告警）；§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-17T19:01:40-07:00"}],"HeadCommit":{"Sha1":"a03bc2d7789a81e0da6b79e51f2abb32fff2b906","Message":"docs(计划): stack-image-pins 退役，check:evidence 首次全绿（真源仓 a9fd6e8）\n\n第三份无生成脚本的手工记录按其例外自写的「倾向 ① 退役」执行。结论已由\nrelease-manifest 的 parseComposeImages 覆盖（同为 12 条 0 未锁，未锁进\nmissing，由真脚本产出自动保鲜）。evidence-scopes exceptions 自此为空。\n\n§1 证据行改为 passed（33 新鲜 / 0 过期 / 0 例外 / 0 告警）；§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-17T19:01:40-07:00"},"CompareURL":"luoanwu/platform-governance/compare/150e625ed2a33300a3bc051fd4e60fa6e76a7947...a03bc2d7789a81e0da6b79e51f2abb32fff2b906","Len":1}...
|
1789696904
|
Edit
Delete
|
|
30742
|
19
|
5
|
19
|
69
|
0
|
0
|
refs/heads/chanpin-20261013
|
0
|
{"Commits":[{"Sha1":"3acc1167b {"Commits":[{"Sha1":"3acc1167b01ad0228e51424c97d0385bc26be3bc","Message":"数据报表改名业务查询；平台收入结算报表新增霸屏收入结算三级模块\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:07:13+08:00"}],"HeadCommit":{"Sha1":"3acc1167b01ad0228e51424c97d0385bc26be3bc","Message":"数据报表改名业务查询；平台收入结算报表新增霸屏收入结算三级模块\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:07:13+08:00"},"CompareURL":"linmingzhang/ktv-booking-prototype/compare/fe3c44ce9fcd5ad1eab5fc746050bdb0be8b2935...3acc1167b01ad0228e51424c97d0385bc26be3bc","Len":1}...
|
1789697338
|
Edit
Delete
|
|
30743
|
17
|
5
|
19
|
69
|
0
|
0
|
refs/heads/chanpin-20261013
|
0
|
{"Commits":[{"Sha1":"3acc1167b {"Commits":[{"Sha1":"3acc1167b01ad0228e51424c97d0385bc26be3bc","Message":"数据报表改名业务查询；平台收入结算报表新增霸屏收入结算三级模块\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:07:13+08:00"}],"HeadCommit":{"Sha1":"3acc1167b01ad0228e51424c97d0385bc26be3bc","Message":"数据报表改名业务查询；平台收入结算报表新增霸屏收入结算三级模块\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:07:13+08:00"},"CompareURL":"linmingzhang/ktv-booking-prototype/compare/fe3c44ce9fcd5ad1eab5fc746050bdb0be8b2935...3acc1167b01ad0228e51424c97d0385bc26be3bc","Len":1}...
|
1789697338
|
Edit
Delete
|
|
30744
|
18
|
5
|
19
|
69
|
0
|
0
|
refs/heads/chanpin-20261013
|
0
|
{"Commits":[{"Sha1":"3acc1167b {"Commits":[{"Sha1":"3acc1167b01ad0228e51424c97d0385bc26be3bc","Message":"数据报表改名业务查询；平台收入结算报表新增霸屏收入结算三级模块\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:07:13+08:00"}],"HeadCommit":{"Sha1":"3acc1167b01ad0228e51424c97d0385bc26be3bc","Message":"数据报表改名业务查询；平台收入结算报表新增霸屏收入结算三级模块\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:07:13+08:00"},"CompareURL":"linmingzhang/ktv-booking-prototype/compare/fe3c44ce9fcd5ad1eab5fc746050bdb0be8b2935...3acc1167b01ad0228e51424c97d0385bc26be3bc","Len":1}...
|
1789697338
|
Edit
Delete
|
|
30745
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"314c17936 {"Commits":[{"Sha1":"314c179366fb02a53485f4efbd0e3d3e88cd5470","Message":"chore(reports): 回绑 @ 71b306f，登记面 33 → 35 全新鲜\n\nrelease-manifest 与 sbom 首次带嵌套 provenance 并受新鲜度保护。\n\nManifest 刷新后缺项 4 → 6，多出的两条都是真的、被旧快照藏了四天：\n- images.stack.*：compose 启用 runtime 服务后镜像是变量 ${PLATFORM_RUNTIME_IMAGE:?}，\n 未按 digest 锁定（PF-05 / PF-23 晋级前解决）\n- sbom：局部 lockfile 清单（268 包，仅 Node 依赖，不含基础镜像 Debian 包）\n 不满足 D-2 的完整 SBOM 要求\n\ncheck:evidence passed：35 份已登记全部新鲜，0 过期 / 0 例外 / 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-17T19:21:00-07:00"},{"Sha1":"71b306f53390e6119590b5225b660cd4effcd3b5","Message":"chore(governance): 登记 release-manifest 与 sbom 进 evidence-scopes（35 条）\n\n承 c5d9897。三份补了嵌套 provenance 之后，其中两份现在就能登记：\n\n- release-manifest（warn）：作用域 = compose、image-digest.json、四类包的\n package.json、runtime/modules、生成器与 schema。**这是 MS-4 退出条件的判据\n 输入**，此前无人监控其新鲜度\n- sbom（warn）：作用域 = image-digest.json、生成器、runtime 锁文件\n\nimage-smoke 本轮不登记：生成器已修，但要补上形状得起真实容器重跑（脚本强制\n--env-file，需 DB/Redis），不值得为补一个形状去起一套底座——待其下一次真实\n运行后登记。note 里写明了这一条与 mainline-dev-deployment 的区别（后者没有\n生成脚本，属手工记录那一类，不是形状问题）。\n\n同时修正 note 里 ① 类的描述：原写「没有 provenance.gitSha，要先让产生脚本写\nprovenance」，对这四份是不准确的——数据早就有。\n\ngovernance 测试 277/277。\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-17T19:20:23-07:00"},{"Sha1":"c5d98975f8c466d035550a4f38899db325d8b806","Message":"feat(governance): 三份报告补嵌套 provenance，让 MS-4 判据输入受新鲜度保护\n\n2026-09-17 目录负责人裁决：补嵌套 provenance，四份有 SHA 的全做。\n\n问题：release-manifest / sbom / image-smoke / mainline-dev-deployment 都写了\n源 SHA，但是**平铺**在顶层（sourceSha），而 check:evidence 只认嵌套的\nprovenance.gitSha。于是它们登记不进 evidence-scopes，游离在新鲜度之外。\n此前 evidence-scopes 的口径说明把它们归为「没有 provenance.gitSha，要先让\n产生脚本写 provenance」——对其中四份是不准确的：数据早就有，缺的是形状。\n\n实锤这不是理论风险：Manifest 绑 ac3683d（2026-09-14），其后它的结论输入改了\n10 个文件（contracts/governance 的 package.json、image-digest.json、\ncompose.yaml、client-fact 全套），四天无人报警。重跑后缺项 4 → 6，多出的两条\n都是真的——compose 启用 runtime 服务后镜像是变量未按 digest 锁定；SBOM 未随\n19150ae 镜像重生成。**一份过期的 Manifest 一直在少报，而 MS-4 的退出条件正是\n读它**（status=complete 且 runner 为 CI）。\n\n改动：\n- stack/release-manifest.schema.json 增可选 provenance 对象（不进 required，\n 向后兼容；additionalProperties:false 故必须显式加），并写明与顶层三项同源\n- release-manifest.mjs 同时写 provenance 与顶层兼容字段，实测两者一致\n- sbom.mjs / smoke-image.mjs 增 provenance: gitProvenance(root)。注意它们原有的\n sourceSha 是**镜像的**源提交，与「本报告在哪个提交产出」不是一回事，两者都留\n\nmainline-dev-deployment 做不了：全仓搜索确认它没有生成脚本，是第四份手工记录\n（与今日退役的三份同类），不是形状问题。另行处置。\n\ngovernance 测试 277/277。\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-17T19:19:03-07:00"}],"HeadCommit":{"Sha1":"314c179366fb02a53485f4efbd0e3d3e88cd5470","Message":"chore(reports): 回绑 @ 71b306f，登记面 33 → 35 全新鲜\n\nrelease-manifest 与 sbom 首次带嵌套 provenance 并受新鲜度保护。\n\nManifest 刷新后缺项 4 → 6，多出的两条都是真的、被旧快照藏了四天：\n- images.stack.*：compose 启用 runtime 服务后镜像是变量 ${PLATFORM_RUNTIME_IMAGE:?}，\n 未按 digest 锁定（PF-05 / PF-23 晋级前解决）\n- sbom：局部 lockfile 清单（268 包，仅 Node 依赖，不含基础镜像 Debian 包）\n 不满足 D-2 的完整 SBOM 要求\n\ncheck:evidence passed：35 份已登记全部新鲜，0 过期 / 0 例外 / 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-17T19:21:00-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/2dfbcb9148a7beabb926462eebb82645e548c10a...314c179366fb02a53485f4efbd0e3d3e88cd5470","Len":3}...
|
1789698065
|
Edit
Delete
|
|
30746
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"e81617fb8 {"Commits":[{"Sha1":"e81617fb827a3db190701bc33bca21cc14ce20c8","Message":"docs(计划): MS-4 判据输入纳入新鲜度监控；Manifest 缺项 4 → 6（真源仓 314c179）\n\nrelease-manifest / sbom / image-smoke / mainline-dev-deployment 此前被归为\n「没有 provenance.gitSha」，实为写了源 SHA 但平铺在顶层，check:evidence 只认\n嵌套形状。实锤危害：Manifest 绑 ac3683d 四天，其后结论输入改了 10 个文件，\n刷新后缺项 4 → 6，多出的 images.stack.* 未锁与 SBOM 不满足 D-2 两条都是真的\n——而 MS-4 的退出条件正是读这份 Manifest。\n\n§1 Release Manifest 行按刷新后的六项缺项重采；§1 证据行改为 35 份全新鲜；\n§8 增一行，含未做项与理由（image-smoke 待下次真实运行、mainline-dev-deployment\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-17T19:21:54-07:00"}],"HeadCommit":{"Sha1":"e81617fb827a3db190701bc33bca21cc14ce20c8","Message":"docs(计划): MS-4 判据输入纳入新鲜度监控；Manifest 缺项 4 → 6（真源仓 314c179）\n\nrelease-manifest / sbom / image-smoke / mainline-dev-deployment 此前被归为\n「没有 provenance.gitSha」，实为写了源 SHA 但平铺在顶层，check:evidence 只认\n嵌套形状。实锤危害：Manifest 绑 ac3683d 四天，其后结论输入改了 10 个文件，\n刷新后缺项 4 → 6，多出的 images.stack.* 未锁与 SBOM 不满足 D-2 两条都是真的\n——而 MS-4 的退出条件正是读这份 Manifest。\n\n§1 Release Manifest 行按刷新后的六项缺项重采；§1 证据行改为 35 份全新鲜；\n§8 增一行，含未做项与理由（image-smoke 待下次真实运行、mainline-dev-deployment\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-17T19:21:54-07:00"},"CompareURL":"luoanwu/platform-governance/compare/a03bc2d7789a81e0da6b79e51f2abb32fff2b906...e81617fb827a3db190701bc33bca21cc14ce20c8","Len":1}...
|
1789698116
|
Edit
Delete
|
|
30747
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"96bfdde50 {"Commits":[{"Sha1":"96bfdde508464b4b0e1e3fb05f77a9f488492fc0","Message":"chore(reports): 回绑 @ 903f019\n\ncheck:evidence passed：35 份已登记全部新鲜，0 过期 / 0 例外 / 0 告警；\n未登记 13 份（四份手工记录退役后的稳定态）。\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-17T19:23:58-07:00"},{"Sha1":"903f019dc8033d3042cc0446e054e2665782fedc","Message":"chore(governance): 退役 mainline-dev-deployment，四份手工记录清零\n\n目录负责人裁决：与今日退役的另三份同类处置。\n\n它只记 09-12 在 dev 栈启用 Redpanda 这一件事（自述 scope「Redpanda only」），\n仓内无生成脚本、不可重跑。该结论现由三处覆盖且都会自动保鲜：\n\n- stack/compose.yaml 的 redpanda 已是启用状态（非候选注释块），MS-2 的机器\n 判定直接读它\n- stack/reports/runtime-up.*.json：四份更新的 dev 运行记录（09-14 / 09-16 ×3）\n- pnpm check:deployed：活体核验运行镜像与源提交\n\ndev 栈此后已重建多轮，09-12 那份快照描述的容器与端点早已不是当前事实。\n\nevidence-scopes note 补记本次裁决（它本就未登记，无条目可撤）；\n09-12 的执行记录里那处纯文本引用补一句退役说明——L4 不报（不是 markdown\n链接），但读者会去找一个不存在的文件。\n\n至此四份无生成脚本的手工记录全部退役：identity-http、\nmainline-candidate-regression、stack-image-pins、mainline-dev-deployment。\n\ncheck:evidence passed：35 份已登记全部新鲜，未登记 14 → 13。\ngovernance 测试 277/277。\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-17T19:23:31-07:00"}],"HeadCommit":{"Sha1":"96bfdde508464b4b0e1e3fb05f77a9f488492fc0","Message":"chore(reports): 回绑 @ 903f019\n\ncheck:evidence passed：35 份已登记全部新鲜，0 过期 / 0 例外 / 0 告警；\n未登记 13 份（四份手工记录退役后的稳定态）。\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-17T19:23:58-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/314c179366fb02a53485f4efbd0e3d3e88cd5470...96bfdde508464b4b0e1e3fb05f77a9f488492fc0","Len":2}...
|
1789698242
|
Edit
Delete
|
|
30748
|
19
|
5
|
19
|
69
|
0
|
0
|
refs/heads/chanpin-20261013
|
0
|
{"Commits":[{"Sha1":"a5cfb02de {"Commits":[{"Sha1":"a5cfb02de0c5005803687631f1a6df3c0158c509","Message":"去掉收入报表多余注释并恢复霸屏需求描述\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:23:54+08:00"}],"HeadCommit":{"Sha1":"a5cfb02de0c5005803687631f1a6df3c0158c509","Message":"去掉收入报表多余注释并恢复霸屏需求描述\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:23:54+08:00"},"CompareURL":"linmingzhang/ktv-booking-prototype/compare/3acc1167b01ad0228e51424c97d0385bc26be3bc...a5cfb02de0c5005803687631f1a6df3c0158c509","Len":1}...
|
1789698273
|
Edit
Delete
|
|
30749
|
17
|
5
|
19
|
69
|
0
|
0
|
refs/heads/chanpin-20261013
|
0
|
{"Commits":[{"Sha1":"a5cfb02de {"Commits":[{"Sha1":"a5cfb02de0c5005803687631f1a6df3c0158c509","Message":"去掉收入报表多余注释并恢复霸屏需求描述\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:23:54+08:00"}],"HeadCommit":{"Sha1":"a5cfb02de0c5005803687631f1a6df3c0158c509","Message":"去掉收入报表多余注释并恢复霸屏需求描述\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:23:54+08:00"},"CompareURL":"linmingzhang/ktv-booking-prototype/compare/3acc1167b01ad0228e51424c97d0385bc26be3bc...a5cfb02de0c5005803687631f1a6df3c0158c509","Len":1}...
|
1789698273
|
Edit
Delete
|
|
30750
|
18
|
5
|
19
|
69
|
0
|
0
|
refs/heads/chanpin-20261013
|
0
|
{"Commits":[{"Sha1":"a5cfb02de {"Commits":[{"Sha1":"a5cfb02de0c5005803687631f1a6df3c0158c509","Message":"去掉收入报表多余注释并恢复霸屏需求描述\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:23:54+08:00"}],"HeadCommit":{"Sha1":"a5cfb02de0c5005803687631f1a6df3c0158c509","Message":"去掉收入报表多余注释并恢复霸屏需求描述\n","AuthorEmail":"codex@example.local","AuthorName":"Codex","CommitterEmail":"codex@example.local","CommitterName":"Codex","Timestamp":"2026-09-18T10:23:54+08:00"},"CompareURL":"linmingzhang/ktv-booking-prototype/compare/3acc1167b01ad0228e51424c97d0385bc26be3bc...a5cfb02de0c5005803687631f1a6df3c0158c509","Len":1}...
|
1789698273
|
Edit
Delete
|
|
30751
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ae6cf47e5 {"Commits":[{"Sha1":"ae6cf47e538de724c00c270f78ad014669585c8d","Message":"docs(计划): mainline-dev-deployment 退役，四份手工记录清零（真源仓 903f019）\n\n结论由 compose 的 redpanda 启用状态、四份更新的 runtime-up 记录与\ncheck:deployed 覆盖，三者都会自动保鲜；dev 栈此后已重建多轮，09-12 的\n快照早已不是当前事实。\n\n§1 证据行补第三步；§8 增一行。未登记 16 → 13。\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-17T19:24:42-07:00"}],"HeadCommit":{"Sha1":"ae6cf47e538de724c00c270f78ad014669585c8d","Message":"docs(计划): mainline-dev-deployment 退役，四份手工记录清零（真源仓 903f019）\n\n结论由 compose 的 redpanda 启用状态、四份更新的 runtime-up 记录与\ncheck:deployed 覆盖，三者都会自动保鲜；dev 栈此后已重建多轮，09-12 的\n快照早已不是当前事实。\n\n§1 证据行补第三步；§8 增一行。未登记 16 → 13。\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-17T19:24:42-07:00"},"CompareURL":"luoanwu/platform-governance/compare/e81617fb827a3db190701bc33bca21cc14ce20c8...ae6cf47e538de724c00c270f78ad014669585c8d","Len":1}...
|
1789698286
|
Edit
Delete
|
|
30752
|
7
|
5
|
7
|
22
|
0
|
0
|
refs/heads/app-260818
|
0
|
{"Commits":[{"Sha1":"16e0a5094 {"Commits":[{"Sha1":"16e0a5094917b0b424e976e043ef66e229dd7ded","Message":"营业状态\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T10:05:28+08:00"}],"HeadCommit":{"Sha1":"16e0a5094917b0b424e976e043ef66e229dd7ded","Message":"营业状态\n","AuthorEmail":"11833999+littlemaidi@user.noreply.gitee.com","AuthorName":"LITTLEMAIDI","CommitterEmail":"11833999+littlemaidi@user.noreply.gitee.com","CommitterName":"LITTLEMAIDI","Timestamp":"2026-09-18T10:05:28+08:00"},"CompareURL":"vodtest/app/compare/b92b949a1d4fa57c121b1d455f5706c112a7fc68...16e0a5094917b0b424e976e043ef66e229dd7ded","Len":1}...
|
1789699457
|
Edit
Delete
|