|
29979
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d10dae4ab {"Commits":[{"Sha1":"d10dae4ab5cf2e2f61c009033f00970b9a51c600","Message":"fix(governance): 门禁按 workspace.json 定位平台层,恢复迁移后失效的审计\n\n阶段 3 把平台目录从 基础/ 移到 企业控制面/ 之后,仍按 resolve(scriptDir,'..')\n推导的门禁全部失效:派生仓探测不到 git 仓(13/13 missing-git-repo)、平台发现\n数为 0、候选契约 ENOENT、audit-ci-gates 直接 ERR_MODULE_NOT_FOUND。冻结证据\n一直都在,只是脚本找错了路。\n\nlib/workspace.mjs 新增平台层解析器:\n- platformLayerRoot 取清单 layers.基础设施,platformDir / derivedRepo 据此展开\n (git 仓在 \u003c平台\u003e/base-framework,不在平台目录本身)\n- frameworkSourceRepo 取清单 paths.baseFramework\n- discoverPlatformNames 以「含 base-framework/ 子目录」为判据,宿主仓\n enterprise-platform、真源仓 企业IdP快照 与四个无派生仓的候选目录据此自动排除,\n 不再维护 excluded 目录名黑名单\n\n改接清单的脚本与测试:\n- workspace-evidence-status / audit-platform-openings / check-archived-derived-repos\n- audit-ci-gates 只改兼容入口传参——审计核心在 archived-20260910 冻结的\n 统一交付平台仓内,不可改\n- validate-new-platform-contracts、check-new-platform-contract-compatibility 与\n tests/new-platform-consumer-contracts:治理脚本与候选平台契约是两个基准,\n 原先共用一个变量,拆开\n- tests/helpers/devx-review-* 的 new URL 相对定位改走清单(pathname 对中文是\n 百分号编码,findWorkspaceRoot 认不出会回落到 cwd)\n\n验证:\n check-archived-derived-repos 13/13 冻结在 tag(原 0/13)\n audit-platform-openings 13/18 通过(原「应为 18,实际 0」)\n audit-ci-gates 18/18 结构通过,仅数量 19 vs 18(企业 IdP 已登记缺失)\n validate-new-platform-contracts 8 schemas / 19 accepted / 8 rejected\n check-new-platform-contract-compatibility 4 projects / 8 schemas / 19 types\n audit-foundation 恢复出具审计(原 exit 2 崩溃)\n tests/ 10/11 文件全绿\n\n余 new-platform-catalog-readiness 6 例失败,成因不是路径:阶段 4 改动了\nCHG-001 修订 6 的三个冻结输入,指纹失配,另行处理。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:52:14-07:00"},{"Sha1":"65c7ba829fdaa95b4373a4ced80246f6265b603c","Message":"feat(governance): 新增工作区一致性门禁,把迁移破坏类型固化成机器检查\n\n2026-09-14 迁移暴露的三类破坏都不在既有门禁视野里:判定逻辑按旧布局写死、\n冻结物摘要相符而内容过期、git worktree 两侧路径失联。新增 L1—L8 八项检查:\n\n L1 清单 layers/paths 声明的目录必须存在\n L2 `X/X/` 二次替换(替换脚本跑了两遍的痕迹)\n L3 旧层名残留(历史记录文件豁免)\n L4 受控 Markdown 本地链接可解析\n L5 Catalog / 候选清单登记路径可解析\n L6 worktree 两侧 gitdir 互指\n L7 冻结物摘要与磁盘内容一致\n L8 摘要相符但内容仍是旧布局 —— 本轮真正咬人的一类\n\n纯判定逻辑拆入 lib/workspace-consistency-core.mjs,7 个夹具用例覆盖正反向,\n其中一例直接锁住 L8 的教训:冻结 patch 摘要完好、内容仍写 `基础/\u003c平台\u003e`。\n门禁只读,不写任何文件;退出码 0/1/2。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:51:09-07:00"},{"Sha1":"f29bbbbeb8371825387d9437b91291af58f075d9","Message":"fix(governance): 基础审计改以清单定位基础设施层\n\n阶段 3 把 19 个平台仓从 基础/ 移入 企业控制面/,但 audit-foundation\n仍按 基础/ 的子目录枚举平台,且随后的机械替换把前缀改成了 平台治理/基础/\n——方向相反:那里只剩治理脚本与文档,平台一个也发现不了,\nclassifyDirectories 遂以 Invalid candidate directory 抛错,整条门禁跑不起来。\n\n- foundation-audit-core: 层前缀参数化(默认 企业控制面,可由调用方覆盖),\n 候选目录校验改用前缀比较而非硬编码正则;新增 externalDirectories,\n 使 工程基础框架 / 数字员工OS 这类跨层登记项不再被误判 missing-directory\n- audit-foundation: 平台层、框架真源仓与 OS 仓改由 workspace.json 解析\n (platformLayerRoot / frameworkSourceRepo / workspacePath)。\n try 块内 workspace 被同名 const 遮蔽,故派生路径一律在顶层先解析以避开 TDZ\n- 测试前缀改正,并补两个用例:跨层登记项、层名可覆盖\n\n回归:foundation-audit 11 → 13 用例全绿;audit-foundation 恢复可执行,\n阻塞项 8 项与迁移前基线逐项一致,派生仓发现 18/18。\ncontracts test 104 pass、governance test 193 pass、contracts check 4 项已知,\n三者亦与基线相同。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:50:36-07:00"}],"HeadCommit":{"Sha1":"d10dae4ab5cf2e2f61c009033f00970b9a51c600","Message":"fix(governance): 门禁按 workspace.json 定位平台层,恢复迁移后失效的审计\n\n阶段 3 把平台目录从 基础/ 移到 企业控制面/ 之后,仍按 resolve(scriptDir,'..')\n推导的门禁全部失效:派生仓探测不到 git 仓(13/13 missing-git-repo)、平台发现\n数为 0、候选契约 ENOENT、audit-ci-gates 直接 ERR_MODULE_NOT_FOUND。冻结证据\n一直都在,只是脚本找错了路。\n\nlib/workspace.mjs 新增平台层解析器:\n- platformLayerRoot 取清单 layers.基础设施,platformDir / derivedRepo 据此展开\n (git 仓在 \u003c平台\u003e/base-framework,不在平台目录本身)\n- frameworkSourceRepo 取清单 paths.baseFramework\n- discoverPlatformNames 以「含 base-framework/ 子目录」为判据,宿主仓\n enterprise-platform、真源仓 企业IdP快照 与四个无派生仓的候选目录据此自动排除,\n 不再维护 excluded 目录名黑名单\n\n改接清单的脚本与测试:\n- workspace-evidence-status / audit-platform-openings / check-archived-derived-repos\n- audit-ci-gates 只改兼容入口传参——审计核心在 archived-20260910 冻结的\n 统一交付平台仓内,不可改\n- validate-new-platform-contracts、check-new-platform-contract-compatibility 与\n tests/new-platform-consumer-contracts:治理脚本与候选平台契约是两个基准,\n 原先共用一个变量,拆开\n- tests/helpers/devx-review-* 的 new URL 相对定位改走清单(pathname 对中文是\n 百分号编码,findWorkspaceRoot 认不出会回落到 cwd)\n\n验证:\n check-archived-derived-repos 13/13 冻结在 tag(原 0/13)\n audit-platform-openings 13/18 通过(原「应为 18,实际 0」)\n audit-ci-gates 18/18 结构通过,仅数量 19 vs 18(企业 IdP 已登记缺失)\n validate-new-platform-contracts 8 schemas / 19 accepted / 8 rejected\n check-new-platform-contract-compatibility 4 projects / 8 schemas / 19 types\n audit-foundation 恢复出具审计(原 exit 2 崩溃)\n tests/ 10/11 文件全绿\n\n余 new-platform-catalog-readiness 6 例失败,成因不是路径:阶段 4 改动了\nCHG-001 修订 6 的三个冻结输入,指纹失配,另行处理。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T21:52:14-07:00"},"CompareURL":"luoanwu/platform-governance/compare/98ec9e9e61a1efb0e49011c06c28f63377accc23...d10dae4ab5cf2e2f61c009033f00970b9a51c600","Len":3}...
|
1789447994
|
Edit
Delete
|
|
30051
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"615c017a3 {"Commits":[{"Sha1":"615c017a32da032ecaeb00215d8b8b5418d9b122","Message":"fix(governance): 收回 CHG-001 四项审批并关闭合并闸门,回执按 SOP 归档\n\n修订 7 的四项 APPROVED(2026-09-15T05:40:40Z)与变更窗口(05:40:30Z)建立在\n一个目标真源有问题的包上:CHG-001 整包钉在 平台治理/platform-contracts,而\nDEC-010 已批准的 A 案明写「独立 Git-first 真源由基础设施仓的 contracts/\n工作区承担」,平台治理/README.md 也把前者定性为「冻结待移除,阶段 2 物理移除」。\n\n按现状合并的后果(核对记录 3689711):四个候选会登记进一个待移除的副本,\n而 audit-foundation 读 paths.activeContracts,三项 Catalog 阻断\n(CANDIDATES_NOT_REGISTERED / FORMAL_CATALOG_CHECK_FAILED /\nCANDIDATE_CATALOG_GATE_BLOCKED)不会消除;修订 7 补丁对活跃真源\npatch --fuzz=0 --dry-run 时 test/governance-linter.test.mjs 4 个 hunk 失败 1 个。\n\n目录负责人决定改指活跃真源、重基线为修订 8。按审批录入 SOP §5「包指纹或\n冻结文件漂移 → 全部旧回执失效,重新冻结包并重新审批」,本次先收口人的决定:\n\n- 四份回执连同 archive-manifest 归档到\n reports/catalog-package-archive/6e2e69d6…/approvals-withdrawn/,\n 记明失效原因与「不得转移到修订 8」,approvals/ 清空\n- 审批记录回到审批前形态:四项 PENDING、approver/decidedAt/evidenceRef/\n receiptSha256 置空、changeWindow.scheduledAt 置空(owner 与 rollbackOwner\n 按门禁要求保留 Catalog Owner)、mergeGate.eligible=false、\n authorizations.catalogMutationAuthorized 由 true 回到 false\n- revisionNote 追加【2026-09-14 收回】段,写明依据与修订 8 的前置\n\n包内容未动:revision 仍为 7,指纹 6e2e69d6…a84ffa97f 不变。修订 8 的重基线\n须等活跃真源 contracts/ 工作树 clean(当前有 src/domain/ 九个域包等在途实现),\n否则冻结摘要会钉住半成品。\n\n验证:tests/new-platform-approval-recording 7/7 恢复(此前 4 例因审批落库而\n红——这些用例把正式审批记录当夹具读)。tests/new-platform-catalog-readiness\n仍有 6 例红,成因是并行会话在途把 simulate-new-platform-catalog-merge.mjs\n改指 activeContractsRoot 而修订 8 摘要尚未重算,不属本次变更。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:46:57-07:00"},{"Sha1":"8832e2257d0c10cbf5cec5516604e46f1ee2e922","Message":"docs(governance): 提交 CHG-001 目标真源裁决请求,并登记进待裁决索引\n\n四份回执已签、就绪门禁 READY,但合并目标钉在冻结副本 平台治理/platform-contracts/,\n而 DEC-010 批准的真源是 企业控制面/enterprise-platform/contracts/。裁决请求列出\n三个方案与各自代价,推荐 A(改指活跃真源、重基线修订 8),并说明为什么必须现在定:\n\n包指纹覆盖 formalBaselineDigests,改指即换指纹,四份回执随之全部失效;现在定最多\n作废 4 份,等 CHG-002—005 也按冻结副本验证完再定,作废的是整条链。\n\n支撑推荐的实测:仅活跃真源独有 26 个文件、仅冻结副本独有 0 个(冻结副本是内容上的\n真子集,测试 3 vs 17);catalogs 五份里只有 platform-projects.json 不同,差异正是活跃\n真源已补、冻结副本仍缺的 7 条 Fact 前置;完整补丁对活跃真源 dry-run 只有\ntest/governance-linter.test.mjs 的 1 个 hunk 需重渲染,其余三份干净可落。\n\n另附两个连带问题:冻结副本的去留,以及就绪门禁按 platformContracts 还是\nactiveContracts 读取。本文不自行选定,裁决写入 §6 后方可执行。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:45:21-07:00"},{"Sha1":"bd63d88dc431e4fd106e5ba45404114c460bd264","Message":"docs(governance): 订正核对文档中 CHG-001 的状态——并发提交已使其转 READY\n\n上一条提交(a140998,22:42:31)的 §8 写于 c571477(22:42:10)之前,相隔\n21 秒,因此把 CHG-001 记成「四方审批 PENDING + 变更窗口未排」。实跑现状为\nREADY:pending 0、blockingReasons 空、packageValid=true。\n\n订正三处:§8 对照表 CHG-001 行、check.mjs 行、以及「未做」清单中 4 条\nPLATFORM_PROJECT_UNREGISTERED 的归因(改为待 Catalog Owner 在已排定窗口内\n执行合并;合并前 check.mjs 仍 exit=1 属预期)。\n\n并在节末加并发说明:本文核验跑在 22:30—22:42 之间,期间另有会话提交;\n3689711(22:41:49)独立记录了同一处结构性矛盾——CHG-001 钉在已被 DEC-010\n否定的目标真源上,与本文结论一致。\n\n这正是本文 §6 与回灌台账 C-17 所指的同类错误:陈述与机器基线脱节。区别是\n这次间隔 21 秒而非四天。\n\nL4 链接失效 0、L7 冻结物 0 条不符。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:45:13-07:00"},{"Sha1":"a140998ef2b0be91dcd2a416547b5f2ff9e4beaf","Message":"docs(governance): 架构图评审核对——27 项「缺失」24 项已有归属,真缺口 3 条\n\n新增 平台治理/架构图分析与仓库现状核对-2026-09-14.md:对一份纯图面架构评审\n意见逐条核对仓库现状。结论是该意见方向对、归因错——它判断「实施就绪度低」\n成立,但归因为「规范没定义清楚」;实际规范层相当完整(32 条 DEC 全部已批、\n四类带负向测试的机器契约),缺的是运行时(活 Catalog 21 条平台条目\nimplemented_e2 为 0)。其建议的「六条架构铁律」六条全部已存在于产品纲领且\n措辞更严;建议的试点链与 §11.2 重复。真缺口 3 条:注入防护规范、评测门禁\n实现(均卡 Q02 收口)、Agent Memory 保留与删除语义(待 OS Owner 认领)。\n\n误判源头是评审读了 平台治理/platform-contracts/README.md——它自述为真源却\n停在 2026-09-10(「5 approved / 27 pending」「DEC-010/012 尚未裁决」),而\n机器基线已是 32 approved / 0 pending。据此加两处时效提示:\n\n- platform-contracts/README.md 顶部加冻结待移除副本警示,指向 activeContracts\n- 产品纲领 §4 带日期快照加提示,并指回 决策批次-2026-09-12.md\n\n两处均不改写正文,遵回灌台账 §4 维护规则。README 不在 CHG-001 任何冻结摘要\n内——packageFingerprintForDocument 只哈希审批文档声明的 changeId + 三组摘要\n列表 + expectedFormalBefore/After,不扫描目录。\n\n回灌台账追加 C-17 / C-18。C-18 纠正 §1 第 1 条「CHG-001 包指纹以该目录为准,\n改动会触发就绪度重基线」的不精确表述:冻结面是 14 份具名文件,不是整个目录;\n动手前实算比对,不要按目录名推断。\n\n本文同时纠正两处过期结论:企业应用群挖掘分析-2026-09-14-2142.md(21:45)的\n第 3、4 条已被其后提交处理(CHG-001 22:02 重基线为修订 7、治理测试转绿);\n本文初稿据冻结副本把 causation_id 误记为必填,实为可选(ENVELOPE_OPTIONAL_FIELDS),\n因果链判定由 A 降为 A/C。\n\n一致性门禁 L1—L8 仍 0(本次新增链接已纳入扫描,1530 条);L9 2 条为既有,\n已有框架变更请求 aed8f8c。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:42:31-07:00"},{"Sha1":"c571477584e0f194316d78c8c49768d2303d2d7e","Message":"feat(governance): CHG-001 四项审批落库并排定变更窗口,合并闸门开启\n\n修订 7 技术侧此前已就绪(就绪度 BLOCKED 而非 INVALID),五条阻塞全部是人的\n决定。本次按决策落库:四个角色均由 luoanwu 审批 APPROVED,变更窗口排在\n2026-09-15T05:40:30Z。\n\n- changeWindow.scheduledAt 先于回执写入。record 脚本注释警告过反序的后果:\n 四份回执录完后再排窗口,录入器对已录回执返回 NOOP 并在重算闸门前退出,\n \"UNSCHEDULED: change window\" 将再无脚本可清。先排窗口后录回执可避开该陷阱,\n dry-run 已验证第一份录入后该条即消失\n- 四份回执置于 平台治理/基础/approvals/,逐份通过 validator(VALID,各引 3 份证据:\n 变更请求、DEC-033—036 正式评审包、发布运行手册),再逐份 --commit\n- .gitignore 放行 approvals/:此前被 /平台治理/基础/*/ 一律忽略,而审批记录的\n receiptSha256 正指回这些文件,不入库则 mergeGate 的证据链断在仓外\n\n结果:status pending_approval → approved_for_catalog_merge;\nmergeGate.eligible=true、blockingReasons 清空;就绪度 BLOCKED → READY;\naudit-foundation 阻塞项 7 → 5(CANDIDATE_CATALOG_GATE_BLOCKED 消解)。\n授权边界未越线:catalogMutationAuthorized=true,而 runtime / serviceCreation /\ndeployment 三项仍为 false——登记目录不等于宣告平台可用。\n\n回执 comment 记录了一处已知偏差:变更请求正文写「79/79 测试通过」,本轮独立复验\nverify-new-platform-change.mjs 实为 80/80(rollbackByteIdentical=true、\nformalUnchanged=true)。偏差方向是增加用例,经决策不为此重基线为修订 8,\n在回执中声明知悉。\n\n包指纹 6e2e69d6…ffa97f 全程未变:审批记录不在 frozenInputs/frozenEvidence 之列。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:42:10-07:00"}],"HeadCommit":{"Sha1":"615c017a32da032ecaeb00215d8b8b5418d9b122","Message":"fix(governance): 收回 CHG-001 四项审批并关闭合并闸门,回执按 SOP 归档\n\n修订 7 的四项 APPROVED(2026-09-15T05:40:40Z)与变更窗口(05:40:30Z)建立在\n一个目标真源有问题的包上:CHG-001 整包钉在 平台治理/platform-contracts,而\nDEC-010 已批准的 A 案明写「独立 Git-first 真源由基础设施仓的 contracts/\n工作区承担」,平台治理/README.md 也把前者定性为「冻结待移除,阶段 2 物理移除」。\n\n按现状合并的后果(核对记录 3689711):四个候选会登记进一个待移除的副本,\n而 audit-foundation 读 paths.activeContracts,三项 Catalog 阻断\n(CANDIDATES_NOT_REGISTERED / FORMAL_CATALOG_CHECK_FAILED /\nCANDIDATE_CATALOG_GATE_BLOCKED)不会消除;修订 7 补丁对活跃真源\npatch --fuzz=0 --dry-run 时 test/governance-linter.test.mjs 4 个 hunk 失败 1 个。\n\n目录负责人决定改指活跃真源、重基线为修订 8。按审批录入 SOP §5「包指纹或\n冻结文件漂移 → 全部旧回执失效,重新冻结包并重新审批」,本次先收口人的决定:\n\n- 四份回执连同 archive-manifest 归档到\n reports/catalog-package-archive/6e2e69d6…/approvals-withdrawn/,\n 记明失效原因与「不得转移到修订 8」,approvals/ 清空\n- 审批记录回到审批前形态:四项 PENDING、approver/decidedAt/evidenceRef/\n receiptSha256 置空、changeWindow.scheduledAt 置空(owner 与 rollbackOwner\n 按门禁要求保留 Catalog Owner)、mergeGate.eligible=false、\n authorizations.catalogMutationAuthorized 由 true 回到 false\n- revisionNote 追加【2026-09-14 收回】段,写明依据与修订 8 的前置\n\n包内容未动:revision 仍为 7,指纹 6e2e69d6…a84ffa97f 不变。修订 8 的重基线\n须等活跃真源 contracts/ 工作树 clean(当前有 src/domain/ 九个域包等在途实现),\n否则冻结摘要会钉住半成品。\n\n验证:tests/new-platform-approval-recording 7/7 恢复(此前 4 例因审批落库而\n红——这些用例把正式审批记录当夹具读)。tests/new-platform-catalog-readiness\n仍有 6 例红,成因是并行会话在途把 simulate-new-platform-catalog-merge.mjs\n改指 activeContractsRoot 而修订 8 摘要尚未重算,不属本次变更。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:46:57-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d10dae4ab5cf2e2f61c009033f00970b9a51c600...615c017a32da032ecaeb00215d8b8b5418d9b122","Len":31}...
|
1789451250
|
Edit
Delete
|
|
30052
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"b54b34efc {"Commits":[{"Sha1":"b54b34efc535e49428e3f3d8fbe3b0e6fe204503","Message":"fix(governance): 补登记 EmploymentTransferred 三个参与方的 DEC 前置\n\naudit-foundation 的 FACT_DEPENDENCY_SUMMARY_GAPS:EmploymentTransferred 的\nblocked_by(DEC-010/012/032)未体现在三个参与方的项目摘要里——\nenterprise-fact-backbone 缺 DEC-032、digital-employee-os 为空、\npermission-platform 缺 010/012/032。\n\nblockers 记录的是 Fact 前置依赖(可追溯性),不等于「当前被阻塞」:审计用\n「未批准」单独一列表达阻塞,该列三行均为「无」。既有数据本就登记了已批准的\nDEC-010/012,本次与之一致。\n\n改的是活契约(正式真源——audit-foundation.mjs 注释明写「platform-contracts\n是冻结待移除的副本,审计不能拿它当依据」)。平台治理/platform-contracts/ 的\n冻结副本未触碰:CHG-001 修订 7 的 14 份冻结物复核 14/14 匹配,\npackageValid=true、formalCatalogMutated=false。\n\n审计阻塞项 7 → 6;活契约 test 167/167、治理 test 188/188、L7 冻结物 0 条不符。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:42:20-07:00"},{"Sha1":"edb5218c3bd33f8001d63ff192323ea642d86547","Message":"docs: 修复 2026-09-14 迁移后仓内失效的 48 条相对链接\n\n平台目录由 基础/ 移入 企业控制面/、基础设施文档移入 平台治理/基础设施文档/ 后,\n本仓 394 条相对链接中 48 条失效,全部指向旧的兄弟目录布局:\n\n- ../开发计划.md、../docs/基础设施开发设计方案.md、../CLAUDE.md(6+5+1 条)\n → 平台治理/基础设施文档/ 下对应文件\n- ../../../基础/\u003c平台\u003e/开发计划.md → 企业控制面/\u003c平台\u003e/开发计划.md\n- ../../../上层对接经验回灌台账.md → 平台治理/基础/上层对接经验回灌台账.md\n- ../../../doc/decisions/… → 平台治理/doc/decisions/…\n\n解析方式:以工作区根建全文件后缀索引,只在后缀唯一命中时改写;\n「开发计划.md」在全树有 25 处、后缀不唯一,按本仓语义显式定向到基础设施层。\n\n另两点:\n- 路径按本仓既有风格写明文中文,不做百分号编码;含空格的目录名\n (租户组织与 Scope 平台、通知与 Webhook 中心、AI 治理平台、\n 企业 IM 与智能会话平台)只把空格编码为 %20——目标里的字面空格会被\n Markdown 当作 title 起始而截断链接。\n- docs/项目完整能力表.md 原有 4 条全编码链接随之改为同一风格,目标未变。\n\n校验:本仓 394 条相对链接失效 0(校验含空格目标,此前的校验正则会漏掉它们)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:17:19-07:00"}],"HeadCommit":{"Sha1":"b54b34efc535e49428e3f3d8fbe3b0e6fe204503","Message":"fix(governance): 补登记 EmploymentTransferred 三个参与方的 DEC 前置\n\naudit-foundation 的 FACT_DEPENDENCY_SUMMARY_GAPS:EmploymentTransferred 的\nblocked_by(DEC-010/012/032)未体现在三个参与方的项目摘要里——\nenterprise-fact-backbone 缺 DEC-032、digital-employee-os 为空、\npermission-platform 缺 010/012/032。\n\nblockers 记录的是 Fact 前置依赖(可追溯性),不等于「当前被阻塞」:审计用\n「未批准」单独一列表达阻塞,该列三行均为「无」。既有数据本就登记了已批准的\nDEC-010/012,本次与之一致。\n\n改的是活契约(正式真源——audit-foundation.mjs 注释明写「platform-contracts\n是冻结待移除的副本,审计不能拿它当依据」)。平台治理/platform-contracts/ 的\n冻结副本未触碰:CHG-001 修订 7 的 14 份冻结物复核 14/14 匹配,\npackageValid=true、formalCatalogMutated=false。\n\n审计阻塞项 7 → 6;活契约 test 167/167、治理 test 188/188、L7 冻结物 0 条不符。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:42:20-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/30565bfa7709e7905e2050f43b8a5d6595158069...b54b34efc535e49428e3f3d8fbe3b0e6fe204503","Len":2}...
|
1789451252
|
Edit
Delete
|
|
30053
|
5
|
5
|
5
|
114
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"14a5b8d33 {"Commits":[{"Sha1":"14a5b8d33d1d95137de02e921b772c5db121e215","Message":"chore: 移除被跟踪的 .DS_Store 并加 .gitignore 拦截\n\n仓内 .DS_Store 与 docs/.DS_Store 被 git 跟踪,且没有 .gitignore,\n删掉后 Finder 一访问就会重新进入索引。补一份 .gitignore 收口。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:24:25-07:00"}],"HeadCommit":{"Sha1":"14a5b8d33d1d95137de02e921b772c5db121e215","Message":"chore: 移除被跟踪的 .DS_Store 并加 .gitignore 拦截\n\n仓内 .DS_Store 与 docs/.DS_Store 被 git 跟踪,且没有 .gitignore,\n删掉后 Finder 一访问就会重新进入索引。补一份 .gitignore 收口。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:24:25-07:00"},"CompareURL":"luoanwu/spatiotemporal-fact-model/compare/b5241c619a6252f86eead6f150eb025765793a1a...14a5b8d33d1d95137de02e921b772c5db121e215","Len":1}...
|
1789451255
|
Edit
Delete
|
|
30054
|
5
|
5
|
5
|
54
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"9690ba986 {"Commits":[{"Sha1":"9690ba98673547cb338309cd66f41ff6dbcaf61b","Message":"docs: 同步同步计划文档的新路径\n\n2026-09-14 应用群迁入新根后,治理文档移至 平台治理/基础/。\nCOMPATIBILITY.md 的 0.1.0-pre 行引用 `基础/框架新版本同步计划.md`,\n改为 `平台治理/基础/框架新版本同步计划.md`(目标已核实存在)。\n\n改动本身是迁移当天路径替换的一部分,当时未随其他仓一并入库,\n导致本仓工作树长期 dirty,基础审计据此把框架资产判为 worktreeClean=false。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:24:34-07:00"}],"HeadCommit":{"Sha1":"9690ba98673547cb338309cd66f41ff6dbcaf61b","Message":"docs: 同步同步计划文档的新路径\n\n2026-09-14 应用群迁入新根后,治理文档移至 平台治理/基础/。\nCOMPATIBILITY.md 的 0.1.0-pre 行引用 `基础/框架新版本同步计划.md`,\n改为 `平台治理/基础/框架新版本同步计划.md`(目标已核实存在)。\n\n改动本身是迁移当天路径替换的一部分,当时未随其他仓一并入库,\n导致本仓工作树长期 dirty,基础审计据此把框架资产判为 worktreeClean=false。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:24:34-07:00"},"CompareURL":"luoanwu/base-framework/compare/023d78883392f389eef8363b752fcd2c86813fc1...9690ba98673547cb338309cd66f41ff6dbcaf61b","Len":1}...
|
1789451258
|
Edit
Delete
|
|
30055
|
5
|
5
|
5
|
76
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"c433d57b4 {"Commits":[{"Sha1":"c433d57b4aae2249bd19a085d1c520bf6baedf55","Message":"docs: 文档链接改为仓内相对路径,修复迁移后失效\n\n2026-09-14 应用群迁入新根 企业AI应用开发群/,本仓路径由\n企业产品/企业/企业应用/基础/AI数字员工/ 变为 数字员工OS/。\n\n- development-blueprint-2026-09-04.md:33 处链接写的是旧根绝对路径\n (/Users/hillao/AI产品/企业产品/企业/基础/AI数字员工/digital-employee-os/…),\n 迁移后全部失效。改为仓内相对路径 ../../,行号锚点保留;\n 逐条校验替换后的目标文件均存在。相对路径也让链接不再受未来目录调整影响\n- employment-projection-blueprint.md:上位文档引用 基础/AI数字员工/开发计划.md\n 改为 数字员工OS/开发计划.md\n\ndocs/operations/local-restart-2026-09-13.md 里的旧路径是当时的运维记述,\n属历史事实,保留未改。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:20:56-07:00"}],"HeadCommit":{"Sha1":"c433d57b4aae2249bd19a085d1c520bf6baedf55","Message":"docs: 文档链接改为仓内相对路径,修复迁移后失效\n\n2026-09-14 应用群迁入新根 企业AI应用开发群/,本仓路径由\n企业产品/企业/企业应用/基础/AI数字员工/ 变为 数字员工OS/。\n\n- development-blueprint-2026-09-04.md:33 处链接写的是旧根绝对路径\n (/Users/hillao/AI产品/企业产品/企业/基础/AI数字员工/digital-employee-os/…),\n 迁移后全部失效。改为仓内相对路径 ../../,行号锚点保留;\n 逐条校验替换后的目标文件均存在。相对路径也让链接不再受未来目录调整影响\n- employment-projection-blueprint.md:上位文档引用 基础/AI数字员工/开发计划.md\n 改为 数字员工OS/开发计划.md\n\ndocs/operations/local-restart-2026-09-13.md 里的旧路径是当时的运维记述,\n属历史事实,保留未改。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:20:56-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/23d1b7ac7da6d8779bf29f8fabd126d9f7a15493...c433d57b4aae2249bd19a085d1c520bf6baedf55","Len":1}...
|
1789451260
|
Edit
Delete
|
|
30056
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"4b9218ca6 {"Commits":[{"Sha1":"4b9218ca6b938f802870c9b048b2fba70245c666","Message":"docs(governance): §8 改写为 CHG-001 收口后的实际状态——审批已收回、改指活跃真源\n\n当晚 CHG-001 状态在 5 分钟内翻转两次,本文前两版各记了其中一个中间态:\n- a140998(22:42:31)记 PENDING\n- bd63d88 订正为 READY(据 c571477,22:42:10)\n- 615c017(22:46:57)目录负责人收回全部四项审批、关闭合并闸门\n\n现按收口状态改写,中间态不再保留为结论:四项 PENDING、\nmergeGate.eligible=false、catalogMutationAuthorized=false,回执连同\narchive-manifest 归档至 reports/catalog-package-archive/6e2e69d6…/\napprovals-withdrawn/ 并标明「不得转移到修订 8」。\n\n同时把「两份 catalog 的结构性矛盾」一条从「需裁决」改为「已裁决」:\nCHG-001 整包钉在 平台治理/platform-contracts,而 DEC-010 A 案明写独立\nGit-first 真源由基础设施仓 contracts/ 承担。核对记录 3689711 指出按现状\n合并会把四个候选登记进待移除副本、三项 Catalog 阻断不会消除,且修订 7\n补丁对活跃真源 --fuzz=0 --dry-run 有 1 个 hunk 失败。决定改指活跃真源、\n重基线为修订 8。该矛盾由并发会话独立发现并当场裁决,非本文促成,两条\n路径结论一致,作交叉印证记录。\n\n并发说明段补一条教训,与 §6、回灌台账 C-17 同源:治理文档里任何「现状」\n行都有半衰期,这次是 21 秒;引用状态须写明观测时刻,据状态做决定须当场\n实跑,不得引用他文。\n\n门禁:L4 链接失效 0。L7 当前 2 条不符(simulate-new-platform-catalog-merge.mjs\n与完整变更.patch),成因是并发会话在途重算修订 8 摘要,615c017 已预告,\n不属本次变更。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:49:16-07:00"},{"Sha1":"a06705a0015517aa5968c14d12bbfe631918868b","Message":"fix(governance): 白名单补上反向兜底——机密类文件的排除规则\n\n迁移方案 §8.4 教训 2 写着\"既查该纳入的是否纳入,也查不该纳入的是否排除,\n凭证泄露正源于只做了前一半\"。L1—L9 把九类迁移破坏都固化成了机器检查,\n唯独这一类没有落地——门禁代码里 gitignore / secrets / .env 出现次数均为 0,\n全工作区也无任何机密扫描(无脚本、无 git hook、无 CI)。\n\n用 git check-ignore 实测白名单反向,破绽恰好集中在 平台治理/ 这一层本身\n(也就是 09-14 真正泄过密的那一层):doc/、基础/、基础/scripts/、基础/reports/、\n基础设施文档/、platform-contracts/ 六个放行区,9 类机密文件名里有 8 类会被纳入。\n其它层安全不是因为有防护,而是白名单本来就窄(!/数字员工OS/*.md 只放行 .md)。\n\n根因是兜底段只有两条规则,而 *.env 只匹配以 .env 结尾的名字——\n.env.production / .env.local 都不匹配,.pem / .p12 / id_rsa / secrets.* 则根本没规则。\n\n本次补:.env.*(配 .env.example / .env.*.example 例外)、私钥与证书五类、\nid_rsa* / id_ed25519*、.netrc、secrets.* 与 credentials.* 各三种扩展名。\n\n.npmrc 有意不列:全工作区 8 处合法跟踪(enterprise-platform 仓根与 runtime/、\n报价仓 sites/、嗨赞造意 output/),它是 registry 配置不是机密。\n\n验证:\n- git ls-files | git check-ignore --stdin → 空,无任何已跟踪文件被新规则命中,\n 改动纯预防,不需要先清历史\n- 缺口测绘重跑:六个放行区由\"8 类可纳入\"降为\"仅 .npmrc\"\n- 逐条抽查:doc/.env.production、reports/dump.pem、基础/.env.local、\n decisions/id_rsa、platform-contracts/credentials.json、scripts/.netrc 全部已排除;\n .env.example 仍正常放行\n\n加规则前先扫过现状:密钥类文件名被跟踪 0 个(30+ 仓逐个 git ls-files)、\n硬编码密钥(sk- / AKIA / ghp_ / BEGIN PRIVATE KEY / xox*)0 处、\n未跟踪但不被忽略的机密文件 0 个——开局全绿。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:48:34-07:00"}],"HeadCommit":{"Sha1":"4b9218ca6b938f802870c9b048b2fba70245c666","Message":"docs(governance): §8 改写为 CHG-001 收口后的实际状态——审批已收回、改指活跃真源\n\n当晚 CHG-001 状态在 5 分钟内翻转两次,本文前两版各记了其中一个中间态:\n- a140998(22:42:31)记 PENDING\n- bd63d88 订正为 READY(据 c571477,22:42:10)\n- 615c017(22:46:57)目录负责人收回全部四项审批、关闭合并闸门\n\n现按收口状态改写,中间态不再保留为结论:四项 PENDING、\nmergeGate.eligible=false、catalogMutationAuthorized=false,回执连同\narchive-manifest 归档至 reports/catalog-package-archive/6e2e69d6…/\napprovals-withdrawn/ 并标明「不得转移到修订 8」。\n\n同时把「两份 catalog 的结构性矛盾」一条从「需裁决」改为「已裁决」:\nCHG-001 整包钉在 平台治理/platform-contracts,而 DEC-010 A 案明写独立\nGit-first 真源由基础设施仓 contracts/ 承担。核对记录 3689711 指出按现状\n合并会把四个候选登记进待移除副本、三项 Catalog 阻断不会消除,且修订 7\n补丁对活跃真源 --fuzz=0 --dry-run 有 1 个 hunk 失败。决定改指活跃真源、\n重基线为修订 8。该矛盾由并发会话独立发现并当场裁决,非本文促成,两条\n路径结论一致,作交叉印证记录。\n\n并发说明段补一条教训,与 §6、回灌台账 C-17 同源:治理文档里任何「现状」\n行都有半衰期,这次是 21 秒;引用状态须写明观测时刻,据状态做决定须当场\n实跑,不得引用他文。\n\n门禁:L4 链接失效 0。L7 当前 2 条不符(simulate-new-platform-catalog-merge.mjs\n与完整变更.patch),成因是并发会话在途重算修订 8 摘要,615c017 已预告,\n不属本次变更。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-14T22:49:16-07:00"},"CompareURL":"luoanwu/platform-governance/compare/615c017a32da032ecaeb00215d8b8b5418d9b122...4b9218ca6b938f802870c9b048b2fba70245c666","Len":2}...
|
1789451359
|
Edit
Delete
|
|
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
|
|
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
|
|
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
|
|
30251
|
1
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
|
1789525214
|
Edit
Delete
|
|
30252
|
9
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
|
1789525214
|
Edit
Delete
|
|
30253
|
3
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
|
1789525214
|
Edit
Delete
|
|
30254
|
4
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
|
1789525214
|
Edit
Delete
|
|
30255
|
7
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
|
1789525214
|
Edit
Delete
|
|
30256
|
8
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
|
1789525214
|
Edit
Delete
|
|
30257
|
10
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
|
1789525214
|
Edit
Delete
|
|
30258
|
11
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
|
1789525214
|
Edit
Delete
|
|
30259
|
1
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"5006b67f2 {"Commits":[{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"}],"HeadCommit":{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"},"CompareURL":"","Len":1}...
|
1789525214
|
Edit
Delete
|
|
30260
|
9
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"5006b67f2 {"Commits":[{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"}],"HeadCommit":{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"},"CompareURL":"","Len":1}...
|
1789525214
|
Edit
Delete
|
|
30261
|
3
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"5006b67f2 {"Commits":[{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"}],"HeadCommit":{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"},"CompareURL":"","Len":1}...
|
1789525214
|
Edit
Delete
|
|
30262
|
4
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"5006b67f2 {"Commits":[{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"}],"HeadCommit":{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"},"CompareURL":"","Len":1}...
|
1789525214
|
Edit
Delete
|
|
30263
|
7
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"5006b67f2 {"Commits":[{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"}],"HeadCommit":{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"},"CompareURL":"","Len":1}...
|
1789525214
|
Edit
Delete
|
|
30264
|
8
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"5006b67f2 {"Commits":[{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"}],"HeadCommit":{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"},"CompareURL":"","Len":1}...
|
1789525214
|
Edit
Delete
|
|
30265
|
10
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"5006b67f2 {"Commits":[{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"}],"HeadCommit":{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"},"CompareURL":"","Len":1}...
|
1789525214
|
Edit
Delete
|
|
30266
|
11
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"5006b67f2 {"Commits":[{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"}],"HeadCommit":{"Sha1":"5006b67f2058af953bcd18e2a5db7c28628e48db","Message":"init: initial commit - KTV YouTube resolver full source tree\n\n- Android app (app/)\n- Windows resolver (windows-resolver/)\n- YouTube channel finder (youtube-channel-finder/)\n- Research notes (_research_newpipe_0276/)\n- Protocol docs, install guides, SHA256SUMS, firewall scripts\n- youtube-guide static assets\n\nBuild artifacts (*.apk, *.exe, *.rar, *.zip) ignored via .gitignore\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-09-16T10:16:56+08:00"},"CompareURL":"","Len":1}...
|
1789525214
|
Edit
Delete
|
|
30276
|
21
|
5
|
21
|
119
|
0
|
0
|
refs/heads/main
|
1
|
|
1789527331
|
Edit
Delete
|
|
30277
|
21
|
5
|
21
|
119
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"dc9e73e6e {"Commits":[{"Sha1":"dc9e73e6e97de0960f2e6c449d7cb7a9d1a54847","Message":"Initial commit\n","AuthorEmail":"chenyd@g-hi.com","AuthorName":"chenyd","CommitterEmail":"chenyd@g-hi.com","CommitterName":"chenyd","Timestamp":"2026-09-16T10:54:54+08:00"}],"HeadCommit":{"Sha1":"dc9e73e6e97de0960f2e6c449d7cb7a9d1a54847","Message":"Initial commit\n","AuthorEmail":"chenyd@g-hi.com","AuthorName":"chenyd","CommitterEmail":"chenyd@g-hi.com","CommitterName":"chenyd","Timestamp":"2026-09-16T10:54:54+08:00"},"CompareURL":"","Len":1}...
|
1789527331
|
Edit
Delete
|
|
30278
|
21
|
5
|
21
|
119
|
0
|
0
|
refs/heads/main
|
1
|
{"Commits":[{"Sha1":"4a3b5f0b1 {"Commits":[{"Sha1":"4a3b5f0b1f50e773e113fe91bbf3e5017c14bc19","Message":"Add device SSH keys\n","AuthorEmail":"chenyd@g-hi.com","AuthorName":"chenyd","CommitterEmail":"chenyd@g-hi.com","CommitterName":"chenyd","Timestamp":"2026-09-16T10:56:35+08:00"}],"HeadCommit":{"Sha1":"4a3b5f0b1f50e773e113fe91bbf3e5017c14bc19","Message":"Add device SSH keys\n","AuthorEmail":"chenyd@g-hi.com","AuthorName":"chenyd","CommitterEmail":"chenyd@g-hi.com","CommitterName":"chenyd","Timestamp":"2026-09-16T10:56:35+08:00"},"CompareURL":"chenyd/juhaiwebtool/compare/dc9e73e6e97de0960f2e6c449d7cb7a9d1a54847...4a3b5f0b1f50e773e113fe91bbf3e5017c14bc19","Len":1}...
|
1789527398
|
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
|
|
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
|