| content |
{"Commits":[{"Sha1":"d24b762cd {"Commits":[{"Sha1":"d24b762cd6740f0bce850ae3fffcc84e8a279c28","Message":"chore(reports): 框架同步 0.16.1 → 0.22.0 后全套验收回绑 @ 765300b\n\n三级验收全部在干净树重跑，与升级前逐项持平：\n\n- runtime-acceptance **775 / 775 passed**，租户 RLS enforce（地板 775 未降）\n- ui-acceptance 5 / 5，1 组合\n- mainline-acceptance 四套件 11 / 17 / 19 / 18\n- mainline-restore passed，port-conformance 41 / 41\n- revocation-sla partial（invalidationPush 仍是 harness 传输，生产未接线）\n- release-manifest / sbom / identity-ui 随后重跑\n\ncheck:evidence **passed：35 份全新鲜 / 0 过期 / 0 例外**。\n\n过程中一处自伤已修复：曾用 git checkout -- runtime/reports 还原「跑门禁弄脏\n的报告」，连带把真跑出的六份验收证据还原成旧版，已在干净树重跑全套找回。\n教训：还原前必须按 provenance.gitSha 分辨本轮产出与脏绑，不可整目录 checkout。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T22:38:56-07:00"},{"Sha1":"d66f63659bc07fa65ac84685335a0f3c5e15af5d","Message":"docs(runtime): 动态区 SHA 回灌至 765300b（重跑后的验收绑定）\n\n上一轮误用 git checkout -- runtime/reports 把真跑出的六份验收报告还原成了\n旧版，已在干净树重跑全套（runtime 775/775、UI 5/5、主线 11/17/19/18、恢复\n演练、端口一致性 41/41），六份统一绑 765300b / dirty=false。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T22:36:52-07:00"},{"Sha1":"765300b962ca658d112ac6064f925d82d0579dfd","Message":"docs(runtime): 动态区回灌框架同步后的三级验收 @ 56e78df\n\ncheck:docs-truth 再次拦下「报告已刷新而动态区未跟上」。\n\n- 真实 DB：775 tests / 0 failures clean 56e78df——框架同步 0.16.1 → 0.22.0 后\n 首跑，测试数与升级前持平、租户 RLS 仍 enforce\n- 浏览器：5 用例 / 1 组合 clean 56e78df\n- 环境如实记：隔离栈 enterprise-platform-ms23-ci（PG :55485 / Redis :56395 /\n Redpanda :59105）+ 验收库 enterprise_platform_acceptance_fwsync\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T22:29:47-07:00"},{"Sha1":"56e78dfa4fb1001fad92e6d93b0e3bb2f7569594","Message":"fix(runtime): 修正 CHANGELOG 并入六段后的跨仓断链（一致性门禁 L4）\n\n框架 CHANGELOG 0.17.0—0.22.0 六段里的 ../\u003c框架变更请求\u003e.md 指的是框架仓同级，\n并入本仓后全部失效，L4 报 5 条。改为 ../../../工程基础框架/\u003c文件\u003e 跨仓路径。\n\n这是框架同步的真实副作用：并入上游文档时，其相对链接的锚点也跟着换了仓。\nL4 / L10 / L13 恢复 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-17T21:38:33-07:00"},{"Sha1":"b30ddd94965db4c6686a249d280ce579a879fc65","Message":"feat(runtime): 框架同步 0.16.1 → 0.22.0 主体（F-2b / F-3 / F-4）\n\nC-14 的实际形态。本轮把版本轴与两后端行为接线一次做完，部署两级按目录负责人\n裁决走「改判据 + 提 FR-6」。\n\nF-3 版本轴\n- 12 处 @juhai/kernel pin、runtime/package.json.version、packages/contracts\n version 全部 0.16.1 → 0.22.0；**F11 转绿**（这是抬 pin 一直卡住的门禁）\n- CHANGELOG 并入框架 0.17.0—0.22.0 六段，版本序连续；COMPATIBILITY.md 取 0.22.0\n\nF-4 两后端接线（C34 / C35 / C39 绊网全绿）\n- 直取六个未改过的文件：health.controller / health.module / health-checks.registry\n / request-log.middleware / logger / routes/health，另 types.ts、四个 C39 文件\n- 两处真三方合并：\n · api-fastify/src/app.ts：取 0.22.0 后按 sample-domain 标记剥离三个示例域块\n （本仓以 --strip-sample 建仓，本仓对该文件的唯一定制就是这三处剥离）\n · api-nestjs/src/create-app.ts：两侧改动不重叠——本仓加平台模块装载、框架加\n 访问日志中间件，合并保留两者\n\nF-2b 门禁脚本\n- check-dual-backend-parity / check-docs-truth / check-runtime-acceptance 取 0.22.0\n\ndocs-truth 四级新鲜度的本地修正（已提 FR-6）\n框架 0.22.0 把新鲜度断言由两级扩到四级，新增的部署 / 生产两级在本仓无法成立：\n其验收链要求 apps/api-nestjs/Dockerfile，而那份里写着 COPY packages/kernel/\npackage.json——本仓**不 vendor 内核**（pin 已发布包，packages/kernel 不存在），\n实测构建必然失败。本仓自己的制品镜像是 D-1 的 runtime/Dockerfile，与框架那套\n并存会变成两条镜像路径。判据改为「只对本仓真正接线了的级别断言」，未接线的\n打印 SKIPPED 而非伪装通过——不接受占位报告，与框架 doctrine「诚实的空」一致。\n已撤回全部 F-5 部署物与失败留下的半截报告。\n\n治理测试锚点 0.16.1 → 0.22.0。\n\n验收：turbo build 17/17、typecheck 31/31、runtime check 全链通过（两级 SKIPPED\n如实打印）、governance 测试 277/277。**真实三级验收随后在 clean 树重跑并回绑**\n——check:evidence 已如实报出 20 份证据的输入被本轮改动，不得只回绑静态报告。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T21:23:29-07:00"}],"HeadCommit":{"Sha1":"d24b762cd6740f0bce850ae3fffcc84e8a279c28","Message":"chore(reports): 框架同步 0.16.1 → 0.22.0 后全套验收回绑 @ 765300b\n\n三级验收全部在干净树重跑，与升级前逐项持平：\n\n- runtime-acceptance **775 / 775 passed**，租户 RLS enforce（地板 775 未降）\n- ui-acceptance 5 / 5，1 组合\n- mainline-acceptance 四套件 11 / 17 / 19 / 18\n- mainline-restore passed，port-conformance 41 / 41\n- revocation-sla partial（invalidationPush 仍是 harness 传输，生产未接线）\n- release-manifest / sbom / identity-ui 随后重跑\n\ncheck:evidence **passed：35 份全新鲜 / 0 过期 / 0 例外**。\n\n过程中一处自伤已修复：曾用 git checkout -- runtime/reports 还原「跑门禁弄脏\n的报告」，连带把真跑出的六份验收证据还原成旧版，已在干净树重跑全套找回。\n教训：还原前必须按 provenance.gitSha 分辨本轮产出与脏绑，不可整目录 checkout。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-17T22:38:56-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/96bfdde508464b4b0e1e3fb05f77a9f488492fc0...d24b762cd6740f0bce850ae3fffcc84e8a279c28","Len":6}... |