| content |
{"Commits":[{"Sha1":"5288ac175 {"Commits":[{"Sha1":"5288ac175ac522dbf9881cc17eb269e95e8062c3","Message":"chore(reports): refresh provenance report and anchor\n\n复验时重跑 check:platform-provenance 产生的报告刷新（仍为诚实红 3 处）。\n按 C241：只刷新 reports/ 的提交同样是提交，随带把快照锚点指向父提交 63e695b。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-13T21:20:45-07:00"},{"Sha1":"63e695b509c2300e6ec30626a92ad51438a5e309","Message":"docs(governance): correct clean-HEAD step count and name the unrun steps\n\n上一提交把静态门禁结果写成「23 个步骤 exit 0，止于第 24 步」——数错了：日志里第一行\n`\u003e digital-employee-os@0.1.0 check` 是包装命令本身，实际是**前 22 个门禁步骤通过、\n第 23 步 check:docs-truth 失败**（23 份 clean 报告的数字无误，报告数 ≠ 步数）。\n\n更重要的是上一提交只提了 check:platform-provenance 未执行，漏了 fail-fast 同样跳过的\ncheck:governance、lint、typecheck——那会让人以为治理棘轮与类型检查已在 clean HEAD 通过。\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-13T21:20:21-07:00"},{"Sha1":"450faaffcfcad7c776b48fd01cec7ac3e28112fa","Message":"docs(governance): record first clean-HEAD static evidence and OS-04 DB runs\n\n首次在 clean HEAD（46f89b7）执行 `pnpm check`：23 个步骤 exit 0 并写下 23 份\nworktreeDirty:false 的报告——本仓 reports/ 第一次绑定 clean SHA（此前 54 份全部是\n历史 dirty 树产物）。整轮仍未通过，止于第 24 步 check:docs-truth 的\ngovernance-number-evidence-shape：它要求 runtime/governance/baseline 三份数字真源\n都 passed，而 runtime-acceptance.latest.json 仍是 failed。末位的\ncheck:platform-provenance 因 fail-fast 未执行；单独运行按 G25③ 诚实红 3 处。\n\nOS-04 employment 投影在 clean 源码上跑了真实 DB：NestJS 9/9、Fastify 9/9、\ncontracts 24 文件 312/312（共享开发库 digital_employee_os_dev_*）。\n显式登记边界：这是 vitest 单文件运行，没有 latest 报告承载，**不构成阶段门证据**；\nOS-04 退出门仍要求 check:runtime 整轮在 clean HEAD 通过。\n\n快照锚点指向父提交（C232/C241）。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-13T21:19:56-07:00"},{"Sha1":"46f89b728979d21972828899f1a1eb51472b7f34","Message":"docs(governance): register G25③ dependency-provenance gate and refresh anchor\n\nCLAUDE.md（AGENTS.md 为其符号链接，自动跟随）：\n- G25③ 从「包未发布」改写为机器化表述：说明 pin 形态合规 ≠ 解析来源合规这一形态，\n 以及 check:platform-provenance 的四条判据与「临时目录来源不可登记豁免」\n- GOVERNANCE-BASELINE 新增 platform-dependency-provenance 行，诚实标 🟡 OPEN（红 3 处）\n- 验证命令段补 check:platform-provenance 与其 self-test\n- 快照基准提交锚点指向父提交 0a99a6a（C232/C241）\n\nreports/：本批 reports 为 dirty 工作区产物，按事实作用域纪律只绑定各自\nprovenance，不作阶段门证据；clean HEAD 三级门禁重跑仍是 OS-04 退出门的前置。\n被此前工作删除的 8 份报告已恢复到 HEAD 版本——它们本身也是 dirty 且锚在 9159f925，\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-13T21:17:01-07:00"},{"Sha1":"0a99a6a1702cbe04afe319e239601a14e9f83a8e","Message":"feat(governance): gate @juhai/* dependency provenance at the lockfile\n\n`juhai-governance check:pins` 只读 package.json 的版本字符串：\n`\"@juhai/client-fact\": \"1.0.0-rc.2\"` 在它眼里是完美 exact pin，而 pnpm-lock.yaml\n实际把它解析到 file:/private/tmp/claude-501/\u003c会话目录\u003e/scratchpad/pkg/*.tgz。\npin 形态合规、解析来源不合规，是比明着写 file: 依赖更危险的形态——它在所有既有门禁里\n都是绿的，只有别人 clone 后 pnpm install 失败时才暴露。\n\n新门禁把判据从「声明」下沉到「解析结果」：\n- importers 的 @juhai/* specifier 必须是 exact x.y.z[-pre] 或 workspace:*\n- packages 的 resolution tarball 必须落在 .npmrc 声明的 @juhai:registry 下\n （registry 地址单源读 .npmrc，不在脚本里硬编码；未声明即红，不静默放行）\n- 非 registry 来源须在 governance/platform-dependency-deviations.json 完整登记\n （reason/registeredAt/expiresAt/blockedBy/replacementPlan 五字段全填且未过期；\n 半份登记不算登记——它看起来像已受控）\n- 临时目录来源不可登记豁免：登记一个不可复现的构建没有意义\n\n--self-test 以合成 lock 跑 7 条判据（1 正 6 负）自证，避免「只会红的假门禁」。\n当前实跑诚实红 3 处，转绿的唯一路径是基础设施仓执行 CL-5 发布列车。\n\ncheck-all.mjs 是 fail-fast，本门禁因此排在末尾：诚实报红不应连带抹掉其余门禁的证据。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-13T21:16:43-07:00"}],"HeadCommit":{"Sha1":"5288ac175ac522dbf9881cc17eb269e95e8062c3","Message":"chore(reports): refresh provenance report and anchor\n\n复验时重跑 check:platform-provenance 产生的报告刷新（仍为诚实红 3 处）。\n按 C241：只刷新 reports/ 的提交同样是提交，随带把快照锚点指向父提交 63e695b。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-13T21:20:45-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/18a1b036f3dbb3f51ac773862e0cafac278bb34e...5288ac175ac522dbf9881cc17eb269e95e8062c3","Len":6}... |