|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
30163
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"553813dbe {"Commits":[{"Sha1":"553813dbe9541b78f89eca3151c117473b8444f4","Message":"chore(governance): 刷新门禁运行与消费两份报告\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:43:16-07:00"},{"Sha1":"cfe7f98accc01c95ed0c024d4e2d28e8ceb6ecfa","Message":"docs(governance): 企业控制面梳理与两份框架变更请求的增补落盘(另一会话的工作区改动)\n\n本提交内容不是本会话所写,是基础设施侧会话留在工作区的 6 个文档改动,按\"提交推送\"\n一并落盘。内容自洽、交叉引用齐备,且已静置 34 分钟(其 03:07 提交后未再动):\n\n- 企业控制面/README.md:能力框状态表重构为\"只记已验证的事实与仍缺的,不记计划\",\n 并加一句关键澄清——\"派生目录里现在剩下的是脚手架\"这句只对目录成立,不等于规则\n 也没了:18 个仓的独有规则已全部迁出真源仓(模块域 6 处、契约包域 9 处)\n- 基础设施文档/docs/企业控制面完整梳理-2026-09-15.md、采纳形态覆盖度对照-2026-09-14.md:\n 横向盘点与 G-* 缺口判据的增补\n- 工程基础框架/框架变更请求-治理报告结论字段-2026-09-15.md、迁移指纹分类-2026-09-14.md\n- 平台治理/基础/派生仓状态.json\n\n`派生仓状态.json` 是门禁读的数据真源,落盘前跑了全套:306 测试 301 通过 0 失败。\n\n本会话未改动其中任何一个字。若对方其实仍在编辑,按本仓惯例以后续提交订正,\n不 rebase 已推送内容。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:43:11-07:00"},{"Sha1":"241fc27b274606dee0b3198bb9d855e5a65a17c3","Message":"feat(governance): 本门禁补 11 条自证探针 —— D11 那把尺子先量自己\n\nD11 判别人\"有没有证明过自己会红\",而本门禁自己一条负向探针都没有。按它自己的\n判据,它属于\"未经验证\"那一档。\n\n夹具测试不能替代探针:测试跑的是构造输入,探针跑的是**本工作区真实数据的形状**。\n两者失效的方式不同——测试挂了没人能提交,探针哑了说明判定对真实数据不成立,\n而那正是 U-31(:503 单方向)/ U-33(:781 前提写死)/ U-36(\"跑不起来\"记成\"0 例\")\n的共同死法。\n\n11 条探针成对设计,正向要报、反向不得报(只做一半等于没测):\n d2 倒挂要报 / 公用应用持有不得报\n d5 DEC 全批仍 draft 要报 / 有未决 DEC 不得报\n d9 必填差异要报 / 只差 description 不得报\n d8 源码改动要让证据失效 / 只动 reports/ 不得失效\n 另有 d9 副本分叉、d11 哑探针、d4 无事实出口四条单向\n\n造不出探针时(本工作区缺相应数据)记 `skipped` 并写明原因,**绝不记\ndetected: false**——那会把\"跑不起来\"伪装成\"门禁没抓到\",正是 U-36 批评的谎报。\nskipped 条目不带 detected 字段,collectProbes 不收,D11 也就不会把它算成哑探针。\n\n哑探针报 D0 让本门禁自己失败,不只是写进报告——探针哑火意味着判定能力丢失,\n比它报出的任何一条都严重。\n\n实测 11 条全部命中,0 哑 0 跳过;夹具 51/51。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:39:59-07:00"}],"HeadCommit":{"Sha1":"553813dbe9541b78f89eca3151c117473b8444f4","Message":"chore(governance): 刷新门禁运行与消费两份报告\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:43:16-07:00"},"CompareURL":"luoanwu/platform-governance/compare/a8c2c315c5987714bc084f534c364ca525639562...553813dbe9541b78f89eca3151c117473b8444f4","Len":3}...
|
1789469000
|
Edit
Delete
|
|
30164
|
5
|
5
|
5
|
54
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"23c6960de {"Commits":[{"Sha1":"23c6960de45354e3ea524f9d81ce8b9d2d2fc7af","Message":"chore(reports): refresh clean static evidence @ 2ceb5d8(v0.22.0 记录提交;45 文件 / 314 静态用例)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:57:17-07:00"},{"Sha1":"2ceb5d88c1b36c1e5bb92608054e6503bedcc292","Message":"docs: record clean commit acceptance @ 6443380(v0.22.0:四级证据同 SHA——runtime 325 / 差分 10×2 / tenantRlsEnforced=1;UI 4×11;部署 13 步 + 回滚演练;生产 14 步 + 故障注入 + 恢复演练)\n\n- CLAUDE.md 动态区四级条目全部改为 clean `6443380`;tests-passing 地板 320 → 325;framework-version 行钉 v0.22.0@6443380\n- reports/baseline.json testsPassed 325\n- registry 实测仍为 0.16.1:0.17.0–0.22.0 未发布,发布动作留给框架 Owner(本轮 publish 未获执行许可)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:56:44-07:00"},{"Sha1":"64433802b34d1780402486d61a9b6dbf911ac0f7","Message":"docs(release): 0.22.0 版本轴收口——录入 C39 告警生产方、证据新鲜度四级断言与地板收紧\n\n- CHANGELOG 0.22.0 补第四项(C39:作业重试耗尽 / Redis 连接异常两个告警生产方,18fba1c 只提交了实现与门禁)\n- CLAUDE.md:C39 处置行、G20 仍缺清单去掉已补的两个生产方、own-tests 45 / own-test-cases 314(此前表内仍写 42 / 286)\n- reports/baseline.json:ownTestCases 311 → 314(棘轮只收紧)\n- COMPATIBILITY.md 0.22.0 小节补告警生产方的派生仓动作\n- check-docs-truth:freshness-sha-* 判定收紧为声明形式(另一会话在途改动,随本提交一并落地)\n- reports/ 为本轮 dirty 运行的中间产物,随后在 clean 提交上重跑刷新\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:50:54-07:00"},{"Sha1":"18fba1c6dc228a6b2cf425bd003892e5cfc6feaa","Message":"feat(observability): 补两个告警生产方——作业重试耗尽与 Redis 连接异常(G20,C39)\n\nG20 此前只有两个生产方(outbox 死信、流阻断)。另外两类同样该让值班知道的事件此前是静音的:\n\n- 作业重试耗尽:只广播 job.failed 实时事件 + 一行日志——**没人订阅实时事件时它就是静音的**,\n 而\"作业彻底失败\"恰恰最需要有人知道\n- Redis 连接异常:Redis 一断,实时投递与作业队列同时失效,此前只有一行 error 日志\n\n实现:\n- 内核 alert.ts 新增两个码与两个构造函数 buildJobRetryExhaustedAlert / buildRedisConnectionLostAlert\n (两后端共用同一份构造;各写一套会让同一事件在两个后端推出 severity/fingerprint 不同的告警,\n 值班侧无法按同一规则路由与去重)\n- 去重口径:作业按 jobId、Redis 按连接角色(重连风暴压成一条,投递器自带 TTL)\n- 两后端四处接线;Redis 告警失败不再触发告警,避免连接异常时自激\n- 内核 3 个单测(形状/去重/租户维度)+ check:dual-backend C39 绊网,负向已验证\n (把任一侧的构造函数改名即 exit 1)\n\n注:本轮只提交实现与门禁。CHANGELOG / CLAUDE.md 的录入与地板收紧留给正在并行做记录的会话——\n另:先前的 4f45161 因用了 git add -A,把该会话在途的 check-docs-truth.mjs 改动一并提交了,\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:04:54-07:00"},{"Sha1":"db5e2c0b9e1523e5db3b74b143fae3e6725d640a","Message":"feat(gates): 治理聚合报告必须声明结论(0.22.0,受理结论字段 FR-1/FR-2;C38)\n\n兄弟报告(runtime/ui)都写 status,唯独 governance.latest.json 不写:成败只由退出码表达,而退出码\n不进报告、不进证据链。工作区实测 20 份无一携带 status,消费侧两条 blocker 恒红且重跑一千次也不会变。\n更尖锐的一半是写入时机——三处失败关闭都在写入之后,指标 schema 挂了、棘轮回退了,磁盘上留下的仍是\n一份与成功运行无法区分的报告。看起来通过是彻底的静音,比永远红更坏。\n\n- 报告增 status(running → passed/failed)与 failures[{kind,detail}];先落 running,进程被杀也不会\n 留下 passed\n- 单点 finish():四条失败分支(状态清单生成失败、来源绑定违规、指标 schema 缺失、棘轮回退)与两条\n 成功分支(基线初始化、--update-baseline)全部经它定稿后才 exit;将来新增分支走 finish() 即不会漏\n- 负向实做:临时让子门禁少写一个预期指标 key → 退出码 1、磁盘 status=failed、failures 原因可读;\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-15T02:23:17-07:00"}],"HeadCommit":{"Sha1":"23c6960de45354e3ea524f9d81ce8b9d2d2fc7af","Message":"chore(reports): refresh clean static evidence @ 2ceb5d8(v0.22.0 记录提交;45 文件 / 314 静态用例)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:57:17-07:00"},"CompareURL":"luoanwu/base-framework/compare/9690ba98673547cb338309cd66f41ff6dbcaf61b...23c6960de45354e3ea524f9d81ce8b9d2d2fc7af","Len":27}...
|
1789469862
|
Edit
Delete
|
|
30165
|
5
|
9
|
5
|
54
|
0
|
0
|
refs/tags/v0.17.0
|
0
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"313137b9d94fff4665c34fcf8463c35ab72bd30a","Message":"feat(gates): compose project 身份随派生仓走,宿主端口可覆盖(0.17.0,F14/C32)\n\n受理平台治理 2026-09-14 的框架变更请求 FR-1/FR-2。缺陷是模板级的:compose 没有顶层 name\n时按**文件所在目录名**推导 project 名,而该文件在每个派生仓里都是 apps/api-nestjs/,于是\n28 个仓推导出同一个 project `api-nestjs`,共用 api-nestjs_pgdata / _redisdata 与同名容器,\n后 up 的那个接管先起者的容器与卷。2026-09-14 本机实测已发生(配置开关平台的 postgres/redis\n与 AI 工单系统的 minio 同属一个 project,公共卷创建于 2026-08-29)。单仓内部永远不与自己\n冲突,所以这件事只有横着比多份 compose 才判得出——F14 把它变成仓内静态断言。\n\n- 模板:顶层 name: ${COMPOSE_PROJECT_NAME:-base-framework};redis 宿主端口 ${REDIS_PORT:-6379}\n (取 :- 而非 fail-closed 的 :?——「连得上≠连的是本仓」那一层已由 G15 在 runner preflight\n 失败关闭,宿主端口冲突是响亮失败,不需要再打断所有现存 up)\n- F14(check:fork-readiness):顶层 name 必须存在、必须写成 ${COMPOSE_PROJECT_NAME:-\u003c身份\u003e}、\n 默认值必须等于 package.json.name 派生身份,ports 宿主侧一律不得写死。与 F3(验收库名前缀)、\n F12(RLS 组角色前缀)同族:集群级资源身份必须派生自 package.json.name。\n 负向三条已验证(删 name / 默认值仍是源身份 / 端口写死,均 exit 1)\n- scaffold:身份重绑定步骤一并改写 compose 默认值,结果写入记录行\n- 0.17.0:按 COMPATIBILITY §4「破坏性变更只允许出现在 minor」——改后首次 up 建新空卷,旧卷数据\n 不自动迁移。内核与契约包版本同步 0.17.0,本轮未发布到 registry\n- 回灌:CHANGELOG 0.17.0、COMPATIBILITY §2 [0.17.0]、迁移手册步骤 1 补三处集群级身份对照表、\n doctrine F14 行 / C32 索引 / 版本轴 / 常用命令补本地基座起法\n\nCo-Authored-By: Claude Opus 5 \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:29:54-07:00"},"CompareURL":"luoanwu/base-framework/compare/0000000000000000000000000000000000000000...ebfdb7c0f8574a8c30458ebe003aaf66c2fd0285","Len":0}...
|
1789469862
|
Edit
Delete
|
|
30166
|
5
|
9
|
5
|
54
|
0
|
0
|
refs/tags/v0.18.0
|
0
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"0b2c98923ab49f8cb8046091870ca5f8110ebeec","Message":"feat(ops): 运维平面从零到有——制品、生产编排与部署/生产两级验收(0.18.0,G20 第一二片)\n\nGOV-PRODUCTION-OPS-001 引用的两份报告此前没有任何生产者,状态清单按 MISSING 呈现。doctrine 明写\n「这是诚实的空,不得用占位报告转绿」,所以本版给的是真实链路而不是存在性打勾:\n\n- apps/api-nestjs/Dockerfile:deps / migrator / runtime 三 target;runtime 非 root、NODE_ENV=production、\n 入口 dist/src/main.js;migrator 是一次性运维容器(独有 prisma CLI 与 scripts/),迁移不在应用启动时跑\n- deploy/production/compose.yml:生产纪律变量在编排层就 ${VAR:?} fail-closed(APP_ID / RLS 两个角色 URL /\n TENANT_RLS_MODE / AUTH_MODE / 密钥 / ALERT_CHANNEL / PLATFORM_PORTS_MODE / REDIS_URL),与内核同口径\n- pnpm check:deployment(13 步):构建→迁移→供给 RLS 登录用户→生产纪律启动→健康分项→无凭证 401→\n JWT 真实写读→跨租户不可见→重启后数据仍在→回滚演练(切新标签再切回上一标签)→拆栈\n- pnpm check:production-acceptance:可观测(requestId 三态 + 制品日志必须是带 appId 的单行 JSON)、\n 依赖故障注入(停 Redis → health 必须 503 且 redis=down → 起回自愈 200)、备份恢复演练(pg_dump →\n 真删业务数据 → 恢复 → 重启 → 数据回来)\n- scripts/lib/deploy-stack.mjs:两个 runner 的编排是同一份真源,避免「一边按生产纪律起、另一边少一个\n fail-closed」这种最危险的漂移\n- F14 扩到全仓每一份 compose,允许 \u003c身份\u003e-\u003c用途\u003e 子命名;scaffold 的 compose 重绑同步扩面(负向已验证)\n- docs/deployment-runbook.md;迁移手册 P23(.dockerignore 漏排 tsbuildinfo → tsc 静默不产出)、\n P24(syntax 指令让构建依赖 Docker Hub)\n\n修复 C33:start:prod 指向不存在的 dist/main,文档承诺的生产启动命令一跑就 MODULE_NOT_FOUND——\n本仓此前从未以制品形态启动过,故长期无人踩到,由本版部署验收首轮红盘抓出。\n\n两个 runner 都跑在本机 Docker:证据等级到「部署形态可验证」为止,不是生产签收。仍缺 SLO、告警路由、\n灰度/多副本、限流熔断,以及 NestJS 侧成功请求没有访问日志(Fastify 侧自带)——均登记在 G20。\n\nCo-Authored-By: Claude Opus 5 \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:03:32-07:00"},"CompareURL":"luoanwu/base-framework/compare/0000000000000000000000000000000000000000...8a1f6300754e9599eb76f92b340dbeb0165731d3","Len":0}...
|
1789469862
|
Edit
Delete
|
|
30167
|
5
|
9
|
5
|
54
|
0
|
0
|
refs/tags/v0.19.0
|
0
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"535a0f5c9483f3b5fd08ac375a070d7cffd28394","Message":"fix(test): 健康用例并入既有验收文件——每多起一个 app 就多一个会派发毒药行的 dispatcher(P25)\n\n0.19.0 首轮 runtime 红盘:NestJS 侧 outbox.deadletter 的「前序失败时后序 seq 不得跨洞派发」失败,\npoisonRow.dispatchedAt 不为 null。根因不是写链,是**测试布局**:新开的两个 health 测试文件各自\ncreateApp()/buildApp(),多出来的 outbox dispatcher 在同一个库上真的把别的用例刚写下的毒药行派发了,\n而两个后端的 test 任务由 turbo 并行。\n\n- 两后端的附加健康子检查用例并入各自既有的 http.acceptance.test.ts(各 +4 例,23/23 通过),\n 删掉两个新开的测试文件;名字判责与重复登记合并为一例\n- 地板按合并后的实际值修正为 ownTests 44 / ownTestCases 305(本轮早先按未合并的布局误设为 46/307;\n 相对本轮开始前的 42/286 仍是收紧,不是放宽既有地板)\n- 迁移手册 P25 记下这条:失败现场看起来像跨洞派发的业务 bug,实际是多起了一个 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:18:31-07:00"},"CompareURL":"luoanwu/base-framework/compare/0000000000000000000000000000000000000000...62590d18280bd28f20cfc07e87f2f1a2a781489c","Len":0}...
|
1789469862
|
Edit
Delete
|
|
30168
|
5
|
9
|
5
|
54
|
0
|
0
|
refs/tags/v0.20.0
|
0
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"4be9d715627e11e93e1d06f6c2d044618ed7930a","Message":"fix(gates): 验收镜像构建在 BuildKit 元数据解析失败时回退经典构建器(P26)\n\n本机 Docker 代理挂掉后,docker build 不是快速失败而是**挂住**:22 分钟零输出,部署验收看起来像卡死。\n根因是 BuildKit 每次构建都要向 registry 解析 FROM 的 manifest,代理不可达时长时间重试;而基础镜像\n明明已经在本地镜像库里——同一份 Dockerfile 用经典构建器 5 秒就进到 apk add。\n\n- deploy-stack 的 buildImages:先 BuildKit,命中元数据解析失败特征(failed to resolve source metadata /\n registry / proxy / connection refused)就回退 DOCKER_BUILDKIT=0,并把回退记进 stack.buildFallbacks\n- 两个 runner 的报告新增 buildFallbacks 字段:证据必须说清自己是怎么来的,不能让「这次是怎么构建出来的」\n 成为读报告的人猜不到的事\n- 迁移手册 P26\n\nCo-Authored-By: Claude Opus 5 \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:18-07:00"},"CompareURL":"luoanwu/base-framework/compare/0000000000000000000000000000000000000000...931a3cb66d94b2cfef2fb4c4d8d68c0382b37172","Len":0}...
|
1789469862
|
Edit
Delete
|
|
30169
|
5
|
9
|
5
|
54
|
0
|
0
|
refs/tags/v0.21.0
|
0
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"729d6ae4fae463534fe768c94b837abee7ed8dc6","Message":"fix(gates): 镜像构建三级回退——BuildKit → 经典构建器 → 清代理(P26 扩写)\n\nDocker Desktop 把守护进程的代理配置注入构建容器:代理死掉时容器里的 pnpm install / prisma 引擎\n下载全部失败(实测 @prisma/engines postinstall: Failed),而容器直连网络其实是通的。三次尝试各对应\n一种本机基座故障,成功走的是哪一条写进报告 buildFallbacks。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T02:15:51-07:00"},"CompareURL":"luoanwu/base-framework/compare/0000000000000000000000000000000000000000...700f72fb25ba6f901be309c1312ea9cade497a46","Len":0}...
|
1789469862
|
Edit
Delete
|
|
30170
|
5
|
9
|
5
|
54
|
0
|
0
|
refs/tags/v0.22.0
|
0
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"64433802b34d1780402486d61a9b6dbf911ac0f7","Message":"docs(release): 0.22.0 版本轴收口——录入 C39 告警生产方、证据新鲜度四级断言与地板收紧\n\n- CHANGELOG 0.22.0 补第四项(C39:作业重试耗尽 / Redis 连接异常两个告警生产方,18fba1c 只提交了实现与门禁)\n- CLAUDE.md:C39 处置行、G20 仍缺清单去掉已补的两个生产方、own-tests 45 / own-test-cases 314(此前表内仍写 42 / 286)\n- reports/baseline.json:ownTestCases 311 → 314(棘轮只收紧)\n- COMPATIBILITY.md 0.22.0 小节补告警生产方的派生仓动作\n- check-docs-truth:freshness-sha-* 判定收紧为声明形式(另一会话在途改动,随本提交一并落地)\n- reports/ 为本轮 dirty 运行的中间产物,随后在 clean 提交上重跑刷新\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:50:54-07:00"},"CompareURL":"luoanwu/base-framework/compare/0000000000000000000000000000000000000000...70721a32fc48a464fd528d15bf1faae15ccf6ed1","Len":0}...
|
1789469862
|
Edit
Delete
|
|
30171
|
5
|
5
|
5
|
115
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"c1eaacaf6 {"Commits":[{"Sha1":"c1eaacaf61e725779ef920c36d1473cf1cf2819c","Message":"fix(gates): 两道 OS 门禁改为从 OS 检出解析依赖——移出框架仓后 O7 从未绿过\n\n- check-os-product-compat:tsc / zod / @nestjs/common / fastify / react 类型与 typeRoots 全部改指 OS_ROOT(此前沿用框架仓布局 join(ROOT, apps|packages/...),本仓无此目录,typecheck 恒 1)\n- 默认 OS_ROOT 改为工作区布局 ../../../数字员工OS/digital-employee-os(原 ../../Digital Employee OS 不存在),DIGITAL_EMPLOYEE_OS_ROOT 仍可覆盖\n- vitest.os-host.config:unplugin-swc 从 OS apps/api-nestjs/package.json 起解析(pnpm 不 hoist 到 OS 根)\n- 实跑:OS c433d57 / protocol 1.3.0,check:os-product 通过;check:os-product:runtime NestJS + Fastify 8 cases 通过\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:57:30-07:00"}],"HeadCommit":{"Sha1":"c1eaacaf61e725779ef920c36d1473cf1cf2819c","Message":"fix(gates): 两道 OS 门禁改为从 OS 检出解析依赖——移出框架仓后 O7 从未绿过\n\n- check-os-product-compat:tsc / zod / @nestjs/common / fastify / react 类型与 typeRoots 全部改指 OS_ROOT(此前沿用框架仓布局 join(ROOT, apps|packages/...),本仓无此目录,typecheck 恒 1)\n- 默认 OS_ROOT 改为工作区布局 ../../../数字员工OS/digital-employee-os(原 ../../Digital Employee OS 不存在),DIGITAL_EMPLOYEE_OS_ROOT 仍可覆盖\n- vitest.os-host.config:unplugin-swc 从 OS apps/api-nestjs/package.json 起解析(pnpm 不 hoist 到 OS 根)\n- 实跑:OS c433d57 / protocol 1.3.0,check:os-product 通过;check:os-product:runtime NestJS + Fastify 8 cases 通过\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:57:30-07:00"},"CompareURL":"luoanwu/base-framework-os-product/compare/893c0ef891743c1b55aae0f68073ba3ace55889b...c1eaacaf61e725779ef920c36d1473cf1cf2819c","Len":1}...
|
1789469869
|
Edit
Delete
|
|
30172
|
5
|
5
|
5
|
54
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"c358bd2a5 {"Commits":[{"Sha1":"c358bd2a5db604566b840c6dfb1ade93feeaf558","Message":"docs: 远端与 CI 状态回灌——两端已对齐 23c6960、tag v0.9.0–v0.22.0 齐;GitHub run 34960704560 因账户计费未启动,G14 仍不得 GREEN\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:59:19-07:00"}],"HeadCommit":{"Sha1":"c358bd2a5db604566b840c6dfb1ade93feeaf558","Message":"docs: 远端与 CI 状态回灌——两端已对齐 23c6960、tag v0.9.0–v0.22.0 齐;GitHub run 34960704560 因账户计费未启动,G14 仍不得 GREEN\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T03:59:19-07:00"},"CompareURL":"luoanwu/base-framework/compare/23c6960de45354e3ea524f9d81ce8b9d2d2fc7af...c358bd2a5db604566b840c6dfb1ade93feeaf558","Len":1}...
|
1789469962
|
Edit
Delete
|
|
30205
|
5
|
5
|
5
|
54
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d6747e346 {"Commits":[{"Sha1":"d6747e3462dad1329a0d99ed090c658cd7a42bed","Message":"chore(reports): refresh clean static evidence @ acf6482(G31 登记提交)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:53:44-07:00"},{"Sha1":"acf6482326e030965a080b792d3e90490e790aa9","Message":"feat(gates): 依赖安全审计门禁 pnpm check:dependencies(G31)——按运行时/工具链路径分类,首跑即红 28 条阻断\n\n- scripts/check-dependency-audit.mjs:pnpm audit --json → reports/dependency-audit.latest.json(带 provenance、status 三值 passed/failed/unrunnable)\n- critical 任意路径 / high 运行时路径未豁免即红;工具链(vitest、@nestjs/cli、@capacitor/cli、prisma CLI、eslint 家族、autoprefixer…)只记录\n- dependency-audit.allowlist.json:豁免必须带 reason + expires,过期失效;缺字段即红\n- 需要网络,不进 pnpm check(G9);CLAUDE.md 登记 G31 与基线表 RED 行,CHANGELOG [Unreleased]\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:53:36-07:00"}],"HeadCommit":{"Sha1":"d6747e3462dad1329a0d99ed090c658cd7a42bed","Message":"chore(reports): refresh clean static evidence @ acf6482(G31 登记提交)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:53:44-07:00"},"CompareURL":"luoanwu/base-framework/compare/c358bd2a5db604566b840c6dfb1ade93feeaf558...d6747e3462dad1329a0d99ed090c658cd7a42bed","Len":2}...
|
1789476826
|
Edit
Delete
|
|
30206
|
5
|
5
|
5
|
115
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"f63141d40 {"Commits":[{"Sha1":"f63141d4087ea0b27318bc844f2912d7bbe79684","Message":"feat(gates): 上游 OS SHA 钉住(os.upstream.json)+ 版本轴 0.2.0 + 报告入库\n\n- 两道门禁默认比对 os.upstream.json 的 gitSha(env 覆盖、空串解除);错钉负向 O0-SHA 红并指出上游已演进\n- CHANGELOG.md、package.json 0.2.0、tag v0.2.0;reports/*.latest.json 不再 gitignore\n- 证据:对 OS c433d57 静态兼容 passed、双宿主运行 8 cases passed\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:54:21-07:00"}],"HeadCommit":{"Sha1":"f63141d4087ea0b27318bc844f2912d7bbe79684","Message":"feat(gates): 上游 OS SHA 钉住(os.upstream.json)+ 版本轴 0.2.0 + 报告入库\n\n- 两道门禁默认比对 os.upstream.json 的 gitSha(env 覆盖、空串解除);错钉负向 O0-SHA 红并指出上游已演进\n- CHANGELOG.md、package.json 0.2.0、tag v0.2.0;reports/*.latest.json 不再 gitignore\n- 证据:对 OS c433d57 静态兼容 passed、双宿主运行 8 cases passed\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:54:21-07:00"},"CompareURL":"luoanwu/base-framework-os-product/compare/c1eaacaf61e725779ef920c36d1473cf1cf2819c...f63141d4087ea0b27318bc844f2912d7bbe79684","Len":1}...
|
1789476864
|
Edit
Delete
|
|
30207
|
5
|
9
|
5
|
115
|
0
|
0
|
refs/tags/v0.2.0
|
1
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"f63141d4087ea0b27318bc844f2912d7bbe79684","Message":"feat(gates): 上游 OS SHA 钉住(os.upstream.json)+ 版本轴 0.2.0 + 报告入库\n\n- 两道门禁默认比对 os.upstream.json 的 gitSha(env 覆盖、空串解除);错钉负向 O0-SHA 红并指出上游已演进\n- CHANGELOG.md、package.json 0.2.0、tag v0.2.0;reports/*.latest.json 不再 gitignore\n- 证据:对 OS c433d57 静态兼容 passed、双宿主运行 8 cases passed\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:54:21-07:00"},"CompareURL":"luoanwu/base-framework-os-product/compare/0000000000000000000000000000000000000000...9d0739b514719d1d8c795cccbb632fc2d665ad84","Len":0}...
|
1789476864
|
Edit
Delete
|
|
30208
|
5
|
5
|
5
|
115
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"f48463241 {"Commits":[{"Sha1":"f48463241be0a9f8ae2caee31ebdfdac645926cf","Message":"chore(reports): refresh clean evidence @ f63141d(v0.2.0:静态兼容 + 双宿主 8 cases,OS c433d57)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:54:50-07:00"}],"HeadCommit":{"Sha1":"f48463241be0a9f8ae2caee31ebdfdac645926cf","Message":"chore(reports): refresh clean evidence @ f63141d(v0.2.0:静态兼容 + 双宿主 8 cases,OS c433d57)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:54:50-07:00"},"CompareURL":"luoanwu/base-framework-os-product/compare/f63141d4087ea0b27318bc844f2912d7bbe79684...f48463241be0a9f8ae2caee31ebdfdac645926cf","Len":1}...
|
1789476893
|
Edit
Delete
|
|
30279
|
5
|
5
|
5
|
54
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"df53867de {"Commits":[{"Sha1":"df53867debc4df305454a4132edebe44819e5445","Message":"chore(dev): .claude/launch.json 基座端口对齐本机口径 5432/6379(原 55432/6382 是旧机器)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T23:02:06-07:00"}],"HeadCommit":{"Sha1":"df53867debc4df305454a4132edebe44819e5445","Message":"chore(dev): .claude/launch.json 基座端口对齐本机口径 5432/6379(原 55432/6382 是旧机器)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T23:02:06-07:00"},"CompareURL":"luoanwu/base-framework/compare/d6747e3462dad1329a0d99ed090c658cd7a42bed...df53867debc4df305454a4132edebe44819e5445","Len":1}...
|
1789538530
|
Edit
Delete
|
|
30294
|
5
|
5
|
5
|
106
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"f978ade7e {"Commits":[{"Sha1":"f978ade7e90469ee1a0a8992c1073d4275b00b51","Message":"docs: scope-snapshot-blueprint 把 DEC-001—005 从\"仍待裁决\"改为\"已裁定、权威 Resolver 未实现\"\n\n治理层 check-workspace-consistency L10 最后一条命中:DEC-001—005 已于 2026-09-12 批准,本文仍写作未决前置。\n改为\"卡在没做\"而不是\"卡在裁决\"(真源仓 runtime/modules/scope 仍 state=shape)。清扫后 L10 归零,工作区一致性 4 → 3 条。\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-15T05:53:28-07:00"}],"HeadCommit":{"Sha1":"f978ade7e90469ee1a0a8992c1073d4275b00b51","Message":"docs: scope-snapshot-blueprint 把 DEC-001—005 从\"仍待裁决\"改为\"已裁定、权威 Resolver 未实现\"\n\n治理层 check-workspace-consistency L10 最后一条命中:DEC-001—005 已于 2026-09-12 批准,本文仍写作未决前置。\n改为\"卡在没做\"而不是\"卡在裁决\"(真源仓 runtime/modules/scope 仍 state=shape)。清扫后 L10 归零,工作区一致性 4 → 3 条。\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-15T05:53:28-07:00"},"CompareURL":"luoanwu/tenant-scope/compare/0a9a11a92a9e45d647e7feaea0bafe7cdc3d5f11...f978ade7e90469ee1a0a8992c1073d4275b00b51","Len":1}...
|
1789539963
|
Edit
Delete
|
|
30314
|
5
|
9
|
5
|
97
|
0
|
0
|
refs/tags/retired-20260915
|
1
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"b4b17ab8285db6991daf85e768f0252cbb1c9470","Message":"chore(reports): refresh final static evidence\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"hillao","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"hillao","Timestamp":"2026-09-04T19:15:26-07:00"},"CompareURL":"luoanwu/fact-backbone/compare/0000000000000000000000000000000000000000...b4b17ab8285db6991daf85e768f0252cbb1c9470","Len":0}...
|
1789541864
|
Edit
Delete
|
|
30315
|
5
|
9
|
5
|
106
|
0
|
0
|
refs/tags/retired-20260915
|
1
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"f978ade7e90469ee1a0a8992c1073d4275b00b51","Message":"docs: scope-snapshot-blueprint 把 DEC-001—005 从\"仍待裁决\"改为\"已裁定、权威 Resolver 未实现\"\n\n治理层 check-workspace-consistency L10 最后一条命中:DEC-001—005 已于 2026-09-12 批准,本文仍写作未决前置。\n改为\"卡在没做\"而不是\"卡在裁决\"(真源仓 runtime/modules/scope 仍 state=shape)。清扫后 L10 归零,工作区一致性 4 → 3 条。\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-15T05:53:28-07:00"},"CompareURL":"luoanwu/tenant-scope/compare/0000000000000000000000000000000000000000...f978ade7e90469ee1a0a8992c1073d4275b00b51","Len":0}...
|
1789541865
|
Edit
Delete
|
|
30316
|
5
|
9
|
5
|
108
|
0
|
0
|
refs/tags/retired-20260915
|
1
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"fa567527d297679347044b92de17fb137023d3c4","Message":"chore(reports): refresh final static evidence\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"hillao","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"hillao","Timestamp":"2026-09-04T19:15:26-07:00"},"CompareURL":"luoanwu/permission-platform/compare/0000000000000000000000000000000000000000...fa567527d297679347044b92de17fb137023d3c4","Len":0}...
|
1789541869
|
Edit
Delete
|
|
30320
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"82dbfa466 {"Commits":[{"Sha1":"82dbfa4669a7ff239f4b58827dd4f5999738ea46","Message":"docs(governance): 退役目录已物理删除;CHG-008 README 链接修正\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T00:16:48-07:00"},{"Sha1":"c501adad7a1d918b9f3b4a8b971e52c5d3b466d2","Message":"chore(governance): 派生仓退役 14 个——Catalog 退役形态、retired 档、文档归档、CHG-003/006/008 证据改指\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T00:13:22-07:00"},{"Sha1":"bdf4a0495174cab16def1b947eda69a46eb5412a","Message":"docs(governance): 缺失梳理 M-10 / M-16 与 README 观测行按 OTel 产生端与 Grafana 仪表板落地回写\n\n- M-10 runtime 接 OTel SDK:已落(enterprise-platform df436c1),dev 常驻 runtime 已切镜像,Tempo / Loki / Prometheus 三处实测收到;\n 余项改写为指标租户 / 应用维度、Node 进程指标、Caddy / LiteLLM 两个产生端\n- M-16:SLO 面板已落(四份文件供给仪表板,58 条查询实测编译),没有产生端的 SLO 不建面板;告警规则与值班仍为零\n- README 六框表观测行:划掉\"没有一个产生端在发\",改写仍缺项\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T23:18:54-07:00"},{"Sha1":"5b1ccb397c4d6101592017e63feb54de975a3dbe","Message":"feat(governance): 工作区门禁 L11 FRAMEWORK_VERSION_DRIFT——目录级文档声明的框架版本必须等于仓内 package.json 且有 tag;缺失梳理补执行记录\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:53:50-07:00"},{"Sha1":"6b19bcd9889100b9e864507263204587e61e7dd2","Message":"docs(governance): 企业控制面缺失全面梳理(七层 34 条)、完整梳理 §0 补记、README 六框表补写四个权威模块的登记落后\n\n- 新增 企业控制面缺失全面梳理-2026-09-15:按运行 / 接线 / 登记 / 交付 / 收口 / 消费 / 安全七层,逐域对照能力表 138 条与横切 15 条,\n 34 条编号缺口按\"只差 Owner 一个动作 / 裁决已齐要写代码 / 要先裁决\"分组;本轮处置与三轮只读分析记在 §9\n- 完整梳理 §0 追加改口:12/12 镜像已 digest 固定、9 份契约无路由、22 条未合并分支、catalog:drift 只记录不阻断、证据新鲜度补登记后的新数字\n- README 六框表:身份与权限 / 观测与审计 / 事实与契约三行补写 Catalog 仍 candidate_e0 与进程内端口壳;开头加缺失梳理链接\n- 只提交本会话的三个文件;平台治理/基础/scripts 与 tests 下另一会话的改动不在本次提交内\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-15T05:53:24-07:00"}],"HeadCommit":{"Sha1":"82dbfa4669a7ff239f4b58827dd4f5999738ea46","Message":"docs(governance): 退役目录已物理删除;CHG-008 README 链接修正\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T00:16:48-07:00"},"CompareURL":"luoanwu/platform-governance/compare/553813dbe9541b78f89eca3151c117473b8444f4...82dbfa4669a7ff239f4b58827dd4f5999738ea46","Len":7}...
|
1789543223
|
Edit
Delete
|
|
30380
|
5
|
5
|
5
|
51
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"0f790bee5 {"Commits":[{"Sha1":"0f790bee5ab0fb5277c79c3667cf513fabd074b5","Message":"docs: platform-onboarding 里 DEC-003 的过期措辞——已于 2026-09-12 批准,不再写作待裁决\n\n治理层一致性门禁 L10(2026-09-16 起认「DEC-0xx 待裁决」)抓到;只改这一句。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:43:00-07:00"},{"Sha1":"ddd441aee810965b6657ae11882707cc1d5d7712","Message":"docs: 如实标注三处从未入库的引用\n\n工作区一致性门禁 L4 报出本仓三条悬空链接。核查 git 历史:三个目标\n**从未入过库**,不是被删除,因此无法恢复,只能如实标注。\n\n- README.md:深度体检会话的四份分析里,`项目深挖分析与完善建议` 与\n `项目进展分析` 在库,`项目全维度技术体检与完善建议` 与 `尤克特拉商业价值评估`\n 缺失——同一批文档漏提交了两份。两处改为不带链接的文件名并标注「未随仓提交」\n- COLIMA.md:正文让读者「安装 deploy/nginx/yggdrasil.conf」,而 deploy/ 目录\n 整个不存在且 .gitignore 并未排除它。照文档操作会直接卡住,标注「未随仓提交,\n 需自行准备」\n\n只做标注,不臆造内容:这三份文件该由持有它们的人补进来,标注是为了在补进来之前\n不再误导读者。L4 由 8 条降至 5 条(余下 5 条是嗨赞造意 2026-09-05 治理日志里的\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:59-07:00"}],"HeadCommit":{"Sha1":"0f790bee5ab0fb5277c79c3667cf513fabd074b5","Message":"docs: platform-onboarding 里 DEC-003 的过期措辞——已于 2026-09-12 批准,不再写作待裁决\n\n治理层一致性门禁 L10(2026-09-16 起认「DEC-0xx 待裁决」)抓到;只改这一句。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:43:00-07:00"},"CompareURL":"luoanwu/yggdrasil-local-life-tools/compare/fe40791d1aec2f0e2a6fa6826d26b210add5f8bd...0f790bee5ab0fb5277c79c3667cf513fabd074b5","Len":2}...
|
1789555496
|
Edit
Delete
|
|
30381
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"fce1694e3 {"Commits":[{"Sha1":"fce1694e3624325b36af65052cccc775189c96aa","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ 6a31052\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:44:43-07:00"},{"Sha1":"6a31052e5f6b709b400d275210b53f1057e6475c","Message":"feat(governance): 机密反向兜底门禁、一致性门禁 L13 与 L3/L10 扩面、统一入口 skipped 与恒定输出、测试报告改写临时目录、统一审计落盘;并行会话约定\n\n缺失梳理 §10.2 可直接执行项(记录见 平台治理缺失全面梳理 §12.1):\n- PG-18 check-tracked-secrets.mjs:规则取自根 .gitignore 机密段,18 仓 13375 份受跟踪文件 0 命中;登记为统一入口阻断位;输出不回显命中值\n- PG-17 L13 治理层数字声明(裁决数 / 平台项目数对活跃 Catalog,收纳表文件数对 git ls-files);L10 增「尚未裁决 / 待裁决」;L3 增旧根层名;开发计划梳理不再按历史豁免、platform-contracts 冻结副本按历史豁免;仓发现抽到 lib/workspace-repositories.mjs\n- PG-13 / 14 run-foundation-gates:skipped 显形(audit-foundation 出 FOUNDATION_GATES_SKIPPED)、sameAsPrevious / unchangedRuns / constantOutput(lib/gate-run-history.mjs)\n- PG-23 / 24 FOUNDATION_REPORT_DIR:pnpm test 写临时目录,受跟踪报告 mtime 不变(测试自证);audit-foundation 落盘 基础目录统一审计.latest.json 并带 provenance(pnpm run audit)\n- PG-13 五例就绪 SKIP 改为在合并提交父提交重建的基线上实跑(tests/helpers/pre-merge-formal-root.mjs);重建不成立→新发现 PG-41(冻结的 governance-linter.test.mjs 摘要不对应任何提交)\n- PG-34 .gitea/workflows/governance.yml(不阻断);PG-36 基础/CLAUDE.md 并行会话约定\n- 顺带:L3/L10 首轮抓到的过期措辞与旧根路径已改;时空事实流转/README.md 补登记落点;派生仓计数措辞;平台治理/README 收纳表按 ls-files 刷新\n\n治理层测试 339(333 过 / 0 失败 / 6 跳过);pnpm check 阻断性 8/8。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:44:27-07:00"},{"Sha1":"af23c76f6a51a0b03da9d4740d5a8cd1a5040e4d","Message":"chore(governance): 集中观测平台退役(CHG-009)——派生仓 retired 档 15 个、目录级文档归档、控制面与梳理文档回写\n\n- 派生仓状态.json:集中观测平台由 archived 移入 retired(tag 沿用 archived-20260910,bundle 在仓备份-2026-09-15),archived 档只剩应用群网关;note 注明现存派生仓 3 个\n- CHG-009 材料(README + platform-projects.delta.json):Owner 2026-09-16 裁决 G-6 密码学核验与采样不作阻塞,证据改指 Collector 配置 / check:otel / 蓝图(已应用到活跃 Catalog,enterprise-platform 仓另提交)\n- 目录级文档搬到 基础设施文档/docs/已退役平台/集中观测平台/(CLAUDE.md 改名 .archived)\n- 企业控制面/README、缺失梳理 M-27、完整梳理、移除路径 §9、覆盖度对照、同步计划等按 15 个已退役回写\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:44:27-07:00"}],"HeadCommit":{"Sha1":"fce1694e3624325b36af65052cccc775189c96aa","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ 6a31052\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:44:43-07:00"},"CompareURL":"luoanwu/platform-governance/compare/82dbfa4669a7ff239f4b58827dd4f5999738ea46...fce1694e3624325b36af65052cccc775189c96aa","Len":3}...
|
1789555527
|
Edit
Delete
|
|
30382
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"7c65e2971 {"Commits":[{"Sha1":"7c65e297197325ffa3480e1f21c6020ec85b66ff","Message":"chore(reports): caddy / catalog-drift / catalog-reconciliation / facts / migration-decs / module-imports 回绑 @ 8a70ce2\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:46:02-07:00"},{"Sha1":"8a70ce251ad8c44372efe329a49767acd7d19fa9","Message":"docs(contracts): 过期措辞——DEC-001 已于 2026-09-12 批准,不再写作尚未裁决;候选目录 README 的 CHG-004 材料路径改指 平台治理/doc\n\n治理层一致性门禁 2026-09-16 扩面(L10 认「尚未裁决」、L3 认旧根层名 企业应用/)抓到的两处。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:45:38-07:00"},{"Sha1":"aae84ad49a57dd91337b48182e4026df89374727","Message":"feat(governance): check:deployed——运行中 compose runtime 容器的镜像 id 对 reports/image-digest.json\n\n- governance/check-deployed-runtime.mjs + lib/deployed-runtime.mjs:按 com.docker.compose.project / service 标签找容器,比对期望镜像;最新源码无镜像时报 BUILT_IMAGE_SOURCE_BEHIND;默认只打印不写报告;docker 不可用 exit 2\n- 单测 governance/test/deployed-runtime.test.mjs 6 例;governance 全量 240/240\n- package.json 增 check:deployed(不入 pnpm check 串链);governance/README、能力表、runtime/CLAUDE.md 登记(运行面另算:dev 常驻容器需 df436c1 之后镜像重建才有 OTel 信号)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:45:38-07:00"},{"Sha1":"dc7f80341e6ffaf247ae7af0187dcf5f92087a5d","Message":"feat(contracts): CHG-009 集中观测平台退役——Catalog 证据改指采纳形态落点,telemetry-envelope 蓝图迁入\n\n- central-observability:directory=null + retirement 记录(retired_at 2026-09-16,tag archived-20260910,bundle 在仓备份-2026-09-15);证据由派生仓 base-framework 改为 stack/otel/collector.yaml、governance/otel-attributes.json、check-otel.mjs 及其测试与报告、docs/domain/telemetry-envelope-blueprint.md、覆盖度对照\n- implementation_state / evidence_level / blockers / code_truth 不动(采纳形态无本仓代码真源)\n- runbook 的观测原计划链接改指归档位置\n- Owner 2026-09-16 裁决:G-6 密码学核验与采样不作退役阻塞(材料:平台治理/doc/decisions/CHG-009-材料)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:45:38-07:00"},{"Sha1":"70573d83552f8e604ddbb91788e25636933518bd","Message":"docs: 审计蓝图 L10 豁免标记;能力表链接改指归档位置;回绑 catalog 两份报告\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T00:16:51-07:00"}],"HeadCommit":{"Sha1":"7c65e297197325ffa3480e1f21c6020ec85b66ff","Message":"chore(reports): caddy / catalog-drift / catalog-reconciliation / facts / migration-decs / module-imports 回绑 @ 8a70ce2\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T03:46:02-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/68cb0ab2c652fad74b929a1bd92b6c3b91aa1dc2...7c65e297197325ffa3480e1f21c6020ec85b66ff","Len":12}...
|
1789555567
|
Edit
Delete
|
|
30407
|
5
|
9
|
5
|
107
|
0
|
0
|
refs/tags/retired-20260916
|
1
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"5a638a9a615f513177534b4c8d7c9e3efbb949a7","Message":"chore(reports): refresh clean final static evidence\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"hillao","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"hillao","Timestamp":"2026-09-04T18:50:51-07:00"},"CompareURL":"luoanwu/delivery-platform/compare/0000000000000000000000000000000000000000...5a638a9a615f513177534b4c8d7c9e3efbb949a7","Len":0}...
|
1789560161
|
Edit
Delete
|
|
30440
|
5
|
9
|
5
|
102
|
0
|
0
|
refs/tags/retired-20260916
|
1
|
{"Commits":null,"HeadCommit":{" {"Commits":null,"HeadCommit":{"Sha1":"56cff29d5bebc4328cb8c76e88a5bab7ec60dcff","Message":"chore(reports): refresh clean final static evidence\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"hillao","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"hillao","Timestamp":"2026-09-04T18:50:51-07:00"},"CompareURL":"luoanwu/app-registry/compare/0000000000000000000000000000000000000000...56cff29d5bebc4328cb8c76e88a5bab7ec60dcff","Len":0}...
|
1789561019
|
Edit
Delete
|
|
30441
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"975091270 {"Commits":[{"Sha1":"975091270ad2bdd234020c8ee9d6e2e7c8aff281","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ 80ed264\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:40:55-07:00"},{"Sha1":"80ed26441d4f74bb90d5c3eabc05191929f60cb9","Message":"feat(governance): 撤销四个候选平台(CHG-015)——审批记录 withdrawn 终态、候选门禁改读归档、控制面目录清空;第三轮执行记录\n\n- 目录负责人裁决撤销 企业搜索 / 外部连接器 / 数据治理与隐私 / 开发者自助 四个候选:M0 材料整体 git mv 到 基础设施文档/docs/已撤销候选/(50 文件),.gitignore 去掉四条放行\n- CHG-001 审批记录 merged → withdrawn(保留 merge 块,新增 withdrawal 块,冻结物一字未动);就绪检查器增第二终态:merge 块允许、withdrawal 块必需可核验、expectedFormalWithdrawn(21 / 19 / 36 / 0 pending、四项不在册、四条 DEC rejected)、--assert-settled 视 WITHDRAWN 已定\n- lib/workspace.mjs 新增 candidateWithdrawal / candidatePlatformRoot / candidatePlatformDir:契约兼容基线、M0 契约验证、12 项消费者契约测试、devx 夹具改读归档目录;决策评审包门禁报撤销态退出 0;统一审计与 L5 不再把冻结候选清单当待登记项;统一审计 counts 增 rejected\n- 终态测试改为 merged / withdrawn 各自的负向断言;就绪终态用例接受 WITHDRAWN;评审包护栏按撤销态解析引用\n- 文档:基础/CLAUDE.md 口径改 21 个在册项目;基础/README、企业控制面/README、待裁决 N-02 记撤销;裁决数 / 项目数声明与收纳表刷新;63 处链接改指归档位置(L4 = 0);已撤销候选/README 与 CHG-015 材料\n- 缺失梳理 §12.2 第三轮执行记录;移除路径 §9 补记四仓全退;一致性门禁登记基线改为 3 条(L8 1 / L9 1 / L12 1)\n\n治理层测试 341(335 过 / 0 失败 / 6 跳过)。企业控制面/ 此后只剩 README 与真源仓。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:40:41-07:00"},{"Sha1":"551e33221dab86ea217c77009e985585d10cb431","Message":"chore(governance): 应用与契约注册中心退役(CHG-014)——18 个派生仓全部退役,active / archived 档清空\n\n- 派生仓 HEAD 56cff29 打 retired-20260916 推 Gitea;bundle 仓备份-2026-09-16/控制面__应用与契约注册中心.bundle;四份目录级文档(含只在磁盘的 开发经验.md)搬入 已退役平台/应用与契约注册中心/;目录停放待 Owner rm\n- 派生仓状态:active → retired(18),四档合计仍 19(missing 1 + retired 18);三道按 active + archived 读盘的门禁 0/0,登记表 note / reason 改写;workspace-evidence-status 测试改为 expected 0 时发现数也须为 0\n- 企业控制面/README 铁律段、四档表、派生仓段与 基础/CLAUDE.md 修订按\"全部退役\"回写;已退役平台/README 加行;四份活文档链接改指归档位置;收纳表计数刷新\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:26:08-07:00"},{"Sha1":"ea86f2e16d8c34f645feeef170b3dee4e9ac92fb","Message":"test(governance): 扫描面仓数门槛按 2026-09-16 退役后的嵌套仓数下调\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:16:54-07:00"},{"Sha1":"dc1e3065f2b0482ad006780cc61e69fbeedb0e92","Message":"chore(governance): 统一交付平台退役(CHG-012)——两处部分覆盖由真源仓 check-promotion R11 / R12 关闭后退\n\n- 派生仓 HEAD 5a638a9 打 retired-20260916 推 Gitea;bundle 仓备份-2026-09-16/控制面__统一交付平台.bundle;目录级文档搬入 已退役平台/统一交付平台/(链接按新位置改写);目录停放待 Owner rm\n- 派生仓状态:active → retired(17),现存派生仓 1 个;企业控制面/README 四档表与派生仓段、已退役平台/README、覆盖度对照 §3 两行改 ✅ + §4 结论行 + §5.2 关闭 + §5.5 说明\n- 四份活文档指向交付目录的链接改指归档位置;收纳表计数刷新\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:12:31-07:00"}],"HeadCommit":{"Sha1":"975091270ad2bdd234020c8ee9d6e2e7c8aff281","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ 80ed264\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:40:55-07:00"},"CompareURL":"luoanwu/platform-governance/compare/fce1694e3624325b36af65052cccc775189c96aa...975091270ad2bdd234020c8ee9d6e2e7c8aff281","Len":9}...
|
1789562459
|
Edit
Delete
|
|
30442
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1c3ee58f9 {"Commits":[{"Sha1":"1c3ee58f99ad51cb9f2399bdc4097b19844bd949","Message":"chore(reports): caddy / catalog-drift / catalog-reconciliation / facts / migration-decs / module-imports 回绑 @ 2fe61f8\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:41:05-07:00"},{"Sha1":"2fe61f8548fb94111deb251c440c6a519ba8faca","Message":"feat(contracts): CHG-015 撤销四个候选平台——Catalog 移除四项(25 → 21),DEC-033—036 记 rejected 并改指归档草案\n\n- 目录负责人 2026-09-16 裁决撤销 enterprise-search / external-integration-connectors / data-governance-privacy / developer-self-service 的候选资格;M0 材料归档到 平台治理/基础设施文档/docs/已撤销候选/\n- 36 条裁决:32 approved / 4 rejected / 0 pending;linter 测试计数 21 / 19 / 0 pending,候选用例改为\"撤销后不在册、DEC rejected\",目录探针改为确定性临时目录,缺目录探针改用 数字员工OS\n- 能力表四条候选链接改指归档位置\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:40:06-07:00"},{"Sha1":"6bf637145cd4aca839a07f049e43385c54542db4","Message":"feat(contracts): CHG-014 应用与契约注册中心退役——directory=null + retirement(证据与 code_truth 已由 CHG-013 指向 contracts/src/domain)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:26:08-07:00"},{"Sha1":"aea93ffc52e433883d6ed0cff3c54f023d638275","Message":"test(contracts): linter 负例夹具不再钉在已退役的网关条目上——用任一有目录的条目 / 复活的退役条目\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:16:54-07:00"},{"Sha1":"8bd5b3751412bc81c3befafefe8e413f10ec8085","Message":"feat(governance): check-promotion R11 源提交交叉断言 + R12 迁移就绪——关掉统一交付平台的两处部分覆盖;CHG-012 交付退役\n\n- R11:staging/prod 记录 manifest.sourceSha = Manifest sourceSha = 制品 images.runtime.sourceSha,均 40 位(迁自 FULL_SOURCE_COMMIT_REQUIRED / ARTIFACT_SOURCE_MISMATCH)\n- R12:Manifest 迁移目录计数 \u003e 0 时记录须带 migrations 段(expand_migrate_contract / ready / backwardCompatible / rollbackEvidence;迁自 MIGRATION_*);schema 新增可选段、模板同步、README 规则清单补记;负向测试各一例(promotion 34 例)\n- Catalog delivery-platform:directory=null + retirement(tag retired-20260916 已推 Gitea),证据改指 release-manifest / check-promotion / verify-candidate / promotion schema / 迁入蓝图 / 治理层 ci-gate-audit 副本 / 覆盖度对照\n- delivery-control 蓝图自派生仓迁入 docs/domain/(L10 迁入豁免);能力表链接改指归档位置\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:12:31-07:00"}],"HeadCommit":{"Sha1":"1c3ee58f99ad51cb9f2399bdc4097b19844bd949","Message":"chore(reports): caddy / catalog-drift / catalog-reconciliation / facts / migration-decs / module-imports 回绑 @ 2fe61f8\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T05:41:05-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/7c65e297197325ffa3480e1f21c6020ec85b66ff...1c3ee58f99ad51cb9f2399bdc4097b19844bd949","Len":9}...
|
1789562468
|
Edit
Delete
|
|
30443
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ff7d2f5f2 {"Commits":[{"Sha1":"ff7d2f5f21e82dfae2a35ea0b09a14b075fdf6b3","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ abf3da1(三份均带 provenance)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:49:26-07:00"},{"Sha1":"abf3da1333775705216233cf7bc7b06eb5f202b7","Message":"feat(governance): reports 登记与归档(PG-20/21/22)、两道门禁补测试(PG-15)、同名文档订正(PG-32)\n\n- reports/登记.json:顶层 39 份受控报告逐份登记生产者 / 消费者 / 绑定 / 保留(latest 3 / evidence 35 / frozen 1);新门禁 check-report-registry.mjs(R1—R6)登记为统一入口阻断位,夹具 8 例\n- 223 份无人引用的报告(含 67 份 .log)按 9 个家族 git mv 到 reports/archive/2026-09-16/,顶层 262 → 39;.gitignore 不再收新 .log\n- run-foundation-gates / check-gate-consumption 的报告带 provenance(lib/report-provenance.mjs,忽略自身 latest 报告判脏)\n- check-idp-token-contract 增 --fixture、audit-platform-openings 增 DERIVED_STATUS_PATH(只供测试注入),各补正向 + 负向用例(翻转夹具 / 注入幽灵仓即红)\n- 两份《业务发展视角的基础设施与公用应用缺失》是同名不同文:文首互指,基础设施文档/README 迁入登记订正\n- 缺失梳理 §12.3 第四轮记录、§10.2 划掉;基础/README 工具清单;收纳表计数刷新\n\n治理层测试 354(348 过 / 0 失败 / 6 跳过);一致性门禁基线 3 条不变。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:49:12-07:00"}],"HeadCommit":{"Sha1":"ff7d2f5f21e82dfae2a35ea0b09a14b075fdf6b3","Message":"chore(reports): 门禁运行 / 门禁消费 / 基础目录统一审计 回绑 @ abf3da1(三份均带 provenance)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:49:26-07:00"},"CompareURL":"luoanwu/platform-governance/compare/975091270ad2bdd234020c8ee9d6e2e7c8aff281...ff7d2f5f21e82dfae2a35ea0b09a14b075fdf6b3","Len":2}...
|
1789570170
|
Edit
Delete
|
|
30444
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6fa036457 {"Commits":[{"Sha1":"6fa03645749413cddbd7752401d55a1cbb7400b7","Message":"docs: 能力表 v1.3 勘误——21 项目、候选撤销、派生仓全退、PF-04 阶段 2、R11/R12、观测产生端、OpenBao 仍注释(2026-09-16)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:49:32-07:00"}],"HeadCommit":{"Sha1":"6fa03645749413cddbd7752401d55a1cbb7400b7","Message":"docs: 能力表 v1.3 勘误——21 项目、候选撤销、派生仓全退、PF-04 阶段 2、R11/R12、观测产生端、OpenBao 仍注释(2026-09-16)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:49:32-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/1c3ee58f99ad51cb9f2399bdc4097b19844bd949...6fa03645749413cddbd7752401d55a1cbb7400b7","Len":1}...
|
1789570177
|
Edit
Delete
|
|
30445
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ecc77d987 {"Commits":[{"Sha1":"ecc77d987dbd2cfd9e00a3655fdd68efcd994bcc","Message":"chore(reports): 回绑 @ ff7d2f5——登记门禁读到带 provenance 的上一份报告后 9/9 通过\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:50:27-07:00"}],"HeadCommit":{"Sha1":"ecc77d987dbd2cfd9e00a3655fdd68efcd994bcc","Message":"chore(reports): 回绑 @ ff7d2f5——登记门禁读到带 provenance 的上一份报告后 9/9 通过\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T07:50:27-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ff7d2f5f21e82dfae2a35ea0b09a14b075fdf6b3...ecc77d987dbd2cfd9e00a3655fdd68efcd994bcc","Len":1}...
|
1789570230
|
Edit
Delete
|
|
30446
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"466bca265 {"Commits":[{"Sha1":"466bca265185d740d4a71432dc93e823797c39b7","Message":"chore(reports): 门禁回绑 @ e9ede64——根链 12 道绿、runtime 静态门禁除 F8 外全绿、端口一致性 passed、evidence 32 份新鲜\n\n在 clean HEAD e9ede64 上重跑:check:pins / modules / module-imports / catalog / catalog:drift(drift 4,与登记面缺口一致)/ fixtures(17 套件 166 例)/ facts / migration-decs(40 迁移含新增 202609160001)/ caddy(2 profile,docker 语法均 passed)/ otel(8 条告警规则,promtool passed)/ governance 测试 283 例 / contracts check:local;runtime:naming / schema / validation / contract-consumers / conformance-matrix / dual-backend / write-guard / migrations / governance-docs / docs-truth / governance-rules / agent-adapters / lint / typecheck 全绿;check:port-conformance passed;check:evidence 32 份新鲜、7 条 warn(runtime / ui / identity / mainline 五类需隔离底座重跑的验收)。\n\n仍红的一条与本轮无关:runtime check:fork-readiness F8(迁移技能指纹与 docs/migration-playbook.md 不符,09-15 348499d 已暴露),由此 check:governance 记指标回退 forkReadinessViolations 0 → 1;修复要重跑迁移记录器(record-migration),留给框架同步技能处理。fork-readiness / governance 两份报告如实记 failed,不以旧绿盘代替。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:11:20-07:00"},{"Sha1":"e9ede64815ee1db69c6ed153179f842d825272bc","Message":"docs: 基础设施对抗性验收记录 2026-09-16(并行会话产出,按原样收入)\n\n对 HEAD 6fa0364 的独立对抗性验收记录,由另一会话写入工作树(08:17,此后无改动);本提交只收入文档,不改其结论。其复跑的 fixtures / otel 两份报告随后续 chore(reports) 在新 HEAD 上重跑覆盖。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:07:49-07:00"},{"Sha1":"2ba41a95b25cacf74f1c501a6ee73567091d27e7","Message":"feat(runtime,stack,governance): 缺口代码 W-1…W-5——fact 意图账本端口、audit chain-verify 作业、持久化开关、告警规则门禁、staging TLS profile\n\n- fact:新迁移 202609160001_fact_export_intent(意图账本 platform_fact_export_intent,FORCE RLS,头引 DEC-010 / 012 / 013—016 / 032);FactStore.declareIntent / intent,accept 核对意图(producer / 类型 / 实体 / 载荷摘要)并标 fulfilled;FactExportPort 按 PLATFORM_PERSISTENCE_ENABLED 在 fact-ledger 与 fact-shape 间切换,缺 DATABASE_URL_FACT 即拒绝装配\n- audit:chain-verify 作业真实处理器(逐租户验哈希链 + 仓外 checkpoint;未开持久化 / 缺库 URL / 入参非法 / 非 canonical 租户终态拒绝,账本不可达交内核重试,验证结果为返回值 + error 日志)\n- stack:runtime 声明 PLATFORM_PERSISTENCE_ENABLED=1;Prometheus rule_files + otel/rules/platform.rules.yaml(8 条,只对实测存在的指标写规则);Caddyfile.staging({$PLATFORM_PUBLIC_HOST} 站点、tls {$PLATFORM_TLS_ISSUER}、HSTS,无 :80 明文站点)与 staging overlay 覆盖挂载、:? 强制两个变量\n- governance:check-otel 增告警规则 7 条判定与 promtool 校验(CHECK_OTEL_DOCKER=1 用 compose 锁定镜像);check-caddy 逐 profile 校验 + 5 条 TLS 规则(docker validate 按 validateEnv 注入占位);登记真源 otel-attributes.json alerts 段(含 6 项缺产生端的 pending)、caddy-routes.json profiles 段;evidence-scopes 纳入 Caddyfile.staging 与规则文件\n- docs:缺失模块完善清单-2026-09-16(逐模块文件级缺口、PR 映射、§8 本轮处置)、runbook §3 / §9、staging 晋级说明、收口方案状态行、governance / stack README\n\n验证(本机):fact 单测 48 + 隔离 PG 集成 6;audit 单测 45 + 隔离 PG 集成 4;runtime 端口套件 41;governance caddy / otel / evidence 测试 46;check:caddy docker 语法两份 passed;check:otel promtool passed;migration-decs / modules / module-imports / pins 0 违规;api-nestjs 与两模块 typecheck 通过。dev 底座已应用新迁移并按本配置重建 runtime / prometheus 容器(镜像仍为 df436c1,本提交的代码待 image:build)。报告不随本提交回绑,见后续 chore(reports)。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:07:49-07:00"}],"HeadCommit":{"Sha1":"466bca265185d740d4a71432dc93e823797c39b7","Message":"chore(reports): 门禁回绑 @ e9ede64——根链 12 道绿、runtime 静态门禁除 F8 外全绿、端口一致性 passed、evidence 32 份新鲜\n\n在 clean HEAD e9ede64 上重跑:check:pins / modules / module-imports / catalog / catalog:drift(drift 4,与登记面缺口一致)/ fixtures(17 套件 166 例)/ facts / migration-decs(40 迁移含新增 202609160001)/ caddy(2 profile,docker 语法均 passed)/ otel(8 条告警规则,promtool passed)/ governance 测试 283 例 / contracts check:local;runtime:naming / schema / validation / contract-consumers / conformance-matrix / dual-backend / write-guard / migrations / governance-docs / docs-truth / governance-rules / agent-adapters / lint / typecheck 全绿;check:port-conformance passed;check:evidence 32 份新鲜、7 条 warn(runtime / ui / identity / mainline 五类需隔离底座重跑的验收)。\n\n仍红的一条与本轮无关:runtime check:fork-readiness F8(迁移技能指纹与 docs/migration-playbook.md 不符,09-15 348499d 已暴露),由此 check:governance 记指标回退 forkReadinessViolations 0 → 1;修复要重跑迁移记录器(record-migration),留给框架同步技能处理。fork-readiness / governance 两份报告如实记 failed,不以旧绿盘代替。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:11:20-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/6fa03645749413cddbd7752401d55a1cbb7400b7...466bca265185d740d4a71432dc93e823797c39b7","Len":3}...
|
1789601218
|
Edit
Delete
|
|
30447
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"c64115148 {"Commits":[{"Sha1":"c641151481665a321840ee8081e09101a3b74360","Message":"docs(决策): 决策批次 2026-09-16——31 项待裁事项一次签署并登记\n\n目录负责人经会话逐条签署:A 批 7 条登记与收口全部批准(CHG-007、CHG-002 → 003 → 006、CHG-001 追认、审批记录终态 merged、门禁脚本按 SHA 引用、permissions.json 离开 draft、CHG-004 阶段 2 分两批);B 批:单人代签长期化、CI 通道 B 案、19 个 PR 按登记顺序合并、Catalog 保持 proposed 到 staging 晋级;C 批:Q01—Q10 按收口方案采纳,X06 由 identity 作业编排,G-3 自建限流镜像、方法白名单回收入口层,prod 批准人必须 human,drift 升阻断,碰撞卷 dump 后删,内核一步升 0.22.0,订阅计费并入 C19,OpenBao dev 立即启用,OS 先接决策 API,嗨设允许自建,Alertmanager + 企业 IM;D 批:staging TLS 先 internal 再 ACME,§6 偏差六条按建议。五处改案及后果见批次 §1A。\n\n登记:待裁决架构事项 CHG-001 / N-02 / N-07 三行改为已裁决;开发计划 §8 新增变更记录(偏差 #5 / #23 / #31 随之关闭)。未做:DEC-010 附条件修订与 C19 范围改写各需一个 CHG。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:08:02-07:00"}],"HeadCommit":{"Sha1":"c641151481665a321840ee8081e09101a3b74360","Message":"docs(决策): 决策批次 2026-09-16——31 项待裁事项一次签署并登记\n\n目录负责人经会话逐条签署:A 批 7 条登记与收口全部批准(CHG-007、CHG-002 → 003 → 006、CHG-001 追认、审批记录终态 merged、门禁脚本按 SHA 引用、permissions.json 离开 draft、CHG-004 阶段 2 分两批);B 批:单人代签长期化、CI 通道 B 案、19 个 PR 按登记顺序合并、Catalog 保持 proposed 到 staging 晋级;C 批:Q01—Q10 按收口方案采纳,X06 由 identity 作业编排,G-3 自建限流镜像、方法白名单回收入口层,prod 批准人必须 human,drift 升阻断,碰撞卷 dump 后删,内核一步升 0.22.0,订阅计费并入 C19,OpenBao dev 立即启用,OS 先接决策 API,嗨设允许自建,Alertmanager + 企业 IM;D 批:staging TLS 先 internal 再 ACME,§6 偏差六条按建议。五处改案及后果见批次 §1A。\n\n登记:待裁决架构事项 CHG-001 / N-02 / N-07 三行改为已裁决;开发计划 §8 新增变更记录(偏差 #5 / #23 / #31 随之关闭)。未做:DEC-010 附条件修订与 C19 范围改写各需一个 CHG。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:08:02-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ecc77d987dbd2cfd9e00a3655fdd68efcd994bcc...c641151481665a321840ee8081e09101a3b74360","Len":1}...
|
1789601223
|
Edit
Delete
|
|
30448
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"21e845a4b {"Commits":[{"Sha1":"21e845a4b34a2e5c8f15a9993c541a08e3b01389","Message":"chore(reports): 重签迁移记录关闭 F8,并回绑 fork-readiness / governance @ 466bca2\n\nF8 的根因是 docs/migration-playbook.md 在 2026-09-14 目录迁移后修了 48 条相对链接(edb5218),迁移技能指纹随之变化而记录未重签(348499d 已暴露)。本次用迁移技能唯一入口 pnpm migration:record 重签:mode 仍为 bootstrap(与 09-10 原记录同模式,不是新的迁移),源钉在框架 v0.16.1 tag 的临时 worktree(与 runtime 当前 pin 一致,签完即移除),目标为本仓 runtime@466bca2 clean。未迁入任何代码。\n\n结果:check:fork-readiness 通过;check:governance 的 forkReadinessViolations 回到 0,指标回退消失;根 check:evidence 32 份新鲜、7 条 warn 不变(需隔离底座重跑的验收类报告)。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:28:33-07:00"}],"HeadCommit":{"Sha1":"21e845a4b34a2e5c8f15a9993c541a08e3b01389","Message":"chore(reports): 重签迁移记录关闭 F8,并回绑 fork-readiness / governance @ 466bca2\n\nF8 的根因是 docs/migration-playbook.md 在 2026-09-14 目录迁移后修了 48 条相对链接(edb5218),迁移技能指纹随之变化而记录未重签(348499d 已暴露)。本次用迁移技能唯一入口 pnpm migration:record 重签:mode 仍为 bootstrap(与 09-10 原记录同模式,不是新的迁移),源钉在框架 v0.16.1 tag 的临时 worktree(与 runtime 当前 pin 一致,签完即移除),目标为本仓 runtime@466bca2 clean。未迁入任何代码。\n\n结果:check:fork-readiness 通过;check:governance 的 forkReadinessViolations 回到 0,指标回退消失;根 check:evidence 32 份新鲜、7 条 warn 不变(需隔离底座重跑的验收类报告)。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:28:33-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/466bca265185d740d4a71432dc93e823797c39b7...21e845a4b34a2e5c8f15a9993c541a08e3b01389","Len":1}...
|
1789601317
|
Edit
Delete
|
|
30449
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"101380fb8 {"Commits":[{"Sha1":"101380fb8b7d4c8b1095d7f3a53cb6df5251a58f","Message":"docs(决策): CHG-016 / CHG-017 材料——DEC-010 附条件修订、C19 范围改写(待签署后应用)\n\n决策批次 2026-09-16 五处改案带出的两个受控变更:\n- CHG-016:DEC-010 批准记录附条件修订——Required Check 证据来源改 Gitea(B-2)、CODEOWNERS 实名不再作前置(B-1 长期代签,附代签 SOP 原文)、proposed → active 判据改为首次 staging 晋级记录(B-4);decisions.delta.json 只加 note 不改 status。\n- CHG-017:成本与容量治理平台范围并入外部客户订阅计量与出账(C-15),能力表 C19 增 C19.07 / C19.08、C02.01 扩外部客户开户路径、边界表与机器读者处置;不改活跃 Catalog,不建服务。\n批次记录 §3 登记行同步。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:29:59-07:00"}],"HeadCommit":{"Sha1":"101380fb8b7d4c8b1095d7f3a53cb6df5251a58f","Message":"docs(决策): CHG-016 / CHG-017 材料——DEC-010 附条件修订、C19 范围改写(待签署后应用)\n\n决策批次 2026-09-16 五处改案带出的两个受控变更:\n- CHG-016:DEC-010 批准记录附条件修订——Required Check 证据来源改 Gitea(B-2)、CODEOWNERS 实名不再作前置(B-1 长期代签,附代签 SOP 原文)、proposed → active 判据改为首次 staging 晋级记录(B-4);decisions.delta.json 只加 note 不改 status。\n- CHG-017:成本与容量治理平台范围并入外部客户订阅计量与出账(C-15),能力表 C19 增 C19.07 / C19.08、C02.01 扩外部客户开户路径、边界表与机器读者处置;不改活跃 Catalog,不建服务。\n批次记录 §3 登记行同步。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:29:59-07:00"},"CompareURL":"luoanwu/platform-governance/compare/c641151481665a321840ee8081e09101a3b74360...101380fb8b7d4c8b1095d7f3a53cb6df5251a58f","Len":1}...
|
1789601402
|
Edit
Delete
|
|
30450
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ff384b37a {"Commits":[{"Sha1":"ff384b37ad09b2677bdad44ee2da86ae3a2386bd","Message":"chore(reports): 镜像 21e845a4b34a 构建 / 冒烟 6 项 / dev 常驻切换记录 @ 21e845a\n\n- reports/image-digest.json:enterprise-platform/runtime:21e845a4b34a(image id d914de82…,linux/arm64,184 MB,sourceSha 21e845a clean;本机 --load,registryDigest=null)\n- reports/image-smoke.latest.json:六项全过(容器起、/api/health 200、模块视图、scope 模块 /health 200、无凭证决策 401、HEALTHCHECK healthy;单 profile,53002 端口,env 只列变量名)\n- stack/reports/runtime-up.2026-09-16-persistence.json:dev 常驻 runtime 切到该镜像,PLATFORM_PERSISTENCE_ENABLED=1,启动日志 FactExportPort←fact(fact-ledger)、PermissionDecisionPort←permission(permission-ledger),audit.chain_verify 注册;直连与经 Caddy 探活 200,无凭证决策 401;check:deployed passed;仓外 env 的 PLATFORM_RUNTIME_IMAGE 已改指该镜像\n- 缺失模块完善清单 §8 ③ 标为已做\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:34:11-07:00"}],"HeadCommit":{"Sha1":"ff384b37ad09b2677bdad44ee2da86ae3a2386bd","Message":"chore(reports): 镜像 21e845a4b34a 构建 / 冒烟 6 项 / dev 常驻切换记录 @ 21e845a\n\n- reports/image-digest.json:enterprise-platform/runtime:21e845a4b34a(image id d914de82…,linux/arm64,184 MB,sourceSha 21e845a clean;本机 --load,registryDigest=null)\n- reports/image-smoke.latest.json:六项全过(容器起、/api/health 200、模块视图、scope 模块 /health 200、无凭证决策 401、HEALTHCHECK healthy;单 profile,53002 端口,env 只列变量名)\n- stack/reports/runtime-up.2026-09-16-persistence.json:dev 常驻 runtime 切到该镜像,PLATFORM_PERSISTENCE_ENABLED=1,启动日志 FactExportPort←fact(fact-ledger)、PermissionDecisionPort←permission(permission-ledger),audit.chain_verify 注册;直连与经 Caddy 探活 200,无凭证决策 401;check:deployed passed;仓外 env 的 PLATFORM_RUNTIME_IMAGE 已改指该镜像\n- 缺失模块完善清单 §8 ③ 标为已做\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:34:11-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/21e845a4b34a2e5c8f15a9993c541a08e3b01389...ff384b37ad09b2677bdad44ee2da86ae3a2386bd","Len":1}...
|
1789601655
|
Edit
Delete
|
|
30451
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"784e72397 {"Commits":[{"Sha1":"784e723973b9e1e6e44c2b87cffb8f2a7cd545c1","Message":"docs: CLAUDE.md 补「开发命令与仓结构」(并行会话产出,按原样收入)\n\n三个 pnpm 根与安装顺序、门禁链单跑命令、单测 / 集成 / 端口一致性入口、四个交付面与过渡区、runtime 装载拓扑、模块解剖、隔离门禁、contracts 与 stack 对照、证据与提交顺序、项目内技能与代理。由另一会话于 2026-09-16 16:32 写入工作树,本提交只收入文档。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:37:19-07:00"}],"HeadCommit":{"Sha1":"784e723973b9e1e6e44c2b87cffb8f2a7cd545c1","Message":"docs: CLAUDE.md 补「开发命令与仓结构」(并行会话产出,按原样收入)\n\n三个 pnpm 根与安装顺序、门禁链单跑命令、单测 / 集成 / 端口一致性入口、四个交付面与过渡区、runtime 装载拓扑、模块解剖、隔离门禁、contracts 与 stack 对照、证据与提交顺序、项目内技能与代理。由另一会话于 2026-09-16 16:32 写入工作树,本提交只收入文档。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:37:19-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/ff384b37ad09b2677bdad44ee2da86ae3a2386bd...784e723973b9e1e6e44c2b87cffb8f2a7cd545c1","Len":1}...
|
1789601842
|
Edit
Delete
|
|
30452
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"631820930 {"Commits":[{"Sha1":"631820930fa53485f2aecebf20f3be971e28badc","Message":"docs(企业控制面): 目录级 CLAUDE.md(并行会话产出,按原样收入)\n\n目录定位(基础设施层物理目录,只剩真源仓)、两个 git 仓的边界与远端、命令入口指向真源仓、四级文档层级、状态措辞纪律。由另一会话于 2026-09-16 16:31 写入工作树;治理层一致性门禁 root scope L4 / L10 零命中。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:38:09-07:00"}],"HeadCommit":{"Sha1":"631820930fa53485f2aecebf20f3be971e28badc","Message":"docs(企业控制面): 目录级 CLAUDE.md(并行会话产出,按原样收入)\n\n目录定位(基础设施层物理目录,只剩真源仓)、两个 git 仓的边界与远端、命令入口指向真源仓、四级文档层级、状态措辞纪律。由另一会话于 2026-09-16 16:31 写入工作树;治理层一致性门禁 root scope L4 / L10 零命中。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:38:09-07:00"},"CompareURL":"luoanwu/platform-governance/compare/101380fb8b7d4c8b1095d7f3a53cb6df5251a58f...631820930fa53485f2aecebf20f3be971e28badc","Len":1}...
|
1789601891
|
Edit
Delete
|
|
30453
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ec19ba1b7 {"Commits":[{"Sha1":"ec19ba1b701730e2901aba160298111d06e8660c","Message":"feat(stack): runtime 传入身份模块 dev 运行配置(IDP_* 四变量)——dev 首租户 bootstrap,托管登录页首次带真实事务渲染(缺失清单 I-7)\n\n- compose runtime 服务新增 IDP_CANONICAL_ORIGIN / IDP_BOOTSTRAP_TOKEN / IDP_PUBLIC_JWKS_JSON / IDP_LOCAL_SIGNING_KEYS_JSON(值在仓外 .secrets;dev 本地 RSA 密钥,DEC-006 / 025 终态 OpenBao Transit)\n- dev:容器重建后用 bootstrap 接口建租户 demo、管理员与公开客户端 demo-console;authorize(S256)302 到带 transaction_id 的登录页并渲染表单;无事务与 plain challenge 均被拒;check:deployed passed\n- docs:runbook §2 补身份 dev 配置与 bootstrap / 授权步骤;缺失清单 §8.1 补记;stack/reports/runtime-up.2026-09-16-identity.json 记录(口令与密钥不入记录)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:57:49-07:00"}],"HeadCommit":{"Sha1":"ec19ba1b701730e2901aba160298111d06e8660c","Message":"feat(stack): runtime 传入身份模块 dev 运行配置(IDP_* 四变量)——dev 首租户 bootstrap,托管登录页首次带真实事务渲染(缺失清单 I-7)\n\n- compose runtime 服务新增 IDP_CANONICAL_ORIGIN / IDP_BOOTSTRAP_TOKEN / IDP_PUBLIC_JWKS_JSON / IDP_LOCAL_SIGNING_KEYS_JSON(值在仓外 .secrets;dev 本地 RSA 密钥,DEC-006 / 025 终态 OpenBao Transit)\n- dev:容器重建后用 bootstrap 接口建租户 demo、管理员与公开客户端 demo-console;authorize(S256)302 到带 transaction_id 的登录页并渲染表单;无事务与 plain challenge 均被拒;check:deployed passed\n- docs:runbook §2 补身份 dev 配置与 bootstrap / 授权步骤;缺失清单 §8.1 补记;stack/reports/runtime-up.2026-09-16-identity.json 记录(口令与密钥不入记录)\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T16:57:49-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/784e723973b9e1e6e44c2b87cffb8f2a7cd545c1...ec19ba1b701730e2901aba160298111d06e8660c","Len":1}...
|
1789603073
|
Edit
Delete
|
|
30454
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ec29ace2d {"Commits":[{"Sha1":"ec29ace2dc8f4e3e51b716c3bb673b741f85b47f","Message":"docs(identity): 托管登录端到端首次走通记录——PKCE 换令牌 / JWKS 验签 / userinfo / 重放与篡改拒绝(缺失清单 I-7)\n\n- stack/reports/identity-oidc-e2e.2026-09-16.json:authorize → 登录(人工)→ 同意 → 回调码 → 换令牌 200(RS256 kid dev-20260916,iss http://localhost:3098/t/demo,tenant_id / sid / acr / amr / nonce)→ JWKS 验签 valid → userinfo 200 → 重放 400 → 篡改 401 → introspect 对 public client 401;授权码 60 s\n- 生产口径容器换令牌 503 属设计内(本地 JWK 签名器只允许 test / development;生产 = OpenBao Transit);演示用本机 development 口径 identity 单 profile 进程(:3101),常驻容器不动\n- 踩坑登记:bash 加载含 JSON 的 env 会剥双引号 → discovery 503 / token 500;值须单引号\n- runbook §2 与缺失清单 §8.1 同步\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T17:09:55-07:00"}],"HeadCommit":{"Sha1":"ec29ace2dc8f4e3e51b716c3bb673b741f85b47f","Message":"docs(identity): 托管登录端到端首次走通记录——PKCE 换令牌 / JWKS 验签 / userinfo / 重放与篡改拒绝(缺失清单 I-7)\n\n- stack/reports/identity-oidc-e2e.2026-09-16.json:authorize → 登录(人工)→ 同意 → 回调码 → 换令牌 200(RS256 kid dev-20260916,iss http://localhost:3098/t/demo,tenant_id / sid / acr / amr / nonce)→ JWKS 验签 valid → userinfo 200 → 重放 400 → 篡改 401 → introspect 对 public client 401;授权码 60 s\n- 生产口径容器换令牌 503 属设计内(本地 JWK 签名器只允许 test / development;生产 = OpenBao Transit);演示用本机 development 口径 identity 单 profile 进程(:3101),常驻容器不动\n- 踩坑登记:bash 加载含 JSON 的 env 会剥双引号 → discovery 503 / token 500;值须单引号\n- runbook §2 与缺失清单 §8.1 同步\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-16T17:09:55-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/ec19ba1b701730e2901aba160298111d06e8660c...ec29ace2dc8f4e3e51b716c3bb673b741f85b47f","Len":1}...
|
1789603798
|
Edit
Delete
|