|
31056
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"392f0fde4 {"Commits":[{"Sha1":"392f0fde46813c5d061762b8985c74948f6bb088","Message":"docs(计划): 登记 check:gate-flow——真源仓补上「每个门禁的失败信号有谁在看」\n\n治理层 2026-09-14 已为自己建了门禁消费登记并写明病因,真源仓一直没问过这个问题。\n实测 44 个脚本里 12 个既不在 check 链、CI 也不调用,其中三个是真门禁;最实的一处是\nCI 的 image job 构建、生成 SBOM、签名镜像却从不启动它一次,而那六项冒烟正是 D-1 的\n退出条件——且 image-smoke 报告在未登记账里的搁置因此没有出口。\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-18T01:10:55-07:00"}],"HeadCommit":{"Sha1":"392f0fde46813c5d061762b8985c74948f6bb088","Message":"docs(计划): 登记 check:gate-flow——真源仓补上「每个门禁的失败信号有谁在看」\n\n治理层 2026-09-14 已为自己建了门禁消费登记并写明病因,真源仓一直没问过这个问题。\n实测 44 个脚本里 12 个既不在 check 链、CI 也不调用,其中三个是真门禁;最实的一处是\nCI 的 image job 构建、生成 SBOM、签名镜像却从不启动它一次,而那六项冒烟正是 D-1 的\n退出条件——且 image-smoke 报告在未登记账里的搁置因此没有出口。\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-18T01:10:55-07:00"},"CompareURL":"luoanwu/platform-governance/compare/f0d1f11ac7747e845e2781e441cf35bf86717dd5...392f0fde46813c5d061762b8985c74948f6bb088","Len":1}...
|
1789719058
|
Edit
Delete
|
|
31066
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ed4a869bd {"Commits":[{"Sha1":"ed4a869bde4de3243013e74e7f48454e053bd2fa","Message":"docs(框架): 提 FR-7——governance.rules 的 mode 与 ADR-0010 状态的耦合没有执行者\n\nADR-0010 正文写着「在本 ADR 仍为 Proposed 时,mode 固定为 observe」。这句话是整份\n17 条规则注册表**是建议还是约束**的唯一依据。2026-09-18 逐行走读实测:没有任何东西\n在执行它。\n\n governance.rules.schema.json 只把 mode 约束成枚举,管形状不管该是哪个\n check-governance-rules.mjs 校验了 profile 入口、例外到期、enforced 规则须有\n owner、依赖成环等多项,唯独从不判 mode——全文只在\n 成功行里把它打印出来\n generate-governance-status.mjs 按正则读了 ADR 状态,但只回显进报告,不参与判定\n\n两个方向的失效都是静默的:把 mode 翻成 enforced 而 ADR 仍 Proposed 会全绿;ADR 受理\n之后 mode 一直留在 observe 也全绿,17 条规则就此永远停在诊断态,既无提示也无复核期。\n这是「搁置没有出口」,而且落在治理模型的核心开关上。另有一处降级:decisionStatus\n取不到时静默退回 \"Unknown\" 并照常回显,ADR 标题改一个字就会让这条读取无声失效。\n\n请求逐字落实 ADR 已写的那句,不新增政策;不改 schema、不改任何规则的 severity 或\nenforcement、不改 mode 当前取值——今天跑起来仍全绿,只在有人动 mode 或动 ADR 状态时\n才说话。\n\n**本仓未做任何本地修正**:governance.rules.json、其 schema、check-governance-rules.mjs\n与 ADR-0010 四者在 enterprise-platform/runtime/ 下与框架仓逐字相同,本仓改它等于分叉\n框架治理核心,下次同步必冲突。这与 FR-6 的处置不同——那条本仓已本地修正是因为它只在\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-18T01:18:22-07:00"}],"HeadCommit":{"Sha1":"ed4a869bde4de3243013e74e7f48454e053bd2fa","Message":"docs(框架): 提 FR-7——governance.rules 的 mode 与 ADR-0010 状态的耦合没有执行者\n\nADR-0010 正文写着「在本 ADR 仍为 Proposed 时,mode 固定为 observe」。这句话是整份\n17 条规则注册表**是建议还是约束**的唯一依据。2026-09-18 逐行走读实测:没有任何东西\n在执行它。\n\n governance.rules.schema.json 只把 mode 约束成枚举,管形状不管该是哪个\n check-governance-rules.mjs 校验了 profile 入口、例外到期、enforced 规则须有\n owner、依赖成环等多项,唯独从不判 mode——全文只在\n 成功行里把它打印出来\n generate-governance-status.mjs 按正则读了 ADR 状态,但只回显进报告,不参与判定\n\n两个方向的失效都是静默的:把 mode 翻成 enforced 而 ADR 仍 Proposed 会全绿;ADR 受理\n之后 mode 一直留在 observe 也全绿,17 条规则就此永远停在诊断态,既无提示也无复核期。\n这是「搁置没有出口」,而且落在治理模型的核心开关上。另有一处降级:decisionStatus\n取不到时静默退回 \"Unknown\" 并照常回显,ADR 标题改一个字就会让这条读取无声失效。\n\n请求逐字落实 ADR 已写的那句,不新增政策;不改 schema、不改任何规则的 severity 或\nenforcement、不改 mode 当前取值——今天跑起来仍全绿,只在有人动 mode 或动 ADR 状态时\n才说话。\n\n**本仓未做任何本地修正**:governance.rules.json、其 schema、check-governance-rules.mjs\n与 ADR-0010 四者在 enterprise-platform/runtime/ 下与框架仓逐字相同,本仓改它等于分叉\n框架治理核心,下次同步必冲突。这与 FR-6 的处置不同——那条本仓已本地修正是因为它只在\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-18T01:18:22-07:00"},"CompareURL":"luoanwu/platform-governance/compare/392f0fde46813c5d061762b8985c74948f6bb088...ed4a869bde4de3243013e74e7f48454e053bd2fa","Len":1}...
|
1789719506
|
Edit
Delete
|
|
31069
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"58a896f8a {"Commits":[{"Sha1":"58a896f8a4030c0d72fa3b631d8f823f144d1650","Message":"docs(计划): 登记 FR-7 与 gate-flow 推导修正,并订正跨目录待办的 FR 清单\n\n跨目录待办原写「余 FR-6 待受理」,漏了 FR-2 / FR-3——两条 2026-09-12 提出、09-18 复核\n仍成立并补了新证据。现改为四条:FR-2 / FR-3 / FR-6 / FR-7。\n\nFR-7:governance.rules.json 的 mode 与 ADR-0010 状态的耦合没有执行者。ADR 写着「仍为\nProposed 时 mode 固定为 observe」,而 schema 只管枚举、check-governance-rules 只打印\n不判、generate-governance-status 只回显。翻成 enforced 没人拦,ADR 受理后留在 observe\n也没人报,17 条规则会永远停在诊断态。本仓未做本地修正:那四个文件与框架逐字相同。\n\n同轮修了 check:gate-flow 的一处真缺陷:推导在 CI 原文上按名匹配,而工作流里本就有\n带 `pnpm 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-18T01:22:21-07:00"}],"HeadCommit":{"Sha1":"58a896f8a4030c0d72fa3b631d8f823f144d1650","Message":"docs(计划): 登记 FR-7 与 gate-flow 推导修正,并订正跨目录待办的 FR 清单\n\n跨目录待办原写「余 FR-6 待受理」,漏了 FR-2 / FR-3——两条 2026-09-12 提出、09-18 复核\n仍成立并补了新证据。现改为四条:FR-2 / FR-3 / FR-6 / FR-7。\n\nFR-7:governance.rules.json 的 mode 与 ADR-0010 状态的耦合没有执行者。ADR 写着「仍为\nProposed 时 mode 固定为 observe」,而 schema 只管枚举、check-governance-rules 只打印\n不判、generate-governance-status 只回显。翻成 enforced 没人拦,ADR 受理后留在 observe\n也没人报,17 条规则会永远停在诊断态。本仓未做本地修正:那四个文件与框架逐字相同。\n\n同轮修了 check:gate-flow 的一处真缺陷:推导在 CI 原文上按名匹配,而工作流里本就有\n带 `pnpm 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-18T01:22:21-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ed4a869bde4de3243013e74e7f48454e053bd2fa...58a896f8a4030c0d72fa3b631d8f823f144d1650","Len":1}...
|
1789719743
|
Edit
Delete
|
|
31080
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d5323e2b1 {"Commits":[{"Sha1":"d5323e2b149e012cd3340f330a860c232d285738","Message":"docs(计划): 登记 check:ci-mirror——两条 CI 通道「只差四处必须同步改」此前没有执行者\n\nCLAUDE.md 与镜像文件自己的头注释都写着这条规则,而实测没有任何东西在比对它们。\n规范化后两份 461 行逐行相同,文件层面的差异恰好三类,据此立了 M1—M3 三条判据。\n\n值得有执行者的理由:镜像里那行 GOV_REPORT_RUNNER 是证据来源标注的唯一保证,\n不显式覆盖,这条通道产出的报告会冒充 github-actions 并被 verify-candidate 接受。\n\n顺带查出一处真实漂移但不替人裁决:头注释宣称的差异③「fork 判定改用 gitea.* 上下文」\n在文件里根本不存在。若 act_runner 不如实填充 pull_request.head.repo.full_name,\nQ12-A 的 fork 守卫在这条通道上就是失效的。归 SRE / 框架 Owner,该通道从未启用。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T01:52:23-07:00"}],"HeadCommit":{"Sha1":"d5323e2b149e012cd3340f330a860c232d285738","Message":"docs(计划): 登记 check:ci-mirror——两条 CI 通道「只差四处必须同步改」此前没有执行者\n\nCLAUDE.md 与镜像文件自己的头注释都写着这条规则,而实测没有任何东西在比对它们。\n规范化后两份 461 行逐行相同,文件层面的差异恰好三类,据此立了 M1—M3 三条判据。\n\n值得有执行者的理由:镜像里那行 GOV_REPORT_RUNNER 是证据来源标注的唯一保证,\n不显式覆盖,这条通道产出的报告会冒充 github-actions 并被 verify-candidate 接受。\n\n顺带查出一处真实漂移但不替人裁决:头注释宣称的差异③「fork 判定改用 gitea.* 上下文」\n在文件里根本不存在。若 act_runner 不如实填充 pull_request.head.repo.full_name,\nQ12-A 的 fork 守卫在这条通道上就是失效的。归 SRE / 框架 Owner,该通道从未启用。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T01:52:23-07:00"},"CompareURL":"luoanwu/platform-governance/compare/58a896f8a4030c0d72fa3b631d8f823f144d1650...d5323e2b149e012cd3340f330a860c232d285738","Len":1}...
|
1789721547
|
Edit
Delete
|
|
31099
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6b045590e {"Commits":[{"Sha1":"6b045590e6ba93dd703453bc478b3b6c879491f3","Message":"docs(计划): 订正 contracts:check 的登记,并登记偏差 #37 / #38\n\n#38:真实 Catalog 的治理判定不在任何自动流里。contracts/scripts/check.mjs 只在\ncontracts check 里,链与 CI 用的都是 check:local。挡它在链外的历史理由(余 6 项待\nCHG-001)经实测已全部通过——又一次「条件早已满足而无人察觉」。\n\n#37:CHG-007 立的「闸门 blocked_by vs 溯源 decided_by」只应用在 facts 的一条事实上,\nrelationships 与 scopes 仍有 4 条阻断声明指向已批准的 DEC-002 / DEC-004,且当时没留\n探测器。改 Catalog 归 Catalog Owner,本轮只登记不改数据;也没给 linter 加探测器,\n因为给一道没人跑的门禁加规则是无用功,次序上要先解决 #38。\n\n同时订正前一轮把 contracts:check 登记成 tool 的错误,并记下本轮一次把并行会话文件\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-18T02:05:35-07:00"}],"HeadCommit":{"Sha1":"6b045590e6ba93dd703453bc478b3b6c879491f3","Message":"docs(计划): 订正 contracts:check 的登记,并登记偏差 #37 / #38\n\n#38:真实 Catalog 的治理判定不在任何自动流里。contracts/scripts/check.mjs 只在\ncontracts check 里,链与 CI 用的都是 check:local。挡它在链外的历史理由(余 6 项待\nCHG-001)经实测已全部通过——又一次「条件早已满足而无人察觉」。\n\n#37:CHG-007 立的「闸门 blocked_by vs 溯源 decided_by」只应用在 facts 的一条事实上,\nrelationships 与 scopes 仍有 4 条阻断声明指向已批准的 DEC-002 / DEC-004,且当时没留\n探测器。改 Catalog 归 Catalog Owner,本轮只登记不改数据;也没给 linter 加探测器,\n因为给一道没人跑的门禁加规则是无用功,次序上要先解决 #38。\n\n同时订正前一轮把 contracts:check 登记成 tool 的错误,并记下本轮一次把并行会话文件\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-18T02:05:35-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d5323e2b149e012cd3340f330a860c232d285738...6b045590e6ba93dd703453bc478b3b6c879491f3","Len":1}...
|
1789722339
|
Edit
Delete
|
|
31112
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"7433af77e {"Commits":[{"Sha1":"7433af77e643c41f2ccb34fb8aebe363ec76e306","Message":"test(治理): L6 的判定搬进 core 并补负向用例——它此前是唯一零覆盖的一条\n\n一致性门禁 L1—L5 / L7—L13 的判定都在 lib/workspace-consistency-core.mjs 里、各有负向\n用例,**唯独 L6(worktree 两侧 gitdir)与文件系统读取缠在 check-workspace-consistency.mjs\n里**,全量扫描确认 tests/ 里没有任何一条用例触达它。它「能工作」的唯一证据是恰好没在\n实数据上报错——而「没报错」与「判不出来」在外部看来一模一样。\n\n本轮只搬不改:IO 函数改为只收集事实,判定交给新的纯函数 evaluateWorktreeGitdirs。\n**判词逐字未变,改前改后门禁 --json 输出实测完全相同**(status / counts / issues 三者\n逐字相等,prunableWorktrees 仍为 5、L9 仍为 1)。\n\n补 8 条负向用例,覆盖两个方向的全部分支:\n 方向一 .git 为空 / 指向不存在的登记 / 登记反指不回来(含反指读不出时须写「(空)」);\n 三种坏法互斥,前一种命中不再叠加后一种\n 方向二 gitdir 为空即红;目标还在就跳过(反指归方向一,不重复报);\n **目标没了且旁边没有同名工作树 = prunable,只计数不报**——那是 git worktree\n prune 的日常;目标没了但工作树就在旁边 = 失联,判红且不计入 prunable\n\n顺带核实两条初测假阳性,记在这里免得再查一遍:L9 的判定其实在 core 里且有用例\n(composeProjectName / composeProjectCollisions),只是测试里不出现「L9」这个字面量;\nL0 与 L28 是正则误匹配(一个字符类、一处注释里的行号)。\n\n一致性门禁测试 34 → 42,治理层全量 389 → 401(395 过 / 6 跳 / 0 失败);\n统一入口阻断性门禁 11/11。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T02:39:16-07:00"},{"Sha1":"1e6a813a72945400129128947654df4ecdc8849d","Message":"docs(回灌): U-39 / U-40——发布物与源码同版本不同内容,且 provenance 无 gitSha\n\n新增 §2E 第 5 轮条目(基础基座 → 基础设施)。采集自 OS 执行「内核退回 pin 立项」B1\n(contracts exact pin @juhai/kernel@0.22.0)时对接已发布客户端包的实测。\n\nU-39 发布物与其源码同版本不同内容,peer 只是露出来的一角。已发布的\n @juhai/client-fact@1.0.0-rc.3 声明 peer @juhai/kernel: 0.16.1(发布物自证),而控制面仓\n 同版本源码声明 0.22.0——2026-09-17 框架同步只改了 runtime/clients/fact/package.json 未重发。\n 进一步拆开发布物:dist 里没有 Authorization 回查鉴权,源码 reader.ts:31 却发\n Bearer ${token}。消费侧对此完全不可见:pnpm 对未满足 peer 只打一行 WARN 就继续装。\n → 平台侧动作:重发 rc.4 携带正确 peer,发布前确认 dist 与源码同一提交。\n 基座侧已自保:新增 PEER_UNSATISFIED 判据 + 五字段登记(期限 2026-12-18)。\n\nU-40 本地旁路发布的发布物不可对账到提交。registry 上 rc.3 的 provenance.json 为\n runner:\"local\" / reports:[] / gitSha:\"\"——空字符串。任何消费者都无法验证装到的包出自哪次\n 提交,U-39 那种「同版本不同内容」因此无法被机器发现。这比 peer 错一版严重:peer 至少还有\n 一个可比的值,gitSha 为空是判据缺席。\n → 平台侧动作:发布物 provenance.json 必须带真实 gitSha,本地旁路也不得留空——旁路可以解除\n CI 身份检查,但不应连「这是哪次提交构建的」都放弃。\n\n两条均标 🔴 下层缺口,阻塞于平台发布列车(G-12 计费)。基座侧不停等:按立项 §6 三条出路\n裁为 ③(登记偏差 + 加判据),B2 / B3′ 继续推进。\n\n一致性门禁复跑:合计 1 条,仅 L9(8 仓共用 compose project api-nestjs),与本次改动无关——\n它正是 OS 在 framework-criteria.json 里登记为 missing 的框架 F14。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T02:39:13-07:00"}],"HeadCommit":{"Sha1":"7433af77e643c41f2ccb34fb8aebe363ec76e306","Message":"test(治理): L6 的判定搬进 core 并补负向用例——它此前是唯一零覆盖的一条\n\n一致性门禁 L1—L5 / L7—L13 的判定都在 lib/workspace-consistency-core.mjs 里、各有负向\n用例,**唯独 L6(worktree 两侧 gitdir)与文件系统读取缠在 check-workspace-consistency.mjs\n里**,全量扫描确认 tests/ 里没有任何一条用例触达它。它「能工作」的唯一证据是恰好没在\n实数据上报错——而「没报错」与「判不出来」在外部看来一模一样。\n\n本轮只搬不改:IO 函数改为只收集事实,判定交给新的纯函数 evaluateWorktreeGitdirs。\n**判词逐字未变,改前改后门禁 --json 输出实测完全相同**(status / counts / issues 三者\n逐字相等,prunableWorktrees 仍为 5、L9 仍为 1)。\n\n补 8 条负向用例,覆盖两个方向的全部分支:\n 方向一 .git 为空 / 指向不存在的登记 / 登记反指不回来(含反指读不出时须写「(空)」);\n 三种坏法互斥,前一种命中不再叠加后一种\n 方向二 gitdir 为空即红;目标还在就跳过(反指归方向一,不重复报);\n **目标没了且旁边没有同名工作树 = prunable,只计数不报**——那是 git worktree\n prune 的日常;目标没了但工作树就在旁边 = 失联,判红且不计入 prunable\n\n顺带核实两条初测假阳性,记在这里免得再查一遍:L9 的判定其实在 core 里且有用例\n(composeProjectName / composeProjectCollisions),只是测试里不出现「L9」这个字面量;\nL0 与 L28 是正则误匹配(一个字符类、一处注释里的行号)。\n\n一致性门禁测试 34 → 42,治理层全量 389 → 401(395 过 / 6 跳 / 0 失败);\n统一入口阻断性门禁 11/11。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T02:39:16-07:00"},"CompareURL":"luoanwu/platform-governance/compare/6b045590e6ba93dd703453bc478b3b6c879491f3...7433af77e643c41f2ccb34fb8aebe363ec76e306","Len":2}...
|
1789724358
|
Edit
Delete
|
|
31113
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"72c053ccb {"Commits":[{"Sha1":"72c053ccbb2b4effb1451b6b61e69faf9c313fd5","Message":"docs(治理): README 订正——「判定逻辑在 core」这句话此前对 L6 并不成立\n\n第 49 行写着「判定逻辑在 workspace-consistency-core.mjs,夹具用例 19/19」。前半句对\nL6 是假的(它的判定与文件系统读取缠在 IO 脚本里、测试零覆盖),后半句的 19 也早已陈旧。\n\nL6 的判定已于同日搬进 core 并补 8 条用例,这句话现在成立了;数字改为当前的 42,\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-18T02:39:56-07:00"}],"HeadCommit":{"Sha1":"72c053ccbb2b4effb1451b6b61e69faf9c313fd5","Message":"docs(治理): README 订正——「判定逻辑在 core」这句话此前对 L6 并不成立\n\n第 49 行写着「判定逻辑在 workspace-consistency-core.mjs,夹具用例 19/19」。前半句对\nL6 是假的(它的判定与文件系统读取缠在 IO 脚本里、测试零覆盖),后半句的 19 也早已陈旧。\n\nL6 的判定已于同日搬进 core 并补 8 条用例,这句话现在成立了;数字改为当前的 42,\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-18T02:39:56-07:00"},"CompareURL":"luoanwu/platform-governance/compare/7433af77e643c41f2ccb34fb8aebe363ec76e306...72c053ccbb2b4effb1451b6b61e69faf9c313fd5","Len":1}...
|
1789724399
|
Edit
Delete
|
|
31122
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"54738a32d {"Commits":[{"Sha1":"54738a32d101f97cc5dd3a5bca7ea426dceea9c6","Message":"feat(治理): L9 的完整仓名单带进 JSON——裁决输入不该每次重新推导\n\nL9 目前是全工作区唯一在报的那条,挂在 N-11 的裁决上,而裁决要回答的正是「哪些仓各自\n补 compose `name:`」。判定本来就算出了完整名单(composeProjectCollisions 返回\nrepos / files),但建 issue 时被丢掉:消息里只写前三个加「等 N 个」,JSON 里一个都没有。\n于是每次想知道是哪八个,都得重新推导一遍。\n\n`issue()` 增一个可选 extra 参数,只用于把**判定已算出、消息里放不下**的结构化数据带进\nJSON;没有 extra 的检查一个字段都不多(用例钉住 L13 的键仍是四个)。\n\n实测:门禁现在报出的 8 个仓与我按同一口径(排除 29 个工作树、按 .git 目录归仓)独立\n重推的结果完全一致——数字员工OS、知识云、AI项目与工单、AI人事系统、设备云、巨嗨智服、\n巨嗨报价系统、嗨赞造意/image-generation。counts 未变(total 1 / L9 1)。\n\n补两条用例:L9 的发现必须携带 repos 且数量与消息声称的一致、不得重复、files 不少于仓数;\n以及 issue() 的默认形状不变。前者守的是「有冲突时名单不得丢」,不是「必须有冲突」——\nL9 清零后它自然为空。\n\n一致性门禁测试 42 → 44,治理层全量 397 过 / 6 跳 / 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-18T02:46:51-07:00"}],"HeadCommit":{"Sha1":"54738a32d101f97cc5dd3a5bca7ea426dceea9c6","Message":"feat(治理): L9 的完整仓名单带进 JSON——裁决输入不该每次重新推导\n\nL9 目前是全工作区唯一在报的那条,挂在 N-11 的裁决上,而裁决要回答的正是「哪些仓各自\n补 compose `name:`」。判定本来就算出了完整名单(composeProjectCollisions 返回\nrepos / files),但建 issue 时被丢掉:消息里只写前三个加「等 N 个」,JSON 里一个都没有。\n于是每次想知道是哪八个,都得重新推导一遍。\n\n`issue()` 增一个可选 extra 参数,只用于把**判定已算出、消息里放不下**的结构化数据带进\nJSON;没有 extra 的检查一个字段都不多(用例钉住 L13 的键仍是四个)。\n\n实测:门禁现在报出的 8 个仓与我按同一口径(排除 29 个工作树、按 .git 目录归仓)独立\n重推的结果完全一致——数字员工OS、知识云、AI项目与工单、AI人事系统、设备云、巨嗨智服、\n巨嗨报价系统、嗨赞造意/image-generation。counts 未变(total 1 / L9 1)。\n\n补两条用例:L9 的发现必须携带 repos 且数量与消息声称的一致、不得重复、files 不少于仓数;\n以及 issue() 的默认形状不变。前者守的是「有冲突时名单不得丢」,不是「必须有冲突」——\nL9 清零后它自然为空。\n\n一致性门禁测试 42 → 44,治理层全量 397 过 / 6 跳 / 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-18T02:46:51-07:00"},"CompareURL":"luoanwu/platform-governance/compare/72c053ccbb2b4effb1451b6b61e69faf9c313fd5...54738a32d101f97cc5dd3a5bca7ea426dceea9c6","Len":1}...
|
1789724816
|
Edit
Delete
|
|
31123
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"a7075e40e {"Commits":[{"Sha1":"a7075e40e9aed8fbe69edb7fb7f0ebc05e477214","Message":"docs(计划): 登记 L6 / L9 两处补强,并订正自己提交信息里的一句过头话\n\nL6 此前是唯一判定与 IO 缠在一起、测试零覆盖的规则,已搬进 core 并补 8 条用例,\n只搬不改、输出逐字相同;README 那句「判定逻辑在 core」此前对它是假的,已订正。\n\nL9 的完整仓名单现在进 JSON。但我在那条提交信息里写的「每次都得重新推导」过头了:\nN-11 正文 2026-09-17 就手写了这 8 个仓名。真实缺口是名单只有手抄的一份、门禁不产\n机器形态,两者可以无声分叉。本轮独立重推的 8 个与 N-11 手抄的完全一致。\n\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-18T02:47:33-07:00"}],"HeadCommit":{"Sha1":"a7075e40e9aed8fbe69edb7fb7f0ebc05e477214","Message":"docs(计划): 登记 L6 / L9 两处补强,并订正自己提交信息里的一句过头话\n\nL6 此前是唯一判定与 IO 缠在一起、测试零覆盖的规则,已搬进 core 并补 8 条用例,\n只搬不改、输出逐字相同;README 那句「判定逻辑在 core」此前对它是假的,已订正。\n\nL9 的完整仓名单现在进 JSON。但我在那条提交信息里写的「每次都得重新推导」过头了:\nN-11 正文 2026-09-17 就手写了这 8 个仓名。真实缺口是名单只有手抄的一份、门禁不产\n机器形态,两者可以无声分叉。本轮独立重推的 8 个与 N-11 手抄的完全一致。\n\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-18T02:47:33-07:00"},"CompareURL":"luoanwu/platform-governance/compare/54738a32d101f97cc5dd3a5bca7ea426dceea9c6...a7075e40e9aed8fbe69edb7fb7f0ebc05e477214","Len":1}...
|
1789724855
|
Edit
Delete
|
|
31141
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/claude/zealous-tu-6f0fca
|
0
|
|
1789740931
|
Edit
Delete
|
|
31142
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/claude/zealous-tu-6f0fca
|
0
|
{"Commits":[{"Sha1":"031878b2a {"Commits":[{"Sha1":"031878b2a7dbd2e2021b6dd71b0197e50cec3c96","Message":"docs(计划): 第四处同病改判已修(08c3788),并订正本条原先给错的一个修法\n\n登记时给了两个修法,取的是「把写报告挪到前置校验之后」;另一个「直接删掉占位写」被接手\n会话否掉,理由成立,本条一并订正:「跑起来但没跑完」确实该在盘上留 RUN_NOT_COMPLETED 而\n不是上一轮的 partial——这是用例自己写报告带来的责任,和「上轮结论已被后续提交推翻」不是\n同一个事实,不能用 check:evidence 判过期替代。\n\n实现是把那句抽成 markRunStarted(),调用点挪到模块库白名单通过、真实连库、API 子进程\n/health 就绪之后。两个方向都做了负向实测:同一条件下旧代码毁报告(sha256 变化),新代码\n测试照样失败而报告逐字节不变;正向确认 t+85s 兜底仍写 RUN_NOT_COMPLETED。\n\n受影响四份已重跑回绑 dfd4832(全绑 08c3788 / dirty=false,结果与修复前一致,说明动的只是\n写报告的时机);runbook §7 收尾同步改成已修(925eee8)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T07:13:53-07:00"},{"Sha1":"f7a6b8eb62651f612a8a0e9666b22a5413b4fb1a","Message":"docs(计划): 登记第四处「前置失败销毁好证据」——revocation-sla 由用例自己在 beforeAll 写 failed\n\nadda76a 把三个 runner(runtime / UI / 双后端差分)统一改成前置失败即退出、不碰报告,\n本表上一条据此记「三处同病」。复核接手会话的重跑计划时发现同族还有第四处,且不在那\n三个 runner 里:revocation-sla.latest.json 的写入者是用例自己,不是 runner。\n\n要害是写入时机。runtime/test/e2e/revocation-sla.test.ts:68 在 beforeAll 的第一句就\n无条件写下 status:failed / reason:RUN_NOT_COMPLETED,下一句才做 isolated() 库名校验\n(mainline-support.ts:11 要求 /platform_\u003ckind\u003e_(ms23|test|ci))。先毁证据再校验前置,\n恰是 adda76a 所确立口径的反面。\n\n触发面比「跑主线验收」宽:runtime/test 是工作区包 platform-tests,pnpm\nruntime:check:runtime 第 5 步的 turbo run test 就会跑到它。runbook §7 那句「前置守卫\n段已修复,但跑到一半失败仍会写 failed」对本处不成立——连跑到一半都不需要。\n\n当日由接手会话实测复现:七个模块库建成 platform_\u003cm\u003e_acc0918 后 e2e/chaos 整片失败,\n其独立检出里那份报告已被清成 RUN_NOT_COMPLETED 绑 46265a6;主工作区绑 765300b 的\npartial 因其在独立检出里跑而幸存。连带结论是七个模块库后缀只能是 ms23 / test / ci,\n且 check:runtime 与 mainline:check 本就该共用同一批库。\n\n本轮只登记不修:六份验收报告的重跑已移交主会话并在其独立检出里进行,改同一批文件必\n撞车。真源仓侧的代码修正与 runbook §7 的措辞订正留给接手会话。全程只读,未跑门禁、\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-18T02:04:54-07:00"}],"HeadCommit":{"Sha1":"031878b2a7dbd2e2021b6dd71b0197e50cec3c96","Message":"docs(计划): 第四处同病改判已修(08c3788),并订正本条原先给错的一个修法\n\n登记时给了两个修法,取的是「把写报告挪到前置校验之后」;另一个「直接删掉占位写」被接手\n会话否掉,理由成立,本条一并订正:「跑起来但没跑完」确实该在盘上留 RUN_NOT_COMPLETED 而\n不是上一轮的 partial——这是用例自己写报告带来的责任,和「上轮结论已被后续提交推翻」不是\n同一个事实,不能用 check:evidence 判过期替代。\n\n实现是把那句抽成 markRunStarted(),调用点挪到模块库白名单通过、真实连库、API 子进程\n/health 就绪之后。两个方向都做了负向实测:同一条件下旧代码毁报告(sha256 变化),新代码\n测试照样失败而报告逐字节不变;正向确认 t+85s 兜底仍写 RUN_NOT_COMPLETED。\n\n受影响四份已重跑回绑 dfd4832(全绑 08c3788 / dirty=false,结果与修复前一致,说明动的只是\n写报告的时机);runbook §7 收尾同步改成已修(925eee8)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T07:13:53-07:00"},"CompareURL":"luoanwu/platform-governance/compare/58a896f8a4030c0d72fa3b631d8f823f144d1650...031878b2a7dbd2e2021b6dd71b0197e50cec3c96","Len":2}...
|
1789740931
|
Edit
Delete
|
|
31174
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"9a8b716a0 {"Commits":[{"Sha1":"9a8b716a056597786b9fcbc8fd57bff6c5b44722","Message":"docs(回灌): 订正 U-40——「gitSha 为空」不成立,字段叫 sourceSha 且有值,落点随之改向\n\nU-40 原文称 registry 上的 @juhai/client-fact@1.0.0-rc.3 其 provenance.json 为 gitSha:\"\" 空字符串,\n据此把落点定为「平台侧必须带真实 gitSha,本地旁路发布也不得留空」。一手实测推翻该前提:\n\n在真源仓 npm 作用域下 npm pack 拉取架上 tarball 读其 provenance.json,client-fact 与 contracts 的\nrc.3 两份一字不差,且都带 \"sourceSha\": \"036a308f27acf35a46f068c96fea7723ef74d05e\"。\n字段名是 sourceSha 不是 gitSha,且有真实值——提交号一直在包里。照原落点做,平台会去补一个已经存在的字段。\n\n本条结论仍成立、病因换了:不是「平台没写」,是两侧键名对不上,且基座判据根本没读产物的\nprovenance.json——复核 数字员工OS/digital-employee-os/scripts/check-platform-dependency-provenance.mjs,\n其中 gitSha / sourceSha 的命中全部属于它自己报告的 provenance,没有一处读依赖产物。\n\n落点改为两条:① 平台侧把 sourceSha 这个字段名写进对外契约(发布物 schema / 接入套件文档),\n使消费者不必靠猜;旁路车另缺 tag(tag:null,与 CL-5「一次发布 = 一个 tag = 一组同版本包」不符),该项仍欠。\n② 基座侧把判据从「解析来源」扩到「内容出处」,只需读包内 sourceSha 与期望提交比对,不必等平台改任何东西。\n\n状态 🔴 → 🟡:不再与 U-39 同一阻塞,两侧都可立即动工,不受 G-12 计费阻塞;仅 tag:null 仍挂在旁路车上。\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-18T16:05:19-07:00"},{"Sha1":"63850ac3b7b1a51d74aac689837fdf7ed58905bb","Message":"docs(回灌): U-39 补 contracts 同版本不同内容的新实例——落差由一个提交扩大到一整轮硬化\n\n@juhai/contracts@1.0.0-rc.3 与 client-fact 同属 2026-09-13 那趟本地旁路车。实查架上包:其\nprovenance.json 自证 sourceSha=036a308,而仓内同版本源码已含 2026-09-18 九个契约包域\n(public-file / IM / 跨域流程 / 通知 / 数据分析 / 成本容量 / 统一体验 / 注册中心 / 配置与功能开关)\n的失败关闭硬化。消费者 exact pin 1.0.0-rc.3 拿到的是硬化前代码;./domain/* 是公开子路径导出,\n失败一侧行为已变。U-39 的「同版本不同内容」因此不是 client-fact 一例。\n\n不另开 U 号:本实例由基础设施自查发现、没有上层对接方,不符合本台账 §0「只有业务应用的开发轮次\n触发回灌」的驱动方口径,故并入 U-39 状态格,不新设真源。\n\n证据取自一手产物:在仓内 npm 作用域下 npm pack 拉取架上 tarball,读其 provenance.json。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T16:03:44-07:00"},{"Sha1":"fad563310502477427181b6cbe2b48af4aebb668","Message":"docs(计划): 登记四份过期证据回绑与一次撤回 @ 772b253\n\nrelease-manifest / sbom / naming / fork-readiness 四份在干净检出内重跑回绑,结论逐项\n对照无劣化;sbom 的 ref 更新后它描述的才是当前登记的镜像。check:evidence 由\n36 新鲜 / 5 过期 变为 40 新鲜 / 1 过期 / 0 error,仅剩 image-smoke(须 Secret 到位后\n由 CI 插一步冒烟,带复核期 2026-10-31)。\n\n另记一次撤回:module-imports 那次回绑是多余的——并行会话提交门禁改动时已连报告一起\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-18T15:47:52-07:00"},{"Sha1":"80eced637aa8796ffec9c266cde6d6567e4fdb49","Message":"docs(计划): 登记注册中心就绪闸门补判与干净检出回绑 @ 94366bc / de532d4\n\n并更正上一行登记:注册中心 9ac9914 已被 7f82399 的合并整体放弃,上一行现在只对\n统一体验 caefbf6 成立。远端那版的摘要归一化比本地那版的「一律拒」更好,本轮采纳\n其口径;只补它仍缺的四条就绪闸门真值判定,并把零覆盖的 snapshot-upgrade-review.ts\n接进夹具门禁。\n\n回绑改走 #34-A 立的干净检出路径:主工作区 4 小时没出现干净树。附带记下一条坑——\n检出必须落在工作区内,否则 workspaceRelative 套件会以 unavailable 让门禁 exit 1。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T12:26:45-07:00"},{"Sha1":"1d2416ab6482cf2ad8f2e4c311c62545daebfd16","Message":"docs(计划): 登记统一体验与注册中心两个契约包入参硬化 @ caefbf6 / 9ac9914\n\n两域各有一条同形缺陷(闸门用真值判断,\"false\" 一律放行——统一体验是 G3 本身与\n权限 / Scope 判定,注册中心是四条就绪闸门)与各自的崩溃面;注册中心另有 blockedBy\n传字符串时 .length 是字符数、摘要正则带 i 导致同一制品两个身份两处。修的都是同一\n文件里正确写法本来就在的那种。顺带补两块零门禁覆盖:统一体验持闸的两个公开函数、\n注册中心整份 393 行的升级复核。九个契约包域至此全部补强,套件合计 188 例 0 失败。\n\n另回写一条技术教训:独立索引提交后必须 git reset -- \u003c路径\u003e 把共享索引刷回 HEAD,\n否则并行会话下一次从索引提交会把已提交的改动带回去(2026-09-18 已实际发生一次)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T07:53:53-07:00"}],"HeadCommit":{"Sha1":"9a8b716a056597786b9fcbc8fd57bff6c5b44722","Message":"docs(回灌): 订正 U-40——「gitSha 为空」不成立,字段叫 sourceSha 且有值,落点随之改向\n\nU-40 原文称 registry 上的 @juhai/client-fact@1.0.0-rc.3 其 provenance.json 为 gitSha:\"\" 空字符串,\n据此把落点定为「平台侧必须带真实 gitSha,本地旁路发布也不得留空」。一手实测推翻该前提:\n\n在真源仓 npm 作用域下 npm pack 拉取架上 tarball 读其 provenance.json,client-fact 与 contracts 的\nrc.3 两份一字不差,且都带 \"sourceSha\": \"036a308f27acf35a46f068c96fea7723ef74d05e\"。\n字段名是 sourceSha 不是 gitSha,且有真实值——提交号一直在包里。照原落点做,平台会去补一个已经存在的字段。\n\n本条结论仍成立、病因换了:不是「平台没写」,是两侧键名对不上,且基座判据根本没读产物的\nprovenance.json——复核 数字员工OS/digital-employee-os/scripts/check-platform-dependency-provenance.mjs,\n其中 gitSha / sourceSha 的命中全部属于它自己报告的 provenance,没有一处读依赖产物。\n\n落点改为两条:① 平台侧把 sourceSha 这个字段名写进对外契约(发布物 schema / 接入套件文档),\n使消费者不必靠猜;旁路车另缺 tag(tag:null,与 CL-5「一次发布 = 一个 tag = 一组同版本包」不符),该项仍欠。\n② 基座侧把判据从「解析来源」扩到「内容出处」,只需读包内 sourceSha 与期望提交比对,不必等平台改任何东西。\n\n状态 🔴 → 🟡:不再与 U-39 同一阻塞,两侧都可立即动工,不受 G-12 计费阻塞;仅 tag:null 仍挂在旁路车上。\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-18T16:05:19-07:00"},"CompareURL":"luoanwu/platform-governance/compare/a7075e40e9aed8fbe69edb7fb7f0ebc05e477214...9a8b716a056597786b9fcbc8fd57bff6c5b44722","Len":6}...
|
1789772759
|
Edit
Delete
|
|
31176
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"2395fff75 {"Commits":[{"Sha1":"2395fff75b12126982536526d4ae47676954a0b2","Message":"docs(计划): 注册中心取舍行补交叉实测证据——「大部分好或相当」可以收紧成「放弃那套实有 4 个缺陷」\n\n第 196 行原写「远端那版大部分比本地那版做得好或相当」,是对现行实现单向复测得出的。另一会话随后做了\n双向交叉实测(两套实现各自编译成 dist 后互喂夹具与单测),结论更明确:被放弃的 9ac9914 实有 4 个缺陷——\nN10 放行可变版本标签、N11 拒错原因(其 \\d+\\.\\d+\\.\\d+ 收下 1.02.0)、P03 与 P04 两处误拒(后者会拒掉\n平台自己在发的 1.0.0-rc.x);根因是它三个文件各带一套版本文法,远端抽 registry-primitives.ts 正为收敛这三套。\n\n反向也测了:9ac9914 的 19 例夹具喂当前实现 13 通过,6 例不通过里 5 例只是原因码改名(同一输入两侧都拒)、\n1 例是摘要大小写的设计取向差异,无任何输入类别失守;其 40 例单测喂当前实现 36 通过。\n\n只补证据与出处(真源仓 7523bd0 的 contracts/SOURCE.md),不改该行原有的复测结论与实现取舍。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T16:07:14-07:00"}],"HeadCommit":{"Sha1":"2395fff75b12126982536526d4ae47676954a0b2","Message":"docs(计划): 注册中心取舍行补交叉实测证据——「大部分好或相当」可以收紧成「放弃那套实有 4 个缺陷」\n\n第 196 行原写「远端那版大部分比本地那版做得好或相当」,是对现行实现单向复测得出的。另一会话随后做了\n双向交叉实测(两套实现各自编译成 dist 后互喂夹具与单测),结论更明确:被放弃的 9ac9914 实有 4 个缺陷——\nN10 放行可变版本标签、N11 拒错原因(其 \\d+\\.\\d+\\.\\d+ 收下 1.02.0)、P03 与 P04 两处误拒(后者会拒掉\n平台自己在发的 1.0.0-rc.x);根因是它三个文件各带一套版本文法,远端抽 registry-primitives.ts 正为收敛这三套。\n\n反向也测了:9ac9914 的 19 例夹具喂当前实现 13 通过,6 例不通过里 5 例只是原因码改名(同一输入两侧都拒)、\n1 例是摘要大小写的设计取向差异,无任何输入类别失守;其 40 例单测喂当前实现 36 通过。\n\n只补证据与出处(真源仓 7523bd0 的 contracts/SOURCE.md),不改该行原有的复测结论与实现取舍。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T16:07:14-07:00"},"CompareURL":"luoanwu/platform-governance/compare/9a8b716a056597786b9fcbc8fd57bff6c5b44722...2395fff75b12126982536526d4ae47676954a0b2","Len":1}...
|
1789772837
|
Edit
Delete
|
|
31182
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"8e5cc87f0 {"Commits":[{"Sha1":"8e5cc87f027dab462c6f3f5bf8f0e42894778016","Message":"docs(计划): 登记本轮五件事,并订正 image-smoke「本机解决不了」与镜像落差 116\n\n§8 加一行:① 目录快照发布维度补 not-in-manifest——「Manifest 落后 HEAD」是一个全局\n事实,此前被复制成 21 条目各自的 release.status=stale,其中 14 条没有运行时模块、\nManifest 从未收录过;② runtime 动态区回灌两级验收 SHA(报告已绑 08c3788 / 1b23285,\n动态区还写 765300b);③ 完整 pnpm --dir runtime check 让 18 份静态子报告同绑一次运行,\nreportProvenanceViolations 归零——单跑一道门禁做不到这条;④ 镜像冒烟本机真跑 6/6 后\n补绑定,check:evidence 在 95b88d3 上到 passed / 41 新鲜 / 0 过期;⑤ runbook §7 补\n--env-file 来源,连带回绑两份工作台快照;⑥ 镜像同步被 GH006 拒绝并留证。\n\n订正上一条登记:image-smoke 被记成「不是本机静态能解决的」,实测不是——它的 sourceSha\n与 image-digest.json 一致,说明冒的是当前镜像、结论有效,过期只是绑定落后,本机真跑一次\n即清。但 §5 那条「CI 在 build 与 sbom 之间插一步冒烟」的登记不因此关闭。\n\n另记一条机制发现:直推镜像 main 在机制上走不通(workflow 只在 pull_request /\npush:[main] / workflow_dispatch 触发,而保护要求 check 挂在被推的 commit 上,该 commit\n没到过 GitHub 就没有 check,要跑就得先推上 main)。可行路线只剩合 PR #45 或侧分支\ndispatch 后推同一 SHA,都要计费先恢复。\n\n三处「落后 116 个提交」按实测改为 245,并写明实测日期与「引用前重测」——这个数每天在涨,\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-18T16:09:33-07:00"}],"HeadCommit":{"Sha1":"8e5cc87f027dab462c6f3f5bf8f0e42894778016","Message":"docs(计划): 登记本轮五件事,并订正 image-smoke「本机解决不了」与镜像落差 116\n\n§8 加一行:① 目录快照发布维度补 not-in-manifest——「Manifest 落后 HEAD」是一个全局\n事实,此前被复制成 21 条目各自的 release.status=stale,其中 14 条没有运行时模块、\nManifest 从未收录过;② runtime 动态区回灌两级验收 SHA(报告已绑 08c3788 / 1b23285,\n动态区还写 765300b);③ 完整 pnpm --dir runtime check 让 18 份静态子报告同绑一次运行,\nreportProvenanceViolations 归零——单跑一道门禁做不到这条;④ 镜像冒烟本机真跑 6/6 后\n补绑定,check:evidence 在 95b88d3 上到 passed / 41 新鲜 / 0 过期;⑤ runbook §7 补\n--env-file 来源,连带回绑两份工作台快照;⑥ 镜像同步被 GH006 拒绝并留证。\n\n订正上一条登记:image-smoke 被记成「不是本机静态能解决的」,实测不是——它的 sourceSha\n与 image-digest.json 一致,说明冒的是当前镜像、结论有效,过期只是绑定落后,本机真跑一次\n即清。但 §5 那条「CI 在 build 与 sbom 之间插一步冒烟」的登记不因此关闭。\n\n另记一条机制发现:直推镜像 main 在机制上走不通(workflow 只在 pull_request /\npush:[main] / workflow_dispatch 触发,而保护要求 check 挂在被推的 commit 上,该 commit\n没到过 GitHub 就没有 check,要跑就得先推上 main)。可行路线只剩合 PR #45 或侧分支\ndispatch 后推同一 SHA,都要计费先恢复。\n\n三处「落后 116 个提交」按实测改为 245,并写明实测日期与「引用前重测」——这个数每天在涨,\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-18T16:09:33-07:00"},"CompareURL":"luoanwu/platform-governance/compare/2395fff75b12126982536526d4ae47676954a0b2...8e5cc87f027dab462c6f3f5bf8f0e42894778016","Len":1}...
|
1789773007
|
Edit
Delete
|
|
31195
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"b0c8f85aa {"Commits":[{"Sha1":"b0c8f85aaf3e0d5d8581c460a2bebbe2c14e9a85","Message":"docs(治理): 总架构 §1 表前五项复核改记 2026-09-18,图 1 / 图 2 图注同步对齐\n\n按原复算方式对活契约与 runtime/modules.json 重读平台项目 21 / 裁决 39 / 事实 11 /\n实体 168 / 运行时模块 7 五项,取值与 09-17 完全一致,故观测时刻改记 2026-09-18,\n并在 §1 表下补一段复核记:复核是工作区内只读直读,未产出登记报告,证据只绑定本地\n工作区。两张图(图 1 五层与依赖方向、图 2 现存跨应用关系)的图注观测时刻一并改到\n09-18,与表对齐;§0 增补段补一句指向这次改记。\n\n未重跑的五项——派生仓分档、框架版本 L11 / L12、docker ps、文档口径一致性——\n保持 2026-09-17 不动。本轮复跑 check-workspace-consistency.mjs 仍只有 L9 一条\n(COMPOSE_PROJECT_COLLISION,7 个仓共用 api-nestjs project 名),与文中写法一致。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T16:34:29-07:00"}],"HeadCommit":{"Sha1":"b0c8f85aaf3e0d5d8581c460a2bebbe2c14e9a85","Message":"docs(治理): 总架构 §1 表前五项复核改记 2026-09-18,图 1 / 图 2 图注同步对齐\n\n按原复算方式对活契约与 runtime/modules.json 重读平台项目 21 / 裁决 39 / 事实 11 /\n实体 168 / 运行时模块 7 五项,取值与 09-17 完全一致,故观测时刻改记 2026-09-18,\n并在 §1 表下补一段复核记:复核是工作区内只读直读,未产出登记报告,证据只绑定本地\n工作区。两张图(图 1 五层与依赖方向、图 2 现存跨应用关系)的图注观测时刻一并改到\n09-18,与表对齐;§0 增补段补一句指向这次改记。\n\n未重跑的五项——派生仓分档、框架版本 L11 / L12、docker ps、文档口径一致性——\n保持 2026-09-17 不动。本轮复跑 check-workspace-consistency.mjs 仍只有 L9 一条\n(COMPOSE_PROJECT_COLLISION,7 个仓共用 api-nestjs project 名),与文中写法一致。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T16:34:29-07:00"},"CompareURL":"luoanwu/platform-governance/compare/8e5cc87f027dab462c6f3f5bf8f0e42894778016...b0c8f85aaf3e0d5d8581c460a2bebbe2c14e9a85","Len":1}...
|
1789774905
|
Edit
Delete
|
|
31218
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"0bd8704df {"Commits":[{"Sha1":"0bd8704df3bd5cfbed6e6b06cbcf6d211d0da76f","Message":"docs(计划): 登记 docs-truth 那条红的修复 @ 8a621fd / 12093b8\n\n动态区 UI 条目实为三处漂移(SHA、端口、验收库),门禁只抓得到 SHA 一处;只换 SHA 会把红\n变绿却留着两句假话,故三处一并订正。同时记下 freshness-sha-* 的覆盖边界:它只断言 SHA\n的声明形式,同条目里的端口与库名可以静默漂移——绿不代表整行都对。\n\nruntime check 现 exit 0、16 项全过;报告在干净 worktree 整批重出回绑,check:evidence\n降至 0 error。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T17:34:13-07:00"},{"Sha1":"f84a1e12c72975d9a25af5f9fe62413314b9a280","Message":"docs(计划): 登记盲区复核第二轮结果——无新洞,并自查本轮新增的两处接线\n\n四类结果与首轮一致:够不到的检查器 1 个(dev helper 非门禁)、登记报告 0 份无产出方、\n未构建检出逐道跑无新的空跑即绿、流外门禁 5 道复核期均未过期。\n\n自查本轮自己新加的两样是否变成同类盲区:check:fixture-coverage 四处接线齐全;identity\n的两条 freshness 断言经递归展开确认 CI 的 identity job 可达。\n\n同时写清边界:接线正确不等于当前在把关——GitHub Actions 因计费停摆、Gitea 镜像通道从未\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-18T17:29:40-07:00"},{"Sha1":"4a26207d8d4f89aa1b24b7ad4698b6091cc92361","Message":"docs(计划): 登记 identity docs-truth 补 freshness-sha 断言 @ 1f3ff8c / 6687aec\n\n出口二选一取 ②。口径移植自 runtime 版并保留其三条设计判断(不含静态级、未接线跳过而非\n恒红、必须是声明形式);唯一差异是认本仓实际写法 clean commit `sha`。负向三项实做,含\n上游记载过的「SHA 只出现在提交区间里」那条自我假绿陷阱。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T17:25:17-07:00"},{"Sha1":"32f549d3f61c3729d1a00abb65f50df542c84c39","Message":"docs(计划): 登记全仓盲区复核结果与 identity 漂移订正 @ a48cbd6\n\n系统性扫描四类形态,唯一真发现是 identity/reports 完全在新鲜度扫描面之外,且已造成\n一处数字漂移(文档 255 @ 85d538b vs 报告 261 @ 25ead3e),当日已修并补处置说明。\n其余四类均核过且干净,含未构建检出里逐道跑根链验证无新的空跑即绿。\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-18T17:20:38-07:00"},{"Sha1":"c3ae79df23ed6c5e055ef1c5ac6862f14bc477fe","Message":"docs(计划): 登记 fixture-coverage 升格为门禁 @ ab28a95 / 83a5542\n\nOwner 裁方案 B。升格前提是先修掉它自己的假绿:不构建直接跑时 15 个套件全跳过而两个\n总数双双为 0、退出码 0,naive 接进 CI 就是永远绿。只阻断 wiringTotal,nowhereTotal 因\n改进过程中非单调只记不拦。另修一处证据污染:显式 --suite 不再写仓级报告。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T17:13:51-07:00"}],"HeadCommit":{"Sha1":"0bd8704df3bd5cfbed6e6b06cbcf6d211d0da76f","Message":"docs(计划): 登记 docs-truth 那条红的修复 @ 8a621fd / 12093b8\n\n动态区 UI 条目实为三处漂移(SHA、端口、验收库),门禁只抓得到 SHA 一处;只换 SHA 会把红\n变绿却留着两句假话,故三处一并订正。同时记下 freshness-sha-* 的覆盖边界:它只断言 SHA\n的声明形式,同条目里的端口与库名可以静默漂移——绿不代表整行都对。\n\nruntime check 现 exit 0、16 项全过;报告在干净 worktree 整批重出回绑,check:evidence\n降至 0 error。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T17:34:13-07:00"},"CompareURL":"luoanwu/platform-governance/compare/b0c8f85aaf3e0d5d8581c460a2bebbe2c14e9a85...0bd8704df3bd5cfbed6e6b06cbcf6d211d0da76f","Len":8}...
|
1789778300
|
Edit
Delete
|
|
31220
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"dea10cf11 {"Commits":[{"Sha1":"dea10cf1124b0e7714fe60f395709cda0be55fdb","Message":"docs(计划): 登记推送结果与两条实测更正 @ a178ba3\n\n三处远端均已推送并核对 SHA 一致。过程中查出 main 分支保护整个消失(404 Branch not\nprotected,非只摘必需检查)与计费仍未恢复(run 35410044850 三 job failure、注解逐字\n未变)两条,已补进 CLAUDE.md 云端治理段。\n\n按事实作用域,现在只能说到「远端已有该 SHA」,不能说「远端 CI 已通过」。保护由谁摘、\n为何摘未知,本会话未改动任何 GitHub 设置,留给仓库管理权限持有者二选一收口。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T17:45:36-07:00"}],"HeadCommit":{"Sha1":"dea10cf1124b0e7714fe60f395709cda0be55fdb","Message":"docs(计划): 登记推送结果与两条实测更正 @ a178ba3\n\n三处远端均已推送并核对 SHA 一致。过程中查出 main 分支保护整个消失(404 Branch not\nprotected,非只摘必需检查)与计费仍未恢复(run 35410044850 三 job failure、注解逐字\n未变)两条,已补进 CLAUDE.md 云端治理段。\n\n按事实作用域,现在只能说到「远端已有该 SHA」,不能说「远端 CI 已通过」。保护由谁摘、\n为何摘未知,本会话未改动任何 GitHub 设置,留给仓库管理权限持有者二选一收口。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T17:45:36-07:00"},"CompareURL":"luoanwu/platform-governance/compare/0bd8704df3bd5cfbed6e6b06cbcf6d211d0da76f...dea10cf1124b0e7714fe60f395709cda0be55fdb","Len":1}...
|
1789778936
|
Edit
Delete
|
|
31230
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"078af5fc6 {"Commits":[{"Sha1":"078af5fc66585384df768683780239154d06dc7b","Message":"docs(计划): 登记本会话——C-3 宿主协议签收面首次有落点,并附三处自查出的自造缺陷\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T19:41:03-07:00"},{"Sha1":"c777303990ce57b7b331c10c8d135b455238797a","Message":"docs(基础): 开发环境.md 重写到 2026-09-18 实测——修掉两条已不成立的声明并补端口盘\n\n原文停在 2026-09-04,两条声明已不成立:\n- 「派生仓现存 3 个」——派生仓状态.json 实为 active 0 / archived 0 / missing 1 / retired 18;\n- 路径 `AI数字员工/digital-employee-os` 不存在,实为 `数字员工OS/digital-employee-os`。\n\n补上原文完全没有的本机端口盘(41 个运行容器 / 6 个栈):enterprise-platform-stack\nPG 55470 / Redis 56379 / runtime 53001 / Caddy 58080,ep-delivery-20260917 PG 55481,\nbase-framework PG 5432 / Redis 6379,hi-atelier,deos-local-verify,deos-acceptance-redis 6404。\n新增 §4 工作区一致性门禁一节(当日 CLEAN,14 仓 / 8346 文件 / 4462 链接 / 22 份 compose)。\n\n§5 已知差异按当日实测重写:\n- deos-local-verify 栈不完整——gateway 的 nginx 找不到上游 api-active(该栈无 api 容器),\n 已连续重启 2946 次,当日 docker stop 停下,容器保留可 start 恢复;根因属 OS 层未查。\n- base-framework-app 容器已不存在,当日随 73 个死容器清理,原文那条「看 3500—3502」作废。\n- 7 个上层应用仓仍无 F14 守卫,compose 身份复发只能靠工作区 L9 兜住。\n\n文内每条命令均当场复核过输出与文中声明一致;旧版两条错误声明与初始化经过移入文末「历史记录」,\n不删除。门禁 check-workspace-consistency.mjs 重写后仍 CLEAN(exit 0 / 0 issues)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T19:17:52-07:00"},{"Sha1":"c894b8ce4445a7e939a0a8d5022dfb526aa3f1a5","Message":"docs(决策): N-11 关闭——七个仓补齐 compose 身份,L9 转 CLEAN,并更正两处前置\n\n选项 ① 已执行:七个仓的 apps/api-nestjs/docker-compose.yml 各补\n`name: ${COMPOSE_PROJECT_NAME:-\u003c本仓 package.json name\u003e}`,各仓本地提交(未推远端)。\ndocker compose config 逐份实测 project 名互不相同、卷已变为 \u003cname\u003e_*;\ncheck-workspace-consistency.mjs 由 ISSUES 转 CLEAN(exit 0 / 0 issues)。\n\n两处更正写进条目:\n- 数量是 7 个仓不是 8 个。09-17 清单里的数字员工OS 此后已自行补上 name:,本轮不在名单内。\n- 本条一直把「共用卷里的数据归谁」列为选 ①/② 的前置,实测**该前置是空的**:\n 本机 260 个卷无任何 api-nestjs_*,project=api-nestjs 零命中,这七份 compose 在本机\n 从未以默认推导名起过;已存在的 juhai-knowledge-cloud / juhai-quotation 两个 project 的\n config_files 指向工作区外的另一棵树,与本条无关。故零数据迁移,且该结论只绑本机。\n\n未随本条关闭:选项 ② 的防复发半边。七个仓仍无 F14 守卫,仓内 pnpm check 在冲突状态下\n依旧会绿,复发只能靠工作区 L9 兜住——另行派活。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T19:14:16-07:00"}],"HeadCommit":{"Sha1":"078af5fc66585384df768683780239154d06dc7b","Message":"docs(计划): 登记本会话——C-3 宿主协议签收面首次有落点,并附三处自查出的自造缺陷\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T19:41:03-07:00"},"CompareURL":"luoanwu/platform-governance/compare/dea10cf1124b0e7714fe60f395709cda0be55fdb...078af5fc66585384df768683780239154d06dc7b","Len":3}...
|
1789786684
|
Edit
Delete
|
|
31234
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ea1054cc6 {"Commits":[{"Sha1":"ea1054cc672f778229bd51b5c4327884a98b9236","Message":"docs(决策): CHG-020 材料成稿 + 采纳形态对照 §5.6 收口 G-10 @ 0ec2442\n\n- 采纳形态覆盖度对照增 §5.6:「采纳的组件自身不在被观测面内」此前在 G-1…G-9 的对照表里\n 没有位置——那张表问的是原规则的判定有没有被承接,没问承接方自己看得见吗。Collector\n 是被观测的(Prometheus 回抓 :8888 + 三条告警),Caddy 完全在外面。trace / metrics /\n logs 三面同日关闭,实现与实测在真源仓 0ec2442 / 72df024。\n- 开发计划:候选 OpenAPI 6 → 11 份(2026-09-18 增五份宿主契约)、CHG-020 进「材料已成\n 待签署」行、新增 G-16 行(契约登记面的门禁覆盖)、裁决队列 ③ a 项加 CHG-020 并注明\n 签署前先答其 §0 的方向题(偏差 #39)。\n- CHG-020 材料五份:四份宿主契约由候选转正式登记,含门禁扩面(check:candidate-contracts\n 扫两目录 + 反向规则 REGISTERED_STILL_PENDING)。本包未改动任何文件,§0 挂着一处\n blocked_by 方向循环待 Catalog Owner 定口径:签收单侧写「先登记后签收」,五份候选的\n x-enterprise-blocked-by 写的是「先签收后登记」。\n\n一致性门禁 CLEAN(本次提交前实测)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T22:55:09-07:00"}],"HeadCommit":{"Sha1":"ea1054cc672f778229bd51b5c4327884a98b9236","Message":"docs(决策): CHG-020 材料成稿 + 采纳形态对照 §5.6 收口 G-10 @ 0ec2442\n\n- 采纳形态覆盖度对照增 §5.6:「采纳的组件自身不在被观测面内」此前在 G-1…G-9 的对照表里\n 没有位置——那张表问的是原规则的判定有没有被承接,没问承接方自己看得见吗。Collector\n 是被观测的(Prometheus 回抓 :8888 + 三条告警),Caddy 完全在外面。trace / metrics /\n logs 三面同日关闭,实现与实测在真源仓 0ec2442 / 72df024。\n- 开发计划:候选 OpenAPI 6 → 11 份(2026-09-18 增五份宿主契约)、CHG-020 进「材料已成\n 待签署」行、新增 G-16 行(契约登记面的门禁覆盖)、裁决队列 ③ a 项加 CHG-020 并注明\n 签署前先答其 §0 的方向题(偏差 #39)。\n- CHG-020 材料五份:四份宿主契约由候选转正式登记,含门禁扩面(check:candidate-contracts\n 扫两目录 + 反向规则 REGISTERED_STILL_PENDING)。本包未改动任何文件,§0 挂着一处\n blocked_by 方向循环待 Catalog Owner 定口径:签收单侧写「先登记后签收」,五份候选的\n x-enterprise-blocked-by 写的是「先签收后登记」。\n\n一致性门禁 CLEAN(本次提交前实测)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T22:55:09-07:00"},"CompareURL":"luoanwu/platform-governance/compare/078af5fc66585384df768683780239154d06dc7b...ea1054cc672f778229bd51b5c4327884a98b9236","Len":1}...
|
1789798059
|
Edit
Delete
|
|
31235
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"705fb456d {"Commits":[{"Sha1":"705fb456d585cf4825078b6af0e2ef9d41ecd5f5","Message":"docs(计划): 登记本会话——松散端 A 组 16 条全部做完,并附三处清单口径更正与一处新缺陷\n\n- §1 两行按当天实测改:运行证据行的 mainline 由四套件改**六套件 72 例**(A15 新接的\n permission-ops 2 / ai-route-persistence 5)、绑定改 `51f100b`、治理测试 444 → 449;\n 证据新鲜度行原写「35 份全部新鲜、0 过期 / 0 告警」,**与实测差得远**(开工时是 5 error\n + 14 warning),整行改为 `partial @ 3be0bb7`(45 份 / 41 新鲜 / 4 过期 / 0 error)并写清\n 收口过程与余下 4 条为何还在。\n- §8 账本增当天一行:A1—A16 逐项做法与实测出口、三处清单本身给错的口径(Prometheus\n 端口与无 lifecycle 标志、陈旧 worktree 属治理仓、reports:rebind 的覆盖面)、一处新查出\n 的缺陷(`pnpm test` 与 `GOV_REPORT_DIR` 互相抵消,没有一种跑法既不污染又全绿),以及\n B1—B11 十一项待裁的归属与本轮各做到哪一步。\n\n一致性门禁 CLEAN,`prunableWorktrees` 归零。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T00:08:42-07:00"},{"Sha1":"f2e130d38b5a8ae5d7f18d7a717bf1fb89f02b08","Message":"docs(数字): 文档订正第三批(治理层侧)—— §1 的五处报告绑定全不对,并修三个数\n\n按各报告 `provenance.gitSha` 逐份实测,§1「运行 / UI 证据」一行原先**五处绑定全不对**:\n\n| 报告 | 原写 | 实测 |\n|---|---|---|\n| runtime-acceptance | `765300b` | `8a621fd` |\n| ui-acceptance | `003aadd` | `67e8193` |\n| mainline-acceptance | `bc978a8` | `8a621fd` |\n| mainline-restore | `bc978a8` | `765300b` |\n| identity-ui | `828f178` | `46265a6` |\n\n五份 `worktreeDirty` 均 false;用例数(775 / 5·1 / 11·17·19·18 / 3 库 / 2)逐份核对无误,\n错的只是绑定——而绑定正是「这个结论由哪个提交支撑」的唯一定位手段。\n\n另修三个数:\n- `check:fixtures` 17 套件 **189 例 → 702 例**(这条现已有 `check:doc-claims` 机器守);\n- 治理测试 **277/277 → 444(443 通过 / 1 skipped)**;\n- 撤权 SLA cacheBound p95 **5042 ms → 5027.7 ms**(invalidationPush 122 ms 与其\n `measured-with-harness-transport` 的定性无误,不动);\n- Release Manifest 绑定 `71b306f` → `2e06b92`(本日重跑回绑;缺 6 项不变)。\n\n一致性门禁 CLEAN。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T23:32:28-07:00"},{"Sha1":"aa8550683e912d5442a0e8248915ccdb95a36f10","Message":"docs(事实): 文档订正第二批(治理层侧)—— 镜像落后数、「分叉」定性、worktree 与 check 链描述\n\n- 开发计划三处镜像声明:「落后 Gitea 245 个提交」→ **41 个提交**(`github/main` =\n `51e311b`,2026-09-18 23:20 实测)。§1 仓与远端一行整行重写:本地 main = Gitea\n `origin/main` = `12bed2f`、0 个未推提交;本地分支 46 条(含 main),其中 30 条领先\n main、15 条已被 main 完全吸收。\n- §8「两远端分叉扩大」**定性也错了**:GitHub 侧 0 个独有提交,不是分叉,是纯落后;\n 同条里「直推已实证不可行」也已不成立(分支保护其间消失)。三处一并订正并留痕。\n- `企业控制面/CLAUDE.md` 两处:① `.worktrees/` 实测是**两条**(security-governance-hardening\n + docs/registry-blueprint-record),另有一条在本目录之外的 `/private/tmp/ep-delivery-20260917`,\n 并写明权威口径是 `git worktree list` 而不是本表;② 仓根 `pnpm check` 由「静态门禁链」\n 改为逐环列出的 **20 环**,并记下本会话实测到的坑——第 15 环 `pnpm test` 会改写\n `reports/caddy.latest.json`,而用 `GOV_REPORT_DIR` 规避改写又会让 12 个回读仓内报告\n 路径的用例判红,两者互相抵消,跑完整链后须 `git status` 看一眼。\n\n一致性门禁 CLEAN(4491 条链接)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T23:27:24-07:00"},{"Sha1":"e707f1df114df1b3eaeaa8731fd21efe9354933f","Message":"docs(状态): 文档订正第一批(治理层侧)—— ai-gateway 档位、工作台交付 ② 状态、A-7 事实数\n\n与真源仓同批(见 enterprise-platform 同日提交):\n\n- `企业控制面/README.md` AI 与集成行:`ai-gateway` 模块 `state=shape` → `authority`\n (2026-09-17 `ai-route.v1` 第一批转权威账本)。\n- 开发计划 §状态行、交付五步行、领取队列 ④ 三处:工作台交付 ② 由「▶ 可开工」改为\n 「🟡 进行中」。理由是实测——WB-1 脚手架、目录读面、受控执行面第一条、同源托管 +\n 入口 forward_auth、服务目录环境列探针均已落,**未闭合的是阶段 ② 验收本身**\n (目标环境四页 + `check:deployed`)。原写法会让读者以为一行代码都还没写。\n- 基础设施文档 README 的开发计划摘要同步(「前置只余 OPS-3 第一条」已不成立)。\n- 决策批次-2026-09-16 A-7:`check:facts` 登记 1 / 候选 15 是裁决当时的盘面,保留历史\n 取值并标注 2026-09-18 实测的 11 / 5。\n\n一致性门禁 CLEAN。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T23:23:51-07:00"},{"Sha1":"a5d023f2ee1eb81503166218eceece073ab2e2bb","Message":"docs(计划): 并回陈旧 worktree 独有的「第四处同病」账本行,并补上一提交漏改的 L13 收纳数\n\n- A6:`claude/zealous-tu-6f0fca` 这个 worktree 挂在盘上两天,相对 main 只有一条独有内容——\n 开发计划.md 里「第四处同病」那条账本行(revocation-sla 的报告由用例自己在 beforeAll 起手\n 无条件写 failed,adda76a 的 runner 侧修复没覆盖到;同日已修 08c3788)。手工插回它自称的\n 位置(「本表上一条」= 验收 runner 三处同病那条,按最新在上的表序即其正上方),而不是\n cherry-pick:该分支另有 6 行是 main 早已推进过的旧版本,整条并回会把状态倒退。\n- 同时修掉上一提交(ea1054c)漏掉的一处:CHG-020 材料 5 个文件进仓后,\n `平台治理/README.md` 收纳表的 `doc/` 数没跟着改,一致性门禁 L13 判 GOVERNANCE_COUNT_DRIFT\n (声明 149 / 实为 154)。已改 154,并把材料区间写到 CHG-001~020。门禁复跑 CLEAN。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T23:10:48-07:00"}],"HeadCommit":{"Sha1":"705fb456d585cf4825078b6af0e2ef9d41ecd5f5","Message":"docs(计划): 登记本会话——松散端 A 组 16 条全部做完,并附三处清单口径更正与一处新缺陷\n\n- §1 两行按当天实测改:运行证据行的 mainline 由四套件改**六套件 72 例**(A15 新接的\n permission-ops 2 / ai-route-persistence 5)、绑定改 `51f100b`、治理测试 444 → 449;\n 证据新鲜度行原写「35 份全部新鲜、0 过期 / 0 告警」,**与实测差得远**(开工时是 5 error\n + 14 warning),整行改为 `partial @ 3be0bb7`(45 份 / 41 新鲜 / 4 过期 / 0 error)并写清\n 收口过程与余下 4 条为何还在。\n- §8 账本增当天一行:A1—A16 逐项做法与实测出口、三处清单本身给错的口径(Prometheus\n 端口与无 lifecycle 标志、陈旧 worktree 属治理仓、reports:rebind 的覆盖面)、一处新查出\n 的缺陷(`pnpm test` 与 `GOV_REPORT_DIR` 互相抵消,没有一种跑法既不污染又全绿),以及\n B1—B11 十一项待裁的归属与本轮各做到哪一步。\n\n一致性门禁 CLEAN,`prunableWorktrees` 归零。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T00:08:42-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ea1054cc672f778229bd51b5c4327884a98b9236...705fb456d585cf4825078b6af0e2ef9d41ecd5f5","Len":5}...
|
1789801725
|
Edit
Delete
|
|
31237
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"7e11860ff {"Commits":[{"Sha1":"7e11860ff60ecbcf1c10f1c0a578263f6e39e7b0","Message":"docs(计划): 镜像落后数三处更新到收尾实测 53(23:20 量到的 41 已被本会话自己的 12 个提交推开)\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-19T00:13:51-07:00"}],"HeadCommit":{"Sha1":"7e11860ff60ecbcf1c10f1c0a578263f6e39e7b0","Message":"docs(计划): 镜像落后数三处更新到收尾实测 53(23:20 量到的 41 已被本会话自己的 12 个提交推开)\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-19T00:13:51-07:00"},"CompareURL":"luoanwu/platform-governance/compare/705fb456d585cf4825078b6af0e2ef9d41ecd5f5...7e11860ff60ecbcf1c10f1c0a578263f6e39e7b0","Len":1}...
|
1789802036
|
Edit
Delete
|
|
31239
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/claude/laughing-rhodes-1236b1
|
0
|
|
1789803105
|
Edit
Delete
|
|
31240
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/claude/laughing-rhodes-1236b1
|
0
|
{"Commits":[{"Sha1":"761786d97 {"Commits":[{"Sha1":"761786d97015a39c32fe8fb74680c9cdd3513fb8","Message":"docs(计划): 登记治理测试两条跑法合上(真源仓 7021758),CLAUDE.md 那处坑改为已修\n\n- `企业控制面/CLAUDE.md` check 链描述:第 15 环 `pnpm test` 原先「不设 GOV_REPORT_DIR\n 会脏绑 reports/caddy.latest.json、设了又让 12 个用例判红、两者互相抵消」,改为已修,\n 并写明现在的判据(两条跑法都 0 失败、不设变量跑完 reports/ 一份不改写)与\n `report-clobber.test.mjs` 现存的唯一一条具名豁免。\n- `平台治理/基础设施文档/开发计划.md` §8 账本增一行,收口上一行「松散端 A 组」那次\n 留下的「一处新缺陷(已登记,未修)」。\n\n**与并行会话重叠一处**:同一句 CLAUDE.md 描述,并行会话在主检出的工作树里已另改过一版\n(连同它新增的 `stub-surface` 环,链写成 21 环、`pnpm test` 前移为第 16 环)。那版此刻\n尚未提交,且它描述的门禁在仓里还是未跟踪文件,所以本提交按**当前已提交状态**写(20 环 /\n第 15 环)。两版说的是同一件事,合并时取环数与新增门禁都对得上的那版即可。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T00:31:33-07:00"}],"HeadCommit":{"Sha1":"761786d97015a39c32fe8fb74680c9cdd3513fb8","Message":"docs(计划): 登记治理测试两条跑法合上(真源仓 7021758),CLAUDE.md 那处坑改为已修\n\n- `企业控制面/CLAUDE.md` check 链描述:第 15 环 `pnpm test` 原先「不设 GOV_REPORT_DIR\n 会脏绑 reports/caddy.latest.json、设了又让 12 个用例判红、两者互相抵消」,改为已修,\n 并写明现在的判据(两条跑法都 0 失败、不设变量跑完 reports/ 一份不改写)与\n `report-clobber.test.mjs` 现存的唯一一条具名豁免。\n- `平台治理/基础设施文档/开发计划.md` §8 账本增一行,收口上一行「松散端 A 组」那次\n 留下的「一处新缺陷(已登记,未修)」。\n\n**与并行会话重叠一处**:同一句 CLAUDE.md 描述,并行会话在主检出的工作树里已另改过一版\n(连同它新增的 `stub-surface` 环,链写成 21 环、`pnpm test` 前移为第 16 环)。那版此刻\n尚未提交,且它描述的门禁在仓里还是未跟踪文件,所以本提交按**当前已提交状态**写(20 环 /\n第 15 环)。两版说的是同一件事,合并时取环数与新增门禁都对得上的那版即可。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T00:31:33-07:00"},"CompareURL":"luoanwu/platform-governance/compare/7e11860ff60ecbcf1c10f1c0a578263f6e39e7b0...761786d97015a39c32fe8fb74680c9cdd3513fb8","Len":1}...
|
1789803105
|
Edit
Delete
|
|
31241
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/claude/laughing-rhodes-1236b1
|
0
|
{"Commits":[{"Sha1":"f8cebdaec {"Commits":[{"Sha1":"f8cebdaeca41316d8f1ea7745265ec8abf8311a3","Message":"docs(计划): §8 账本登记治理测试两条跑法合上(真源仓 7021758)\n\n收口上一行「松散端 A 组」那次留下的「一处新缺陷(已登记,未修)」:治理测试里 spawn\n门禁 CLI 的用例没把报告落盘目录钉死,于是不设 `GOV_REPORT_DIR` 跑会脏绑\n`reports/caddy.latest.json`、设了又让 12 个跑在临时沙箱里的用例判红。本轮逐个钉死,\n两条跑法实测都是 471 例 470 通过 / 0 失败 / 1 跳过,且不设变量那次跑前跑后\n`reports/*.json` 的 md5 逐份不变、`git status --porcelain` 为空。\n\n`企业控制面/CLAUDE.md` 那处 check 链描述不在本提交里:并行会话已在 `4a9dad2` 改过\n同一句,且连同它新增的 `stub-surface` 环写成了 21 环 / 第 16 环,比本会话按当前\n20 环写的那版更跟得上现状,故撤回自己那版,不制造同行冲突。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T00:31:33-07:00"}],"HeadCommit":{"Sha1":"f8cebdaeca41316d8f1ea7745265ec8abf8311a3","Message":"docs(计划): §8 账本登记治理测试两条跑法合上(真源仓 7021758)\n\n收口上一行「松散端 A 组」那次留下的「一处新缺陷(已登记,未修)」:治理测试里 spawn\n门禁 CLI 的用例没把报告落盘目录钉死,于是不设 `GOV_REPORT_DIR` 跑会脏绑\n`reports/caddy.latest.json`、设了又让 12 个跑在临时沙箱里的用例判红。本轮逐个钉死,\n两条跑法实测都是 471 例 470 通过 / 0 失败 / 1 跳过,且不设变量那次跑前跑后\n`reports/*.json` 的 md5 逐份不变、`git status --porcelain` 为空。\n\n`企业控制面/CLAUDE.md` 那处 check 链描述不在本提交里:并行会话已在 `4a9dad2` 改过\n同一句,且连同它新增的 `stub-surface` 环写成了 21 环 / 第 16 环,比本会话按当前\n20 环写的那版更跟得上现状,故撤回自己那版,不制造同行冲突。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T00:31:33-07:00"},"CompareURL":"luoanwu/platform-governance/compare/761786d97015a39c32fe8fb74680c9cdd3513fb8...f8cebdaeca41316d8f1ea7745265ec8abf8311a3","Len":1}...
|
1789803290
|
Edit
Delete
|
|
31242
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"cf82ac49a {"Commits":[{"Sha1":"cf82ac49afd4e6da0307bf0f0e1e255be6701bab","Message":"docs(治理): workspace.json 补五层职责字段——层定义此前只在总架构图 PNG 里\n\nterminology.layers 每层加 responsibility,五句逐字取自根目录\n「AI 应用开发的企业应用群总架构图.png」的层图注。此前本文件只有\nterm / alias / directory / order,五层「是什么」没有任何机器口径,\n于是既无法被引用,也无法反驳把基础基座与基础框架压成一格\nBASE_ASSET / asset 的 Catalog 登记(platform-projects.json)。\n\n职责是应然口径,不是现状声明——该图已由\n平台治理/企业应用群总架构-2026-09-17.md §2.1 定性为愿景图并记了三处过期。\n平台治理不在图上,不给该字段(其原有 note 已说明)。\n\nnote 内一并记录两处现存措辞不一致,本提交不改它们:\n- 数字员工OS/README.md 首句作「运行时宿主,装载并串接……」,弱于图注的「运行与控制中枢」\n- 工程基础框架/README.md 标题自称「基础资产」而非层名\n另三层 README 首句与图注逐字一致。\n\n纯加法:唯一消费方 平台治理/基础/scripts/lib/domain-layer-core.mjs 的\nlayerIndex() 只读 directory / term,复算映射仍 6 条、取值未变。\n门禁 check-workspace-consistency.mjs --json → status=CLEAN / issues=0 / EXIT=0\n(14 仓 8371 文件 4493 链接,2026-09-19,工作区作用域)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T00:59:20-07:00"},{"Sha1":"4a9dad2c0559feeb66d3c74e4720e70d5bedf698","Message":"docs(治理): 门禁链 20 → 21 环——真源仓新增 check:stub-surface,并订正 pnpm test 两条跑法的已合口径\n\n- `pnpm check` 增第 12 环 `check:stub-surface`(真源仓 `6986527`):把「失败关闭的桩 /\n 只在登记里或只在测试夹具里装配 / 环境开关决定走哪条分支」三种未落地形态扫成清单,\n 34 条逐条登记在 `enterprise-platform/governance/stub-surface.json`(只写为什么还在,\n 清单本身由门禁从源码推导),并守住仓根 CLAUDE.md 对清单数字的声明。环数与序号跟着改:\n `pnpm test` 由第 15 环变第 16 环。\n- 订正同句尾巴:本条此前写「`pnpm test` 会改写 `reports/caddy.latest.json`,而设\n `GOV_REPORT_DIR` 规避又会让 12 个回读仓内报告路径的用例判红,两者互相抵消」。该状态已由\n 真源仓 `7021758` 合上——2026-09-19 在干净树上两条跑法各跑一遍实测:均 471 例\n 470 通过 / 0 失败 / 1 跳过,且不设 `GOV_REPORT_DIR` 时 `reports/` 一个字节不动。\n\n`node 平台治理/基础/scripts/check-workspace-consistency.mjs` 合计 0 条\n(14 个仓 / 8370 份受控文件,L4 断链 0 / L13 数字声明 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-19T00:30:44-07:00"}],"HeadCommit":{"Sha1":"cf82ac49afd4e6da0307bf0f0e1e255be6701bab","Message":"docs(治理): workspace.json 补五层职责字段——层定义此前只在总架构图 PNG 里\n\nterminology.layers 每层加 responsibility,五句逐字取自根目录\n「AI 应用开发的企业应用群总架构图.png」的层图注。此前本文件只有\nterm / alias / directory / order,五层「是什么」没有任何机器口径,\n于是既无法被引用,也无法反驳把基础基座与基础框架压成一格\nBASE_ASSET / asset 的 Catalog 登记(platform-projects.json)。\n\n职责是应然口径,不是现状声明——该图已由\n平台治理/企业应用群总架构-2026-09-17.md §2.1 定性为愿景图并记了三处过期。\n平台治理不在图上,不给该字段(其原有 note 已说明)。\n\nnote 内一并记录两处现存措辞不一致,本提交不改它们:\n- 数字员工OS/README.md 首句作「运行时宿主,装载并串接……」,弱于图注的「运行与控制中枢」\n- 工程基础框架/README.md 标题自称「基础资产」而非层名\n另三层 README 首句与图注逐字一致。\n\n纯加法:唯一消费方 平台治理/基础/scripts/lib/domain-layer-core.mjs 的\nlayerIndex() 只读 directory / term,复算映射仍 6 条、取值未变。\n门禁 check-workspace-consistency.mjs --json → status=CLEAN / issues=0 / EXIT=0\n(14 仓 8371 文件 4493 链接,2026-09-19,工作区作用域)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T00:59:20-07:00"},"CompareURL":"luoanwu/platform-governance/compare/7e11860ff60ecbcf1c10f1c0a578263f6e39e7b0...cf82ac49afd4e6da0307bf0f0e1e255be6701bab","Len":2}...
|
1789804817
|
Edit
Delete
|
|
31244
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"7ad320a65 {"Commits":[{"Sha1":"7ad320a65b921c9d68a4ab48df81241998e64867","Message":"docs(决策): 写回 CHG-021 材料的 README——77aaf85 里存进去的那份不是本包内容\n\n事故与更正,如实记:本包 README 于 2026-09-19 01:53 写成,提交 77aaf85 于约 02:0x 落库;\n两者之间另一并行会话(九域/六域收编那条线)在同一路径写入了它自己的材料,而我提交前\n只核了文件名清单、没核文件内容,于是 77aaf85 存进去的是它的「CHG-021-C3-NINE-DOMAIN-MODULE-INTAKE」,\n本包的 README 从未真正入库。四份 delta 与 DEC-040 草案未被波及,一直是本包内容(changeId 均为\nCHG-021-HOSTED-MODULE-PROMOTION),可据以复核本文与它们是否一致。\n\n本次按本会话原稿写回,内容与四份 delta 逐项对齐,并补一节「与 CHG-022 的分工」:\n- CHG-021(本包)= C11 公共文件 / C12 通知与 Webhook / C13 配置与功能开关三条**有真实现与存量\n 消费者**的托管能力升格,要处理权威状态迁移、宿主改造与回切;\n- CHG-022 = 其余六个**零运行面**契约域(C15—C19 + C01)的收编。\n两包范围不重叠。编号维持现状:并行会话已自取 CHG-022 并在其材料里引用本包为 CHG-021,\n无须改号。\n\n链接自检:8 条相对链接逐条验在(含新增的 ../CHG-022-材料/README.md)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:21:58-07:00"},{"Sha1":"e8d488b2bf75395b2aae4a653146440a624073f1","Message":"docs(治理): 收纳表随 DEC-040 / CHG-021 落地改数——doc/ 154 → 160,编号区间跟到 040 / 021\n\nL13(治理层自己的数字声明与 git ls-files 不符)在上一条提交后即判红:收纳表写 154,实为 160。\n六个文件全部来自 77aaf85(DEC-040 草案 1 份 + CHG-021 材料 5 份)。同时把区间描述从\nDEC-001~039 / CHG-001~020 跟到 DEC-001~040 / CHG-001~021。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:10:28-07:00"},{"Sha1":"77aaf8599b0379a71bf3eed4e07fa93e08317325","Message":"docs(决策): DEC-040 托管能力升格为平台运行时模块 + CHG-021 受控变更包(均待签署)\n\n目录负责人 2026-09-19 提出「托管模块应该直接迁进本仓」。该指示与三处已批准口径相反\n(Q01「不得以方便实现自动新增 M8」、设计方案第 155 行「三消费者 + G4 后用 scaffold 加模块」、\n第 35 行把自动服务化文件/通知/配置列为非目标),故先成裁决材料,批准后实现才有依据。\n\nDEC-040 草案(待批准):\n- 底账:三条能力的代码两半都已在本仓(规则 2026-09-14 进 contracts/src/domain,副作用\n 2026-09-18 进 runtime/clients),没有的是运行服务与权威状态——后者仍完整在工单宿主。\n- 消费者实测 3 / 3 / 1;配置的三消费者条件按建议 Decision 第 4 条显式豁免,带回看期\n 2027-03-19 与 single-consumer 接口标记。\n- 补齐 Q01 要求的两个宿主方案成本与迁移影响对比(不做这张表,本裁决不满足自己的准入条件)。\n- 写明两处代价:① 验收等级如实由 E2 降到 E0(宿主实现的 E2 不证明平台实现);② 业务外键\n (Attachment.ticket_id 必填 + Cascade、Notification 唯一键含 escalation_id)必须断开,\n 级联删除语义要由宿主显式调用重建。\n- 内核无对应端口且 kernel 由仓外框架 Owner 发布,故升格出的模块 provides 为空、消费面只有 HTTP。\n\nCHG-021 材料(待 DEC-040 批准 + Catalog Owner 签署,本包未改动任何文件):\n- 四份 delta:decisions / platform-projects / modules / catalog-map,各带当前值与目标值。\n- 逐行核过 check:modules(第 45—57 行)的六条判据并写进应用顺序;登记面与模块骨架必须同批落地。\n- 附实施工作包七步链与已知风险;顺带记录三条模块登记会补上 Release Manifest 少三行的现存缺口。\n\n自检:四份 delta JSON 合法;两份文档 10 条相对链接逐条验在。治理层一致性检查只扫已跟踪文件,\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-19T02:08:58-07:00"}],"HeadCommit":{"Sha1":"7ad320a65b921c9d68a4ab48df81241998e64867","Message":"docs(决策): 写回 CHG-021 材料的 README——77aaf85 里存进去的那份不是本包内容\n\n事故与更正,如实记:本包 README 于 2026-09-19 01:53 写成,提交 77aaf85 于约 02:0x 落库;\n两者之间另一并行会话(九域/六域收编那条线)在同一路径写入了它自己的材料,而我提交前\n只核了文件名清单、没核文件内容,于是 77aaf85 存进去的是它的「CHG-021-C3-NINE-DOMAIN-MODULE-INTAKE」,\n本包的 README 从未真正入库。四份 delta 与 DEC-040 草案未被波及,一直是本包内容(changeId 均为\nCHG-021-HOSTED-MODULE-PROMOTION),可据以复核本文与它们是否一致。\n\n本次按本会话原稿写回,内容与四份 delta 逐项对齐,并补一节「与 CHG-022 的分工」:\n- CHG-021(本包)= C11 公共文件 / C12 通知与 Webhook / C13 配置与功能开关三条**有真实现与存量\n 消费者**的托管能力升格,要处理权威状态迁移、宿主改造与回切;\n- CHG-022 = 其余六个**零运行面**契约域(C15—C19 + C01)的收编。\n两包范围不重叠。编号维持现状:并行会话已自取 CHG-022 并在其材料里引用本包为 CHG-021,\n无须改号。\n\n链接自检:8 条相对链接逐条验在(含新增的 ../CHG-022-材料/README.md)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:21:58-07:00"},"CompareURL":"luoanwu/platform-governance/compare/cf82ac49afd4e6da0307bf0f0e1e255be6701bab...7ad320a65b921c9d68a4ab48df81241998e64867","Len":3}...
|
1789810066
|
Edit
Delete
|
|
31246
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"87c3722f6 {"Commits":[{"Sha1":"87c3722f6c778c786ea50eba75bc5806fa300b0b","Message":"docs(决策): DEC-041 零运行面契约域收编为平台运行时模块 + CHG-022 受控变更包(均待签署)\n\n目录负责人 2026-09-19 提出「调度跨域、企业 IM、数据分析、统一体验、成本容量 + 应用与\n契约注册中心,应该直接放到企业控制面作为运行时模块;企业控制面要支持运行时模块的新增\n和删除」。该指示与已批准的 决策批次-2026-09-16 C-3 相反——C-3 的承接表把这几项裁给上层\n既有宿主,附条件「不新增 M8」「宿主协议签收才算准入」——故先成裁决材料,批准后实现才有依据。\n\n范围与 DEC-040 / CHG-021 划清:那一对管 C11—C13 三条有真实现的托管能力,本对管六个\n零运行面的域(C15 / C16 / C17 / C18 / C19 + C01)。两包独立签署、互不为前置(目录负责人当日定案)。\n\nDEC-041 草案(待批准):\n- Q01 备选条款是唯一合法入口,其触发条件经实测成立,且成立得比该条款预想的彻底:C-3\n 指定的五个宿主里三个不存在——C17「已有分析产品宿主」在业务应用层四个 + 企业领域应用层\n 四个里无一是分析产品;C19「复用 C17」随之落空;C15「业务应用的托管流程执行器」全工作区\n grep 零命中,最接近的工单仓 AutomationRun.ticketId 是必填外键 + onDelete Cascade,绑死\n 单张工单。一个须新建(C16 要的 Conversation/Membership/Message 工单 schema 里没有,而\n C-3 自己要求与 TicketMessage 分开),一个不是状态宿主(C18)。不是「评估后认为不足」,\n 是没有评估对象。\n- 补齐 Q01 要求的两个宿主方案成本与迁移影响对比(不做这张表,本裁决不满足自己的准入条件):\n 逐域给 C-3 指定者 + 全工作区内另找的最接近者,两个候选都评。\n- 一处此前没有材料提过的事实:这六项的 Catalog hosted_by 早就是 enterprise-platform。\n 登记面一直说它们归控制面,是 C-3 把运行宿主裁给了上层——本件是把裁决对齐到登记,\n 不是反过来。另引 workspace.json 2026-09-19 才补入的 layers[].responsibility 作为层职责口径\n (应然口径,不作现状证据)。\n- 建议 Decision 八条:provides 全空不动 kernel(exact pin 不受影响)/「不新增 M8」改写为\n 九项准入标准而非删除(Q01「不得以方便实现自动新增」保留,从「不许新增」变成「不许绕过\n 准入条件新增」)/ 先契约后实现 / 六域起 shape,升 authority 各需一条新的已批准 DEC,本件\n 不代批 / Fact 按 DEC-038(仍 pending)停在候选 / 验收等级不升不降(六域本就 candidate_e0\n E0,与 DEC-040 那三条 E2→E0 相反,两份材料别串)/ 无消费者的模块只能停 shape / 退役机制\n 与本件同批建。末两条为目录负责人当日对原待定项 B / C 的定案。\n- 第 7 条的后果已写明:六域今天零消费者,与「shape 不得有迁移」叠加,等于第一个真实消费者\n 出现前一个都不能升 authority、也建不了权威表。这是已决且尚未满足,不是未决。\n\nCHG-022 材料(待 DEC-041 批准 + Catalog Owner 签署,本包未改动任何文件):\n- 四份 delta:decisions / platform-projects / modules / catalog-map,各带当前值与目标值。\n platform-projects 每条另列 unchanged 段,把「六域只改 form、hosted_by 与验收等级都不动」\n 与 CHG-021 三条的相反处置区分开。\n- §4A 八步应用顺序,每步注明为什么在那一位;六个模块可分批,但每批内部第 3—7 步必须同一提交,\n 否则 catalog:drift(2026-09-17 起 drift 档一律阻断)在中间态判红。\n- 第 8 步是退役机制:今天 runtime/modules.json 没有任何退役表达(无 retirement 字段、无\n directory: null 等价物),删目录 + 删登记行之后 check:modules 反而是绿的——这正是 Q01 要求\n 宿主提供「退出保障」的那一条,对控制面自己同样不成立的地方。没有退役路径,「支持新增」\n 就是单向门。\n- 顺带记录一处由 CHG-021 的 catalog-map.delta.json 查明、本包据以补进准入第 1 条的判据:\n 每个新模块必须在 governance/catalog-map.json 显式登记 模块 id → Catalog id 的映射,不靠\n 同名推断(既有 identity→enterprise-idp 就不同名),漏掉则 build-workbench-snapshots 报\n MODULE_WITHOUT_CATALOG_ENTRY、check:catalog 对账同时判红。\n\n收纳表随之改数:doc/ 160 → 166,编号区间跟到 041 / 022。\n\n配套的两份设计文档在真源仓 docs/能力设计/(九域模块化落地设计、运行时模块进出机制设计),\n本次不在治理仓提交范围内。\n\n自检:四份 delta JSON 合法;六份文件的相对链接逐条验在;治理层一致性检查 CLEAN\n(14 仓 / 8377 文件 / 4507 链接)——它只扫已跟踪文件,本批提交后才算机器验过。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:36:03-07:00"}],"HeadCommit":{"Sha1":"87c3722f6c778c786ea50eba75bc5806fa300b0b","Message":"docs(决策): DEC-041 零运行面契约域收编为平台运行时模块 + CHG-022 受控变更包(均待签署)\n\n目录负责人 2026-09-19 提出「调度跨域、企业 IM、数据分析、统一体验、成本容量 + 应用与\n契约注册中心,应该直接放到企业控制面作为运行时模块;企业控制面要支持运行时模块的新增\n和删除」。该指示与已批准的 决策批次-2026-09-16 C-3 相反——C-3 的承接表把这几项裁给上层\n既有宿主,附条件「不新增 M8」「宿主协议签收才算准入」——故先成裁决材料,批准后实现才有依据。\n\n范围与 DEC-040 / CHG-021 划清:那一对管 C11—C13 三条有真实现的托管能力,本对管六个\n零运行面的域(C15 / C16 / C17 / C18 / C19 + C01)。两包独立签署、互不为前置(目录负责人当日定案)。\n\nDEC-041 草案(待批准):\n- Q01 备选条款是唯一合法入口,其触发条件经实测成立,且成立得比该条款预想的彻底:C-3\n 指定的五个宿主里三个不存在——C17「已有分析产品宿主」在业务应用层四个 + 企业领域应用层\n 四个里无一是分析产品;C19「复用 C17」随之落空;C15「业务应用的托管流程执行器」全工作区\n grep 零命中,最接近的工单仓 AutomationRun.ticketId 是必填外键 + onDelete Cascade,绑死\n 单张工单。一个须新建(C16 要的 Conversation/Membership/Message 工单 schema 里没有,而\n C-3 自己要求与 TicketMessage 分开),一个不是状态宿主(C18)。不是「评估后认为不足」,\n 是没有评估对象。\n- 补齐 Q01 要求的两个宿主方案成本与迁移影响对比(不做这张表,本裁决不满足自己的准入条件):\n 逐域给 C-3 指定者 + 全工作区内另找的最接近者,两个候选都评。\n- 一处此前没有材料提过的事实:这六项的 Catalog hosted_by 早就是 enterprise-platform。\n 登记面一直说它们归控制面,是 C-3 把运行宿主裁给了上层——本件是把裁决对齐到登记,\n 不是反过来。另引 workspace.json 2026-09-19 才补入的 layers[].responsibility 作为层职责口径\n (应然口径,不作现状证据)。\n- 建议 Decision 八条:provides 全空不动 kernel(exact pin 不受影响)/「不新增 M8」改写为\n 九项准入标准而非删除(Q01「不得以方便实现自动新增」保留,从「不许新增」变成「不许绕过\n 准入条件新增」)/ 先契约后实现 / 六域起 shape,升 authority 各需一条新的已批准 DEC,本件\n 不代批 / Fact 按 DEC-038(仍 pending)停在候选 / 验收等级不升不降(六域本就 candidate_e0\n E0,与 DEC-040 那三条 E2→E0 相反,两份材料别串)/ 无消费者的模块只能停 shape / 退役机制\n 与本件同批建。末两条为目录负责人当日对原待定项 B / C 的定案。\n- 第 7 条的后果已写明:六域今天零消费者,与「shape 不得有迁移」叠加,等于第一个真实消费者\n 出现前一个都不能升 authority、也建不了权威表。这是已决且尚未满足,不是未决。\n\nCHG-022 材料(待 DEC-041 批准 + Catalog Owner 签署,本包未改动任何文件):\n- 四份 delta:decisions / platform-projects / modules / catalog-map,各带当前值与目标值。\n platform-projects 每条另列 unchanged 段,把「六域只改 form、hosted_by 与验收等级都不动」\n 与 CHG-021 三条的相反处置区分开。\n- §4A 八步应用顺序,每步注明为什么在那一位;六个模块可分批,但每批内部第 3—7 步必须同一提交,\n 否则 catalog:drift(2026-09-17 起 drift 档一律阻断)在中间态判红。\n- 第 8 步是退役机制:今天 runtime/modules.json 没有任何退役表达(无 retirement 字段、无\n directory: null 等价物),删目录 + 删登记行之后 check:modules 反而是绿的——这正是 Q01 要求\n 宿主提供「退出保障」的那一条,对控制面自己同样不成立的地方。没有退役路径,「支持新增」\n 就是单向门。\n- 顺带记录一处由 CHG-021 的 catalog-map.delta.json 查明、本包据以补进准入第 1 条的判据:\n 每个新模块必须在 governance/catalog-map.json 显式登记 模块 id → Catalog id 的映射,不靠\n 同名推断(既有 identity→enterprise-idp 就不同名),漏掉则 build-workbench-snapshots 报\n MODULE_WITHOUT_CATALOG_ENTRY、check:catalog 对账同时判红。\n\n收纳表随之改数:doc/ 160 → 166,编号区间跟到 041 / 022。\n\n配套的两份设计文档在真源仓 docs/能力设计/(九域模块化落地设计、运行时模块进出机制设计),\n本次不在治理仓提交范围内。\n\n自检:四份 delta JSON 合法;六份文件的相对链接逐条验在;治理层一致性检查 CLEAN\n(14 仓 / 8377 文件 / 4507 链接)——它只扫已跟踪文件,本批提交后才算机器验过。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:36:03-07:00"},"CompareURL":"luoanwu/platform-governance/compare/7ad320a65b921c9d68a4ab48df81241998e64867...87c3722f6c778c786ea50eba75bc5806fa300b0b","Len":1}...
|
1789810841
|
Edit
Delete
|
|
31248
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6310f9627 {"Commits":[{"Sha1":"6310f96273f3871838ed559d8ba7376fca142465","Message":"docs(决策): DEC-040 补第 6 条终局形态——16 模块 + 3 采纳 + 2 排除资产,C07/C08/C09 显式裁定不升格\n\n目录负责人 2026-09-19 口径:「除 C07 交付、C08 网关、C09 观测外的项目都应该是运行时模块」。\n对着机器 Catalog 核过,这句与桌上两包严丝合缝,不需要第三包:7(已有)+ 3(DEC-040/CHG-021)\n+ 6(DEC-041/CHG-022)= 16,余下正好是那三条采纳形态,加两条排除资产即 21 条 Catalog 项目。\n\n但有个措辞缺口:两包此前只是**没覆盖** C07/C08/C09,而「没被覆盖」与「已裁定维持采纳形态」\n不是一回事——DEC-041 全文对这三条零提及(实测 grep 零命中)。故在 DEC-040 建议 Decision 补第 6 条:\n\n- 三档分法成表,逐条点名。\n- 三条不升格的理由落到具体落点:交付=release-manifest / check-promotion / verify-candidate;\n 网关=Caddyfile + caddy-routes.json + check-caddy;观测=collector + otel-attributes.json + check-otel。\n 给它们建模块=再造一个已经在跑的东西,且 DEC-024 / DEC-025 已批准这三处选型。\n- 例外入口不关死:将来某条被证明给不了隔离 / 故障预算 / 退出保障,仍可按 Q01 备选条款另提裁决,\n 但同样须附两个宿主方案的成本与迁移影响,不得以「形态统一」为由自动升格。\n\nCHG-021 的「与 CHG-022 的分工」段同步补成三分法并指回本条。\n自检:两份文档相对链接逐条验在;工作区一致性 0 条(8386 份受控文件 / 4607 条链接)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:49:08-07:00"}],"HeadCommit":{"Sha1":"6310f96273f3871838ed559d8ba7376fca142465","Message":"docs(决策): DEC-040 补第 6 条终局形态——16 模块 + 3 采纳 + 2 排除资产,C07/C08/C09 显式裁定不升格\n\n目录负责人 2026-09-19 口径:「除 C07 交付、C08 网关、C09 观测外的项目都应该是运行时模块」。\n对着机器 Catalog 核过,这句与桌上两包严丝合缝,不需要第三包:7(已有)+ 3(DEC-040/CHG-021)\n+ 6(DEC-041/CHG-022)= 16,余下正好是那三条采纳形态,加两条排除资产即 21 条 Catalog 项目。\n\n但有个措辞缺口:两包此前只是**没覆盖** C07/C08/C09,而「没被覆盖」与「已裁定维持采纳形态」\n不是一回事——DEC-041 全文对这三条零提及(实测 grep 零命中)。故在 DEC-040 建议 Decision 补第 6 条:\n\n- 三档分法成表,逐条点名。\n- 三条不升格的理由落到具体落点:交付=release-manifest / check-promotion / verify-candidate;\n 网关=Caddyfile + caddy-routes.json + check-caddy;观测=collector + otel-attributes.json + check-otel。\n 给它们建模块=再造一个已经在跑的东西,且 DEC-024 / DEC-025 已批准这三处选型。\n- 例外入口不关死:将来某条被证明给不了隔离 / 故障预算 / 退出保障,仍可按 Q01 备选条款另提裁决,\n 但同样须附两个宿主方案的成本与迁移影响,不得以「形态统一」为由自动升格。\n\nCHG-021 的「与 CHG-022 的分工」段同步补成三分法并指回本条。\n自检:两份文档相对链接逐条验在;工作区一致性 0 条(8386 份受控文件 / 4607 条链接)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:49:08-07:00"},"CompareURL":"luoanwu/platform-governance/compare/87c3722f6c778c786ea50eba75bc5806fa300b0b...6310f96273f3871838ed559d8ba7376fca142465","Len":1}...
|
1789811363
|
Edit
Delete
|
|
31249
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"97e65b262 {"Commits":[{"Sha1":"97e65b262e22f4bfef8755e848e5bacbf33574b3","Message":"docs(决策): DEC-040 / DEC-041 批准记录落定——九域全收开工,起手 C11 公共文件\n\n目录负责人 2026-09-19 在会话内批准两件,逐句留痕记在各自批准记录里:\n- DEC-040 选 A(C11/C12/C13 三条一并升格),第 4 条配置豁免与第 6 条终局形态均照原文批准;\n 附加条件:按 CHG-021 §6 一条走完再开下一条,起手 C11 公共文件。\n- DEC-041 选 A(C01 + C15—C19 六域一并收编),四项待定照其正文已定案原文批准;\n 六域实施由其材料的负责会话推进,与本三条并行、互不为前置。\n\n两件的「Current action 不得做」自本记录起失效,改由各自 CHG 的应用顺序一步一验约束。\n下一步是 CHG-021 §5 第 1 步:把 DEC-040 登记进真源仓 contracts/catalogs/decisions.json。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:55:33-07:00"}],"HeadCommit":{"Sha1":"97e65b262e22f4bfef8755e848e5bacbf33574b3","Message":"docs(决策): DEC-040 / DEC-041 批准记录落定——九域全收开工,起手 C11 公共文件\n\n目录负责人 2026-09-19 在会话内批准两件,逐句留痕记在各自批准记录里:\n- DEC-040 选 A(C11/C12/C13 三条一并升格),第 4 条配置豁免与第 6 条终局形态均照原文批准;\n 附加条件:按 CHG-021 §6 一条走完再开下一条,起手 C11 公共文件。\n- DEC-041 选 A(C01 + C15—C19 六域一并收编),四项待定照其正文已定案原文批准;\n 六域实施由其材料的负责会话推进,与本三条并行、互不为前置。\n\n两件的「Current action 不得做」自本记录起失效,改由各自 CHG 的应用顺序一步一验约束。\n下一步是 CHG-021 §5 第 1 步:把 DEC-040 登记进真源仓 contracts/catalogs/decisions.json。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:55:33-07:00"},"CompareURL":"luoanwu/platform-governance/compare/6310f96273f3871838ed559d8ba7376fca142465...97e65b262e22f4bfef8755e848e5bacbf33574b3","Len":1}...
|
1789811736
|
Edit
Delete
|
|
31251
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"3e1c4767a {"Commits":[{"Sha1":"3e1c4767a1d962075bfbcd815c9ce1f1bb7fd0a2","Message":"docs(基础): 治理测试计数由 471 改 480 —— 随 check:modules 投影准入新增 8 例\n\n真源仓 `c1d6baa` 给 check:modules 加了投影类模块准入(CHG-022 §3.2 第 10 条\n可机器判定的那一半),带 8 个负向用例;另有并行会话 1 例。两条跑法复测都是\n480 例 479 通过 / 0 失败 / 1 跳过,`reports/` 仍一个字节不动。\n\n两仓数字一起改(本目录 CLAUDE.md 纪律):真源仓改实现,治理层改引用。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T04:15:39-07:00"}],"HeadCommit":{"Sha1":"3e1c4767a1d962075bfbcd815c9ce1f1bb7fd0a2","Message":"docs(基础): 治理测试计数由 471 改 480 —— 随 check:modules 投影准入新增 8 例\n\n真源仓 `c1d6baa` 给 check:modules 加了投影类模块准入(CHG-022 §3.2 第 10 条\n可机器判定的那一半),带 8 个负向用例;另有并行会话 1 例。两条跑法复测都是\n480 例 479 通过 / 0 失败 / 1 跳过,`reports/` 仍一个字节不动。\n\n两仓数字一起改(本目录 CLAUDE.md 纪律):真源仓改实现,治理层改引用。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T04:15:39-07:00"},"CompareURL":"luoanwu/platform-governance/compare/97e65b262e22f4bfef8755e848e5bacbf33574b3...3e1c4767a1d962075bfbcd815c9ce1f1bb7fd0a2","Len":1}...
|
1789823568
|
Edit
Delete
|
|
31252
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"204cd56ae {"Commits":[{"Sha1":"204cd56aef423637994576cd323a2e466c19380a","Message":"docs(基础): 裁决计数随 DEC-040 由 39/32 改 40/33 —— L13 两处锚点\n\n真源仓 2026-09-19 按 CHG-021 §5 第 1 步登记 DEC-040 = approved,活跃 Catalog\n现为 40 条:33 approved / 3 pending / 4 rejected。治理层两处「快照时效提示」\n锚点后的机器基线声明仍写 39 / 32,一致性门禁 L13 四处判红。\n\n只改锚点后那句「机器基线为 N 条」——它是当前声明。同段落里 2026-09-04—09-10\n与 2026-09-12 决策会的历史数字**原样不动**:那是当时的事实,改它等于篡改记录。\n\n复跑 check-workspace-consistency:5 条降到 1 条。余下 1 条是 L10,在\nruntime/modules/public-file/src/persistence/public-file-store.ts 的注释里\n(「等 DEC-040 问题 5 裁完再加」),该注释早于「控制器四个操作落地」与\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-19T06:17:06-07:00"}],"HeadCommit":{"Sha1":"204cd56aef423637994576cd323a2e466c19380a","Message":"docs(基础): 裁决计数随 DEC-040 由 39/32 改 40/33 —— L13 两处锚点\n\n真源仓 2026-09-19 按 CHG-021 §5 第 1 步登记 DEC-040 = approved,活跃 Catalog\n现为 40 条:33 approved / 3 pending / 4 rejected。治理层两处「快照时效提示」\n锚点后的机器基线声明仍写 39 / 32,一致性门禁 L13 四处判红。\n\n只改锚点后那句「机器基线为 N 条」——它是当前声明。同段落里 2026-09-04—09-10\n与 2026-09-12 决策会的历史数字**原样不动**:那是当时的事实,改它等于篡改记录。\n\n复跑 check-workspace-consistency:5 条降到 1 条。余下 1 条是 L10,在\nruntime/modules/public-file/src/persistence/public-file-store.ts 的注释里\n(「等 DEC-040 问题 5 裁完再加」),该注释早于「控制器四个操作落地」与\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-19T06:17:06-07:00"},"CompareURL":"luoanwu/platform-governance/compare/3e1c4767a1d962075bfbcd815c9ce1f1bb7fd0a2...204cd56aef423637994576cd323a2e466c19380a","Len":1}...
|
1789823829
|
Edit
Delete
|
|
31256
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"e4287f952 {"Commits":[{"Sha1":"e4287f952d278ffe74c3ad682b9d11bc7028908c","Message":"docs(governance): reconcile DEC-040/041 status and CHG-021 progress\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T07:48:19-07:00"}],"HeadCommit":{"Sha1":"e4287f952d278ffe74c3ad682b9d11bc7028908c","Message":"docs(governance): reconcile DEC-040/041 status and CHG-021 progress\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T07:48:19-07:00"},"CompareURL":"luoanwu/platform-governance/compare/204cd56aef423637994576cd323a2e466c19380a...e4287f952d278ffe74c3ad682b9d11bc7028908c","Len":1}...
|
1789829310
|
Edit
Delete
|
|
31260
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1d0dd2c04 {"Commits":[{"Sha1":"1d0dd2c042d6a06ccd5c53cfcc5115850fefe859","Message":"docs(governance): record verified dev runtime update\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T07:53:47-07:00"}],"HeadCommit":{"Sha1":"1d0dd2c042d6a06ccd5c53cfcc5115850fefe859","Message":"docs(governance): record verified dev runtime update\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T07:53:47-07:00"},"CompareURL":"luoanwu/platform-governance/compare/e4287f952d278ffe74c3ad682b9d11bc7028908c...1d0dd2c042d6a06ccd5c53cfcc5115850fefe859","Len":1}...
|
1789829649
|
Edit
Delete
|
|
31280
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"e665ccae2 {"Commits":[{"Sha1":"e665ccae21f6bfec22ea24f341e726c550634b00","Message":"docs(governance): align layer terminology and platform status\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:57:10-07:00"}],"HeadCommit":{"Sha1":"e665ccae21f6bfec22ea24f341e726c550634b00","Message":"docs(governance): align layer terminology and platform status\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:57:10-07:00"},"CompareURL":"luoanwu/platform-governance/compare/1d0dd2c042d6a06ccd5c53cfcc5115850fefe859...e665ccae21f6bfec22ea24f341e726c550634b00","Len":1}...
|
1789862243
|
Edit
Delete
|
|
31281
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"600b27dd7 {"Commits":[{"Sha1":"600b27dd78486b235f958cb358b936a3b64abf07","Message":"docs(governance): align DEC-041 catalog counts\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:58:02-07:00"}],"HeadCommit":{"Sha1":"600b27dd78486b235f958cb358b936a3b64abf07","Message":"docs(governance): align DEC-041 catalog counts\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:58:02-07:00"},"CompareURL":"luoanwu/platform-governance/compare/e665ccae21f6bfec22ea24f341e726c550634b00...600b27dd78486b235f958cb358b936a3b64abf07","Len":1}...
|
1789862288
|
Edit
Delete
|
|
31286
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"47a3de602 {"Commits":[{"Sha1":"47a3de602dfa355f1dce32f192ddf4478d0c923a","Message":"docs(计划): 登记 B5 收口、check:runtime 重跑撞出的回归与状态格再订 @ 真源仓 c0422ba\n\n- 状态行与 §1 四行按 2026-09-20T01:05Z 实测重订:作业由 15 个拒绝桩改为 job-readiness 记账\n (active 8 / alternate 2 / deferred 12,真正新写的处理器只有 identity.session-cleanup),未落地面 47 → 33;\n dev 当晚又切三次、现跑 793dd51 构建的镜像;check:deployed 判定范围按依赖闭包修正(B5,84a8991)。\n- check:runtime 在 HEAD 重跑:clean 20f2211 上红(a64dc81 留下两条旧夹具用例,根链不跑 api-nestjs 单测\n 所以过了整链并部署到 dev),修于 0482667 后 1109 tests / 0 failures,回绑 c0422ba。\n- 未认证写入的读数改成实测口径:已登记的操作路由 401,裸集合路径 404(与当日几份部署记录不符,未回查)。\n- §5 ⑤ 增门禁缺口待裁;§7 增「根链绿 ≠ 运行时测试绿」;§8 增一行。\n\n一致性门禁 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-19T18:13:13-07:00"},{"Sha1":"f2c623fd273fd92026151c1e305ecf51f430c218","Message":"docs(计划): 登记 F1 收口与当晚状态格重订——变更记录一行 + 控制面 CLAUDE.md 三处随实测改\n\n开发计划 §8 增 2026-09-19 晚一行:F1 依据判定(真源仓 27e8679 / 7c0d8df)、本文订正范围、\n一致性门禁由 5 条转 CLEAN(其中 L4 是数字员工OS 仓并行验收临时删报告的瞬态,未改该仓)、\n以及订正过程中真源仓 HEAD 由 44f8a6c 走到 12b7347、本批改动被 e665cca / 600b27d 带走提交的事实。\n\n企业控制面/CLAUDE.md:worktree 由两条订正为四条并注明这张表一天就能过期;治理测试计数\n不再写死单一数字(当天 480 → 510 → 513);门禁链说明补第 2 环 modules 新守的 authority 依据。\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-19T17:10:18-07:00"}],"HeadCommit":{"Sha1":"47a3de602dfa355f1dce32f192ddf4478d0c923a","Message":"docs(计划): 登记 B5 收口、check:runtime 重跑撞出的回归与状态格再订 @ 真源仓 c0422ba\n\n- 状态行与 §1 四行按 2026-09-20T01:05Z 实测重订:作业由 15 个拒绝桩改为 job-readiness 记账\n (active 8 / alternate 2 / deferred 12,真正新写的处理器只有 identity.session-cleanup),未落地面 47 → 33;\n dev 当晚又切三次、现跑 793dd51 构建的镜像;check:deployed 判定范围按依赖闭包修正(B5,84a8991)。\n- check:runtime 在 HEAD 重跑:clean 20f2211 上红(a64dc81 留下两条旧夹具用例,根链不跑 api-nestjs 单测\n 所以过了整链并部署到 dev),修于 0482667 后 1109 tests / 0 failures,回绑 c0422ba。\n- 未认证写入的读数改成实测口径:已登记的操作路由 401,裸集合路径 404(与当日几份部署记录不符,未回查)。\n- §5 ⑤ 增门禁缺口待裁;§7 增「根链绿 ≠ 运行时测试绿」;§8 增一行。\n\n一致性门禁 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-19T18:13:13-07:00"},"CompareURL":"luoanwu/platform-governance/compare/600b27dd78486b235f958cb358b936a3b64abf07...47a3de602dfa355f1dce32f192ddf4478d0c923a","Len":2}...
|
1789867918
|
Edit
Delete
|
|
31344
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ede3bf589 {"Commits":[{"Sha1":"ede3bf5896a22d0dd6585945e8c7cdc4e7e0bda1","Message":"docs(计划): 登记治理缺口收口——check:deployed 核镜像源是否被通过的 check:runtime 覆盖 @ 真源仓 a6a2ee7 / ef116fb\n\n§5 ⑤ 的「门禁缺口待裁」改为已收口并说明选了哪条路(设为前置的机器形态,不重跑验收,\n核验收绑定的提交与镜像源之间镜像代码面有无差异)、没选哪条(runtime 无库单测并进根链)与理由;\n§1「stack / 部署」补判定规则、作用域收窄与当前读数;§7 一处补引;§8 增一行。\nF4 未动,理由写进 §8。一致性门禁 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-19T20:30:22-07:00"}],"HeadCommit":{"Sha1":"ede3bf5896a22d0dd6585945e8c7cdc4e7e0bda1","Message":"docs(计划): 登记治理缺口收口——check:deployed 核镜像源是否被通过的 check:runtime 覆盖 @ 真源仓 a6a2ee7 / ef116fb\n\n§5 ⑤ 的「门禁缺口待裁」改为已收口并说明选了哪条路(设为前置的机器形态,不重跑验收,\n核验收绑定的提交与镜像源之间镜像代码面有无差异)、没选哪条(runtime 无库单测并进根链)与理由;\n§1「stack / 部署」补判定规则、作用域收窄与当前读数;§7 一处补引;§8 增一行。\nF4 未动,理由写进 §8。一致性门禁 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-19T20:30:22-07:00"},"CompareURL":"luoanwu/platform-governance/compare/47a3de602dfa355f1dce32f192ddf4478d0c923a...ede3bf5896a22d0dd6585945e8c7cdc4e7e0bda1","Len":1}...
|
1789875027
|
Edit
Delete
|
|
31592
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d7e59326a {"Commits":[{"Sha1":"d7e59326a6fc0c340628de4a8fb4d9822007fc96","Message":"docs(计划): 登记 09-20 第四轮对抗验收与 F1 ①② 收口,订正作业计数 8→6 @ 真源仓 4b8872b8\n\n「模块」行:作业登记 active 8 / alternate 2 / deferred 12、jobs 合计 8 → 6 / 2 / 14、合计 6(09-20 两个重试作业改 deferred,本文未跟);\n补 identity.session-cleanup 在 dev 被 IDP_SESSION_CLEANUP_ENABLED=false 关着且该开关不在 stub-surface 扫描面(F3)。\n「对抗性验收」行:增 09-20 一轮(固定 263b2ec1,真源仓 3f001b92):check:fact-pii 三条绕过,前两条同晚收口 77c370b2 / 回绑 4b8872b8,\n候选目录 0 字段待 Catalog Owner 裁;F2—F4 归属平台后端。偏差 #40「Fact 侧已经是这个形态」改为名义形态 + 实测 0 字段。§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-20T20:26:43-07:00"}],"HeadCommit":{"Sha1":"d7e59326a6fc0c340628de4a8fb4d9822007fc96","Message":"docs(计划): 登记 09-20 第四轮对抗验收与 F1 ①② 收口,订正作业计数 8→6 @ 真源仓 4b8872b8\n\n「模块」行:作业登记 active 8 / alternate 2 / deferred 12、jobs 合计 8 → 6 / 2 / 14、合计 6(09-20 两个重试作业改 deferred,本文未跟);\n补 identity.session-cleanup 在 dev 被 IDP_SESSION_CLEANUP_ENABLED=false 关着且该开关不在 stub-surface 扫描面(F3)。\n「对抗性验收」行:增 09-20 一轮(固定 263b2ec1,真源仓 3f001b92):check:fact-pii 三条绕过,前两条同晚收口 77c370b2 / 回绑 4b8872b8,\n候选目录 0 字段待 Catalog Owner 裁;F2—F4 归属平台后端。偏差 #40「Fact 侧已经是这个形态」改为名义形态 + 实测 0 字段。§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-20T20:26:43-07:00"},"CompareURL":"luoanwu/platform-governance/compare/ede3bf5896a22d0dd6585945e8c7cdc4e7e0bda1...d7e59326a6fc0c340628de4a8fb4d9822007fc96","Len":1}...
|
1789961207
|
Edit
Delete
|
|
31602
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d6d5f567c {"Commits":[{"Sha1":"d6d5f567cd7752b0d5ab9c4ff2dc0b4114b3169d","Message":"docs(计划): 登记 F3 收口——作业登记 enabledBy 对账与开关扫描放宽 @ 真源仓 9e587bd0 / bc038a5a\n\n「模块」行:未落地面 33 → 34(环境开关 10)、F3 由「未修」改为同晚收口并写明新抓出的两条受 PLATFORM_PERSISTENCE_ENABLED 约束的作业;\n「对抗性验收」行 F3 改已收口;§8 加一行。dev 上 IDP_SESSION_CLEANUP_ENABLED 仍 false,开启归平台后端。\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-20T20:39:48-07:00"}],"HeadCommit":{"Sha1":"d6d5f567cd7752b0d5ab9c4ff2dc0b4114b3169d","Message":"docs(计划): 登记 F3 收口——作业登记 enabledBy 对账与开关扫描放宽 @ 真源仓 9e587bd0 / bc038a5a\n\n「模块」行:未落地面 33 → 34(环境开关 10)、F3 由「未修」改为同晚收口并写明新抓出的两条受 PLATFORM_PERSISTENCE_ENABLED 约束的作业;\n「对抗性验收」行 F3 改已收口;§8 加一行。dev 上 IDP_SESSION_CLEANUP_ENABLED 仍 false,开启归平台后端。\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-20T20:39:48-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d7e59326a6fc0c340628de4a8fb4d9822007fc96...d6d5f567cd7752b0d5ab9c4ff2dc0b4114b3169d","Len":1}...
|
1789961992
|
Edit
Delete
|
|
31605
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"c4eda2fca {"Commits":[{"Sha1":"c4eda2fca0004b2e28718d54b984e40b9aefc5dd","Message":"docs(计划): 登记 F4 与 F1 ③ 收口——作业接线真解析、候选 Fact 指针跟随 @ 真源仓 dac71aa0 / f2d611c4\n\n「对抗性验收」行两条改已收口并写明口径(不可达登账同 candidate-contracts 先例);偏差 #40 Fact 侧补收口句;§8 加一行。\n09-20 四项只剩 F2(register() 生产供给点与 contracts 摘要绑定)未动,归平台后端。本层材料改动须手动重跑 check:fact-pii。\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-20T20:59:21-07:00"}],"HeadCommit":{"Sha1":"c4eda2fca0004b2e28718d54b984e40b9aefc5dd","Message":"docs(计划): 登记 F4 与 F1 ③ 收口——作业接线真解析、候选 Fact 指针跟随 @ 真源仓 dac71aa0 / f2d611c4\n\n「对抗性验收」行两条改已收口并写明口径(不可达登账同 candidate-contracts 先例);偏差 #40 Fact 侧补收口句;§8 加一行。\n09-20 四项只剩 F2(register() 生产供给点与 contracts 摘要绑定)未动,归平台后端。本层材料改动须手动重跑 check:fact-pii。\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-20T20:59:21-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d6d5f567cd7752b0d5ab9c4ff2dc0b4114b3169d...c4eda2fca0004b2e28718d54b984e40b9aefc5dd","Len":1}...
|
1789963164
|
Edit
Delete
|
|
31611
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"77c4d41e9 {"Commits":[{"Sha1":"77c4d41e96574bf34c378d84ac07e8b5b6cb8091","Message":"Merge remote-tracking branch 'origin/claude/zealous-tu-6f0fca'\n\n# Conflicts:\n#\t平台治理/基础设施文档/开发计划.md\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-20T21:25:58-07:00"},{"Sha1":"deb083ad1eec5abd8539721eb75f28f60e382d8b","Message":"Merge branch 'claude/laughing-rhodes-1236b1'\n\n# Conflicts:\n#\t平台治理/基础设施文档/开发计划.md\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-20T21:25:00-07:00"},{"Sha1":"f8cebdaeca41316d8f1ea7745265ec8abf8311a3","Message":"docs(计划): §8 账本登记治理测试两条跑法合上(真源仓 7021758)\n\n收口上一行「松散端 A 组」那次留下的「一处新缺陷(已登记,未修)」:治理测试里 spawn\n门禁 CLI 的用例没把报告落盘目录钉死,于是不设 `GOV_REPORT_DIR` 跑会脏绑\n`reports/caddy.latest.json`、设了又让 12 个跑在临时沙箱里的用例判红。本轮逐个钉死,\n两条跑法实测都是 471 例 470 通过 / 0 失败 / 1 跳过,且不设变量那次跑前跑后\n`reports/*.json` 的 md5 逐份不变、`git status --porcelain` 为空。\n\n`企业控制面/CLAUDE.md` 那处 check 链描述不在本提交里:并行会话已在 `4a9dad2` 改过\n同一句,且连同它新增的 `stub-surface` 环写成了 21 环 / 第 16 环,比本会话按当前\n20 环写的那版更跟得上现状,故撤回自己那版,不制造同行冲突。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T00:31:33-07:00"},{"Sha1":"031878b2a7dbd2e2021b6dd71b0197e50cec3c96","Message":"docs(计划): 第四处同病改判已修(08c3788),并订正本条原先给错的一个修法\n\n登记时给了两个修法,取的是「把写报告挪到前置校验之后」;另一个「直接删掉占位写」被接手\n会话否掉,理由成立,本条一并订正:「跑起来但没跑完」确实该在盘上留 RUN_NOT_COMPLETED 而\n不是上一轮的 partial——这是用例自己写报告带来的责任,和「上轮结论已被后续提交推翻」不是\n同一个事实,不能用 check:evidence 判过期替代。\n\n实现是把那句抽成 markRunStarted(),调用点挪到模块库白名单通过、真实连库、API 子进程\n/health 就绪之后。两个方向都做了负向实测:同一条件下旧代码毁报告(sha256 变化),新代码\n测试照样失败而报告逐字节不变;正向确认 t+85s 兜底仍写 RUN_NOT_COMPLETED。\n\n受影响四份已重跑回绑 dfd4832(全绑 08c3788 / dirty=false,结果与修复前一致,说明动的只是\n写报告的时机);runbook §7 收尾同步改成已修(925eee8)。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T07:13:53-07:00"},{"Sha1":"f7a6b8eb62651f612a8a0e9666b22a5413b4fb1a","Message":"docs(计划): 登记第四处「前置失败销毁好证据」——revocation-sla 由用例自己在 beforeAll 写 failed\n\nadda76a 把三个 runner(runtime / UI / 双后端差分)统一改成前置失败即退出、不碰报告,\n本表上一条据此记「三处同病」。复核接手会话的重跑计划时发现同族还有第四处,且不在那\n三个 runner 里:revocation-sla.latest.json 的写入者是用例自己,不是 runner。\n\n要害是写入时机。runtime/test/e2e/revocation-sla.test.ts:68 在 beforeAll 的第一句就\n无条件写下 status:failed / reason:RUN_NOT_COMPLETED,下一句才做 isolated() 库名校验\n(mainline-support.ts:11 要求 /platform_\u003ckind\u003e_(ms23|test|ci))。先毁证据再校验前置,\n恰是 adda76a 所确立口径的反面。\n\n触发面比「跑主线验收」宽:runtime/test 是工作区包 platform-tests,pnpm\nruntime:check:runtime 第 5 步的 turbo run test 就会跑到它。runbook §7 那句「前置守卫\n段已修复,但跑到一半失败仍会写 failed」对本处不成立——连跑到一半都不需要。\n\n当日由接手会话实测复现:七个模块库建成 platform_\u003cm\u003e_acc0918 后 e2e/chaos 整片失败,\n其独立检出里那份报告已被清成 RUN_NOT_COMPLETED 绑 46265a6;主工作区绑 765300b 的\npartial 因其在独立检出里跑而幸存。连带结论是七个模块库后缀只能是 ms23 / test / ci,\n且 check:runtime 与 mainline:check 本就该共用同一批库。\n\n本轮只登记不修:六份验收报告的重跑已移交主会话并在其独立检出里进行,改同一批文件必\n撞车。真源仓侧的代码修正与 runbook §7 的措辞订正留给接手会话。全程只读,未跑门禁、\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-18T02:04:54-07:00"}],"HeadCommit":{"Sha1":"77c4d41e96574bf34c378d84ac07e8b5b6cb8091","Message":"Merge remote-tracking branch 'origin/claude/zealous-tu-6f0fca'\n\n# Conflicts:\n#\t平台治理/基础设施文档/开发计划.md\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-20T21:25:58-07:00"},"CompareURL":"luoanwu/platform-governance/compare/c4eda2fca0004b2e28718d54b984e40b9aefc5dd...77c4d41e96574bf34c378d84ac07e8b5b6cb8091","Len":5}...
|
1789964769
|
Edit
Delete
|
|
31614
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d3e7977b7 {"Commits":[{"Sha1":"d3e7977b7089f2ecc4465a469c7b9cb5c09d0559","Message":"docs(计划): 登记 F2 收口——register() 只接受 contracts 登记的 schema @ 真源仓 2d11ee6a\n\n「对抗性验收」行 F2 改已收口(随包规范化摘要 + 治理测试守漂移),09-20 四项全部收口;§8 加一行。\n部署边界:runtime 改动、dev 镜像未重建,切 dev 前须 check:runtime 回绑;生产 provisioning 入口的设计另归属。\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-20T22:34:10-07:00"}],"HeadCommit":{"Sha1":"d3e7977b7089f2ecc4465a469c7b9cb5c09d0559","Message":"docs(计划): 登记 F2 收口——register() 只接受 contracts 登记的 schema @ 真源仓 2d11ee6a\n\n「对抗性验收」行 F2 改已收口(随包规范化摘要 + 治理测试守漂移),09-20 四项全部收口;§8 加一行。\n部署边界:runtime 改动、dev 镜像未重建,切 dev 前须 check:runtime 回绑;生产 provisioning 入口的设计另归属。\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-20T22:34:10-07:00"},"CompareURL":"luoanwu/platform-governance/compare/77c4d41e96574bf34c378d84ac07e8b5b6cb8091...d3e7977b7089f2ecc4465a469c7b9cb5c09d0559","Len":1}...
|
1789968854
|
Edit
Delete
|
|
31675
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"15890a652 {"Commits":[{"Sha1":"15890a652ead543d4e2800481e00c7fd91f0bf15","Message":"docs(计划): 登记开关扫描盲区收口——ConfigService 读法与 defaultOn 登记,状态头按 §8 订正 @ 真源仓 b32aaeec / e9aac78e\n\ncheck-workspace-consistency --json:CLEAN,0 issues。\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-21T00:10:15-07:00"}],"HeadCommit":{"Sha1":"15890a652ead543d4e2800481e00c7fd91f0bf15","Message":"docs(计划): 登记开关扫描盲区收口——ConfigService 读法与 defaultOn 登记,状态头按 §8 订正 @ 真源仓 b32aaeec / e9aac78e\n\ncheck-workspace-consistency --json:CLEAN,0 issues。\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-21T00:10:15-07:00"},"CompareURL":"luoanwu/platform-governance/compare/d3e7977b7089f2ecc4465a469c7b9cb5c09d0559...15890a652ead543d4e2800481e00c7fd91f0bf15","Len":1}...
|
1789975609
|
Edit
Delete
|
|
31708
|
5
|
5
|
5
|
117
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"c37b1463e {"Commits":[{"Sha1":"c37b1463e23adfa7ce730351dd6430e4de8adb33","Message":"docs(计划): 续记后端注销分发环无库单测与模块目录作用域的回绑代价 @ 真源仓 6373d8c3 / d39adda8 / 8287e9b0\n\ncheck-workspace-consistency --json:CLEAN,0 issues。\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-21T01:01:21-07:00"},{"Sha1":"47561814b70971774ccb296700a67ce19f99610c","Message":"docs(计划): 续记仓纪律 3 措辞订正与三个 it.todo 标签改 pending-impl @ 真源仓 d9325095 / 9d9c3a9a\n\ncheck-workspace-consistency --json:CLEAN,0 issues。\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-21T00:27:40-07:00"}],"HeadCommit":{"Sha1":"c37b1463e23adfa7ce730351dd6430e4de8adb33","Message":"docs(计划): 续记后端注销分发环无库单测与模块目录作用域的回绑代价 @ 真源仓 6373d8c3 / d39adda8 / 8287e9b0\n\ncheck-workspace-consistency --json:CLEAN,0 issues。\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-21T01:01:21-07:00"},"CompareURL":"luoanwu/platform-governance/compare/15890a652ead543d4e2800481e00c7fd91f0bf15...c37b1463e23adfa7ce730351dd6430e4de8adb33","Len":2}...
|
1789979395
|
Edit
Delete
|
|
30243
|
1
|
1
|
1
|
118
|
0
|
0
|
|
1
|
|
1789524798
|
Edit
Delete
|
|
30251
|
1
|
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
|
|
30245
|
3
|
1
|
1
|
118
|
0
|
0
|
|
1
|
|
1789524798
|
Edit
Delete
|
|
30253
|
3
|
5
|
1
|
118
|
0
|
0
|
refs/heads/main
|
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
|