|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
30707
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"06cdd6f0f {"Commits":[{"Sha1":"06cdd6f0fdfa799a55c0c78b11bdcb0601bcb0e7","Message":"chore(reports): 延后op 报告回绑 @ ce04278\n\n上一条提交里的报告绑的是其父提交;重跑后绑到真正包含 check-deferred-ops 的提交。8 条延后 op(已登记生效 2、已撤销 1)0 违规。\n\nworktreeDirty 仍为 true 且如实记录:工作树里有并行会话的在途文件(开发计划.md、workspace-consistency.test.mjs 与三份门禁运行产物),本会话无法在 clean 树上取证,故该报告只绑定本地工作区,不作为「clean HEAD 证据」引用。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:16:31-07:00"}],"HeadCommit":{"Sha1":"06cdd6f0fdfa799a55c0c78b11bdcb0601bcb0e7","Message":"chore(reports): 延后op 报告回绑 @ ce04278\n\n上一条提交里的报告绑的是其父提交;重跑后绑到真正包含 check-deferred-ops 的提交。8 条延后 op(已登记生效 2、已撤销 1)0 违规。\n\nworktreeDirty 仍为 true 且如实记录:工作树里有并行会话的在途文件(开发计划.md、workspace-consistency.test.mjs 与三份门禁运行产物),本会话无法在 clean 树上取证,故该报告只绑定本地工作区,不作为「clean HEAD 证据」引用。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:16:31-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ce042782a285d1d8a79e5c5a43636ea05f4868d3...06cdd6f0fdfa799a55c0c78b11bdcb0601bcb0e7","Len":1}...
|
1789686993
|
Edit
Delete
|
|
30708
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"22f145c7c {"Commits":[{"Sha1":"22f145c7cc1d26ac35b6ce4781f2c36621c17de7","Message":"chore(reports): 门禁运行 / 门禁消费 / 统一审计 / 延后op 回绑 @ 06cdd6f(clean 树)\n\n并行会话的在途文件落地后工作树转干净(非报告类脏文件 0),重跑取 clean 绑定:阻断性门禁 10/10 通过(含新增 check-deferred-ops),仅记录 3 道(workspace-consistency 3 条既有 + domain-layer 13 条,均不参与总账);延后op 8 条 0 违规。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:17:04-07:00"}],"HeadCommit":{"Sha1":"22f145c7cc1d26ac35b6ce4781f2c36621c17de7","Message":"chore(reports): 门禁运行 / 门禁消费 / 统一审计 / 延后op 回绑 @ 06cdd6f(clean 树)\n\n并行会话的在途文件落地后工作树转干净(非报告类脏文件 0),重跑取 clean 绑定:阻断性门禁 10/10 通过(含新增 check-deferred-ops),仅记录 3 道(workspace-consistency 3 条既有 + domain-layer 13 条,均不参与总账);延后op 8 条 0 违规。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:17:04-07:00"},"CompareURL":"luoanwu/platform-governance/compare/06cdd6f0fdfa799a55c0c78b11bdcb0601bcb0e7...22f145c7cc1d26ac35b6ce4781f2c36621c17de7","Len":1}...
|
1789687026
|
Edit
Delete
|
|
30709
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"96dbcd998 {"Commits":[{"Sha1":"96dbcd998453ba6720203ea63ab612caa4d34687","Message":"chore(reports): 延后op 回绑 @ 17b81dd(clean 树,worktreeDirty=false)\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:17:30-07:00"},{"Sha1":"17b81dde8df1c9c426b95261a8d7c1ad60054bd2","Message":"fix(governance): check-deferred-ops 改用治理层统一 provenance 口径\n\n原先自己数 `git status --porcelain` 行数判 worktreeDirty,把本轮要覆盖的 latest 报告也算成脏文件——字段随即恒为 true,一个永远为真的 provenance 字段没有信息量,也与真源仓 governance/lib/provenance.mjs、治理层 report-provenance.mjs 的既有口径(忽略本轮生成的 latest 报告)不一致。改为复用 governanceProvenance,一并得到 repository / dirtyPaths。11 例单测不变全绿。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:17:30-07:00"}],"HeadCommit":{"Sha1":"96dbcd998453ba6720203ea63ab612caa4d34687","Message":"chore(reports): 延后op 回绑 @ 17b81dd(clean 树,worktreeDirty=false)\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:17:30-07:00"},"CompareURL":"luoanwu/platform-governance/compare/22f145c7cc1d26ac35b6ce4781f2c36621c17de7...96dbcd998453ba6720203ea63ab612caa4d34687","Len":2}...
|
1789687054
|
Edit
Delete
|
|
30710
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"25751af08 {"Commits":[{"Sha1":"25751af083e566216e1803734573cfdb8184e65b","Message":"docs(开发计划): §8 补「延后 op 门禁与两处收口」一行\n\n登记 check-deferred-ops 的建立、它当场抓出的两个真问题(CHG-003/006 同条目冲突的延后 op、CHG-003 enterprise-idp 的半应用)与随之收口的两处恒红/崩溃。一致性检查 L4 / L10 / L13 清零。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:17:51-07:00"}],"HeadCommit":{"Sha1":"25751af083e566216e1803734573cfdb8184e65b","Message":"docs(开发计划): §8 补「延后 op 门禁与两处收口」一行\n\n登记 check-deferred-ops 的建立、它当场抓出的两个真问题(CHG-003/006 同条目冲突的延后 op、CHG-003 enterprise-idp 的半应用)与随之收口的两处恒红/崩溃。一致性检查 L4 / L10 / L13 清零。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:17:51-07:00"},"CompareURL":"luoanwu/platform-governance/compare/96dbcd998453ba6720203ea63ab612caa4d34687...25751af083e566216e1803734573cfdb8184e65b","Len":1}...
|
1789687075
|
Edit
Delete
|
|
30711
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"15bce0f4b {"Commits":[{"Sha1":"15bce0f4b672fc7456786bc61d493b3ffc04e630","Message":"docs(平台治理): 收纳表随新增门禁改数——scripts 48→50、tests 32→33、reports 324→325(顶层 39→40)\n\ncheck-deferred-ops.mjs 与 lib/deferred-ops-core.mjs、deferred-ops.test.mjs、延后op.latest.json 四个新文件没同步收纳表,上一条提交(25751af)因此把 L13 三条漂移推了出去。本次补齐,L13 清零。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:18:34-07:00"}],"HeadCommit":{"Sha1":"15bce0f4b672fc7456786bc61d493b3ffc04e630","Message":"docs(平台治理): 收纳表随新增门禁改数——scripts 48→50、tests 32→33、reports 324→325(顶层 39→40)\n\ncheck-deferred-ops.mjs 与 lib/deferred-ops-core.mjs、deferred-ops.test.mjs、延后op.latest.json 四个新文件没同步收纳表,上一条提交(25751af)因此把 L13 三条漂移推了出去。本次补齐,L13 清零。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:18:34-07:00"},"CompareURL":"luoanwu/platform-governance/compare/25751af083e566216e1803734573cfdb8184e65b...15bce0f4b672fc7456786bc61d493b3ffc04e630","Len":1}...
|
1789687118
|
Edit
Delete
|
|
30712
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"a9e489b08 {"Commits":[{"Sha1":"a9e489b08d6d8dd510c9f63dd663b94037d5f9f4","Message":"docs(计划): PF-03 收口完成(真源仓 a084c5e,报告回绑 a7a19ec)\n\n- §3 PF-03 行改为「✅ 完成」,退出条件落为「三份文档均声明本目录身份与\n 版本轴归属、不含框架仓状态声明」\n- §5 ⑤ 移除已完成的「PF-03 ⑤ 文档回灌」\n- §8 增一行,含 check:evidence 仍 partial 的如实登记\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:19:27-07:00"}],"HeadCommit":{"Sha1":"a9e489b08d6d8dd510c9f63dd663b94037d5f9f4","Message":"docs(计划): PF-03 收口完成(真源仓 a084c5e,报告回绑 a7a19ec)\n\n- §3 PF-03 行改为「✅ 完成」,退出条件落为「三份文档均声明本目录身份与\n 版本轴归属、不含框架仓状态声明」\n- §5 ⑤ 移除已完成的「PF-03 ⑤ 文档回灌」\n- §8 增一行,含 check:evidence 仍 partial 的如实登记\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:19:27-07:00"},"CompareURL":"luoanwu/platform-governance/compare/15bce0f4b672fc7456786bc61d493b3ffc04e630...a9e489b08d6d8dd510c9f63dd663b94037d5f9f4","Len":1}...
|
1789687171
|
Edit
Delete
|
|
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
|
|
30716
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d991c4494 {"Commits":[{"Sha1":"d991c449457408aed0e9b98accb23feffdcc3d92","Message":"fix(governance): L8 补冻结物的显式豁免出口——审批记录条目写明,缺理由不放行\n\nL2 有 pragma 与 frozenInputs 两条出口,L8 一条也没有:冻结物改一字节即触发 L7 摘要不符,\n文件内的`一致性门禁豁免`标记对它无效,于是命中即永久噪声,与本门禁自己立的收敛原则\n(报出来的每一条都应当是能直接去改的)相反。\n\n出口改为由审批记录条目写明 consistencyExempt + consistencyExemptNote,缺 note 不放行;\n豁免以 frozenExempted 计数与 frozenExemptions 明细出现在 JSON 输出里,不静默。\n两个字段都不进 packageFingerprint(只取 path + sha256),登记前后指纹实测未变 1fdc2e1666c5。\n\n首条登记:新增基础应用MachineCatalog完整变更.patch。核验结论是误报——命中只 1 处、位于\ndiff 的上下文行(补丁并未引入),且处在一句陈述「旧断言写成了迁移双替换产物、等于没断言」的\n注释里,是对缺陷的描述而非被使用的路径。解除条件:变更包合并或撤回归档后随条目移除。\n\n验证:一致性门禁 3 → 2(余 L9 compose 撞名、L12 内核 pin 落后,均有既定归属);\ntests/workspace-consistency.test.mjs 35/35;变更包就绪门禁与评审门禁 exit 0。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:22:29-07:00"}],"HeadCommit":{"Sha1":"d991c449457408aed0e9b98accb23feffdcc3d92","Message":"fix(governance): L8 补冻结物的显式豁免出口——审批记录条目写明,缺理由不放行\n\nL2 有 pragma 与 frozenInputs 两条出口,L8 一条也没有:冻结物改一字节即触发 L7 摘要不符,\n文件内的`一致性门禁豁免`标记对它无效,于是命中即永久噪声,与本门禁自己立的收敛原则\n(报出来的每一条都应当是能直接去改的)相反。\n\n出口改为由审批记录条目写明 consistencyExempt + consistencyExemptNote,缺 note 不放行;\n豁免以 frozenExempted 计数与 frozenExemptions 明细出现在 JSON 输出里,不静默。\n两个字段都不进 packageFingerprint(只取 path + sha256),登记前后指纹实测未变 1fdc2e1666c5。\n\n首条登记:新增基础应用MachineCatalog完整变更.patch。核验结论是误报——命中只 1 处、位于\ndiff 的上下文行(补丁并未引入),且处在一句陈述「旧断言写成了迁移双替换产物、等于没断言」的\n注释里,是对缺陷的描述而非被使用的路径。解除条件:变更包合并或撤回归档后随条目移除。\n\n验证:一致性门禁 3 → 2(余 L9 compose 撞名、L12 内核 pin 落后,均有既定归属);\ntests/workspace-consistency.test.mjs 35/35;变更包就绪门禁与评审门禁 exit 0。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:22:29-07:00"},"CompareURL":"luoanwu/platform-governance/compare/cfaef2fc83837096a19a0d330b709017c0f322dd...d991c449457408aed0e9b98accb23feffdcc3d92","Len":1}...
|
1789687361
|
Edit
Delete
|
|
30717
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"bc850cd56 {"Commits":[{"Sha1":"bc850cd56895bf917bf6ec91b565f582e3dc601d","Message":"docs(决策): C-12 drift 升档已执行(真源仓 8382c04)\n\n决策批次 C-12 的两个前置(A-2 合并、drift 清零)均满足后执行升档:catalog:drift 的 error 与 drift 两档一律 exit 1,去掉从无调用方的 --strict 开关。逐条登记实况比原裁决所记更弱的那一点(此前连 error 都不阻断),并记 CLI 层四段负向。开发计划 §8 同步一行。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:23:08-07:00"}],"HeadCommit":{"Sha1":"bc850cd56895bf917bf6ec91b565f582e3dc601d","Message":"docs(决策): C-12 drift 升档已执行(真源仓 8382c04)\n\n决策批次 C-12 的两个前置(A-2 合并、drift 清零)均满足后执行升档:catalog:drift 的 error 与 drift 两档一律 exit 1,去掉从无调用方的 --strict 开关。逐条登记实况比原裁决所记更弱的那一点(此前连 error 都不阻断),并记 CLI 层四段负向。开发计划 §8 同步一行。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:23:08-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d991c449457408aed0e9b98accb23feffdcc3d92...bc850cd56895bf917bf6ec91b565f582e3dc601d","Len":1}...
|
1789687392
|
Edit
Delete
|
|
30718
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d5f1b641b {"Commits":[{"Sha1":"d5f1b641b05f0b3a351c8792b64d7215f3356d38","Message":"docs(计划): 偏差 #34 补第二个缺陷;登记 evidence-scopes 口径修正(真源仓 ac396a0)\n\nEVIDENCE_BOUND_DIRTY 读工作区里的报告文件,判定严重级所用的 currentTreeDirty\n却走 gitProvenance(),而后者显式排除 *.latest.json。并行会话正在跑门禁、只有\n报告文件脏时,门禁认定「当前树干净」,把 4 份尚未提交的在途报告判成 error 并\n输出「脏绑报告被提交了」——该断言在此情形下为假:那 4 份的 HEAD 版本干净绑定\n8382c04,只有工作区版本绑 bd625a1 + dirty。对比工作区版本与 HEAD 版本即可分辨,\n门禁不该断言它没有核实的事。两点同属一条规则,建议一并处置。\n\n§8 同时登记 evidence-scopes 口径说明补第五类(真源仓 ac396a0)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:25:08-07:00"}],"HeadCommit":{"Sha1":"d5f1b641b05f0b3a351c8792b64d7215f3356d38","Message":"docs(计划): 偏差 #34 补第二个缺陷;登记 evidence-scopes 口径修正(真源仓 ac396a0)\n\nEVIDENCE_BOUND_DIRTY 读工作区里的报告文件,判定严重级所用的 currentTreeDirty\n却走 gitProvenance(),而后者显式排除 *.latest.json。并行会话正在跑门禁、只有\n报告文件脏时,门禁认定「当前树干净」,把 4 份尚未提交的在途报告判成 error 并\n输出「脏绑报告被提交了」——该断言在此情形下为假:那 4 份的 HEAD 版本干净绑定\n8382c04,只有工作区版本绑 bd625a1 + dirty。对比工作区版本与 HEAD 版本即可分辨,\n门禁不该断言它没有核实的事。两点同属一条规则,建议一并处置。\n\n§8 同时登记 evidence-scopes 口径说明补第五类(真源仓 ac396a0)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:25:08-07:00"},"CompareURL":"luoanwu/platform-governance/compare/bc850cd56895bf917bf6ec91b565f582e3dc601d...d5f1b641b05f0b3a351c8792b64d7215f3356d38","Len":1}...
|
1789687511
|
Edit
Delete
|
|
30721
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1e0ea0813 {"Commits":[{"Sha1":"1e0ea08130bcbed848d075740bb4b5c44c1ffde4","Message":"chore(reports): 治理层门禁报告回绑 @ 6e0d7aa\n\n清树重跑 run-foundation-gates:阻断性 10/10 通过,仅记录 3\n(工作区一致性 2 条 L9 / L12、域分层 13 条,均不参与总账)。\n三份报告 worktreeDirty=false,绑定 6e0d7aa。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:30:08-07:00"},{"Sha1":"6e0d7aa2570ce0046c8e1860044a8547f8567c23","Message":"docs(治理): L9 收口为「根因已闭、扩散无渠道」,登记 N-11 交派活\n\n核到底的结论是 L9 不该按「待修的缺陷」处理:\n\n- 模板根因早已关闭。框架 0.17.0(实现提交 313137b)给 compose 写了\n name: ${COMPOSE_PROJECT_NAME:-base-framework} 与 ${REDIS_PORT:-6379},\n F14 在框架 pnpm check 链里守全仓每一份 compose,scaffold-derived.mjs\n 派生时重绑身份,变更请求文首已记「已受理并落地」。enterprise-platform\n 两份 compose 也已带身份。新建仓不再扩散该缺陷。\n- 但扩散没有发生,且没有渠道可走。回灌台账 §3 第 8 条指定的\n 框架新版本同步计划自述「同步波次事实上已无目标」(18 个派生仓已退役),\n 它也从不覆盖上层应用仓。L9 当日实测仍有 8 个应用仓共用 project\n api-nestjs,且这 8 个仓自己的门禁一个都不报:5 个带 F14 之前的旧版\n check-fork-readiness.mjs(文件内 F14 零命中),3 个没有该脚本——\n 它们的 pnpm check 在冲突状态下仍是绿的。\n- 台账原话「在模板修好前,任何两个仓不得同时 docker compose up」的前提\n 已不成立而风险未变,按实际判据改述为「上列 8 个仓两两之间不得同时 up」。\n\n治理层按回灌边界「不代业务应用仓提交」,不自行下手,本轮只落记录:\nC-15 与 §3 第 8 条加订正(append-only,不改写原文),新登记待裁决 N-11\n交目录负责人三选一,并写明 0.17.0 的 F14 是破坏性变更——改 project 名后\n首次 up 会建新空卷,旧卷 api-nestjs_* 的开发数据不跟着走,这正是 N-09\n当时搁置同步的那一条,选任一路线都要先答共用卷里的数据归谁。\n\nL9 保持红,不降级。\n\n证据:治理层 365 例 0 失败、阻断性门禁 10/10;工作区一致性仍 2 条\n(L9 / L12),无新增断链与措辞违规。报告在脏树上产出,不随本提交,\n清树重跑后另行回绑。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:29:41-07:00"}],"HeadCommit":{"Sha1":"1e0ea08130bcbed848d075740bb4b5c44c1ffde4","Message":"chore(reports): 治理层门禁报告回绑 @ 6e0d7aa\n\n清树重跑 run-foundation-gates:阻断性 10/10 通过,仅记录 3\n(工作区一致性 2 条 L9 / L12、域分层 13 条,均不参与总账)。\n三份报告 worktreeDirty=false,绑定 6e0d7aa。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:30:08-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d5f1b641b05f0b3a351c8792b64d7215f3356d38...1e0ea08130bcbed848d075740bb4b5c44c1ffde4","Len":2}...
|
1789687811
|
Edit
Delete
|
|
30722
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1645e7288 {"Commits":[{"Sha1":"1645e7288b484ab39a4e3ebb2da44678e9b9e300","Message":"docs(计划): 偏差 #34 已裁决并实现,移入已关闭(真源仓 e5cc39f / 4b067cd)\n\n目录负责人 2026-09-17 裁决:\n- A「干净检出生成报告」:不放宽 worktreeDirty,改为 pnpm reports:rebind 在\n HEAD 开 git worktree 跑零依赖门禁、只带回干净绑定的报告\n- B「修正断言」:EVIDENCE_BOUND_DIRTY 按报告文件自身是否未提交区分,在途\n 产物降 info 并如实描述,已提交的脏绑仍 error\n\n§6 中 #34 由开放表移入已关闭一行并附实现与证据;§8 增一行记录裁决与实现细节\n(含范围外声明与三条护栏)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:33:10-07:00"}],"HeadCommit":{"Sha1":"1645e7288b484ab39a4e3ebb2da44678e9b9e300","Message":"docs(计划): 偏差 #34 已裁决并实现,移入已关闭(真源仓 e5cc39f / 4b067cd)\n\n目录负责人 2026-09-17 裁决:\n- A「干净检出生成报告」:不放宽 worktreeDirty,改为 pnpm reports:rebind 在\n HEAD 开 git worktree 跑零依赖门禁、只带回干净绑定的报告\n- B「修正断言」:EVIDENCE_BOUND_DIRTY 按报告文件自身是否未提交区分,在途\n 产物降 info 并如实描述,已提交的脏绑仍 error\n\n§6 中 #34 由开放表移入已关闭一行并附实现与证据;§8 增一行记录裁决与实现细节\n(含范围外声明与三条护栏)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:33:10-07:00"},"CompareURL":"luoanwu/platform-governance/compare/1e0ea08130bcbed848d075740bb4b5c44c1ffde4...1645e7288b484ab39a4e3ebb2da44678e9b9e300","Len":1}...
|
1789687994
|
Edit
Delete
|
|
30724
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"eca16cecb {"Commits":[{"Sha1":"eca16cecb1b0e54e66d69268589ffa59c2fe6eff","Message":"chore(reports): 治理层门禁报告回绑 @ 3ca6a19\n\n清树重跑 run-foundation-gates:阻断性 11/11 通过(check-domain-layer 首次\n以阻断位计入,基线口径 0 阻断),仅记录 2(工作区一致性 L9 / L12)。\n三份报告 worktreeDirty=false,绑定 3ca6a19。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:37:02-07:00"},{"Sha1":"3ca6a19355e099d1643d6f03eeb59ae360011615","Message":"feat(governance): 域分层门禁转阻断位,按基线只拦新增\n\n查 L9 派活路径时撞见一条静音:门禁消费登记里 check-domain-layer 的接入\n条件写的是「D5(CHG-007 合并)与 D9(两份契约副本收敛)清零后转阻断位」,\n2026-09-17 实测 D5 = 0、D9 = 0——条件早已满足而无人察觉。\n\n根因:check-gate-consumption 的 G4 只断言 wireInWhen 非空,从不校验它是否\n已成立。该登记本是为治「门禁失败信号无人看」而建的,流外出口是它唯一的\n豁免口,而豁免口自己没有到期判据——用来防静音的机制在自己身上静音了。\n\n处置不能是直接翻阻断位:余下 13 条全在上层应用仓,治理层按回灌边界不代其\n提交,接入即恒红,而恒红正是该登记要治的病。原条件后半句「其余各条按\nOwner 各自的节奏消」已写明正确形态,只是从没人把它实现成基线。故:\n\n- 新增 域分层基线.json:13 条存量逐条具名 Owner 与复核期(D2 权威倒挂 3 ·\n D4 无事实出口 3 · D6 未装入基座 3 · D7 同版本分叉 1 · D10 已装内容不可\n 追溯 1 · D11 门禁零负向探针 2),来源登记指回台账 U-24 / U-32 / U-34 /\n U-36 与 §3 第 2 条。\n- 新增 scripts/lib/domain-layer-baseline.mjs:B1 新增 / B2 存量恶化 /\n B3 基线腐烂或缺 Owner / B4 过复核期,四类任一非空即阻断。B3 与 B4 守的是\n 基线自己——修好了必须删条目,过了复核期必须复核,否则基线会腐烂成豁免清单。\n- check-domain-layer 退出码改基线口径,--no-baseline 仍看未过滤的全量\n (13 条,退出 1);registry 里该条转 run-foundation-gates 阻断位。\n\n一处要点:棘轮只认单调变坏的量。D10 的 matched(命中源仓提交的文件数)与\nD11 的 probes(负向探针条数)都是越大越好,拿来当上限会把改进判成恶化、\n反过来把修复锁死;已在 findingCount 里排除并写明理由,现只有 D2 的 count\n做棘轮。这条有单测守着。\n\n顺带更正 check-workspace-consistency 那条已过期的基线文字:L8 已归零\n(并行会话登记了具名冻结豁免),L9 的「12 仓」按当日实测改为 8 个上层\n应用仓;其接入形态改写为照此先例走基线棘轮,不再用「全清零再接入」——\n否则又是一个可能长期悬空的流外出口。\n\n仍缺一道,已记台账 C-19:G4 至今不会因「wireInWhen 已成立」而判红,\n下一个流外出口还能同样悬空。\n\n证据:治理层 377 例 0 失败(新增 12 例负向)、阻断性门禁 11/11、\n工作区一致性仍 2 条(L9 / L12)。L13 当场抓出收纳表漂移,已随本提交改数\n(根文件 62→63、scripts 50→51、tests 33→34)。报告在脏树上产出,\n不随本提交,清树重跑后另行回绑。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:36:39-07:00"}],"HeadCommit":{"Sha1":"eca16cecb1b0e54e66d69268589ffa59c2fe6eff","Message":"chore(reports): 治理层门禁报告回绑 @ 3ca6a19\n\n清树重跑 run-foundation-gates:阻断性 11/11 通过(check-domain-layer 首次\n以阻断位计入,基线口径 0 阻断),仅记录 2(工作区一致性 L9 / L12)。\n三份报告 worktreeDirty=false,绑定 3ca6a19。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:37:02-07:00"},"CompareURL":"luoanwu/platform-governance/compare/1645e7288b484ab39a4e3ebb2da44678e9b9e300...eca16cecb1b0e54e66d69268589ffa59c2fe6eff","Len":2}...
|
1789688225
|
Edit
Delete
|
|
30725
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"693800cea {"Commits":[{"Sha1":"693800ceaf834b217a01466e19579af6a23925cf","Message":"chore(reports): 治理层门禁报告回绑 @ 87ec431\n\n清树重跑 run-foundation-gates:阻断性 11/11 通过,仅记录 2(工作区一致性\nL9 / L12)。三份报告 worktreeDirty=false,绑定 87ec431。\n\n(订正:本条信息初次写成「回绑 @ 9a5b3c0」,那是提交前预估的 SHA,实际\n实现提交是 87ec431。报告内容的绑定一直是对的,错的只是信息里的那串字。)\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:40:15-07:00"},{"Sha1":"87ec4315c77935405e16314c11789ddb6ae45e5a","Message":"feat(governance): G6 流外出口必须写复核期,缺失或过期即判红\n\n补上前一提交记为「仍缺一道」的缺口,不留登记而不建。\n\n根因:门禁消费登记的 G4 只断言 wireInWhen 非空,从不校验它是否已成立。\n流外出口是这份登记唯一的豁免口,而豁免口自己没有到期判据——用来防静音的\n机制在自己身上静音了。实锤就是前一提交处理的那条:check-domain-layer 的\n接入条件「D5 与 D9 清零」早已双双成立,G4 全绿,无人发现。\n\nG6 OUT_OF_FLOW_UNREVIEWED:流外条目必须写 conditionReviewBy(YYYY-MM-DD),\n缺失、格式不对或已过期即判红;当天不算过期;只对流外生效,阻断位条目每轮\n都在跑,不需要复核期。6 例负向覆盖这五种形态。\n\n守日期而不守条件是有意的:接入条件多半含人的判断(「框架同步波次扩散后」\n「再有派生仓开仓时」),机器判不了;能机器化的是「必须有人按期回来看一眼」。\n与同日落的域分层基线 B4 同形——缓期不是豁免。\n\n两条现存流外条目各自写了复核期与理由:\n- check-workspace-consistency 2026-10-31:L9 / L12 挂在活裁决 N-11 / C-14\n 上,六周内应有进展。\n- audit-platform-openings 2026-12-31:触发事件罕见,现存派生仓 0 个\n (派生仓状态.json 只剩 missing 1 + retired 18),不是六周尺度的事。\n\n台账 C-19 由「仍缺一道」改为已补,落点写明。\n\n证据:治理层 378 例 0 失败(新增 6 例负向)、阻断性门禁 11/11、\n工作区一致性仍 2 条(L9 / L12)。报告在脏树上产出,不随本提交。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:40:01-07:00"}],"HeadCommit":{"Sha1":"693800ceaf834b217a01466e19579af6a23925cf","Message":"chore(reports): 治理层门禁报告回绑 @ 87ec431\n\n清树重跑 run-foundation-gates:阻断性 11/11 通过,仅记录 2(工作区一致性\nL9 / L12)。三份报告 worktreeDirty=false,绑定 87ec431。\n\n(订正:本条信息初次写成「回绑 @ 9a5b3c0」,那是提交前预估的 SHA,实际\n实现提交是 87ec431。报告内容的绑定一直是对的,错的只是信息里的那串字。)\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T16:40:15-07:00"},"CompareURL":"luoanwu/platform-governance/compare/eca16cecb1b0e54e66d69268589ffa59c2fe6eff...693800ceaf834b217a01466e19579af6a23925cf","Len":2}...
|
1789688425
|
Edit
Delete
|
|
30727
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"689e924f3 {"Commits":[{"Sha1":"689e924f3db984f90ee13c2e0dd1a0082a70c1d3","Message":"docs(计划): 过期证据 9 → 8 且 error 清零;§1 证据行按 f9cb195 重采\n\n偏差 #34 裁决落地后的首轮清理:port-conformance 重绑、runtime 静态链四份\n重绑(WB-1 使 runtime/apps 变动而落进作用域)、工作台两份快照经\npnpm reports:rebind 重绑。check:evidence 由 failed 转 partial(27/8/1,0 error)。\n余 8 份全部需真实环境重跑,已逐一点名。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T18:22:48-07:00"}],"HeadCommit":{"Sha1":"689e924f3db984f90ee13c2e0dd1a0082a70c1d3","Message":"docs(计划): 过期证据 9 → 8 且 error 清零;§1 证据行按 f9cb195 重采\n\n偏差 #34 裁决落地后的首轮清理:port-conformance 重绑、runtime 静态链四份\n重绑(WB-1 使 runtime/apps 变动而落进作用域)、工作台两份快照经\npnpm reports:rebind 重绑。check:evidence 由 failed 转 partial(27/8/1,0 error)。\n余 8 份全部需真实环境重跑,已逐一点名。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T18:22:48-07:00"},"CompareURL":"luoanwu/platform-governance/compare/693800ceaf834b217a01466e19579af6a23925cf...689e924f3db984f90ee13c2e0dd1a0082a70c1d3","Len":1}...
|
1789694571
|
Edit
Delete
|
|
30731
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"150e625ed {"Commits":[{"Sha1":"150e625ed2a33300a3bc051fd4e60fa6e76a7947","Message":"docs(计划): 真实环境八份证据重跑通过,证据零过期(真源仓 36e0423)\n\n§1 证据新鲜度行与运行/UI 证据行按 2026-09-18 实测重采;§8 增一行。\n\n重跑:runtime-acceptance 775(地板 652 → 775)、ui-acceptance 5、\nmainline-acceptance 四套件 11/17/19/18、mainline-restore 3 库逐库 SHA-256\n一致、revocation-sla、identity-ui 2。退役(目录负责人裁决):identity-http\n与 mainline-candidate-regression,两者仓内无生成脚本、永远无法重跑,结论\n已由自动化门禁覆盖。\n\ncheck:evidence:33 新鲜 / 0 过期 / 0 告警 / 1 例外。\n\n如实保留:invalidationPush 仍是 measured-with-harness-transport,生产传输\n未接线,不构成 MS-3 达成证据。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T18:58:36-07:00"}],"HeadCommit":{"Sha1":"150e625ed2a33300a3bc051fd4e60fa6e76a7947","Message":"docs(计划): 真实环境八份证据重跑通过,证据零过期(真源仓 36e0423)\n\n§1 证据新鲜度行与运行/UI 证据行按 2026-09-18 实测重采;§8 增一行。\n\n重跑:runtime-acceptance 775(地板 652 → 775)、ui-acceptance 5、\nmainline-acceptance 四套件 11/17/19/18、mainline-restore 3 库逐库 SHA-256\n一致、revocation-sla、identity-ui 2。退役(目录负责人裁决):identity-http\n与 mainline-candidate-regression,两者仓内无生成脚本、永远无法重跑,结论\n已由自动化门禁覆盖。\n\ncheck:evidence:33 新鲜 / 0 过期 / 0 告警 / 1 例外。\n\n如实保留:invalidationPush 仍是 measured-with-harness-transport,生产传输\n未接线,不构成 MS-3 达成证据。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T18:58:36-07:00"},"CompareURL":"luoanwu/platform-governance/compare/689e924f3db984f90ee13c2e0dd1a0082a70c1d3...150e625ed2a33300a3bc051fd4e60fa6e76a7947","Len":1}...
|
1789696719
|
Edit
Delete
|
|
30741
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"a03bc2d77 {"Commits":[{"Sha1":"a03bc2d7789a81e0da6b79e51f2abb32fff2b906","Message":"docs(计划): stack-image-pins 退役,check:evidence 首次全绿(真源仓 a9fd6e8)\n\n第三份无生成脚本的手工记录按其例外自写的「倾向 ① 退役」执行。结论已由\nrelease-manifest 的 parseComposeImages 覆盖(同为 12 条 0 未锁,未锁进\nmissing,由真脚本产出自动保鲜)。evidence-scopes exceptions 自此为空。\n\n§1 证据行改为 passed(33 新鲜 / 0 过期 / 0 例外 / 0 告警);§8 增一行。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T19:01:40-07:00"}],"HeadCommit":{"Sha1":"a03bc2d7789a81e0da6b79e51f2abb32fff2b906","Message":"docs(计划): stack-image-pins 退役,check:evidence 首次全绿(真源仓 a9fd6e8)\n\n第三份无生成脚本的手工记录按其例外自写的「倾向 ① 退役」执行。结论已由\nrelease-manifest 的 parseComposeImages 覆盖(同为 12 条 0 未锁,未锁进\nmissing,由真脚本产出自动保鲜)。evidence-scopes exceptions 自此为空。\n\n§1 证据行改为 passed(33 新鲜 / 0 过期 / 0 例外 / 0 告警);§8 增一行。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T19:01:40-07:00"},"CompareURL":"luoanwu/platform-governance/compare/150e625ed2a33300a3bc051fd4e60fa6e76a7947...a03bc2d7789a81e0da6b79e51f2abb32fff2b906","Len":1}...
|
1789696904
|
Edit
Delete
|
|
30746
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"e81617fb8 {"Commits":[{"Sha1":"e81617fb827a3db190701bc33bca21cc14ce20c8","Message":"docs(计划): MS-4 判据输入纳入新鲜度监控;Manifest 缺项 4 → 6(真源仓 314c179)\n\nrelease-manifest / sbom / image-smoke / mainline-dev-deployment 此前被归为\n「没有 provenance.gitSha」,实为写了源 SHA 但平铺在顶层,check:evidence 只认\n嵌套形状。实锤危害:Manifest 绑 ac3683d 四天,其后结论输入改了 10 个文件,\n刷新后缺项 4 → 6,多出的 images.stack.* 未锁与 SBOM 不满足 D-2 两条都是真的\n——而 MS-4 的退出条件正是读这份 Manifest。\n\n§1 Release Manifest 行按刷新后的六项缺项重采;§1 证据行改为 35 份全新鲜;\n§8 增一行,含未做项与理由(image-smoke 待下次真实运行、mainline-dev-deployment\n无生成脚本属手工记录)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T19:21:54-07:00"}],"HeadCommit":{"Sha1":"e81617fb827a3db190701bc33bca21cc14ce20c8","Message":"docs(计划): MS-4 判据输入纳入新鲜度监控;Manifest 缺项 4 → 6(真源仓 314c179)\n\nrelease-manifest / sbom / image-smoke / mainline-dev-deployment 此前被归为\n「没有 provenance.gitSha」,实为写了源 SHA 但平铺在顶层,check:evidence 只认\n嵌套形状。实锤危害:Manifest 绑 ac3683d 四天,其后结论输入改了 10 个文件,\n刷新后缺项 4 → 6,多出的 images.stack.* 未锁与 SBOM 不满足 D-2 两条都是真的\n——而 MS-4 的退出条件正是读这份 Manifest。\n\n§1 Release Manifest 行按刷新后的六项缺项重采;§1 证据行改为 35 份全新鲜;\n§8 增一行,含未做项与理由(image-smoke 待下次真实运行、mainline-dev-deployment\n无生成脚本属手工记录)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T19:21:54-07:00"},"CompareURL":"luoanwu/platform-governance/compare/a03bc2d7789a81e0da6b79e51f2abb32fff2b906...e81617fb827a3db190701bc33bca21cc14ce20c8","Len":1}...
|
1789698116
|
Edit
Delete
|
|
30751
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ae6cf47e5 {"Commits":[{"Sha1":"ae6cf47e538de724c00c270f78ad014669585c8d","Message":"docs(计划): mainline-dev-deployment 退役,四份手工记录清零(真源仓 903f019)\n\n结论由 compose 的 redpanda 启用状态、四份更新的 runtime-up 记录与\ncheck:deployed 覆盖,三者都会自动保鲜;dev 栈此后已重建多轮,09-12 的\n快照早已不是当前事实。\n\n§1 证据行补第三步;§8 增一行。未登记 16 → 13。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T19:24:42-07:00"}],"HeadCommit":{"Sha1":"ae6cf47e538de724c00c270f78ad014669585c8d","Message":"docs(计划): mainline-dev-deployment 退役,四份手工记录清零(真源仓 903f019)\n\n结论由 compose 的 redpanda 启用状态、四份更新的 runtime-up 记录与\ncheck:deployed 覆盖,三者都会自动保鲜;dev 栈此后已重建多轮,09-12 的\n快照早已不是当前事实。\n\n§1 证据行补第三步;§8 增一行。未登记 16 → 13。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T19:24:42-07:00"},"CompareURL":"luoanwu/platform-governance/compare/e81617fb827a3db190701bc33bca21cc14ce20c8...ae6cf47e538de724c00c270f78ad014669585c8d","Len":1}...
|
1789698286
|
Edit
Delete
|
|
30776
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1b9402778 {"Commits":[{"Sha1":"1b940277848578801e16f969b874470ff90adce7","Message":"docs(治理): C-13 卷归属执行记录——备份 + 删卷已做,compose 半边未做\n\n决策批次 C-13 的附条件是「删卷前 dump 必须复验」,按字面执行:\n\n备份(/Users/hillao/AI产品/仓备份-2026-09-16/碰撞卷-C13/,24 MB)\n- 五个碰撞卷文件级 tar + 两个 PG 簇的 pg_dumpall,附 SHA256SUMS 与 README\n- 原卷全程 :ro,快照解到临时副本卷后在副本上起 PG 导出——在原卷上起 PG 会\n 触发 WAL 与恢复写入,而删不删当时尚未决定,不能先把它改了\n\n复验(不是「文件存在」)\n- 逻辑备份灌入全新空实例:4 库表数逐库一致,74 张表逐表 count(*) 零差异\n\n删除(核实确属历史遗留后)\n- 六个容器的工作目录全部指向迁移前旧布局,三条路径均已不存在,创建于\n 08-28—09-05;顺带清除一个漏网的同工程容器 api-nestjs-minio-init-1\n- 五卷 + 六容器清零,dev 常驻栈 13 容器未动、健康探针 200\n\n实测更正:api-nestjs_pgdata 占 47.8 MB 却是空簇(唯一库 0 张表),有数据的\n只有 enterprise-idp_pgdata(4 库 / 74 表 / ≈2088 行)。\n\n未做的半边:8 个上层应用仓的 compose 补顶层 name:,跨仓且待 N-11 裁决。\n因此 L9 仍报 1 条(它查 compose 声明,不是卷是否存在),C-14 抬内核 pin 的\n前置只部分满足——这一条同时写进了门禁消费登记,免得下次误读为「C-13 已完成」。\n\ncheck:gates 通过;gate-consumption 与 workspace-consistency 测试 46/46。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T20:13:04-07:00"}],"HeadCommit":{"Sha1":"1b940277848578801e16f969b874470ff90adce7","Message":"docs(治理): C-13 卷归属执行记录——备份 + 删卷已做,compose 半边未做\n\n决策批次 C-13 的附条件是「删卷前 dump 必须复验」,按字面执行:\n\n备份(/Users/hillao/AI产品/仓备份-2026-09-16/碰撞卷-C13/,24 MB)\n- 五个碰撞卷文件级 tar + 两个 PG 簇的 pg_dumpall,附 SHA256SUMS 与 README\n- 原卷全程 :ro,快照解到临时副本卷后在副本上起 PG 导出——在原卷上起 PG 会\n 触发 WAL 与恢复写入,而删不删当时尚未决定,不能先把它改了\n\n复验(不是「文件存在」)\n- 逻辑备份灌入全新空实例:4 库表数逐库一致,74 张表逐表 count(*) 零差异\n\n删除(核实确属历史遗留后)\n- 六个容器的工作目录全部指向迁移前旧布局,三条路径均已不存在,创建于\n 08-28—09-05;顺带清除一个漏网的同工程容器 api-nestjs-minio-init-1\n- 五卷 + 六容器清零,dev 常驻栈 13 容器未动、健康探针 200\n\n实测更正:api-nestjs_pgdata 占 47.8 MB 却是空簇(唯一库 0 张表),有数据的\n只有 enterprise-idp_pgdata(4 库 / 74 表 / ≈2088 行)。\n\n未做的半边:8 个上层应用仓的 compose 补顶层 name:,跨仓且待 N-11 裁决。\n因此 L9 仍报 1 条(它查 compose 声明,不是卷是否存在),C-14 抬内核 pin 的\n前置只部分满足——这一条同时写进了门禁消费登记,免得下次误读为「C-13 已完成」。\n\ncheck:gates 通过;gate-consumption 与 workspace-consistency 测试 46/46。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T20:13:04-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ae6cf47e538de724c00c270f78ad014669585c8d...1b940277848578801e16f969b874470ff90adce7","Len":1}...
|
1789701193
|
Edit
Delete
|
|
30787
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"bc014de63 {"Commits":[{"Sha1":"bc014de63a169082ff81ff54e77012c5fda7e50f","Message":"docs(计划): 登记偏差 #35——C-14「抬内核 pin」的实际范围是框架同步 74 冲突\n\n按目录负责人指令动工后实测:裁决文本说的是抬 pin,机制成本是一次完整框架\n同步。已完整撤回,未提交任何 pin 改动、未做框架合并。\n\n做到哪一步:12 处 pin 全改 0.22.0,pnpm install 成功、锁文件更新、\ncheck:pins 通过、构建 17/17、类型检查 31/31 全过。\n\n卡在哪:F11(check:fork-readiness)要求 @juhai/kernel pin 必须等于本仓\npackage.json.version——框架版本轴 = 内核版本轴;仓版本又被 check:docs-truth\n的 changelog-version-matches-package 绑到 runtime/CHANGELOG.md。\n\n真实范围(migration:plan,以框架仓为源,只读):冲突 74(apps/api-nestjs 22、\napps/api-fastify 14、apps/web 8,另含 check-dual-backend-parity.mjs、\ncheck-docs-truth.mjs、CLAUDE.md、package.json、pnpm-lock.yaml)、safe-copy 55、\nmerge-sensitive 12。六版累加含 F14 compose 身份、C34 健康经内核聚合、C35 统一\n访问日志与 req 序列化变更、新增 Dockerfile 与生产编排、三个门禁脚本迁入。\napi-nestjs 那 22 个正是平台装配点(端口合成 / HTTP 适配 / 运维命令 API)。\n\n反向的好消息:内核包本身六个 minor 只有 364 增 / 3 删,纯新增八个导出,且\ntenantIdFromClaims 改为 tenant_id → tenantId → tid 读序——本仓 FR-4 已被框架\n受理,对 DEC-032 canonical 租户是白赚。风险全在框架源码同步,不在内核 API。\n\n给三个处置选项待裁,并写明不可接受的第四条:只改 pin + 仓版本 + 补 CHANGELOG\n而不取框架源码——F11 会过,但仓就在声称自己是 0.22.0 却没有 0.22.0 的门禁与\n中间件,迁移凭证会记下一个假事实。\n\n门禁消费登记同步:L12 的接入条件应读作「待框架同步立项并完成」,不是「待抬\n一次 pin」。check:gates 通过,相关测试 46/46。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T20:54:37-07:00"}],"HeadCommit":{"Sha1":"bc014de63a169082ff81ff54e77012c5fda7e50f","Message":"docs(计划): 登记偏差 #35——C-14「抬内核 pin」的实际范围是框架同步 74 冲突\n\n按目录负责人指令动工后实测:裁决文本说的是抬 pin,机制成本是一次完整框架\n同步。已完整撤回,未提交任何 pin 改动、未做框架合并。\n\n做到哪一步:12 处 pin 全改 0.22.0,pnpm install 成功、锁文件更新、\ncheck:pins 通过、构建 17/17、类型检查 31/31 全过。\n\n卡在哪:F11(check:fork-readiness)要求 @juhai/kernel pin 必须等于本仓\npackage.json.version——框架版本轴 = 内核版本轴;仓版本又被 check:docs-truth\n的 changelog-version-matches-package 绑到 runtime/CHANGELOG.md。\n\n真实范围(migration:plan,以框架仓为源,只读):冲突 74(apps/api-nestjs 22、\napps/api-fastify 14、apps/web 8,另含 check-dual-backend-parity.mjs、\ncheck-docs-truth.mjs、CLAUDE.md、package.json、pnpm-lock.yaml)、safe-copy 55、\nmerge-sensitive 12。六版累加含 F14 compose 身份、C34 健康经内核聚合、C35 统一\n访问日志与 req 序列化变更、新增 Dockerfile 与生产编排、三个门禁脚本迁入。\napi-nestjs 那 22 个正是平台装配点(端口合成 / HTTP 适配 / 运维命令 API)。\n\n反向的好消息:内核包本身六个 minor 只有 364 增 / 3 删,纯新增八个导出,且\ntenantIdFromClaims 改为 tenant_id → tenantId → tid 读序——本仓 FR-4 已被框架\n受理,对 DEC-032 canonical 租户是白赚。风险全在框架源码同步,不在内核 API。\n\n给三个处置选项待裁,并写明不可接受的第四条:只改 pin + 仓版本 + 补 CHANGELOG\n而不取框架源码——F11 会过,但仓就在声称自己是 0.22.0 却没有 0.22.0 的门禁与\n中间件,迁移凭证会记下一个假事实。\n\n门禁消费登记同步:L12 的接入条件应读作「待框架同步立项并完成」,不是「待抬\n一次 pin」。check:gates 通过,相关测试 46/46。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T20:54:37-07:00"},"CompareURL":"luoanwu/platform-governance/compare/1b940277848578801e16f969b874470ff90adce7...bc014de63a169082ff81ff54e77012c5fda7e50f","Len":1}...
|
1789703681
|
Edit
Delete
|
|
30788
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"3cbdf7409 {"Commits":[{"Sha1":"3cbdf7409759ef6652fe7811dee6e30fb84baaa5","Message":"docs(计划): 框架同步 0.16.1 → 0.22.0 立项,分 F-1—F-7 七批\n\n目录负责人指令:偏差 #35 选③「框架同步单独立项」。新增立项书\ndocs/框架同步立项.md,文件名刻意不带日期——否则会被一致性门禁的\nHISTORY_NAME_PATTERN 当历史快照而跳过 L3/L4/L10 扫描(教训出自\n开发计划梳理-2026-09-14 的同名坑)。\n\n立项前逐文件核实,三条比首轮更准的事实:\n\n1. 74 个冲突里 20 个本仓从未改过(仍逐字节等于框架 v0.16.1),可直接快进;\n 真需三方合并的是 53 个,另 1 个是两侧各自新增的 .dockerignore\n2. apps/api-nestjs 的 17 个真冲突里只有 1 个在 src/platform/——首轮按目录\n 粗计说「22 个正是平台装配点」不成立。平台自有的七模块 / clients /\n platform-tests 共 531 文件全在 target-only,框架同步根本不碰\n3. 两个前置都比裁决时乐观:C-13 的卷那一半已执行;F14 在本仓基本已合规\n (runtime 的 compose 已是 ${COMPOSE_PROJECT_NAME:-…} 形式,只剩\n stack/compose.yaml 改变量形式与 act-runner 补 name:)\n\n内核 API 不是风险源:六个 minor 只有 364 增 / 3 删,纯新增八个导出,唯一\n语义变更是 tenantIdFromClaims 改读序——本仓 FR-4 被受理,对 DEC-032 是白赚。\n风险全在框架源码的行为接线(C34 / C35 / C39 / F14)。\n\n七批各带机器退出条件,F-4 两后端接线标为高风险(唯一会动 platform-ports.module.ts\n的批次)。立项书显式禁止「只改 pin + 版本 + CHANGELOG 而不取框架源码」——\nF11 会过,但会伪造迁移凭证,与本仓当日清理的病同源。\n\n§3A 增领取行,§6 偏差 #35 结论改为已选③并立项,README 增索引。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T20:57:38-07:00"}],"HeadCommit":{"Sha1":"3cbdf7409759ef6652fe7811dee6e30fb84baaa5","Message":"docs(计划): 框架同步 0.16.1 → 0.22.0 立项,分 F-1—F-7 七批\n\n目录负责人指令:偏差 #35 选③「框架同步单独立项」。新增立项书\ndocs/框架同步立项.md,文件名刻意不带日期——否则会被一致性门禁的\nHISTORY_NAME_PATTERN 当历史快照而跳过 L3/L4/L10 扫描(教训出自\n开发计划梳理-2026-09-14 的同名坑)。\n\n立项前逐文件核实,三条比首轮更准的事实:\n\n1. 74 个冲突里 20 个本仓从未改过(仍逐字节等于框架 v0.16.1),可直接快进;\n 真需三方合并的是 53 个,另 1 个是两侧各自新增的 .dockerignore\n2. apps/api-nestjs 的 17 个真冲突里只有 1 个在 src/platform/——首轮按目录\n 粗计说「22 个正是平台装配点」不成立。平台自有的七模块 / clients /\n platform-tests 共 531 文件全在 target-only,框架同步根本不碰\n3. 两个前置都比裁决时乐观:C-13 的卷那一半已执行;F14 在本仓基本已合规\n (runtime 的 compose 已是 ${COMPOSE_PROJECT_NAME:-…} 形式,只剩\n stack/compose.yaml 改变量形式与 act-runner 补 name:)\n\n内核 API 不是风险源:六个 minor 只有 364 增 / 3 删,纯新增八个导出,唯一\n语义变更是 tenantIdFromClaims 改读序——本仓 FR-4 被受理,对 DEC-032 是白赚。\n风险全在框架源码的行为接线(C34 / C35 / C39 / F14)。\n\n七批各带机器退出条件,F-4 两后端接线标为高风险(唯一会动 platform-ports.module.ts\n的批次)。立项书显式禁止「只改 pin + 版本 + CHANGELOG 而不取框架源码」——\nF11 会过,但会伪造迁移凭证,与本仓当日清理的病同源。\n\n§3A 增领取行,§6 偏差 #35 结论改为已选③并立项,README 增索引。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T20:57:38-07:00"},"CompareURL":"luoanwu/platform-governance/compare/bc014de63a169082ff81ff54e77012c5fda7e50f...3cbdf7409759ef6652fe7811dee6e30fb84baaa5","Len":1}...
|
1789703862
|
Edit
Delete
|
|
30789
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d70b1e5b6 {"Commits":[{"Sha1":"d70b1e5b6f3ed902a64adac86d0a4d953cadddb8","Message":"docs(计划): F-1 开工即证伪——「零判读快进」实收 0 个文件,本批取消\n\n按立项书从 F-1 起做,逐项审定 75 个候选(55 safe-copy + 20 个本仓从未改过的\n冲突文件)后实收 0 个,未改动仓内任何文件。\n\n拒收 44:\n- 30 个 packages/kernel/*:本仓不 vendor 内核源码,pin 的是已发布的\n @juhai/kernel;而 packages/* 在本仓 workspace 内,收进来会与 pin 直接冲突\n- 14 个示例 Order 域(orders.* / order.ts / orderMachine.ts / OrdersPanel.tsx):\n 本仓以 --strip-sample 建仓,实测 0 个同名文件,收回即让剥离回潮;仓内\n docs/strip-sample-domain.md 正是该机制的说明\n\n其余 31 个归位:F-2 门禁脚本 11、F-4 的 C34/C35/C39 接线面 12、F-5 部署物 4、\nF-3 COMPATIBILITY 1、F-6 文档 1,另 2 个保护路径延后判读。\n\n核心教训:migration:plan 的「safe-copy」标签指的是「目标没有这个文件」,不是\n「拿过来安全」。对一个 --strip-sample 且不 vendor 内核的派生仓,「目标没有」\n恰恰常常意味着「本仓刻意不要」。照单全收会同时干两件坏事:把剥离掉的示例域\n装回来、把 pin 的内核变成 vendor 的源码。\n\n立项书 §5.1 记下证伪与批次修正:不存在零判读快进层;余下六批内容不变,但每批\n开工须先逐文件审定,不得直接采信 migration:plan 的分类;F-2 成为实际起点。\n\n顺带修 L13:新增立项书使 平台治理/README.md 收纳表计数 157 → 158。\n全量一致性门禁回到 L9 / L12 两条常驻基线;测试 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-17T21:01:00-07:00"}],"HeadCommit":{"Sha1":"d70b1e5b6f3ed902a64adac86d0a4d953cadddb8","Message":"docs(计划): F-1 开工即证伪——「零判读快进」实收 0 个文件,本批取消\n\n按立项书从 F-1 起做,逐项审定 75 个候选(55 safe-copy + 20 个本仓从未改过的\n冲突文件)后实收 0 个,未改动仓内任何文件。\n\n拒收 44:\n- 30 个 packages/kernel/*:本仓不 vendor 内核源码,pin 的是已发布的\n @juhai/kernel;而 packages/* 在本仓 workspace 内,收进来会与 pin 直接冲突\n- 14 个示例 Order 域(orders.* / order.ts / orderMachine.ts / OrdersPanel.tsx):\n 本仓以 --strip-sample 建仓,实测 0 个同名文件,收回即让剥离回潮;仓内\n docs/strip-sample-domain.md 正是该机制的说明\n\n其余 31 个归位:F-2 门禁脚本 11、F-4 的 C34/C35/C39 接线面 12、F-5 部署物 4、\nF-3 COMPATIBILITY 1、F-6 文档 1,另 2 个保护路径延后判读。\n\n核心教训:migration:plan 的「safe-copy」标签指的是「目标没有这个文件」,不是\n「拿过来安全」。对一个 --strip-sample 且不 vendor 内核的派生仓,「目标没有」\n恰恰常常意味着「本仓刻意不要」。照单全收会同时干两件坏事:把剥离掉的示例域\n装回来、把 pin 的内核变成 vendor 的源码。\n\n立项书 §5.1 记下证伪与批次修正:不存在零判读快进层;余下六批内容不变,但每批\n开工须先逐文件审定,不得直接采信 migration:plan 的分类;F-2 成为实际起点。\n\n顺带修 L13:新增立项书使 平台治理/README.md 收纳表计数 157 → 158。\n全量一致性门禁回到 L9 / L12 两条常驻基线;测试 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-17T21:01:00-07:00"},"CompareURL":"luoanwu/platform-governance/compare/3cbdf7409759ef6652fe7811dee6e30fb84baaa5...d70b1e5b6f3ed902a64adac86d0a4d953cadddb8","Len":1}...
|
1789704064
|
Edit
Delete
|
|
30825
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"9a959dc86 {"Commits":[{"Sha1":"9a959dc86d101a8abfcd42db52f679d5dbb8de8c","Message":"docs(计划): 框架同步 0.16.1 → 0.22.0 完成,一致性门禁 L12 清零\n\n七批里 F-2a / F-2b / F-3 / F-4 / F-7 完成,F-1 证伪取消,F-5 撤回并提 FR-6,\nF-6 并入。真源仓 a63414a。\n\n验收(clean 765300b,与升级前逐项持平):runtime 775/775 且租户 RLS enforce、\nUI 5/5、主线四套件 11/17/19/18、恢复演练 passed、端口一致性 41/41,\ncheck:evidence passed 35 份全新鲜 / 0 过期 / 0 例外。\nmigration:record --mode sync 出凭证 frameworkVersion=0.22.0。\n\n立项书补两节:§5.2 执行记录(含同步过程中撞到的三件事:git show 重定向会造\n空文件、并入上游 CHANGELOG 带来跨仓断链、治理测试锚定旧 pin),§5.3 三级验收\n结果,并记下两次教训——\n- 一次假阴性:首轮报 682/775 失败 5 条,读错误码才发现是环境缺 MAINLINE_CHAOS_\n CONTAINER,不是代码回归。验收红了先读错误码,别先怀疑代码\n- 一次自伤:git checkout -- runtime/reports 连带把真跑出的六份验收证据还原成\n 旧版,只能重跑找回;还原前须按 provenance.gitSha 分辨本轮产出与脏绑\n\n常驻问题 L9 / L12 两条降为 L9 一条(8 个上层应用仓的 compose 身份,待 N-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-17T22:40:49-07:00"},{"Sha1":"48c5a9c821798dbd7b2aae8355a55aba95d68c20","Message":"docs(框架): 提 FR-6——四级新鲜度须按「该级别是否已接线」断言\n\n框架 0.22.0 把 check:docs-truth 的证据新鲜度断言由两级扩到四级,新增的部署 /\n生产两级在本仓无法成立:其证据生产者依赖 apps/api-nestjs/Dockerfile,而那份\n里写着 COPY packages/kernel/package.json——本仓按 DEC-010 / DEC-031 的分发口径\n只 exact pin 已发布的 @juhai/kernel,仓内不存在 packages/kernel,2026-09-18\n实测该镜像构建必然失败。本仓自己的制品镜像是另一套架构(runtime/Dockerfile,\nD-1),并存会变成两条镜像路径。\n\n结果是这道门禁在本仓只能恒红,而恒红门禁不携带信息——正是框架自己在 0.22.0\n里要治的失效模式的反面。\n\n请求:四级断言按该级别是否已接线判定——对应 pnpm 脚本在 package.json 里存在\n则断言照旧,不存在则打印 SKIPPED 并跳过。不接受占位报告,与 doctrine「诚实的\n空,不得用占位报告转绿」一致;接线了却让报告陈旧的仓仍照旧判红,门禁的牙一\n颗不少。\n\n临时处置已在本仓 runtime/scripts/check-docs-truth.mjs 落地,改动处带注释指向\n本 FR,框架受理后删除该段回到框架原文(同 FR-4 / FR-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-17T21:53:48-07:00"}],"HeadCommit":{"Sha1":"9a959dc86d101a8abfcd42db52f679d5dbb8de8c","Message":"docs(计划): 框架同步 0.16.1 → 0.22.0 完成,一致性门禁 L12 清零\n\n七批里 F-2a / F-2b / F-3 / F-4 / F-7 完成,F-1 证伪取消,F-5 撤回并提 FR-6,\nF-6 并入。真源仓 a63414a。\n\n验收(clean 765300b,与升级前逐项持平):runtime 775/775 且租户 RLS enforce、\nUI 5/5、主线四套件 11/17/19/18、恢复演练 passed、端口一致性 41/41,\ncheck:evidence passed 35 份全新鲜 / 0 过期 / 0 例外。\nmigration:record --mode sync 出凭证 frameworkVersion=0.22.0。\n\n立项书补两节:§5.2 执行记录(含同步过程中撞到的三件事:git show 重定向会造\n空文件、并入上游 CHANGELOG 带来跨仓断链、治理测试锚定旧 pin),§5.3 三级验收\n结果,并记下两次教训——\n- 一次假阴性:首轮报 682/775 失败 5 条,读错误码才发现是环境缺 MAINLINE_CHAOS_\n CONTAINER,不是代码回归。验收红了先读错误码,别先怀疑代码\n- 一次自伤:git checkout -- runtime/reports 连带把真跑出的六份验收证据还原成\n 旧版,只能重跑找回;还原前须按 provenance.gitSha 分辨本轮产出与脏绑\n\n常驻问题 L9 / L12 两条降为 L9 一条(8 个上层应用仓的 compose 身份,待 N-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-17T22:40:49-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d70b1e5b6f3ed902a64adac86d0a4d953cadddb8...9a959dc86d101a8abfcd42db52f679d5dbb8de8c","Len":2}...
|
1789710053
|
Edit
Delete
|
|
30850
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"4be34a841 {"Commits":[{"Sha1":"4be34a8411ad6ac48125865937ecad8ec32abc1f","Message":"docs(计划): 登记偏差 #36——S-5 转正的前提不成立,试做后撤回\n\n框架同步带来 FR-1(HealthResponse.checks 可扩展,0.19.0 受理),本仓提该 FR\n的动机正是让 S-5 模块健康子检查从「过渡方案」转正、汇入 /api/health。\n\n试做后撤回:接线后真实 DB 验收由 775 跌到 561,e2e/identity-profile.test.ts\n两条失败。读用例才看清——其中一条的名字就写着「identity 依赖故障时宿主数据库\n仍健康」,第 188—189 行是成对断言:模块视图须报 degraded,而宿主 /api/health\n须仍为 200。本仓早已有意分离「模块依赖故障」与「宿主运行时不健康」,我的改动\n等于把模块故障提升成宿主故障,破坏既有设计。\n\n已完整撤回,真源仓回到 a63414a / dirty 0,未提交任何接线改动。\n\n§6 增偏差 #36,给三个处置选项(维持分离 / 汇入但不影响状态码,需另提 FR 支持\nobservational 子检查 / 按模块 state 分级传导,属设计问题);裁决前 S-5 保持\n过渡方案,不因 FR-1 已受理就当作可转正。\n\n方法上的教训:FR 被受理 ≠ 它解锁的工作就该做;转正前要先读既有用例在守什么。\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-17T23:36:51-07:00"}],"HeadCommit":{"Sha1":"4be34a8411ad6ac48125865937ecad8ec32abc1f","Message":"docs(计划): 登记偏差 #36——S-5 转正的前提不成立,试做后撤回\n\n框架同步带来 FR-1(HealthResponse.checks 可扩展,0.19.0 受理),本仓提该 FR\n的动机正是让 S-5 模块健康子检查从「过渡方案」转正、汇入 /api/health。\n\n试做后撤回:接线后真实 DB 验收由 775 跌到 561,e2e/identity-profile.test.ts\n两条失败。读用例才看清——其中一条的名字就写着「identity 依赖故障时宿主数据库\n仍健康」,第 188—189 行是成对断言:模块视图须报 degraded,而宿主 /api/health\n须仍为 200。本仓早已有意分离「模块依赖故障」与「宿主运行时不健康」,我的改动\n等于把模块故障提升成宿主故障,破坏既有设计。\n\n已完整撤回,真源仓回到 a63414a / dirty 0,未提交任何接线改动。\n\n§6 增偏差 #36,给三个处置选项(维持分离 / 汇入但不影响状态码,需另提 FR 支持\nobservational 子检查 / 按模块 state 分级传导,属设计问题);裁决前 S-5 保持\n过渡方案,不因 FR-1 已受理就当作可转正。\n\n方法上的教训:FR 被受理 ≠ 它解锁的工作就该做;转正前要先读既有用例在守什么。\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-17T23:36:51-07:00"},"CompareURL":"luoanwu/platform-governance/compare/9a959dc86d101a8abfcd42db52f679d5dbb8de8c...4be34a8411ad6ac48125865937ecad8ec32abc1f","Len":1}...
|
1789713415
|
Edit
Delete
|
|
30852
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"e393d2db5 {"Commits":[{"Sha1":"e393d2db524e2c16a517866d412b1d039c01640a","Message":"docs(计划): 偏差 #36 裁决「维持分离」,S-5 由过渡方案改判为终态\n\n目录负责人裁定选项 ①:模块依赖故障 ≠ 宿主运行时不健康。模块健康只在\nGET /api/platform/modules[/:id/health] 可见,/api/health 只反映宿主依赖。\n\n两处改判:\n- S-5 不再标「过渡方案」而是终态。这条分离由 e2e/identity-profile.test.ts\n 第 188—189 行的成对断言守着,是设计不是欠账;真源仓已给该用例补注释说明\n 裁决出处与那次 775 → 561 的实锤\n- 跨目录待办更新:FR-1—5 已随框架 0.22.0 全部到位(FR-1 健康子检查 0.19.0、\n FR-4 租户 claim 读序 0.20.0、FR-5 runner 三值 0.20.0),余 FR-6 待受理\n\n偏差 #36 移入已关闭,并在其中记下「FR 被受理 ≠ 它解锁的工作就该做」。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T23:49:17-07:00"}],"HeadCommit":{"Sha1":"e393d2db524e2c16a517866d412b1d039c01640a","Message":"docs(计划): 偏差 #36 裁决「维持分离」,S-5 由过渡方案改判为终态\n\n目录负责人裁定选项 ①:模块依赖故障 ≠ 宿主运行时不健康。模块健康只在\nGET /api/platform/modules[/:id/health] 可见,/api/health 只反映宿主依赖。\n\n两处改判:\n- S-5 不再标「过渡方案」而是终态。这条分离由 e2e/identity-profile.test.ts\n 第 188—189 行的成对断言守着,是设计不是欠账;真源仓已给该用例补注释说明\n 裁决出处与那次 775 → 561 的实锤\n- 跨目录待办更新:FR-1—5 已随框架 0.22.0 全部到位(FR-1 健康子检查 0.19.0、\n FR-4 租户 claim 读序 0.20.0、FR-5 runner 三值 0.20.0),余 FR-6 待受理\n\n偏差 #36 移入已关闭,并在其中记下「FR 被受理 ≠ 它解锁的工作就该做」。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T23:49:17-07:00"},"CompareURL":"luoanwu/platform-governance/compare/4be34a8411ad6ac48125865937ecad8ec32abc1f...e393d2db524e2c16a517866d412b1d039c01640a","Len":1}...
|
1789714159
|
Edit
Delete
|
|
30853
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"5b7a1c033 {"Commits":[{"Sha1":"5b7a1c033ef290f7fa48f58bf0eae5eaa38150aa","Message":"docs(框架): FR-6 提交框架 Owner——在送达入口 README 登记待受理\n\nFR-6 的正文 2026-09-18 已写入 基础设施仓框架变更请求-2026-09-12.md(48c5a9c),\n但那份文档本身不是送达入口:框架 Owner 是从 工程基础框架/README.md 的变更请求\n条目看待办的(FR-1 / FR-4 / FR-5 与另两份平台治理的请求都是这么送达并受理的)。\n此前只写了正文没更新入口,等于没提。\n\nREADME 该条更新为:FR-1 已落地 0.19.0、FR-4 / FR-5 已落地 0.20.0、**FR-6 新提\n待受理**、FR-2 / FR-3 仍未受理,并就地摘出 FR-6 的请求与依据:\n\ncheck:docs-truth 的四级证据新鲜度须按「该级别是否已接线」判定。起因是基础设施仓\n同步到 0.22.0 时实测,新增的制品部署 / 生产运维两级依赖 apps/api-nestjs/Dockerfile,\n而那份里有 COPY packages/kernel/package.json——该仓按 DEC-010 / DEC-031 只 exact\npin 已发布的 @juhai/kernel,仓内不存在 packages/kernel,构建必然失败,这道门禁\n在该仓只能恒红。恒红门禁不携带信息,正是 0.22.0 自己要治的失效模式的反面。\n\n请求对应 pnpm 脚本存在则断言照旧、不存在则 SKIPPED,不接受占位报告;接线了却让\n报告陈旧的仓仍照旧判红。影响面是框架仓单点改动加一条负向用例。基础设施仓已本地\n修正并在改动处注释指向 FR-6,受理后删除该段回到框架原文。\n\n未触碰框架仓 base-framework(其工作区有 12 项他人在途改动)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T23:57:57-07:00"}],"HeadCommit":{"Sha1":"5b7a1c033ef290f7fa48f58bf0eae5eaa38150aa","Message":"docs(框架): FR-6 提交框架 Owner——在送达入口 README 登记待受理\n\nFR-6 的正文 2026-09-18 已写入 基础设施仓框架变更请求-2026-09-12.md(48c5a9c),\n但那份文档本身不是送达入口:框架 Owner 是从 工程基础框架/README.md 的变更请求\n条目看待办的(FR-1 / FR-4 / FR-5 与另两份平台治理的请求都是这么送达并受理的)。\n此前只写了正文没更新入口,等于没提。\n\nREADME 该条更新为:FR-1 已落地 0.19.0、FR-4 / FR-5 已落地 0.20.0、**FR-6 新提\n待受理**、FR-2 / FR-3 仍未受理,并就地摘出 FR-6 的请求与依据:\n\ncheck:docs-truth 的四级证据新鲜度须按「该级别是否已接线」判定。起因是基础设施仓\n同步到 0.22.0 时实测,新增的制品部署 / 生产运维两级依赖 apps/api-nestjs/Dockerfile,\n而那份里有 COPY packages/kernel/package.json——该仓按 DEC-010 / DEC-031 只 exact\npin 已发布的 @juhai/kernel,仓内不存在 packages/kernel,构建必然失败,这道门禁\n在该仓只能恒红。恒红门禁不携带信息,正是 0.22.0 自己要治的失效模式的反面。\n\n请求对应 pnpm 脚本存在则断言照旧、不存在则 SKIPPED,不接受占位报告;接线了却让\n报告陈旧的仓仍照旧判红。影响面是框架仓单点改动加一条负向用例。基础设施仓已本地\n修正并在改动处注释指向 FR-6,受理后删除该段回到框架原文。\n\n未触碰框架仓 base-framework(其工作区有 12 项他人在途改动)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T23:57:57-07:00"},"CompareURL":"luoanwu/platform-governance/compare/e393d2db524e2c16a517866d412b1d039c01640a...5b7a1c033ef290f7fa48f58bf0eae5eaa38150aa","Len":1}...
|
1789714680
|
Edit
Delete
|