|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
30702
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"589467ea0 {"Commits":[{"Sha1":"589467ea0debc370a8800dc05cd744af7360cbbd","Message":"docs(计划): 开发计划梳理 09-14 标为已被取代——排序职责移交开发计划 §5\n\n开发计划 §5 于 2026-09-17 按阻塞链重排后,09-14 梳理成了第二份「现行领取\n表」,而它的完成判据自 09-15 起没再更新。逐条复核后确认大部分已被 09-16\n决策批次与 09-17 各 CHG 取代:\n\n- 统一审计 blockers 4 → 1(只余 ASSET_EVIDENCE_REVIEW_REQUIRED)\n- catalog:drift 的 drift 4 → 0(error 0 / info 5)\n- DEC-033—036 由 pending 转 rejected(候选平台随 CHG-015 撤销)\n- 派生仓 13 冻结仓 retirable 0/13 → 18 retired + 1 missing,active 0\n- 冻结副本已于 09-16 物理移除(PF-04 阶段 2 / CHG-013)\n- 阶段 B 的 B1/B2/B5 与阶段 C 的登记链均已签署或应用\n\n据此在其头部加状态段:声明不再是现行领取顺序、指向开发计划 §5、逐条列出\n判据差异,并点明仍然有效的只有 E2 的资产证据与 E7 ③。它仍是现行文档(被\n30 余处文档与脚本引用),故门禁例外保留,只把 workspace-consistency-core\n的理由注释与对应测试名从「现行领取表」改为「现行文档」,断言不动。\n\nL4 / L10 / L13 CLEAN;全量门禁基线仍为 L8 / L9 / L12 三条既有项;\nworkspace-consistency 测试 35/35。\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:08:19-07:00"}],"HeadCommit":{"Sha1":"589467ea0debc370a8800dc05cd744af7360cbbd","Message":"docs(计划): 开发计划梳理 09-14 标为已被取代——排序职责移交开发计划 §5\n\n开发计划 §5 于 2026-09-17 按阻塞链重排后,09-14 梳理成了第二份「现行领取\n表」,而它的完成判据自 09-15 起没再更新。逐条复核后确认大部分已被 09-16\n决策批次与 09-17 各 CHG 取代:\n\n- 统一审计 blockers 4 → 1(只余 ASSET_EVIDENCE_REVIEW_REQUIRED)\n- catalog:drift 的 drift 4 → 0(error 0 / info 5)\n- DEC-033—036 由 pending 转 rejected(候选平台随 CHG-015 撤销)\n- 派生仓 13 冻结仓 retirable 0/13 → 18 retired + 1 missing,active 0\n- 冻结副本已于 09-16 物理移除(PF-04 阶段 2 / CHG-013)\n- 阶段 B 的 B1/B2/B5 与阶段 C 的登记链均已签署或应用\n\n据此在其头部加状态段:声明不再是现行领取顺序、指向开发计划 §5、逐条列出\n判据差异,并点明仍然有效的只有 E2 的资产证据与 E7 ③。它仍是现行文档(被\n30 余处文档与脚本引用),故门禁例外保留,只把 workspace-consistency-core\n的理由注释与对应测试名从「现行领取表」改为「现行文档」,断言不动。\n\nL4 / L10 / L13 CLEAN;全量门禁基线仍为 L8 / L9 / L12 三条既有项;\nworkspace-consistency 测试 35/35。\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:08:19-07:00"},"CompareURL":"luoanwu/platform-governance/compare/7f5b2e680072ff3c40ad39617334e9d268d49e14...589467ea0debc370a8800dc05cd744af7360cbbd","Len":1}...
|
1789686509
|
Edit
Delete
|
|
30701
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"7f5b2e680 {"Commits":[{"Sha1":"7f5b2e680072ff3c40ad39617334e9d268d49e14","Message":"docs(计划): 开发计划状态格同步 OPS-1——条件 A 仓内满足、交付阶段 ② 可开工\n\n精简改版落盘后并行会话实现了 OPS-1 受控执行面(真源仓 6378b6f + 回绑\n1ccb3b6),只补了 §8 一行,状态格仍写「条件 A 部分满足」。按机器证据同步:\n\n- 头部与 §1 标题:真源仓 HEAD 7ca5952 → 361a0e4(报告绑 1ccb3b6)\n- §1 仓与远端:工作树 clean、origin 1ccb3b6、GitHub 落后 116、41 条未合分支\n- §1 模块:M3 增受控运维运行时 permission-ops.ts(operationId 幂等键 + outbox 中继)\n- §1 证据新鲜度:26 新鲜 / 9 过期 warn / 1 豁免 @ 6378b6f\n- §1 工作台:受控执行面四条路径与验收计数,controlled_operations 转 recorded\n- §2 交付五步、§2A 交付 ② 判定:条件 A / D / E 均解除,判定补目标环境部分\n- §3A:OPS 组归入已完成,删去「OPS-3 第一条」开放行,余四操作与 OPS-4—6\n 前置改写,WB-1 前置清空\n- §4 M3 行、§5 ④、§7 两远端与并行会话两条风险\n\n未改证据口径,未改机器 Catalog。L4 / L10 / L13 CLEAN,全量门禁基线仍为\nL8 / L9 / L12 三条既有项;治理层 workspace-consistency 测试 35/35。\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:03:26-07:00"}],"HeadCommit":{"Sha1":"7f5b2e680072ff3c40ad39617334e9d268d49e14","Message":"docs(计划): 开发计划状态格同步 OPS-1——条件 A 仓内满足、交付阶段 ② 可开工\n\n精简改版落盘后并行会话实现了 OPS-1 受控执行面(真源仓 6378b6f + 回绑\n1ccb3b6),只补了 §8 一行,状态格仍写「条件 A 部分满足」。按机器证据同步:\n\n- 头部与 §1 标题:真源仓 HEAD 7ca5952 → 361a0e4(报告绑 1ccb3b6)\n- §1 仓与远端:工作树 clean、origin 1ccb3b6、GitHub 落后 116、41 条未合分支\n- §1 模块:M3 增受控运维运行时 permission-ops.ts(operationId 幂等键 + outbox 中继)\n- §1 证据新鲜度:26 新鲜 / 9 过期 warn / 1 豁免 @ 6378b6f\n- §1 工作台:受控执行面四条路径与验收计数,controlled_operations 转 recorded\n- §2 交付五步、§2A 交付 ② 判定:条件 A / D / E 均解除,判定补目标环境部分\n- §3A:OPS 组归入已完成,删去「OPS-3 第一条」开放行,余四操作与 OPS-4—6\n 前置改写,WB-1 前置清空\n- §4 M3 行、§5 ④、§7 两远端与并行会话两条风险\n\n未改证据口径,未改机器 Catalog。L4 / L10 / L13 CLEAN,全量门禁基线仍为\nL8 / L9 / L12 三条既有项;治理层 workspace-consistency 测试 35/35。\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:03:26-07:00"},"CompareURL":"luoanwu/platform-governance/compare/deae8475189dc2fbb2efb54b2f1f8ddccef56bf6...7f5b2e680072ff3c40ad39617334e9d268d49e14","Len":1}...
|
1789686326
|
Edit
Delete
|
|
30699
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"deae84751 {"Commits":[{"Sha1":"deae8475189dc2fbb2efb54b2f1f8ddccef56bf6","Message":"docs(开发计划): §8 补 OPS-1 一行——上一条提交(654ff8f)的编辑因编码报错未落盘\n\n654ff8f 的提交信息写了「开发计划 §8 增 OPS-1 一行」,但该次 python 编辑以非 UTF-8 stdin 报错中断,实际只改了三份决策文档。本次补上该行:四条路径、三重守卫、幂等与回执、真源仓 6378b6f + 回绑 1ccb3b6、条件 A 满足与未做项。沿用并行会话精简后的表格,不另起表。一致性检查 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:00:32-07:00"}],"HeadCommit":{"Sha1":"deae8475189dc2fbb2efb54b2f1f8ddccef56bf6","Message":"docs(开发计划): §8 补 OPS-1 一行——上一条提交(654ff8f)的编辑因编码报错未落盘\n\n654ff8f 的提交信息写了「开发计划 §8 增 OPS-1 一行」,但该次 python 编辑以非 UTF-8 stdin 报错中断,实际只改了三份决策文档。本次补上该行:四条路径、三重守卫、幂等与回执、真源仓 6378b6f + 回绑 1ccb3b6、条件 A 满足与未做项。沿用并行会话精简后的表格,不另起表。一致性检查 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:00:32-07:00"},"CompareURL":"luoanwu/platform-governance/compare/654ff8fb8ece3c56829bb6b340369f44d191dcee...deae8475189dc2fbb2efb54b2f1f8ddccef56bf6","Len":1}...
|
1789686036
|
Edit
Delete
|
|
30698
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"654ff8fb8 {"Commits":[{"Sha1":"654ff8fb8ece3c56829bb6b340369f44d191dcee","Message":"docs(决策): OPS-1 受控执行面已实现(真源仓 6378b6f),CHG-018 条件 A 满足、阶段 ② 可开工\n\nCHG-005 材料登记四条路径与首条命令已实现,并列明仍未做项(拍板 ① 的 M6 投影与 audit-seeds、② 的 IdP 管理员核验暂以环境白名单承接、其余四条定义与审批路径、platform.operations 升 active、目标环境验收)。CHG-018 材料与待裁决架构事项 N-10 的条件 A 由「部分满足」改为满足;开发计划 §8 增 OPS-1 一行(沿用并行会话精简后的表)。一致性检查 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:00:02-07:00"},{"Sha1":"f5ea5ab56f2516ec7361b02b4addb5090bfb851e","Message":"docs(计划): 基础设施仓开发计划精简改版——按真源仓 7ca5952 重采,§5 按阻塞链重排、§3A 已完成项归表\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T15:59:02-07:00"}],"HeadCommit":{"Sha1":"654ff8fb8ece3c56829bb6b340369f44d191dcee","Message":"docs(决策): OPS-1 受控执行面已实现(真源仓 6378b6f),CHG-018 条件 A 满足、阶段 ② 可开工\n\nCHG-005 材料登记四条路径与首条命令已实现,并列明仍未做项(拍板 ① 的 M6 投影与 audit-seeds、② 的 IdP 管理员核验暂以环境白名单承接、其余四条定义与审批路径、platform.operations 升 active、目标环境验收)。CHG-018 材料与待裁决架构事项 N-10 的条件 A 由「部分满足」改为满足;开发计划 §8 增 OPS-1 一行(沿用并行会话精简后的表)。一致性检查 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:00:02-07:00"},"CompareURL":"luoanwu/platform-governance/compare/93e41b4e1266da3443de00fa89c81a22d83dd92c...654ff8fb8ece3c56829bb6b340369f44d191dcee","Len":2}...
|
1789686005
|
Edit
Delete
|
|
30695
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"93e41b4e1 {"Commits":[{"Sha1":"93e41b4e1266da3443de00fa89c81a22d83dd92c","Message":"docs(决策): CHG-019 材料——A-6 八项权限资源升 active + P-4 运行时目录准入(已代签并应用,真源仓 bde8af9)\n\n材料含 permissions / code / tests 三份 delta、语义边界(active 只表示词表定稿)、机器读者处置与代签回执;决策批次 §3 与开发计划 §8 登记;收纳表 doc/ 计数 145→149、CHG 范围至 019。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T08:39:49-07:00"}],"HeadCommit":{"Sha1":"93e41b4e1266da3443de00fa89c81a22d83dd92c","Message":"docs(决策): CHG-019 材料——A-6 八项权限资源升 active + P-4 运行时目录准入(已代签并应用,真源仓 bde8af9)\n\n材料含 permissions / code / tests 三份 delta、语义边界(active 只表示词表定稿)、机器读者处置与代签回执;决策批次 §3 与开发计划 §8 登记;收纳表 doc/ 计数 145→149、CHG 范围至 019。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T08:39:49-07:00"},"CompareURL":"luoanwu/platform-governance/compare/0cc1eb07d72db16fc5ae9b9b491d1016ab767ba6...93e41b4e1266da3443de00fa89c81a22d83dd92c","Len":1}...
|
1789659592
|
Edit
Delete
|
|
30692
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"0cc1eb07d {"Commits":[{"Sha1":"0cc1eb07d72db16fc5ae9b9b491d1016ab767ba6","Message":"docs(决策): CHG-005 批准并应用(真源仓 255dc31);simulate-chg-005 增 --contracts=active / --apply\n\n三份代签回执写入材料;状态改为已批准并应用,登记未做项(audit-seeds、platform:ops 守卫与四条路径随 OPS-1)。决策批次 §3 与开发计划 §8 登记,并记录目录负责人对 A-6 形态与首条命令的决定。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T08:29:52-07:00"}],"HeadCommit":{"Sha1":"0cc1eb07d72db16fc5ae9b9b491d1016ab767ba6","Message":"docs(决策): CHG-005 批准并应用(真源仓 255dc31);simulate-chg-005 增 --contracts=active / --apply\n\n三份代签回执写入材料;状态改为已批准并应用,登记未做项(audit-seeds、platform:ops 守卫与四条路径随 OPS-1)。决策批次 §3 与开发计划 §8 登记,并记录目录负责人对 A-6 形态与首条命令的决定。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T08:29:52-07:00"},"CompareURL":"luoanwu/platform-governance/compare/25eb193e8b0e59fdeaf41285bde074d8dc9e1a77...0cc1eb07d72db16fc5ae9b9b491d1016ab767ba6","Len":1}...
|
1789658994
|
Edit
Delete
|
|
30690
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"25eb193e8 {"Commits":[{"Sha1":"25eb193e8b0e59fdeaf41285bde074d8dc9e1a77","Message":"feat(governance): simulate-chg-004 增 --contracts=active / --apply;CHG-004 阶段 2 已应用(真源仓 d88c3f1)\n\n模拟器新模式镜像活跃契约并跳过已落地的 CHG-001—003,passed 后可把同一组 ops 应用到活跃目录并打印修改清单(镜像未 passed 拒绝应用)。tests.delta 重基线增 validators 锚点 12 → 17。CHG-004 材料状态改为已应用并登记两处重基线调整(validators 锚点;已批准 blocked_by → decided_by);DEC-020 草案指向候选文件的链接改指已登记的 schemas/facts;决策批次 §3 与开发计划 §8 登记 A-7 第一批完成,下一步 A-6 与 CHG-005。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T08:20:24-07:00"}],"HeadCommit":{"Sha1":"25eb193e8b0e59fdeaf41285bde074d8dc9e1a77","Message":"feat(governance): simulate-chg-004 增 --contracts=active / --apply;CHG-004 阶段 2 已应用(真源仓 d88c3f1)\n\n模拟器新模式镜像活跃契约并跳过已落地的 CHG-001—003,passed 后可把同一组 ops 应用到活跃目录并打印修改清单(镜像未 passed 拒绝应用)。tests.delta 重基线增 validators 锚点 12 → 17。CHG-004 材料状态改为已应用并登记两处重基线调整(validators 锚点;已批准 blocked_by → decided_by);DEC-020 草案指向候选文件的链接改指已登记的 schemas/facts;决策批次 §3 与开发计划 §8 登记 A-7 第一批完成,下一步 A-6 与 CHG-005。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T08:20:24-07:00"},"CompareURL":"luoanwu/platform-governance/compare/2a7ecc8e5116cdc8d9dcf12f5e7e98cab9433e0e...25eb193e8b0e59fdeaf41285bde074d8dc9e1a77","Len":1}...
|
1789658428
|
Edit
Delete
|
|
30688
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"2a7ecc8e5 {"Commits":[{"Sha1":"2a7ecc8e5116cdc8d9dcf12f5e7e98cab9433e0e","Message":"docs(决策): CHG-002 已应用(真源仓 73959f8,重基线三处调整);DEC-037—039 登记为 pending,裁决数声明 36→39\n\nCHG-002 材料状态改为已应用并登记重基线调整(archived_tag 取 retirement.derived_repo_tag、OS evidence 缺失保留现值、pending 锚点 0→3、modules.json scope +039);待裁决架构事项 DEC-037/038/039 三行由「未登记(CHG-002 待批)」改为「已登记 pending,裁决未做」;决策批次 §3 与开发计划 §8 登记 A-2 第一包完成及后续包(CHG-003 / 006 延后 op、CHG-004 重基线);基础/README 与总体开发计划的裁决数声明同步为 39 条 / 3 pending,L13 清零。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T08:10:53-07:00"}],"HeadCommit":{"Sha1":"2a7ecc8e5116cdc8d9dcf12f5e7e98cab9433e0e","Message":"docs(决策): CHG-002 已应用(真源仓 73959f8,重基线三处调整);DEC-037—039 登记为 pending,裁决数声明 36→39\n\nCHG-002 材料状态改为已应用并登记重基线调整(archived_tag 取 retirement.derived_repo_tag、OS evidence 缺失保留现值、pending 锚点 0→3、modules.json scope +039);待裁决架构事项 DEC-037/038/039 三行由「未登记(CHG-002 待批)」改为「已登记 pending,裁决未做」;决策批次 §3 与开发计划 §8 登记 A-2 第一包完成及后续包(CHG-003 / 006 延后 op、CHG-004 重基线);基础/README 与总体开发计划的裁决数声明同步为 39 条 / 3 pending,L13 清零。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T08:10:53-07:00"},"CompareURL":"luoanwu/platform-governance/compare/09b641c13abb0c1d020c2c0fe9af7d04888cec9f...2a7ecc8e5116cdc8d9dcf12f5e7e98cab9433e0e","Len":1}...
|
1789657857
|
Edit
Delete
|
|
30686
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"09b641c13 {"Commits":[{"Sha1":"09b641c13abb0c1d020c2c0fe9af7d04888cec9f","Message":"docs(决策): CHG-007 已应用(真源仓 7b4c3ed);登记 A-2 / A-6 / A-7 / CHG-005 未应用及其重基线前置\n\n决策批次 A-1 的 CHG-007 按三份 delta 应用到活跃契约,D5 清零、283/283;材料状态改为已应用。决策批次 §3 与开发计划 §8 登记:CHG-002—006 模拟器以已退役冻结副本为基线而 blocked,需重基线到活跃 Catalog 后逐包应用,这是 CHG-018 条件 A 受控执行面(CHG-005)的前置链。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T08:04:25-07:00"}],"HeadCommit":{"Sha1":"09b641c13abb0c1d020c2c0fe9af7d04888cec9f","Message":"docs(决策): CHG-007 已应用(真源仓 7b4c3ed);登记 A-2 / A-6 / A-7 / CHG-005 未应用及其重基线前置\n\n决策批次 A-1 的 CHG-007 按三份 delta 应用到活跃契约,D5 清零、283/283;材料状态改为已应用。决策批次 §3 与开发计划 §8 登记:CHG-002—006 模拟器以已退役冻结副本为基线而 blocked,需重基线到活跃 Catalog 后逐包应用,这是 CHG-018 条件 A 受控执行面(CHG-005)的前置链。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T08:04:25-07:00"},"CompareURL":"luoanwu/platform-governance/compare/884efad105f1779a3a74c02d83e3359a81a833c0...09b641c13abb0c1d020c2c0fe9af7d04888cec9f","Len":1}...
|
1789657469
|
Edit
Delete
|
|
30684
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"884efad10 {"Commits":[{"Sha1":"884efad105f1779a3a74c02d83e3359a81a833c0","Message":"docs(决策): CHG-018 条件 A 进展——只读面已实现(真源仓 8ced3d1),受控执行面待 CHG-005\n\n登记目录负责人点选的形态与真源仓实现:服务目录快照 + GET /api/platform/catalog + 运维证据快照,两份快照登记进 check:evidence;受控执行面第一条被 CHG-005(待审批、依赖 CHG-001→004)阻塞,条件 A 部分满足。CHG-018 材料状态行、N-10、开发计划 09-17 段与 §8 同步。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T07:58:43-07:00"}],"HeadCommit":{"Sha1":"884efad105f1779a3a74c02d83e3359a81a833c0","Message":"docs(决策): CHG-018 条件 A 进展——只读面已实现(真源仓 8ced3d1),受控执行面待 CHG-005\n\n登记目录负责人点选的形态与真源仓实现:服务目录快照 + GET /api/platform/catalog + 运维证据快照,两份快照登记进 check:evidence;受控执行面第一条被 CHG-005(待审批、依赖 CHG-001→004)阻塞,条件 A 部分满足。CHG-018 材料状态行、N-10、开发计划 09-17 段与 §8 同步。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T07:58:43-07:00"},"CompareURL":"luoanwu/platform-governance/compare/39a93b16cbbddf5405aeda4fbf20804d41b688ac...884efad105f1779a3a74c02d83e3359a81a833c0","Len":1}...
|
1789657126
|
Edit
Delete
|
|
30682
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"39a93b16c {"Commits":[{"Sha1":"39a93b16cbbddf5405aeda4fbf20804d41b688ac","Message":"docs(决策): CHG-018 条件 D 已满足——工作台维护者实名 luoguoguo,阶段 ② 前置只余条件 A\n\nCHG-018 材料状态行登记 D 落实(真源仓 CODEOWNERS /runtime/apps/workbench/ 实名行);N-10、开发计划 09-17 段与 §8、设计方案 §22.1 / §23 同步。余下前置:对外交付设计 §6 两项「缺失」管理接口实现并验收。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T07:41:35-07:00"}],"HeadCommit":{"Sha1":"39a93b16cbbddf5405aeda4fbf20804d41b688ac","Message":"docs(决策): CHG-018 条件 D 已满足——工作台维护者实名 luoguoguo,阶段 ② 前置只余条件 A\n\nCHG-018 材料状态行登记 D 落实(真源仓 CODEOWNERS /runtime/apps/workbench/ 实名行);N-10、开发计划 09-17 段与 §8、设计方案 §22.1 / §23 同步。余下前置:对外交付设计 §6 两项「缺失」管理接口实现并验收。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T07:41:35-07:00"},"CompareURL":"luoanwu/platform-governance/compare/1318ce98ce92ecd6875ea21440c7bb6f15c16ec0...39a93b16cbbddf5405aeda4fbf20804d41b688ac","Len":1}...
|
1789656098
|
Edit
Delete
|
|
30680
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1318ce98c {"Commits":[{"Sha1":"1318ce98ce92ecd6875ea21440c7bb6f15c16ec0","Message":"docs(决策): CHG-018 第二份回执——撤回条件 E,裁定工作台技术栈为 Next.js 静态导出 + React + TypeScript 纯静态 SPA\n\n签署人同日改为沿用现有 Next.js/React/TypeScript 并选纯静态 SPA。CHG-018 材料 §5 追加第二份回执(amends conditions[E],techStackDecision 全字段);状态行、决策批次 §3、N-10、开发计划 09-17 段与 §8、设计方案 §22.1 / §26 同步:阶段 ② 前置余 A(§6 缺失管理接口验收)、D(维护者实名)。Catalog 不动,一致性检查 L4 / L10 / L13 清零。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T07:37:20-07:00"}],"HeadCommit":{"Sha1":"1318ce98ce92ecd6875ea21440c7bb6f15c16ec0","Message":"docs(决策): CHG-018 第二份回执——撤回条件 E,裁定工作台技术栈为 Next.js 静态导出 + React + TypeScript 纯静态 SPA\n\n签署人同日改为沿用现有 Next.js/React/TypeScript 并选纯静态 SPA。CHG-018 材料 §5 追加第二份回执(amends conditions[E],techStackDecision 全字段);状态行、决策批次 §3、N-10、开发计划 09-17 段与 §8、设计方案 §22.1 / §26 同步:阶段 ② 前置余 A(§6 缺失管理接口验收)、D(维护者实名)。Catalog 不动,一致性检查 L4 / L10 / L13 清零。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T07:37:20-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d6deb3aa8539adc597eef52f0fd70b6f852c8525...1318ce98ce92ecd6875ea21440c7bb6f15c16ec0","Len":1}...
|
1789655843
|
Edit
Delete
|
|
30678
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d6deb3aa8 {"Commits":[{"Sha1":"d6deb3aa8539adc597eef52f0fd70b6f852c8525","Message":"docs(决策): CHG-018 签署并应用——C-9 修正为「平台入口由本仓独立工作台承载」,附条件 A/D/E\n\n回执写入 CHG-018 材料 §5(luoanwu 代签,approve-with-conditions,2026-09-17T14:28:37Z)。条件:A 阶段 ② 须待对外交付设计 §6 两项「缺失」管理接口验收;D 工作台维护者实名后才开工,不沿 B-1 代签;E 技术栈另裁、不沿用 Next.js/React,裁决前不开工。默认项 B / C / F 未偏离。\n回写:决策批次 §3 登记修正;待裁决架构事项 N-10 关闭;开发计划 09-17 段与 §8 登记三项前置;设计方案 §22.1 阶段 ② 加前置、§23 维护者行改为实名前置、§26 变更记录加行。Catalog enterprise-experience 不动。一致性检查 L4 / L10 / L13 清零。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T07:29:45-07:00"}],"HeadCommit":{"Sha1":"d6deb3aa8539adc597eef52f0fd70b6f852c8525","Message":"docs(决策): CHG-018 签署并应用——C-9 修正为「平台入口由本仓独立工作台承载」,附条件 A/D/E\n\n回执写入 CHG-018 材料 §5(luoanwu 代签,approve-with-conditions,2026-09-17T14:28:37Z)。条件:A 阶段 ② 须待对外交付设计 §6 两项「缺失」管理接口验收;D 工作台维护者实名后才开工,不沿 B-1 代签;E 技术栈另裁、不沿用 Next.js/React,裁决前不开工。默认项 B / C / F 未偏离。\n回写:决策批次 §3 登记修正;待裁决架构事项 N-10 关闭;开发计划 09-17 段与 §8 登记三项前置;设计方案 §22.1 阶段 ② 加前置、§23 维护者行改为实名前置、§26 变更记录加行。Catalog enterprise-experience 不动。一致性检查 L4 / L10 / L13 清零。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T07:29:45-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d18826fbfe37c9974ac1f075942efd38cd8d1f07...d6deb3aa8539adc597eef52f0fd70b6f852c8525","Len":1}...
|
1789655387
|
Edit
Delete
|
|
30675
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d18826fbf {"Commits":[{"Sha1":"d18826fbfe37c9974ac1f075942efd38cd8d1f07","Message":"docs(决策): CHG-018 材料——修正决策批次 C-9「不建第二个 Portal」,平台工作台同仓独立建设(待签署后应用)\n\nC-9(2026-09-16 签署)裁定一套 Shell 归基座、本仓不建第二个 Portal;09-17 用户确认另建同仓独立工作台,设计文档已改写但裁决记录未改。本包按 CHG-016/017 格式起修正材料:企业业务 Shell 仍归基座、多 Owner Provider 与同一回执不变,只把「不建第二个 Portal」细分为「不建企业业务 Portal;平台自身入口由本仓独立工作台承载」;Catalog enterprise-experience 不动,不建目录、不改 CODEOWNERS。\n\n同步登记:待裁决架构事项 §8A 增 N-10(待签署);决策批次 §3 增 09-17 增补段;开发计划 09-17 增量段把阶段 ② 开工前置改为「CHG-018 签署」;收纳表 doc/ 计数 144→145、CHG 范围补至 018。一致性检查 L4 / L10 / L13 清零。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T05:25:28-07:00"}],"HeadCommit":{"Sha1":"d18826fbfe37c9974ac1f075942efd38cd8d1f07","Message":"docs(决策): CHG-018 材料——修正决策批次 C-9「不建第二个 Portal」,平台工作台同仓独立建设(待签署后应用)\n\nC-9(2026-09-16 签署)裁定一套 Shell 归基座、本仓不建第二个 Portal;09-17 用户确认另建同仓独立工作台,设计文档已改写但裁决记录未改。本包按 CHG-016/017 格式起修正材料:企业业务 Shell 仍归基座、多 Owner Provider 与同一回执不变,只把「不建第二个 Portal」细分为「不建企业业务 Portal;平台自身入口由本仓独立工作台承载」;Catalog enterprise-experience 不动,不建目录、不改 CODEOWNERS。\n\n同步登记:待裁决架构事项 §8A 增 N-10(待签署);决策批次 §3 增 09-17 增补段;开发计划 09-17 增量段把阶段 ② 开工前置改为「CHG-018 签署」;收纳表 doc/ 计数 144→145、CHG 范围补至 018。一致性检查 L4 / L10 / L13 清零。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T05:25:28-07:00"},"CompareURL":"luoanwu/platform-governance/compare/61081e56e2b37ba5e77440b55ef576c366854dba...d18826fbfe37c9974ac1f075942efd38cd8d1f07","Len":1}...
|
1789647930
|
Edit
Delete
|
|
30673
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"61081e56e {"Commits":[{"Sha1":"61081e56e2b37ba5e77440b55ef576c366854dba","Message":"docs(平台治理): 开发计划与总体计划登记四项交付、独立工作台与「分别发布」修订\n\n逐条对照对外交付设计方案后补齐三处外围文档:\n- 基础设施文档/开发计划.md:头部增 2026-09-17 增量段(五步领取顺序,① 文档部分已完成、②—⑤ 待实施,不新设 PF/MS),§8 变更记录增一行登记两仓提交与检查结果。\n- 基础/总体开发计划.md:v5.24 修订条目,把 v5.18 的「一次部署」改为「一个独立项目、分别发布」。\n- 基础/README.md:基础设施仓设计条目下加 2026-09-17 修订指针。\n仅设计登记;工作区一致性检查 L4 / L10 / L13 清零,余 L8 / L9 / L12 为既有问题。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T05:18:02-07:00"}],"HeadCommit":{"Sha1":"61081e56e2b37ba5e77440b55ef576c366854dba","Message":"docs(平台治理): 开发计划与总体计划登记四项交付、独立工作台与「分别发布」修订\n\n逐条对照对外交付设计方案后补齐三处外围文档:\n- 基础设施文档/开发计划.md:头部增 2026-09-17 增量段(五步领取顺序,① 文档部分已完成、②—⑤ 待实施,不新设 PF/MS),§8 变更记录增一行登记两仓提交与检查结果。\n- 基础/总体开发计划.md:v5.24 修订条目,把 v5.18 的「一次部署」改为「一个独立项目、分别发布」。\n- 基础/README.md:基础设施仓设计条目下加 2026-09-17 修订指针。\n仅设计登记;工作区一致性检查 L4 / L10 / L13 清零,余 L8 / L9 / L12 为既有问题。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T05:18:02-07:00"},"CompareURL":"luoanwu/platform-governance/compare/f1ec550575bc3d6331824a3fb8378c5d4656c7ef...61081e56e2b37ba5e77440b55ef576c366854dba","Len":1}...
|
1789647486
|
Edit
Delete
|
|
30671
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"f1ec55057 {"Commits":[{"Sha1":"f1ec550575bc3d6331824a3fb8378c5d4656c7ef","Message":"docs(平台治理): 收纳表 doc/ 计数 140→144、CHG 范围补至 017\n\n对外交付设计落地后执行工作区一致性检查,L13 报 doc/ 声明 140 与 git ls-files 144 不符——差值来自决策批次 2026-09-16 与 CHG-016 / CHG-017 材料四个文件。修正后 L13 清零;剩余 L8(冻结 patch 旧布局)、L9(compose project 撞名)、L12(内核 pin 落后)为既有问题,不属本轮设计范围。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T05:11:00-07:00"}],"HeadCommit":{"Sha1":"f1ec550575bc3d6331824a3fb8378c5d4656c7ef","Message":"docs(平台治理): 收纳表 doc/ 计数 140→144、CHG 范围补至 017\n\n对外交付设计落地后执行工作区一致性检查,L13 报 doc/ 声明 140 与 git ls-files 144 不符——差值来自决策批次 2026-09-16 与 CHG-016 / CHG-017 材料四个文件。修正后 L13 清零;剩余 L8(冻结 patch 旧布局)、L9(compose project 撞名)、L12(内核 pin 落后)为既有问题,不属本轮设计范围。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T05:11:00-07:00"},"CompareURL":"luoanwu/platform-governance/compare/10b674efed0a14c598e1de9de1b5ee255554b434...f1ec550575bc3d6331824a3fb8378c5d4656c7ef","Len":1}...
|
1789647064
|
Edit
Delete
|
|
30622
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"10b674efe {"Commits":[{"Sha1":"10b674efed0a14c598e1de9de1b5ee255554b434","Message":"docs(企业控制面): 同步四项交付与独立工作台设计边界\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T04:20:31-07:00"}],"HeadCommit":{"Sha1":"10b674efed0a14c598e1de9de1b5ee255554b434","Message":"docs(企业控制面): 同步四项交付与独立工作台设计边界\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T04:20:31-07:00"},"CompareURL":"luoanwu/platform-governance/compare/631820930fa53485f2aecebf20f3be971e28badc...10b674efed0a14c598e1de9de1b5ee255554b434","Len":1}...
|
1789644045
|
Edit
Delete
|
|
30452
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"631820930 {"Commits":[{"Sha1":"631820930fa53485f2aecebf20f3be971e28badc","Message":"docs(企业控制面): 目录级 CLAUDE.md(并行会话产出,按原样收入)\n\n目录定位(基础设施层物理目录,只剩真源仓)、两个 git 仓的边界与远端、命令入口指向真源仓、四级文档层级、状态措辞纪律。由另一会话于 2026-09-16 16:31 写入工作树;治理层一致性门禁 root scope L4 / L10 零命中。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:38:09-07:00"}],"HeadCommit":{"Sha1":"631820930fa53485f2aecebf20f3be971e28badc","Message":"docs(企业控制面): 目录级 CLAUDE.md(并行会话产出,按原样收入)\n\n目录定位(基础设施层物理目录,只剩真源仓)、两个 git 仓的边界与远端、命令入口指向真源仓、四级文档层级、状态措辞纪律。由另一会话于 2026-09-16 16:31 写入工作树;治理层一致性门禁 root scope L4 / L10 零命中。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:38:09-07:00"},"CompareURL":"luoanwu/platform-governance/compare/101380fb8b7d4c8b1095d7f3a53cb6df5251a58f...631820930fa53485f2aecebf20f3be971e28badc","Len":1}...
|
1789601891
|
Edit
Delete
|
|
30449
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"101380fb8 {"Commits":[{"Sha1":"101380fb8b7d4c8b1095d7f3a53cb6df5251a58f","Message":"docs(决策): CHG-016 / CHG-017 材料——DEC-010 附条件修订、C19 范围改写(待签署后应用)\n\n决策批次 2026-09-16 五处改案带出的两个受控变更:\n- CHG-016:DEC-010 批准记录附条件修订——Required Check 证据来源改 Gitea(B-2)、CODEOWNERS 实名不再作前置(B-1 长期代签,附代签 SOP 原文)、proposed → active 判据改为首次 staging 晋级记录(B-4);decisions.delta.json 只加 note 不改 status。\n- CHG-017:成本与容量治理平台范围并入外部客户订阅计量与出账(C-15),能力表 C19 增 C19.07 / C19.08、C02.01 扩外部客户开户路径、边界表与机器读者处置;不改活跃 Catalog,不建服务。\n批次记录 §3 登记行同步。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:29:59-07:00"}],"HeadCommit":{"Sha1":"101380fb8b7d4c8b1095d7f3a53cb6df5251a58f","Message":"docs(决策): CHG-016 / CHG-017 材料——DEC-010 附条件修订、C19 范围改写(待签署后应用)\n\n决策批次 2026-09-16 五处改案带出的两个受控变更:\n- CHG-016:DEC-010 批准记录附条件修订——Required Check 证据来源改 Gitea(B-2)、CODEOWNERS 实名不再作前置(B-1 长期代签,附代签 SOP 原文)、proposed → active 判据改为首次 staging 晋级记录(B-4);decisions.delta.json 只加 note 不改 status。\n- CHG-017:成本与容量治理平台范围并入外部客户订阅计量与出账(C-15),能力表 C19 增 C19.07 / C19.08、C02.01 扩外部客户开户路径、边界表与机器读者处置;不改活跃 Catalog,不建服务。\n批次记录 §3 登记行同步。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:29:59-07:00"},"CompareURL":"luoanwu/platform-governance/compare/c641151481665a321840ee8081e09101a3b74360...101380fb8b7d4c8b1095d7f3a53cb6df5251a58f","Len":1}...
|
1789601402
|
Edit
Delete
|
|
30447
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"c64115148 {"Commits":[{"Sha1":"c641151481665a321840ee8081e09101a3b74360","Message":"docs(决策): 决策批次 2026-09-16——31 项待裁事项一次签署并登记\n\n目录负责人经会话逐条签署:A 批 7 条登记与收口全部批准(CHG-007、CHG-002 → 003 → 006、CHG-001 追认、审批记录终态 merged、门禁脚本按 SHA 引用、permissions.json 离开 draft、CHG-004 阶段 2 分两批);B 批:单人代签长期化、CI 通道 B 案、19 个 PR 按登记顺序合并、Catalog 保持 proposed 到 staging 晋级;C 批:Q01—Q10 按收口方案采纳,X06 由 identity 作业编排,G-3 自建限流镜像、方法白名单回收入口层,prod 批准人必须 human,drift 升阻断,碰撞卷 dump 后删,内核一步升 0.22.0,订阅计费并入 C19,OpenBao dev 立即启用,OS 先接决策 API,嗨设允许自建,Alertmanager + 企业 IM;D 批:staging TLS 先 internal 再 ACME,§6 偏差六条按建议。五处改案及后果见批次 §1A。\n\n登记:待裁决架构事项 CHG-001 / N-02 / N-07 三行改为已裁决;开发计划 §8 新增变更记录(偏差 #5 / #23 / #31 随之关闭)。未做:DEC-010 附条件修订与 C19 范围改写各需一个 CHG。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:08:02-07:00"}],"HeadCommit":{"Sha1":"c641151481665a321840ee8081e09101a3b74360","Message":"docs(决策): 决策批次 2026-09-16——31 项待裁事项一次签署并登记\n\n目录负责人经会话逐条签署:A 批 7 条登记与收口全部批准(CHG-007、CHG-002 → 003 → 006、CHG-001 追认、审批记录终态 merged、门禁脚本按 SHA 引用、permissions.json 离开 draft、CHG-004 阶段 2 分两批);B 批:单人代签长期化、CI 通道 B 案、19 个 PR 按登记顺序合并、Catalog 保持 proposed 到 staging 晋级;C 批:Q01—Q10 按收口方案采纳,X06 由 identity 作业编排,G-3 自建限流镜像、方法白名单回收入口层,prod 批准人必须 human,drift 升阻断,碰撞卷 dump 后删,内核一步升 0.22.0,订阅计费并入 C19,OpenBao dev 立即启用,OS 先接决策 API,嗨设允许自建,Alertmanager + 企业 IM;D 批:staging TLS 先 internal 再 ACME,§6 偏差六条按建议。五处改案及后果见批次 §1A。\n\n登记:待裁决架构事项 CHG-001 / N-02 / N-07 三行改为已裁决;开发计划 §8 新增变更记录(偏差 #5 / #23 / #31 随之关闭)。未做:DEC-010 附条件修订与 C19 范围改写各需一个 CHG。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:08:02-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ecc77d987dbd2cfd9e00a3655fdd68efcd994bcc...c641151481665a321840ee8081e09101a3b74360","Len":1}...
|
1789601223
|
Edit
Delete
|
|
30445
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ecc77d987 {"Commits":[{"Sha1":"ecc77d987dbd2cfd9e00a3655fdd68efcd994bcc","Message":"chore(reports): 回绑 @ ff7d2f5——登记门禁读到带 provenance 的上一份报告后 9/9 通过\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:50:27-07:00"}],"HeadCommit":{"Sha1":"ecc77d987dbd2cfd9e00a3655fdd68efcd994bcc","Message":"chore(reports): 回绑 @ ff7d2f5——登记门禁读到带 provenance 的上一份报告后 9/9 通过\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:50:27-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ff7d2f5f21e82dfae2a35ea0b09a14b075fdf6b3...ecc77d987dbd2cfd9e00a3655fdd68efcd994bcc","Len":1}...
|
1789570230
|
Edit
Delete
|
|
30443
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ff7d2f5f2 {"Commits":[{"Sha1":"ff7d2f5f21e82dfae2a35ea0b09a14b075fdf6b3","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ abf3da1(三份均带 provenance)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:49:26-07:00"},{"Sha1":"abf3da1333775705216233cf7bc7b06eb5f202b7","Message":"feat(governance): reports 登记与归档(PG-20/21/22)、两道门禁补测试(PG-15)、同名文档订正(PG-32)\n\n- reports/登记.json:顶层 39 份受控报告逐份登记生产者 / 消费者 / 绑定 / 保留(latest 3 / evidence 35 / frozen 1);新门禁 check-report-registry.mjs(R1—R6)登记为统一入口阻断位,夹具 8 例\n- 223 份无人引用的报告(含 67 份 .log)按 9 个家族 git mv 到 reports/archive/2026-09-16/,顶层 262 → 39;.gitignore 不再收新 .log\n- run-foundation-gates / check-gate-consumption 的报告带 provenance(lib/report-provenance.mjs,忽略自身 latest 报告判脏)\n- check-idp-token-contract 增 --fixture、audit-platform-openings 增 DERIVED_STATUS_PATH(只供测试注入),各补正向 + 负向用例(翻转夹具 / 注入幽灵仓即红)\n- 两份《业务发展视角的基础设施与公用应用缺失》是同名不同文:文首互指,基础设施文档/README 迁入登记订正\n- 缺失梳理 §12.3 第四轮记录、§10.2 划掉;基础/README 工具清单;收纳表计数刷新\n\n治理层测试 354(348 过 / 0 失败 / 6 跳过);一致性门禁基线 3 条不变。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:49:12-07:00"}],"HeadCommit":{"Sha1":"ff7d2f5f21e82dfae2a35ea0b09a14b075fdf6b3","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ abf3da1(三份均带 provenance)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:49:26-07:00"},"CompareURL":"luoanwu/platform-governance/compare/975091270ad2bdd234020c8ee9d6e2e7c8aff281...ff7d2f5f21e82dfae2a35ea0b09a14b075fdf6b3","Len":2}...
|
1789570170
|
Edit
Delete
|
|
30441
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"975091270 {"Commits":[{"Sha1":"975091270ad2bdd234020c8ee9d6e2e7c8aff281","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ 80ed264\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:40:55-07:00"},{"Sha1":"80ed26441d4f74bb90d5c3eabc05191929f60cb9","Message":"feat(governance): 撤销四个候选平台(CHG-015)——审批记录 withdrawn 终态、候选门禁改读归档、控制面目录清空;第三轮执行记录\n\n- 目录负责人裁决撤销 企业搜索 / 外部连接器 / 数据治理与隐私 / 开发者自助 四个候选:M0 材料整体 git mv 到 基础设施文档/docs/已撤销候选/(50 文件),.gitignore 去掉四条放行\n- CHG-001 审批记录 merged → withdrawn(保留 merge 块,新增 withdrawal 块,冻结物一字未动);就绪检查器增第二终态:merge 块允许、withdrawal 块必需可核验、expectedFormalWithdrawn(21 / 19 / 36 / 0 pending、四项不在册、四条 DEC rejected)、--assert-settled 视 WITHDRAWN 已定\n- lib/workspace.mjs 新增 candidateWithdrawal / candidatePlatformRoot / candidatePlatformDir:契约兼容基线、M0 契约验证、12 项消费者契约测试、devx 夹具改读归档目录;决策评审包门禁报撤销态退出 0;统一审计与 L5 不再把冻结候选清单当待登记项;统一审计 counts 增 rejected\n- 终态测试改为 merged / withdrawn 各自的负向断言;就绪终态用例接受 WITHDRAWN;评审包护栏按撤销态解析引用\n- 文档:基础/CLAUDE.md 口径改 21 个在册项目;基础/README、企业控制面/README、待裁决 N-02 记撤销;裁决数 / 项目数声明与收纳表刷新;63 处链接改指归档位置(L4 = 0);已撤销候选/README 与 CHG-015 材料\n- 缺失梳理 §12.2 第三轮执行记录;移除路径 §9 补记四仓全退;一致性门禁登记基线改为 3 条(L8 1 / L9 1 / L12 1)\n\n治理层测试 341(335 过 / 0 失败 / 6 跳过)。企业控制面/ 此后只剩 README 与真源仓。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:40:41-07:00"},{"Sha1":"551e33221dab86ea217c77009e985585d10cb431","Message":"chore(governance): 应用与契约注册中心退役(CHG-014)——18 个派生仓全部退役,active / archived 档清空\n\n- 派生仓 HEAD 56cff29 打 retired-20260916 推 Gitea;bundle 仓备份-2026-09-16/控制面__应用与契约注册中心.bundle;四份目录级文档(含只在磁盘的 开发经验.md)搬入 已退役平台/应用与契约注册中心/;目录停放待 Owner rm\n- 派生仓状态:active → retired(18),四档合计仍 19(missing 1 + retired 18);三道按 active + archived 读盘的门禁 0/0,登记表 note / reason 改写;workspace-evidence-status 测试改为 expected 0 时发现数也须为 0\n- 企业控制面/README 铁律段、四档表、派生仓段与 基础/CLAUDE.md 修订按\"全部退役\"回写;已退役平台/README 加行;四份活文档链接改指归档位置;收纳表计数刷新\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:26:08-07:00"},{"Sha1":"ea86f2e16d8c34f645feeef170b3dee4e9ac92fb","Message":"test(governance): 扫描面仓数门槛按 2026-09-16 退役后的嵌套仓数下调\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:16:54-07:00"},{"Sha1":"dc1e3065f2b0482ad006780cc61e69fbeedb0e92","Message":"chore(governance): 统一交付平台退役(CHG-012)——两处部分覆盖由真源仓 check-promotion R11 / R12 关闭后退\n\n- 派生仓 HEAD 5a638a9 打 retired-20260916 推 Gitea;bundle 仓备份-2026-09-16/控制面__统一交付平台.bundle;目录级文档搬入 已退役平台/统一交付平台/(链接按新位置改写);目录停放待 Owner rm\n- 派生仓状态:active → retired(17),现存派生仓 1 个;企业控制面/README 四档表与派生仓段、已退役平台/README、覆盖度对照 §3 两行改 ✅ + §4 结论行 + §5.2 关闭 + §5.5 说明\n- 四份活文档指向交付目录的链接改指归档位置;收纳表计数刷新\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:12:31-07:00"}],"HeadCommit":{"Sha1":"975091270ad2bdd234020c8ee9d6e2e7c8aff281","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ 80ed264\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:40:55-07:00"},"CompareURL":"luoanwu/platform-governance/compare/fce1694e3624325b36af65052cccc775189c96aa...975091270ad2bdd234020c8ee9d6e2e7c8aff281","Len":9}...
|
1789562459
|
Edit
Delete
|
|
30381
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"fce1694e3 {"Commits":[{"Sha1":"fce1694e3624325b36af65052cccc775189c96aa","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ 6a31052\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:44:43-07:00"},{"Sha1":"6a31052e5f6b709b400d275210b53f1057e6475c","Message":"feat(governance): 机密反向兜底门禁、一致性门禁 L13 与 L3/L10 扩面、统一入口 skipped 与恒定输出、测试报告改写临时目录、统一审计落盘;并行会话约定\n\n缺失梳理 §10.2 可直接执行项(记录见 平台治理缺失全面梳理 §12.1):\n- PG-18 check-tracked-secrets.mjs:规则取自根 .gitignore 机密段,18 仓 13375 份受跟踪文件 0 命中;登记为统一入口阻断位;输出不回显命中值\n- PG-17 L13 治理层数字声明(裁决数 / 平台项目数对活跃 Catalog,收纳表文件数对 git ls-files);L10 增「尚未裁决 / 待裁决」;L3 增旧根层名;开发计划梳理不再按历史豁免、platform-contracts 冻结副本按历史豁免;仓发现抽到 lib/workspace-repositories.mjs\n- PG-13 / 14 run-foundation-gates:skipped 显形(audit-foundation 出 FOUNDATION_GATES_SKIPPED)、sameAsPrevious / unchangedRuns / constantOutput(lib/gate-run-history.mjs)\n- PG-23 / 24 FOUNDATION_REPORT_DIR:pnpm test 写临时目录,受跟踪报告 mtime 不变(测试自证);audit-foundation 落盘 基础目录统一审计.latest.json 并带 provenance(pnpm run audit)\n- PG-13 五例就绪 SKIP 改为在合并提交父提交重建的基线上实跑(tests/helpers/pre-merge-formal-root.mjs);重建不成立→新发现 PG-41(冻结的 governance-linter.test.mjs 摘要不对应任何提交)\n- PG-34 .gitea/workflows/governance.yml(不阻断);PG-36 基础/CLAUDE.md 并行会话约定\n- 顺带:L3/L10 首轮抓到的过期措辞与旧根路径已改;时空事实流转/README.md 补登记落点;派生仓计数措辞;平台治理/README 收纳表按 ls-files 刷新\n\n治理层测试 339(333 过 / 0 失败 / 6 跳过);pnpm check 阻断性 8/8。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:44:27-07:00"},{"Sha1":"af23c76f6a51a0b03da9d4740d5a8cd1a5040e4d","Message":"chore(governance): 集中观测平台退役(CHG-009)——派生仓 retired 档 15 个、目录级文档归档、控制面与梳理文档回写\n\n- 派生仓状态.json:集中观测平台由 archived 移入 retired(tag 沿用 archived-20260910,bundle 在仓备份-2026-09-15),archived 档只剩应用群网关;note 注明现存派生仓 3 个\n- CHG-009 材料(README + platform-projects.delta.json):Owner 2026-09-16 裁决 G-6 密码学核验与采样不作阻塞,证据改指 Collector 配置 / check:otel / 蓝图(已应用到活跃 Catalog,enterprise-platform 仓另提交)\n- 目录级文档搬到 基础设施文档/docs/已退役平台/集中观测平台/(CLAUDE.md 改名 .archived)\n- 企业控制面/README、缺失梳理 M-27、完整梳理、移除路径 §9、覆盖度对照、同步计划等按 15 个已退役回写\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:44:27-07:00"}],"HeadCommit":{"Sha1":"fce1694e3624325b36af65052cccc775189c96aa","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ 6a31052\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:44:43-07:00"},"CompareURL":"luoanwu/platform-governance/compare/82dbfa4669a7ff239f4b58827dd4f5999738ea46...fce1694e3624325b36af65052cccc775189c96aa","Len":3}...
|
1789555527
|
Edit
Delete
|
|
30320
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"82dbfa466 {"Commits":[{"Sha1":"82dbfa4669a7ff239f4b58827dd4f5999738ea46","Message":"docs(governance): 退役目录已物理删除;CHG-008 README 链接修正\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T00:16:48-07:00"},{"Sha1":"c501adad7a1d918b9f3b4a8b971e52c5d3b466d2","Message":"chore(governance): 派生仓退役 14 个——Catalog 退役形态、retired 档、文档归档、CHG-003/006/008 证据改指\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T00:13:22-07:00"},{"Sha1":"bdf4a0495174cab16def1b947eda69a46eb5412a","Message":"docs(governance): 缺失梳理 M-10 / M-16 与 README 观测行按 OTel 产生端与 Grafana 仪表板落地回写\n\n- M-10 runtime 接 OTel SDK:已落(enterprise-platform df436c1),dev 常驻 runtime 已切镜像,Tempo / Loki / Prometheus 三处实测收到;\n 余项改写为指标租户 / 应用维度、Node 进程指标、Caddy / LiteLLM 两个产生端\n- M-16:SLO 面板已落(四份文件供给仪表板,58 条查询实测编译),没有产生端的 SLO 不建面板;告警规则与值班仍为零\n- README 六框表观测行:划掉\"没有一个产生端在发\",改写仍缺项\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T23:18:54-07:00"},{"Sha1":"5b1ccb397c4d6101592017e63feb54de975a3dbe","Message":"feat(governance): 工作区门禁 L11 FRAMEWORK_VERSION_DRIFT——目录级文档声明的框架版本必须等于仓内 package.json 且有 tag;缺失梳理补执行记录\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:53:50-07:00"},{"Sha1":"6b19bcd9889100b9e864507263204587e61e7dd2","Message":"docs(governance): 企业控制面缺失全面梳理(七层 34 条)、完整梳理 §0 补记、README 六框表补写四个权威模块的登记落后\n\n- 新增 企业控制面缺失全面梳理-2026-09-15:按运行 / 接线 / 登记 / 交付 / 收口 / 消费 / 安全七层,逐域对照能力表 138 条与横切 15 条,\n 34 条编号缺口按\"只差 Owner 一个动作 / 裁决已齐要写代码 / 要先裁决\"分组;本轮处置与三轮只读分析记在 §9\n- 完整梳理 §0 追加改口:12/12 镜像已 digest 固定、9 份契约无路由、22 条未合并分支、catalog:drift 只记录不阻断、证据新鲜度补登记后的新数字\n- README 六框表:身份与权限 / 观测与审计 / 事实与契约三行补写 Catalog 仍 candidate_e0 与进程内端口壳;开头加缺失梳理链接\n- 只提交本会话的三个文件;平台治理/基础/scripts 与 tests 下另一会话的改动不在本次提交内\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:53:24-07:00"}],"HeadCommit":{"Sha1":"82dbfa4669a7ff239f4b58827dd4f5999738ea46","Message":"docs(governance): 退役目录已物理删除;CHG-008 README 链接修正\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T00:16:48-07:00"},"CompareURL":"luoanwu/platform-governance/compare/553813dbe9541b78f89eca3151c117473b8444f4...82dbfa4669a7ff239f4b58827dd4f5999738ea46","Len":7}...
|
1789543223
|
Edit
Delete
|
|
30163
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"553813dbe {"Commits":[{"Sha1":"553813dbe9541b78f89eca3151c117473b8444f4","Message":"chore(governance): 刷新门禁运行与消费两份报告\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-15T03:43:16-07:00"},{"Sha1":"cfe7f98accc01c95ed0c024d4e2d28e8ceb6ecfa","Message":"docs(governance): 企业控制面梳理与两份框架变更请求的增补落盘(另一会话的工作区改动)\n\n本提交内容不是本会话所写,是基础设施侧会话留在工作区的 6 个文档改动,按\"提交推送\"\n一并落盘。内容自洽、交叉引用齐备,且已静置 34 分钟(其 03:07 提交后未再动):\n\n- 企业控制面/README.md:能力框状态表重构为\"只记已验证的事实与仍缺的,不记计划\",\n 并加一句关键澄清——\"派生目录里现在剩下的是脚手架\"这句只对目录成立,不等于规则\n 也没了:18 个仓的独有规则已全部迁出真源仓(模块域 6 处、契约包域 9 处)\n- 基础设施文档/docs/企业控制面完整梳理-2026-09-15.md、采纳形态覆盖度对照-2026-09-14.md:\n 横向盘点与 G-* 缺口判据的增补\n- 工程基础框架/框架变更请求-治理报告结论字段-2026-09-15.md、迁移指纹分类-2026-09-14.md\n- 平台治理/基础/派生仓状态.json\n\n`派生仓状态.json` 是门禁读的数据真源,落盘前跑了全套:306 测试 301 通过 0 失败。\n\n本会话未改动其中任何一个字。若对方其实仍在编辑,按本仓惯例以后续提交订正,\n不 rebase 已推送内容。\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-15T03:43:11-07:00"},{"Sha1":"241fc27b274606dee0b3198bb9d855e5a65a17c3","Message":"feat(governance): 本门禁补 11 条自证探针 —— D11 那把尺子先量自己\n\nD11 判别人\"有没有证明过自己会红\",而本门禁自己一条负向探针都没有。按它自己的\n判据,它属于\"未经验证\"那一档。\n\n夹具测试不能替代探针:测试跑的是构造输入,探针跑的是**本工作区真实数据的形状**。\n两者失效的方式不同——测试挂了没人能提交,探针哑了说明判定对真实数据不成立,\n而那正是 U-31(:503 单方向)/ U-33(:781 前提写死)/ U-36(\"跑不起来\"记成\"0 例\")\n的共同死法。\n\n11 条探针成对设计,正向要报、反向不得报(只做一半等于没测):\n d2 倒挂要报 / 公用应用持有不得报\n d5 DEC 全批仍 draft 要报 / 有未决 DEC 不得报\n d9 必填差异要报 / 只差 description 不得报\n d8 源码改动要让证据失效 / 只动 reports/ 不得失效\n 另有 d9 副本分叉、d11 哑探针、d4 无事实出口四条单向\n\n造不出探针时(本工作区缺相应数据)记 `skipped` 并写明原因,**绝不记\ndetected: false**——那会把\"跑不起来\"伪装成\"门禁没抓到\",正是 U-36 批评的谎报。\nskipped 条目不带 detected 字段,collectProbes 不收,D11 也就不会把它算成哑探针。\n\n哑探针报 D0 让本门禁自己失败,不只是写进报告——探针哑火意味着判定能力丢失,\n比它报出的任何一条都严重。\n\n实测 11 条全部命中,0 哑 0 跳过;夹具 51/51。\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-15T03:39:59-07:00"}],"HeadCommit":{"Sha1":"553813dbe9541b78f89eca3151c117473b8444f4","Message":"chore(governance): 刷新门禁运行与消费两份报告\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-15T03:43:16-07:00"},"CompareURL":"luoanwu/platform-governance/compare/a8c2c315c5987714bc084f534c364ca525639562...553813dbe9541b78f89eca3151c117473b8444f4","Len":3}...
|
1789469000
|
Edit
Delete
|
|
30157
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"a8c2c315c {"Commits":[{"Sha1":"a8c2c315c5987714bc084f534c364ca525639562","Message":"chore(governance): 清扫后重跑统一门禁入口并回写报告\n\n阻断性 7/7 通过;仅记录 3 道仍失败,但内容已变:\ncheck-workspace-consistency 22 → 4(L8 1 / L9 2 / L10 1),\ncheck-domain-layer 19 → 16(D3 三条已关),audit-platform-openings 5 条不变。\n\n剩下 25 条没有一条能由执行者单方面关闭:L8 要重做 CHG-001 补丁并重新基线;L9 两条\n卡在\"api-nestjs 与 enterprise-idp 两个 project 的共用卷里数据属于谁\";L10 最后一条\n在 active 的 Scope 仓内,而该仓正因\"收尾提交连带改文档\"被判红,随手改一句话正好\n制造它警告的失败;D5 = CHG-007(材料齐备、模拟器绿,等 Catalog Owner);D9 等 PF-04\n阶段 2;D2 / D4 / D6 / D7 / D10 是跨层的数据与装载动作;D11 要给工单 20 道、设备云\n17 道门禁各补负向探针;audit-platform-openings 五条等 E1 或那次 A / B / C 取舍。\n\n两份报告不带 provenance,工作树中另一会话的三份在途改动不影响本次结论。\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-15T03:07:04-07:00"},{"Sha1":"cc81a45fecbf4ea14e8b9198270061f14ab89544","Message":"docs(governance): 企业控制面的横向梳理、十八个派生仓的移除路径、门禁清扫记录\n\n三份只读盘点,均不改 Catalog、不改模块状态、不下裁决。\n\n- 企业控制面完整梳理:把目录、真源、规则落点、Catalog 登记、门禁、运行与缺口\n 合到一张表上。实测 18 个派生仓的独有规则已全部迁出(模块域 6、契约包域 9、\n 网关与观测两处由组件配置承接),并标出六处已被事实推翻的旧陈述——README 的\n 架构图六框表、项目完整能力表 E02/E06、CHG-003 材料的机器事实基线。\n\n- 十八个派生仓的移除路径:把\"移除\"拆成冻结写入 / 解除登记依赖 / 物理删除三件事。\n 历史安全性已不是问题(18 仓全部有 Gitea 远端且 origin/main == HEAD,另有 18 份\n bundle);94% 的体积与治理无关(18 GB / 947,810 个磁盘文件,受控文件只有 5,486\n 个)。按 delta 语义逐仓模拟 CHG-002/003/006 合并后,9 个仓证据残余归零、9 个不归零,\n 此前无任何文档给过这个分档。四类阻塞里只有 directory 双向绑定没有任何变更包覆盖。\n\n- 三道仅记录门禁的清扫记录:本轮清扫的执行记录与未关项的归属。\n\n当日实跑推翻一条旧记录:CHG-002/003/006/007 四个模拟器全部 passed、formalMutated\nfalse,而 CHG-006 README 记的 2026-09-14 实测是三个 blocked、\"CHG-001 重做是前置\"。\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-15T03:05:39-07:00"},{"Sha1":"edfd2ec2814c85007a5019d02e1d6b0d0b258061","Message":"fix(governance): 三道仅记录门禁的清扫 —— 报出来的每一条都应当是能直接去改的\n\n`check-workspace-consistency` 22 → 4。三道 report-only 门禁长期全红,正落在\n`门禁消费登记.json` 自己写的那句判词里:门禁能跑、结果无人看,于是稳定在\"永远红\"\n或\"永远绿\",两种都不携带信息。\n\n门禁改造两处:\n\n- L3 / L10 放过冻结派生仓。13 个 archived-20260910 仓由 check-archived-derived-repos\n (阻塞档)断言 tag = HEAD ∧ 工作树 clean,改一个字节它就红——也就是说 L3 / L10 在\n 那里报出来的东西没有一条能直接去改,与 L10 自己立的收敛原则正相反。新增\n frozenDerivedRepoPrefixes / isFrozenDerivedRepo,只放过 archived 一档:active 的\n 5 个仍在视野内,清扫后剩下的唯一一条 L10 就在其中,没被误放过。\n\n- 冻结物的二次替换由 L2 改归 L8。L2 要求改掉字符串、L7 要求字节与 sha256 相符,\n 同一份文件两个相反的要求。L8(摘要相符、内容却仍是旧布局)本来就是为这种情形\n 存在的,其处置口径——重做变更包并重新基线——才执行得了。staleLayoutHits 增收\n 二次替换,L2 跳过审批记录登记的冻结物。该条仍是红的,只是红在正确的位置。\n\nD3 的前提订正:旧判据照抄契约 linter 的 productId === app.id ∧ productVersion ===\napp.version,而 DEC-009(2026-09-12 批准)写明\"三清单独立 Schema / Owner / 版本,\n跨清单只存引用\"——把一条已批准的裁决反过来写。linkSatisfiability 按新前提重写,\n唯一剩下的不可满足情形是\"产品列表里多于一个产品\"。契约侧的规则重写另仓提交。\n\n正文订正 22 处:DEC-010 / 031 / 032 于 2026-09-10 批准,其余 27 条于 2026-09-12\n决策会批准,各处按裁决原文改写,把\"卡在裁决\"与\"卡在没做\"分开。集中观测那条不是\n滞后而是被事实推翻——Collector 已在 stack/otel 部署并由 check:otel 守着。\n\n五个文件加 `一致性门禁豁免: L10` 并写明理由:两份 DEC 草案与待裁决架构事项逐条\n转录裁决原文,其中\"Workload Identity 待 DEC-024 后复评\"是裁决自带的条件条款,不是\n对 DEC-024 审批状态的断言,不得为了让门禁变绿而改写。\n\n回灌台账 U-33 关闭,两次订正的轨迹保留:第一次把\"规则写错了\"误判成\"各仓没补数据\",\n第二次才查到规则与已批准的裁决冲突——判定前提本身可能是错的,这类缺口按\"谁没做\"\n派活会一直派错人。\n\n核验:tests/workspace-consistency 19 → 24,tests/domain-layer 47/47,平台治理/基础\n全量 302(297 通过 / 5 跳过);run-foundation-gates 阻塞档 7/7;\ncheck-archived-derived-repos 13/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-15T03:05:31-07:00"}],"HeadCommit":{"Sha1":"a8c2c315c5987714bc084f534c364ca525639562","Message":"chore(governance): 清扫后重跑统一门禁入口并回写报告\n\n阻断性 7/7 通过;仅记录 3 道仍失败,但内容已变:\ncheck-workspace-consistency 22 → 4(L8 1 / L9 2 / L10 1),\ncheck-domain-layer 19 → 16(D3 三条已关),audit-platform-openings 5 条不变。\n\n剩下 25 条没有一条能由执行者单方面关闭:L8 要重做 CHG-001 补丁并重新基线;L9 两条\n卡在\"api-nestjs 与 enterprise-idp 两个 project 的共用卷里数据属于谁\";L10 最后一条\n在 active 的 Scope 仓内,而该仓正因\"收尾提交连带改文档\"被判红,随手改一句话正好\n制造它警告的失败;D5 = CHG-007(材料齐备、模拟器绿,等 Catalog Owner);D9 等 PF-04\n阶段 2;D2 / D4 / D6 / D7 / D10 是跨层的数据与装载动作;D11 要给工单 20 道、设备云\n17 道门禁各补负向探针;audit-platform-openings 五条等 E1 或那次 A / B / C 取舍。\n\n两份报告不带 provenance,工作树中另一会话的三份在途改动不影响本次结论。\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-15T03:07:04-07:00"},"CompareURL":"luoanwu/platform-governance/compare/1a4d98035c3dd75f82c2ac63f1c7e557ddb764d6...a8c2c315c5987714bc084f534c364ca525639562","Len":3}...
|
1789468023
|
Edit
Delete
|
|
30106
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1a4d98035 {"Commits":[{"Sha1":"1a4d98035c3dd75f82c2ac63f1c7e557ddb764d6","Message":"chore(governance): 刷新门禁运行报告 —— D11 落地后领域层由 17 条增至 19 条\n\n本次 run-foundation-gates 的结果:阻断性 7/7 通过,仅记录 3。\ncheck-domain-layer 由 17 条增至 19 条,增量是 D11 新报的两条——工单 20 道、\n设备云 17 道门禁一条负向探针都没有,从未证明过自己会红。条数上升不是退步:\n此前这 37 道门禁的状态是不可知,现在是已知未验证。\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-15T00:59:22-07:00"}],"HeadCommit":{"Sha1":"1a4d98035c3dd75f82c2ac63f1c7e557ddb764d6","Message":"chore(governance): 刷新门禁运行报告 —— D11 落地后领域层由 17 条增至 19 条\n\n本次 run-foundation-gates 的结果:阻断性 7/7 通过,仅记录 3。\ncheck-domain-layer 由 17 条增至 19 条,增量是 D11 新报的两条——工单 20 道、\n设备云 17 道门禁一条负向探针都没有,从未证明过自己会红。条数上升不是退步:\n此前这 37 道门禁的状态是不可知,现在是已知未验证。\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-15T00:59:22-07:00"},"CompareURL":"luoanwu/platform-governance/compare/407fe08edcf66ba3b09c111db4d1824ff9dd58bb...1a4d98035c3dd75f82c2ac63f1c7e557ddb764d6","Len":1}...
|
1789459164
|
Edit
Delete
|
|
30105
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"407fe08ed {"Commits":[{"Sha1":"407fe08edcf66ba3b09c111db4d1824ff9dd58bb","Message":"feat(governance): D11 —— 门禁有没有证明过自己会红\n\n本轮反复撞上同一个形态:规则写了,但触发条件让它对真实数据永远不成立。\nU-31(:503 只判反方向)、U-33(:781 把\"一应用一产品同 id 同版本\"写死成前提)、\nU-36(把\"跑不起来\"写成\"0 例通过\")三条各自独立,共同特征是**门禁一直是绿的,\n而绿得没有信息量**。\n\n仓里本来就有对症机制:负向探针——故意注入一个该被拦的缺陷,断言门禁确实拦住了。\n知识云的 docs-truth 正是靠它自报\"数字负向探针只命中 7/9,门禁可能是假绿\"。\n\nD11 把这个机制提到工作区一层,两类判定严重程度不同:\n- 哑探针(detected 非 true):门禁自己注入的缺陷没被自己抓到 → 假绿,硬失败\n- 无探针:从未证明过自己会红 → 不等于坏,但等于未经验证\n\n实测:434 条探针哑火 0 条,机制本身健康;但覆盖极不对称——\n 知识云 15/24 道门禁有探针、HR 11/25,**工单 0/20、设备云 0/17**\n后两仓的 37 道门禁从未证明过自己会红。\n\n探针字段名各仓不统一(negativeProbes / probes / *ProbeResults / shadowNegativeProbes),\n按**形状**递归收集而非字段名白名单:白名单会随新门禁漂移,而漂移的方向恰好是\n\"漏掉新探针\"——那正是本判据要防的。detected 只认严格 true,缺字段 / null /\n字符串 \"true\" 一律算哑火。\n\n夹具用例 47/47。\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-15T00:57:04-07:00"}],"HeadCommit":{"Sha1":"407fe08edcf66ba3b09c111db4d1824ff9dd58bb","Message":"feat(governance): D11 —— 门禁有没有证明过自己会红\n\n本轮反复撞上同一个形态:规则写了,但触发条件让它对真实数据永远不成立。\nU-31(:503 只判反方向)、U-33(:781 把\"一应用一产品同 id 同版本\"写死成前提)、\nU-36(把\"跑不起来\"写成\"0 例通过\")三条各自独立,共同特征是**门禁一直是绿的,\n而绿得没有信息量**。\n\n仓里本来就有对症机制:负向探针——故意注入一个该被拦的缺陷,断言门禁确实拦住了。\n知识云的 docs-truth 正是靠它自报\"数字负向探针只命中 7/9,门禁可能是假绿\"。\n\nD11 把这个机制提到工作区一层,两类判定严重程度不同:\n- 哑探针(detected 非 true):门禁自己注入的缺陷没被自己抓到 → 假绿,硬失败\n- 无探针:从未证明过自己会红 → 不等于坏,但等于未经验证\n\n实测:434 条探针哑火 0 条,机制本身健康;但覆盖极不对称——\n 知识云 15/24 道门禁有探针、HR 11/25,**工单 0/20、设备云 0/17**\n后两仓的 37 道门禁从未证明过自己会红。\n\n探针字段名各仓不统一(negativeProbes / probes / *ProbeResults / shadowNegativeProbes),\n按**形状**递归收集而非字段名白名单:白名单会随新门禁漂移,而漂移的方向恰好是\n\"漏掉新探针\"——那正是本判据要防的。detected 只认严格 true,缺字段 / null /\n字符串 \"true\" 一律算哑火。\n\n夹具用例 47/47。\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-15T00:57:04-07:00"},"CompareURL":"luoanwu/platform-governance/compare/86a7e52c6b5843851881a91625bc944a51df2205...407fe08edcf66ba3b09c111db4d1824ff9dd58bb","Len":1}...
|
1789459149
|
Edit
Delete
|
|
30100
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"86a7e52c6 {"Commits":[{"Sha1":"86a7e52c6b5843851881a91625bc944a51df2205","Message":"chore(governance): 刷新门禁运行与消费两份报告\n\n本会话多轮运行 run-foundation-gates 后的最新一次结果:阻断性 7/7 通过,仅记录 3\n(audit-platform-openings / check-workspace-consistency / check-domain-layer,\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-15T00:54:26-07:00"},{"Sha1":"de0ebe04b4a27a0bba7f8981c635193a19d8e902","Message":"docs(framework): 框架 0.19.0 的变更请求受理记录落盘(另一会话的工作区改动)\n\n本提交的内容不是本会话所写,是框架侧会话留在工作区的 5 个文档改动,按\"全面提交\"\n一并落盘。内容自洽且已静置 35 分钟(最后修改 00:19,提交于 00:54):\n\n- 基础设施仓框架变更请求-2026-09-12.md:受理表由五项全\"待\"改为 FR-1 受理并落地\n (0.19.0)、FR-4 / FR-5 受理(实现在下一个提交)、FR-2 / FR-3 暂不受理并写明理由\n (FR-2 触及写链四同边界与 check:write-guard 规则形态,框架侧无法独立判绿;\n FR-3 的 Fact 信封 v1 是 additionalProperties: false,加字段不能自称向后兼容,\n 属契约裁决)\n- CLAUDE.md:状态行推进到 v0.19.0,补 0.17.0 / 0.18.0 两节\n- 开发计划.md:补 0.17.0(compose 身份与端口,F14)与 0.18.0(G20 运维平面)两段进展\n- README.md:补 compose 变更请求的受理结论与\"扩散未决\"纪律\n- 框架变更请求-compose身份与端口-2026-09-14.md:受理结论回填\n\n本会话未改动其中任何一个字,只做落盘。若框架侧会话对措辞或时机有异议,按本仓惯例\n以后续提交订正,不 rebase 已落盘内容。\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-15T00:54:21-07:00"},{"Sha1":"3cffd5406c379159d0074622c550ce5d4a81b17a","Message":"docs(governance): 回灌台账 U-37 / U-38 —— 接真实 DB 一轮跑出的两条下层缺口\n\n本轮把四个领域仓的证据等级从\"静态\"往\"真实 DB\"推,基座(base-framework-postgres-1 /\nredis-1)已在运行,按本目录\"每轮新建空验收库\"的口径逐仓建独立库。结果:\n\nU-37 工单仓在文档所述基座上根本跑不起来。prisma migrate deploy 在\n20260827015000_ticket_ai_pgvector 失败(P3009)——基座镜像 postgres:16-alpine 的\npg_available_extensions 里没有 vector 扩展。知识云用 DOUBLE PRECISION[] 绕开了\n同一需求所以不受影响,工单需要真扩展。二选一:换镜像(影响所有共用该实例的项目)\n或改列形态(影响检索实现)。在此之前工单的证据等级封顶在\"静态\"。\n\nU-38 HR 的 check-outbox-multi-instance 接上真实 DB 后可复现失败:\ndispatched=120, observed=0, subscriberStatus=ready,双后端一致,连跑两次相同。\n门禁跑完了全程,不属\"缺环境变量跑不起来\"那一类。本仓 .env 没有任何 REDIS/DATABASE\n项,无法判断是缺少未文档化的 relay/worker 配置还是真实缺陷——不在治理层臆断,\n证据已如实落盘,根因归仓 Owner。\n\n顺带记下:G15 库名守卫工作正常。首次用 juhai_hr_parity_* 被三条门禁正确拒绝\n(\"Database … does not belong to juhai_ai_hr_system\"),前缀按 package.json 的 name\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-15T00:50:36-07:00"},{"Sha1":"b4c4c61f455cd46e6c13bb28beb6ac506fee936a","Message":"docs(governance): 回灌台账 U-36 —— 门禁在缺实例时把\"跑不起来\"写成\"0 例通过\"\n\n知识云 docs-truth 报 3 处文档漂移,根因不在文档:CLAUDE.md 记\nbackend-behavior-parity 为 28 例,而机器真源被写成 0。\ncheck-backend-behavior-parity.mjs:140 写 `raw?.metrics?.… ?? 0`——vitest 因缺\nDATABASE_URL / REDIS_URL 跑不起来时不产出报告,于是\"跑不起来\"被记成\"0 例通过\",\n再经 check-docs-truth.mjs:292 变成文档漂移。\n\ndocs-truth 自己已经察觉(第 3 条违规:\"动态数字负向探针只命中 7/9,门禁可能是\n假绿\"),但它只能报征状。\n\n**没有直接修**:最小改法(指标记 null + docs-truth 跳过比较)会让 :381 的负向探针\n失效,docs-truth 反而变成真的假绿。这是\"证据不可用\"如何穿过门禁链表达的设计问题,\n不是两行修补;治理层正在做同构的事(4d3efd5 拆开「报告没写结论」与「结论不合格」),\n本条等该口径定稿后按同一形态落到各仓。\n\n§3 第 9 条补一行:四个仓的需实例门禁共 8 条有同类风险;口径定稿前这些报告不应\n提交——本轮 HR 3 份、知识云 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-15T00:41:51-07:00"},{"Sha1":"812ed430b9066c1fedebd7dd3aa5b0138f2ed644","Message":"fix(governance): D8 的构造性缺陷 —— 提交证据这个动作本身会让证据失效\n\n实测发现:门禁在 clean HEAD 上生成报告,报告记下当时的 gitSha;把报告提交,HEAD\n随即前进到新提交,于是报告永远指向父提交。按 D8 原本\"必须绑定当前 HEAD\"的字面规则,\n**落盘那一刻证据就自动作废**——这条判据不可能被满足。四个领域仓刚提交完新鲜证据,\nD8 依旧报 4 条,就是这个缺陷的现场。\n\n正确口径是看被验收的内容有没有变:从证据所绑的提交走到 HEAD,若沿途每个提交只动\nreports/,则源码与配置一字未改,证据仍然当前。这与 report-provenance.mjs 把\nreports/*.latest.json 排除在 worktreeDirty 之外是同一条道理,一个作用于工作树、\n一个作用于提交历史。\n\n不放宽到\"内容相似\":沿途只要有一个提交碰了 reports/ 以外的东西,证据即失效;\n查不出文件清单的提交(如合并提交)一律判失效。\n\n修正后 D8 由 4 条降为 **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-15T00:36:22-07:00"}],"HeadCommit":{"Sha1":"86a7e52c6b5843851881a91625bc944a51df2205","Message":"chore(governance): 刷新门禁运行与消费两份报告\n\n本会话多轮运行 run-foundation-gates 后的最新一次结果:阻断性 7/7 通过,仅记录 3\n(audit-platform-openings / check-workspace-consistency / check-domain-layer,\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-15T00:54:26-07:00"},"CompareURL":"luoanwu/platform-governance/compare/cdb7f45657484b0ee996962444a060ca1f33c305...86a7e52c6b5843851881a91625bc944a51df2205","Len":42}...
|
1789458887
|
Edit
Delete
|
|
30064
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"cdb7f4565 {"Commits":[{"Sha1":"cdb7f45657484b0ee996962444a060ca1f33c305","Message":"fix(governance): 两条迁移残留门禁归零——评审包路径基准与平台数口径\n\n两个脚本都不在任何测试覆盖里,所以迁移把它们打坏后一直没人发现。\n\n1) check-new-platform-decision-review:评审包校验完全空转\n\n局部变量名叫 workspaceRoot,实际指的是 平台治理/基础 目录。evidenceRefs 与\nDecisionCatalog 的 source 在 98ec9e9 的数据改写中已变为**工作区相对**路径\n(平台治理/基础/… 与 企业控制面/…),脚本却仍在剥 `^基础/` 前缀再按 基础/ 解析,\n于是拼出 平台治理/基础/平台治理/基础/…,首条即抛\nDECISION_REVIEW_PACKET_INVALID: missing evidence,退出码恒为 1。\n\n实测这不是\"少数几条失效\":按工作区根解析 11/11 命中,按旧的 基础/ 根解析 0/11\n(7 条 evidenceRefs + 4 条 ADR source)——整条证据链检查一条都没跑到。\n\n改为引入 lib/workspace.mjs 的 workspaceRoot(),把两处按工作区根解析;\n局部变量改名 foundationRoot,评审包自身文件仍相对它读取。去掉前缀剥离:\n数据若再退回旧形态,应当直接红,而不是被一个正则悄悄吞掉。\n\n与 simulate-chg-005 的 `let mirror;` 是同一类——回灌台账 C-14\n\"一个旧目录拆成多个新目录时,机械前缀替换不成立\"的最后一个未收口实例。\n\n2) audit-ci-gates:与 派生仓状态.json 并存两套平台数口径\n\n冻结核心里 DEFAULT_EXPECTED_PLATFORM_COUNT = 19 成文于企业 IdP 并入\nenterprise-platform 之前。并入后 派生仓状态.json 把它登记为 missing,现场只剩\nactive 5 + archived 13 = 18,本审计恒报 `目标平台数量应为 19,实际 18`;而同一份\n真源驱动的 audit-platform-openings 这项却通过——一个工作区两套口径。\n\n冻结仓 archived-20260910 不可改,但 runCiGateAudit 只是 auditPlatformSet +\nformatAuditSummary 的便捷封装,且 auditPlatformSet 本就接受 expectedPlatformCount,\n只是便捷入口没透传。兼容入口在治理仓、可自由改,于是改为直接组合这两个导出,\n期望值从 派生仓状态.json 现算(只数 active + archived,missing 是\"没有派生仓\"的\n登记,计入会把口径推回 19)。\n\n验证:\n- check-new-platform-decision-review → 退出码 0,\n \"4 independent pending decisions,17 pending signoffs,0 runtime/service authorizations\"\n- audit-ci-gates → 退出码 0,18/18 通过,expectedPlatformCount=18,globalProblems 空,\n --json 输出形状不变\n- 冻结仓 统一交付平台/base-framework 工作树 git status 为空,一个字节未动;\n check-archived-derived-repos 仍 13/13\n- audit-foundation 阻塞项 7 → 4(另三项由并行进行的 CHG-001 修订 8 收口)\n\n遗留:这两个脚本仍无测试覆盖,正是它们能长期静默失效的原因;\n建议后续补两例(路径基准、口径来源)到 平台治理/基础/tests/。\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-14T23:02:55-07:00"},{"Sha1":"52ac2e9762313f122e49915c094f903634b34932","Message":"feat(governance): 修订 8 四项审批落库并排定窗口,合并闸门重新开启\n\n承接 a64e30a(改指活跃真源)。修订 7 的审批因目标真源有问题被收回(615c017),\n本次针对修订 8 重走:四个角色均由 luoanwu 审批 APPROVED,窗口排在\n2026-09-15T05:59:53Z,仍是先排窗口后录回执以避开 record 脚本注释警告的顺序陷阱。\n\n与修订 7 的关键差别:本包钉的是 DEC-010 A 案裁定的物理真源\n企业控制面/enterprise-platform/contracts,镜像验证 274/274、官方 check 在\n合并态转绿,合并后统一审计的 CANDIDATES_NOT_REGISTERED 可真正消除——\n而修订 7 合并进的是待移除的冻结副本,三项 Catalog 阻断一个都不会掉。\n\n结果:mergeGate.eligible=true、就绪度 READY、blockingReasons 清空;\ncatalogMutationAuthorized=true,runtime / serviceCreation / deployment 仍 false。\n包指纹 1fdc2e16…efdd87 全程未变(审批记录不在冻结清单内)。\n\n回执四份置于 approvals/,各引变更请求、DEC-033—036 评审包、发布运行手册三份证据。\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-14T23:00:25-07:00"},{"Sha1":"a3e9052a1a31cac006fe47f3b03f913c849a39b8","Message":"fix(governance): 合并演练测试的真源与被测脚本同源\n\n测试把 formalRoot 硬编码为 resolve(foundationRoot,\"..\",\"platform-contracts\"),\n而 a64e30a 已把 simulate-new-platform-catalog-merge.mjs 改走 activeContractsRoot()。\n两边分叉后 5 条用例全红:被测脚本拒绝的是活跃真源,测试递进去的却是冻结副本,\n\"refuses formal targets\" 一类断言自然落空。\n\n改为与脚本同源解析(workspaceRoot + activeContractsRoot),目标真源再变时\n只改 workspace.json 一处,测试不必跟着改。5 条用例恢复通过。\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-14T22:54:41-07:00"},{"Sha1":"a64e30a7108cf09938763809eac75534defc6ba3","Message":"feat(governance): CHG-001 重基线为修订 8,目标真源改指活跃契约\n\n承接 615c017(收回四项审批)与核对记录 3689711:CHG-001 整包钉在\n平台治理/platform-contracts(冻结待移除),而 DEC-010 A 案裁定的物理真源是\n企业控制面/enterprise-platform/contracts。合并到冻结副本不会消除统一审计的\nCANDIDATES_NOT_REGISTERED,且修订 7 补丁对活跃真源 --fuzz=0 时\ntest/governance-linter.test.mjs 4 个 hunk 失败 1 个。本次完成改指。\n\n- 新增 activeContractsRoot()(读 workspace.json 的 paths.activeContracts),\n check-new-platform-catalog-change-readiness / verify-new-platform-change /\n simulate-new-platform-catalog-merge 三者改走它。simulate 尤其必要:\n 它的 formalRoot 正是「禁止写入正式目录」的保护对象,不改会放行写入活跃真源\n- 完整补丁按活跃真源重新渲染,fileCount 仍 4(scripts/governance-linter.mjs\n 依旧无差异),被拒的那个 hunk 按活跃真源的上下文重新落位\n\n顺带修掉三处只在新环境下暴露的缺陷:\n1. 新增测试的 platformLayerEntries 与 linter 一样用 Dirent.isDirectory(),\n 在镜像里把 19 个平台目录误判为普通文件,三条断言集体反向(linter 侧见\n enterprise-platform 2d7265c)\n2. 「真实的未登记平台目录必须仍被报出」依赖环境里恰好存在未登记目录,\n 而本变更登记了全部 4 个候选——合并态下该断言必然落空。改为确定性构造:\n 从克隆注册表摘掉一个已登记平台,断言它被报出,原意(豁免不得消音真实治理债)不变\n3. verify 的回滚基线断言把 check 的汇总行计入错误数,在活跃真源上成了 5 !== 4。\n 改为只计 [PLATFORM_PROJECT_UNREGISTERED],另行断言不得出现其他类型错误;\n 报告里的 formal_catalog_root 由写死的 'platform-contracts' 改为动态相对路径\n\n验证:镜像 274/274、官方 check 在合并态转绿、回滚逐字节、正式目录未动;\n就绪度 READY→BLOCKED 而非 INVALID,即技术侧就绪、只差四方审批与变更窗口。\n修订 7 指纹 6e2e69d6…ffa97f 作废,修订 8 指纹 1fdc2e16…efdd87。\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-14T22:53:46-07:00"}],"HeadCommit":{"Sha1":"cdb7f45657484b0ee996962444a060ca1f33c305","Message":"fix(governance): 两条迁移残留门禁归零——评审包路径基准与平台数口径\n\n两个脚本都不在任何测试覆盖里,所以迁移把它们打坏后一直没人发现。\n\n1) check-new-platform-decision-review:评审包校验完全空转\n\n局部变量名叫 workspaceRoot,实际指的是 平台治理/基础 目录。evidenceRefs 与\nDecisionCatalog 的 source 在 98ec9e9 的数据改写中已变为**工作区相对**路径\n(平台治理/基础/… 与 企业控制面/…),脚本却仍在剥 `^基础/` 前缀再按 基础/ 解析,\n于是拼出 平台治理/基础/平台治理/基础/…,首条即抛\nDECISION_REVIEW_PACKET_INVALID: missing evidence,退出码恒为 1。\n\n实测这不是\"少数几条失效\":按工作区根解析 11/11 命中,按旧的 基础/ 根解析 0/11\n(7 条 evidenceRefs + 4 条 ADR source)——整条证据链检查一条都没跑到。\n\n改为引入 lib/workspace.mjs 的 workspaceRoot(),把两处按工作区根解析;\n局部变量改名 foundationRoot,评审包自身文件仍相对它读取。去掉前缀剥离:\n数据若再退回旧形态,应当直接红,而不是被一个正则悄悄吞掉。\n\n与 simulate-chg-005 的 `let mirror;` 是同一类——回灌台账 C-14\n\"一个旧目录拆成多个新目录时,机械前缀替换不成立\"的最后一个未收口实例。\n\n2) audit-ci-gates:与 派生仓状态.json 并存两套平台数口径\n\n冻结核心里 DEFAULT_EXPECTED_PLATFORM_COUNT = 19 成文于企业 IdP 并入\nenterprise-platform 之前。并入后 派生仓状态.json 把它登记为 missing,现场只剩\nactive 5 + archived 13 = 18,本审计恒报 `目标平台数量应为 19,实际 18`;而同一份\n真源驱动的 audit-platform-openings 这项却通过——一个工作区两套口径。\n\n冻结仓 archived-20260910 不可改,但 runCiGateAudit 只是 auditPlatformSet +\nformatAuditSummary 的便捷封装,且 auditPlatformSet 本就接受 expectedPlatformCount,\n只是便捷入口没透传。兼容入口在治理仓、可自由改,于是改为直接组合这两个导出,\n期望值从 派生仓状态.json 现算(只数 active + archived,missing 是\"没有派生仓\"的\n登记,计入会把口径推回 19)。\n\n验证:\n- check-new-platform-decision-review → 退出码 0,\n \"4 independent pending decisions,17 pending signoffs,0 runtime/service authorizations\"\n- audit-ci-gates → 退出码 0,18/18 通过,expectedPlatformCount=18,globalProblems 空,\n --json 输出形状不变\n- 冻结仓 统一交付平台/base-framework 工作树 git status 为空,一个字节未动;\n check-archived-derived-repos 仍 13/13\n- audit-foundation 阻塞项 7 → 4(另三项由并行进行的 CHG-001 修订 8 收口)\n\n遗留:这两个脚本仍无测试覆盖,正是它们能长期静默失效的原因;\n建议后续补两例(路径基准、口径来源)到 平台治理/基础/tests/。\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-14T23:02:55-07:00"},"CompareURL":"luoanwu/platform-governance/compare/4b9218ca6b938f802870c9b048b2fba70245c666...cdb7f45657484b0ee996962444a060ca1f33c305","Len":4}...
|
1789452186
|
Edit
Delete
|
|
30056
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"4b9218ca6 {"Commits":[{"Sha1":"4b9218ca6b938f802870c9b048b2fba70245c666","Message":"docs(governance): §8 改写为 CHG-001 收口后的实际状态——审批已收回、改指活跃真源\n\n当晚 CHG-001 状态在 5 分钟内翻转两次,本文前两版各记了其中一个中间态:\n- a140998(22:42:31)记 PENDING\n- bd63d88 订正为 READY(据 c571477,22:42:10)\n- 615c017(22:46:57)目录负责人收回全部四项审批、关闭合并闸门\n\n现按收口状态改写,中间态不再保留为结论:四项 PENDING、\nmergeGate.eligible=false、catalogMutationAuthorized=false,回执连同\narchive-manifest 归档至 reports/catalog-package-archive/6e2e69d6…/\napprovals-withdrawn/ 并标明「不得转移到修订 8」。\n\n同时把「两份 catalog 的结构性矛盾」一条从「需裁决」改为「已裁决」:\nCHG-001 整包钉在 平台治理/platform-contracts,而 DEC-010 A 案明写独立\nGit-first 真源由基础设施仓 contracts/ 承担。核对记录 3689711 指出按现状\n合并会把四个候选登记进待移除副本、三项 Catalog 阻断不会消除,且修订 7\n补丁对活跃真源 --fuzz=0 --dry-run 有 1 个 hunk 失败。决定改指活跃真源、\n重基线为修订 8。该矛盾由并发会话独立发现并当场裁决,非本文促成,两条\n路径结论一致,作交叉印证记录。\n\n并发说明段补一条教训,与 §6、回灌台账 C-17 同源:治理文档里任何「现状」\n行都有半衰期,这次是 21 秒;引用状态须写明观测时刻,据状态做决定须当场\n实跑,不得引用他文。\n\n门禁:L4 链接失效 0。L7 当前 2 条不符(simulate-new-platform-catalog-merge.mjs\n与完整变更.patch),成因是并发会话在途重算修订 8 摘要,615c017 已预告,\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-14T22:49:16-07:00"},{"Sha1":"a06705a0015517aa5968c14d12bbfe631918868b","Message":"fix(governance): 白名单补上反向兜底——机密类文件的排除规则\n\n迁移方案 §8.4 教训 2 写着\"既查该纳入的是否纳入,也查不该纳入的是否排除,\n凭证泄露正源于只做了前一半\"。L1—L9 把九类迁移破坏都固化成了机器检查,\n唯独这一类没有落地——门禁代码里 gitignore / secrets / .env 出现次数均为 0,\n全工作区也无任何机密扫描(无脚本、无 git hook、无 CI)。\n\n用 git check-ignore 实测白名单反向,破绽恰好集中在 平台治理/ 这一层本身\n(也就是 09-14 真正泄过密的那一层):doc/、基础/、基础/scripts/、基础/reports/、\n基础设施文档/、platform-contracts/ 六个放行区,9 类机密文件名里有 8 类会被纳入。\n其它层安全不是因为有防护,而是白名单本来就窄(!/数字员工OS/*.md 只放行 .md)。\n\n根因是兜底段只有两条规则,而 *.env 只匹配以 .env 结尾的名字——\n.env.production / .env.local 都不匹配,.pem / .p12 / id_rsa / secrets.* 则根本没规则。\n\n本次补:.env.*(配 .env.example / .env.*.example 例外)、私钥与证书五类、\nid_rsa* / id_ed25519*、.netrc、secrets.* 与 credentials.* 各三种扩展名。\n\n.npmrc 有意不列:全工作区 8 处合法跟踪(enterprise-platform 仓根与 runtime/、\n报价仓 sites/、嗨赞造意 output/),它是 registry 配置不是机密。\n\n验证:\n- git ls-files | git check-ignore --stdin → 空,无任何已跟踪文件被新规则命中,\n 改动纯预防,不需要先清历史\n- 缺口测绘重跑:六个放行区由\"8 类可纳入\"降为\"仅 .npmrc\"\n- 逐条抽查:doc/.env.production、reports/dump.pem、基础/.env.local、\n decisions/id_rsa、platform-contracts/credentials.json、scripts/.netrc 全部已排除;\n .env.example 仍正常放行\n\n加规则前先扫过现状:密钥类文件名被跟踪 0 个(30+ 仓逐个 git ls-files)、\n硬编码密钥(sk- / AKIA / ghp_ / BEGIN PRIVATE KEY / xox*)0 处、\n未跟踪但不被忽略的机密文件 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-14T22:48:34-07:00"}],"HeadCommit":{"Sha1":"4b9218ca6b938f802870c9b048b2fba70245c666","Message":"docs(governance): §8 改写为 CHG-001 收口后的实际状态——审批已收回、改指活跃真源\n\n当晚 CHG-001 状态在 5 分钟内翻转两次,本文前两版各记了其中一个中间态:\n- a140998(22:42:31)记 PENDING\n- bd63d88 订正为 READY(据 c571477,22:42:10)\n- 615c017(22:46:57)目录负责人收回全部四项审批、关闭合并闸门\n\n现按收口状态改写,中间态不再保留为结论:四项 PENDING、\nmergeGate.eligible=false、catalogMutationAuthorized=false,回执连同\narchive-manifest 归档至 reports/catalog-package-archive/6e2e69d6…/\napprovals-withdrawn/ 并标明「不得转移到修订 8」。\n\n同时把「两份 catalog 的结构性矛盾」一条从「需裁决」改为「已裁决」:\nCHG-001 整包钉在 平台治理/platform-contracts,而 DEC-010 A 案明写独立\nGit-first 真源由基础设施仓 contracts/ 承担。核对记录 3689711 指出按现状\n合并会把四个候选登记进待移除副本、三项 Catalog 阻断不会消除,且修订 7\n补丁对活跃真源 --fuzz=0 --dry-run 有 1 个 hunk 失败。决定改指活跃真源、\n重基线为修订 8。该矛盾由并发会话独立发现并当场裁决,非本文促成,两条\n路径结论一致,作交叉印证记录。\n\n并发说明段补一条教训,与 §6、回灌台账 C-17 同源:治理文档里任何「现状」\n行都有半衰期,这次是 21 秒;引用状态须写明观测时刻,据状态做决定须当场\n实跑,不得引用他文。\n\n门禁:L4 链接失效 0。L7 当前 2 条不符(simulate-new-platform-catalog-merge.mjs\n与完整变更.patch),成因是并发会话在途重算修订 8 摘要,615c017 已预告,\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-14T22:49:16-07:00"},"CompareURL":"luoanwu/platform-governance/compare/615c017a32da032ecaeb00215d8b8b5418d9b122...4b9218ca6b938f802870c9b048b2fba70245c666","Len":2}...
|
1789451359
|
Edit
Delete
|
|
30051
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"615c017a3 {"Commits":[{"Sha1":"615c017a32da032ecaeb00215d8b8b5418d9b122","Message":"fix(governance): 收回 CHG-001 四项审批并关闭合并闸门,回执按 SOP 归档\n\n修订 7 的四项 APPROVED(2026-09-15T05:40:40Z)与变更窗口(05:40:30Z)建立在\n一个目标真源有问题的包上:CHG-001 整包钉在 平台治理/platform-contracts,而\nDEC-010 已批准的 A 案明写「独立 Git-first 真源由基础设施仓的 contracts/\n工作区承担」,平台治理/README.md 也把前者定性为「冻结待移除,阶段 2 物理移除」。\n\n按现状合并的后果(核对记录 3689711):四个候选会登记进一个待移除的副本,\n而 audit-foundation 读 paths.activeContracts,三项 Catalog 阻断\n(CANDIDATES_NOT_REGISTERED / FORMAL_CATALOG_CHECK_FAILED /\nCANDIDATE_CATALOG_GATE_BLOCKED)不会消除;修订 7 补丁对活跃真源\npatch --fuzz=0 --dry-run 时 test/governance-linter.test.mjs 4 个 hunk 失败 1 个。\n\n目录负责人决定改指活跃真源、重基线为修订 8。按审批录入 SOP §5「包指纹或\n冻结文件漂移 → 全部旧回执失效,重新冻结包并重新审批」,本次先收口人的决定:\n\n- 四份回执连同 archive-manifest 归档到\n reports/catalog-package-archive/6e2e69d6…/approvals-withdrawn/,\n 记明失效原因与「不得转移到修订 8」,approvals/ 清空\n- 审批记录回到审批前形态:四项 PENDING、approver/decidedAt/evidenceRef/\n receiptSha256 置空、changeWindow.scheduledAt 置空(owner 与 rollbackOwner\n 按门禁要求保留 Catalog Owner)、mergeGate.eligible=false、\n authorizations.catalogMutationAuthorized 由 true 回到 false\n- revisionNote 追加【2026-09-14 收回】段,写明依据与修订 8 的前置\n\n包内容未动:revision 仍为 7,指纹 6e2e69d6…a84ffa97f 不变。修订 8 的重基线\n须等活跃真源 contracts/ 工作树 clean(当前有 src/domain/ 九个域包等在途实现),\n否则冻结摘要会钉住半成品。\n\n验证:tests/new-platform-approval-recording 7/7 恢复(此前 4 例因审批落库而\n红——这些用例把正式审批记录当夹具读)。tests/new-platform-catalog-readiness\n仍有 6 例红,成因是并行会话在途把 simulate-new-platform-catalog-merge.mjs\n改指 activeContractsRoot 而修订 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-14T22:46:57-07:00"},{"Sha1":"8832e2257d0c10cbf5cec5516604e46f1ee2e922","Message":"docs(governance): 提交 CHG-001 目标真源裁决请求,并登记进待裁决索引\n\n四份回执已签、就绪门禁 READY,但合并目标钉在冻结副本 平台治理/platform-contracts/,\n而 DEC-010 批准的真源是 企业控制面/enterprise-platform/contracts/。裁决请求列出\n三个方案与各自代价,推荐 A(改指活跃真源、重基线修订 8),并说明为什么必须现在定:\n\n包指纹覆盖 formalBaselineDigests,改指即换指纹,四份回执随之全部失效;现在定最多\n作废 4 份,等 CHG-002—005 也按冻结副本验证完再定,作废的是整条链。\n\n支撑推荐的实测:仅活跃真源独有 26 个文件、仅冻结副本独有 0 个(冻结副本是内容上的\n真子集,测试 3 vs 17);catalogs 五份里只有 platform-projects.json 不同,差异正是活跃\n真源已补、冻结副本仍缺的 7 条 Fact 前置;完整补丁对活跃真源 dry-run 只有\ntest/governance-linter.test.mjs 的 1 个 hunk 需重渲染,其余三份干净可落。\n\n另附两个连带问题:冻结副本的去留,以及就绪门禁按 platformContracts 还是\nactiveContracts 读取。本文不自行选定,裁决写入 §6 后方可执行。\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-14T22:45:21-07:00"},{"Sha1":"bd63d88dc431e4fd106e5ba45404114c460bd264","Message":"docs(governance): 订正核对文档中 CHG-001 的状态——并发提交已使其转 READY\n\n上一条提交(a140998,22:42:31)的 §8 写于 c571477(22:42:10)之前,相隔\n21 秒,因此把 CHG-001 记成「四方审批 PENDING + 变更窗口未排」。实跑现状为\nREADY:pending 0、blockingReasons 空、packageValid=true。\n\n订正三处:§8 对照表 CHG-001 行、check.mjs 行、以及「未做」清单中 4 条\nPLATFORM_PROJECT_UNREGISTERED 的归因(改为待 Catalog Owner 在已排定窗口内\n执行合并;合并前 check.mjs 仍 exit=1 属预期)。\n\n并在节末加并发说明:本文核验跑在 22:30—22:42 之间,期间另有会话提交;\n3689711(22:41:49)独立记录了同一处结构性矛盾——CHG-001 钉在已被 DEC-010\n否定的目标真源上,与本文结论一致。\n\n这正是本文 §6 与回灌台账 C-17 所指的同类错误:陈述与机器基线脱节。区别是\n这次间隔 21 秒而非四天。\n\nL4 链接失效 0、L7 冻结物 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-14T22:45:13-07:00"},{"Sha1":"a140998ef2b0be91dcd2a416547b5f2ff9e4beaf","Message":"docs(governance): 架构图评审核对——27 项「缺失」24 项已有归属,真缺口 3 条\n\n新增 平台治理/架构图分析与仓库现状核对-2026-09-14.md:对一份纯图面架构评审\n意见逐条核对仓库现状。结论是该意见方向对、归因错——它判断「实施就绪度低」\n成立,但归因为「规范没定义清楚」;实际规范层相当完整(32 条 DEC 全部已批、\n四类带负向测试的机器契约),缺的是运行时(活 Catalog 21 条平台条目\nimplemented_e2 为 0)。其建议的「六条架构铁律」六条全部已存在于产品纲领且\n措辞更严;建议的试点链与 §11.2 重复。真缺口 3 条:注入防护规范、评测门禁\n实现(均卡 Q02 收口)、Agent Memory 保留与删除语义(待 OS Owner 认领)。\n\n误判源头是评审读了 平台治理/platform-contracts/README.md——它自述为真源却\n停在 2026-09-10(「5 approved / 27 pending」「DEC-010/012 尚未裁决」),而\n机器基线已是 32 approved / 0 pending。据此加两处时效提示:\n\n- platform-contracts/README.md 顶部加冻结待移除副本警示,指向 activeContracts\n- 产品纲领 §4 带日期快照加提示,并指回 决策批次-2026-09-12.md\n\n两处均不改写正文,遵回灌台账 §4 维护规则。README 不在 CHG-001 任何冻结摘要\n内——packageFingerprintForDocument 只哈希审批文档声明的 changeId + 三组摘要\n列表 + expectedFormalBefore/After,不扫描目录。\n\n回灌台账追加 C-17 / C-18。C-18 纠正 §1 第 1 条「CHG-001 包指纹以该目录为准,\n改动会触发就绪度重基线」的不精确表述:冻结面是 14 份具名文件,不是整个目录;\n动手前实算比对,不要按目录名推断。\n\n本文同时纠正两处过期结论:企业应用群挖掘分析-2026-09-14-2142.md(21:45)的\n第 3、4 条已被其后提交处理(CHG-001 22:02 重基线为修订 7、治理测试转绿);\n本文初稿据冻结副本把 causation_id 误记为必填,实为可选(ENVELOPE_OPTIONAL_FIELDS),\n因果链判定由 A 降为 A/C。\n\n一致性门禁 L1—L8 仍 0(本次新增链接已纳入扫描,1530 条);L9 2 条为既有,\n已有框架变更请求 aed8f8c。\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-14T22:42:31-07:00"},{"Sha1":"c571477584e0f194316d78c8c49768d2303d2d7e","Message":"feat(governance): CHG-001 四项审批落库并排定变更窗口,合并闸门开启\n\n修订 7 技术侧此前已就绪(就绪度 BLOCKED 而非 INVALID),五条阻塞全部是人的\n决定。本次按决策落库:四个角色均由 luoanwu 审批 APPROVED,变更窗口排在\n2026-09-15T05:40:30Z。\n\n- changeWindow.scheduledAt 先于回执写入。record 脚本注释警告过反序的后果:\n 四份回执录完后再排窗口,录入器对已录回执返回 NOOP 并在重算闸门前退出,\n \"UNSCHEDULED: change window\" 将再无脚本可清。先排窗口后录回执可避开该陷阱,\n dry-run 已验证第一份录入后该条即消失\n- 四份回执置于 平台治理/基础/approvals/,逐份通过 validator(VALID,各引 3 份证据:\n 变更请求、DEC-033—036 正式评审包、发布运行手册),再逐份 --commit\n- .gitignore 放行 approvals/:此前被 /平台治理/基础/*/ 一律忽略,而审批记录的\n receiptSha256 正指回这些文件,不入库则 mergeGate 的证据链断在仓外\n\n结果:status pending_approval → approved_for_catalog_merge;\nmergeGate.eligible=true、blockingReasons 清空;就绪度 BLOCKED → READY;\naudit-foundation 阻塞项 7 → 5(CANDIDATE_CATALOG_GATE_BLOCKED 消解)。\n授权边界未越线:catalogMutationAuthorized=true,而 runtime / serviceCreation /\ndeployment 三项仍为 false——登记目录不等于宣告平台可用。\n\n回执 comment 记录了一处已知偏差:变更请求正文写「79/79 测试通过」,本轮独立复验\nverify-new-platform-change.mjs 实为 80/80(rollbackByteIdentical=true、\nformalUnchanged=true)。偏差方向是增加用例,经决策不为此重基线为修订 8,\n在回执中声明知悉。\n\n包指纹 6e2e69d6…ffa97f 全程未变:审批记录不在 frozenInputs/frozenEvidence 之列。\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-14T22:42:10-07:00"}],"HeadCommit":{"Sha1":"615c017a32da032ecaeb00215d8b8b5418d9b122","Message":"fix(governance): 收回 CHG-001 四项审批并关闭合并闸门,回执按 SOP 归档\n\n修订 7 的四项 APPROVED(2026-09-15T05:40:40Z)与变更窗口(05:40:30Z)建立在\n一个目标真源有问题的包上:CHG-001 整包钉在 平台治理/platform-contracts,而\nDEC-010 已批准的 A 案明写「独立 Git-first 真源由基础设施仓的 contracts/\n工作区承担」,平台治理/README.md 也把前者定性为「冻结待移除,阶段 2 物理移除」。\n\n按现状合并的后果(核对记录 3689711):四个候选会登记进一个待移除的副本,\n而 audit-foundation 读 paths.activeContracts,三项 Catalog 阻断\n(CANDIDATES_NOT_REGISTERED / FORMAL_CATALOG_CHECK_FAILED /\nCANDIDATE_CATALOG_GATE_BLOCKED)不会消除;修订 7 补丁对活跃真源\npatch --fuzz=0 --dry-run 时 test/governance-linter.test.mjs 4 个 hunk 失败 1 个。\n\n目录负责人决定改指活跃真源、重基线为修订 8。按审批录入 SOP §5「包指纹或\n冻结文件漂移 → 全部旧回执失效,重新冻结包并重新审批」,本次先收口人的决定:\n\n- 四份回执连同 archive-manifest 归档到\n reports/catalog-package-archive/6e2e69d6…/approvals-withdrawn/,\n 记明失效原因与「不得转移到修订 8」,approvals/ 清空\n- 审批记录回到审批前形态:四项 PENDING、approver/decidedAt/evidenceRef/\n receiptSha256 置空、changeWindow.scheduledAt 置空(owner 与 rollbackOwner\n 按门禁要求保留 Catalog Owner)、mergeGate.eligible=false、\n authorizations.catalogMutationAuthorized 由 true 回到 false\n- revisionNote 追加【2026-09-14 收回】段,写明依据与修订 8 的前置\n\n包内容未动:revision 仍为 7,指纹 6e2e69d6…a84ffa97f 不变。修订 8 的重基线\n须等活跃真源 contracts/ 工作树 clean(当前有 src/domain/ 九个域包等在途实现),\n否则冻结摘要会钉住半成品。\n\n验证:tests/new-platform-approval-recording 7/7 恢复(此前 4 例因审批落库而\n红——这些用例把正式审批记录当夹具读)。tests/new-platform-catalog-readiness\n仍有 6 例红,成因是并行会话在途把 simulate-new-platform-catalog-merge.mjs\n改指 activeContractsRoot 而修订 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-14T22:46:57-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d10dae4ab5cf2e2f61c009033f00970b9a51c600...615c017a32da032ecaeb00215d8b8b5418d9b122","Len":31}...
|
1789451250
|
Edit
Delete
|
|
29979
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d10dae4ab {"Commits":[{"Sha1":"d10dae4ab5cf2e2f61c009033f00970b9a51c600","Message":"fix(governance): 门禁按 workspace.json 定位平台层,恢复迁移后失效的审计\n\n阶段 3 把平台目录从 基础/ 移到 企业控制面/ 之后,仍按 resolve(scriptDir,'..')\n推导的门禁全部失效:派生仓探测不到 git 仓(13/13 missing-git-repo)、平台发现\n数为 0、候选契约 ENOENT、audit-ci-gates 直接 ERR_MODULE_NOT_FOUND。冻结证据\n一直都在,只是脚本找错了路。\n\nlib/workspace.mjs 新增平台层解析器:\n- platformLayerRoot 取清单 layers.基础设施,platformDir / derivedRepo 据此展开\n (git 仓在 \u003c平台\u003e/base-framework,不在平台目录本身)\n- frameworkSourceRepo 取清单 paths.baseFramework\n- discoverPlatformNames 以「含 base-framework/ 子目录」为判据,宿主仓\n enterprise-platform、真源仓 企业IdP快照 与四个无派生仓的候选目录据此自动排除,\n 不再维护 excluded 目录名黑名单\n\n改接清单的脚本与测试:\n- workspace-evidence-status / audit-platform-openings / check-archived-derived-repos\n- audit-ci-gates 只改兼容入口传参——审计核心在 archived-20260910 冻结的\n 统一交付平台仓内,不可改\n- validate-new-platform-contracts、check-new-platform-contract-compatibility 与\n tests/new-platform-consumer-contracts:治理脚本与候选平台契约是两个基准,\n 原先共用一个变量,拆开\n- tests/helpers/devx-review-* 的 new URL 相对定位改走清单(pathname 对中文是\n 百分号编码,findWorkspaceRoot 认不出会回落到 cwd)\n\n验证:\n check-archived-derived-repos 13/13 冻结在 tag(原 0/13)\n audit-platform-openings 13/18 通过(原「应为 18,实际 0」)\n audit-ci-gates 18/18 结构通过,仅数量 19 vs 18(企业 IdP 已登记缺失)\n validate-new-platform-contracts 8 schemas / 19 accepted / 8 rejected\n check-new-platform-contract-compatibility 4 projects / 8 schemas / 19 types\n audit-foundation 恢复出具审计(原 exit 2 崩溃)\n tests/ 10/11 文件全绿\n\n余 new-platform-catalog-readiness 6 例失败,成因不是路径:阶段 4 改动了\nCHG-001 修订 6 的三个冻结输入,指纹失配,另行处理。\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-14T21:52:14-07:00"},{"Sha1":"65c7ba829fdaa95b4373a4ced80246f6265b603c","Message":"feat(governance): 新增工作区一致性门禁,把迁移破坏类型固化成机器检查\n\n2026-09-14 迁移暴露的三类破坏都不在既有门禁视野里:判定逻辑按旧布局写死、\n冻结物摘要相符而内容过期、git worktree 两侧路径失联。新增 L1—L8 八项检查:\n\n L1 清单 layers/paths 声明的目录必须存在\n L2 `X/X/` 二次替换(替换脚本跑了两遍的痕迹)\n L3 旧层名残留(历史记录文件豁免)\n L4 受控 Markdown 本地链接可解析\n L5 Catalog / 候选清单登记路径可解析\n L6 worktree 两侧 gitdir 互指\n L7 冻结物摘要与磁盘内容一致\n L8 摘要相符但内容仍是旧布局 —— 本轮真正咬人的一类\n\n纯判定逻辑拆入 lib/workspace-consistency-core.mjs,7 个夹具用例覆盖正反向,\n其中一例直接锁住 L8 的教训:冻结 patch 摘要完好、内容仍写 `基础/\u003c平台\u003e`。\n门禁只读,不写任何文件;退出码 0/1/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-14T21:51:09-07:00"},{"Sha1":"f29bbbbeb8371825387d9437b91291af58f075d9","Message":"fix(governance): 基础审计改以清单定位基础设施层\n\n阶段 3 把 19 个平台仓从 基础/ 移入 企业控制面/,但 audit-foundation\n仍按 基础/ 的子目录枚举平台,且随后的机械替换把前缀改成了 平台治理/基础/\n——方向相反:那里只剩治理脚本与文档,平台一个也发现不了,\nclassifyDirectories 遂以 Invalid candidate directory 抛错,整条门禁跑不起来。\n\n- foundation-audit-core: 层前缀参数化(默认 企业控制面,可由调用方覆盖),\n 候选目录校验改用前缀比较而非硬编码正则;新增 externalDirectories,\n 使 工程基础框架 / 数字员工OS 这类跨层登记项不再被误判 missing-directory\n- audit-foundation: 平台层、框架真源仓与 OS 仓改由 workspace.json 解析\n (platformLayerRoot / frameworkSourceRepo / workspacePath)。\n try 块内 workspace 被同名 const 遮蔽,故派生路径一律在顶层先解析以避开 TDZ\n- 测试前缀改正,并补两个用例:跨层登记项、层名可覆盖\n\n回归:foundation-audit 11 → 13 用例全绿;audit-foundation 恢复可执行,\n阻塞项 8 项与迁移前基线逐项一致,派生仓发现 18/18。\ncontracts test 104 pass、governance test 193 pass、contracts check 4 项已知,\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-14T21:50:36-07:00"}],"HeadCommit":{"Sha1":"d10dae4ab5cf2e2f61c009033f00970b9a51c600","Message":"fix(governance): 门禁按 workspace.json 定位平台层,恢复迁移后失效的审计\n\n阶段 3 把平台目录从 基础/ 移到 企业控制面/ 之后,仍按 resolve(scriptDir,'..')\n推导的门禁全部失效:派生仓探测不到 git 仓(13/13 missing-git-repo)、平台发现\n数为 0、候选契约 ENOENT、audit-ci-gates 直接 ERR_MODULE_NOT_FOUND。冻结证据\n一直都在,只是脚本找错了路。\n\nlib/workspace.mjs 新增平台层解析器:\n- platformLayerRoot 取清单 layers.基础设施,platformDir / derivedRepo 据此展开\n (git 仓在 \u003c平台\u003e/base-framework,不在平台目录本身)\n- frameworkSourceRepo 取清单 paths.baseFramework\n- discoverPlatformNames 以「含 base-framework/ 子目录」为判据,宿主仓\n enterprise-platform、真源仓 企业IdP快照 与四个无派生仓的候选目录据此自动排除,\n 不再维护 excluded 目录名黑名单\n\n改接清单的脚本与测试:\n- workspace-evidence-status / audit-platform-openings / check-archived-derived-repos\n- audit-ci-gates 只改兼容入口传参——审计核心在 archived-20260910 冻结的\n 统一交付平台仓内,不可改\n- validate-new-platform-contracts、check-new-platform-contract-compatibility 与\n tests/new-platform-consumer-contracts:治理脚本与候选平台契约是两个基准,\n 原先共用一个变量,拆开\n- tests/helpers/devx-review-* 的 new URL 相对定位改走清单(pathname 对中文是\n 百分号编码,findWorkspaceRoot 认不出会回落到 cwd)\n\n验证:\n check-archived-derived-repos 13/13 冻结在 tag(原 0/13)\n audit-platform-openings 13/18 通过(原「应为 18,实际 0」)\n audit-ci-gates 18/18 结构通过,仅数量 19 vs 18(企业 IdP 已登记缺失)\n validate-new-platform-contracts 8 schemas / 19 accepted / 8 rejected\n check-new-platform-contract-compatibility 4 projects / 8 schemas / 19 types\n audit-foundation 恢复出具审计(原 exit 2 崩溃)\n tests/ 10/11 文件全绿\n\n余 new-platform-catalog-readiness 6 例失败,成因不是路径:阶段 4 改动了\nCHG-001 修订 6 的三个冻结输入,指纹失配,另行处理。\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-14T21:52:14-07:00"},"CompareURL":"luoanwu/platform-governance/compare/98ec9e9e61a1efb0e49011c06c28f63377accc23...d10dae4ab5cf2e2f61c009033f00970b9a51c600","Len":3}...
|
1789447994
|
Edit
Delete
|
|
29978
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"98ec9e9e6 {"Commits":[{"Sha1":"98ec9e9e61a1efb0e49011c06c28f63377accc23","Message":"fix(migration): 路径登记替换与门禁适配新结构\n\n数据登记(1099 处):code_truth / evidence / repository / directory 由旧\n层名改指新结构。历史记录(日期命名的分析与执行记录,28 份)保留旧路径,\n它们记录的是当时状态。\n\n门禁适配:\n- platform-project-catalog Schema 的 directory pattern 改为\n ^(企业控制面/[^/]+|数字员工OS|工程基础框架)$ —— 迁移后平台项目分散在\n 企业控制面/ 下与两个独占层,不再统一在 基础/ 下\n- governance-linter 平台目录扫描由 基础/ 改为 企业控制面/ + 两个独占层,\n 排除宿主仓 enterprise-platform 与事实模型仓\n- check-catalog-drift 前缀与排除集同步\n- WORKSPACE_ROOT_MARKERS 由 ['基础','doc'] 改为 ['平台治理','企业控制面']:\n 旧值在新结构下会误判——平台治理/ 下同时有 基础/ 与 doc/,镜像工作区的\n 中间层会被当成根\n- 冻结版 platform-contracts 同步上述改动,并补 workspace.json 根探测\n (它没有 workspace-root.mjs,原用 resolve(root,'..') 推导)\n- simulate-chg-* 的镜像工作区改由 lib/workspace.mjs 的 mirrorWorkspace\n 构造:platform-contracts 现嵌在 平台治理/ 下,镜像需还原两级结构\n- 测试中 resolve(root,'../X') 一律改走 baseline.workspaceRoot\n\n验证:contracts 104/104、governance 193/193、冻结版 76/76;\ncheck 回到基线 4 项 PLATFORM_PROJECT_UNREGISTERED(等 CHG-001 登记的\n4 个候选平台);simulate-chg-002/003/004 formalMutated=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-14T21:45:14-07:00"},{"Sha1":"2c886ca6ec1a6ba5d66aeddedcf53e9fa37e7317","Message":"feat(migration): 阶段 3 — 迁入新根,按架构图六层归位\n\n源根 企业产品/企业/企业应用/ 已清空,全部内容迁至 企业AI应用开发群/:\n\n 业务应用层/ 4 仓(嗨赞造意、巨嗨报价、巨嗨智服、尤克特拉)\n 企业领域应用层/ 4 仓(AI人事、AI项目与工单、知识云、设备云)\n 数字员工OS/ digital-employee-os + 层文档\n 企业控制面/ enterprise-platform + 18 平台仓 + 4 候选平台\n + 企业IdP快照 + 时空事实流转 + .secrets/.worktrees\n 工程基础框架/ base-framework ×2 + 层文档\n 平台治理/ doc/ + 基础/ + platform-contracts/ + 基础设施文档/\n\n本仓根由 企业应用/ 迁至新根,白名单重写;675 个文件识别为重命名。\nworkspace.json 的 layers/paths 切换到新结构,migration 段记录来源根。\n\n安全修正:.secrets/ 与 *.env 加入硬排除。此前 `!/基础设施/` 放行整个\n目录时误将 .secrets/ 两个文件纳入并推送(提交 91a01b1),凭证需轮换,\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-14T21:28:46-07:00"},{"Sha1":"65264f9956d370cc6d7789477feb5ebbdf608666","Message":"fix(workspace): 目录按架构图命名,词表名作为概念名正式对应\n\n先前把新根五个目录从架构图命名改成了治理词表命名,理由是\"改用展示名\n要多付 171 处替换\"——该理由不成立:两种命名下 171 处旧路径都要改,\n工作量相同,被误记成了展示名的单边代价。且新根目录本就按架构图建好,\n属明确意图。\n\nworkspace.json 新增 terminology.layers:term(治理词表名,治理文档与\n门禁口径用)↔ directory(物理目录名,取自架构图,路径与 code_truth 用)。\n两套名称不是分叉,是同一层的概念名与路径名。\n\nmigration 增 targetLayers / targetPaths,作为阶段 3 路径替换的映射来源。\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-14T20:46:07-07:00"},{"Sha1":"da52f2ea85b9398bd5e25b67e971f5bec1e50337","Message":"feat(governance): 工作区根改由 workspace.json 定位,解除目录名耦合\n\n基础/scripts/* 一律用 resolve(基础目录, '..') 推导工作区根。迁移方案把\n基础/ 移入 平台治理/ 后该式子会得到 平台治理/,而那里没有 公用应用/、\n业务应用/、基础设施/——simulate-chg-* 靠 readdirSync(workspace) 重建的\n临时镜像工作区将残缺,check.mjs 的平台目录扫描随之全错。\n\n- 新增根 workspace.json:既是工作区根标记,也声明各层与关键路径,\n 目录重排时只改本文件\n- 新增 基础/scripts/lib/workspace.mjs:向上查找清单确定工作区根,\n 无清单时回落到旧式推导\n- 7 个脚本改用它:audit-foundation、verify-new-platform-change、\n simulate-chg-002/003/004/005、simulate-new-platform-catalog-merge、\n check-new-platform-catalog-change-readiness\n\n回归与基线逐项一致:simulate-chg-002/003/004/005 全部 status=passed、\n80/80、formalMutated=false,CHG-003 仍 6→0;audit-foundation 仍 8 项阻塞。\n迁移后场景实测:旧式定位到 平台治理/ 且只看到 3 个条目,新式正确定位\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-14T20:40:01-07:00"},{"Sha1":"95d7c59e1064a02460b90d41436c69c76d095554","Message":"docs(governance): hi-atelier 正式名改为嗨赞造意并登记对照\n\n活文档统一改名(CLAUDE.md 五层词表、回灌台账驱动方清单、\n基础平台接入模型消费者矩阵、DEC-037 契约材料、分层与装配模型)。\n\n回灌台账新增 §0.1 应用改名登记,列出新旧名对照,并说明\n三类有意保留旧名的位置:冻结来源目录(CHG-001 指纹)、\n已批准 DEC 正文(决议不因改名改写)、日期命名的历史记录\n(记录当时状态,不追溯改写)。\n\n架构图 PNG 仍标旧名,待重新导出。\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-14T20:35:52-07:00"}],"HeadCommit":{"Sha1":"98ec9e9e61a1efb0e49011c06c28f63377accc23","Message":"fix(migration): 路径登记替换与门禁适配新结构\n\n数据登记(1099 处):code_truth / evidence / repository / directory 由旧\n层名改指新结构。历史记录(日期命名的分析与执行记录,28 份)保留旧路径,\n它们记录的是当时状态。\n\n门禁适配:\n- platform-project-catalog Schema 的 directory pattern 改为\n ^(企业控制面/[^/]+|数字员工OS|工程基础框架)$ —— 迁移后平台项目分散在\n 企业控制面/ 下与两个独占层,不再统一在 基础/ 下\n- governance-linter 平台目录扫描由 基础/ 改为 企业控制面/ + 两个独占层,\n 排除宿主仓 enterprise-platform 与事实模型仓\n- check-catalog-drift 前缀与排除集同步\n- WORKSPACE_ROOT_MARKERS 由 ['基础','doc'] 改为 ['平台治理','企业控制面']:\n 旧值在新结构下会误判——平台治理/ 下同时有 基础/ 与 doc/,镜像工作区的\n 中间层会被当成根\n- 冻结版 platform-contracts 同步上述改动,并补 workspace.json 根探测\n (它没有 workspace-root.mjs,原用 resolve(root,'..') 推导)\n- simulate-chg-* 的镜像工作区改由 lib/workspace.mjs 的 mirrorWorkspace\n 构造:platform-contracts 现嵌在 平台治理/ 下,镜像需还原两级结构\n- 测试中 resolve(root,'../X') 一律改走 baseline.workspaceRoot\n\n验证:contracts 104/104、governance 193/193、冻结版 76/76;\ncheck 回到基线 4 项 PLATFORM_PROJECT_UNREGISTERED(等 CHG-001 登记的\n4 个候选平台);simulate-chg-002/003/004 formalMutated=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-14T21:45:14-07:00"},"CompareURL":"luoanwu/platform-governance/compare/55f8a2b2b794f3104f47bde1db41106fe38d1b21...98ec9e9e61a1efb0e49011c06c28f63377accc23","Len":7}...
|
1789447687
|
Edit
Delete
|
|
29977
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/feat/platform-governance-baseline
|
0
|
{"Commits":[{"Sha1":"65264f995 {"Commits":[{"Sha1":"65264f9956d370cc6d7789477feb5ebbdf608666","Message":"fix(workspace): 目录按架构图命名,词表名作为概念名正式对应\n\n先前把新根五个目录从架构图命名改成了治理词表命名,理由是\"改用展示名\n要多付 171 处替换\"——该理由不成立:两种命名下 171 处旧路径都要改,\n工作量相同,被误记成了展示名的单边代价。且新根目录本就按架构图建好,\n属明确意图。\n\nworkspace.json 新增 terminology.layers:term(治理词表名,治理文档与\n门禁口径用)↔ directory(物理目录名,取自架构图,路径与 code_truth 用)。\n两套名称不是分叉,是同一层的概念名与路径名。\n\nmigration 增 targetLayers / targetPaths,作为阶段 3 路径替换的映射来源。\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-14T20:46:07-07:00"},{"Sha1":"da52f2ea85b9398bd5e25b67e971f5bec1e50337","Message":"feat(governance): 工作区根改由 workspace.json 定位,解除目录名耦合\n\n基础/scripts/* 一律用 resolve(基础目录, '..') 推导工作区根。迁移方案把\n基础/ 移入 平台治理/ 后该式子会得到 平台治理/,而那里没有 公用应用/、\n业务应用/、基础设施/——simulate-chg-* 靠 readdirSync(workspace) 重建的\n临时镜像工作区将残缺,check.mjs 的平台目录扫描随之全错。\n\n- 新增根 workspace.json:既是工作区根标记,也声明各层与关键路径,\n 目录重排时只改本文件\n- 新增 基础/scripts/lib/workspace.mjs:向上查找清单确定工作区根,\n 无清单时回落到旧式推导\n- 7 个脚本改用它:audit-foundation、verify-new-platform-change、\n simulate-chg-002/003/004/005、simulate-new-platform-catalog-merge、\n check-new-platform-catalog-change-readiness\n\n回归与基线逐项一致:simulate-chg-002/003/004/005 全部 status=passed、\n80/80、formalMutated=false,CHG-003 仍 6→0;audit-foundation 仍 8 项阻塞。\n迁移后场景实测:旧式定位到 平台治理/ 且只看到 3 个条目,新式正确定位\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-14T20:40:01-07:00"},{"Sha1":"95d7c59e1064a02460b90d41436c69c76d095554","Message":"docs(governance): hi-atelier 正式名改为嗨赞造意并登记对照\n\n活文档统一改名(CLAUDE.md 五层词表、回灌台账驱动方清单、\n基础平台接入模型消费者矩阵、DEC-037 契约材料、分层与装配模型)。\n\n回灌台账新增 §0.1 应用改名登记,列出新旧名对照,并说明\n三类有意保留旧名的位置:冻结来源目录(CHG-001 指纹)、\n已批准 DEC 正文(决议不因改名改写)、日期命名的历史记录\n(记录当时状态,不追溯改写)。\n\n架构图 PNG 仍标旧名,待重新导出。\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-14T20:35:52-07:00"},{"Sha1":"98de9b14bed6ea4597187525f26d046d3a64c7d6","Message":"fix(governance): 排除 git worktree 目录,勿作嵌入仓纳入\n\n基础设施/.worktrees/security-governance-hardening 是 enterprise-platform\n的 worktree,首次提交时被当作嵌入仓加成 gitlink(clone 后为空目录)。\nworktree 的 .git 是文件而非目录,常规仓扫描会漏掉。\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-14T20:20:08-07:00"},{"Sha1":"2c324e70c3aa9d29f0eb4a8f4bab1d1842dc6bc6","Message":"chore(governance): 为平台治理资产建立版本控制\n\n此前 doc/、基础/ 治理文档、门禁脚本与证据、platform-contracts/ 均不在\n任何 git 仓中——整个应用群的规则真源没有版本历史,改错无法回滚、\n变更无从追溯。2026-09-14 全量备份时确认这是比无远端仓更严重的单点。\n\n纳入(678 文件 / 6.2 MB):\n- doc/:DEC-001~039 决议草案与 CHG-002~005 变更材料\n- platform-contracts/:Catalog、Schema 与门禁脚本\n (PF-04 阶段 2 物理移除前仍是 基础/scripts 的运行依赖)\n- 基础/:治理文档、scripts/ 门禁、tests/、reports/ 机器证据\n- 基础设施/:设计方案与开发计划(enterprise-platform 为独立仓)\n- 根目录分析报告与路径变更 patch\n\n不纳入:32 个应用/平台子仓(各有自己的仓)、node_modules、\n业务应用/ 下 3.4 GB 验收与发布产物。策略为白名单,见 .gitignore。\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-14T20:18:46-07:00"}],"HeadCommit":{"Sha1":"65264f9956d370cc6d7789477feb5ebbdf608666","Message":"fix(workspace): 目录按架构图命名,词表名作为概念名正式对应\n\n先前把新根五个目录从架构图命名改成了治理词表命名,理由是\"改用展示名\n要多付 171 处替换\"——该理由不成立:两种命名下 171 处旧路径都要改,\n工作量相同,被误记成了展示名的单边代价。且新根目录本就按架构图建好,\n属明确意图。\n\nworkspace.json 新增 terminology.layers:term(治理词表名,治理文档与\n门禁口径用)↔ directory(物理目录名,取自架构图,路径与 code_truth 用)。\n两套名称不是分叉,是同一层的概念名与路径名。\n\nmigration 增 targetLayers / targetPaths,作为阶段 3 路径替换的映射来源。\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-14T20:46:07-07:00"},"CompareURL":"luoanwu/platform-governance/compare/55f8a2b2b794f3104f47bde1db41106fe38d1b21...65264f9956d370cc6d7789477feb5ebbdf608666","Len":5}...
|
1789447687
|
Edit
Delete
|
|
29891
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/feat/platform-governance-baseline
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"55f8a2b2b794f3104f47bde1db41106fe38d1b21","Message":"fix(workspace): 目录按架构图命名,词表名作为概念名正式对应\n\n先前把新根五个目录从架构图命名改成了治理词表命名,理由是\"改用展示名\n要多付 171 处替换\"——该理由不成立:两种命名下 171 处旧路径都要改,\n工作量相同,被误记成了展示名的单边代价。且新根目录本就按架构图建好,\n属明确意图。\n\nworkspace.json 新增 terminology.layers:term(治理词表名,治理文档与\n门禁口径用)↔ directory(物理目录名,取自架构图,路径与 code_truth 用)。\n两套名称不是分叉,是同一层的概念名与路径名。\n\nmigration 增 targetLayers / targetPaths,作为阶段 3 路径替换的映射来源。\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-14T20:46:07-07:00"},"CompareURL":"luoanwu/platform-governance/compare/main...55f8a2b2b794f3104f47bde1db41106fe38d1b21","Len":0}...
|
1789444436
|
Edit
Delete
|
|
29890
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/feat/platform-governance-baseline
|
0
|
|
1789444436
|
Edit
Delete
|
|
29889
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"55f8a2b2b {"Commits":[{"Sha1":"55f8a2b2b794f3104f47bde1db41106fe38d1b21","Message":"fix(workspace): 目录按架构图命名,词表名作为概念名正式对应\n\n先前把新根五个目录从架构图命名改成了治理词表命名,理由是\"改用展示名\n要多付 171 处替换\"——该理由不成立:两种命名下 171 处旧路径都要改,\n工作量相同,被误记成了展示名的单边代价。且新根目录本就按架构图建好,\n属明确意图。\n\nworkspace.json 新增 terminology.layers:term(治理词表名,治理文档与\n门禁口径用)↔ directory(物理目录名,取自架构图,路径与 code_truth 用)。\n两套名称不是分叉,是同一层的概念名与路径名。\n\nmigration 增 targetLayers / targetPaths,作为阶段 3 路径替换的映射来源。\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-14T20:46:07-07:00"},{"Sha1":"97f72b07d16ede5d504bd8ec32f5900a9b466c28","Message":"feat(governance): 工作区根改由 workspace.json 定位,解除目录名耦合\n\n基础/scripts/* 一律用 resolve(基础目录, '..') 推导工作区根。迁移方案把\n基础/ 移入 平台治理/ 后该式子会得到 平台治理/,而那里没有 公用应用/、\n业务应用/、基础设施/——simulate-chg-* 靠 readdirSync(workspace) 重建的\n临时镜像工作区将残缺,check.mjs 的平台目录扫描随之全错。\n\n- 新增根 workspace.json:既是工作区根标记,也声明各层与关键路径,\n 目录重排时只改本文件\n- 新增 基础/scripts/lib/workspace.mjs:向上查找清单确定工作区根,\n 无清单时回落到旧式推导\n- 7 个脚本改用它:audit-foundation、verify-new-platform-change、\n simulate-chg-002/003/004/005、simulate-new-platform-catalog-merge、\n check-new-platform-catalog-change-readiness\n\n回归与基线逐项一致:simulate-chg-002/003/004/005 全部 status=passed、\n80/80、formalMutated=false,CHG-003 仍 6→0;audit-foundation 仍 8 项阻塞。\n迁移后场景实测:旧式定位到 平台治理/ 且只看到 3 个条目,新式正确定位\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-14T20:40:01-07:00"},{"Sha1":"e195d3529baa2df8e53df644cc877a6d9109f357","Message":"docs(governance): hi-atelier 正式名改为嗨赞造意并登记对照\n\n活文档统一改名(CLAUDE.md 五层词表、回灌台账驱动方清单、\n基础平台接入模型消费者矩阵、DEC-037 契约材料、分层与装配模型)。\n\n回灌台账新增 §0.1 应用改名登记,列出新旧名对照,并说明\n三类有意保留旧名的位置:冻结来源目录(CHG-001 指纹)、\n已批准 DEC 正文(决议不因改名改写)、日期命名的历史记录\n(记录当时状态,不追溯改写)。\n\n架构图 PNG 仍标旧名,待重新导出。\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-14T20:35:52-07:00"},{"Sha1":"ee2bcf98a46ff8e8f4601ee722f45af06480ec2a","Message":"fix(governance): 排除 git worktree 目录,勿作嵌入仓纳入\n\n基础设施/.worktrees/security-governance-hardening 是 enterprise-platform\n的 worktree,首次提交时被当作嵌入仓加成 gitlink(clone 后为空目录)。\nworktree 的 .git 是文件而非目录,常规仓扫描会漏掉。\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-14T20:20:08-07:00"},{"Sha1":"91a01b1e4c69ff0dd582ccf6bff4d0d6d3a17ee9","Message":"chore(governance): 为平台治理资产建立版本控制\n\n此前 doc/、基础/ 治理文档、门禁脚本与证据、platform-contracts/ 均不在\n任何 git 仓中——整个应用群的规则真源没有版本历史,改错无法回滚、\n变更无从追溯。2026-09-14 全量备份时确认这是比无远端仓更严重的单点。\n\n纳入(678 文件 / 6.2 MB):\n- doc/:DEC-001~039 决议草案与 CHG-002~005 变更材料\n- platform-contracts/:Catalog、Schema 与门禁脚本\n (PF-04 阶段 2 物理移除前仍是 基础/scripts 的运行依赖)\n- 基础/:治理文档、scripts/ 门禁、tests/、reports/ 机器证据\n- 基础设施/:设计方案与开发计划(enterprise-platform 为独立仓)\n- 根目录分析报告与路径变更 patch\n\n不纳入:32 个应用/平台子仓(各有自己的仓)、node_modules、\n业务应用/ 下 3.4 GB 验收与发布产物。策略为白名单,见 .gitignore。\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-14T20:18:46-07:00"}],"HeadCommit":{"Sha1":"55f8a2b2b794f3104f47bde1db41106fe38d1b21","Message":"fix(workspace): 目录按架构图命名,词表名作为概念名正式对应\n\n先前把新根五个目录从架构图命名改成了治理词表命名,理由是\"改用展示名\n要多付 171 处替换\"——该理由不成立:两种命名下 171 处旧路径都要改,\n工作量相同,被误记成了展示名的单边代价。且新根目录本就按架构图建好,\n属明确意图。\n\nworkspace.json 新增 terminology.layers:term(治理词表名,治理文档与\n门禁口径用)↔ directory(物理目录名,取自架构图,路径与 code_truth 用)。\n两套名称不是分叉,是同一层的概念名与路径名。\n\nmigration 增 targetLayers / targetPaths,作为阶段 3 路径替换的映射来源。\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-14T20:46:07-07:00"},"CompareURL":"","Len":5}...
|
1789444434
|
Edit
Delete
|
|
29888
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
|
1789444434
|
Edit
Delete
|
|
29887
|
5
|
1
|
5
|
117
|
0
|
0
|
|
0
|
|
1789444404
|
Edit
Delete
|