|
30159
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"7340f6472 {"Commits":[{"Sha1":"7340f6472014bec4a3f1b148bc9b8c34507f69bf","Message":"fix(docs): 2026-09-05 治理日志的五条本地链接改为相对本文件的路径\n\n工作区一致性门禁 L4 在本仓报出五条失效链接,全在这一份文件。五个目标文件都在,\n问题是链接写成了仓根相对路径(docs/product/x.md),而本文件在 docs/governance/log/\n下,解析成 docs/governance/log/docs/product/x.md。\n\n改为相对本文件:docs/product|design/* → ../../product|design/*,docs/README.md →\n../../README.md,reports/* → ../../../reports/*。日志正文一字未动。\n\n核验:node 平台治理/基础/scripts/check-workspace-consistency.mjs --only L4 由 5 条\n降为 0(扫描面 33 个仓 / 5372 条本地链接)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:06:34-07:00"}],"HeadCommit":{"Sha1":"7340f6472014bec4a3f1b148bc9b8c34507f69bf","Message":"fix(docs): 2026-09-05 治理日志的五条本地链接改为相对本文件的路径\n\n工作区一致性门禁 L4 在本仓报出五条失效链接,全在这一份文件。五个目标文件都在,\n问题是链接写成了仓根相对路径(docs/product/x.md),而本文件在 docs/governance/log/\n下,解析成 docs/governance/log/docs/product/x.md。\n\n改为相对本文件:docs/product|design/* → ../../product|design/*,docs/README.md →\n../../README.md,reports/* → ../../../reports/*。日志正文一字未动。\n\n核验:node 平台治理/基础/scripts/check-workspace-consistency.mjs --only L4 由 5 条\n降为 0(扫描面 33 个仓 / 5372 条本地链接)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:06:34-07:00"},"CompareURL":"luoanwu/image-generation/compare/0724820e7884688d0466bc74563122005bbac86e...7340f6472014bec4a3f1b148bc9b8c34507f69bf","Len":1}...
|
1789468038
|
Edit
Delete
|
|
30158
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"68cb0ab2c {"Commits":[{"Sha1":"68cb0ab2c652fad74b929a1bd92b6c3b91aa1dc2","Message":"chore(reports): 在 clean HEAD 8b969bc 上重跑静态门禁并回绑\n\n九份报告的 provenance 全部绑定 8b969bc、worktreeDirty=false:caddy / catalog-drift /\ncatalog-reconciliation / evidence-freshness / facts / fixtures / migration-decs /\nmodule-imports / otel。check:fixtures 17 套件 166 例 0 失败 0 不可用;catalog:drift\n仍 error 0 / drift 4(四条已知待办走 CHG-002 → 003)。\n\ncheck:evidence 由 3 条告警增至 4 条:新增的一条是\nreports/port-conformance.latest.json(绑定 dbf0fb7),作用域内变更的唯一文件是\nruntime/modules/kit/src/facts.ts —— 上一提交里那处只改了文档注释。新鲜度判定按\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-15T03:06:27-07:00"},{"Sha1":"8b969bceb52bd11d9a456b51eb635350322be2d9","Message":"docs: 三处把已批准的 DEC 仍写作未决前置的陈述订正\n\n工作区一致性门禁 L10(已批准的 DEC 仍被写作未决前置)在本仓报出三处:\n\n- docs/owner-matrix.md:credential 的\"权威表等 DEC-006 / 007 / 025\"、scope 的\n \"等 DEC-001—005 / 017 / 018 / 039\"、ai-gateway 的\"路由与账本等 DEC-007\"。前述\n DEC 均已于 2026-09-12 批准,改写成\"未建(阻塞不在裁决侧)\";DEC-039 例外——它\n 至今未进机器 Catalog,仍待 CHG-002 登记,这半句保留。\n- runtime/modules/kit/src/facts.ts:顺序元数据\"待 DEC-013—016 定\"已由 DEC-016\n 裁定(Owner 单调 aggregateVersion、消费者 lastAppliedVersion + 有界 gap)。\n- contracts/candidates/facts/OrganizationUnitMoved.v1.json 的 note:组织 Owner 已由\n DEC-002 裁定(A 案:逻辑独立 Organization 域,首期宿主 HR,hosted_by 显式)。\n\nblocked_by 一个字没动。候选事实的过期阻塞位与 EmploymentTransferred 同属一类,\n改动走变更包(参照 CHG-007),不在本次范围。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:05:57-07:00"},{"Sha1":"171baf4983c82b9b2c1ba9cc4b3bfc7764be9a14","Message":"fix(contracts): 跨清单链接规则按 DEC-009 重写 —— 门禁不该把已批准的裁决反过来写\n\nSOURCE_MANIFEST_MISMATCH 判定 productId === app.id ∧ productVersion ===\napp.version,而 DEC-009(2026-09-12 批准,A 案)写明\"三清单独立 Schema / Owner /\n版本,跨清单只存引用\"——它要求两份清单同 id 同版本,正是该裁决明令分开的东西。\n\n后果是实测出来的:12 份 AppManifest 只有 juhai.hr 碰巧满足,另三个公用应用\"补了\nsourceManifest 也过不去\",于是干脆没人补,跨清单链接整体缺位(回灌台账 U-33、\ncheck-domain-layer 的 D3 三条)。\n\n规则改为只断言 DEC-009 允许断言的那部分:引用必须解析得到一份产品清单、且不含糊。\n新增导出 resolveProductDeclaration,认单产品文件(products/\u003cid\u003e/manifest.json、\nkernel.products.entry.json)与产品列表(kernel.products.json)两种在用形状;\nSOURCE_MANIFEST_MISMATCH 由 SOURCE_MANIFEST_NOT_A_PRODUCT 与\nSOURCE_MANIFEST_AMBIGUOUS(列表里多于一个产品)取代。id 与版本的一致性不归这里\n——版本相等而内容分叉的漂移由内容摘要对账承接(GAP-10;D7 / D10)。\n\n连带修掉一条此前永远报不出来的规则:SOURCE_MANIFEST_NOT_FOUND 在文件不存在时本该\n报,实际是下一行的 readJson 先抛原始 ENOENT、门禁在收齐 issues 之前就崩。写这条的\n负向用例时它没红,才发现。check() 改为返回存在性并据此短路。规则写了、触发条件让它\n对真实输入永不成立,与 D11 判的那类假绿同源。\n\n三份 AppManifest 各补一条 app.sourceManifest(字段本就在 Schema 里,非 Schema 变更)。\n\n核验:contracts 测试 270 → 278;scripts/check.mjs exit 0;check-domain-layer --only D3\n由 3 条降为 0;根链 check:modules / check:module-imports / check:catalog / check:facts /\ncheck:caddy / check:otel 全绿,governance 测试 215/215。负向实做两次:sourceManifest\n指向 contracts/package.json 触发 NOT_A_PRODUCT,指向不存在的路径触发 NOT_FOUND。\n\n未做:镜像 平台治理/platform-contracts 的同名 linter 未同步——它是 C5 待退役的旧副本,\n两份早已分叉。三个仓的 app.version 仍是占位的 0.1.0,DEC-009 下不再影响判定。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:05:49-07:00"},{"Sha1":"5a8ea1ffa427806d2d16ee01b8accab08b50e1fc","Message":"chore(reports): 摘除跳过豁免后在 clean HEAD 8a891fc 上重跑回绑\n\ncheck:evidence 13 份已登记报告全部新鲜。余下三条 EVIDENCE_STALE 是 runtime/UI\n与主线验收报告,需真实 DB/Redis 重跑,不在静态链范围。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T23:58:24-07:00"},{"Sha1":"8a891fc7c617ef141a0d750b91161e2500c8e5b4","Message":"fix(governance): 摘掉 dec-039 的跳过豁免,并禁止根链再出现 allow-unavailable\n\n治理机制自身的失效模式-2026-09-14 模式一判据 3。dec-039 套件的路径此前是迁移双\n替换产物,套件报 unavailable,而根链挂着 --allow-unavailable-suite\ndec-039-party-model,于是那 25 例正反向夹具**从来没有真正跑过**,门禁一直显示\n通过。永远红至少还刺眼,永远绿是彻底的静音。\n\n路径已在 1ecac14 修好、夹具实跑 25/25,本轮把豁免开关摘掉:check:fixtures 17 套件\n166 例,不可用 0,status=passed。\n\n护栏守根因不守当时的输出:任何 package.json 脚本再出现 --allow-unavailable 即红;\n另断言最近一次 fixtures 报告的不可用套件为 0、豁免名单为空。确有套件暂时跑不了时,\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-14T23:58:03-07:00"}],"HeadCommit":{"Sha1":"68cb0ab2c652fad74b929a1bd92b6c3b91aa1dc2","Message":"chore(reports): 在 clean HEAD 8b969bc 上重跑静态门禁并回绑\n\n九份报告的 provenance 全部绑定 8b969bc、worktreeDirty=false:caddy / catalog-drift /\ncatalog-reconciliation / evidence-freshness / facts / fixtures / migration-decs /\nmodule-imports / otel。check:fixtures 17 套件 166 例 0 失败 0 不可用;catalog:drift\n仍 error 0 / drift 4(四条已知待办走 CHG-002 → 003)。\n\ncheck:evidence 由 3 条告警增至 4 条:新增的一条是\nreports/port-conformance.latest.json(绑定 dbf0fb7),作用域内变更的唯一文件是\nruntime/modules/kit/src/facts.ts —— 上一提交里那处只改了文档注释。新鲜度判定按\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-15T03:06:27-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/b54b34efc535e49428e3f3d8fbe3b0e6fe204503...68cb0ab2c652fad74b929a1bd92b6c3b91aa1dc2","Len":15}...
|
1789468031
|
Edit
Delete
|
|
30157
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"a8c2c315c {"Commits":[{"Sha1":"a8c2c315c5987714bc084f534c364ca525639562","Message":"chore(governance): 清扫后重跑统一门禁入口并回写报告\n\n阻断性 7/7 通过;仅记录 3 道仍失败,但内容已变:\ncheck-workspace-consistency 22 → 4(L8 1 / L9 2 / L10 1),\ncheck-domain-layer 19 → 16(D3 三条已关),audit-platform-openings 5 条不变。\n\n剩下 25 条没有一条能由执行者单方面关闭:L8 要重做 CHG-001 补丁并重新基线;L9 两条\n卡在\"api-nestjs 与 enterprise-idp 两个 project 的共用卷里数据属于谁\";L10 最后一条\n在 active 的 Scope 仓内,而该仓正因\"收尾提交连带改文档\"被判红,随手改一句话正好\n制造它警告的失败;D5 = CHG-007(材料齐备、模拟器绿,等 Catalog Owner);D9 等 PF-04\n阶段 2;D2 / D4 / D6 / D7 / D10 是跨层的数据与装载动作;D11 要给工单 20 道、设备云\n17 道门禁各补负向探针;audit-platform-openings 五条等 E1 或那次 A / B / C 取舍。\n\n两份报告不带 provenance,工作树中另一会话的三份在途改动不影响本次结论。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:07:04-07:00"},{"Sha1":"cc81a45fecbf4ea14e8b9198270061f14ab89544","Message":"docs(governance): 企业控制面的横向梳理、十八个派生仓的移除路径、门禁清扫记录\n\n三份只读盘点,均不改 Catalog、不改模块状态、不下裁决。\n\n- 企业控制面完整梳理:把目录、真源、规则落点、Catalog 登记、门禁、运行与缺口\n 合到一张表上。实测 18 个派生仓的独有规则已全部迁出(模块域 6、契约包域 9、\n 网关与观测两处由组件配置承接),并标出六处已被事实推翻的旧陈述——README 的\n 架构图六框表、项目完整能力表 E02/E06、CHG-003 材料的机器事实基线。\n\n- 十八个派生仓的移除路径:把\"移除\"拆成冻结写入 / 解除登记依赖 / 物理删除三件事。\n 历史安全性已不是问题(18 仓全部有 Gitea 远端且 origin/main == HEAD,另有 18 份\n bundle);94% 的体积与治理无关(18 GB / 947,810 个磁盘文件,受控文件只有 5,486\n 个)。按 delta 语义逐仓模拟 CHG-002/003/006 合并后,9 个仓证据残余归零、9 个不归零,\n 此前无任何文档给过这个分档。四类阻塞里只有 directory 双向绑定没有任何变更包覆盖。\n\n- 三道仅记录门禁的清扫记录:本轮清扫的执行记录与未关项的归属。\n\n当日实跑推翻一条旧记录:CHG-002/003/006/007 四个模拟器全部 passed、formalMutated\nfalse,而 CHG-006 README 记的 2026-09-14 实测是三个 blocked、\"CHG-001 重做是前置\"。\n该前置是否仍成立需按今天的结果重判。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:05:39-07:00"},{"Sha1":"edfd2ec2814c85007a5019d02e1d6b0d0b258061","Message":"fix(governance): 三道仅记录门禁的清扫 —— 报出来的每一条都应当是能直接去改的\n\n`check-workspace-consistency` 22 → 4。三道 report-only 门禁长期全红,正落在\n`门禁消费登记.json` 自己写的那句判词里:门禁能跑、结果无人看,于是稳定在\"永远红\"\n或\"永远绿\",两种都不携带信息。\n\n门禁改造两处:\n\n- L3 / L10 放过冻结派生仓。13 个 archived-20260910 仓由 check-archived-derived-repos\n (阻塞档)断言 tag = HEAD ∧ 工作树 clean,改一个字节它就红——也就是说 L3 / L10 在\n 那里报出来的东西没有一条能直接去改,与 L10 自己立的收敛原则正相反。新增\n frozenDerivedRepoPrefixes / isFrozenDerivedRepo,只放过 archived 一档:active 的\n 5 个仍在视野内,清扫后剩下的唯一一条 L10 就在其中,没被误放过。\n\n- 冻结物的二次替换由 L2 改归 L8。L2 要求改掉字符串、L7 要求字节与 sha256 相符,\n 同一份文件两个相反的要求。L8(摘要相符、内容却仍是旧布局)本来就是为这种情形\n 存在的,其处置口径——重做变更包并重新基线——才执行得了。staleLayoutHits 增收\n 二次替换,L2 跳过审批记录登记的冻结物。该条仍是红的,只是红在正确的位置。\n\nD3 的前提订正:旧判据照抄契约 linter 的 productId === app.id ∧ productVersion ===\napp.version,而 DEC-009(2026-09-12 批准)写明\"三清单独立 Schema / Owner / 版本,\n跨清单只存引用\"——把一条已批准的裁决反过来写。linkSatisfiability 按新前提重写,\n唯一剩下的不可满足情形是\"产品列表里多于一个产品\"。契约侧的规则重写另仓提交。\n\n正文订正 22 处:DEC-010 / 031 / 032 于 2026-09-10 批准,其余 27 条于 2026-09-12\n决策会批准,各处按裁决原文改写,把\"卡在裁决\"与\"卡在没做\"分开。集中观测那条不是\n滞后而是被事实推翻——Collector 已在 stack/otel 部署并由 check:otel 守着。\n\n五个文件加 `一致性门禁豁免: L10` 并写明理由:两份 DEC 草案与待裁决架构事项逐条\n转录裁决原文,其中\"Workload Identity 待 DEC-024 后复评\"是裁决自带的条件条款,不是\n对 DEC-024 审批状态的断言,不得为了让门禁变绿而改写。\n\n回灌台账 U-33 关闭,两次订正的轨迹保留:第一次把\"规则写错了\"误判成\"各仓没补数据\",\n第二次才查到规则与已批准的裁决冲突——判定前提本身可能是错的,这类缺口按\"谁没做\"\n派活会一直派错人。\n\n核验:tests/workspace-consistency 19 → 24,tests/domain-layer 47/47,平台治理/基础\n全量 302(297 通过 / 5 跳过);run-foundation-gates 阻塞档 7/7;\ncheck-archived-derived-repos 13/13(全程未改任何冻结仓)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:05:31-07:00"}],"HeadCommit":{"Sha1":"a8c2c315c5987714bc084f534c364ca525639562","Message":"chore(governance): 清扫后重跑统一门禁入口并回写报告\n\n阻断性 7/7 通过;仅记录 3 道仍失败,但内容已变:\ncheck-workspace-consistency 22 → 4(L8 1 / L9 2 / L10 1),\ncheck-domain-layer 19 → 16(D3 三条已关),audit-platform-openings 5 条不变。\n\n剩下 25 条没有一条能由执行者单方面关闭:L8 要重做 CHG-001 补丁并重新基线;L9 两条\n卡在\"api-nestjs 与 enterprise-idp 两个 project 的共用卷里数据属于谁\";L10 最后一条\n在 active 的 Scope 仓内,而该仓正因\"收尾提交连带改文档\"被判红,随手改一句话正好\n制造它警告的失败;D5 = CHG-007(材料齐备、模拟器绿,等 Catalog Owner);D9 等 PF-04\n阶段 2;D2 / D4 / D6 / D7 / D10 是跨层的数据与装载动作;D11 要给工单 20 道、设备云\n17 道门禁各补负向探针;audit-platform-openings 五条等 E1 或那次 A / B / C 取舍。\n\n两份报告不带 provenance,工作树中另一会话的三份在途改动不影响本次结论。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:07:04-07:00"},"CompareURL":"luoanwu/platform-governance/compare/1a4d98035c3dd75f82c2ac63f1c7e557ddb764d6...a8c2c315c5987714bc084f534c364ca525639562","Len":3}...
|
1789468023
|
Edit
Delete
|
|
30106
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1a4d98035 {"Commits":[{"Sha1":"1a4d98035c3dd75f82c2ac63f1c7e557ddb764d6","Message":"chore(governance): 刷新门禁运行报告 —— D11 落地后领域层由 17 条增至 19 条\n\n本次 run-foundation-gates 的结果:阻断性 7/7 通过,仅记录 3。\ncheck-domain-layer 由 17 条增至 19 条,增量是 D11 新报的两条——工单 20 道、\n设备云 17 道门禁一条负向探针都没有,从未证明过自己会红。条数上升不是退步:\n此前这 37 道门禁的状态是不可知,现在是已知未验证。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:59:22-07:00"}],"HeadCommit":{"Sha1":"1a4d98035c3dd75f82c2ac63f1c7e557ddb764d6","Message":"chore(governance): 刷新门禁运行报告 —— D11 落地后领域层由 17 条增至 19 条\n\n本次 run-foundation-gates 的结果:阻断性 7/7 通过,仅记录 3。\ncheck-domain-layer 由 17 条增至 19 条,增量是 D11 新报的两条——工单 20 道、\n设备云 17 道门禁一条负向探针都没有,从未证明过自己会红。条数上升不是退步:\n此前这 37 道门禁的状态是不可知,现在是已知未验证。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:59:22-07:00"},"CompareURL":"luoanwu/platform-governance/compare/407fe08edcf66ba3b09c111db4d1824ff9dd58bb...1a4d98035c3dd75f82c2ac63f1c7e557ddb764d6","Len":1}...
|
1789459164
|
Edit
Delete
|
|
30105
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"407fe08ed {"Commits":[{"Sha1":"407fe08edcf66ba3b09c111db4d1824ff9dd58bb","Message":"feat(governance): D11 —— 门禁有没有证明过自己会红\n\n本轮反复撞上同一个形态:规则写了,但触发条件让它对真实数据永远不成立。\nU-31(:503 只判反方向)、U-33(:781 把\"一应用一产品同 id 同版本\"写死成前提)、\nU-36(把\"跑不起来\"写成\"0 例通过\")三条各自独立,共同特征是**门禁一直是绿的,\n而绿得没有信息量**。\n\n仓里本来就有对症机制:负向探针——故意注入一个该被拦的缺陷,断言门禁确实拦住了。\n知识云的 docs-truth 正是靠它自报\"数字负向探针只命中 7/9,门禁可能是假绿\"。\n\nD11 把这个机制提到工作区一层,两类判定严重程度不同:\n- 哑探针(detected 非 true):门禁自己注入的缺陷没被自己抓到 → 假绿,硬失败\n- 无探针:从未证明过自己会红 → 不等于坏,但等于未经验证\n\n实测:434 条探针哑火 0 条,机制本身健康;但覆盖极不对称——\n 知识云 15/24 道门禁有探针、HR 11/25,**工单 0/20、设备云 0/17**\n后两仓的 37 道门禁从未证明过自己会红。\n\n探针字段名各仓不统一(negativeProbes / probes / *ProbeResults / shadowNegativeProbes),\n按**形状**递归收集而非字段名白名单:白名单会随新门禁漂移,而漂移的方向恰好是\n\"漏掉新探针\"——那正是本判据要防的。detected 只认严格 true,缺字段 / null /\n字符串 \"true\" 一律算哑火。\n\n夹具用例 47/47。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:57:04-07:00"}],"HeadCommit":{"Sha1":"407fe08edcf66ba3b09c111db4d1824ff9dd58bb","Message":"feat(governance): D11 —— 门禁有没有证明过自己会红\n\n本轮反复撞上同一个形态:规则写了,但触发条件让它对真实数据永远不成立。\nU-31(:503 只判反方向)、U-33(:781 把\"一应用一产品同 id 同版本\"写死成前提)、\nU-36(把\"跑不起来\"写成\"0 例通过\")三条各自独立,共同特征是**门禁一直是绿的,\n而绿得没有信息量**。\n\n仓里本来就有对症机制:负向探针——故意注入一个该被拦的缺陷,断言门禁确实拦住了。\n知识云的 docs-truth 正是靠它自报\"数字负向探针只命中 7/9,门禁可能是假绿\"。\n\nD11 把这个机制提到工作区一层,两类判定严重程度不同:\n- 哑探针(detected 非 true):门禁自己注入的缺陷没被自己抓到 → 假绿,硬失败\n- 无探针:从未证明过自己会红 → 不等于坏,但等于未经验证\n\n实测:434 条探针哑火 0 条,机制本身健康;但覆盖极不对称——\n 知识云 15/24 道门禁有探针、HR 11/25,**工单 0/20、设备云 0/17**\n后两仓的 37 道门禁从未证明过自己会红。\n\n探针字段名各仓不统一(negativeProbes / probes / *ProbeResults / shadowNegativeProbes),\n按**形状**递归收集而非字段名白名单:白名单会随新门禁漂移,而漂移的方向恰好是\n\"漏掉新探针\"——那正是本判据要防的。detected 只认严格 true,缺字段 / null /\n字符串 \"true\" 一律算哑火。\n\n夹具用例 47/47。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:57:04-07:00"},"CompareURL":"luoanwu/platform-governance/compare/86a7e52c6b5843851881a91625bc944a51df2205...407fe08edcf66ba3b09c111db4d1824ff9dd58bb","Len":1}...
|
1789459149
|
Edit
Delete
|
|
30104
|
5
|
5
|
5
|
80
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"50f4399dc {"Commits":[{"Sha1":"50f4399dc7bb4ef9be6f97aa60a8e3148667c3e2","Message":"chore(governance): 在 clean HEAD 上重跑静态门禁,证据第一次绑定当前提交\n\n迁移后本仓 19 份 reports/*.latest.json 无一绑定当前 HEAD,全部生成于 2026-08-26 /\n09-10 的旧树,按证据纪律一律按 STALE 对待——也就是说当前 HEAD 的质量一直是未知数。\n\n本次在 clean HEAD (bda8349) 上逐条重跑全部静态门禁:12 通过 / 2 失败,14 份报告\nprovenance 全部 gitSha=bda8349 且 worktreeDirty=false。\n\n两条失败都是跨仓耦合,不是本仓静态问题:\n- check-evidence-current:os-product-runtime 的 upstream 指向基座 checkout 状态\n- check-os-product-compat:产品兼容性需要基座侧路径\n\n不跑需实例的门禁(runtime / UI / 容器 / 灾备),那些要 DATABASE_URL 与浏览器,\n按证据等级\"静态 \u003c 真实 DB \u003c 浏览器\",本次只提升到静态一级。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:34:03-07:00"}],"HeadCommit":{"Sha1":"50f4399dc7bb4ef9be6f97aa60a8e3148667c3e2","Message":"chore(governance): 在 clean HEAD 上重跑静态门禁,证据第一次绑定当前提交\n\n迁移后本仓 19 份 reports/*.latest.json 无一绑定当前 HEAD,全部生成于 2026-08-26 /\n09-10 的旧树,按证据纪律一律按 STALE 对待——也就是说当前 HEAD 的质量一直是未知数。\n\n本次在 clean HEAD (bda8349) 上逐条重跑全部静态门禁:12 通过 / 2 失败,14 份报告\nprovenance 全部 gitSha=bda8349 且 worktreeDirty=false。\n\n两条失败都是跨仓耦合,不是本仓静态问题:\n- check-evidence-current:os-product-runtime 的 upstream 指向基座 checkout 状态\n- check-os-product-compat:产品兼容性需要基座侧路径\n\n不跑需实例的门禁(runtime / UI / 容器 / 灾备),那些要 DATABASE_URL 与浏览器,\n按证据等级\"静态 \u003c 真实 DB \u003c 浏览器\",本次只提升到静态一级。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:34:03-07:00"},"CompareURL":"luoanwu/juhai-device-cloud/compare/bda8349f3440331dc74da6a4a41880607201d63d...50f4399dc7bb4ef9be6f97aa60a8e3148667c3e2","Len":1}...
|
1789458924
|
Edit
Delete
|
|
30103
|
5
|
5
|
5
|
84
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"cbf31b3bc {"Commits":[{"Sha1":"cbf31b3bc76e8f62c1587f5ffb1ed4703f4760b8","Message":"chore(governance): 接真实 DB 重跑,19/19 全绿,并证实 3 处\"文档漂移\"是级联假象\n\n上一轮只提交了静态面 17 份,刻意留下 backend-behavior-parity 与 docs-truth——\n前者无实例时会把\"跑不起来\"写成\"0 例通过\",后者被这个 0 带塌(CLAUDE.md 记 28 例\nvs 机器真源 0)。本轮补上实例把这条链跑通。\n\n按本目录\"每轮新建空验收库\"的口径,建独立库而不是用 dev 库:\n juhai_knowledge_cloud_parity_20260915(prisma migrate deploy 后为空库)\n REDIS_URL 用 /13 号逻辑库,避开 .env 的 /12\n\n结果:\n- backend-behavior-parity 28 个 HTTP/DB/outbox 黑盒检查一致,负向探针 3/3\n ——28 正是 CLAUDE.md 记的数字,证实那个 0 纯粹是\"跑不起来\"的产物(U-36)\n- docs-truth 由 3 处漂移变为通过,**且数字负向探针由 7/9 升为 9/9**——此前它自己\n 报的\"门禁可能是假绿\"成立:parity 数字为 0 时两条探针是哑的,现在才真正有效\n- 静态 + 真实 DB 合计 19/19 全绿,19 份报告 provenance 全部绑定 558e30b 且\n worktreeDirty=false\n\n证据等级由\"静态\"提升到\"真实 DB\"(浏览器一级仍未做)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:45:32-07:00"},{"Sha1":"f77022f4abb4c9de6fc4d7214432480dc3a2cd6e","Message":"chore(governance): 在 clean HEAD 上重跑静态门禁,证据第一次绑定当前提交\n\n迁移后本仓 27 份 reports/*.latest.json 无一绑定当前 HEAD,全部生成于脏树,按证据\n纪律一律 STALE——当前 HEAD 的质量一直是未知数。\n\n本次在 clean HEAD (558e30b) 上重跑:静态面 17/17 全绿,17 份报告 provenance 全部\ngitSha=558e30b 且 worktreeDirty=false。\n\n刻意**不**提交两份:\n- backend-behavior-parity:实跑证实它需要 DATABASE_URL + REDIS_URL\n (test/backend.behavior.parity.test.ts:385 直接抛),属需实例门禁。无实例时它会\n 写出\"0 例\"的报告——把\"跑不起来\"记成\"0 例通过\",比留着旧报告更坏。\n- docs-truth:它的失败是上一条的级联——CLAUDE.md 记的 parity 是 28 例,而机器真源\n 被上一条写成 0,于是判文档漂移。根因消除前这份报告没有意义。\n\n按证据等级\"静态 \u003c 真实 DB \u003c 浏览器\",本次只提升到静态一级;那两条与 runtime / UI\n一起要另起一轮带实例的。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:34:57-07:00"}],"HeadCommit":{"Sha1":"cbf31b3bc76e8f62c1587f5ffb1ed4703f4760b8","Message":"chore(governance): 接真实 DB 重跑,19/19 全绿,并证实 3 处\"文档漂移\"是级联假象\n\n上一轮只提交了静态面 17 份,刻意留下 backend-behavior-parity 与 docs-truth——\n前者无实例时会把\"跑不起来\"写成\"0 例通过\",后者被这个 0 带塌(CLAUDE.md 记 28 例\nvs 机器真源 0)。本轮补上实例把这条链跑通。\n\n按本目录\"每轮新建空验收库\"的口径,建独立库而不是用 dev 库:\n juhai_knowledge_cloud_parity_20260915(prisma migrate deploy 后为空库)\n REDIS_URL 用 /13 号逻辑库,避开 .env 的 /12\n\n结果:\n- backend-behavior-parity 28 个 HTTP/DB/outbox 黑盒检查一致,负向探针 3/3\n ——28 正是 CLAUDE.md 记的数字,证实那个 0 纯粹是\"跑不起来\"的产物(U-36)\n- docs-truth 由 3 处漂移变为通过,**且数字负向探针由 7/9 升为 9/9**——此前它自己\n 报的\"门禁可能是假绿\"成立:parity 数字为 0 时两条探针是哑的,现在才真正有效\n- 静态 + 真实 DB 合计 19/19 全绿,19 份报告 provenance 全部绑定 558e30b 且\n worktreeDirty=false\n\n证据等级由\"静态\"提升到\"真实 DB\"(浏览器一级仍未做)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:45:32-07:00"},"CompareURL":"luoanwu/juhai-knowledge-cloud/compare/558e30bac2666ebe08fed4d2649e433638ead6c6...cbf31b3bc76e8f62c1587f5ffb1ed4703f4760b8","Len":2}...
|
1789458923
|
Edit
Delete
|
|
30102
|
5
|
5
|
5
|
82
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"7c4b197f0 {"Commits":[{"Sha1":"7c4b197f018b02f5ed675758af3f5be5dbd1de02","Message":"chore(governance): 在 clean HEAD 上重跑静态门禁,证据第一次绑定当前提交\n\n迁移后本仓 22 份 reports/*.latest.json 无一绑定当前 HEAD,21 份还生成于脏树,\n按证据纪律一律 STALE——当前 HEAD 的质量一直是未知数。\n\n本次在 clean HEAD (ab2e7f1) 上逐条重跑:15 通过 / 3 失败,16 份报告 provenance\n全部 gitSha=ab2e7f1 且 worktreeDirty=false。\n\n三条失败**不是判定失败,是跑不起来**——缺环境变量,属需实例门禁:\n- check-capacity CAPACITY_FASTIFY_URL\n- check-dual-backend-behavior DATABASE_URL + REDIS_URL\n- check-outbox-operations DATABASE_URL\n\n也就是说本仓静态面 15/15 全绿。按证据等级\"静态 \u003c 真实 DB \u003c 浏览器\",本次只提升\n到静态一级;需实例那三条要另起一轮。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:34:15-07:00"}],"HeadCommit":{"Sha1":"7c4b197f018b02f5ed675758af3f5be5dbd1de02","Message":"chore(governance): 在 clean HEAD 上重跑静态门禁,证据第一次绑定当前提交\n\n迁移后本仓 22 份 reports/*.latest.json 无一绑定当前 HEAD,21 份还生成于脏树,\n按证据纪律一律 STALE——当前 HEAD 的质量一直是未知数。\n\n本次在 clean HEAD (ab2e7f1) 上逐条重跑:15 通过 / 3 失败,16 份报告 provenance\n全部 gitSha=ab2e7f1 且 worktreeDirty=false。\n\n三条失败**不是判定失败,是跑不起来**——缺环境变量,属需实例门禁:\n- check-capacity CAPACITY_FASTIFY_URL\n- check-dual-backend-behavior DATABASE_URL + REDIS_URL\n- check-outbox-operations DATABASE_URL\n\n也就是说本仓静态面 15/15 全绿。按证据等级\"静态 \u003c 真实 DB \u003c 浏览器\",本次只提升\n到静态一级;需实例那三条要另起一轮。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:34:15-07:00"},"CompareURL":"luoanwu/juhai-ai-work-order-system/compare/ab2e7f155b4fbe2e9bebc1ac4887247efc0e97c7...7c4b197f018b02f5ed675758af3f5be5dbd1de02","Len":1}...
|
1789458921
|
Edit
Delete
|
|
30101
|
5
|
5
|
5
|
83
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"3c9f6df78 {"Commits":[{"Sha1":"3c9f6df78f540226554cb4ecc6115741fe478c41","Message":"chore(governance): 接真实 DB 重跑,13→15 通过,并暴露 outbox 多实例的可复现失败\n\n按本目录\"每轮新建空验收库\"的口径建独立库:\n juhai_ai_hr_system_parity_20260915(prisma migrate deploy 后为空库)\n REDIS_URL 用 /14 号逻辑库\n\n库名前缀不是随便起的——G15 守卫按 package.json 的 name 推导(juhai_ai_hr_system),\n首次用 juhai_hr_parity_* 被三条门禁正确拒绝:\"Database … does not belong to …\"。\n守卫工作正常,是库名起错了。\n\n接上实例后两条转绿:check-dual-backend-behavior、check-health-dependency-failure。\n\n**新暴露一条可复现失败:check-outbox-multi-instance**\n nestjs / fastify 双侧同样结果:dispatched=120, observed=0, subscriberStatus=ready\n连跑两次一致。门禁本身跑完了全程,不是\"缺环境变量跑不起来\"那一类。根因未定——\n可能是缺少未文档化的 relay / worker 配置(本仓 .env 里没有任何 REDIS/DATABASE 项),\n也可能是真实缺陷。不在此下结论,交仓 Owner;报告如实记录该结果。\n\n仍失败的另外 4 条:api-migration-safety 需 MIGRATION_TEST_ADMIN_URL;\nos-product-host-ui 需浏览器;os-product-layer 与 os-product-registration 分别级联于\nhost-ui 报告与 target OS checkout / runtime 验收证据。\n\n18 份报告 provenance 全部绑定 d970541 且 worktreeDirty=false;连接串中口令已按仓内\n既有口径脱敏为 app:***,仅余本机地址与库名。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:50:03-07:00"},{"Sha1":"d970541bd56e5f82659322c8f738d2f5d49c1770","Message":"chore(governance): 命名门禁修复后在新 HEAD 上重跑,静态面由 12 通过升为 13\n\n上一提交(8d74d4d)改了 scripts/ 下四个治理模块,按证据纪律旧报告随即失效——\n本提交只动 reports/,绑定 8d74d4d,与源码内容一一对应。\n\n静态门禁 13 通过 / 7 失败。7 条里没有一条是本仓代码质量问题:\n- 4 条缺实例:dual-backend-behavior / health-dependency-failure /\n outbox-multi-instance 需 DATABASE_URL,api-migration-safety 需\n MIGRATION_TEST_ADMIN_URL(这三份报告刻意不提交,见上一轮说明)\n- 1 条崩栈:os-product-host-ui\n- 2 条级联:os-product-layer 卡在 host-ui 报告,\n os-product-registration-verification 卡在 target OS checkout 与 runtime 验收证据\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:41:17-07:00"},{"Sha1":"8d74d4d814aad8e2df43f867e1dd61baf59b9075","Message":"fix(governance): 命名门禁 32 条违规逐行豁免 —— 治理脚本里的 terminal 是终态不是终端\n\na0ebf77(当前 HEAD 的前一提交)引入 scripts/lib/database-rls-*-governance.mjs 与\nos-product-migration-governance.mjs 时,命名门禁没跑过——提交后 naming 由 0 条变\n32 条,而 reports/naming.latest.json 停在 09-01 的 violations: 0,没人看得见。\n这正是\"无一份证据绑定当前 HEAD\"的实际后果。\n\n32 条全部是误报类:\n- 31 × terminal:`employment-terminal-late-authority-revoke` 这类指的是**迁移序列\n 与 RLS 的终态**,业务词典要求改成 device(设备)在这里是错的\n- 1 × business:`shared business database` 是 PostgreSQL 术语,不是业务方\n\n扫描面与词典自 2026-08-25 bootstrap 起未变,所以不是门禁改严了,是新代码撞上了\n一直存在的词表。\n\n用门禁自带的逐行 `// naming-ignore` 机制,并逐条写明理由——不收窄 SCAN_DIRS:\n治理脚本里同样会出现业务概念名,去掉 scripts/ 会让真的违规漏网。豁免要作者写明,\n不能按路径猜,与工作区一致性门禁的 `\u003c!-- 一致性门禁豁免 --\u003e` 同一口径。\n\n改动只在行尾追加注释,5 处含模板字符串的行已逐一核对反引号在同行闭合。\n三份治理模块的自有测试 311/311 通过,四个文件 node --check 通过。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:40:57-07:00"},{"Sha1":"7d14ff2472a4204046b7d6bbea1a4d84f408e7f3","Message":"chore(governance): 在 clean HEAD 上重跑静态门禁,并记下 naming 的 32 条真实违规\n\n迁移后本仓 37 份 reports/*.latest.json 无一绑定当前 HEAD,全部生成于脏树,其中\n15 份正文还带着 /Users/ailaoluo/ 的两代前绝对根——那是另一台机器。所以此前既不能\n说\"当前 HEAD 是绿的\",也不能说\"是红的\",它一直是未知数。\n\n本次在 clean HEAD (a0ebf77) 上重跑全部静态门禁:12 通过 / 8 失败,提交其中 15 份\n(provenance 全部 gitSha=a0ebf77 且 worktreeDirty=false)。\n\n**一条真实失败:check-naming 32 条违规。** 上一份报告(09-01)记的是 violations: 0。\n命中全部落在门禁脚本自己身上——scripts/lib/database-rls-history-governance.mjs 的\n`terminal`(RLS 终态)被业务词典判成应改为 device,check-api-migration-safety.mjs 的\n`business database` 判成应改为 merchant。业务词典的扫描面覆盖到了治理脚本,而那里的\n词是技术义不是业务义。这是扫描面扩大后出现的误报类失败,词典或扫描面需收敛。\n\n**刻意不提交 3 份**:dual-backend-behavior / health-dependency-failure /\noutbox-multi-instance 因缺 DATABASE_URL 写出 failed——那是跑不起来,不是判定失败,\n记进去会把环境缺失伪装成质量问题。\n\n**保留两份 OS 产品的失败报告**:os-product-layer 与 os-product-registration-verification\n这次的失败理由是当前的(前者卡 host-ui 报告、后者卡 target OS checkout 与 runtime\n验收证据),且不再含两代前的绝对根——比它们替换掉的旧报告更可用。\n\n按证据等级\"静态 \u003c 真实 DB \u003c 浏览器\",本次只提升到静态一级。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:35:28-07:00"}],"HeadCommit":{"Sha1":"3c9f6df78f540226554cb4ecc6115741fe478c41","Message":"chore(governance): 接真实 DB 重跑,13→15 通过,并暴露 outbox 多实例的可复现失败\n\n按本目录\"每轮新建空验收库\"的口径建独立库:\n juhai_ai_hr_system_parity_20260915(prisma migrate deploy 后为空库)\n REDIS_URL 用 /14 号逻辑库\n\n库名前缀不是随便起的——G15 守卫按 package.json 的 name 推导(juhai_ai_hr_system),\n首次用 juhai_hr_parity_* 被三条门禁正确拒绝:\"Database … does not belong to …\"。\n守卫工作正常,是库名起错了。\n\n接上实例后两条转绿:check-dual-backend-behavior、check-health-dependency-failure。\n\n**新暴露一条可复现失败:check-outbox-multi-instance**\n nestjs / fastify 双侧同样结果:dispatched=120, observed=0, subscriberStatus=ready\n连跑两次一致。门禁本身跑完了全程,不是\"缺环境变量跑不起来\"那一类。根因未定——\n可能是缺少未文档化的 relay / worker 配置(本仓 .env 里没有任何 REDIS/DATABASE 项),\n也可能是真实缺陷。不在此下结论,交仓 Owner;报告如实记录该结果。\n\n仍失败的另外 4 条:api-migration-safety 需 MIGRATION_TEST_ADMIN_URL;\nos-product-host-ui 需浏览器;os-product-layer 与 os-product-registration 分别级联于\nhost-ui 报告与 target OS checkout / runtime 验收证据。\n\n18 份报告 provenance 全部绑定 d970541 且 worktreeDirty=false;连接串中口令已按仓内\n既有口径脱敏为 app:***,仅余本机地址与库名。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:50:03-07:00"},"CompareURL":"luoanwu/juhai-ai-hr-system/compare/a0ebf7769727344892ab96c1240bd809b5791430...3c9f6df78f540226554cb4ecc6115741fe478c41","Len":4}...
|
1789458920
|
Edit
Delete
|
|
30100
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"86a7e52c6 {"Commits":[{"Sha1":"86a7e52c6b5843851881a91625bc944a51df2205","Message":"chore(governance): 刷新门禁运行与消费两份报告\n\n本会话多轮运行 run-foundation-gates 后的最新一次结果:阻断性 7/7 通过,仅记录 3\n(audit-platform-openings / check-workspace-consistency / check-domain-layer,\n均已在门禁消费登记里具名接入条件)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:54:26-07:00"},{"Sha1":"de0ebe04b4a27a0bba7f8981c635193a19d8e902","Message":"docs(framework): 框架 0.19.0 的变更请求受理记录落盘(另一会话的工作区改动)\n\n本提交的内容不是本会话所写,是框架侧会话留在工作区的 5 个文档改动,按\"全面提交\"\n一并落盘。内容自洽且已静置 35 分钟(最后修改 00:19,提交于 00:54):\n\n- 基础设施仓框架变更请求-2026-09-12.md:受理表由五项全\"待\"改为 FR-1 受理并落地\n (0.19.0)、FR-4 / FR-5 受理(实现在下一个提交)、FR-2 / FR-3 暂不受理并写明理由\n (FR-2 触及写链四同边界与 check:write-guard 规则形态,框架侧无法独立判绿;\n FR-3 的 Fact 信封 v1 是 additionalProperties: false,加字段不能自称向后兼容,\n 属契约裁决)\n- CLAUDE.md:状态行推进到 v0.19.0,补 0.17.0 / 0.18.0 两节\n- 开发计划.md:补 0.17.0(compose 身份与端口,F14)与 0.18.0(G20 运维平面)两段进展\n- README.md:补 compose 变更请求的受理结论与\"扩散未决\"纪律\n- 框架变更请求-compose身份与端口-2026-09-14.md:受理结论回填\n\n本会话未改动其中任何一个字,只做落盘。若框架侧会话对措辞或时机有异议,按本仓惯例\n以后续提交订正,不 rebase 已落盘内容。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:54:21-07:00"},{"Sha1":"3cffd5406c379159d0074622c550ce5d4a81b17a","Message":"docs(governance): 回灌台账 U-37 / U-38 —— 接真实 DB 一轮跑出的两条下层缺口\n\n本轮把四个领域仓的证据等级从\"静态\"往\"真实 DB\"推,基座(base-framework-postgres-1 /\nredis-1)已在运行,按本目录\"每轮新建空验收库\"的口径逐仓建独立库。结果:\n\nU-37 工单仓在文档所述基座上根本跑不起来。prisma migrate deploy 在\n20260827015000_ticket_ai_pgvector 失败(P3009)——基座镜像 postgres:16-alpine 的\npg_available_extensions 里没有 vector 扩展。知识云用 DOUBLE PRECISION[] 绕开了\n同一需求所以不受影响,工单需要真扩展。二选一:换镜像(影响所有共用该实例的项目)\n或改列形态(影响检索实现)。在此之前工单的证据等级封顶在\"静态\"。\n\nU-38 HR 的 check-outbox-multi-instance 接上真实 DB 后可复现失败:\ndispatched=120, observed=0, subscriberStatus=ready,双后端一致,连跑两次相同。\n门禁跑完了全程,不属\"缺环境变量跑不起来\"那一类。本仓 .env 没有任何 REDIS/DATABASE\n项,无法判断是缺少未文档化的 relay/worker 配置还是真实缺陷——不在治理层臆断,\n证据已如实落盘,根因归仓 Owner。\n\n顺带记下:G15 库名守卫工作正常。首次用 juhai_hr_parity_* 被三条门禁正确拒绝\n(\"Database … does not belong to juhai_ai_hr_system\"),前缀按 package.json 的 name\n推导,是库名起错了不是守卫误报。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:50:36-07:00"},{"Sha1":"b4c4c61f455cd46e6c13bb28beb6ac506fee936a","Message":"docs(governance): 回灌台账 U-36 —— 门禁在缺实例时把\"跑不起来\"写成\"0 例通过\"\n\n知识云 docs-truth 报 3 处文档漂移,根因不在文档:CLAUDE.md 记\nbackend-behavior-parity 为 28 例,而机器真源被写成 0。\ncheck-backend-behavior-parity.mjs:140 写 `raw?.metrics?.… ?? 0`——vitest 因缺\nDATABASE_URL / REDIS_URL 跑不起来时不产出报告,于是\"跑不起来\"被记成\"0 例通过\",\n再经 check-docs-truth.mjs:292 变成文档漂移。\n\ndocs-truth 自己已经察觉(第 3 条违规:\"动态数字负向探针只命中 7/9,门禁可能是\n假绿\"),但它只能报征状。\n\n**没有直接修**:最小改法(指标记 null + docs-truth 跳过比较)会让 :381 的负向探针\n失效,docs-truth 反而变成真的假绿。这是\"证据不可用\"如何穿过门禁链表达的设计问题,\n不是两行修补;治理层正在做同构的事(4d3efd5 拆开「报告没写结论」与「结论不合格」),\n本条等该口径定稿后按同一形态落到各仓。\n\n§3 第 9 条补一行:四个仓的需实例门禁共 8 条有同类风险;口径定稿前这些报告不应\n提交——本轮 HR 3 份、知识云 2 份即按此处理。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:41:51-07:00"},{"Sha1":"812ed430b9066c1fedebd7dd3aa5b0138f2ed644","Message":"fix(governance): D8 的构造性缺陷 —— 提交证据这个动作本身会让证据失效\n\n实测发现:门禁在 clean HEAD 上生成报告,报告记下当时的 gitSha;把报告提交,HEAD\n随即前进到新提交,于是报告永远指向父提交。按 D8 原本\"必须绑定当前 HEAD\"的字面规则,\n**落盘那一刻证据就自动作废**——这条判据不可能被满足。四个领域仓刚提交完新鲜证据,\nD8 依旧报 4 条,就是这个缺陷的现场。\n\n正确口径是看被验收的内容有没有变:从证据所绑的提交走到 HEAD,若沿途每个提交只动\nreports/,则源码与配置一字未改,证据仍然当前。这与 report-provenance.mjs 把\nreports/*.latest.json 排除在 worktreeDirty 之外是同一条道理,一个作用于工作树、\n一个作用于提交历史。\n\n不放宽到\"内容相似\":沿途只要有一个提交碰了 reports/ 以外的东西,证据即失效;\n查不出文件清单的提交(如合并提交)一律判失效。\n\n修正后 D8 由 4 条降为 **0 条**——四个领域仓的证据第一次全部当前。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:36:22-07:00"}],"HeadCommit":{"Sha1":"86a7e52c6b5843851881a91625bc944a51df2205","Message":"chore(governance): 刷新门禁运行与消费两份报告\n\n本会话多轮运行 run-foundation-gates 后的最新一次结果:阻断性 7/7 通过,仅记录 3\n(audit-platform-openings / check-workspace-consistency / check-domain-layer,\n均已在门禁消费登记里具名接入条件)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T00:54:26-07:00"},"CompareURL":"luoanwu/platform-governance/compare/cdb7f45657484b0ee996962444a060ca1f33c305...86a7e52c6b5843851881a91625bc944a51df2205","Len":42}...
|
1789458887
|
Edit
Delete
|
|
30064
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"cdb7f4565 {"Commits":[{"Sha1":"cdb7f45657484b0ee996962444a060ca1f33c305","Message":"fix(governance): 两条迁移残留门禁归零——评审包路径基准与平台数口径\n\n两个脚本都不在任何测试覆盖里,所以迁移把它们打坏后一直没人发现。\n\n1) check-new-platform-decision-review:评审包校验完全空转\n\n局部变量名叫 workspaceRoot,实际指的是 平台治理/基础 目录。evidenceRefs 与\nDecisionCatalog 的 source 在 98ec9e9 的数据改写中已变为**工作区相对**路径\n(平台治理/基础/… 与 企业控制面/…),脚本却仍在剥 `^基础/` 前缀再按 基础/ 解析,\n于是拼出 平台治理/基础/平台治理/基础/…,首条即抛\nDECISION_REVIEW_PACKET_INVALID: missing evidence,退出码恒为 1。\n\n实测这不是\"少数几条失效\":按工作区根解析 11/11 命中,按旧的 基础/ 根解析 0/11\n(7 条 evidenceRefs + 4 条 ADR source)——整条证据链检查一条都没跑到。\n\n改为引入 lib/workspace.mjs 的 workspaceRoot(),把两处按工作区根解析;\n局部变量改名 foundationRoot,评审包自身文件仍相对它读取。去掉前缀剥离:\n数据若再退回旧形态,应当直接红,而不是被一个正则悄悄吞掉。\n\n与 simulate-chg-005 的 `let mirror;` 是同一类——回灌台账 C-14\n\"一个旧目录拆成多个新目录时,机械前缀替换不成立\"的最后一个未收口实例。\n\n2) audit-ci-gates:与 派生仓状态.json 并存两套平台数口径\n\n冻结核心里 DEFAULT_EXPECTED_PLATFORM_COUNT = 19 成文于企业 IdP 并入\nenterprise-platform 之前。并入后 派生仓状态.json 把它登记为 missing,现场只剩\nactive 5 + archived 13 = 18,本审计恒报 `目标平台数量应为 19,实际 18`;而同一份\n真源驱动的 audit-platform-openings 这项却通过——一个工作区两套口径。\n\n冻结仓 archived-20260910 不可改,但 runCiGateAudit 只是 auditPlatformSet +\nformatAuditSummary 的便捷封装,且 auditPlatformSet 本就接受 expectedPlatformCount,\n只是便捷入口没透传。兼容入口在治理仓、可自由改,于是改为直接组合这两个导出,\n期望值从 派生仓状态.json 现算(只数 active + archived,missing 是\"没有派生仓\"的\n登记,计入会把口径推回 19)。\n\n验证:\n- check-new-platform-decision-review → 退出码 0,\n \"4 independent pending decisions,17 pending signoffs,0 runtime/service authorizations\"\n- audit-ci-gates → 退出码 0,18/18 通过,expectedPlatformCount=18,globalProblems 空,\n --json 输出形状不变\n- 冻结仓 统一交付平台/base-framework 工作树 git status 为空,一个字节未动;\n check-archived-derived-repos 仍 13/13\n- audit-foundation 阻塞项 7 → 4(另三项由并行进行的 CHG-001 修订 8 收口)\n\n遗留:这两个脚本仍无测试覆盖,正是它们能长期静默失效的原因;\n建议后续补两例(路径基准、口径来源)到 平台治理/基础/tests/。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T23:02:55-07:00"},{"Sha1":"52ac2e9762313f122e49915c094f903634b34932","Message":"feat(governance): 修订 8 四项审批落库并排定窗口,合并闸门重新开启\n\n承接 a64e30a(改指活跃真源)。修订 7 的审批因目标真源有问题被收回(615c017),\n本次针对修订 8 重走:四个角色均由 luoanwu 审批 APPROVED,窗口排在\n2026-09-15T05:59:53Z,仍是先排窗口后录回执以避开 record 脚本注释警告的顺序陷阱。\n\n与修订 7 的关键差别:本包钉的是 DEC-010 A 案裁定的物理真源\n企业控制面/enterprise-platform/contracts,镜像验证 274/274、官方 check 在\n合并态转绿,合并后统一审计的 CANDIDATES_NOT_REGISTERED 可真正消除——\n而修订 7 合并进的是待移除的冻结副本,三项 Catalog 阻断一个都不会掉。\n\n结果:mergeGate.eligible=true、就绪度 READY、blockingReasons 清空;\ncatalogMutationAuthorized=true,runtime / serviceCreation / deployment 仍 false。\n包指纹 1fdc2e16…efdd87 全程未变(审批记录不在冻结清单内)。\n\n回执四份置于 approvals/,各引变更请求、DEC-033—036 评审包、发布运行手册三份证据。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T23:00:25-07:00"},{"Sha1":"a3e9052a1a31cac006fe47f3b03f913c849a39b8","Message":"fix(governance): 合并演练测试的真源与被测脚本同源\n\n测试把 formalRoot 硬编码为 resolve(foundationRoot,\"..\",\"platform-contracts\"),\n而 a64e30a 已把 simulate-new-platform-catalog-merge.mjs 改走 activeContractsRoot()。\n两边分叉后 5 条用例全红:被测脚本拒绝的是活跃真源,测试递进去的却是冻结副本,\n\"refuses formal targets\" 一类断言自然落空。\n\n改为与脚本同源解析(workspaceRoot + activeContractsRoot),目标真源再变时\n只改 workspace.json 一处,测试不必跟着改。5 条用例恢复通过。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:54:41-07:00"},{"Sha1":"a64e30a7108cf09938763809eac75534defc6ba3","Message":"feat(governance): CHG-001 重基线为修订 8,目标真源改指活跃契约\n\n承接 615c017(收回四项审批)与核对记录 3689711:CHG-001 整包钉在\n平台治理/platform-contracts(冻结待移除),而 DEC-010 A 案裁定的物理真源是\n企业控制面/enterprise-platform/contracts。合并到冻结副本不会消除统一审计的\nCANDIDATES_NOT_REGISTERED,且修订 7 补丁对活跃真源 --fuzz=0 时\ntest/governance-linter.test.mjs 4 个 hunk 失败 1 个。本次完成改指。\n\n- 新增 activeContractsRoot()(读 workspace.json 的 paths.activeContracts),\n check-new-platform-catalog-change-readiness / verify-new-platform-change /\n simulate-new-platform-catalog-merge 三者改走它。simulate 尤其必要:\n 它的 formalRoot 正是「禁止写入正式目录」的保护对象,不改会放行写入活跃真源\n- 完整补丁按活跃真源重新渲染,fileCount 仍 4(scripts/governance-linter.mjs\n 依旧无差异),被拒的那个 hunk 按活跃真源的上下文重新落位\n\n顺带修掉三处只在新环境下暴露的缺陷:\n1. 新增测试的 platformLayerEntries 与 linter 一样用 Dirent.isDirectory(),\n 在镜像里把 19 个平台目录误判为普通文件,三条断言集体反向(linter 侧见\n enterprise-platform 2d7265c)\n2. 「真实的未登记平台目录必须仍被报出」依赖环境里恰好存在未登记目录,\n 而本变更登记了全部 4 个候选——合并态下该断言必然落空。改为确定性构造:\n 从克隆注册表摘掉一个已登记平台,断言它被报出,原意(豁免不得消音真实治理债)不变\n3. verify 的回滚基线断言把 check 的汇总行计入错误数,在活跃真源上成了 5 !== 4。\n 改为只计 [PLATFORM_PROJECT_UNREGISTERED],另行断言不得出现其他类型错误;\n 报告里的 formal_catalog_root 由写死的 'platform-contracts' 改为动态相对路径\n\n验证:镜像 274/274、官方 check 在合并态转绿、回滚逐字节、正式目录未动;\n就绪度 READY→BLOCKED 而非 INVALID,即技术侧就绪、只差四方审批与变更窗口。\n修订 7 指纹 6e2e69d6…ffa97f 作废,修订 8 指纹 1fdc2e16…efdd87。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:53:46-07:00"}],"HeadCommit":{"Sha1":"cdb7f45657484b0ee996962444a060ca1f33c305","Message":"fix(governance): 两条迁移残留门禁归零——评审包路径基准与平台数口径\n\n两个脚本都不在任何测试覆盖里,所以迁移把它们打坏后一直没人发现。\n\n1) check-new-platform-decision-review:评审包校验完全空转\n\n局部变量名叫 workspaceRoot,实际指的是 平台治理/基础 目录。evidenceRefs 与\nDecisionCatalog 的 source 在 98ec9e9 的数据改写中已变为**工作区相对**路径\n(平台治理/基础/… 与 企业控制面/…),脚本却仍在剥 `^基础/` 前缀再按 基础/ 解析,\n于是拼出 平台治理/基础/平台治理/基础/…,首条即抛\nDECISION_REVIEW_PACKET_INVALID: missing evidence,退出码恒为 1。\n\n实测这不是\"少数几条失效\":按工作区根解析 11/11 命中,按旧的 基础/ 根解析 0/11\n(7 条 evidenceRefs + 4 条 ADR source)——整条证据链检查一条都没跑到。\n\n改为引入 lib/workspace.mjs 的 workspaceRoot(),把两处按工作区根解析;\n局部变量改名 foundationRoot,评审包自身文件仍相对它读取。去掉前缀剥离:\n数据若再退回旧形态,应当直接红,而不是被一个正则悄悄吞掉。\n\n与 simulate-chg-005 的 `let mirror;` 是同一类——回灌台账 C-14\n\"一个旧目录拆成多个新目录时,机械前缀替换不成立\"的最后一个未收口实例。\n\n2) audit-ci-gates:与 派生仓状态.json 并存两套平台数口径\n\n冻结核心里 DEFAULT_EXPECTED_PLATFORM_COUNT = 19 成文于企业 IdP 并入\nenterprise-platform 之前。并入后 派生仓状态.json 把它登记为 missing,现场只剩\nactive 5 + archived 13 = 18,本审计恒报 `目标平台数量应为 19,实际 18`;而同一份\n真源驱动的 audit-platform-openings 这项却通过——一个工作区两套口径。\n\n冻结仓 archived-20260910 不可改,但 runCiGateAudit 只是 auditPlatformSet +\nformatAuditSummary 的便捷封装,且 auditPlatformSet 本就接受 expectedPlatformCount,\n只是便捷入口没透传。兼容入口在治理仓、可自由改,于是改为直接组合这两个导出,\n期望值从 派生仓状态.json 现算(只数 active + archived,missing 是\"没有派生仓\"的\n登记,计入会把口径推回 19)。\n\n验证:\n- check-new-platform-decision-review → 退出码 0,\n \"4 independent pending decisions,17 pending signoffs,0 runtime/service authorizations\"\n- audit-ci-gates → 退出码 0,18/18 通过,expectedPlatformCount=18,globalProblems 空,\n --json 输出形状不变\n- 冻结仓 统一交付平台/base-framework 工作树 git status 为空,一个字节未动;\n check-archived-derived-repos 仍 13/13\n- audit-foundation 阻塞项 7 → 4(另三项由并行进行的 CHG-001 修订 8 收口)\n\n遗留:这两个脚本仍无测试覆盖,正是它们能长期静默失效的原因;\n建议后续补两例(路径基准、口径来源)到 平台治理/基础/tests/。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T23:02:55-07:00"},"CompareURL":"luoanwu/platform-governance/compare/4b9218ca6b938f802870c9b048b2fba70245c666...cdb7f45657484b0ee996962444a060ca1f33c305","Len":4}...
|
1789452186
|
Edit
Delete
|
|
30056
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"4b9218ca6 {"Commits":[{"Sha1":"4b9218ca6b938f802870c9b048b2fba70245c666","Message":"docs(governance): §8 改写为 CHG-001 收口后的实际状态——审批已收回、改指活跃真源\n\n当晚 CHG-001 状态在 5 分钟内翻转两次,本文前两版各记了其中一个中间态:\n- a140998(22:42:31)记 PENDING\n- bd63d88 订正为 READY(据 c571477,22:42:10)\n- 615c017(22:46:57)目录负责人收回全部四项审批、关闭合并闸门\n\n现按收口状态改写,中间态不再保留为结论:四项 PENDING、\nmergeGate.eligible=false、catalogMutationAuthorized=false,回执连同\narchive-manifest 归档至 reports/catalog-package-archive/6e2e69d6…/\napprovals-withdrawn/ 并标明「不得转移到修订 8」。\n\n同时把「两份 catalog 的结构性矛盾」一条从「需裁决」改为「已裁决」:\nCHG-001 整包钉在 平台治理/platform-contracts,而 DEC-010 A 案明写独立\nGit-first 真源由基础设施仓 contracts/ 承担。核对记录 3689711 指出按现状\n合并会把四个候选登记进待移除副本、三项 Catalog 阻断不会消除,且修订 7\n补丁对活跃真源 --fuzz=0 --dry-run 有 1 个 hunk 失败。决定改指活跃真源、\n重基线为修订 8。该矛盾由并发会话独立发现并当场裁决,非本文促成,两条\n路径结论一致,作交叉印证记录。\n\n并发说明段补一条教训,与 §6、回灌台账 C-17 同源:治理文档里任何「现状」\n行都有半衰期,这次是 21 秒;引用状态须写明观测时刻,据状态做决定须当场\n实跑,不得引用他文。\n\n门禁:L4 链接失效 0。L7 当前 2 条不符(simulate-new-platform-catalog-merge.mjs\n与完整变更.patch),成因是并发会话在途重算修订 8 摘要,615c017 已预告,\n不属本次变更。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:49:16-07:00"},{"Sha1":"a06705a0015517aa5968c14d12bbfe631918868b","Message":"fix(governance): 白名单补上反向兜底——机密类文件的排除规则\n\n迁移方案 §8.4 教训 2 写着\"既查该纳入的是否纳入,也查不该纳入的是否排除,\n凭证泄露正源于只做了前一半\"。L1—L9 把九类迁移破坏都固化成了机器检查,\n唯独这一类没有落地——门禁代码里 gitignore / secrets / .env 出现次数均为 0,\n全工作区也无任何机密扫描(无脚本、无 git hook、无 CI)。\n\n用 git check-ignore 实测白名单反向,破绽恰好集中在 平台治理/ 这一层本身\n(也就是 09-14 真正泄过密的那一层):doc/、基础/、基础/scripts/、基础/reports/、\n基础设施文档/、platform-contracts/ 六个放行区,9 类机密文件名里有 8 类会被纳入。\n其它层安全不是因为有防护,而是白名单本来就窄(!/数字员工OS/*.md 只放行 .md)。\n\n根因是兜底段只有两条规则,而 *.env 只匹配以 .env 结尾的名字——\n.env.production / .env.local 都不匹配,.pem / .p12 / id_rsa / secrets.* 则根本没规则。\n\n本次补:.env.*(配 .env.example / .env.*.example 例外)、私钥与证书五类、\nid_rsa* / id_ed25519*、.netrc、secrets.* 与 credentials.* 各三种扩展名。\n\n.npmrc 有意不列:全工作区 8 处合法跟踪(enterprise-platform 仓根与 runtime/、\n报价仓 sites/、嗨赞造意 output/),它是 registry 配置不是机密。\n\n验证:\n- git ls-files | git check-ignore --stdin → 空,无任何已跟踪文件被新规则命中,\n 改动纯预防,不需要先清历史\n- 缺口测绘重跑:六个放行区由\"8 类可纳入\"降为\"仅 .npmrc\"\n- 逐条抽查:doc/.env.production、reports/dump.pem、基础/.env.local、\n decisions/id_rsa、platform-contracts/credentials.json、scripts/.netrc 全部已排除;\n .env.example 仍正常放行\n\n加规则前先扫过现状:密钥类文件名被跟踪 0 个(30+ 仓逐个 git ls-files)、\n硬编码密钥(sk- / AKIA / ghp_ / BEGIN PRIVATE KEY / xox*)0 处、\n未跟踪但不被忽略的机密文件 0 个——开局全绿。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:48:34-07:00"}],"HeadCommit":{"Sha1":"4b9218ca6b938f802870c9b048b2fba70245c666","Message":"docs(governance): §8 改写为 CHG-001 收口后的实际状态——审批已收回、改指活跃真源\n\n当晚 CHG-001 状态在 5 分钟内翻转两次,本文前两版各记了其中一个中间态:\n- a140998(22:42:31)记 PENDING\n- bd63d88 订正为 READY(据 c571477,22:42:10)\n- 615c017(22:46:57)目录负责人收回全部四项审批、关闭合并闸门\n\n现按收口状态改写,中间态不再保留为结论:四项 PENDING、\nmergeGate.eligible=false、catalogMutationAuthorized=false,回执连同\narchive-manifest 归档至 reports/catalog-package-archive/6e2e69d6…/\napprovals-withdrawn/ 并标明「不得转移到修订 8」。\n\n同时把「两份 catalog 的结构性矛盾」一条从「需裁决」改为「已裁决」:\nCHG-001 整包钉在 平台治理/platform-contracts,而 DEC-010 A 案明写独立\nGit-first 真源由基础设施仓 contracts/ 承担。核对记录 3689711 指出按现状\n合并会把四个候选登记进待移除副本、三项 Catalog 阻断不会消除,且修订 7\n补丁对活跃真源 --fuzz=0 --dry-run 有 1 个 hunk 失败。决定改指活跃真源、\n重基线为修订 8。该矛盾由并发会话独立发现并当场裁决,非本文促成,两条\n路径结论一致,作交叉印证记录。\n\n并发说明段补一条教训,与 §6、回灌台账 C-17 同源:治理文档里任何「现状」\n行都有半衰期,这次是 21 秒;引用状态须写明观测时刻,据状态做决定须当场\n实跑,不得引用他文。\n\n门禁:L4 链接失效 0。L7 当前 2 条不符(simulate-new-platform-catalog-merge.mjs\n与完整变更.patch),成因是并发会话在途重算修订 8 摘要,615c017 已预告,\n不属本次变更。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:49:16-07:00"},"CompareURL":"luoanwu/platform-governance/compare/615c017a32da032ecaeb00215d8b8b5418d9b122...4b9218ca6b938f802870c9b048b2fba70245c666","Len":2}...
|
1789451359
|
Edit
Delete
|
|
30055
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"c433d57b4 {"Commits":[{"Sha1":"c433d57b4aae2249bd19a085d1c520bf6baedf55","Message":"docs: 文档链接改为仓内相对路径,修复迁移后失效\n\n2026-09-14 应用群迁入新根 企业AI应用开发群/,本仓路径由\n企业产品/企业/企业应用/基础/AI数字员工/ 变为 数字员工OS/。\n\n- development-blueprint-2026-09-04.md:33 处链接写的是旧根绝对路径\n (/Users/hillao/AI产品/企业产品/企业/基础/AI数字员工/digital-employee-os/…),\n 迁移后全部失效。改为仓内相对路径 ../../,行号锚点保留;\n 逐条校验替换后的目标文件均存在。相对路径也让链接不再受未来目录调整影响\n- employment-projection-blueprint.md:上位文档引用 基础/AI数字员工/开发计划.md\n 改为 数字员工OS/开发计划.md\n\ndocs/operations/local-restart-2026-09-13.md 里的旧路径是当时的运维记述,\n属历史事实,保留未改。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:20:56-07:00"}],"HeadCommit":{"Sha1":"c433d57b4aae2249bd19a085d1c520bf6baedf55","Message":"docs: 文档链接改为仓内相对路径,修复迁移后失效\n\n2026-09-14 应用群迁入新根 企业AI应用开发群/,本仓路径由\n企业产品/企业/企业应用/基础/AI数字员工/ 变为 数字员工OS/。\n\n- development-blueprint-2026-09-04.md:33 处链接写的是旧根绝对路径\n (/Users/hillao/AI产品/企业产品/企业/基础/AI数字员工/digital-employee-os/…),\n 迁移后全部失效。改为仓内相对路径 ../../,行号锚点保留;\n 逐条校验替换后的目标文件均存在。相对路径也让链接不再受未来目录调整影响\n- employment-projection-blueprint.md:上位文档引用 基础/AI数字员工/开发计划.md\n 改为 数字员工OS/开发计划.md\n\ndocs/operations/local-restart-2026-09-13.md 里的旧路径是当时的运维记述,\n属历史事实,保留未改。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:20:56-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/23d1b7ac7da6d8779bf29f8fabd126d9f7a15493...c433d57b4aae2249bd19a085d1c520bf6baedf55","Len":1}...
|
1789451260
|
Edit
Delete
|
|
30054
|
5
|
5
|
5
|
54
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"9690ba986 {"Commits":[{"Sha1":"9690ba98673547cb338309cd66f41ff6dbcaf61b","Message":"docs: 同步同步计划文档的新路径\n\n2026-09-14 应用群迁入新根后,治理文档移至 平台治理/基础/。\nCOMPATIBILITY.md 的 0.1.0-pre 行引用 `基础/框架新版本同步计划.md`,\n改为 `平台治理/基础/框架新版本同步计划.md`(目标已核实存在)。\n\n改动本身是迁移当天路径替换的一部分,当时未随其他仓一并入库,\n导致本仓工作树长期 dirty,基础审计据此把框架资产判为 worktreeClean=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-14T22:24:34-07:00"}],"HeadCommit":{"Sha1":"9690ba98673547cb338309cd66f41ff6dbcaf61b","Message":"docs: 同步同步计划文档的新路径\n\n2026-09-14 应用群迁入新根后,治理文档移至 平台治理/基础/。\nCOMPATIBILITY.md 的 0.1.0-pre 行引用 `基础/框架新版本同步计划.md`,\n改为 `平台治理/基础/框架新版本同步计划.md`(目标已核实存在)。\n\n改动本身是迁移当天路径替换的一部分,当时未随其他仓一并入库,\n导致本仓工作树长期 dirty,基础审计据此把框架资产判为 worktreeClean=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-14T22:24:34-07:00"},"CompareURL":"luoanwu/base-framework/compare/023d78883392f389eef8363b752fcd2c86813fc1...9690ba98673547cb338309cd66f41ff6dbcaf61b","Len":1}...
|
1789451258
|
Edit
Delete
|
|
30053
|
5
|
5
|
5
|
114
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"14a5b8d33 {"Commits":[{"Sha1":"14a5b8d33d1d95137de02e921b772c5db121e215","Message":"chore: 移除被跟踪的 .DS_Store 并加 .gitignore 拦截\n\n仓内 .DS_Store 与 docs/.DS_Store 被 git 跟踪,且没有 .gitignore,\n删掉后 Finder 一访问就会重新进入索引。补一份 .gitignore 收口。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:24:25-07:00"}],"HeadCommit":{"Sha1":"14a5b8d33d1d95137de02e921b772c5db121e215","Message":"chore: 移除被跟踪的 .DS_Store 并加 .gitignore 拦截\n\n仓内 .DS_Store 与 docs/.DS_Store 被 git 跟踪,且没有 .gitignore,\n删掉后 Finder 一访问就会重新进入索引。补一份 .gitignore 收口。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:24:25-07:00"},"CompareURL":"luoanwu/spatiotemporal-fact-model/compare/b5241c619a6252f86eead6f150eb025765793a1a...14a5b8d33d1d95137de02e921b772c5db121e215","Len":1}...
|
1789451255
|
Edit
Delete
|
|
30052
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"b54b34efc {"Commits":[{"Sha1":"b54b34efc535e49428e3f3d8fbe3b0e6fe204503","Message":"fix(governance): 补登记 EmploymentTransferred 三个参与方的 DEC 前置\n\naudit-foundation 的 FACT_DEPENDENCY_SUMMARY_GAPS:EmploymentTransferred 的\nblocked_by(DEC-010/012/032)未体现在三个参与方的项目摘要里——\nenterprise-fact-backbone 缺 DEC-032、digital-employee-os 为空、\npermission-platform 缺 010/012/032。\n\nblockers 记录的是 Fact 前置依赖(可追溯性),不等于「当前被阻塞」:审计用\n「未批准」单独一列表达阻塞,该列三行均为「无」。既有数据本就登记了已批准的\nDEC-010/012,本次与之一致。\n\n改的是活契约(正式真源——audit-foundation.mjs 注释明写「platform-contracts\n是冻结待移除的副本,审计不能拿它当依据」)。平台治理/platform-contracts/ 的\n冻结副本未触碰:CHG-001 修订 7 的 14 份冻结物复核 14/14 匹配,\npackageValid=true、formalCatalogMutated=false。\n\n审计阻塞项 7 → 6;活契约 test 167/167、治理 test 188/188、L7 冻结物 0 条不符。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:42:20-07:00"},{"Sha1":"edb5218c3bd33f8001d63ff192323ea642d86547","Message":"docs: 修复 2026-09-14 迁移后仓内失效的 48 条相对链接\n\n平台目录由 基础/ 移入 企业控制面/、基础设施文档移入 平台治理/基础设施文档/ 后,\n本仓 394 条相对链接中 48 条失效,全部指向旧的兄弟目录布局:\n\n- ../开发计划.md、../docs/基础设施开发设计方案.md、../CLAUDE.md(6+5+1 条)\n → 平台治理/基础设施文档/ 下对应文件\n- ../../../基础/\u003c平台\u003e/开发计划.md → 企业控制面/\u003c平台\u003e/开发计划.md\n- ../../../上层对接经验回灌台账.md → 平台治理/基础/上层对接经验回灌台账.md\n- ../../../doc/decisions/… → 平台治理/doc/decisions/…\n\n解析方式:以工作区根建全文件后缀索引,只在后缀唯一命中时改写;\n「开发计划.md」在全树有 25 处、后缀不唯一,按本仓语义显式定向到基础设施层。\n\n另两点:\n- 路径按本仓既有风格写明文中文,不做百分号编码;含空格的目录名\n (租户组织与 Scope 平台、通知与 Webhook 中心、AI 治理平台、\n 企业 IM 与智能会话平台)只把空格编码为 %20——目标里的字面空格会被\n Markdown 当作 title 起始而截断链接。\n- docs/项目完整能力表.md 原有 4 条全编码链接随之改为同一风格,目标未变。\n\n校验:本仓 394 条相对链接失效 0(校验含空格目标,此前的校验正则会漏掉它们)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:17:19-07:00"}],"HeadCommit":{"Sha1":"b54b34efc535e49428e3f3d8fbe3b0e6fe204503","Message":"fix(governance): 补登记 EmploymentTransferred 三个参与方的 DEC 前置\n\naudit-foundation 的 FACT_DEPENDENCY_SUMMARY_GAPS:EmploymentTransferred 的\nblocked_by(DEC-010/012/032)未体现在三个参与方的项目摘要里——\nenterprise-fact-backbone 缺 DEC-032、digital-employee-os 为空、\npermission-platform 缺 010/012/032。\n\nblockers 记录的是 Fact 前置依赖(可追溯性),不等于「当前被阻塞」:审计用\n「未批准」单独一列表达阻塞,该列三行均为「无」。既有数据本就登记了已批准的\nDEC-010/012,本次与之一致。\n\n改的是活契约(正式真源——audit-foundation.mjs 注释明写「platform-contracts\n是冻结待移除的副本,审计不能拿它当依据」)。平台治理/platform-contracts/ 的\n冻结副本未触碰:CHG-001 修订 7 的 14 份冻结物复核 14/14 匹配,\npackageValid=true、formalCatalogMutated=false。\n\n审计阻塞项 7 → 6;活契约 test 167/167、治理 test 188/188、L7 冻结物 0 条不符。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:42:20-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/30565bfa7709e7905e2050f43b8a5d6595158069...b54b34efc535e49428e3f3d8fbe3b0e6fe204503","Len":2}...
|
1789451252
|
Edit
Delete
|
|
30051
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"615c017a3 {"Commits":[{"Sha1":"615c017a32da032ecaeb00215d8b8b5418d9b122","Message":"fix(governance): 收回 CHG-001 四项审批并关闭合并闸门,回执按 SOP 归档\n\n修订 7 的四项 APPROVED(2026-09-15T05:40:40Z)与变更窗口(05:40:30Z)建立在\n一个目标真源有问题的包上:CHG-001 整包钉在 平台治理/platform-contracts,而\nDEC-010 已批准的 A 案明写「独立 Git-first 真源由基础设施仓的 contracts/\n工作区承担」,平台治理/README.md 也把前者定性为「冻结待移除,阶段 2 物理移除」。\n\n按现状合并的后果(核对记录 3689711):四个候选会登记进一个待移除的副本,\n而 audit-foundation 读 paths.activeContracts,三项 Catalog 阻断\n(CANDIDATES_NOT_REGISTERED / FORMAL_CATALOG_CHECK_FAILED /\nCANDIDATE_CATALOG_GATE_BLOCKED)不会消除;修订 7 补丁对活跃真源\npatch --fuzz=0 --dry-run 时 test/governance-linter.test.mjs 4 个 hunk 失败 1 个。\n\n目录负责人决定改指活跃真源、重基线为修订 8。按审批录入 SOP §5「包指纹或\n冻结文件漂移 → 全部旧回执失效,重新冻结包并重新审批」,本次先收口人的决定:\n\n- 四份回执连同 archive-manifest 归档到\n reports/catalog-package-archive/6e2e69d6…/approvals-withdrawn/,\n 记明失效原因与「不得转移到修订 8」,approvals/ 清空\n- 审批记录回到审批前形态:四项 PENDING、approver/decidedAt/evidenceRef/\n receiptSha256 置空、changeWindow.scheduledAt 置空(owner 与 rollbackOwner\n 按门禁要求保留 Catalog Owner)、mergeGate.eligible=false、\n authorizations.catalogMutationAuthorized 由 true 回到 false\n- revisionNote 追加【2026-09-14 收回】段,写明依据与修订 8 的前置\n\n包内容未动:revision 仍为 7,指纹 6e2e69d6…a84ffa97f 不变。修订 8 的重基线\n须等活跃真源 contracts/ 工作树 clean(当前有 src/domain/ 九个域包等在途实现),\n否则冻结摘要会钉住半成品。\n\n验证:tests/new-platform-approval-recording 7/7 恢复(此前 4 例因审批落库而\n红——这些用例把正式审批记录当夹具读)。tests/new-platform-catalog-readiness\n仍有 6 例红,成因是并行会话在途把 simulate-new-platform-catalog-merge.mjs\n改指 activeContractsRoot 而修订 8 摘要尚未重算,不属本次变更。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:46:57-07:00"},{"Sha1":"8832e2257d0c10cbf5cec5516604e46f1ee2e922","Message":"docs(governance): 提交 CHG-001 目标真源裁决请求,并登记进待裁决索引\n\n四份回执已签、就绪门禁 READY,但合并目标钉在冻结副本 平台治理/platform-contracts/,\n而 DEC-010 批准的真源是 企业控制面/enterprise-platform/contracts/。裁决请求列出\n三个方案与各自代价,推荐 A(改指活跃真源、重基线修订 8),并说明为什么必须现在定:\n\n包指纹覆盖 formalBaselineDigests,改指即换指纹,四份回执随之全部失效;现在定最多\n作废 4 份,等 CHG-002—005 也按冻结副本验证完再定,作废的是整条链。\n\n支撑推荐的实测:仅活跃真源独有 26 个文件、仅冻结副本独有 0 个(冻结副本是内容上的\n真子集,测试 3 vs 17);catalogs 五份里只有 platform-projects.json 不同,差异正是活跃\n真源已补、冻结副本仍缺的 7 条 Fact 前置;完整补丁对活跃真源 dry-run 只有\ntest/governance-linter.test.mjs 的 1 个 hunk 需重渲染,其余三份干净可落。\n\n另附两个连带问题:冻结副本的去留,以及就绪门禁按 platformContracts 还是\nactiveContracts 读取。本文不自行选定,裁决写入 §6 后方可执行。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:45:21-07:00"},{"Sha1":"bd63d88dc431e4fd106e5ba45404114c460bd264","Message":"docs(governance): 订正核对文档中 CHG-001 的状态——并发提交已使其转 READY\n\n上一条提交(a140998,22:42:31)的 §8 写于 c571477(22:42:10)之前,相隔\n21 秒,因此把 CHG-001 记成「四方审批 PENDING + 变更窗口未排」。实跑现状为\nREADY:pending 0、blockingReasons 空、packageValid=true。\n\n订正三处:§8 对照表 CHG-001 行、check.mjs 行、以及「未做」清单中 4 条\nPLATFORM_PROJECT_UNREGISTERED 的归因(改为待 Catalog Owner 在已排定窗口内\n执行合并;合并前 check.mjs 仍 exit=1 属预期)。\n\n并在节末加并发说明:本文核验跑在 22:30—22:42 之间,期间另有会话提交;\n3689711(22:41:49)独立记录了同一处结构性矛盾——CHG-001 钉在已被 DEC-010\n否定的目标真源上,与本文结论一致。\n\n这正是本文 §6 与回灌台账 C-17 所指的同类错误:陈述与机器基线脱节。区别是\n这次间隔 21 秒而非四天。\n\nL4 链接失效 0、L7 冻结物 0 条不符。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:45:13-07:00"},{"Sha1":"a140998ef2b0be91dcd2a416547b5f2ff9e4beaf","Message":"docs(governance): 架构图评审核对——27 项「缺失」24 项已有归属,真缺口 3 条\n\n新增 平台治理/架构图分析与仓库现状核对-2026-09-14.md:对一份纯图面架构评审\n意见逐条核对仓库现状。结论是该意见方向对、归因错——它判断「实施就绪度低」\n成立,但归因为「规范没定义清楚」;实际规范层相当完整(32 条 DEC 全部已批、\n四类带负向测试的机器契约),缺的是运行时(活 Catalog 21 条平台条目\nimplemented_e2 为 0)。其建议的「六条架构铁律」六条全部已存在于产品纲领且\n措辞更严;建议的试点链与 §11.2 重复。真缺口 3 条:注入防护规范、评测门禁\n实现(均卡 Q02 收口)、Agent Memory 保留与删除语义(待 OS Owner 认领)。\n\n误判源头是评审读了 平台治理/platform-contracts/README.md——它自述为真源却\n停在 2026-09-10(「5 approved / 27 pending」「DEC-010/012 尚未裁决」),而\n机器基线已是 32 approved / 0 pending。据此加两处时效提示:\n\n- platform-contracts/README.md 顶部加冻结待移除副本警示,指向 activeContracts\n- 产品纲领 §4 带日期快照加提示,并指回 决策批次-2026-09-12.md\n\n两处均不改写正文,遵回灌台账 §4 维护规则。README 不在 CHG-001 任何冻结摘要\n内——packageFingerprintForDocument 只哈希审批文档声明的 changeId + 三组摘要\n列表 + expectedFormalBefore/After,不扫描目录。\n\n回灌台账追加 C-17 / C-18。C-18 纠正 §1 第 1 条「CHG-001 包指纹以该目录为准,\n改动会触发就绪度重基线」的不精确表述:冻结面是 14 份具名文件,不是整个目录;\n动手前实算比对,不要按目录名推断。\n\n本文同时纠正两处过期结论:企业应用群挖掘分析-2026-09-14-2142.md(21:45)的\n第 3、4 条已被其后提交处理(CHG-001 22:02 重基线为修订 7、治理测试转绿);\n本文初稿据冻结副本把 causation_id 误记为必填,实为可选(ENVELOPE_OPTIONAL_FIELDS),\n因果链判定由 A 降为 A/C。\n\n一致性门禁 L1—L8 仍 0(本次新增链接已纳入扫描,1530 条);L9 2 条为既有,\n已有框架变更请求 aed8f8c。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:42:31-07:00"},{"Sha1":"c571477584e0f194316d78c8c49768d2303d2d7e","Message":"feat(governance): CHG-001 四项审批落库并排定变更窗口,合并闸门开启\n\n修订 7 技术侧此前已就绪(就绪度 BLOCKED 而非 INVALID),五条阻塞全部是人的\n决定。本次按决策落库:四个角色均由 luoanwu 审批 APPROVED,变更窗口排在\n2026-09-15T05:40:30Z。\n\n- changeWindow.scheduledAt 先于回执写入。record 脚本注释警告过反序的后果:\n 四份回执录完后再排窗口,录入器对已录回执返回 NOOP 并在重算闸门前退出,\n \"UNSCHEDULED: change window\" 将再无脚本可清。先排窗口后录回执可避开该陷阱,\n dry-run 已验证第一份录入后该条即消失\n- 四份回执置于 平台治理/基础/approvals/,逐份通过 validator(VALID,各引 3 份证据:\n 变更请求、DEC-033—036 正式评审包、发布运行手册),再逐份 --commit\n- .gitignore 放行 approvals/:此前被 /平台治理/基础/*/ 一律忽略,而审批记录的\n receiptSha256 正指回这些文件,不入库则 mergeGate 的证据链断在仓外\n\n结果:status pending_approval → approved_for_catalog_merge;\nmergeGate.eligible=true、blockingReasons 清空;就绪度 BLOCKED → READY;\naudit-foundation 阻塞项 7 → 5(CANDIDATE_CATALOG_GATE_BLOCKED 消解)。\n授权边界未越线:catalogMutationAuthorized=true,而 runtime / serviceCreation /\ndeployment 三项仍为 false——登记目录不等于宣告平台可用。\n\n回执 comment 记录了一处已知偏差:变更请求正文写「79/79 测试通过」,本轮独立复验\nverify-new-platform-change.mjs 实为 80/80(rollbackByteIdentical=true、\nformalUnchanged=true)。偏差方向是增加用例,经决策不为此重基线为修订 8,\n在回执中声明知悉。\n\n包指纹 6e2e69d6…ffa97f 全程未变:审批记录不在 frozenInputs/frozenEvidence 之列。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:42:10-07:00"}],"HeadCommit":{"Sha1":"615c017a32da032ecaeb00215d8b8b5418d9b122","Message":"fix(governance): 收回 CHG-001 四项审批并关闭合并闸门,回执按 SOP 归档\n\n修订 7 的四项 APPROVED(2026-09-15T05:40:40Z)与变更窗口(05:40:30Z)建立在\n一个目标真源有问题的包上:CHG-001 整包钉在 平台治理/platform-contracts,而\nDEC-010 已批准的 A 案明写「独立 Git-first 真源由基础设施仓的 contracts/\n工作区承担」,平台治理/README.md 也把前者定性为「冻结待移除,阶段 2 物理移除」。\n\n按现状合并的后果(核对记录 3689711):四个候选会登记进一个待移除的副本,\n而 audit-foundation 读 paths.activeContracts,三项 Catalog 阻断\n(CANDIDATES_NOT_REGISTERED / FORMAL_CATALOG_CHECK_FAILED /\nCANDIDATE_CATALOG_GATE_BLOCKED)不会消除;修订 7 补丁对活跃真源\npatch --fuzz=0 --dry-run 时 test/governance-linter.test.mjs 4 个 hunk 失败 1 个。\n\n目录负责人决定改指活跃真源、重基线为修订 8。按审批录入 SOP §5「包指纹或\n冻结文件漂移 → 全部旧回执失效,重新冻结包并重新审批」,本次先收口人的决定:\n\n- 四份回执连同 archive-manifest 归档到\n reports/catalog-package-archive/6e2e69d6…/approvals-withdrawn/,\n 记明失效原因与「不得转移到修订 8」,approvals/ 清空\n- 审批记录回到审批前形态:四项 PENDING、approver/decidedAt/evidenceRef/\n receiptSha256 置空、changeWindow.scheduledAt 置空(owner 与 rollbackOwner\n 按门禁要求保留 Catalog Owner)、mergeGate.eligible=false、\n authorizations.catalogMutationAuthorized 由 true 回到 false\n- revisionNote 追加【2026-09-14 收回】段,写明依据与修订 8 的前置\n\n包内容未动:revision 仍为 7,指纹 6e2e69d6…a84ffa97f 不变。修订 8 的重基线\n须等活跃真源 contracts/ 工作树 clean(当前有 src/domain/ 九个域包等在途实现),\n否则冻结摘要会钉住半成品。\n\n验证:tests/new-platform-approval-recording 7/7 恢复(此前 4 例因审批落库而\n红——这些用例把正式审批记录当夹具读)。tests/new-platform-catalog-readiness\n仍有 6 例红,成因是并行会话在途把 simulate-new-platform-catalog-merge.mjs\n改指 activeContractsRoot 而修订 8 摘要尚未重算,不属本次变更。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:46:57-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d10dae4ab5cf2e2f61c009033f00970b9a51c600...615c017a32da032ecaeb00215d8b8b5418d9b122","Len":31}...
|
1789451250
|
Edit
Delete
|
|
29979
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d10dae4ab {"Commits":[{"Sha1":"d10dae4ab5cf2e2f61c009033f00970b9a51c600","Message":"fix(governance): 门禁按 workspace.json 定位平台层,恢复迁移后失效的审计\n\n阶段 3 把平台目录从 基础/ 移到 企业控制面/ 之后,仍按 resolve(scriptDir,'..')\n推导的门禁全部失效:派生仓探测不到 git 仓(13/13 missing-git-repo)、平台发现\n数为 0、候选契约 ENOENT、audit-ci-gates 直接 ERR_MODULE_NOT_FOUND。冻结证据\n一直都在,只是脚本找错了路。\n\nlib/workspace.mjs 新增平台层解析器:\n- platformLayerRoot 取清单 layers.基础设施,platformDir / derivedRepo 据此展开\n (git 仓在 \u003c平台\u003e/base-framework,不在平台目录本身)\n- frameworkSourceRepo 取清单 paths.baseFramework\n- discoverPlatformNames 以「含 base-framework/ 子目录」为判据,宿主仓\n enterprise-platform、真源仓 企业IdP快照 与四个无派生仓的候选目录据此自动排除,\n 不再维护 excluded 目录名黑名单\n\n改接清单的脚本与测试:\n- workspace-evidence-status / audit-platform-openings / check-archived-derived-repos\n- audit-ci-gates 只改兼容入口传参——审计核心在 archived-20260910 冻结的\n 统一交付平台仓内,不可改\n- validate-new-platform-contracts、check-new-platform-contract-compatibility 与\n tests/new-platform-consumer-contracts:治理脚本与候选平台契约是两个基准,\n 原先共用一个变量,拆开\n- tests/helpers/devx-review-* 的 new URL 相对定位改走清单(pathname 对中文是\n 百分号编码,findWorkspaceRoot 认不出会回落到 cwd)\n\n验证:\n check-archived-derived-repos 13/13 冻结在 tag(原 0/13)\n audit-platform-openings 13/18 通过(原「应为 18,实际 0」)\n audit-ci-gates 18/18 结构通过,仅数量 19 vs 18(企业 IdP 已登记缺失)\n validate-new-platform-contracts 8 schemas / 19 accepted / 8 rejected\n check-new-platform-contract-compatibility 4 projects / 8 schemas / 19 types\n audit-foundation 恢复出具审计(原 exit 2 崩溃)\n tests/ 10/11 文件全绿\n\n余 new-platform-catalog-readiness 6 例失败,成因不是路径:阶段 4 改动了\nCHG-001 修订 6 的三个冻结输入,指纹失配,另行处理。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:52:14-07:00"},{"Sha1":"65c7ba829fdaa95b4373a4ced80246f6265b603c","Message":"feat(governance): 新增工作区一致性门禁,把迁移破坏类型固化成机器检查\n\n2026-09-14 迁移暴露的三类破坏都不在既有门禁视野里:判定逻辑按旧布局写死、\n冻结物摘要相符而内容过期、git worktree 两侧路径失联。新增 L1—L8 八项检查:\n\n L1 清单 layers/paths 声明的目录必须存在\n L2 `X/X/` 二次替换(替换脚本跑了两遍的痕迹)\n L3 旧层名残留(历史记录文件豁免)\n L4 受控 Markdown 本地链接可解析\n L5 Catalog / 候选清单登记路径可解析\n L6 worktree 两侧 gitdir 互指\n L7 冻结物摘要与磁盘内容一致\n L8 摘要相符但内容仍是旧布局 —— 本轮真正咬人的一类\n\n纯判定逻辑拆入 lib/workspace-consistency-core.mjs,7 个夹具用例覆盖正反向,\n其中一例直接锁住 L8 的教训:冻结 patch 摘要完好、内容仍写 `基础/\u003c平台\u003e`。\n门禁只读,不写任何文件;退出码 0/1/2。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:51:09-07:00"},{"Sha1":"f29bbbbeb8371825387d9437b91291af58f075d9","Message":"fix(governance): 基础审计改以清单定位基础设施层\n\n阶段 3 把 19 个平台仓从 基础/ 移入 企业控制面/,但 audit-foundation\n仍按 基础/ 的子目录枚举平台,且随后的机械替换把前缀改成了 平台治理/基础/\n——方向相反:那里只剩治理脚本与文档,平台一个也发现不了,\nclassifyDirectories 遂以 Invalid candidate directory 抛错,整条门禁跑不起来。\n\n- foundation-audit-core: 层前缀参数化(默认 企业控制面,可由调用方覆盖),\n 候选目录校验改用前缀比较而非硬编码正则;新增 externalDirectories,\n 使 工程基础框架 / 数字员工OS 这类跨层登记项不再被误判 missing-directory\n- audit-foundation: 平台层、框架真源仓与 OS 仓改由 workspace.json 解析\n (platformLayerRoot / frameworkSourceRepo / workspacePath)。\n try 块内 workspace 被同名 const 遮蔽,故派生路径一律在顶层先解析以避开 TDZ\n- 测试前缀改正,并补两个用例:跨层登记项、层名可覆盖\n\n回归:foundation-audit 11 → 13 用例全绿;audit-foundation 恢复可执行,\n阻塞项 8 项与迁移前基线逐项一致,派生仓发现 18/18。\ncontracts test 104 pass、governance test 193 pass、contracts check 4 项已知,\n三者亦与基线相同。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:50:36-07:00"}],"HeadCommit":{"Sha1":"d10dae4ab5cf2e2f61c009033f00970b9a51c600","Message":"fix(governance): 门禁按 workspace.json 定位平台层,恢复迁移后失效的审计\n\n阶段 3 把平台目录从 基础/ 移到 企业控制面/ 之后,仍按 resolve(scriptDir,'..')\n推导的门禁全部失效:派生仓探测不到 git 仓(13/13 missing-git-repo)、平台发现\n数为 0、候选契约 ENOENT、audit-ci-gates 直接 ERR_MODULE_NOT_FOUND。冻结证据\n一直都在,只是脚本找错了路。\n\nlib/workspace.mjs 新增平台层解析器:\n- platformLayerRoot 取清单 layers.基础设施,platformDir / derivedRepo 据此展开\n (git 仓在 \u003c平台\u003e/base-framework,不在平台目录本身)\n- frameworkSourceRepo 取清单 paths.baseFramework\n- discoverPlatformNames 以「含 base-framework/ 子目录」为判据,宿主仓\n enterprise-platform、真源仓 企业IdP快照 与四个无派生仓的候选目录据此自动排除,\n 不再维护 excluded 目录名黑名单\n\n改接清单的脚本与测试:\n- workspace-evidence-status / audit-platform-openings / check-archived-derived-repos\n- audit-ci-gates 只改兼容入口传参——审计核心在 archived-20260910 冻结的\n 统一交付平台仓内,不可改\n- validate-new-platform-contracts、check-new-platform-contract-compatibility 与\n tests/new-platform-consumer-contracts:治理脚本与候选平台契约是两个基准,\n 原先共用一个变量,拆开\n- tests/helpers/devx-review-* 的 new URL 相对定位改走清单(pathname 对中文是\n 百分号编码,findWorkspaceRoot 认不出会回落到 cwd)\n\n验证:\n check-archived-derived-repos 13/13 冻结在 tag(原 0/13)\n audit-platform-openings 13/18 通过(原「应为 18,实际 0」)\n audit-ci-gates 18/18 结构通过,仅数量 19 vs 18(企业 IdP 已登记缺失)\n validate-new-platform-contracts 8 schemas / 19 accepted / 8 rejected\n check-new-platform-contract-compatibility 4 projects / 8 schemas / 19 types\n audit-foundation 恢复出具审计(原 exit 2 崩溃)\n tests/ 10/11 文件全绿\n\n余 new-platform-catalog-readiness 6 例失败,成因不是路径:阶段 4 改动了\nCHG-001 修订 6 的三个冻结输入,指纹失配,另行处理。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:52:14-07:00"},"CompareURL":"luoanwu/platform-governance/compare/98ec9e9e61a1efb0e49011c06c28f63377accc23...d10dae4ab5cf2e2f61c009033f00970b9a51c600","Len":3}...
|
1789447994
|
Edit
Delete
|
|
29978
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"98ec9e9e6 {"Commits":[{"Sha1":"98ec9e9e61a1efb0e49011c06c28f63377accc23","Message":"fix(migration): 路径登记替换与门禁适配新结构\n\n数据登记(1099 处):code_truth / evidence / repository / directory 由旧\n层名改指新结构。历史记录(日期命名的分析与执行记录,28 份)保留旧路径,\n它们记录的是当时状态。\n\n门禁适配:\n- platform-project-catalog Schema 的 directory pattern 改为\n ^(企业控制面/[^/]+|数字员工OS|工程基础框架)$ —— 迁移后平台项目分散在\n 企业控制面/ 下与两个独占层,不再统一在 基础/ 下\n- governance-linter 平台目录扫描由 基础/ 改为 企业控制面/ + 两个独占层,\n 排除宿主仓 enterprise-platform 与事实模型仓\n- check-catalog-drift 前缀与排除集同步\n- WORKSPACE_ROOT_MARKERS 由 ['基础','doc'] 改为 ['平台治理','企业控制面']:\n 旧值在新结构下会误判——平台治理/ 下同时有 基础/ 与 doc/,镜像工作区的\n 中间层会被当成根\n- 冻结版 platform-contracts 同步上述改动,并补 workspace.json 根探测\n (它没有 workspace-root.mjs,原用 resolve(root,'..') 推导)\n- simulate-chg-* 的镜像工作区改由 lib/workspace.mjs 的 mirrorWorkspace\n 构造:platform-contracts 现嵌在 平台治理/ 下,镜像需还原两级结构\n- 测试中 resolve(root,'../X') 一律改走 baseline.workspaceRoot\n\n验证:contracts 104/104、governance 193/193、冻结版 76/76;\ncheck 回到基线 4 项 PLATFORM_PROJECT_UNREGISTERED(等 CHG-001 登记的\n4 个候选平台);simulate-chg-002/003/004 formalMutated=false。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:45:14-07:00"},{"Sha1":"2c886ca6ec1a6ba5d66aeddedcf53e9fa37e7317","Message":"feat(migration): 阶段 3 — 迁入新根,按架构图六层归位\n\n源根 企业产品/企业/企业应用/ 已清空,全部内容迁至 企业AI应用开发群/:\n\n 业务应用层/ 4 仓(嗨赞造意、巨嗨报价、巨嗨智服、尤克特拉)\n 企业领域应用层/ 4 仓(AI人事、AI项目与工单、知识云、设备云)\n 数字员工OS/ digital-employee-os + 层文档\n 企业控制面/ enterprise-platform + 18 平台仓 + 4 候选平台\n + 企业IdP快照 + 时空事实流转 + .secrets/.worktrees\n 工程基础框架/ base-framework ×2 + 层文档\n 平台治理/ doc/ + 基础/ + platform-contracts/ + 基础设施文档/\n\n本仓根由 企业应用/ 迁至新根,白名单重写;675 个文件识别为重命名。\nworkspace.json 的 layers/paths 切换到新结构,migration 段记录来源根。\n\n安全修正:.secrets/ 与 *.env 加入硬排除。此前 `!/基础设施/` 放行整个\n目录时误将 .secrets/ 两个文件纳入并推送(提交 91a01b1),凭证需轮换,\n历史需清除——另行处理。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:28:46-07:00"},{"Sha1":"65264f9956d370cc6d7789477feb5ebbdf608666","Message":"fix(workspace): 目录按架构图命名,词表名作为概念名正式对应\n\n先前把新根五个目录从架构图命名改成了治理词表命名,理由是\"改用展示名\n要多付 171 处替换\"——该理由不成立:两种命名下 171 处旧路径都要改,\n工作量相同,被误记成了展示名的单边代价。且新根目录本就按架构图建好,\n属明确意图。\n\nworkspace.json 新增 terminology.layers:term(治理词表名,治理文档与\n门禁口径用)↔ directory(物理目录名,取自架构图,路径与 code_truth 用)。\n两套名称不是分叉,是同一层的概念名与路径名。\n\nmigration 增 targetLayers / targetPaths,作为阶段 3 路径替换的映射来源。\n\n目录名与代码的耦合已由上一提交的清单锚点解除,按图命名不再有门禁成本。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T20:46:07-07:00"},{"Sha1":"da52f2ea85b9398bd5e25b67e971f5bec1e50337","Message":"feat(governance): 工作区根改由 workspace.json 定位,解除目录名耦合\n\n基础/scripts/* 一律用 resolve(基础目录, '..') 推导工作区根。迁移方案把\n基础/ 移入 平台治理/ 后该式子会得到 平台治理/,而那里没有 公用应用/、\n业务应用/、基础设施/——simulate-chg-* 靠 readdirSync(workspace) 重建的\n临时镜像工作区将残缺,check.mjs 的平台目录扫描随之全错。\n\n- 新增根 workspace.json:既是工作区根标记,也声明各层与关键路径,\n 目录重排时只改本文件\n- 新增 基础/scripts/lib/workspace.mjs:向上查找清单确定工作区根,\n 无清单时回落到旧式推导\n- 7 个脚本改用它:audit-foundation、verify-new-platform-change、\n simulate-chg-002/003/004/005、simulate-new-platform-catalog-merge、\n check-new-platform-catalog-change-readiness\n\n回归与基线逐项一致:simulate-chg-002/003/004/005 全部 status=passed、\n80/80、formalMutated=false,CHG-003 仍 6→0;audit-foundation 仍 8 项阻塞。\n迁移后场景实测:旧式定位到 平台治理/ 且只看到 3 个条目,新式正确定位\n新根并看到完整六层。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T20:40:01-07:00"},{"Sha1":"95d7c59e1064a02460b90d41436c69c76d095554","Message":"docs(governance): hi-atelier 正式名改为嗨赞造意并登记对照\n\n活文档统一改名(CLAUDE.md 五层词表、回灌台账驱动方清单、\n基础平台接入模型消费者矩阵、DEC-037 契约材料、分层与装配模型)。\n\n回灌台账新增 §0.1 应用改名登记,列出新旧名对照,并说明\n三类有意保留旧名的位置:冻结来源目录(CHG-001 指纹)、\n已批准 DEC 正文(决议不因改名改写)、日期命名的历史记录\n(记录当时状态,不追溯改写)。\n\n架构图 PNG 仍标旧名,待重新导出。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T20:35:52-07:00"}],"HeadCommit":{"Sha1":"98ec9e9e61a1efb0e49011c06c28f63377accc23","Message":"fix(migration): 路径登记替换与门禁适配新结构\n\n数据登记(1099 处):code_truth / evidence / repository / directory 由旧\n层名改指新结构。历史记录(日期命名的分析与执行记录,28 份)保留旧路径,\n它们记录的是当时状态。\n\n门禁适配:\n- platform-project-catalog Schema 的 directory pattern 改为\n ^(企业控制面/[^/]+|数字员工OS|工程基础框架)$ —— 迁移后平台项目分散在\n 企业控制面/ 下与两个独占层,不再统一在 基础/ 下\n- governance-linter 平台目录扫描由 基础/ 改为 企业控制面/ + 两个独占层,\n 排除宿主仓 enterprise-platform 与事实模型仓\n- check-catalog-drift 前缀与排除集同步\n- WORKSPACE_ROOT_MARKERS 由 ['基础','doc'] 改为 ['平台治理','企业控制面']:\n 旧值在新结构下会误判——平台治理/ 下同时有 基础/ 与 doc/,镜像工作区的\n 中间层会被当成根\n- 冻结版 platform-contracts 同步上述改动,并补 workspace.json 根探测\n (它没有 workspace-root.mjs,原用 resolve(root,'..') 推导)\n- simulate-chg-* 的镜像工作区改由 lib/workspace.mjs 的 mirrorWorkspace\n 构造:platform-contracts 现嵌在 平台治理/ 下,镜像需还原两级结构\n- 测试中 resolve(root,'../X') 一律改走 baseline.workspaceRoot\n\n验证:contracts 104/104、governance 193/193、冻结版 76/76;\ncheck 回到基线 4 项 PLATFORM_PROJECT_UNREGISTERED(等 CHG-001 登记的\n4 个候选平台);simulate-chg-002/003/004 formalMutated=false。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:45:14-07:00"},"CompareURL":"luoanwu/platform-governance/compare/55f8a2b2b794f3104f47bde1db41106fe38d1b21...98ec9e9e61a1efb0e49011c06c28f63377accc23","Len":7}...
|
1789447687
|
Edit
Delete
|
|
29977
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/feat/platform-governance-baseline
|
0
|
{"Commits":[{"Sha1":"65264f995 {"Commits":[{"Sha1":"65264f9956d370cc6d7789477feb5ebbdf608666","Message":"fix(workspace): 目录按架构图命名,词表名作为概念名正式对应\n\n先前把新根五个目录从架构图命名改成了治理词表命名,理由是\"改用展示名\n要多付 171 处替换\"——该理由不成立:两种命名下 171 处旧路径都要改,\n工作量相同,被误记成了展示名的单边代价。且新根目录本就按架构图建好,\n属明确意图。\n\nworkspace.json 新增 terminology.layers:term(治理词表名,治理文档与\n门禁口径用)↔ directory(物理目录名,取自架构图,路径与 code_truth 用)。\n两套名称不是分叉,是同一层的概念名与路径名。\n\nmigration 增 targetLayers / targetPaths,作为阶段 3 路径替换的映射来源。\n\n目录名与代码的耦合已由上一提交的清单锚点解除,按图命名不再有门禁成本。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T20:46:07-07:00"},{"Sha1":"da52f2ea85b9398bd5e25b67e971f5bec1e50337","Message":"feat(governance): 工作区根改由 workspace.json 定位,解除目录名耦合\n\n基础/scripts/* 一律用 resolve(基础目录, '..') 推导工作区根。迁移方案把\n基础/ 移入 平台治理/ 后该式子会得到 平台治理/,而那里没有 公用应用/、\n业务应用/、基础设施/——simulate-chg-* 靠 readdirSync(workspace) 重建的\n临时镜像工作区将残缺,check.mjs 的平台目录扫描随之全错。\n\n- 新增根 workspace.json:既是工作区根标记,也声明各层与关键路径,\n 目录重排时只改本文件\n- 新增 基础/scripts/lib/workspace.mjs:向上查找清单确定工作区根,\n 无清单时回落到旧式推导\n- 7 个脚本改用它:audit-foundation、verify-new-platform-change、\n simulate-chg-002/003/004/005、simulate-new-platform-catalog-merge、\n check-new-platform-catalog-change-readiness\n\n回归与基线逐项一致:simulate-chg-002/003/004/005 全部 status=passed、\n80/80、formalMutated=false,CHG-003 仍 6→0;audit-foundation 仍 8 项阻塞。\n迁移后场景实测:旧式定位到 平台治理/ 且只看到 3 个条目,新式正确定位\n新根并看到完整六层。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T20:40:01-07:00"},{"Sha1":"95d7c59e1064a02460b90d41436c69c76d095554","Message":"docs(governance): hi-atelier 正式名改为嗨赞造意并登记对照\n\n活文档统一改名(CLAUDE.md 五层词表、回灌台账驱动方清单、\n基础平台接入模型消费者矩阵、DEC-037 契约材料、分层与装配模型)。\n\n回灌台账新增 §0.1 应用改名登记,列出新旧名对照,并说明\n三类有意保留旧名的位置:冻结来源目录(CHG-001 指纹)、\n已批准 DEC 正文(决议不因改名改写)、日期命名的历史记录\n(记录当时状态,不追溯改写)。\n\n架构图 PNG 仍标旧名,待重新导出。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T20:35:52-07:00"},{"Sha1":"98de9b14bed6ea4597187525f26d046d3a64c7d6","Message":"fix(governance): 排除 git worktree 目录,勿作嵌入仓纳入\n\n基础设施/.worktrees/security-governance-hardening 是 enterprise-platform\n的 worktree,首次提交时被当作嵌入仓加成 gitlink(clone 后为空目录)。\nworktree 的 .git 是文件而非目录,常规仓扫描会漏掉。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T20:20:08-07:00"},{"Sha1":"2c324e70c3aa9d29f0eb4a8f4bab1d1842dc6bc6","Message":"chore(governance): 为平台治理资产建立版本控制\n\n此前 doc/、基础/ 治理文档、门禁脚本与证据、platform-contracts/ 均不在\n任何 git 仓中——整个应用群的规则真源没有版本历史,改错无法回滚、\n变更无从追溯。2026-09-14 全量备份时确认这是比无远端仓更严重的单点。\n\n纳入(678 文件 / 6.2 MB):\n- doc/:DEC-001~039 决议草案与 CHG-002~005 变更材料\n- platform-contracts/:Catalog、Schema 与门禁脚本\n (PF-04 阶段 2 物理移除前仍是 基础/scripts 的运行依赖)\n- 基础/:治理文档、scripts/ 门禁、tests/、reports/ 机器证据\n- 基础设施/:设计方案与开发计划(enterprise-platform 为独立仓)\n- 根目录分析报告与路径变更 patch\n\n不纳入:32 个应用/平台子仓(各有自己的仓)、node_modules、\n业务应用/ 下 3.4 GB 验收与发布产物。策略为白名单,见 .gitignore。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T20:18:46-07:00"}],"HeadCommit":{"Sha1":"65264f9956d370cc6d7789477feb5ebbdf608666","Message":"fix(workspace): 目录按架构图命名,词表名作为概念名正式对应\n\n先前把新根五个目录从架构图命名改成了治理词表命名,理由是\"改用展示名\n要多付 171 处替换\"——该理由不成立:两种命名下 171 处旧路径都要改,\n工作量相同,被误记成了展示名的单边代价。且新根目录本就按架构图建好,\n属明确意图。\n\nworkspace.json 新增 terminology.layers:term(治理词表名,治理文档与\n门禁口径用)↔ directory(物理目录名,取自架构图,路径与 code_truth 用)。\n两套名称不是分叉,是同一层的概念名与路径名。\n\nmigration 增 targetLayers / targetPaths,作为阶段 3 路径替换的映射来源。\n\n目录名与代码的耦合已由上一提交的清单锚点解除,按图命名不再有门禁成本。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T20:46:07-07:00"},"CompareURL":"luoanwu/platform-governance/compare/55f8a2b2b794f3104f47bde1db41106fe38d1b21...65264f9956d370cc6d7789477feb5ebbdf608666","Len":5}...
|
1789447687
|
Edit
Delete
|
|
29976
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"30565bfa7 {"Commits":[{"Sha1":"30565bfa7709e7905e2050f43b8a5d6595158069","Message":"fix(migration): adapt contracts and governance gates to the new directory layout\n\nThe workspace moved from 企业产品/企业/企业应用/ to 企业AI应用开发群/ and the\nfive layers were renamed after the architecture diagram. Catalog registrations\n(code_truth / evidence / repository / directory) now point at the new paths.\n\nGate changes:\n- platform-project-catalog schema: directory pattern is now\n ^(企业控制面/[^/]+|数字员工OS|工程基础框架)$ — platform projects used to sit\n under one parent (基础/) and are now spread across 企业控制面/ plus two\n layers that each hold a single project\n- governance-linter scans 企业控制面/ instead of 基础/, excluding the host repo\n (enterprise-platform) and the fact-model repo\n- check-catalog-drift: same prefix and exclusion set\n- WORKSPACE_ROOT_MARKERS: ['基础','doc'] → ['平台治理','企业控制面']. The old\n pair now matches 平台治理/ itself, so a mirror workspace's intermediate\n directory was being taken for the root\n- tests resolve workspace-relative paths through baseline.workspaceRoot\n\n104/104 contracts tests, 193/193 governance tests, check back to its\n4-issue baseline.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:45:37-07:00"}],"HeadCommit":{"Sha1":"30565bfa7709e7905e2050f43b8a5d6595158069","Message":"fix(migration): adapt contracts and governance gates to the new directory layout\n\nThe workspace moved from 企业产品/企业/企业应用/ to 企业AI应用开发群/ and the\nfive layers were renamed after the architecture diagram. Catalog registrations\n(code_truth / evidence / repository / directory) now point at the new paths.\n\nGate changes:\n- platform-project-catalog schema: directory pattern is now\n ^(企业控制面/[^/]+|数字员工OS|工程基础框架)$ — platform projects used to sit\n under one parent (基础/) and are now spread across 企业控制面/ plus two\n layers that each hold a single project\n- governance-linter scans 企业控制面/ instead of 基础/, excluding the host repo\n (enterprise-platform) and the fact-model repo\n- check-catalog-drift: same prefix and exclusion set\n- WORKSPACE_ROOT_MARKERS: ['基础','doc'] → ['平台治理','企业控制面']. The old\n pair now matches 平台治理/ itself, so a mirror workspace's intermediate\n directory was being taken for the root\n- tests resolve workspace-relative paths through baseline.workspaceRoot\n\n104/104 contracts tests, 193/193 governance tests, check back to its\n4-issue baseline.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:45:37-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/1d84966ad54d59cdf4644114c40e86f4cec7cbb5...30565bfa7709e7905e2050f43b8a5d6595158069","Len":1}...
|
1789447540
|
Edit
Delete
|
|
29975
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1d84966ad {"Commits":[{"Sha1":"1d84966ad54d59cdf4644114c40e86f4cec7cbb5","Message":"chore(reports): rebind provenance to e0fb26d\n\nOnly provenance.gitSha and generatedAt changed; every check verdict is\nunchanged. Regenerated while establishing the pre-migration gate baseline.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:14:36-07:00"}],"HeadCommit":{"Sha1":"1d84966ad54d59cdf4644114c40e86f4cec7cbb5","Message":"chore(reports): rebind provenance to e0fb26d\n\nOnly provenance.gitSha and generatedAt changed; every check verdict is\nunchanged. Regenerated while establishing the pre-migration gate baseline.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:14:36-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/02587c52835c0d763ab44c302cb862b5cb1a0125...1d84966ad54d59cdf4644114c40e86f4cec7cbb5","Len":1}...
|
1789445680
|
Edit
Delete
|
|
29974
|
5
|
5
|
5
|
106
|
0
|
0
|
refs/heads/sync/v0.16.0
|
1
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"0a9a11a92a9e45d647e7feaea0bafe7cdc3d5f11","Message":"docs: record clean acceptance @ 246f04b(sync/v0.16.0:runtime 169 / 差分 7×2 / tenantRlsEnforced=1;UI 4×5;地板按本仓收紧)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"hillao","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"hillao","Timestamp":"2026-09-10T07:19:55-07:00"},"CompareURL":"luoanwu/tenant-scope/compare/main...0a9a11a92a9e45d647e7feaea0bafe7cdc3d5f11","Len":0}...
|
1789445465
|
Edit
Delete
|
|
29973
|
5
|
5
|
5
|
106
|
0
|
0
|
refs/heads/sync/v0.16.0
|
1
|
|
1789445465
|
Edit
Delete
|
|
29972
|
5
|
5
|
5
|
83
|
0
|
0
|
refs/heads/codex/platform-rc1
|
1
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"6823a38dc4626db9f396978663efbc2493a1276c","Message":"fix(ci): fetch report provenance history for HR governance\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-12T06:58:07-07:00"},"CompareURL":"luoanwu/juhai-ai-hr-system/compare/main...6823a38dc4626db9f396978663efbc2493a1276c","Len":0}...
|
1789445442
|
Edit
Delete
|
|
29971
|
5
|
5
|
5
|
83
|
0
|
0
|
refs/heads/codex/platform-rc1
|
1
|
|
1789445442
|
Edit
Delete
|
|
29970
|
5
|
5
|
5
|
83
|
0
|
0
|
refs/heads/codex/ms1-platform-consumer
|
1
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"c934bc46240daae849ad93cfacaa3b25c41b323f","Message":"test(platform): keep dispatcher fixtures aligned with Redis client options\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-12T02:38:16-07:00"},"CompareURL":"luoanwu/juhai-ai-hr-system/compare/main...c934bc46240daae849ad93cfacaa3b25c41b323f","Len":0}...
|
1789445437
|
Edit
Delete
|
|
29969
|
5
|
5
|
5
|
83
|
0
|
0
|
refs/heads/codex/ms1-platform-consumer
|
1
|
|
1789445437
|
Edit
Delete
|
|
29968
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/feat/u31-u33-u34-consumer-feedback
|
0
|
{"Commits":[{"Sha1":"727044996 {"Commits":[{"Sha1":"727044996fde65045ab4ca56a060c0a32fa24c0a","Message":"chore(reports): rebind after merging main into the U-31/33/34 branch\n\n合并 main(6 个提交)后重跑根 pnpm check:exit 0,31 项。\nmodule-imports 报告的合并冲突按「报告是运行产物」取 main 版本后由本轮重新生成。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T19:21:58-07:00"},{"Sha1":"9a7231221ba190a84f91f1f2771017927d991328","Message":"Merge branch 'main' into feat/u31-u33-u34-consumer-feedback\n\n# Conflicts:\n#\treports/module-imports.latest.json\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T19:21:34-07:00"},{"Sha1":"35e44a1d97cad7b20404416743167de2aa15c277","Message":"chore(reports): bind check:evidence baseline @ 5f0473b\n\n13 份已登记报告新鲜,5 条 warn(port-conformance、runtime/ui 验收、\nrevocation-sla、mainline-acceptance —— 都是需要真实库/容器才能重跑的,\n已在 evidence-scopes.json 写明 promoteBy),32 份未登记只计 info。\nmodule-imports 顺带在干净树重跑回绑(315 文件 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-14T10:37:16-07:00"},{"Sha1":"5f0473b6d7bf2089d3715c6f637320d6d96ac862","Message":"feat(governance): gate machine-evidence freshness by scope, not commit distance\n\n仓纪律 5 只要求报告绑 gitSha + worktreeDirty=false,没有任何检查关心那个 SHA\n相对 HEAD 是否已经过期;runtime 的 check:docs-truth 断言 N 也只比对「文档声明的\nSHA == 报告 provenance 的 SHA」。于是 CLAUDE.md 的「当前状态」可以逐字引用一份\n早被后续提交推翻的报告,而全链门禁一片绿。\n\n2026-09-14 实锤:main 上 stack-image-pins.latest.json 绑 7e279c5,其后\nstack/compose.yaml 已被改(ai-gateway 去掉空 DATABASE_URL),那份「12 镜像\n0 未锁」的结论形式上已失效,无人察觉。\n\n判据特意不用「落后几个提交」——实测那样会误报 38 条(runtime 验收落后 32 个\n提交,作用域却一行没动)。判据是:绑定 SHA → HEAD 之间有没有改到该报告自己\n覆盖的文件,作用域逐条登记在 governance/evidence-scopes.json。\n\n- severity 逐条登记:静态检查 error,需真实库/容器重跑的验收先 warn 并写\n promoteBy,覆盖面与严格度都按登记涨,不搞一刀切。\n- 脏绑报告在干净树上判红(说明脏绑被提交了),在脏树上只 warn(改到一半)。\n- 例外须带 reason/recordedAt/resolveBy(G-13),失效判 EXCEPTION_STALE。\n- 未登记的报告只计 SCOPE_UNDECLARED(info),不判红。\n\n10 个用例,含一个真实 git 仓集成用例钉住核心判据:作用域外连改三个提交仍绿,\n作用域内一改即红。放在根 check 链尾。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T10:36:33-07:00"},{"Sha1":"9807535a2b81bc14a35ffc306d7b1b0910f0f99f","Message":"chore(reports): bind the ai-gateway first-start evidence @ 51351b3\n\nliveliness / readiness 200(db: Not connected)、带 master key 的 /v1/models\n200 返回 platform-default-chat、无 key 401 / 错 key 400;/v1/chat/completions\n401 是供应商侧 replace-me,链路本身通。干净树绑 51351b3。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T10:10:43-07:00"}],"HeadCommit":{"Sha1":"727044996fde65045ab4ca56a060c0a32fa24c0a","Message":"chore(reports): rebind after merging main into the U-31/33/34 branch\n\n合并 main(6 个提交)后重跑根 pnpm check:exit 0,31 项。\nmodule-imports 报告的合并冲突按「报告是运行产物」取 main 版本后由本轮重新生成。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T19:21:58-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/a76562a9c4710a6763243f4f1e1b87f12461b429...727044996fde65045ab4ca56a060c0a32fa24c0a","Len":8}...
|
1789445430
|
Edit
Delete
|
|
29967
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/feat/fact-read-http-pick
|
0
|
{"Commits":[{"Sha1":"517414d88 {"Commits":[{"Sha1":"517414d8806adba9ad700d6508e6c563513a583e","Message":"chore(reports): rebind after merging main into the fact-read pick\n\n合并 main(6 提交)后根 pnpm check exit 0,31 项。\n\n合并过程记录两件事:\n1. runtime/clients/fact/README.md 两边都新建过——main 侧是 U-31/34 的中文接入契约,\n 本分支侧是 3074b75 的英文 reader 文档。两者内容不重叠,合并而非二选一:\n 接入契约保持 1—4 节,reader 文档作为第 5 节并入。\n2. 合并后 module-fact 构建失败(FactReadRuntime 未导出)。根因不是合并本身:\n modules/* 用 composite:true,包根的 tsconfig.tsbuildinfo 残留让 tsc -p 认为无变化,\n exit 0 却不产出更新后的 dist/index.d.ts;turbo 随后把这份**空产出缓存**了,\n 于是后续每次构建都从缓存恢复错误的 dist——删 dist 重建也没用,因为 tsbuildinfo 还在。\n 清掉 runtime 下全部 tsconfig.tsbuildinfo + turbo run build --force 后恢复正常。\n 这是 C69 形态在本仓的复现,且被 turbo 缓存放大了一层。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T19:26:21-07:00"},{"Sha1":"2a3471d25243924c1d27cf96654b8d4fa33978ca","Message":"Merge branch 'main' into feat/fact-read-http-pick\n\n# Conflicts:\n#\treports/caddy.latest.json\n#\treports/catalog-drift.latest.json\n#\treports/catalog-reconciliation.latest.json\n#\treports/facts.latest.json\n#\treports/fixtures.latest.json\n#\treports/migration-decs.latest.json\n#\treports/module-imports.latest.json\n#\truntime/clients/fact/README.md\n#\truntime/reports/agent-adapters.latest.json\n#\truntime/reports/conformance-matrix.latest.json\n#\truntime/reports/contract-consumers.latest.json\n#\truntime/reports/docs-truth.latest.json\n#\truntime/reports/dual-backend-parity.latest.json\n#\truntime/reports/fork-readiness.latest.json\n#\truntime/reports/governance-docs.latest.json\n#\truntime/reports/governance-rules.latest.json\n#\truntime/reports/governance-status.latest.json\n#\truntime/reports/governance.latest.json\n#\truntime/reports/migrations.latest.json\n#\truntime/reports/naming.latest.json\n#\truntime/reports/runtime-governance.latest.json\n#\truntime/reports/schema-sync.latest.json\n#\truntime/reports/statemachine-write-guard.latest.json\n#\truntime/reports/validation-source.latest.json\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T19:23:23-07:00"},{"Sha1":"727044996fde65045ab4ca56a060c0a32fa24c0a","Message":"chore(reports): rebind after merging main into the U-31/33/34 branch\n\n合并 main(6 个提交)后重跑根 pnpm check:exit 0,31 项。\nmodule-imports 报告的合并冲突按「报告是运行产物」取 main 版本后由本轮重新生成。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T19:21:58-07:00"},{"Sha1":"9a7231221ba190a84f91f1f2771017927d991328","Message":"Merge branch 'main' into feat/u31-u33-u34-consumer-feedback\n\n# Conflicts:\n#\treports/module-imports.latest.json\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T19:21:34-07:00"},{"Sha1":"35e44a1d97cad7b20404416743167de2aa15c277","Message":"chore(reports): bind check:evidence baseline @ 5f0473b\n\n13 份已登记报告新鲜,5 条 warn(port-conformance、runtime/ui 验收、\nrevocation-sla、mainline-acceptance —— 都是需要真实库/容器才能重跑的,\n已在 evidence-scopes.json 写明 promoteBy),32 份未登记只计 info。\nmodule-imports 顺带在干净树重跑回绑(315 文件 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-14T10:37:16-07:00"}],"HeadCommit":{"Sha1":"517414d8806adba9ad700d6508e6c563513a583e","Message":"chore(reports): rebind after merging main into the fact-read pick\n\n合并 main(6 提交)后根 pnpm check exit 0,31 项。\n\n合并过程记录两件事:\n1. runtime/clients/fact/README.md 两边都新建过——main 侧是 U-31/34 的中文接入契约,\n 本分支侧是 3074b75 的英文 reader 文档。两者内容不重叠,合并而非二选一:\n 接入契约保持 1—4 节,reader 文档作为第 5 节并入。\n2. 合并后 module-fact 构建失败(FactReadRuntime 未导出)。根因不是合并本身:\n modules/* 用 composite:true,包根的 tsconfig.tsbuildinfo 残留让 tsc -p 认为无变化,\n exit 0 却不产出更新后的 dist/index.d.ts;turbo 随后把这份**空产出缓存**了,\n 于是后续每次构建都从缓存恢复错误的 dist——删 dist 重建也没用,因为 tsbuildinfo 还在。\n 清掉 runtime 下全部 tsconfig.tsbuildinfo + turbo run build --force 后恢复正常。\n 这是 C69 形态在本仓的复现,且被 turbo 缓存放大了一层。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T19:26:21-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/176c33149337c2eb03a0cdfb11ed910f75700e0c...517414d8806adba9ad700d6508e6c563513a583e","Len":12}...
|
1789445400
|
Edit
Delete
|
|
29966
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/feat/cl-5-publish-client-fact
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"eb3cf2c38148bfc0dac9ab1e8cdd5733ae8aa13f","Message":"chore(reports): rebind to 64914b9 and refresh the foundation audit snapshot\n\nThe audit snapshot that the MS-4 exit condition cites had not been rerun\nsince 2026-09-05 -- before the decision meeting. It still reported 2 DECs\napproved and 30 pending against today's 32/0, and still raised\nFACT_DECISIONS_PENDING_OR_UNKNOWN, which that meeting resolved. Refreshed\nhere and in 基础/reports/基础目录统一审计.latest.json (the source copy,\noutside version control).\n\nStatus stays BLOCKED. Seven blockers persist, INVENTORY_INVALID is new\n(企业 IdP lacks 开发计划.md). Each is now attributed in plan deviation #32,\nwhich also records that the cited \"19/19\" denominator does not exist in\nthe report at all: it is 25 directories / 21 formal / 4 unregistered\ncandidates, with 20 of 21 formal entries document-complete.\n\nGate reports rebound to 64914b9 on a clean tree; `pnpm check` exits 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-13T21:26:55-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/main...eb3cf2c38148bfc0dac9ab1e8cdd5733ae8aa13f","Len":0}...
|
1789445395
|
Edit
Delete
|
|
29965
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/feat/cl-5-publish-client-fact
|
0
|
|
1789445395
|
Edit
Delete
|
|
29964
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/feat/b7-dev-resident-runtime
|
0
|
{"Commits":[{"Sha1":"b7e62c57b {"Commits":[{"Sha1":"b7e62c57bb8298ef54a679a431dbfdf218814dfe","Message":"chore(reports): bind the ai-gateway first-start evidence @ c27c06a\n\nliveliness / readiness 200(db: Not connected)、带 master key 的 /v1/models\n200 返回 platform-default-chat、无 key 401 / 错 key 400;/v1/chat/completions\n401 是供应商侧 replace-me,链路本身通。干净树绑 c27c06a。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T10:07:05-07:00"},{"Sha1":"c27c06ab1c884ee06c2e783c7b514e98163a2840","Message":"fix(stack): stop injecting an empty DATABASE_URL into ai-gateway\n\nLiteLLM 见到空串即以 \"unsupported scheme '\u003cmissing scheme\u003e'\" 退出,而\n`DATABASE_URL: ${LITELLM_DATABASE_URL:-}` 在变量未设时注入的正是空串。\n这个定义从 2026-09-11 写下起就没被验证过——stack-up 记录里 ai-gateway\n一直是\"未起\",所以缺陷一直没暴露。\n\n- compose.yaml:ai-gateway 不再声明 DATABASE_URL(无 DB 模式)。\n- overlays/ai-gateway-db.yaml:要 DB 模式改为显式叠加,且 LITELLM_DATABASE_URL\n 必填;注释写明不得指向 platform_aigateway_*(M7 权威库)。\n- stack/README:镜像行改为 digest 实况,litellm tag 已首次 pull 核实;\n 两处\"ai-gateway 未起\"改为 12 服务全跑。\n- CLAUDE.md stack 行补 2026-09-14 增量,只引机器证据。\n\n本轮只动 D-7 采纳组件,未动 M7 模块(仍 state=shape / blocked_by DEC-007)。\n供应商密钥仍是 replace-me,真实模型调用返回供应商 401,已在记录里写明。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T10:06:42-07:00"},{"Sha1":"01188daa7965c1cfa90fdc9f8aabdf96a1892d14","Message":"chore(reports): bind the B-7 resident-runtime evidence @ c75f22a\n\n七 profile 装载、内核与七个模块 /health 全 200、无凭证决策端点 401、经 Caddy\n入口 200;容器 restart unless-stopped、healthy。provenance 干净树绑 c75f22a。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T09:52:17-07:00"},{"Sha1":"c75f22a20fb62553cb0b0556dbdce8fbd6087757","Message":"feat(stack): run the platform runtime as a resident dev container (B-7)\n\n核实报告的 B-7 记「没有可被 HR / OS 调用的地址」:compose 的 runtime 一直是\n候选注释块,七个 platform_\u003cm\u003e_dev 库建了但零张表。本次启用该服务并把它跑起来。\n\n- compose.yaml:启用 runtime,镜像改 ${PLATFORM_RUNTIME_IMAGE:?};补上原模板\n 缺的七个 DATABASE_URL_\u003cMODULE\u003e——模板写于一模块一库之前,只有内核三个 URL,\n 按原样启用四个 authority 模块会连不上自己的库。\n- overlays/dev.yaml:restart unless-stopped + 回环 53001。\n- provision/redis-dbs.json:登记逻辑库 14(七 profile 同进程只能独占一个)。\n- runbook §2 / stack README:dev 常驻形态与起停命令。\n\n供给与验收留在 docs/B-7-dev常驻运行时启动记录-2026-09-14.md;环境变量文件在\n仓外 .secrets/,不入 git。ai-gateway 容器因 ghcr 拉取经本机代理被 reset 未起,\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-14T09:51:41-07:00"}],"HeadCommit":{"Sha1":"b7e62c57bb8298ef54a679a431dbfdf218814dfe","Message":"chore(reports): bind the ai-gateway first-start evidence @ c27c06a\n\nliveliness / readiness 200(db: Not connected)、带 master key 的 /v1/models\n200 返回 platform-default-chat、无 key 401 / 错 key 400;/v1/chat/completions\n401 是供应商侧 replace-me,链路本身通。干净树绑 c27c06a。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T10:07:05-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/78edacc6e101fa24876cac37302ffb425fd94597...b7e62c57bb8298ef54a679a431dbfdf218814dfe","Len":4}...
|
1789445393
|
Edit
Delete
|
|
29963
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/feat/b7-dev-resident-runtime
|
0
|
|
1789445393
|
Edit
Delete
|
|
29962
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/codex/ms3-audit-receipt-integrity
|
0
|
{"Commits":[{"Sha1":"330854226 {"Commits":[{"Sha1":"3308542265e6a301126e1135310b11fbcddd5c5d","Message":"Merge pull request #24 from laoluojuhai/codex/ms3-audit-receipt-integrity\n\nfix(audit): 修复回执篡改漏检并整合撤权验收","AuthorEmail":"158980461+laoluojuhai@users.noreply.github.com","AuthorName":"laoluojuhai","CommitterEmail":"noreply@github.com","CommitterName":"GitHub","Timestamp":"2026-09-12T18:03:34-07:00"}],"HeadCommit":{"Sha1":"3308542265e6a301126e1135310b11fbcddd5c5d","Message":"Merge pull request #24 from laoluojuhai/codex/ms3-audit-receipt-integrity\n\nfix(audit): 修复回执篡改漏检并整合撤权验收","AuthorEmail":"158980461+laoluojuhai@users.noreply.github.com","AuthorName":"laoluojuhai","CommitterEmail":"noreply@github.com","CommitterName":"GitHub","Timestamp":"2026-09-12T18:03:34-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/5162994aa3dcdae57fdc9322ca629dbb580178f2...3308542265e6a301126e1135310b11fbcddd5c5d","Len":1}...
|
1789445373
|
Edit
Delete
|
|
29961
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/codex/ms234-runtime
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"399f0d9e72c6b443649a71809dab48cb32faec6a","Message":"Merge Gitea integration evidence without changing validated runtime\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-12T16:45:40-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/main...399f0d9e72c6b443649a71809dab48cb32faec6a","Len":0}...
|
1789445366
|
Edit
Delete
|
|
29960
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/codex/ms234-runtime
|
0
|
|
1789445366
|
Edit
Delete
|
|
29959
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/worktree-uiux-detail-pages
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"30fdd1609a7af216bfda2d4363ca21820d7114f4","Message":"docs: record complete pending-worktree reconciliation\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-09T05:19:04-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...30fdd1609a7af216bfda2d4363ca21820d7114f4","Len":0}...
|
1789445359
|
Edit
Delete
|
|
29958
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/worktree-uiux-detail-pages
|
0
|
|
1789445359
|
Edit
Delete
|
|
29957
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/release/image-type-r45
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"7066f958c067ca2787a77f94e26969023f1a8261","Message":"docs(release): record verified r46 deployment and acceptance\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-08T10:01:19-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...7066f958c067ca2787a77f94e26969023f1a8261","Len":0}...
|
1789445353
|
Edit
Delete
|
|
29956
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/release/image-type-r45
|
0
|
|
1789445353
|
Edit
Delete
|
|
29955
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/ops/restart-20260912
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"dc9fdea356d1b127366356170189bb388740fa5e","Message":"docs(ops): record service restart and scanner mount recovery\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-11T18:36:24-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...dc9fdea356d1b127366356170189bb388740fa5e","Len":0}...
|
1789445348
|
Edit
Delete
|
|
29954
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/ops/restart-20260912
|
0
|
|
1789445348
|
Edit
Delete
|
|
29953
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-workflow-20260912
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"545c98c6ffe5270812c731aa0aa2f08ae1961ef7","Message":"docs(releases): record verified shijie workflow deployment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-11T21:19:54-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...545c98c6ffe5270812c731aa0aa2f08ae1961ef7","Len":0}...
|
1789445341
|
Edit
Delete
|
|
29952
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-workflow-20260912
|
0
|
|
1789445341
|
Edit
Delete
|
|
29951
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-prop-ownership
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"3760ee6c9c7c0daf89b2e5b507b083464b0bce62","Message":"test(shijie): record verified prop ownership release evidence\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-10T16:55:46-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...3760ee6c9c7c0daf89b2e5b507b083464b0bce62","Len":0}...
|
1789445336
|
Edit
Delete
|
|
29950
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-prop-ownership
|
0
|
|
1789445336
|
Edit
Delete
|
|
29949
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-empty-source-sync-20260912
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"4fe8d343cc6b00bed830031e666cc0ac14cc276e","Message":"docs(releases): record live single-scene generation and visual refinement\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-11T19:40:03-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...4fe8d343cc6b00bed830031e666cc0ac14cc276e","Len":0}...
|
1789445331
|
Edit
Delete
|
|
29948
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-empty-source-sync-20260912
|
0
|
|
1789445331
|
Edit
Delete
|
|
29947
|
5
|
5
|
5
|
57
|
0
|
0
|
refs/heads/fix/shijie-actions-20260912
|
0
|
{"Commits":[],"HeadCommit":{"S {"Commits":[],"HeadCommit":{"Sha1":"a5c6bc1f21ff9ee8c6740b20079b2278d5a0a306","Message":"docs(releases): record verified shijie step action deployment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-11T22:04:26-07:00"},"CompareURL":"luoanwu/image-generation/compare/main...a5c6bc1f21ff9ee8c6740b20079b2278d5a0a306","Len":0}...
|
1789445326
|
Edit
Delete
|