|
31214
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"e3b9d1252 {"Commits":[{"Sha1":"e3b9d12525448038fd8d8ac3f3c1470552ce4ff7","Message":"chore(reports): sbom 回绑——包清单一字未变,因为镜像还是 106 个提交前那个\n\nlockfile 模式扫 reports/image-digest.json 指向的镜像(sha256:c0869934…,本机 docker 里还在),\n268 个包,worktreeDirty=false。\n\n**这次回绑没有改变任何实质结论:** 触发过期的是 63ff31f 改的 runtime/pnpm-lock.yaml(把 clients\n三包的 devDeps pin 成 exact),而 SBOM 描述的是镜像里的物料——镜像绑的源提交 05e3826 距当前 HEAD\n106 个提交,那些改动根本还没进镜像。逐包比对确认:新旧两份的包清单完全一致,变的只有 SPDX 生成时间戳。\n\n诚实读法:**provenance.gitSha 说「我是在哪跑的」,sourceSha 说「我描述的是 05e3826 的镜像」——\n两者相距 106 个提交。** 作用域纳入 runtime/pnpm-lock.yaml,是为了在锁文件变动时提醒「SBOM 可能\n不再反映当前源码」;正确回应是**重建镜像**(需 BuildKit + Gitea token,不在本机这轮范围),\n而不是重跑一遍生成器。回绑只是让证据链不挂着一条无人处理的红,没有解决镜像落后本身。\n\ncoverage 仍是 partial:只含 /srv/runtime/apps/api-nestjs 的 Node 依赖,不含基础镜像的 Debian 包。\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:22:33-07:00"},{"Sha1":"a48cbd69d9411a1c7bc85e0fb97520c4392d1e73","Message":"docs(证据): 补 identity/reports 的扫描面处置说明,并修掉它已造成的一处数字漂移\n\n全仓盲区复核查出的唯一真发现:check-evidence-freshness.mjs 只扫 reports/ 与\nruntime/reports/ 两个目录(写死在源码里),identity/reports/ 的 15 份报告既不在作用域\n登记里、也不在未登记账里——不是「未登记」,是压根没被看见。\n\nidentity 是 PF-07 阶段 1 的过渡工作区,按仓纪律 7 其三级门禁不进根 pnpm check 链,这层\n分离是有意的;但报告新鲜度的失察不是:那 15 份确实被当证据用(verify:candidate 从\nidentity/reports/baseline.json 读测试地板,docs/项目完整能力表.md E03 直接引用两份),\n而 identity 自带的 check:docs-truth 有 0 条 freshness-sha-* 断言(runtime 版有 4 条),\n于是「报告往前跑了、文档没跟上」这类漂移没有任何一道门禁能发现。\n\n它已经真的发生了。三处文档写 runtime 255 / UI 12 @ 85d538b,而报告实际绑:\nruntime-acceptance @ 25ead3e(2026-09-12,261 项 / 地板 255)、ui-acceptance @ 90cda56\n(2026-09-13,12 项)、dual-backend-behavior @ 25ead3e(差分 0)。三处按文档既有的\n「当前 + 历史」体例改正,85d538b 那轮移入历史;该次报告未记录的细节(新 UI 运行的\nWeb / API 端口)不补写,明示未记录。\n\n处置说明写进 undeclaredNote,含二选一出口(纳入扫描面逐份登记,或给 identity 的\ncheck-docs-truth 补 freshness-sha-* 断言)并注明 PF-07 阶段 2 后此条作废——但在那之前\n不得把「将来会消失」当作现在不管的理由。归门禁 Owner 裁。\n\n核验:check:evidence 未登记账仍 10 份 0 份无说明;identity check:governance-docs 与\ncheck:docs-truth 均绿;工作区一致性 L4 / L10 / 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-18T17:20:16-07:00"}],"HeadCommit":{"Sha1":"e3b9d12525448038fd8d8ac3f3c1470552ce4ff7","Message":"chore(reports): sbom 回绑——包清单一字未变,因为镜像还是 106 个提交前那个\n\nlockfile 模式扫 reports/image-digest.json 指向的镜像(sha256:c0869934…,本机 docker 里还在),\n268 个包,worktreeDirty=false。\n\n**这次回绑没有改变任何实质结论:** 触发过期的是 63ff31f 改的 runtime/pnpm-lock.yaml(把 clients\n三包的 devDeps pin 成 exact),而 SBOM 描述的是镜像里的物料——镜像绑的源提交 05e3826 距当前 HEAD\n106 个提交,那些改动根本还没进镜像。逐包比对确认:新旧两份的包清单完全一致,变的只有 SPDX 生成时间戳。\n\n诚实读法:**provenance.gitSha 说「我是在哪跑的」,sourceSha 说「我描述的是 05e3826 的镜像」——\n两者相距 106 个提交。** 作用域纳入 runtime/pnpm-lock.yaml,是为了在锁文件变动时提醒「SBOM 可能\n不再反映当前源码」;正确回应是**重建镜像**(需 BuildKit + Gitea token,不在本机这轮范围),\n而不是重跑一遍生成器。回绑只是让证据链不挂着一条无人处理的红,没有解决镜像落后本身。\n\ncoverage 仍是 partial:只含 /srv/runtime/apps/api-nestjs 的 Node 依赖,不含基础镜像的 Debian 包。\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:22:33-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/d7d9fe5adc753a199dba41ec4be184d3db5053c4...e3b9d12525448038fd8d8ac3f3c1470552ce4ff7","Len":2}...
|
1789777366
|
Edit
Delete
|
|
31215
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6687aecfa {"Commits":[{"Sha1":"6687aecfababeb5c03b9fa56d306e8212e79e107","Message":"chore(reports): identity docs-truth 回绑 @ 1f3ff8c —— 含新增的两条 freshness 断言\n\n绑 1f3ff8c、worktreeDirty=false、docsTruthViolations=0。该门禁自身零依赖,故在 HEAD 的\n干净 worktree 里直接 node 即可跑出,不需要 install。\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:24:55-07:00"},{"Sha1":"1f3ff8c8f7d688955cc786f83cc79cc21fd73cc2","Message":"feat(identity): check:docs-truth 补 freshness-sha 断言,证据处置出口 ② 落地\n\na48cbd6 登记的二选一出口,门禁 Owner 取 ②。identity 的报告此前两头都照不到:\nidentity/reports 不在 governance/check-evidence-freshness.mjs 的扫描面内(那边只扫\nreports/ 与 runtime/reports/),而 identity 自带的 check:docs-truth 有 0 条 freshness\n断言(runtime 版有 4 条)。当日实测它已真的漂了一次——动态区写 255 / 12 @ 85d538b,\n报告实际是 25ead3e(261 项)与 90cda56(UI 12)。\n\n口径移植自 runtime/scripts/check-docs-truth.mjs,保留其三条设计判断,逐条都有理由:\n\n 刻意不含静态级——governance.latest.json 每次 check 都重绑当时 HEAD,对它断言等价于\n 「每次提交都必须改文档」,提交报告后必红,那是会误杀的门禁不是有牙的门禁。\n\n 未接线的级别跳过而不是判红——恒红门禁不携带信息。本仓只接了 check:runtime 与 check:ui,\n 故只有这两条;deployment / production 两级在 identity 不存在,未列入。\n\n 必须是声明形式——上游实锤过一次自我假绿:条目为说明陈旧度写了提交区间 A..B,裸 includes\n 命中散文里的顺带提及,于是「文档声明 A、报告是 B」这个断言唯一要防的形态被整个绕过。\n\n与上游的唯一差异:本仓动态区写法是 clean commit `sha`(上游是 clean `sha`),两种都认——\n让断言认识本仓真实措辞,而不是为迁就工具去改文档。\n\n负向三项实做:① 把 runtime 条目 SHA 改回 85d538b → exit 1 并点名期望形式;② SHA 只出现在\n提交区间里(clean commit `85d538b`(区间 85d538b..25ead3e))→ 仍 exit 1,即上游那条陷阱\n在本仓也拦得住;③ UI 条目单独篡改 → exit 1。三项还原后均 exit 0。\n\nevidence-scopes 的处置说明同步更新:② 标记为已实施并记下负向证据;① 明示未做且暂不做\n(identity 按仓纪律 7 本就与根链分离,扩面会把 15 份一次性拖进根链账),现状是「identity\n的报告由 identity 自己的门禁守新鲜度」,边界清楚。本条仍随 PF-07 阶段 2 折入后作废。\n\n报告未随本提交:identity/reports/docs-truth.latest.json 我跑出来的那份绑脏树,已还原,\n按纪律在干净检出重出后另起 chore(reports)。\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:24:38-07:00"},{"Sha1":"a0145351979f7cf18de29b182000f791d6f5de05","Message":"chore(reports): release-manifest 与 port-conformance 回绑 @ e3b9d12 —— 离线可跑的那批收口\n\n排查 7 条过期证据后分三组:A 组离线可跑、B 组要重建镜像并重启容器、C 组要真实 DB / Redpanda 验收。\n本次收 A 组。sbom 那条已由并行会话 e3b9d12 先收(包清单一字未变,因为镜像还是 106 个提交前那个),\n故 A 组实收两条。\n\n- release-manifest:结论仍是 partial,缺 signature(缺少与本次 registry 镜像绑定且 cosign 验证成功的\n 签名,§3A D-2)。回绑的是「当前确实缺这一项」这个事实,不是把它跑绿。\n- port-conformance:passed。\n\n回绑做法同前几次:企业控制面/.worktrees/rebind-a 开 detached 干净检出(HEAD e3b9d12),软链主检出的\nnode_modules(写进本地 info/exclude,用后删除),build contracts / modules / clients 后逐条跑,\n只把这两份 report 拷回主检出、按 pathspec 单独提交——主检出里并行会话另有十余份报告 WIP,一份没碰。\n\n过程中一处返工:首次跑 port-conformance 失败于 `Command \"vitest\" not found`——runtime/test 是独立\nworkspace 包,我第一轮软链只覆盖了 modules / packages / apps / clients,漏了它。补上软链后 passed。\n失败那份报告没有拷回。\n\n结果:两份 provenance 均 gitSha=e3b9d12、worktreeDirty=false;e3b9d12..HEAD 未触及这两份的作用域输入,\n绑定仍成立。\n\n未收(已登记,需你决定):\n B 组 deployed-runtime —— BUILT_IMAGE_SOURCE_BEHIND,运行容器镜像源 05e3826,HEAD 已有 23 个运行时\n 输入变更(其中含本会话接线那批 fixture-evaluator 与夹具)。要 image:build 重建 + 重启 runtime 容器。\n C 组 runtime-acceptance / mainline-acceptance / revocation-sla —— 要真实 PostgreSQL + Redis + Redpanda\n 验收;本机 dev 底座 13 个容器在跑,但会真实读写隔离库。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T17:24:14-07:00"}],"HeadCommit":{"Sha1":"6687aecfababeb5c03b9fa56d306e8212e79e107","Message":"chore(reports): identity docs-truth 回绑 @ 1f3ff8c —— 含新增的两条 freshness 断言\n\n绑 1f3ff8c、worktreeDirty=false、docsTruthViolations=0。该门禁自身零依赖,故在 HEAD 的\n干净 worktree 里直接 node 即可跑出,不需要 install。\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:24:55-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/e3b9d12525448038fd8d8ac3f3c1470552ce4ff7...6687aecfababeb5c03b9fa56d306e8212e79e107","Len":3}...
|
1789777575
|
Edit
Delete
|
|
31216
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"12093b843 {"Commits":[{"Sha1":"12093b843ef69d300370e5da16fcca3399c14d40","Message":"chore(reports): runtime 静态门禁链 18 份回绑 @ 8a621fd\n\n8a621fd 订正动态区 UI 条目后,docs-truth 的作用域(含 runtime/CLAUDE.md)随之过期;\nruntime check 是一条链、跑一次重出全部 16 项,故整批回绑而不是只挑一份——绑定一致比\n少改几个文件重要(同 b60cc18 的口径)。顺带清掉此前 error 级的 runtime-governance\n(绑 7fc7f02,作用域内 3 个文件已变)。\n\n在 HEAD 的干净 worktree(企业控制面/.worktrees/)装依赖 + prisma:generate 后跑\npnpm --dir runtime check:exit 0、16 项全过;只带回 provenance 绑 8a621fd 且\nworktreeDirty=false 的 18 份。\n\n刻意未带回 4 份:runtime-acceptance / ui-acceptance / conformance-differential 需真实\nDB 与浏览器,不由静态链产出,保持各自原绑定(08c3788 / 67e8193);framework-migration\n至今没有嵌套 provenance,已在 evidence-scopes 未登记账里具名。\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:33:42-07:00"},{"Sha1":"8a621fdb03a44cebc985f97332ead8bbb785a685","Message":"docs(runtime): 动态区 UI 条目订正三处——SHA、端口、验收库;check:docs-truth 转绿\n\nc4ec6f6 把 ui-acceptance 重绑到 67e8193 后没回灌动态区,check:docs-truth 的\nfreshness-sha-ui 从那时起一直红。逐项核对报告后发现**这一行有三处与报告对不上,\n而门禁只抓得到其中一处**:\n\n clean `1b23285` → 报告绑 `67e8193`(门禁抓到的就这条)\n web :3120 / api :3222 → 报告是 web :3100 / api :3202\n 「同上验收库与 Redis」 → UI 用的是 enterprise_platform_ui_acceptance,\n 与上一行 runtime 那轮的 enterprise_platform_acceptance_20260918\n 不是同一个库;Redis 逻辑库(:56380 db7)才是相同的\n\n只换 SHA 会把红变绿却留着后两句假话,故三处一并订正,并把「不是同一个库」写明——\n这一行紧跟在 runtime 条目之后,「同上」原本就容易被读成同一套基座。\n\n顺带记下门禁的覆盖边界:freshness-sha-* 只断言「动态区是否以声明形式写出报告当前的\nSHA」,同一条目里的端口、库名、用例描述都不在它的判据内,可以静默漂移——本次两处正是\n这样漂的。这不是缺陷而是取舍(把整行结构化对账会把门禁变成文档格式检查器),但读的人\n要知道绿不代表整行都对。\n\n核验:pnpm --dir runtime check 现 exit 0、16 项全过(本会话首次整条绿);\ncheck:governance-docs 绿(AGENTS.md 符号链接一致)。本次跑链改脏的 runtime/reports\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:32:06-07:00"}],"HeadCommit":{"Sha1":"12093b843ef69d300370e5da16fcca3399c14d40","Message":"chore(reports): runtime 静态门禁链 18 份回绑 @ 8a621fd\n\n8a621fd 订正动态区 UI 条目后,docs-truth 的作用域(含 runtime/CLAUDE.md)随之过期;\nruntime check 是一条链、跑一次重出全部 16 项,故整批回绑而不是只挑一份——绑定一致比\n少改几个文件重要(同 b60cc18 的口径)。顺带清掉此前 error 级的 runtime-governance\n(绑 7fc7f02,作用域内 3 个文件已变)。\n\n在 HEAD 的干净 worktree(企业控制面/.worktrees/)装依赖 + prisma:generate 后跑\npnpm --dir runtime check:exit 0、16 项全过;只带回 provenance 绑 8a621fd 且\nworktreeDirty=false 的 18 份。\n\n刻意未带回 4 份:runtime-acceptance / ui-acceptance / conformance-differential 需真实\nDB 与浏览器,不由静态链产出,保持各自原绑定(08c3788 / 67e8193);framework-migration\n至今没有嵌套 provenance,已在 evidence-scopes 未登记账里具名。\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:33:42-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/6687aecfababeb5c03b9fa56d306e8212e79e107...12093b843ef69d300370e5da16fcca3399c14d40","Len":2}...
|
1789778290
|
Edit
Delete
|
|
31219
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"b90d7a151 {"Commits":[{"Sha1":"b90d7a151e5e9451fa12fb6e883b8898552124df","Message":"chore(reports): C 组三份真实验收回绑 @ 8a621fd —— 在 adversarial 隔离栈上跑,共享底座与 ms23 均未触碰\n\nC 组(runtime-acceptance / mainline-acceptance / revocation-sla)需要真实 PG + Redis + Redpanda。\nms23 那套 35 分钟前刚被并行会话用过(容器 Exited),按 docs/持久主线本地验收.md「同名 project 即使\n容器刚启动也不能直接 up 覆盖,该名称已占用时应协调或选择已有获准且无人使用的测试环境」,改用\nadversarial(PG 55473 / Redis 56382 / Broker 59095,2026-09-12 获准、闲置 3 天、其 Broker 已在故障\n注入白名单)。全程 docker start 既有容器,未 compose up 覆盖任何 project。\n\n结果(均在干净检出 8a621fd 上产出,worktreeDirty=false):\n runtime-acceptance passed 1001 tests(地板 775)、tenantRlsEnforced=1、双后端差分 0\n mainline-acceptance passed\n revocation-sla partial p95 5027ms / max 5041ms / 20 samples——远低于 MS-3 的 30s;\n partial 来自 employmentScope 链仍 pending-scope-consumer-enforcement,\n 以及生产投送/负载/staging 四项 unverified,是既定状态不是失败\n conformance-differential 作为 runtime 验收的副产物一并刷新(同样已登记 severity=warn)\n\n过程中一处失败是我搭环境搭错的,记下来免得下次再犯:首轮 e2e/identity-profile 断言\n`elevated=false` 实测 true——mainline:prepare 只为 fact/permission/audit/owner/consumer 建非超级用户\n角色,identity/credential/scope/aigateway 四个库是我用管理员 platform 手建的,identity 的连接因此是\n特权角色。REASSIGN OWNED 不适用(platform 持有系统对象),改为重建该库并 OWNER 给\nplatform_identity_test_app、以该角色重新 deploy 迁移后转绿。credential / scope 没有\nprisma:migrate:deploy 脚本是对的——它们是 state=shape 模块,按仓纪律不得有迁移。\n\n隔离与收尾:凭据只经仓外 0600 文件(/tmp/c3-mainline.env、/tmp/c3-env.sh),不入仓、不打印;\n验收在独立 worktree 里 pnpm install 自己的 node_modules,不软链主检出,避免与并行会话抢 .prisma;\nadversarial 三容器跑完恢复为 Exited(与我接手前一致)。主检出里并行会话另有十余份报告 WIP,一份没碰。\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:56-07:00"},{"Sha1":"a178ba36c65d82fab8106fa7395dd65f927876ad","Message":"docs(治理): 云端治理段补 2026-09-19 实测——分支保护已整个消失,而计费仍未恢复\n\n推送本会话提交时实测到两条与在案记录对不上的事实:\n\n① main 的分支保护整个没了,不是摘掉那条必需检查而已:\n gh api .../branches/main/protection → 404 \"Branch not protected\"。\n 镜像因此重新推得动,直推 54e6324..12093b8 成功并已核对 github/main 与本地一致;\n 「镜像停在 3308542」这句作废。谁摘的、何时、为什么未知,gh 查不到保护变更历史。\n 本会话未恢复保护、未改动任何 GitHub 设置——不知原委时自行配回去,风险大于留着不动。\n\n② 计费没解决,原记录前半截仍成立:该次直推触发的 run 35410044850 三 job failure、\n 五 skipped,注解逐字仍是 recent account payments have failed。\n\n故「镜像推得动」≠「远端验过了」:这批提交在 GitHub 上一次门禁都没跑过,远端只是有了代码。\n\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:45:16-07:00"}],"HeadCommit":{"Sha1":"b90d7a151e5e9451fa12fb6e883b8898552124df","Message":"chore(reports): C 组三份真实验收回绑 @ 8a621fd —— 在 adversarial 隔离栈上跑,共享底座与 ms23 均未触碰\n\nC 组(runtime-acceptance / mainline-acceptance / revocation-sla)需要真实 PG + Redis + Redpanda。\nms23 那套 35 分钟前刚被并行会话用过(容器 Exited),按 docs/持久主线本地验收.md「同名 project 即使\n容器刚启动也不能直接 up 覆盖,该名称已占用时应协调或选择已有获准且无人使用的测试环境」,改用\nadversarial(PG 55473 / Redis 56382 / Broker 59095,2026-09-12 获准、闲置 3 天、其 Broker 已在故障\n注入白名单)。全程 docker start 既有容器,未 compose up 覆盖任何 project。\n\n结果(均在干净检出 8a621fd 上产出,worktreeDirty=false):\n runtime-acceptance passed 1001 tests(地板 775)、tenantRlsEnforced=1、双后端差分 0\n mainline-acceptance passed\n revocation-sla partial p95 5027ms / max 5041ms / 20 samples——远低于 MS-3 的 30s;\n partial 来自 employmentScope 链仍 pending-scope-consumer-enforcement,\n 以及生产投送/负载/staging 四项 unverified,是既定状态不是失败\n conformance-differential 作为 runtime 验收的副产物一并刷新(同样已登记 severity=warn)\n\n过程中一处失败是我搭环境搭错的,记下来免得下次再犯:首轮 e2e/identity-profile 断言\n`elevated=false` 实测 true——mainline:prepare 只为 fact/permission/audit/owner/consumer 建非超级用户\n角色,identity/credential/scope/aigateway 四个库是我用管理员 platform 手建的,identity 的连接因此是\n特权角色。REASSIGN OWNED 不适用(platform 持有系统对象),改为重建该库并 OWNER 给\nplatform_identity_test_app、以该角色重新 deploy 迁移后转绿。credential / scope 没有\nprisma:migrate:deploy 脚本是对的——它们是 state=shape 模块,按仓纪律不得有迁移。\n\n隔离与收尾:凭据只经仓外 0600 文件(/tmp/c3-mainline.env、/tmp/c3-env.sh),不入仓、不打印;\n验收在独立 worktree 里 pnpm install 自己的 node_modules,不软链主检出,避免与并行会话抢 .prisma;\nadversarial 三容器跑完恢复为 Exited(与我接手前一致)。主检出里并行会话另有十余份报告 WIP,一份没碰。\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:56-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/12093b843ef69d300370e5da16fcca3399c14d40...b90d7a151e5e9451fa12fb6e883b8898552124df","Len":2}...
|
1789778893
|
Edit
Delete
|
|
31221
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6abcd3d93 {"Commits":[{"Sha1":"6abcd3d93b19b2a73eb7869272261dde4e0b66d5","Message":"chore(reports): 新镜像连带过期的四份,收三份回绑 @ dd6de71;image-smoke 如实留红\n\n重建 runtime 镜像后 reports/image-digest.json 变了,它同时落在四份报告的作用域里,四份一起过期。\n这四份都是我造成的,一次批量收:\n\n deployed-runtime passed 容器镜像与 image-digest 一致 @ b90d7a1\n release-manifest partial 仍缺 signature(与 registry 镜像绑定的 cosign 验证),是结论不是失败\n sbom 已刷新 lockfile 模式,随新镜像的源提交重算\n\n**image-smoke 没收,如实留在过期状态**,理由写清楚免得下一个人重走一遍:\n- 它要 `--env-file`,仓里没有也不该有;`.secrets/enterprise-platform-runtime-dev.env` 是给 compose 用的,\n 里面的 DB / Redis 主机名是 compose 服务名,独立 `docker run` 的容器不在那张网里,解析不到;\n- 默认端口 53001 被 dev 常驻 runtime 占着,换 --port 53051 可以绕开端口冲突,但上面那条解析不了,\n 实测 api-health HTTP 0、HEALTHCHECK unhealthy;\n- runbook §2 写的是「指向本机底座时主机名用 host.docker.internal」——要跑得先造一份改写过主机名与端口的\n env 变体。那是新配置,不在本次范围,也不该由我随手拼。\n跑出来的那份 failed 报告**没有拷回主检出**(在临时 worktree 里 git checkout 还原了)——不拿失败结果\n冒充证据,也不让它把一份原本只是\"过期\"的报告变成\"失败\"。\n\n做法同前:企业控制面/.worktrees/settle 干净检出(HEAD dd6de71),只软链 runtime/node_modules,\n跑完把三份 report + sbom.spdx.json 拷回,按 pathspec 提交。三份 provenance 均 dd6de71、worktreeDirty=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-18T17:58:16-07:00"},{"Sha1":"dd6de7125d4ff5c3a32855f67adc483a2cb2c22a","Message":"chore(reports): 工作台两份快照回绑 @ a818ec2 —— 这次内容真的变了(新镜像 + rc.6)\n\n上一次回绑(d7d9fe5)是纯背书,索引内容一字未变。这次不同,两份都有实质变化:\n ops.image ref 05e3826e9e9e → b90d7a151e5e,digest c086993…→ fe5570f…,source_sha 与 built_at 同步\n (B 组重建镜像换容器的结果,a818ec2)\n ops.release version 1.0.0-rc.3 → 1.0.0-rc.6,source_sha 04d02d6 → e3b9d12,三个包版本随之更新\n (并行会话的 rc.6 列车)\n catalog entries 与包版本同步刷新\n\n成因就是它的作用域设计:reports/image-digest.json、release-manifest、evidence-freshness 都在里面,\n任一输入变更即过期——我提交 image-digest.json 的那一刻它就该重跑。\n\n零依赖脚本,在 企业控制面/.worktrees/rebind-ops2 干净检出(HEAD a818ec2)跑\nnode governance/build-workbench-snapshots.mjs,确认 git status 为空后出报告,两份拷回主检出、\n按 pathspec 提交。两份 provenance 均 gitSha=a818ec2、worktreeDirty=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-18T17:56:53-07:00"},{"Sha1":"a818ec2cb2324fc14720fdfc1bc5f07b9cf38309","Message":"chore(reports): B 组 deployed-runtime 转绿 @ b90d7a1 —— 重建 runtime 镜像并换掉 dev 常驻容器\n\ndeployed-runtime 此前 failed:BUILT_IMAGE_SOURCE_BEHIND——运行容器的镜像源停在 05e3826,HEAD 已有\n23 个运行时输入变更,其中含本会话 10 处接线改的那批 fixture-evaluator 与夹具。这条不是重跑报告能收的,\n必须真重建镜像并换容器。\n\n做了什么:\n1. pnpm image:build —— 上下文是 git archive HEAD:runtime(只取已提交的树,不受任何 WIP 影响),\n token 只作 BuildKit secret。产出 enterprise-platform/runtime:b90d7a151e5e,\n image id sha256:fe5570f5cb60…,linux/arm64,195 MB;reports/image-digest.json 随之更新。\n2. 按 runbook §1 的既定写法换镜像:改 .secrets/enterprise-platform-runtime-dev.env 里的\n PLATFORM_RUNTIME_IMAGE 为 \u003cname\u003e@sha256:\u003cimage id\u003e(改前已备份为 .bak-20260919-b90d7a1,该文件在仓外、0600),\n docker compose --env-file … up -d --no-deps runtime 重建。未动底座其他 12 个服务。\n3. 容器 healthy,/api/health 200:{\"status\":\"ok\",\"service\":\"nestjs\",\"checks\":{\"database\":\"up\",\"redis\":\"up\"}}。\n4. 在干净检出跑 node governance/check-deployed-runtime.mjs --write-report → passed @ b90d7a1。\n\n一处踩坑记下来:check-deployed-runtime.mjs 只有带 --write-report 才落盘,不带就只打印。我前两次跑完\n以为报告已更新,实际文件还是 06c3d4c 那份——git status 不显示改动才发现。别被 ✓ 骗了。\n\nreports/image-digest.json 一并提交:它是本次构建的产物,也是 deployed-runtime 与 release-manifest 的\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:52:23-07:00"}],"HeadCommit":{"Sha1":"6abcd3d93b19b2a73eb7869272261dde4e0b66d5","Message":"chore(reports): 新镜像连带过期的四份,收三份回绑 @ dd6de71;image-smoke 如实留红\n\n重建 runtime 镜像后 reports/image-digest.json 变了,它同时落在四份报告的作用域里,四份一起过期。\n这四份都是我造成的,一次批量收:\n\n deployed-runtime passed 容器镜像与 image-digest 一致 @ b90d7a1\n release-manifest partial 仍缺 signature(与 registry 镜像绑定的 cosign 验证),是结论不是失败\n sbom 已刷新 lockfile 模式,随新镜像的源提交重算\n\n**image-smoke 没收,如实留在过期状态**,理由写清楚免得下一个人重走一遍:\n- 它要 `--env-file`,仓里没有也不该有;`.secrets/enterprise-platform-runtime-dev.env` 是给 compose 用的,\n 里面的 DB / Redis 主机名是 compose 服务名,独立 `docker run` 的容器不在那张网里,解析不到;\n- 默认端口 53001 被 dev 常驻 runtime 占着,换 --port 53051 可以绕开端口冲突,但上面那条解析不了,\n 实测 api-health HTTP 0、HEALTHCHECK unhealthy;\n- runbook §2 写的是「指向本机底座时主机名用 host.docker.internal」——要跑得先造一份改写过主机名与端口的\n env 变体。那是新配置,不在本次范围,也不该由我随手拼。\n跑出来的那份 failed 报告**没有拷回主检出**(在临时 worktree 里 git checkout 还原了)——不拿失败结果\n冒充证据,也不让它把一份原本只是\"过期\"的报告变成\"失败\"。\n\n做法同前:企业控制面/.worktrees/settle 干净检出(HEAD dd6de71),只软链 runtime/node_modules,\n跑完把三份 report + sbom.spdx.json 拷回,按 pathspec 提交。三份 provenance 均 dd6de71、worktreeDirty=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-18T17:58:16-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/b90d7a151e5e9451fa12fb6e883b8898552124df...6abcd3d93b19b2a73eb7869272261dde4e0b66d5","Len":3}...
|
1789779515
|
Edit
Delete
|
|
31222
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"07df639ac {"Commits":[{"Sha1":"07df639ac88e1f0ec5a24d21c120bc36e2e722fa","Message":"chore(reports): 工作台两份快照回绑 @ 3eb37ea —— image-smoke 转绿与 runbook 新增章节都进了索引\n\n本会话第三次回绑这两份,成因还是那条作用域设计:docs/runbook.md 与一批 reports 都在里面,\n任一输入变更即过期。这次变的是 runbook §2 新增的 smoke env 生成配方,以及 image-smoke 由过期转 passed。\n内容确有变化(不是纯背书)。\n\n零依赖脚本,干净检出(HEAD 3eb37ea)生成,两份 provenance 均 worktreeDirty=false。\n\n至此 check:evidence 43 份全新鲜。本会话在证据线上收的:\n A 组 release-manifest / port-conformance(sbom 由并行会话收)\n B 组 deployed-runtime —— 重建 runtime 镜像并换掉 dev 常驻容器\n C 组 runtime-acceptance / mainline-acceptance / revocation-sla —— adversarial 隔离栈上真实验收\n 连带 image-digest / image-smoke / sbom / 工作台两份快照\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-18T18:05:37-07:00"},{"Sha1":"3eb37eaf82da1668fb94e3f5c9f06511da52f51a","Message":"chore(reports): image-smoke 转绿 @ 6abcd3d,并把 smoke env 的生成配方写进 runbook\n\n上一条(6abcd3d)把 image-smoke 如实留红,理由是「需要一份主机名改写过的 env 变体,那是新配置」。\n这次把它造出来跑通了,证据面最后一条红清掉。\n\n配方不是手拼的——手拼必错,因为容器侧变量名与 .secrets/…-runtime-dev.env 的键名不是一套\n(compose 里是 `DATABASE_URL: ${PLATFORM_RUNTIME_DATABASE_URL}` 这样映射的)。做法是从\n`docker compose config --format json` 解析出 runtime 的**已解析环境**(32 个变量),只改三处主机名\n(postgres:5432 / redis:6379 / otel-collector:4318 → host.docker.internal + 已发布端口,共 12 个键被改写),\n写进 .secrets/enterprise-platform-runtime-smoke.env(0600,仓外)。\n\n跑通后发现自己漏遵守 runbook 一条,已改正:REDIS_URL 继承了 dev 的逻辑库 14,而 runbook 明写\n「别用 dev 常驻运行时占着的那个,借未分配的」。首轮(db14)虽然六项全绿,但那是和常驻运行时共用\n一个逻辑库;改为 db15 后重跑,六项仍全绿,回绑的是改正后这一份。\n顺带记下一个表本身没说的坑:stack/provision/redis-dbs.json 里 14 / 15 都标未分配,\n**实际占用要看 .secrets 的 dev env,不是看表**。\n\n冒烟结果(镜像 fe5570f5cb60 @ b90d7a1,即 B 组重建的那个):\n container-running / api-health-200(database+redis up)/ platform-modules-view(fail-closed,七模块)\n / module-health-200 / decisions-unauthenticated-401 / docker-healthcheck-healthy —— 六项全绿\n\n报告在干净检出(HEAD 6abcd3d)产出,provenance dirty=false,sourceSha b90d7a1(镜像源提交,与本次\n运行绑定不同是正常的,runbook 已说明)。配方连同两处踩坑写进 docs/runbook.md §2,免得下一个人重走。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T18:05:08-07:00"}],"HeadCommit":{"Sha1":"07df639ac88e1f0ec5a24d21c120bc36e2e722fa","Message":"chore(reports): 工作台两份快照回绑 @ 3eb37ea —— image-smoke 转绿与 runbook 新增章节都进了索引\n\n本会话第三次回绑这两份,成因还是那条作用域设计:docs/runbook.md 与一批 reports 都在里面,\n任一输入变更即过期。这次变的是 runbook §2 新增的 smoke env 生成配方,以及 image-smoke 由过期转 passed。\n内容确有变化(不是纯背书)。\n\n零依赖脚本,干净检出(HEAD 3eb37ea)生成,两份 provenance 均 worktreeDirty=false。\n\n至此 check:evidence 43 份全新鲜。本会话在证据线上收的:\n A 组 release-manifest / port-conformance(sbom 由并行会话收)\n B 组 deployed-runtime —— 重建 runtime 镜像并换掉 dev 常驻容器\n C 组 runtime-acceptance / mainline-acceptance / revocation-sla —— adversarial 隔离栈上真实验收\n 连带 image-digest / image-smoke / sbom / 工作台两份快照\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-18T18:05:37-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/6abcd3d93b19b2a73eb7869272261dde4e0b66d5...07df639ac88e1f0ec5a24d21c120bc36e2e722fa","Len":2}...
|
1789780029
|
Edit
Delete
|
|
31224
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"97d61aa71 {"Commits":[{"Sha1":"97d61aa7117c2f88c4ba5e0bdf4a5b5660f2ecbe","Message":"chore(reports): check:evidence 自身回绑 @ fe9fdca —— 43 份全新鲜,状态由 partial 转 passed\n\n仓里这份还停在 2026-09-18 07:28(绑 a4b3d35),记的是 status=partial、34 新鲜 / 3 过期。\n那三条是 runtime/reports/runtime-acceptance、reports/revocation-sla、reports/mainline-acceptance,\n都因 runtime/test/e2e/identity-profile.test.ts 变更而过期,已在 b90d7a1 那轮收掉;\n只是没人把 check:evidence 自己重跑回绑,证据面的总账一直落后于实况。\n\n本次在干净树上重跑(HEAD fe9fdca,provenance.worktreeDirty=false,门禁 exit 0):\n 43 份已登记,43 份新鲜、0 份过期、0 份输入未提交、0 份无有效绑定、0 份例外\n 0 条告警;10 份未登记作用域,其中 0 份无处置说明\n\n也顺带验了前两个提交没有连带效应:十份零依赖门禁回绑到 07df639 / c570056 之后,\n工作台两份快照等以 reports 为输入的报告仍然新鲜,没有被重新判过期。\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-18T18:16:11-07:00"},{"Sha1":"fe9fdca41e28e3cbfc84f1ece8f76b068781647b","Message":"chore(reports): catalog-drift 与 facts 回绑 @ c570056 —— 在主工作区干净态下重跑\n\n这两份不能走 rebind-reports:它的临时检出在工作区之外,catalog-drift 因此读不到工作区\n(workspaceAvailable 由 true 变 false、candidates 4→0、catalogDriftUnknown 0→154,\n多出一千两百行 unknown 条目),check:facts 则会把临时目录路径写进 candidatesDir。\n改在主工作区跑,用的是上一提交刚腾出的干净窗口:先跑 catalog:drift(树干净 → dirty=false),\n把产出移出工作区、还原文件,再跑 check:facts(树仍干净 → dirty=false),最后把 drift 那份放回来。\n两份因此绑同一个提交 c570056,且 provenance.worktreeDirty 都是 false。\n\n结论与 17:11 那轮在途版本逐字一致(剔除 provenance 三行后无差异),不是靠重跑改出来的:\n catalog:drift —— error 0 / drift 0 / info 5 / unknown 0,工作区可用\n check:facts —— 16 个声明 Fact 全部可追溯(Catalog 11 / 候选 5)\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T18:15:40-07:00"},{"Sha1":"c5700568890c95adf58272c1755e20a54f512d77","Message":"chore(reports): 八份零依赖门禁回绑 @ 07df639 —— 覆盖上一轮绑 1de65fb/dirty 的在途版本\n\n工作区里躺着的这八份是 2026-09-18 17:11—17:26 本地跑的,绑的是\n1de65fb(caddy / catalog-reconciliation / fact-pii / migration-decs / module-imports / otel)、\n5116dc5(ci-mirror)与 6687aec(gate-flow)。前七份 provenance.worktreeDirty=true,\n按状态措辞纪律只能绑本地;而 HEAD 此后又走了六个提交(b90d7a1 … 07df639),\n直接提交等于把一份旧输入、脏树的结论写进证据面。\n\n改用 rebind-reports 在 HEAD 07df639 的干净检出里重跑这八个门禁:\n八份全部门禁 exit 0,provenance 均为 07df639 / worktreeDirty=false。\n\n结论与重跑前一致,没有靠重跑把红洗绿:\n caddy / catalog-reconciliation / migration-decs / otel —— findings 0\n fact-pii / module-imports —— violations 0\n gate-flow / ci-mirror —— status=passed,findings 0\nfact-pii 比上一份已提交的报告多出 scanDirs 与 rulesSource 两个字段,\n那是脚本里早已提交的改动第一次落进报告,不是本次新增的判据。\n\ncatalog-drift 与 facts 不在这一提交里:rebind 的临时检出在工作区之外,\n前者因此读不到工作区(workspaceAvailable true→false,catalogDriftUnknown 0→154,\n多出一千两百行 unknown 条目),后者会把临时目录路径写进 candidatesDir。\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-18T18:15:09-07:00"}],"HeadCommit":{"Sha1":"97d61aa7117c2f88c4ba5e0bdf4a5b5660f2ecbe","Message":"chore(reports): check:evidence 自身回绑 @ fe9fdca —— 43 份全新鲜,状态由 partial 转 passed\n\n仓里这份还停在 2026-09-18 07:28(绑 a4b3d35),记的是 status=partial、34 新鲜 / 3 过期。\n那三条是 runtime/reports/runtime-acceptance、reports/revocation-sla、reports/mainline-acceptance,\n都因 runtime/test/e2e/identity-profile.test.ts 变更而过期,已在 b90d7a1 那轮收掉;\n只是没人把 check:evidence 自己重跑回绑,证据面的总账一直落后于实况。\n\n本次在干净树上重跑(HEAD fe9fdca,provenance.worktreeDirty=false,门禁 exit 0):\n 43 份已登记,43 份新鲜、0 份过期、0 份输入未提交、0 份无有效绑定、0 份例外\n 0 条告警;10 份未登记作用域,其中 0 份无处置说明\n\n也顺带验了前两个提交没有连带效应:十份零依赖门禁回绑到 07df639 / c570056 之后,\n工作台两份快照等以 reports 为输入的报告仍然新鲜,没有被重新判过期。\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-18T18:16:11-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/07df639ac88e1f0ec5a24d21c120bc36e2e722fa...97d61aa7117c2f88c4ba5e0bdf4a5b5660f2ecbe","Len":3}...
|
1789780647
|
Edit
Delete
|
|
31225
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"51e311bf4 {"Commits":[{"Sha1":"51e311bf417385a994296f20da3b9458761bdee8","Message":"docs(部署): 登记第二次「重新部署运行」——判据仍指向只重启,但 identity 跑的是旧构建\n\n与 §12 同形态的请求,前置判据同法重算,结论同样是不重建镜像:镜像源 b90d7a1 →\nHEAD 07df639 的 runtime/ 与 stack/ 变更均为零文件,未提交改动不碰运行时输入,\n容器镜像 ID 与 reports/image-digest.json 逐字一致(sha256:fe5570f5cb60…)。\n13 个 stack 容器一个没动。\n\n与 §12.1 的两点差别记在 §18.1 / §18.2:\n- 这次跑了 check:deployed(passed / IMAGE_SOURCE_EQUIVALENT,在 07df639 上),\n 但脚本在脏树上没有落盘,reports/deployed-runtime.latest.json 仍是 dd6de712 那份、\n worktreeDirty=false,未被本轮污染——所以那一行的证据形态是门禁 stdout,不是回绑报告。\n- 这轮重启有实据,不只是「判据说该做的只有启动那半」:identity 的 dist/src/main.js\n 在 17:31 重建过,而在跑的进程是 07:57 起的,跑的是旧构建;web 与工作台的 .next\n 均不落后于源码。停 pid 5209/18658/43950,按 .claude/launch.json 重起。\n\n重启后复验 11 项全绿(§18.3):identity 无凭证 401 / 现签 HS256 令牌 200、\n控制面 /api/platform/{catalog,modules} 200、CORS 预检 204 带 authorization、\n工作台「读取探针」ok 且 database/redis up、常驻容器经 Caddy :58080 与直连 :53001 均 200、\n:3098 transport 为 Connected(D-8 注入生效)、控制台零错误。\n\n§18.4 登记一条未定位的观察:有个不带凭证的客户端每 2 秒打一次 identity 的 /api/users\n(401,失败关闭)。不是本轮重启带出来的——新进程 18:14:46 起、它 18:15:29 就接上了;\n三个浏览器标签页的 network 抓取里都没有这批请求,lsof 只见一条绕过 :3098 代理、\n直连 127.0.0.1:3101 的长连接。未定位到具体页面,该节不作结论。\n\n提交时 HEAD 已被并行会话推到 97d61aa,期间三个提交全是 chore(reports)、\nruntime/ 与 stack/ 零变更,故 §18.1 的判据在新 HEAD 上仍然成立,正文不改。\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-18T18:19:04-07:00"}],"HeadCommit":{"Sha1":"51e311bf417385a994296f20da3b9458761bdee8","Message":"docs(部署): 登记第二次「重新部署运行」——判据仍指向只重启,但 identity 跑的是旧构建\n\n与 §12 同形态的请求,前置判据同法重算,结论同样是不重建镜像:镜像源 b90d7a1 →\nHEAD 07df639 的 runtime/ 与 stack/ 变更均为零文件,未提交改动不碰运行时输入,\n容器镜像 ID 与 reports/image-digest.json 逐字一致(sha256:fe5570f5cb60…)。\n13 个 stack 容器一个没动。\n\n与 §12.1 的两点差别记在 §18.1 / §18.2:\n- 这次跑了 check:deployed(passed / IMAGE_SOURCE_EQUIVALENT,在 07df639 上),\n 但脚本在脏树上没有落盘,reports/deployed-runtime.latest.json 仍是 dd6de712 那份、\n worktreeDirty=false,未被本轮污染——所以那一行的证据形态是门禁 stdout,不是回绑报告。\n- 这轮重启有实据,不只是「判据说该做的只有启动那半」:identity 的 dist/src/main.js\n 在 17:31 重建过,而在跑的进程是 07:57 起的,跑的是旧构建;web 与工作台的 .next\n 均不落后于源码。停 pid 5209/18658/43950,按 .claude/launch.json 重起。\n\n重启后复验 11 项全绿(§18.3):identity 无凭证 401 / 现签 HS256 令牌 200、\n控制面 /api/platform/{catalog,modules} 200、CORS 预检 204 带 authorization、\n工作台「读取探针」ok 且 database/redis up、常驻容器经 Caddy :58080 与直连 :53001 均 200、\n:3098 transport 为 Connected(D-8 注入生效)、控制台零错误。\n\n§18.4 登记一条未定位的观察:有个不带凭证的客户端每 2 秒打一次 identity 的 /api/users\n(401,失败关闭)。不是本轮重启带出来的——新进程 18:14:46 起、它 18:15:29 就接上了;\n三个浏览器标签页的 network 抓取里都没有这批请求,lsof 只见一条绕过 :3098 代理、\n直连 127.0.0.1:3101 的长连接。未定位到具体页面,该节不作结论。\n\n提交时 HEAD 已被并行会话推到 97d61aa,期间三个提交全是 chore(reports)、\nruntime/ 与 stack/ 零变更,故 §18.1 的判据在新 HEAD 上仍然成立,正文不改。\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-18T18:19:04-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/97d61aa7117c2f88c4ba5e0bdf4a5b5660f2ecbe...51e311bf417385a994296f20da3b9458761bdee8","Len":1}...
|
1789780810
|
Edit
Delete
|
|
31227
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"b69710a74 {"Commits":[{"Sha1":"b69710a74604d55a435971103dc033025cbc6e6b","Message":"docs(治理): 建宿主协议签收单目录——C-3 附条件的执行面,六份逐域单全部未签收\n\n立项这件事在本体系里已经被裁过:决策批次-2026-09-16 的 C-3(✅ 采纳)把九个契约域的\n运行宿主裁给上层既有宿主,附条件写死「宿主协议……签收才算准入」,Q01 原文还有两句更硬的\n——「签收前不运行」与「不得以『方便实现』自动新增 M8」。裁决当天的执行顺序 §3 第 4 条\n即为「C-3 宿主协议逐域签收 → Catalog 六项去向」,而建本目录之前,全仓「宿主协议」四字\n只出现在三篇设计文档里,零份签收材料:空着的不是立项,是签收。\n\n本次按十三项最小内容(能力ID / 数据Owner / 运行Owner / 库 / 对外契约 / 鉴权 / 备份 /\nSLO / 值班 / 依赖 / 预算 / 升级退出 / 消费者清单)逐域建单,五份对应 C-3 承接表:\nC15 跨域流程、C16 企业 IM、C17 数据分析、C18 统一体验、C19 成本与容量,状态一律「未签收」。\n每份代填的只有本仓可机器核验的字段(规则文件与行数、域测试、失败关闭夹具例数、Catalog\n登记与 blockers、本域特有约束),宿主侧字段一律空缺;本目录不代任何 Owner 签字,\n不改任何 Catalog 字段——Catalog 去向登记是签收之后的动作,须走 CHG。\n\n三处不能读岔的,逐单复写:\n- C19 的宿主按 C-3 是「复用 C17 选定宿主」,C17 未签收前它的宿主栏无从填起;且 C-15 改案\n 把订阅计量与出账并入本域,范围改写材料 CHG-017 待签,签前须先确认适用哪版范围。\n- C18 的宿主是劈成两半的:企业业务 Shell 归数字员工基座(本单要签的那半),平台自身入口\n 由本仓独立工作台承载(CHG-018 修正,不走宿主签收)。工作台已在本机 dev 跑起来,\n 不构成把 enterprise-experience 读成「已有承接」的理由。\n- C15 是六域里唯一带「无合格宿主则另提运行承接裁决」口子的,那是 Q01 给新建运行承接\n (含本仓模块)留的唯一合法入口,走它要附至少两个宿主方案的成本与迁移影响,不是跳过签收。\n\nC01 注册中心单列为「不适用」:C-3 的承接表只覆盖 C11—C19,注册中心是 C01、责任在\nCatalog Owner / 平台工程,权威状态是获批的 Git 内容,没有「托管到某个上层业务应用」这个选项。\nA-2 附条件里「注册中心项已由 CHG-013 / 014 处理」指的是登记面(code_truth 改指、证据归零),\n不是运行承接裁决。它真正卡的是六条 blocker(DEC-009/010/011/012/031/032)的落地面——\n六条都已 approved,所以不是等裁决,是这些裁决在本域还没有对应实现。\n\n一条五份单共同的前置(机器实测 2026-09-18):六个域在 contracts/ 里已登记的 HTTP 契约与\nFact 都是 0——contracts/contracts/ 的 7 份 OpenAPI 全属七模块,facts.json 对六域一条没有。\n按仓纪律 1「模块新增端口 / Fact 必须先登记 contracts/」,登记对外契约必须发生在签收之前,\n否则宿主签的是一份没有接口定义的协议。\n\n同时在 Q01 的「待改产物 / 责任」后补一段「签收面」指向本目录,避免新目录成为孤儿文档。\n门禁:治理层 check-workspace-consistency 重跑,除在案常驻的 L9 COMPOSE_PROJECT_COLLISION\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-18T18:46:22-07:00"},{"Sha1":"7dd4429a2d0400fdd2f2e9ec2b93e8cfb6e52609","Message":"docs(工作台): 订正实现记录里「回绑」那句 —— 本轮只回绑了 runtime 作用域的两份\n\n21b0821 写记录时那句是「报告回绑单独成提交跟在本提交之后」,写的是打算而不是结果。\n实际只做到一半,记录里现在把一半的边界画出来:naming 与 fork-readiness 已在 21b0821 上\n以 worktreeDirty=false 回绑(edff342);module-imports 的输入集确实被本轮动到,但取证时\n仓根不干净——树里有并行会话正在写的未跟踪产物 docs/能力设计/宿主协议/——按仓根算就是\ndirty,回绑等于把现有 clean 绑定降级,留给干净树上补;caddy 的输入本轮一个都没动,\n不需要跟着走。\n\n也就是说这两项在 21b0821 上的证据形态是门禁 stdout 与退出码,不是回绑报告。记录 §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-18T18:46:05-07:00"},{"Sha1":"edff342c2c4e3a7b11920e51d87c32905d58280b","Message":"chore(reports): naming 与 fork-readiness 回绑 @ 21b0821 —— 根级两份这轮拿不到 clean\n\n工作台改版(21b0821)动的是 runtime/apps/workbench,naming 与 fork-readiness 的输入集\n覆盖整个 runtime/,所以这两份必须跟着走,否则 check:evidence 会把它们判成过期。两份都在\nruntime 作用域的干净树上重跑,exit 0、worktreeDirty=false。\n\n同一时刻**没有**回绑的两份,以及为什么:\n- reports/module-imports.latest.json:输入集含工作台(规则 3「工作台不得静态 import 任何\n @juhai/module-*」),确实被 21b0821 动到,但它的 provenance 按仓根算——树里有并行会话\n 正在写的 docs/能力设计/宿主协议/(未跟踪,18:43 起),按仓根算就是 dirty=true。回绑一份\n worktreeDirty=true 的报告等于把现有的 clean 绑定降级,不如留着,等干净树上补。\n- reports/caddy.latest.json:同样只能绑 dirty=true,但它的输入(modules.json、\n caddy-routes.json、两个 Caddyfile)21b0821 一个都没动,本来就不需要跟着走。\n\n本轮这四项门禁在 21b0821 上都跑过 exit 0(module-imports、caddy 的证据形态因此是门禁\nstdout,不是回绑报告)。\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-18T18:45:42-07:00"},{"Sha1":"21b0821a2898e0e2d6f4660b8c50744600dd96bb","Message":"feat(workbench): 服务目录重做与交互完善——三处「设计写了、WB-1 没落」的缺口一并补上\n\n本轮只动 runtime/apps/workbench 的前端代码:读的还是原来那三个管理读面与随构建附带的\n目录快照,不新增接口、不新增数据来源、不新增写操作,因此不改变任何模块的验收等级、\n发布档位与 Catalog 状态。\n\n先补的三处不是新功能,是已签署设计里写了而 WB-1 没实现的:\n- 快照的 conflicts / status 此前被整个忽略,页面只渲染 entries。对外交付设计 §3.1 要求\n 「来源冲突展示冲突及证据,不静默挑选更乐观的结果」,现在冲突块排在条目之前,为空时\n 明写「0 处来源冲突」——不靠「没看见」表示没有。\n- §5.3 的「显示来源、环境和更新时间」此前一处都没有。现在每个区块各自显示取数时刻、\n 可单独重取,页脚给出平台接口地址与快照路径。\n- nonce 一直是生成并随授权请求发出,回调里却从未与 id_token 比对(§8 关键验收场景 2\n 要求 PKCE / state / nonce 都正确)。现在 nonce 与 aud 在建立会话之前校验,任一不符即\n 拒绝、不落 sessionStorage;iss 不符只降级为「主体未知」并说明原因——那是 D-10 的部署\n 配置问题,不是这次登录不合法。顺带收了 expires_in 被丢弃的问题:过期令牌此前会补水成\n 「导航栏显示已登录、每个读面都报缺凭证」。\n\n服务目录从一张静态表重做成可取景的服务中心:搜索、四个筛选、排序、分组、选中条目与是否\n对照运行时整体进 URL(默认值一律不写进去,认不出的参数退回默认而不是把页面打空),筛出来\n的视图因此可以直接贴给别人。五列可排序,层按 P0 / P1 / P2 层序、模块档位按 shape →\nauthority → e2 推进序——代码注释与页面 title 都写明这是固定显示顺序、不是优劣排名。详情\n从行内展开改成宽屏常驻面板 / 窄屏行内,六个区加快照自带的 flags 口径提醒;稳定标识、包名、\ncode_truth、绑定提交与 HTTP 前缀都带复制按钮,复制的是完整值而不是截断显示的短号。快照的\ncounts 原样成摘要条,不用筛选结果重算——那是两个时刻的两件事。\n\n新增的「对照运行时」开关默认关:目录页读的是静态快照,不该因为打开一个页面就去打需要令牌\n的接口;开关进 URL,是因为收到链接的人有权知道这个视图会额外取一份数据。打开后表格多一列\n已装载 / 未装载、详情多一节运行时对照。读面失败时只在表格上方说一次(分类 + 原因 + 重试),\n行内用 —,详情那节指回去——同一条 401 不连同同一个重试按钮摆三遍。\n\n运行信息页给出模块与项目的映射及跳回目录的深链(模块 id identity 与项目标识\nenterprise-idp 不是一回事),查不到映射就不给链接。交互面另有:深色模式真正接上(此前\n.dark 变量是死代码),首帧前由内联脚本应用偏好、不闪一帧浅色;焦点环写成原生 outline 而\n不是 @apply ring-*,焦点环消失是可达性缺陷、不该由主题配置的颜色键决定;方向键只在焦点\n落进表格后接管,全局劫持等于抢走页面滚动;窄屏改为收列而不是横向滚动,上一版的详情被困在\n表格的横向滚动容器里、手机上要左右刮着读。\n\n实测与未闭环见 docs/工作台交互与服务目录完善记录-2026-09-18.md。要点两条:nonce / aud\n校验只有单测级证据,托管登录要人工输口令、本轮没走完整授权码流程;工作台仍无仓内测试装置,\n那些断言未进 pnpm check。门禁在本轮的脏树上跑绿(workbench typecheck / lint / build、\ncheck:module-imports、check:naming、check:fork-readiness、check:caddy),报告回绑单独\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-18T18:44:46-07:00"},{"Sha1":"ef1f95e091db917900dd98bf11f6385e6b176387","Message":"docs(部署): 登记「装载全部模块」——1/7 不是回归,是 :3101 的 profile 只写了 identity\n\n§11.4 与 §18.3 两处记的「已装载 1/7」都是当时的实测,本节不追改,补的是成因,\n而成因只在一条链上:常驻容器 :53001 由 compose 注入七个 profile,一直是 7/7;\n工作台读的那条链末端是裸 dev 进程 :3101,它的 PLATFORM_PROFILES 取自\n.secrets/enterprise-platform-identity-dev.env,值是 PF-07 阶段 identity 单启时的\n出厂值 'identity'。同一块读面,两个运行面给的答案差六个模块。\n\n改动一处且在仓外:该 env 第 28 行扩成七个(原件备份 .bak-20260919-profiles),\n七个 DATABASE_URL_\u003cMODULE\u003e 本来就齐、与容器指同一台 PG(容器内 postgres:5432 =\n本机 127.0.0.1:55470),迁移无须补跑;Redis 逻辑库 dev 用 5、容器用 14,不撞。\n按 .claude/launch.json 停 pid 19008、重起为 39237,:3098 / :3010 未动,\n未重建镜像、13 个 stack 容器一个没动。仓内零改动。\n\n实测(§19.3,作用域 = 本机 dev,证据等级 = 运行态链路):启动日志七模块全装载、\n10 条模块作业句柄注册、RLS enforce 校验通过;/api/platform/modules 直打 :3101 与\n经 :3098 代理均 7 条;浏览器 :3010 总览「已装载 / 已登记模块 7 / 7」。端口提供方\n四项由模块承接,其中 factExport 与 serviceCredential 改前是 fail-closed,\npermission / audit 改前走 local-tenant-scope / local-log 回退。\n\n同节写明三条不得读岔的:credential-shape 与 scope 都是 shape 档形状实现、不是权威实现;\n七个模块只有 identity 有 health 探针;装上 ≠ 有能力 ≠ 环境健康。\n\n§19.4 留下四条:① mode 仍是 local(PLATFORM_PORTS_MODE 未设置、非生产按设计回退),\n与容器的 fail-closed 不同档,要不要一并改未裁;② 两个进程现在连同一批模块库,\n队列虽按 Redis 逻辑库分开、作业也要入队才跑,但从 :3101 入队会写容器在读写的库;\n③ env 文件名 identity-dev 与内容(七模块)已名实不符,只登记;④ 本节证据不绑提交——\n裸进程没有 PLATFORM_SOURCE_SHA,且取证时工作区 dirty(工作台改版 WIP)。\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-18T18:36:44-07:00"}],"HeadCommit":{"Sha1":"b69710a74604d55a435971103dc033025cbc6e6b","Message":"docs(治理): 建宿主协议签收单目录——C-3 附条件的执行面,六份逐域单全部未签收\n\n立项这件事在本体系里已经被裁过:决策批次-2026-09-16 的 C-3(✅ 采纳)把九个契约域的\n运行宿主裁给上层既有宿主,附条件写死「宿主协议……签收才算准入」,Q01 原文还有两句更硬的\n——「签收前不运行」与「不得以『方便实现』自动新增 M8」。裁决当天的执行顺序 §3 第 4 条\n即为「C-3 宿主协议逐域签收 → Catalog 六项去向」,而建本目录之前,全仓「宿主协议」四字\n只出现在三篇设计文档里,零份签收材料:空着的不是立项,是签收。\n\n本次按十三项最小内容(能力ID / 数据Owner / 运行Owner / 库 / 对外契约 / 鉴权 / 备份 /\nSLO / 值班 / 依赖 / 预算 / 升级退出 / 消费者清单)逐域建单,五份对应 C-3 承接表:\nC15 跨域流程、C16 企业 IM、C17 数据分析、C18 统一体验、C19 成本与容量,状态一律「未签收」。\n每份代填的只有本仓可机器核验的字段(规则文件与行数、域测试、失败关闭夹具例数、Catalog\n登记与 blockers、本域特有约束),宿主侧字段一律空缺;本目录不代任何 Owner 签字,\n不改任何 Catalog 字段——Catalog 去向登记是签收之后的动作,须走 CHG。\n\n三处不能读岔的,逐单复写:\n- C19 的宿主按 C-3 是「复用 C17 选定宿主」,C17 未签收前它的宿主栏无从填起;且 C-15 改案\n 把订阅计量与出账并入本域,范围改写材料 CHG-017 待签,签前须先确认适用哪版范围。\n- C18 的宿主是劈成两半的:企业业务 Shell 归数字员工基座(本单要签的那半),平台自身入口\n 由本仓独立工作台承载(CHG-018 修正,不走宿主签收)。工作台已在本机 dev 跑起来,\n 不构成把 enterprise-experience 读成「已有承接」的理由。\n- C15 是六域里唯一带「无合格宿主则另提运行承接裁决」口子的,那是 Q01 给新建运行承接\n (含本仓模块)留的唯一合法入口,走它要附至少两个宿主方案的成本与迁移影响,不是跳过签收。\n\nC01 注册中心单列为「不适用」:C-3 的承接表只覆盖 C11—C19,注册中心是 C01、责任在\nCatalog Owner / 平台工程,权威状态是获批的 Git 内容,没有「托管到某个上层业务应用」这个选项。\nA-2 附条件里「注册中心项已由 CHG-013 / 014 处理」指的是登记面(code_truth 改指、证据归零),\n不是运行承接裁决。它真正卡的是六条 blocker(DEC-009/010/011/012/031/032)的落地面——\n六条都已 approved,所以不是等裁决,是这些裁决在本域还没有对应实现。\n\n一条五份单共同的前置(机器实测 2026-09-18):六个域在 contracts/ 里已登记的 HTTP 契约与\nFact 都是 0——contracts/contracts/ 的 7 份 OpenAPI 全属七模块,facts.json 对六域一条没有。\n按仓纪律 1「模块新增端口 / Fact 必须先登记 contracts/」,登记对外契约必须发生在签收之前,\n否则宿主签的是一份没有接口定义的协议。\n\n同时在 Q01 的「待改产物 / 责任」后补一段「签收面」指向本目录,避免新目录成为孤儿文档。\n门禁:治理层 check-workspace-consistency 重跑,除在案常驻的 L9 COMPOSE_PROJECT_COLLISION\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-18T18:46:22-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/51e311bf417385a994296f20da3b9458761bdee8...b69710a74604d55a435971103dc033025cbc6e6b","Len":5}...
|
1789782545
|
Edit
Delete
|
|
31229
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6fbebf528 {"Commits":[{"Sha1":"6fbebf5285a9a335410c5f884d81314d0394429c","Message":"chore(reports): candidate-contracts 回绑 @ 16459e0 —— 9 条探针零豁免\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:55:24-07:00"},{"Sha1":"16459e09061655eb29b432aa5a9334b9685cbced","Message":"test(contracts): 跨域流程的 plan 补第一条 ACCEPT 用例——最后一条 shape 探针豁免清零\n\ncheck:candidate-contracts 此前带着一条豁免:planWorkflowInstance 取不到 ACCEPT 载荷,\n因为 cross-domain-workflow 的 plan 规则在 28 例夹具里全是反例。查隔壁——\ncollaboration-messaging 的同类规则 P03 是有正例的。所以这不是「夹具只固定失败关闭一侧」\n的设计口径,是这一域缺了一条,而豁免让它看起来像是有意为之。\n\n补 P04-approved-snapshot-plans-an-instance:已批准快照 + 合法请求,载荷直接取自该域单测里\n那条已在跑的 planner 正例(不是新造的场景)。夹具 28 → 29 例(正 4 / 反 25),\ncheck:fixtures 该套件 29/29 失败 0,fixture-coverage 三档仍全为 0。\n\n连带把 C15 契约的探针由 skip 换成真探针(planWorkflowInstance ← plan.request):\n9 条探针全部比对通过、零豁免。门禁单测两处计数同步,并把断言从「豁免恰好是这一条」\n改成「豁免必须为空;再出现必须带理由」——前者会在下次加豁免时静默通过。\n\n数字声明同步:仓根 CLAUDE.md 的 17 套件 706 例 → 707,宿主协议 C15 单与索引底账的夹具数\n同步;check-workspace-consistency CLEAN,L13 无漂移。contracts 测试 416/416。\n\n跑这两道门禁都用 GOV_REPORT_DIR 重定向,仓里在途的 fixtures 报告一个字节未动——\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-18T19:55:21-07:00"},{"Sha1":"05497f5a3cad8b4a82d07b81504c06fe6338c972","Message":"chore(reports): candidate-contracts 回绑 @ 864231d —— 含 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-18T19:49:18-07:00"},{"Sha1":"864231dc64629e58ddd53faf5c38b4f58fdf05f9","Message":"feat(contracts): 五份候选契约有了可挂载的参考实现——11 个操作,传输无关、零框架依赖\n\nC-3 把这五个域的运行宿主裁给上层既有宿主、本仓不建模块,所以「完善 HTTP 实现」不能是在\nruntime 里加路由。但「每个宿主各写一遍入参解码与决策映射」必然各写各的:REJECT 被压成 4xx、\nSKIP_DUPLICATE 被当成失败、now 忘了从 ISO 串还原成 Date——每一个都是一次就足以让语义走样。\n把这一段写在 contracts/src/http/,判定与映射同源,宿主实现 = 挂载 + 鉴权 + 持有快照。\n\n本层不做任何入参校验,这是实测后的决定,不是省事。首版写了信封校验(非对象或缺顶层键回 400),\n被夹具 N06-definition-is-not-an-object 当场戳穿——那条用例期望的是 WORKFLOW_DEFINITION_INVALID,\n400 把它盖掉了。随后逐个实测七个规则入口:传非对象 / 空对象 / undefined,一律 REJECT 并带自己的\n原因码,没有一个抛异常。校验层不是多一道保险,是多一套词汇:同一个错两种表达,消费侧必然挑更\n好读的那套,规则的原因码就此架空。五份契约的 400 描述同步改为「宿主的 JSON 解析失败」。\n\n唯一的边界处理是 Date 还原:context.now(体验)与 context.policy.now(成本,嵌深一层)过 HTTP\n是 ISO 串而规则侧是 Date。漏了不会报错,只会让时间判定永远不触发——一条静默放行的路径。\n\n测试拿规则自己的夹具载荷经处理器走一遍:ACCEPT 例仍非 REJECT,REJECT 例 reasons 与夹具逐条一致,\n无快照时 planner 失败关闭仍是 200 REJECT 而非 5xx。contracts 测试 408 → 416/416,\ncheck:generated 无漂移。\n\n门禁加 HANDLER_MISSING / HANDLER_ORPHAN 双向对账。按文本解析 index.ts 而不是 import dist——\n本门禁在 ZERO_DEP_GATES 里,要能在没装依赖的临时检出里重跑,改成 import 就会退化成未构建即\nunavailable,干净回绑随之失效。负向实测:把 assessResourceTags 改名,两条规则各报一次。\n\n未做:catalogs/ 一字未动;本仓不挂路由、不建库、不新增模块,C-3 的「不新增 M8」未被触碰;\n401 / 403 / 503 属宿主责任,不在本层。\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:49:15-07:00"},{"Sha1":"fb371d6cec3a76db97335f51a352cef8c2d7c7b4","Message":"chore(reports): candidate-contracts 回绑 @ fdbefc9 —— 补 rules-entry 后重跑,仍 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-18T19:41:03-07:00"}],"HeadCommit":{"Sha1":"6fbebf5285a9a335410c5f884d81314d0394429c","Message":"chore(reports): candidate-contracts 回绑 @ 16459e0 —— 9 条探针零豁免\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:55:24-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/b69710a74604d55a435971103dc033025cbc6e6b...6fbebf5285a9a335410c5f884d81314d0394429c","Len":24}...
|
1789786673
|
Edit
Delete
|
|
31233
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"928345d27 {"Commits":[{"Sha1":"928345d27ed7ade91e7257238a55e64e9f9c6fad","Message":"chore(reports): evidence-freshness 回绑 —— 45 份已登记 / 40 份新鲜 / 5 份过期 / 0 error\n\n余下 5 条告警都要真实底座或镜像:sbom、runtime-acceptance、ui-acceptance、\nmainline-acceptance、deployed-runtime。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T23:02:49-07:00"},{"Sha1":"be810fc355f9fdb4949343677ce6769bb61d7459","Message":"chore(reports): port-conformance 与 release-manifest 回绑 @ 2e06b92 —— 过期告警 7 → 5\n\n- port-conformance:3 个套件 passed(此前绑 e3b9d12,作用域内已 19 个文件变更)。\n- release-manifest:status 仍非 complete,缺项 6 条且逐条有出口——4 个客户端包未建(CL-1…7)、\n images.runtime.digest(镜像绑 b90d7a1 ≠ 当前 HEAD,须重建)、registryDigest(只有本机构建\n 证据)、images.stack.* 1 个镜像未按 digest 锁定(PF-05 / PF-23)、sbom、signature。\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-18T23:02:47-07:00"},{"Sha1":"2e06b9267b4aaa1ebfbd1e1329f61d2c717c587e","Message":"chore(reports): runtime 静态门禁 18 份回绑 @ 808740f —— 过期告警 13 → 7\n\n跑一次 `pnpm --dir runtime check`(EXIT 0,链上 17 条判词全绿)后,runtime/reports 下\n18 份报告全部重写并绑 808740f / dirty=false。其中 7 份此前是 check:evidence 的\nEVIDENCE_STALE 告警:agent-adapters、docs-truth、dual-backend-parity、fork-readiness、\ngovernance-docs、naming、runtime-governance。\n\ncheck:evidence:45 份已登记 / 38 份新鲜 / 7 份过期 / 0 error。余下 7 条告警都要真实底座、\n容器或镜像才能重跑,不在本批范围:release-manifest、sbom、port-conformance、\nruntime-acceptance、ui-acceptance、mainline-acceptance、deployed-runtime。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T23:01:20-07:00"},{"Sha1":"808740f25add20c3e449cfde913d31ab6715a297","Message":"chore(reports): evidence-freshness 回绑 @ d7c1e0a —— error 清零(5 → 0),余 13 条 warning\n\nA7 出口达成:check:evidence 退出 0、status=partial、error 0 条(45 份已登记 / 32 份新鲜 /\n13 份过期 / 0 份输入未提交 / 0 份无有效绑定 / 0 份例外)。\n\n余下 13 条一律 warning,且都要真实底座或容器才能重跑,不在本批范围:\nruntime-acceptance / ui-acceptance / mainline-acceptance / naming / fork-readiness /\ndual-backend-parity / governance-docs / docs-truth / agent-adapters / port-conformance /\ndeployed-runtime 等。它们是「结论可能已被后续提交推翻」,不是「结论造假」——引用前须重跑。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T22:57:41-07:00"},{"Sha1":"d7c1e0a589f538b720c6fdfda14bbc7bff241c79","Message":"chore(reports): 夹具两份从脏绑改为干净回绑 @ 408d344\n\n两份此前绑在脏树 6fbebf5 上却被提交,check:evidence 因此判 EVIDENCE_BOUND_DIRTY\n(severity=error)。在干净树重跑(需构建产物,不在 reports:rebind 的范围内,\n故直接在主工作区跑):\n\n- check:fixtures 17 套件 702 例 0 失败 0 不可用,与脏绑那次逐项一致;\n- check:fixture-coverage 15 个套件、未接线 0 处、都没有 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-18T22:57:15-07:00"}],"HeadCommit":{"Sha1":"928345d27ed7ade91e7257238a55e64e9f9c6fad","Message":"chore(reports): evidence-freshness 回绑 —— 45 份已登记 / 40 份新鲜 / 5 份过期 / 0 error\n\n余下 5 条告警都要真实底座或镜像:sbom、runtime-acceptance、ui-acceptance、\nmainline-acceptance、deployed-runtime。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T23:02:49-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/6fbebf5285a9a335410c5f884d81314d0394429c...928345d27ed7ade91e7257238a55e64e9f9c6fad","Len":11}...
|
1789798036
|
Edit
Delete
|
|
31236
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"623a58d18 {"Commits":[{"Sha1":"623a58d184232de4493761b6612202abae6561c0","Message":"chore(reports): evidence-freshness 回绑 @ 3be0bb7 —— 41 份新鲜 / 4 份过期 / 0 error\n\n余 4 条告警都要真实底座或镜像:sbom、runtime-acceptance、ui-acceptance、deployed-runtime。\nmainline-acceptance 随 A15 的六套件重跑已转新鲜。\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:06:02-07:00"},{"Sha1":"3be0bb7a8ae0ccbecf762475be4425a7eced5038","Message":"chore(reports): 工作台两份快照 / doc-claims / caddy / otel 回绑 @ 5ef56d0\n\n两件事各一半:\n- 并行会话的 `bd2a5c3` 改了 `docs/runbook.md`,它在 workbench-ops-snapshot 的作用域里,\n `check:evidence` 因此判其过期(本轮唯一一条 error)。\n- 本会话把 `docs/runbook.md` / `README.md` / `reports/otel.latest.json` 加进了 doc-claims\n 的作用域,该报告随之要重绑。\n\ncaddy / otel 一并带上(同一次干净检出里顺手跑,判词不变)。四份全部 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-19T00:05:43-07:00"},{"Sha1":"5ef56d011b28e1000e575b67d354594f53249039","Message":"chore(reports): mainline-acceptance 与 revocation-sla 回绑 @ 51f100b —— 首份六套件 72 例\n\nA15 接线后首次在干净树上跑完整主线(专用 Broker `enterprise-platform-ms23-redpanda-1`\n:59093 + 6 个隔离库,全部非超级用户角色):\n\n| 套件 | 例数 |\n|---|---|\n| fact-read-http | 11 |\n| fact-persistence | 17 |\n| audit-tamper | 19 |\n| mainline-revocation-chaos | 18 |\n| **permission-ops**(新) | **2** |\n| **ai-route-persistence**(新) | **5** |\n\n合计 72 例、0 失败、0 skipped/todo,`validateMainlineReport` 通过。revocation-sla 仍\n`partial`:cacheBound 与 invalidationPush 各 20 个真实样本,后者的传输仍是 test-harness\nledger poll,生产传输未接线——定性不变。\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:05:16-07:00"},{"Sha1":"51f100b42bb2cb89db3609bf69f88835c26aa236","Message":"feat(governance): 两支无门禁消费的 integration 套件接进主线(A15),并补齐 A14 的作用域\n\n**缺口**:四个模块有 `vitest.integration.config.ts`,但 `check-mainline.mjs` 只消费 fact 与\naudit 两支;`permission` 的 `ops.integration.ts`(OPS-1 受控命令 permission.invalidation 的\n真实库验收)与 `ai-gateway` 的 `persistence.integration.ts`(ai-route 权威账本)**没有任何\n门禁消费**,只能靠人手工 `pnpm test:integration`——写了验收却没有任何东西会在它坏掉时叫。\n\n- `check-mainline.mjs` 增两支套件:`permission-ops`、`ai-route-persistence`。它们要的正是\n 本文件已经在准备的那套隔离库,接进来不需要新底座。\n- `lib/mainline-evidence.mjs` 登记地板(按首次隔离库实测,非超级用户角色):2 例 / 5 例。\n 该表同时供 runner 与 `verify:candidate` 使用,`validateMainlineReport` 要求套件数与本表\n 一致——所以「接线」和「候选可晋级核验」是同一件事,不会只改一半。\n- `prepare-mainline.mjs` 增 `aigateway` 一档:`platform_aigateway_ms23` 此前不存在(只有 dev\n 库),ai-gateway 的 integration 套件因此在任何隔离环境里都跑不起来。顺带修一处会绊下一个\n 人的坑——**库名的 kind 与模块目录名不总是同一个词**(`aigateway` ↔ `ai-gateway`),改为显式\n `moduleDir` 映射,不靠字符串等同。\n- `evidence-scopes.json` 补 A14 漏的一半:`doc-claims` 的 scope 加 `README.md`、\n `docs/runbook.md`、`reports/otel.latest.json`。扩了扫描面却没扩作用域,等于那三处一变\n 本报告也不会被判过期。\n\n**实测**(`enterprise-platform-ms23` 专用 Broker :59093 + 6 个隔离库,非超级用户):\n六套件全过 11 / 17 / 19 / 18 / **2** / **5** = 72 例,`mainline:check` 退出 0,\n`validateMainlineReport` 通过。报告回绑另起提交(本次运行时工作树是脏的)。\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:02:22-07:00"},{"Sha1":"bd2a5c39496b0dda12afc98c321119609780f519","Message":"docs(运维): runbook 补工作台「缺配置」的形态判别与入口形态登录的三道坎\n\n入口托管产物按约定摘掉 .env.local 构建,两个 NEXT_PUBLIC_WORKBENCH_* 一起\n没进产物,登录页显示「缺配置」是这份产物的预期结果、不是漏配;写清判形态\n的办法,并点明不该靠「带着 .env.local 重建」去修(那是拿同源形态换登录页)。\n\n入口形态的登录补配置也修不通:构建带变量、补登记入口 origin 回调都可做,\n但换令牌必失败——常驻容器 NODE_ENV=production 而 loadLocalSigningKey 只认\ntest / development,且容器 IDP_CANONICAL_ORIGIN=http://localhost:3098 使入口\n上取到的 discovery issuer 与端点全指 :3098。结论落在等目标环境的真签名源,\n并明写把容器降成 development 是安全面倒退。\n\n同段末句「在那之前不要把工作台挂到网关根路径」已被 426a7df 落地的同源托管与\nforward_auth 超越,改为陈述现状,免得与新段自相矛盾。\n\ncheck:doc-claims ✓(报告经 GOV_REPORT_DIR 导出仓外,仓内 reports/ 未改);\n工作区根 check-workspace-consistency.mjs 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:53:37-07:00"}],"HeadCommit":{"Sha1":"623a58d184232de4493761b6612202abae6561c0","Message":"chore(reports): evidence-freshness 回绑 @ 3be0bb7 —— 41 份新鲜 / 4 份过期 / 0 error\n\n余 4 条告警都要真实底座或镜像:sbom、runtime-acceptance、ui-acceptance、deployed-runtime。\nmainline-acceptance 随 A15 的六套件重跑已转新鲜。\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:06:02-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/928345d27ed7ade91e7257238a55e64e9f9c6fad...623a58d184232de4493761b6612202abae6561c0","Len":13}...
|
1789801729
|
Edit
Delete
|
|
31238
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"7021758cf {"Commits":[{"Sha1":"7021758cffa830beecc7c0af480bc1943a3e78e8","Message":"fix(governance): 治理测试两条跑法合上——不设 GOV_REPORT_DIR 不再污染 reports/,设了也不再判红\n\n2026-09-19 实测的坑:根 `pnpm check` 第 15 环 `pnpm test` 两条路都不干净。\n- 不设 `GOV_REPORT_DIR`:449 例全过,但 `check-caddy.test.mjs` 就地重写\n `reports/caddy.latest.json`(它是 `report-clobber.test.mjs` 里唯一的具名豁免),\n 跑完整条链必然留一份脏绑报告,要靠操作者记得 `git checkout --` 它。\n- 设了 `GOV_REPORT_DIR`:12 个用例判红。它们把门禁 CLI 跑在**临时沙箱**里\n (catalog-drift 的临时检出、evidence 的临时 git 仓、fixtures 的 `--root`),\n 子进程继承了外部这个变量,报告落到沙箱外,用例按沙箱路径回读就读不到。\n\n两头都是同一件事没做:spawn 门禁时没把报告目录钉死。逐个钉:\n\n| 文件 | 钉到哪 |\n|---|---|\n| check-caddy | 临时 `gov-report-*`(解除具名豁免,与另四支 check-* 同款) |\n| check-catalog-drift | `\u003c临时检出\u003e/reports` |\n| check-evidence-freshness | `\u003c临时 git 仓\u003e/reports` |\n| fixture-integrity / platform-fixtures / cli | `\u003c沙箱 --root\u003e/reports` |\n| port-conformance | 进程内调门禁,`process.env` 上钉一次再还原 |\n\n`deployed-runtime.test.mjs` 反着来:它断言的就是「默认不落盘」,故显式 `delete`\n掉外部的 `GOV_REPORT_DIR`——否则报告被重定向走,仓里那份自然不动,断言成空转。\n它继续留在 `CLOBBER_EXEMPT`(现在是唯一一条,理由与解除条件已按这个新事实改写)。\n\n`report-clobber.test.mjs` 同时补两处扫描漏洞:原来只认字面量 `governance/check-*.mjs`\n(漏掉按相对路径与 `bin/cli.mjs` spawn 的 5 个文件),且只要提一嘴变量名就放行\n(`delete` 做的是相反的事)。现在按 `check-*.mjs|cli.mjs` 认,且要求写成赋值形式。\n扫不到的一类(进程内直接调门禁函数)在注释里写明。\n\n出口判据实测:\n- `GOV_REPORT_DIR=\u003ctmp\u003e node --test governance/test/*.test.mjs` → 471 例 470 过 0 失败;\n- 不设变量跑同一套 → 同样 0 失败,且跑前跑后 `reports/*.json` 的 md5 逐份不变、\n `git status --porcelain` 无新增(树上其余脏文件属并行会话)。\n\n无 `chore(reports)` 回绑:本次改动全在 `governance/test/` 下,46 条证据作用域没有一条覆盖它,\n`check:evidence` 的判词不因本提交改变。\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:26:15-07:00"}],"HeadCommit":{"Sha1":"7021758cffa830beecc7c0af480bc1943a3e78e8","Message":"fix(governance): 治理测试两条跑法合上——不设 GOV_REPORT_DIR 不再污染 reports/,设了也不再判红\n\n2026-09-19 实测的坑:根 `pnpm check` 第 15 环 `pnpm test` 两条路都不干净。\n- 不设 `GOV_REPORT_DIR`:449 例全过,但 `check-caddy.test.mjs` 就地重写\n `reports/caddy.latest.json`(它是 `report-clobber.test.mjs` 里唯一的具名豁免),\n 跑完整条链必然留一份脏绑报告,要靠操作者记得 `git checkout --` 它。\n- 设了 `GOV_REPORT_DIR`:12 个用例判红。它们把门禁 CLI 跑在**临时沙箱**里\n (catalog-drift 的临时检出、evidence 的临时 git 仓、fixtures 的 `--root`),\n 子进程继承了外部这个变量,报告落到沙箱外,用例按沙箱路径回读就读不到。\n\n两头都是同一件事没做:spawn 门禁时没把报告目录钉死。逐个钉:\n\n| 文件 | 钉到哪 |\n|---|---|\n| check-caddy | 临时 `gov-report-*`(解除具名豁免,与另四支 check-* 同款) |\n| check-catalog-drift | `\u003c临时检出\u003e/reports` |\n| check-evidence-freshness | `\u003c临时 git 仓\u003e/reports` |\n| fixture-integrity / platform-fixtures / cli | `\u003c沙箱 --root\u003e/reports` |\n| port-conformance | 进程内调门禁,`process.env` 上钉一次再还原 |\n\n`deployed-runtime.test.mjs` 反着来:它断言的就是「默认不落盘」,故显式 `delete`\n掉外部的 `GOV_REPORT_DIR`——否则报告被重定向走,仓里那份自然不动,断言成空转。\n它继续留在 `CLOBBER_EXEMPT`(现在是唯一一条,理由与解除条件已按这个新事实改写)。\n\n`report-clobber.test.mjs` 同时补两处扫描漏洞:原来只认字面量 `governance/check-*.mjs`\n(漏掉按相对路径与 `bin/cli.mjs` spawn 的 5 个文件),且只要提一嘴变量名就放行\n(`delete` 做的是相反的事)。现在按 `check-*.mjs|cli.mjs` 认,且要求写成赋值形式。\n扫不到的一类(进程内直接调门禁函数)在注释里写明。\n\n出口判据实测:\n- `GOV_REPORT_DIR=\u003ctmp\u003e node --test governance/test/*.test.mjs` → 471 例 470 过 0 失败;\n- 不设变量跑同一套 → 同样 0 失败,且跑前跑后 `reports/*.json` 的 md5 逐份不变、\n `git status --porcelain` 无新增(树上其余脏文件属并行会话)。\n\n无 `chore(reports)` 回绑:本次改动全在 `governance/test/` 下,46 条证据作用域没有一条覆盖它,\n`check:evidence` 的判词不因本提交改变。\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:26:15-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/623a58d184232de4493761b6612202abae6561c0...7021758cffa830beecc7c0af480bc1943a3e78e8","Len":1}...
|
1789802791
|
Edit
Delete
|
|
31243
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"8f5832b62 {"Commits":[{"Sha1":"8f5832b626a294a43810b2f6939e59e93a341283","Message":"chore(reports): deployed-runtime 回绑 @ 18e4661 —— 常驻容器跑的是 84ad650 的镜像\n\ncheck:deployed passed(IMAGE_SOURCE_EQUIVALENT:镜像源 84ad650 之后只有报告回绑提交,\n运行时输入未变);容器 a1fa232df8d1 healthy,环境键齐备。本份在开工前(3335f46)就已过期,\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-19T01:16:46-07:00"},{"Sha1":"18e4661c17b4e9f020648434a1f68e7b92ca71ff","Message":"chore(reports): 受实现提交影响的门禁回绑 @ a4ba565 —— 仓根三份 + runtime 十五份\n\n84ad650 改了 governance/build-workbench-snapshots.mjs 与 runtime/apps/workbench/src/**,\n落进 doc-claims / stub-surface / module-imports 与 runtime 侧治理报告的作用域,check:evidence\n判 4 处 error。按仓纪律在干净检出里重跑并带回:\n\n- reports:rebind --gates module-imports,doc-claims,stub-surface(三份均绑 a4ba565 / dirty=false,门禁 exit 0)\n- pnpm --dir runtime check:governance(聚合重写 runtime/reports 十五份,同样绑 a4ba565 / dirty=false)\n\ncheck:evidence 由 failed(12 过期 / 4 error)回到 partial(40 新鲜 / 6 过期 / 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-19T01:16:23-07:00"},{"Sha1":"a4ba565e6bd3d8c50f1653dd9c2a8f8c9f197273","Message":"chore(reports): 工作台两份快照回绑 @ ea622e4 —— 服务目录 21 → 19 条,范围外资产改列 excluded\n\n在干净树上重跑 workbench:snapshots(worktreeDirty=false):catalog 快照 schemaVersion 4、\nprojects=19、mapped=7/7、conflicts=0,excluded 两条(digital-employee-os / base-framework)\n各带 Catalog 里的排除理由;ops 快照同步回绑到已提交的镜像证据(84ad65070b94)。\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-19T01:12:50-07:00"},{"Sha1":"ea622e4d7f4c374a328cfe5501acbc353089a539","Message":"chore(reports): 镜像与冒烟回绑 @ 84ad650 —— 工作台投影收窄后重建并切换常驻运行时\n\n实现提交动了 runtime/apps/workbench/src/**(运行时镜像输入),镜像随之落后,按 runbook §9\n从 clean 提交重建:enterprise-platform/runtime:84ad65070b94(contextMode=head,worktreeDirty=false),\n冒烟 6/6(单 profile、Redis 逻辑库 15、:53009),常驻容器已 up -d --no-deps runtime 切换并 healthy,\ncheck:deployed passed(IMAGE_SOURCE_EQUIVALENT)。\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-19T01:12:22-07:00"},{"Sha1":"84ad65070b945071e0361644342d453b9575ec80","Message":"feat(governance): 服务目录只投影平台服务——范围外资产不进 entries、改列 excluded\n\n工作台服务目录此前把 Catalog 的 21 条全量投影出来,含 in_goal_scope=false 的两条排除资产\n(基础框架 base-framework、AI 数字员工 digital-employee-os),等于把用户明确排除的资产\n说成平台自己的服务。改为只投影 in_goal_scope !== false 的 19 条:\n\n- entries 收窄;被挡下的条目按 id / 名称 / 层 / 排除理由 / code_truth 列进新的顶层 excluded,\n 不静默消失。排除裁决的真源仍是 Catalog,本次不动 contracts/catalogs/platform-projects.json,\n classifyConsumption 也保留 excluded-asset 分类,只是那类条目不再投影。\n- counts.excludedFromProjection;schemaVersion 3 → 4(entries 含义从「Catalog 全量」收窄成\n 「平台服务」,按条目数做统计的消费者须回看)。\n- 新冲突规则 MODULE_MAPPED_TO_EXCLUDED_PROJECT:运行时模块若映射到范围外项目,单列冲突,\n 不被投影收窄盖成「模块没有 Catalog 项目」。\n- 工作台计数条首格「项目」改「服务」并加「范围外资产」一格;快照类型补 excluded,注释里的\n 条目数 21 → 19。\n\n治理单测 472 例 / 471 通过 / 0 失败 / 1 跳过(新增「排除资产不得进 entries、必须带理由进\nexcluded」与上述冲突规则两组断言);check:catalog / catalog:drift / check:candidate-contracts /\ncheck:stub-surface / check:doc-claims 均 passed。\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-19T01:10:32-07:00"}],"HeadCommit":{"Sha1":"8f5832b626a294a43810b2f6939e59e93a341283","Message":"chore(reports): deployed-runtime 回绑 @ 18e4661 —— 常驻容器跑的是 84ad650 的镜像\n\ncheck:deployed passed(IMAGE_SOURCE_EQUIVALENT:镜像源 84ad650 之后只有报告回绑提交,\n运行时输入未变);容器 a1fa232df8d1 healthy,环境键齐备。本份在开工前(3335f46)就已过期,\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-19T01:16:46-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/7021758cffa830beecc7c0af480bc1943a3e78e8...8f5832b626a294a43810b2f6939e59e93a341283","Len":8}...
|
1789807906
|
Edit
Delete
|
|
31245
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"bb63a0cca {"Commits":[{"Sha1":"bb63a0cca03aa4f7e67a8e2630c52788de87708c","Message":"feat(workbench): 服务目录加序号列——当前取景下的行号,分组视图连续编\n\n表格最左加一列 #。口径写在表头 title 与读屏可见的 \u003ccaption\u003e 里:它是**取景产物**,\n答的是「当前这一屏的第几行」,筛选 / 排序 / 分组一变就跟着变,**不是条目的固定编号**;\n要稳定指代条目仍用条目名下面的 id。\n\n三处刻意的取舍:\n- 分组视图下**连续编号**,不在每组内从 1 重来——重置会让同一个数字在一页里出现好几次,\n 而「第 7 行」正是拿它来指路的场合。\n- 这一列**不可排序**:它没有可排的取值,给它挂排序等于自我指涉。\n- 偏移用 map 出的派生数组算,不按下标取。仓里开了 noUncheckedIndexedAccess,\n `groupOffsets[groupIndex]` 是 number | undefined,用 `?? 0` 兜会把编号错位悄悄吞掉。\n\n实测:dev :3010 默认视图 1…19;?group=layer 下 P0 组 1—10、P1 组从 11 接着编;\n?layer=P2\u0026sort=-name 筛出 3 条后重编 1—3;入口 :58080 重建产物后同样;375px 窄屏不挤版。\ntypecheck / lint 均 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-19T02:24:55-07:00"}],"HeadCommit":{"Sha1":"bb63a0cca03aa4f7e67a8e2630c52788de87708c","Message":"feat(workbench): 服务目录加序号列——当前取景下的行号,分组视图连续编\n\n表格最左加一列 #。口径写在表头 title 与读屏可见的 \u003ccaption\u003e 里:它是**取景产物**,\n答的是「当前这一屏的第几行」,筛选 / 排序 / 分组一变就跟着变,**不是条目的固定编号**;\n要稳定指代条目仍用条目名下面的 id。\n\n三处刻意的取舍:\n- 分组视图下**连续编号**,不在每组内从 1 重来——重置会让同一个数字在一页里出现好几次,\n 而「第 7 行」正是拿它来指路的场合。\n- 这一列**不可排序**:它没有可排的取值,给它挂排序等于自我指涉。\n- 偏移用 map 出的派生数组算,不按下标取。仓里开了 noUncheckedIndexedAccess,\n `groupOffsets[groupIndex]` 是 number | undefined,用 `?? 0` 兜会把编号错位悄悄吞掉。\n\n实测:dev :3010 默认视图 1…19;?group=layer 下 P0 组 1—10、P1 组从 11 接着编;\n?layer=P2\u0026sort=-name 筛出 3 条后重编 1—3;入口 :58080 重建产物后同样;375px 窄屏不挤版。\ntypecheck / lint 均 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-19T02:24:55-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/8f5832b626a294a43810b2f6939e59e93a341283...bb63a0cca03aa4f7e67a8e2630c52788de87708c","Len":1}...
|
1789810067
|
Edit
Delete
|
|
31247
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"35302bb5d {"Commits":[{"Sha1":"35302bb5d50d227f0b40a50b4f88dec89865b3a2","Message":"chore(reports): runtime 治理报告十六份回绑 —— 序号列提交落进其作用域\n\nbb63a0c(工作台序号列)落在 runtime/reports/runtime-governance.latest.json 的作用域内,\ncheck:evidence 判它 error(绑定 a4ba565 之后作用域内有 1 个文件变更)。跑 pnpm --dir runtime\ncheck:governance 重出(该聚合会一并重写同目录十六份),provenance dirty=false——runtime 级报告\n的脏判定只看 runtime/ 子树,而并行会话此刻的在途文件都在 stack/ 与 governance/ 下。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:40:17-07:00"},{"Sha1":"87a23ad19a567838ae9cdebbfa7f940cf0e59845","Message":"chore(reports): Alertmanager 提交影响的门禁回绑 @ 594cc29 —— 五份;工作台两份快照 @ 92d62b3\n\n经 pnpm reports:rebind 在 HEAD 干净检出里重跑(零依赖门禁,临时检出不装依赖),七份\nprovenance 均 worktreeDirty=false。\n\n- 绑 594cc29(Alertmanager 提交):caddy、otel、doc-claims、stub-surface、module-imports。\n 其中 otel 是本次改动直接触及的(直抓目标 5 → 6、掉线告警覆盖 alertmanager);caddy 因\n 作用域含 stack/compose.yaml 与 otel-attributes.json;doc-claims 因作用域含 docs/runbook.md;\n stub-surface 与 module-imports 这两份在本次改动前就已过期——bb63a0c 改了\n runtime/apps/workbench 的源码却没跟 chore(reports),顺带一并清掉。\n- 绑 92d62b3(并行会话的 deployed-runtime 回绑):工作台目录与运维两份快照。工具按当前\n HEAD 生成,故与上面五份不同 sha;两者都在 HEAD 历史上,各自作用域内无后续变更。\n\n回绑后 check:evidence 的 error 档清零。仍为 warn 的几份需要构建产物或运行环境,不在零依赖\n回绑工具范围:release-manifest、sbom、runtime-acceptance、ui-acceptance。\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:38:51-07:00"},{"Sha1":"c0c135e2113b8035d2eed751cdffbaaf9e36b162","Message":"docs(能力设计): 九域模块化落地设计 + 运行时模块进出机制设计(依赖 DEC-041 / CHG-022 签署)\n\n治理仓 87c3722 落了 DEC-041(零运行面契约域收编为平台运行时模块)与 CHG-022 受控变更包;\n本批是它们在真源仓的配套设计。签署前 决策批次-2026-09-16 C-3 的承接表仍是生效裁决,\n两份文件的任何一格都不得开工。\n\n九域模块化落地设计:\n- 六个模块的登记形状定到可直接抄进 runtime/modules.json 的程度:id = profile、package、\n prismaAccessor 与库名一律「模块 id 去连字符」(沿用 ai-gateway → aigateway / platform_aigateway\n 的既有惯例,与同日 CHG-021 三条同规则,不为好看改短名)、provides 一律空数组、\n blocked_by 一律 DEC-041、state 起 shape。\n- provides 空数组是最关键的一条约束:九域不提供任何内核端口,因此不需要动 @juhai/kernel,\n exact pin 不受影响。若将来某域确需新端口,那是基础框架层的独立裁决。\n- state 阶梯写明 authority 卡两道:既缺授权建权威表的已批准 DEC(identity 用 DEC-032、\n C11—C13 用 DEC-040,六域没有对应物,DEC-041 第 4 条明确不代批),又缺消费者(DEC-041\n 第 7 条 2026-09-19 定案不放宽)。这是已决且尚未满足,不是未决。\n- §4 列出落一个模块要动的 13 道门禁及建议顺序,其中两条最容易漏:governance/catalog-map.json\n 必须显式补 模块 id → Catalog id 的映射(不靠同名推断——既有 identity→enterprise-idp 就不同名,\n 漏掉则 build-workbench-snapshots 报 MODULE_WITHOUT_CATALOG_ENTRY、check:catalog 对账同时判红),\n 以及 check:stub-surface 的四个清单数字与 CLAUDE.md 的声明被 S6 绑死、每落一个模块要同步改一次。\n Catalog 那一步必须与 modules.json 同一个提交,否则 catalog:drift(2026-09-17 起 drift 档一律阻断)\n 在中间态判红。\n- §5 说明 C11—C13 不在本设计范围(归 DEC-040 / CHG-021),列出两边共享的三条结论,以及一条\n 只对那三条成立、对六域不成立的代价:它们 module_e2 / E2 要降到 candidate_e0 / E0,而六域本就是 E0。\n\n运行时模块进出机制设计:\n- §0 记录今天的实况:新增有路径(modules.json 登记 + check-modules 校验 + profiles.ts 按\n PLATFORM_PROFILES 动态 import,三处拼起来才看得全),退役完全没有——没有 retirement 字段、\n 没有 directory: null 等价物,删目录 + 删登记行之后 check:modules 反而是绿的,库也留在底座上\n 没有任何登记说它该保留还是删除。这正是 Q01 要求宿主提供「退出保障」的那一条,对控制面\n 自己同样不成立的地方。Catalog 侧早有成熟先例(18 个派生仓退役用 directory: null + retirement),\n 本设计把同一套口径下沉到模块登记。\n- §1 新增九步,第 4 步是「退役路径先写」——进来之前先说清怎么出去;§3 退役三原则与 retirement\n 登记形状(retiredAt / decisionRef / packageRemoved / database.disposition / portsFallback /\n consumerMigration,字段义务逐条写明);§3.3 要改的三处代码:check-modules.mjs 认 retirement\n 并改校验对象、profiles.ts 把退役模块排除出 known 且错误消息要带 retiredAt 与 decisionRef、\n check-stub-surface.mjs 扫描面排除退役模块。prismaAccessor 与 database 的唯一性继续对退役条目\n 生效——退役不是让出名字。\n- §4 用目录负责人举的「流程状态设计管理服务」走一遍,并先划清它与 C15 的边界:设计态出定义、\n 运行态吃定义,两者不共库、经契约相连。结论是机制建成后新增一个服务的技术工作量全在机械步骤\n (第 5—9 步),真正的工作在第 1—4 步的裁决与协议——这正是把闸从「模块数量」换成「准入标准」的意义。\n- §5 列出对工作台的三项影响(「已装载模块 N/M」的分母要改成未退役的登记数、退役模块单列一档\n 而不是从列表消失、服务目录「环境」列口径不变)。\n- §7 记录不做运行期热插拔的四条理由:Nest DynamicModule 的端口束在启动时一次合成、Prisma\n 一模块一库的连接池与在途事务、fail-closed 会多出第三种中间态而消费侧分支只按前两种写、\n 模块进出是季度级动作。\n\n两份均为设计,不含任何登记或代码改动:本次提交不动 runtime/modules.json、contracts/catalogs/、\ngovernance/ 与任何模块目录。工作树里五份 reports/*.latest.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:38:37-07:00"},{"Sha1":"92d62b3f9cefbe46854f87cf4b2fb5ddf63004c5","Message":"chore(reports): deployed-runtime 回绑 @ f0be572 —— 常驻容器跑的是 bb63a0c 的镜像\n\n在 .worktrees/image-bb63a0c 的干净检出(f0be572,0 个变更)里跑 check:deployed --write-report:\npassed,容器 1 个,期望镜像 01edea201c85 @ bb63a0c,IMAGE_SOURCE_EQUIVALENT。\n主工作树此刻仍有并行会话的在途文件,故报告在干净检出里生成后拷回(仓纪律 5 / 偏差 #34-A 同款做法)。\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:38:04-07:00"},{"Sha1":"f0be572e09ebf474b528456d81ed1fa6f4333d5d","Message":"chore(reports): 镜像与冒烟回绑 @ bb63a0c —— 序号列提交后重建并切换常驻运行时\n\nbb63a0c 动的是 runtime/apps/workbench/src/**(运行时镜像输入),check:deployed 随即判\nBUILT_IMAGE_SOURCE_BEHIND。本轮重建并切换:\n\n- 主工作树此刻有并行会话的 7 个在途文件(stack/compose.yaml、三份 otel 配置、两个 overlay、\n otel-attributes.json),直接建会把 worktreeDirty 记成 true 而该项是 error。故在\n .worktrees/image-bb63a0c 的干净检出(HEAD=bb63a0c,0 个变更)里 image:build:\n enterprise-platform/runtime:bb63a0cca03a,contextMode=head,worktreeDirty=false。\n- 冒烟 6/6(单 profile、Redis 逻辑库 15、:53009),报告同样绑 bb63a0c / dirty=false。\n- docker compose … up -d --no-deps runtime 切换,healthy;容器内 PLATFORM_SOURCE_SHA=bb63a0c,\n /api/health 200、/api/platform/catalog 200(19 条、schema 4)。--no-deps 未把并行会话在途的\n alertmanager 服务带起来(那个容器是它自己 09:23 起的,我的命令在 09:36)。\n- check:deployed failed → passed(IMAGE_SOURCE_EQUIVALENT)。\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:37:31-07:00"}],"HeadCommit":{"Sha1":"35302bb5d50d227f0b40a50b4f88dec89865b3a2","Message":"chore(reports): runtime 治理报告十六份回绑 —— 序号列提交落进其作用域\n\nbb63a0c(工作台序号列)落在 runtime/reports/runtime-governance.latest.json 的作用域内,\ncheck:evidence 判它 error(绑定 a4ba565 之后作用域内有 1 个文件变更)。跑 pnpm --dir runtime\ncheck:governance 重出(该聚合会一并重写同目录十六份),provenance dirty=false——runtime 级报告\n的脏判定只看 runtime/ 子树,而并行会话此刻的在途文件都在 stack/ 与 governance/ 下。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T02:40:17-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/bb63a0cca03aa4f7e67a8e2630c52788de87708c...35302bb5d50d227f0b40a50b4f88dec89865b3a2","Len":6}...
|
1789810868
|
Edit
Delete
|
|
31250
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"978aaeeb4 {"Commits":[{"Sha1":"978aaeeb46174baca37960b898e7fd086cec6696","Message":"test(contracts): public-file 的 Catalog 断言改为 authority 口径\n\n6b3baf3 把 code_truth 指回模块目录后,契约包里那支断言仍停在 shape 期(code_truth === null,\n用例名也还写着 in shape state),整链第 17 环 contracts:check:local 判红。改为 authority 口径,\n并把两条规则的完整关系写进注释:catalog:drift 管 shape 侧(不得是代码真源),check:catalog 管\nauthority 侧(必须有代码真源)——这轮红过两次,两次都是只跑了其中一条。\n\ncontracts check:local 416 例全过。\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:17:59-07:00"},{"Sha1":"0799f069c8ef5369d80c9a7f1808fbbffb52e833","Message":"chore(reports): catalog / drift / 两份快照回绑 @ 6b3baf3 —— 这次 catalog 真的是绿的\n\n6b3baf3 修好 code_truth 后重绑:catalog-reconciliation 门禁 exit 0(33ca9d0 那份记的是 exit 1 的失败结论,\n见 6b3baf3 的订正说明)。同批把 catalog-drift 与两份工作台快照绑到同一提交。\n\n顺带一条实测口径:整链 pnpm check 会在工作树里写报告(不走 GOV_REPORT_DIR),于是 reports:rebind 会因为\n\"在工作区未提交\"而跳过那几份——先 git 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-19T04:15:17-07:00"},{"Sha1":"6b3baf3a2e95444b1b5bfa7cda867c0273f3b7c2","Message":"fix(catalog): public-file 的 code_truth 随 state=authority 指回模块目录 —— 并订正 33ca9d0 的一句错话\n\n整链 pnpm check 抓到:check:catalog 判 AUTHORITY_NO_TRUTH——模块 state=authority 但 Catalog\ncode_truth=null。两条规则合起来才是完整口径,我只跑了其中一条:\n- catalog:drift 的「shape 模块不得是 Catalog 代码真源」→ 建骨架那轮把 code_truth 置 null(正确);\n- check:catalog 的「authority 模块必须有代码真源」→ 474fcbb 把 state 翻成 authority 时该同步指回模块目录,\n 而我那轮只跑了 check:migration-decs / check:modules / check:stub-surface / catalog:drift,**没跑 check:catalog**。\n\n**同时订正一句错话**:33ca9d0 的提交说明写「逐份绑 673093a / dirty=false,各自门禁 exit 0」。\n实际上 reports:rebind 的输出里 catalog 那行明写着「门禁 exit 1」——回绑工具照常把报告带回来,\n但那份报告记的是失败结论,而我没看日志就断言全绿。本提交把 Catalog 修好、报告重绑(见随后一条),\n那句话以此为准更正:**33ca9d0 落地时 check:catalog 是红的,不是绿的**。\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:14:16-07:00"},{"Sha1":"c1d6baa66052c8b6a544a66aaf63da09f4f52a38","Message":"feat(governance): check:modules 增投影类模块准入——权威在仓外的模块只做投影\n\nCHG-022 §3.2 用九项准入条件替代「不新增 M8」,但九条里没有一条带上 C01\n自己的两条硬约束:权威是「获批的 Git 内容」、生成的快照与查询视图不可反向\n写入真源(C01 签收单第 9—10 行),以及禁止成为业务请求的同步依赖(接入模型\nL67 对 C01 规定的交付形态;AppManifest 与治理目录规范 L257 把「Registry 可用性\n成为所有业务请求的同步依赖」列为反模式)。两种误实现都不违反现有九条,门禁\n不会拦:把模块库当权威让 Git 退化成镜像,或把模块接进业务请求同步链。\n\n本提交守住可机器判定的那一半,三条规则只对显式登记 authority=\"external\"\n的模块生效——规则不猜哪个模块是投影,猜错会把真权威模块判成只读:\n\n PROJECTION_PROVIDES_PORT 投影模块不得 provides 内核端口(端口即权威接口)\n PROJECTION_CONTRACT_MISSING 声明的 http 契约在 contracts/contracts/ 找不到\n 同名文件即判红。失败关闭:找不到就无法判定只读,\n 不能当通过——这是 check:caddy 前缀覆盖那处空判的教训\n PROJECTION_CONTRACT_WRITES 契约含 GET / HEAD 之外的方法即判红\n\n今天仓里零个模块带该字段,规则处于待命态。它是给 C01 / C17 / C18 这类模块\n落地时用的,先于模块存在而存在,免得那两条约束在实现时被悄悄丢掉。\n\n「不进业务请求同步链」**不**在本规则内:那要看调用方怎么用,不在本仓可见面\n内,按 §3.2 第 10 条登记为人工复核项。不把没守的说成已守。\n\n判定逻辑独立成 governance/lib/projection-modules.mjs:check-modules.mjs 是平铺\n脚本、无 main() 守卫,测试一 import 就会把整道门禁跑起来,测不了。\n\n验证:新用例 8/8;check:modules 在真实仓通过(8 模块 / 投影 0);治理全量\n480 例 479 通过 0 失败 1 跳过(GOV_REPORT_DIR 重定向,reports/ 未动)。\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:14:15-07:00"},{"Sha1":"636269e370e031b356124086d0bfbedba5465636","Message":"chore(reports): port-conformance 回绑 @ fd5ab2c —— 新模块与改写后的客户端都在其扫描面内\n\n本轮新增 public-file 模块(provides 为空)与改写成远程调用的 client-public-file 都落在\nrunime/test/port 的一致性扫描面里,故该报告随之过期。主工作树干净时重跑,passed,绑 fd5ab2c。\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:12:10-07:00"}],"HeadCommit":{"Sha1":"978aaeeb46174baca37960b898e7fd086cec6696","Message":"test(contracts): public-file 的 Catalog 断言改为 authority 口径\n\n6b3baf3 把 code_truth 指回模块目录后,契约包里那支断言仍停在 shape 期(code_truth === null,\n用例名也还写着 in shape state),整链第 17 环 contracts:check:local 判红。改为 authority 口径,\n并把两条规则的完整关系写进注释:catalog:drift 管 shape 侧(不得是代码真源),check:catalog 管\nauthority 侧(必须有代码真源)——这轮红过两次,两次都是只跑了其中一条。\n\ncontracts check:local 416 例全过。\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:17:59-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/35302bb5d50d227f0b40a50b4f88dec89865b3a2...978aaeeb46174baca37960b898e7fd086cec6696","Len":18}...
|
1789823568
|
Edit
Delete
|
|
31253
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"3b55095e3 {"Commits":[{"Sha1":"3b55095e3aac481fdce7fde36f0dcc24309d5ef4","Message":"feat(modules): public-file 宿主数据迁移与对账工具(DEC-040 实施工作包第 2—3 步的可执行面)\n\n**不连任何库**:源库在工单仓(另一个 Owner 的环境),目标库在平台,两边凭据不该压进一个进程。\n工具做的是「生成幂等 SQL + 逐条对账」,导出与执行由操作者各自用 psql 完成——与仓里\nstack/provision/db.sh 同形(打印 SQL,由人决定在哪个库上执行)。用法与两条导出命令写在脚本头部。\n\n映射守住 DEC-040 的两条硬约束,各有单测:\n- **业务外键不迁**:宿主 Attachment.ticket_id(必填外键 + onDelete Cascade)降级为 owner_type='ticket'\n + owner_ref 两列,平台侧不建外键;\n- **retention_until 原样带过去**:级联删除迁走后,它是「宿主忘了调删除接口」时唯一兜底的东西。\n另外宿主出现未登记的状态值时落 PENDING 并在对账里单列 unmappedStatuses——**不猜**。\n\nSQL 幂等且不倒退:ON CONFLICT (tenant_id, file_id) DO UPDATE 只覆盖宿主侧的事实列,\n**不覆盖 scan_attempts / purged_at / purge_***(重跑不该把平台已推进的清理进度倒回宿主快照那一刻);\n按租户切分并先 set_config,FORCE RLS 下不设租户一行也写不进去。\n\n对账:行数 + sha256 逐条 + 状态分布;balanced 只在「不缺行且摘要逐条一致」时为真,不平退出码 1。\n**不看 storage_ref**——迁移不搬字节,对象仍在同一个桶里。\n\n端到端实跑过(合成 1 行,跑完已删,表回到 0 行):生成的 SQL 在 dev 平台库真表上 INSERT 0 1 / COMMIT,\n导出目标侧对账判平(源 1 / 目标 1、sha256 一致),目标为空时判不平且退出 1。\n模块单测 31 例通过 / 1 跳过(+9);check:modules / check:module-imports / check:stub-surface / check:pins 均 passed。\n\n**没做也不该由我做的**:真实数据迁移、宿主改调平台端点、级联删除语义的宿主侧改造——那些落在工单仓,\n归该仓 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-19T06:16:30-07:00"}],"HeadCommit":{"Sha1":"3b55095e3aac481fdce7fde36f0dcc24309d5ef4","Message":"feat(modules): public-file 宿主数据迁移与对账工具(DEC-040 实施工作包第 2—3 步的可执行面)\n\n**不连任何库**:源库在工单仓(另一个 Owner 的环境),目标库在平台,两边凭据不该压进一个进程。\n工具做的是「生成幂等 SQL + 逐条对账」,导出与执行由操作者各自用 psql 完成——与仓里\nstack/provision/db.sh 同形(打印 SQL,由人决定在哪个库上执行)。用法与两条导出命令写在脚本头部。\n\n映射守住 DEC-040 的两条硬约束,各有单测:\n- **业务外键不迁**:宿主 Attachment.ticket_id(必填外键 + onDelete Cascade)降级为 owner_type='ticket'\n + owner_ref 两列,平台侧不建外键;\n- **retention_until 原样带过去**:级联删除迁走后,它是「宿主忘了调删除接口」时唯一兜底的东西。\n另外宿主出现未登记的状态值时落 PENDING 并在对账里单列 unmappedStatuses——**不猜**。\n\nSQL 幂等且不倒退:ON CONFLICT (tenant_id, file_id) DO UPDATE 只覆盖宿主侧的事实列,\n**不覆盖 scan_attempts / purged_at / purge_***(重跑不该把平台已推进的清理进度倒回宿主快照那一刻);\n按租户切分并先 set_config,FORCE RLS 下不设租户一行也写不进去。\n\n对账:行数 + sha256 逐条 + 状态分布;balanced 只在「不缺行且摘要逐条一致」时为真,不平退出码 1。\n**不看 storage_ref**——迁移不搬字节,对象仍在同一个桶里。\n\n端到端实跑过(合成 1 行,跑完已删,表回到 0 行):生成的 SQL 在 dev 平台库真表上 INSERT 0 1 / COMMIT,\n导出目标侧对账判平(源 1 / 目标 1、sha256 一致),目标为空时判不平且退出 1。\n模块单测 31 例通过 / 1 跳过(+9);check:modules / check:module-imports / check:stub-surface / check:pins 均 passed。\n\n**没做也不该由我做的**:真实数据迁移、宿主改调平台端点、级联删除语义的宿主侧改造——那些落在工单仓,\n归该仓 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-19T06:16:30-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/978aaeeb46174baca37960b898e7fd086cec6696...3b55095e3aac481fdce7fde36f0dcc24309d5ef4","Len":1}...
|
1789823887
|
Edit
Delete
|
|
31254
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"9dc4f3236 {"Commits":[{"Sha1":"9dc4f3236199294415bd7cb15547687667940246","Message":"chore(reports): deployed-runtime 回绑 —— 常驻容器跑的是 c0bc8c0 的镜像\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:57:37-07:00"},{"Sha1":"68438d6e12f25645ca806681c661340cf989889d","Message":"chore(reports): C12 升格影响的门禁回绑 @ 3602f99 —— 仓根十五份 + runtime 十六份 + 夹具两份\n\nreports:rebind 在干净检出里跑完 14 个零依赖门禁(含两份工作台快照),pnpm --dir runtime\ncheck:governance 重出 runtime/reports 十六份,需构建产物的 fixtures / fixture-coverage 在主工作树\n(此刻干净)重跑——rebind 明确拒收那两份。全部绑 3602f99 / dirty=false。\n\n工作台快照因此记入 notification-webhook 的新档位:form=runtime-module、模块 state=authority、\nconsumption=runtime-service,Catalog 仍 candidate_e0 / E0(authority≠E2 标注保留)。\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:57:36-07:00"},{"Sha1":"3602f991ed80441050696984fc530f114a8bedfe","Message":"chore(reports): 镜像与冒烟回绑 @ c0bc8c0 —— C12 四个实现提交后重建并切换常驻运行时\n\n在 .worktrees/image-c0bc8c0 的干净检出里 image:build(enterprise-platform/runtime:c0bc8c05d14c,\nworktreeDirty=false),冒烟 6/6,up -d --no-deps runtime 切换后 healthy,check:deployed passed。\n运行面实测:/api/health 200;通知的四个端点已随控制器挂载,无凭证调 effects:classify 得 401(鉴权先拦)。\n**两个新模块的 profile 都未装**——数据未迁,装上只会制造\"已可用\"的假象。\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:56:44-07:00"},{"Sha1":"c0bc8c05d14cd036625d6b44bdb7bb3d53e8f2be","Message":"feat(modules): C12 收尾三步——投递实现迁入、客户端改写、运行时与控制器落地\n\n一口气把 C11 走过的三步在 C12 上做完:\n\n**① 投递实现迁入**(288 行,原文照搬未改语义):签名、验签、重放随机数、主机白名单、可重试判定、\n模板渲染,从 runtime/clients/notification-webhook 迁到 runtime/modules/notification-webhook/src/delivery/。\n\n**② 客户端改写成远程调用**(482 → 113 行):把 notification-delivery-api.v1 的四个操作实现为对平台端点的\n调用。消费者从此不再自己持有签名密钥与出口白名单。未配置 baseUrl / 非 2xx / 返回体不合形状 / 传输异常\n四条路径都是拒绝,各有单测。clients/README 的 B 类段落随之从两项减到一项(只剩配置平台)。\n\n**③ 运行时与控制器**:kit 加 notificationWebhookRuntime 钩子;模块给实现(规则一律调 @juhai/contracts,\n一条都不在模块里重写;租户取自 principal 不从请求体取;无已批准快照时用域自带 deny-all);\n装配点加 NotificationWebhookController,四条路由挂在 /api/v1/notification-deliveries 下。\n\n**一处映射必须写实而不是编**:两个分类器返回的是字符串联合(DELIVER / DUPLICATE / DLQ / REJECT_REPLAY /\nREJECT),不带原因码。我读了规则源码才定映射:effect 的 REJECT = 入参形状不合法(标识为空、次数非正整数、\n三个布尔位不是字面布尔)→ WEBHOOK_EFFECT_ATTEMPT_INVALID;REJECT_REPLAY → WEBHOOK_REPLAY_NOT_AUTHORIZED;\nprovider 的 REJECT → PROVIDER_OUTCOME_INVALID。非拒绝的分类结果走 outcome 原样透传,**不塞进拒绝词表**。\n\n**④ 迁移与对账工具**,形态同 C11(生成 SQL + 对账,不连库)。本域最需要写明的判断是**幂等键从哪来**:\n平台的唯一键是 (tenant_id, idempotency_key),而宿主 Notification 没有这一列(它靠含 escalation_id 的五元组)。\n迁移因此确定性派生:sha256(五元组) 前 32 位 + `host:` 前缀——带前缀是为了让迁来的键与平台自生成的键一眼可分,\n用确定性哈希是因为迁移要可重跑(随机键会让 ON CONFLICT 失效、重跑翻倍)。\n对账**单列幂等键碰撞**:宿主那组唯一键里 escalation_id 可空,两条只差 ticket 的记录会撞出同一个键,\n这类必须在迁移前被人看见,不能靠 ON CONFLICT 悄悄合并成一条。\n\n门禁反向记账两条随控制器落地清掉:registry-only(前缀有控制器应答了)与一条 fixture-only\n(域规则从\"只有夹具在调\"变成有运行时消费者)。CLAUDE.md 清单 12 / 7 / 8 / 8 → **12 / 6 / 7 / 8**。\n模块单测 22 例;治理单测 480 例 479 通过 / 0 失败;contracts 416 例全过;六道门禁 passed;api-nestjs typecheck 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-19T06:54:00-07:00"},{"Sha1":"394ad9b7cd96348b1d2d83e50c9b26ddffa4a842","Message":"feat(modules): C12 两个作业处理器落地——认领+退避调度与过期认领释放\n\n- **claim-expiry 完全自洽**:只读写平台账本。释放 = claim_owner / claim_expires_at 置空、\n next_attempt_at 置为现在。**不改 attempts**——认领过期不是一次投递尝试,把它算成尝试会让一条消息\n 因为工作进程崩溃而提前耗尽重试额度。\n- **delivery-retry 只做账本侧调度**:认领、计次、按退避排下次时间;**不发请求**。外发实现(签名 / 超时 / HTTP)\n 今天仍在 runtime/clients/notification-webhook,照 C11 先例将迁入。这不是占位——调度与外发本就该分开,\n 而认领 + 退避正是\"同一条消息不被两个工作进程同时投\"的保证。\n\n认领做成**乐观抢占**:updateMany + 条件(claim 为空或已过期),并发下只有一个进程 count=1,其余拿 0 并跳过。\n用\"先读后写\"会在两个进程之间留竞态窗口——这条在 store 注释里写明了。\n退避是纯函数(base 指数增长、封顶),base/max 由路由策略给,作业不自己发明节奏。\n\nPrisma store 的每个操作都在事务里先 set_config('app.current_tenant_id', …, true)(FORCE RLS 下不设读不到;\ntrue 限定本事务内,避免连接复用带租户)。描述符同批补 health 真检查项(database up/down)。\n\n单测 5 例:三条失败关闭前提、认领成功才记尝试且退避指数封顶、已被他人认领则跳过且不记尝试、\n过期认领释放且不动 attempts、退避纯函数取值。\ncheck:stub-surface 反向逼着删两条桩登记,CLAUDE.md 桩数 14 → 12;治理单测 480 例 479 通过 / 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-19T06:39:06-07:00"}],"HeadCommit":{"Sha1":"9dc4f3236199294415bd7cb15547687667940246","Message":"chore(reports): deployed-runtime 回绑 —— 常驻容器跑的是 c0bc8c0 的镜像\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:57:37-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/3b55095e3aac481fdce7fde36f0dcc24309d5ef4...9dc4f3236199294415bd7cb15547687667940246","Len":7}...
|
1789826703
|
Edit
Delete
|
|
31257
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"7b4f6df8b {"Commits":[{"Sha1":"7b4f6df8b3e347df680d4649515fa3f4c4e09301","Message":"docs(public-file): reflect approved DEC-040 in store comment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T07:48:22-07:00"}],"HeadCommit":{"Sha1":"7b4f6df8b3e347df680d4649515fa3f4c4e09301","Message":"docs(public-file): reflect approved DEC-040 in store comment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T07:48:22-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/9dc4f3236199294415bd7cb15547687667940246...7b4f6df8b3e347df680d4649515fa3f4c4e09301","Len":1}...
|
1789829315
|
Edit
Delete
|
|
31259
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"baaaf4a4d {"Commits":[{"Sha1":"baaaf4a4dd10af62639fadd54abb8a8fe5c05aec","Message":"docs(deploy): record fixed-source 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:36-07:00"}],"HeadCommit":{"Sha1":"baaaf4a4dd10af62639fadd54abb8a8fe5c05aec","Message":"docs(deploy): record fixed-source 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:36-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/7b4f6df8b3e347df680d4649515fa3f4c4e09301...baaaf4a4dd10af62639fadd54abb8a8fe5c05aec","Len":1}...
|
1789829634
|
Edit
Delete
|
|
31263
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"51712a5e0 {"Commits":[{"Sha1":"51712a5e0007b2d33d2ecd681dd5aece0223254c","Message":"chore(reports): bind module intake gates to 0d1a394\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T08:25:01-07:00"},{"Sha1":"0d1a3946823a1e7771b6f359d98eb4273aba4100","Message":"feat(modules): admit remaining platform domains as fail-closed shapes\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T08:01:24-07:00"}],"HeadCommit":{"Sha1":"51712a5e0007b2d33d2ecd681dd5aece0223254c","Message":"chore(reports): bind module intake gates to 0d1a394\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T08:25:01-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/baaaf4a4dd10af62639fadd54abb8a8fe5c05aec...51712a5e0007b2d33d2ecd681dd5aece0223254c","Len":2}...
|
1789831541
|
Edit
Delete
|
|
31264
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"372c80430 {"Commits":[{"Sha1":"372c80430ac30ac81d6d2bb6735d5c53eaca09df","Message":"chore(reports): rebind gates after module intake deployment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T08:31:41-07:00"},{"Sha1":"f0ee06723d25b45fd4aba58c02b953c859ddd6a9","Message":"chore(reports): bind deployed runtime to module intake image\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T08:30:52-07:00"},{"Sha1":"4aa51b1dda383df0c35acb1432d69a8c633d4bff","Message":"docs(deploy): record module intake dev runtime update\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T08:30:34-07:00"},{"Sha1":"57d2e1a0e96eee62ff42ed12a32db8e50d4d8c4d","Message":"chore(image): record isolated module intake smoke\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T08:28:26-07:00"},{"Sha1":"6573febd08e735260d2f3d95df4541277671c92f","Message":"chore(image): record fixed-source module intake build\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T08:28:02-07:00"}],"HeadCommit":{"Sha1":"372c80430ac30ac81d6d2bb6735d5c53eaca09df","Message":"chore(reports): rebind gates after module intake deployment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T08:31:41-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/51712a5e0007b2d33d2ecd681dd5aece0223254c...372c80430ac30ac81d6d2bb6735d5c53eaca09df","Len":5}...
|
1789831928
|
Edit
Delete
|
|
31265
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"0027742e9 {"Commits":[{"Sha1":"0027742e94d18790b9d56227ffeaf1b2dc1e8d05","Message":"docs: record adversarial acceptance of all runtime modules\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T10:40:54-07:00"}],"HeadCommit":{"Sha1":"0027742e94d18790b9d56227ffeaf1b2dc1e8d05","Message":"docs: record adversarial acceptance of all runtime modules\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T10:40:54-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/372c80430ac30ac81d6d2bb6735d5c53eaca09df...0027742e94d18790b9d56227ffeaf1b2dc1e8d05","Len":1}...
|
1789839666
|
Edit
Delete
|
|
31266
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"5344a74ea {"Commits":[{"Sha1":"5344a74ea5b7c31eaf1729a1ae218fbdf635172b","Message":"feat(runtime): wire database environments for all module profiles\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T15:43:35-07:00"}],"HeadCommit":{"Sha1":"5344a74ea5b7c31eaf1729a1ae218fbdf635172b","Message":"feat(runtime): wire database environments for all module profiles\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T15:43:35-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/0027742e94d18790b9d56227ffeaf1b2dc1e8d05...5344a74ea5b7c31eaf1729a1ae218fbdf635172b","Len":1}...
|
1789857869
|
Edit
Delete
|
|
31267
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"c92a83129 {"Commits":[{"Sha1":"c92a831292abb4dac8ef5d39993630eb920c6cc9","Message":"fix(runtime): package generated Prisma clients for hosted modules\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T15:48:22-07:00"}],"HeadCommit":{"Sha1":"c92a831292abb4dac8ef5d39993630eb920c6cc9","Message":"fix(runtime): package generated Prisma clients for hosted modules\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T15:48:22-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/5344a74ea5b7c31eaf1729a1ae218fbdf635172b...c92a831292abb4dac8ef5d39993630eb920c6cc9","Len":1}...
|
1789858153
|
Edit
Delete
|
|
31268
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"f5853b26f {"Commits":[{"Sha1":"f5853b26f29c616308480cba60d45b0026352875","Message":"docs: record all-module dev loading and verification\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T15:55:32-07:00"},{"Sha1":"84def697d823f39881bf1f5effa76ef32dd532dd","Message":"chore(reports): record 16-profile runtime image smoke\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T15:53:58-07:00"}],"HeadCommit":{"Sha1":"f5853b26f29c616308480cba60d45b0026352875","Message":"docs: record all-module dev loading and verification\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T15:55:32-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/c92a831292abb4dac8ef5d39993630eb920c6cc9...f5853b26f29c616308480cba60d45b0026352875","Len":2}...
|
1789858540
|
Edit
Delete
|
|
31269
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d4a56be01 {"Commits":[{"Sha1":"d4a56be01eb60847220b47ceab6e9d67877f57e9","Message":"Merge remote-tracking branch 'origin/main' into codex/mcp-pilot\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:08:56-07:00"},{"Sha1":"f8ff6cd95d0d1ab5551ccbedad2c53c55bca8d10","Message":"docs(mcp): 记录固定版本真实客户端验收与工具治理边界\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:08:14-07:00"},{"Sha1":"2174dd61783fabf43b2a6f8f4ccd36d83f62ea6e","Message":"feat(mcp): 接入只读工具并逐次核验身份撤权与来源\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:02:00-07:00"}],"HeadCommit":{"Sha1":"d4a56be01eb60847220b47ceab6e9d67877f57e9","Message":"Merge remote-tracking branch 'origin/main' into codex/mcp-pilot\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:08:56-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/f5853b26f29c616308480cba60d45b0026352875...d4a56be01eb60847220b47ceab6e9d67877f57e9","Len":3}...
|
1789859339
|
Edit
Delete
|
|
31270
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"44f8a6c0a {"Commits":[{"Sha1":"44f8a6c0a8cd1c035de339ba21db2897b04d0d95","Message":"docs(workbench): record controlled-ops dev deployment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:20:57-07:00"},{"Sha1":"a3e660c1acddecf014a891693697a953d9e53919","Message":"chore(workbench): rebind management snapshots\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:18:23-07:00"},{"Sha1":"9e0ddaa2063329f43d08f1b8738fc518c2aede7c","Message":"chore(evidence): classify MCP pilot snapshot\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:18:14-07:00"},{"Sha1":"a03ad984b7d613b80fdc7ef5c8af032c0c3624a0","Message":"feat(workbench): guide authorized capability operations\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:14:38-07:00"}],"HeadCommit":{"Sha1":"44f8a6c0a8cd1c035de339ba21db2897b04d0d95","Message":"docs(workbench): record controlled-ops dev deployment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:20:57-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/d4a56be01eb60847220b47ceab6e9d67877f57e9...44f8a6c0a8cd1c035de339ba21db2897b04d0d95","Len":4}...
|
1789860093
|
Edit
Delete
|
|
31272
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"b188dd612 {"Commits":[{"Sha1":"b188dd61233c511fcd355ab3d730ee0660271925","Message":"docs(mcp): 记录真实受控写入与全量后端验收\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:42:52-07:00"},{"Sha1":"0b611b26a1f8461e69d8f37e8b5399480ed9156b","Message":"Merge branch 'main' into codex/mcp-pilot\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:42:52-07:00"},{"Sha1":"3f2ef43ecc7597c49f16394fac1ad2115f31aaaf","Message":"fix(workbench): 分离开发身份入口与同源平台 API\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:41:29-07:00"},{"Sha1":"55735d0f1e8c2e3e006fb0cf2bb9f0cd2804cb14","Message":"fix(workbench): 支持临时目录符号链接下的构建入口\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:40:54-07:00"},{"Sha1":"6c7242958373d397008ef4add4fbef211df03a62","Message":"fix(workbench): 显式校验登录构建配置并保持回调同源\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:40:37-07:00"}],"HeadCommit":{"Sha1":"b188dd61233c511fcd355ab3d730ee0660271925","Message":"docs(mcp): 记录真实受控写入与全量后端验收\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:42:52-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/44f8a6c0a8cd1c035de339ba21db2897b04d0d95...b188dd61233c511fcd355ab3d730ee0660271925","Len":9}...
|
1789861456
|
Edit
Delete
|
|
31273
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"1f742c97c {"Commits":[{"Sha1":"1f742c97cb5f3196fa37a2bad9c23b02a05735bc","Message":"docs(workbench): 记录 OIDC 配置与真实登录部署验收\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:44:31-07:00"}],"HeadCommit":{"Sha1":"1f742c97cb5f3196fa37a2bad9c23b02a05735bc","Message":"docs(workbench): 记录 OIDC 配置与真实登录部署验收\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:44:31-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/b188dd61233c511fcd355ab3d730ee0660271925...1f742c97cb5f3196fa37a2bad9c23b02a05735bc","Len":1}...
|
1789861481
|
Edit
Delete
|
|
31274
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6c888edbd {"Commits":[{"Sha1":"6c888edbd933282b3762415ecf07ed4101505735","Message":"docs(workbench): 记录服务模块文案发布验证\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:47:05-07:00"},{"Sha1":"dde1fcef34d0d83ef3a0c809f466e01a1c7cd47b","Message":"fix(workbench): 将服务目录统一更名为服务模块\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:46:11-07:00"}],"HeadCommit":{"Sha1":"6c888edbd933282b3762415ecf07ed4101505735","Message":"docs(workbench): 记录服务模块文案发布验证\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:47:05-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/1f742c97cb5f3196fa37a2bad9c23b02a05735bc...6c888edbd933282b3762415ecf07ed4101505735","Len":2}...
|
1789861628
|
Edit
Delete
|
|
31275
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"70884dff5 {"Commits":[{"Sha1":"70884dff5dab422ecd6e8d71ab2daa433245e283","Message":"Merge branch 'codex/service-modules-onboarding'\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:47:37-07:00"},{"Sha1":"68cd63d93996134bd20b2677a2527d14038ccce9","Message":"chore(workbench): rebind snapshots after naming integration\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:46:48-07:00"},{"Sha1":"f0a3f2d78fc888be40fac26c66063d0dafcde884","Message":"Merge branch 'main' into codex/service-modules-onboarding\n\n# Conflicts:\n#\truntime/apps/workbench/src/app/catalog/layout.tsx\n#\truntime/apps/workbench/src/app/catalog/page.tsx\n#\truntime/apps/workbench/src/app/page.tsx\n#\truntime/apps/workbench/src/components/app-nav.tsx\n#\truntime/apps/workbench/src/components/catalog/counts-strip.tsx\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:46:43-07:00"},{"Sha1":"427fd7c6bec2f171e54114b68ffec8833585cc27","Message":"chore(workbench): rebind snapshots after mainline integration\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:45:11-07:00"},{"Sha1":"a23f280d98f831ee2644736bf40fe0358b148950","Message":"chore(workbench): rebind module and operations snapshots\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:43:57-07:00"}],"HeadCommit":{"Sha1":"70884dff5dab422ecd6e8d71ab2daa433245e283","Message":"Merge branch 'codex/service-modules-onboarding'\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:47:37-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/6c888edbd933282b3762415ecf07ed4101505735...70884dff5dab422ecd6e8d71ab2daa433245e283","Len":6}...
|
1789861723
|
Edit
Delete
|
|
31276
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"12b734769 {"Commits":[{"Sha1":"12b73476987836f0940dce56f483512df5d47156","Message":"Merge branch 'codex/mcp-pilot'\n\n# Conflicts:\n#\treports/caddy.latest.json\n#\treports/candidate-contracts.latest.json\n#\treports/catalog-drift.latest.json\n#\treports/catalog-reconciliation.latest.json\n#\treports/ci-mirror.latest.json\n#\treports/doc-claims.latest.json\n#\treports/evidence-freshness.latest.json\n#\treports/fact-pii.latest.json\n#\treports/facts.latest.json\n#\treports/fixture-coverage.latest.json\n#\treports/fixtures.latest.json\n#\treports/gate-flow.latest.json\n#\treports/migration-decs.latest.json\n#\treports/module-imports.latest.json\n#\treports/otel.latest.json\n#\treports/stub-surface.latest.json\n#\truntime/reports/agent-adapters.latest.json\n#\truntime/reports/conformance-matrix.latest.json\n#\truntime/reports/contract-consumers.latest.json\n#\truntime/reports/docs-truth.latest.json\n#\truntime/reports/dual-backend-parity.latest.json\n#\truntime/reports/fork-readiness.latest.json\n#\truntime/reports/governance-docs.latest.json\n#\truntime/reports/governance-rules.latest.json\n#\truntime/reports/governance-status.latest.json\n#\truntime/reports/governance.latest.json\n#\truntime/reports/migrations.latest.json\n#\truntime/reports/naming.latest.json\n#\truntime/reports/permission-catalog.latest.json\n#\truntime/reports/platform-ops-definitions.latest.json\n#\truntime/reports/runtime-governance.latest.json\n#\truntime/reports/schema-sync.latest.json\n#\truntime/reports/statemachine-write-guard.latest.json\n#\truntime/reports/validation-source.latest.json\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:51:38-07:00"},{"Sha1":"6d452cdfbb91278dace7fa9257d18f15259070c6","Message":"chore(governance): rebind checks after workbench integration\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:50:53-07:00"},{"Sha1":"ac4dfdb49200000b9a8215d9707668cad8590e0e","Message":"Merge branch 'main' into codex/mcp-pilot\n\n# Conflicts:\n#\treports/workbench-catalog-snapshot.latest.json\n#\treports/workbench-ops-snapshot.latest.json\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:50:51-07:00"},{"Sha1":"2d1d6a58098fb2534afad1306733084e242d9926","Message":"chore(mcp): 同步收尾文档检查与管理快照\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:49:57-07:00"},{"Sha1":"a05ee9316bc5ac83d65a322069252abb1d4df30c","Message":"docs(mcp): 记录发布验收、服务更新与试点清理\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:49:04-07:00"}],"HeadCommit":{"Sha1":"12b73476987836f0940dce56f483512df5d47156","Message":"Merge branch 'codex/mcp-pilot'\n\n# Conflicts:\n#\treports/caddy.latest.json\n#\treports/candidate-contracts.latest.json\n#\treports/catalog-drift.latest.json\n#\treports/catalog-reconciliation.latest.json\n#\treports/ci-mirror.latest.json\n#\treports/doc-claims.latest.json\n#\treports/evidence-freshness.latest.json\n#\treports/fact-pii.latest.json\n#\treports/facts.latest.json\n#\treports/fixture-coverage.latest.json\n#\treports/fixtures.latest.json\n#\treports/gate-flow.latest.json\n#\treports/migration-decs.latest.json\n#\treports/module-imports.latest.json\n#\treports/otel.latest.json\n#\treports/stub-surface.latest.json\n#\truntime/reports/agent-adapters.latest.json\n#\truntime/reports/conformance-matrix.latest.json\n#\truntime/reports/contract-consumers.latest.json\n#\truntime/reports/docs-truth.latest.json\n#\truntime/reports/dual-backend-parity.latest.json\n#\truntime/reports/fork-readiness.latest.json\n#\truntime/reports/governance-docs.latest.json\n#\truntime/reports/governance-rules.latest.json\n#\truntime/reports/governance-status.latest.json\n#\truntime/reports/governance.latest.json\n#\truntime/reports/migrations.latest.json\n#\truntime/reports/naming.latest.json\n#\truntime/reports/permission-catalog.latest.json\n#\truntime/reports/platform-ops-definitions.latest.json\n#\truntime/reports/runtime-governance.latest.json\n#\truntime/reports/schema-sync.latest.json\n#\truntime/reports/statemachine-write-guard.latest.json\n#\truntime/reports/validation-source.latest.json\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:51:38-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/70884dff5dab422ecd6e8d71ab2daa433245e283...12b73476987836f0940dce56f483512df5d47156","Len":5}...
|
1789861902
|
Edit
Delete
|
|
31277
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"9be82463b {"Commits":[{"Sha1":"9be82463b8d0a017f7463a651aa31246bcc0363a","Message":"chore(mcp): 记录主分支合并后的文档与证据检查\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:52:03-07:00"}],"HeadCommit":{"Sha1":"9be82463b8d0a017f7463a651aa31246bcc0363a","Message":"chore(mcp): 记录主分支合并后的文档与证据检查\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:52:03-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/12b73476987836f0940dce56f483512df5d47156...9be82463b8d0a017f7463a651aa31246bcc0363a","Len":1}...
|
1789861925
|
Edit
Delete
|
|
31278
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"42e35e5c3 {"Commits":[{"Sha1":"42e35e5c3f0c1cd6de2c41f2de08af8733c6bc03","Message":"chore(mcp): 刷新合并后的管理快照与文档门禁\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:52:25-07:00"}],"HeadCommit":{"Sha1":"42e35e5c3f0c1cd6de2c41f2de08af8733c6bc03","Message":"chore(mcp): 刷新合并后的管理快照与文档门禁\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:52:25-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/9be82463b8d0a017f7463a651aa31246bcc0363a...42e35e5c3f0c1cd6de2c41f2de08af8733c6bc03","Len":1}...
|
1789861949
|
Edit
Delete
|
|
31279
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"534904a99 {"Commits":[{"Sha1":"534904a99c1afad7c6c7c8fa3e47e586f3d9961d","Message":"chore(mcp): 将管理快照同步到最终证据状态\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:52:49-07:00"},{"Sha1":"609d094ee3c883cab2e586deea259e57c1dfd7b0","Message":"docs(workbench): record module onboarding deployment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:52:46-07:00"}],"HeadCommit":{"Sha1":"534904a99c1afad7c6c7c8fa3e47e586f3d9961d","Message":"chore(mcp): 将管理快照同步到最终证据状态\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T16:52:49-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/42e35e5c3f0c1cd6de2c41f2de08af8733c6bc03...534904a99c1afad7c6c7c8fa3e47e586f3d9961d","Len":2}...
|
1789861972
|
Edit
Delete
|
|
31282
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"c165a1bed {"Commits":[{"Sha1":"c165a1bed0a8453fe3892393f900de5c044fd13a","Message":"chore(reports): bind job readiness checks to mainline\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:13:06-07:00"},{"Sha1":"a64dc8153f588fbca0a3b914db8cd37333f29532","Message":"feat(jobs): reconcile executable handlers with readiness ledger\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:11:41-07:00"}],"HeadCommit":{"Sha1":"c165a1bed0a8453fe3892393f900de5c044fd13a","Message":"chore(reports): bind job readiness checks to mainline\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:13:06-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/534904a99c1afad7c6c7c8fa3e47e586f3d9961d...c165a1bed0a8453fe3892393f900de5c044fd13a","Len":2}...
|
1789863218
|
Edit
Delete
|
|
31283
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"b5e20b632 {"Commits":[{"Sha1":"b5e20b632a5e072db13a1f859fcc372643481938","Message":"chore(reports): rebind job rollout checks after deploy\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:20:26-07:00"},{"Sha1":"f3f7b5d0a4c1563435e7f624a8c4d0500187d13f","Message":"docs(deploy): record job runtime dev rollout\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:19:21-07:00"},{"Sha1":"d38aa37f9afdcd2f51f77f5f4881d0dd91ea3b2e","Message":"chore(reports): record fixed runtime image smoke\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:17:04-07:00"},{"Sha1":"c656484767ea4951df8d8af92dd7e5c6bd450d75","Message":"feat(identity): expose opt-in cleanup schedule in dev compose\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:17:04-07:00"}],"HeadCommit":{"Sha1":"b5e20b632a5e072db13a1f859fcc372643481938","Message":"chore(reports): rebind job rollout checks after deploy\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:20:26-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/c165a1bed0a8453fe3892393f900de5c044fd13a...b5e20b632a5e072db13a1f859fcc372643481938","Len":4}...
|
1789863639
|
Edit
Delete
|
|
31284
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"793dd5151 {"Commits":[{"Sha1":"793dd5151bba6af78a871397ff4942dbe9da1622","Message":"Merge branch 'main' into codex/governance-findings-fix\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:53:49-07:00"},{"Sha1":"6d95f6140ae040316fa102ea01539dfdaa17b6c3","Message":"fix(governance): keep integration output in the bound report\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:53:27-07:00"},{"Sha1":"04826671bcd84452bf0c562d5c2af6abace61225","Message":"fix(runtime): 装配点的作业注册用例跟上「jobs 逐项须有处理器」——a64dc81 之后 check:runtime 的 test 步是红的\n\na64dc81 在 module-kit 的 defineModule 里加了对账:jobs 里每一项都必须有 jobHandler(待建作业只记在\ngovernance/job-readiness.json 的 deferred,不进 jobs)。kit 自己的单测跟着改了,装配点这一份没改:\napps/api-nestjs/test/platform.ports.compose.test.ts 的 registerModuleJobHandlers(S-2)两条用例,夹具还停在\n「jobs 可以列没有处理器的作业」的旧语义上,defineModule 当场抛错(「登记 2,处理器 1」「登记 1,处理器 0」)。\n\n根 pnpm check 不跑 api-nestjs 单测(runtime check = 静态门禁 + lint + typecheck),所以 a64dc81 过了整链、\n镜像也从 c165a1b 构建并切到了 dev。是在 clean 20f2211 的隔离 worktree 里重跑 check:runtime 才撞出来的:\n迁移 deploy / status、RLS 角色供给、双后端差分都过,test 步 exit 1,turbo 随即停止调度,880 例后中断。\n规则是对的,错的是夹具——改用例,不动规则:\n\n- 用例 1:jobs 由 [\"relay\",\"replay\"] 改为 [\"relay\"];「只注册登记过的作业、没登记的 kind 查不到」原意不变。\n- 用例 3:它要测的是 registerModuleJobHandlers 自己的守卫,须绕过 defineModule 造坏模块——底座先给一个合法\n 处理器让 defineModule 通过,再把 jobHandlers 换成 kind 不在 jobs 里的那个。\n- 增一条:jobs 列了却没有处理器 → defineModule 拒绝。新语义在装配点这一侧此前没有用例钉着。\n\n该文件单跑 11/11。完整 check:runtime 在本提交之后重跑,结果另行回绑。\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:53:04-07:00"},{"Sha1":"799ea50116e0b14382641c4039bcd9693420209b","Message":"test(governance): load policy runtimes through the profile registry\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:52:30-07:00"},{"Sha1":"c482794d1d62c793a8c8fd26710902dba41db323","Message":"fix(governance): enforce policy authority and fence concurrent ledger writes\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:51:09-07:00"}],"HeadCommit":{"Sha1":"793dd5151bba6af78a871397ff4942dbe9da1622","Message":"Merge branch 'main' into codex/governance-findings-fix\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T17:53:49-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/b5e20b632a5e072db13a1f859fcc372643481938...793dd5151bba6af78a871397ff4942dbe9da1622","Len":7}...
|
1789865655
|
Edit
Delete
|
|
31285
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d8fdc33de {"Commits":[{"Sha1":"d8fdc33de848f6440cc1bb96ab07a37688bd51d5","Message":"chore(reports): refresh final deployment and workbench evidence\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:08:34-07:00"},{"Sha1":"d6f2062a3b865b481f2e5b7948e7a18ac720a24c","Message":"chore(reports): record fixed-source governance checks and runtime rollout\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:07:53-07:00"},{"Sha1":"29df350f389a23883a92204ea044ecfc23d8cffd","Message":"docs(deploy): record policy governance fixes and verified dev rollout\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:07:03-07:00"},{"Sha1":"c0422ba783cd57fe067e93022e6a137beb3178ae","Message":"chore(reports): check:runtime 回绑 @ 0482667 —— 1109 tests / 0 failures,tenantRlsEnforced=1\n\n在 clean 0482667 的隔离 worktree(.worktrees/runtime-acceptance)里按 CI 配方重跑:一次性 PG16(tmpfs)+ Redis7,\ndb.sh test 供给 16 个模块库与非超级用户角色,prepare-mainline 部署 fact / permission / audit / ai-gateway 迁移与\nowner / consumer 夹具,identity / public-file / notification-webhook 迁移另行 deploy,专用 Broker\nenterprise-platform-ms23-redpanda-1。迁移 deploy / status、RLS 角色供给、双后端差分、真实库测试全过。\n\n同一配方在 20f2211 上的第一轮是红的:a64dc81 之后装配点两条作业注册用例未跟上新规则,test 步 exit 1、\n880 例后中断(修于 0482667)。那一轮的 failed 报告留在隔离 worktree 里,未覆盖主树上一份 b188dd6 的结论。\n\nrevocation-sla 是同一轮 turbo run test 的副产物,一并带回;结论仍是 partial(失效推送仍是测试夹具传输)。\n地板 775 未动。\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:02:59-07:00"},{"Sha1":"15539f1ee6bfe9e6ecc691fa07dff8837202633f","Message":"chore(governance): track database regression evidence freshness\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:02:26-07:00"}],"HeadCommit":{"Sha1":"d8fdc33de848f6440cc1bb96ab07a37688bd51d5","Message":"chore(reports): refresh final deployment and workbench evidence\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:08:34-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/793dd5151bba6af78a871397ff4942dbe9da1622...d8fdc33de848f6440cc1bb96ab07a37688bd51d5","Len":5}...
|
1789866518
|
Edit
Delete
|
|
31287
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"d3cea6b29 {"Commits":[{"Sha1":"d3cea6b297bd4191653188f524e3d2b995d44192","Message":"feat: add durable file and notification execution slices\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:34:50-07:00"}],"HeadCommit":{"Sha1":"d3cea6b297bd4191653188f524e3d2b995d44192","Message":"feat: add durable file and notification execution slices\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:34:50-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/d8fdc33de848f6440cc1bb96ab07a37688bd51d5...d3cea6b297bd4191653188f524e3d2b995d44192","Len":1}...
|
1789868287
|
Edit
Delete
|
|
31296
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"04b93d8d6 {"Commits":[{"Sha1":"04b93d8d6d93f40ceba7715985491a0ef892c489","Message":"chore(reports): bind execution and current acceptance evidence\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:51:44-07:00"},{"Sha1":"dccb72ad7041440e41d1628380db781fb7c04a59","Message":"ci: wire real execution slices and scanner service\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:48:50-07:00"},{"Sha1":"e4782c7b80a04c598c08f6906c6354c325b29545","Message":"docs: record fixed-source execution evidence and dev rollout\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:45:54-07:00"}],"HeadCommit":{"Sha1":"04b93d8d6d93f40ceba7715985491a0ef892c489","Message":"chore(reports): bind execution and current acceptance evidence\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T18:51:44-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/d3cea6b297bd4191653188f524e3d2b995d44192...04b93d8d6d93f40ceba7715985491a0ef892c489","Len":3}...
|
1789869108
|
Edit
Delete
|
|
31321
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"5fc7b0cf2 {"Commits":[{"Sha1":"5fc7b0cf2ea5d5f65da2039e4e875cbd59b612d6","Message":"chore(reports): verify all registered evidence is current\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T19:33:13-07:00"},{"Sha1":"d0758d902d4127513ebbf1c830d357fb66dd651a","Message":"docs: close identity MCP and UI matrix evidence gaps\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T19:32:37-07:00"}],"HeadCommit":{"Sha1":"5fc7b0cf2ea5d5f65da2039e4e875cbd59b612d6","Message":"chore(reports): verify all registered evidence is current\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T19:33:13-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/04b93d8d6d93f40ceba7715985491a0ef892c489...5fc7b0cf2ea5d5f65da2039e4e875cbd59b612d6","Len":2}...
|
1789871711
|
Edit
Delete
|
|
31338
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"8dcb04b66 {"Commits":[{"Sha1":"8dcb04b664321242273d29feb4ad9011e779e007","Message":"chore(reports): 校验并行合并后的治理与证据新鲜度\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T19:41:45-07:00"},{"Sha1":"b9659b30b7116be055e3596e14312f4fee8e5020","Message":"merge: 保留并行验收历史并整合持续门禁接线\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T19:41:26-07:00"},{"Sha1":"feb00b081e4b8144b6bc08e03d613ebd7cab18c9","Message":"chore(reports): 回绑隔离验收证据并清零作用域过期报告\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T19:40:17-07:00"},{"Sha1":"b26edf45e41360d45a8bbbdac4fab47368d771e0","Message":"docs(governance): 回灌最终固定源码 runtime 与矩阵证据\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T19:39:34-07:00"},{"Sha1":"1abd12ad543dc5b5bf735c9459383ff8377d22a3","Message":"docs(governance): 记录自主缺口验收结果与部署边界\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T19:30:28-07:00"}],"HeadCommit":{"Sha1":"8dcb04b664321242273d29feb4ad9011e779e007","Message":"chore(reports): 校验并行合并后的治理与证据新鲜度\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T19:41:45-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/5fc7b0cf2ea5d5f65da2039e4e875cbd59b612d6...8dcb04b664321242273d29feb4ad9011e779e007","Len":7}...
|
1789872115
|
Edit
Delete
|
|
31345
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"ef116fb54 {"Commits":[{"Sha1":"ef116fb5485a9c2357b8c6cbc7747b3ea64dcec8","Message":"chore(reports): 验收覆盖判定影响的三份回绑 @ a6a2ee7\n\ndoc-claims / stub-surface 因 CLAUDE.md 与 runbook 各增一句而过期,经 reports:rebind 在 HEAD 的干净检出里重生成(dirty=false)。\ndeployed-runtime 在 clean a6a2ee7 上重写:passed,报告首次带 acceptance 摘要与 DEPLOYED_IMAGE_ACCEPTED 判定\n(镜像源 d3cea6b 的代码面与验收绑定的提交相同)。\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:28:56-07:00"},{"Sha1":"a6a2ee70c86148e91119d37aa7ea448627e45603","Message":"feat(governance): check:deployed 核「镜像源是否被通过的 check:runtime 覆盖」——没验过的代码不得切到 dev\n\n2026-09-19 晚 a64dc81 过了根 pnpm check、构建并切到 dev,而 check:runtime 的 test 步是红的:根链的\nruntime 一环只有静态门禁 + lint + typecheck,不跑任何包的单测;真实库验收又不是构建与切换的前置。\n当晚四次 dev 切换里,能确认切换前跑过 check:runtime 的只有一次。\n\n这里不把验收塞进根链(要真实 PG / Redis / Broker,本机与 CI 都不是随手可跑),也不重跑验收,\n只在 check:deployed 里核一件事:runtime-acceptance 报告绑定的提交与镜像源提交之间,镜像代码面\n有没有差异。有 → DEPLOYED_IMAGE_NOT_ACCEPTED(error);报告缺失 / 未通过 / 绑脏树 / 无法比较各自\n判红;无差异 → DEPLOYED_IMAGE_ACCEPTED(info)。先后不论:验收可以晚于构建,只要中间没改会进\n镜像的代码。报告增 acceptance 摘要(绑定 SHA / status / testsPassed),读者能核对判定依据。\n\n镜像代码面 = 闭包范围(84a8991)再去掉测试面:*.test.ts、test/ 目录、vitest 配置。依据是闭包内\n每个包都只发 dist(+ generated / prisma / migrations),tsconfig 把测试排除在构建外,api-nestjs 的\nbuild 排除 test/ 且 Dockerfile 再 rm -rf src test——这个前提由 image-code-scope.test.mjs 对真仓逐包\n核对,前提一破那条用例先红。BUILT_IMAGE_SOURCE_BEHIND 与未提交输入判定同样改用代码面:\n只改用例(如 0482667 修 a64dc81 留下的旧夹具)不再要求重建镜像,镜像 c165a1b 的代码与 0482667\n逐字相同,那份 1109 / 0 就覆盖它。\n\nevidence-scopes.json 的 deployed-runtime 条目随之收窄:闭包外 9 个包与测试面排除,runtime-acceptance\n报告成为输入;静态排除项由 evidence-scopes-image.test.mjs 钉在 imageWorkspaceClosure 的推导上,\n闭包一变那条用例先红。runbook 的换镜像命令前加 pnpm check:deployed;CLAUDE.md 读取规则补一句。\n治理测试 +10(533 / 532 通过 / 1 跳过)。\n\n真仓此刻:镜像源 d3cea6b,验收绑 1abd12a(1175 / passed),代码面相同 → passed。\n\nCo-Authored-By: Claude Fable 5.1 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T20:21:19-07:00"}],"HeadCommit":{"Sha1":"ef116fb5485a9c2357b8c6cbc7747b3ea64dcec8","Message":"chore(reports): 验收覆盖判定影响的三份回绑 @ a6a2ee7\n\ndoc-claims / stub-surface 因 CLAUDE.md 与 runbook 各增一句而过期,经 reports:rebind 在 HEAD 的干净检出里重生成(dirty=false)。\ndeployed-runtime 在 clean a6a2ee7 上重写:passed,报告首次带 acceptance 摘要与 DEPLOYED_IMAGE_ACCEPTED 判定\n(镜像源 d3cea6b 的代码面与验收绑定的提交相同)。\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:28:56-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/8dcb04b664321242273d29feb4ad9011e779e007...ef116fb5485a9c2357b8c6cbc7747b3ea64dcec8","Len":2}...
|
1789876511
|
Edit
Delete
|
|
31347
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"77ed48a49 {"Commits":[{"Sha1":"77ed48a49d960912c7954639ce00d4e82606c869","Message":"chore(reports): finalize audit acceptance and isolated image smoke\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T21:51:03-07:00"},{"Sha1":"8873fa3abfff49aab2559c094fcb496f0bb4ed8c","Message":"chore(reports): bind lifecycle audit image and fixed-source acceptance\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T21:48:37-07:00"},{"Sha1":"c5ac88fb23c3bedbd705f429e21bdb12ba97b92a","Message":"docs: bind lifecycle audit verification to fixed source\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T21:09:33-07:00"},{"Sha1":"8c2c481601453c26c55c1d5c585b2e9e2f0e847d","Message":"feat: persist lifecycle audit intents with file and delivery transitions\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T21:00:44-07:00"}],"HeadCommit":{"Sha1":"77ed48a49d960912c7954639ce00d4e82606c869","Message":"chore(reports): finalize audit acceptance and isolated image smoke\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T21:51:03-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/ef116fb5485a9c2357b8c6cbc7747b3ea64dcec8...77ed48a49d960912c7954639ce00d4e82606c869","Len":4}...
|
1789879876
|
Edit
Delete
|
|
31348
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"430bc7629 {"Commits":[{"Sha1":"430bc76299b40cbd23a017092df4278415cf934c","Message":"chore(reports): close audit rollout evidence freshness\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T21:57:21-07:00"},{"Sha1":"e1d749bf5df115a1d952707e34dad2eddbef82d3","Message":"docs: record verified lifecycle audit dev rollout\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T21:56:57-07:00"}],"HeadCommit":{"Sha1":"430bc76299b40cbd23a017092df4278415cf934c","Message":"chore(reports): close audit rollout evidence freshness\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T21:57:21-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/77ed48a49d960912c7954639ce00d4e82606c869...430bc76299b40cbd23a017092df4278415cf934c","Len":2}...
|
1789880245
|
Edit
Delete
|
|
31355
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"6e46582b6 {"Commits":[{"Sha1":"6e46582b6257c45565af62d3dcb1e28b07cc6be1","Message":"chore(reports): record final relay governance checks\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:34:17-07:00"},{"Sha1":"33abeb634a5a81f4f951c06bf10e9654dff92f69","Message":"chore(reports): finalize relay artifact verification\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:33:11-07:00"},{"Sha1":"2d2a70f09484a479f82215e3c2f46f0633aeaf8b","Message":"chore(reports): verify complete audit intent binding on final source\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:31:43-07:00"},{"Sha1":"4169046eb3d564df1d35ec29e04577c78040f05d","Message":"fix: bind audit receipts to the complete persisted intent\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:17:12-07:00"},{"Sha1":"2a232049efccf138c8cd9e2edb914931b55c51c8","Message":"chore(reports): bind relay release inputs and workbench snapshots\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:15:08-07:00"}],"HeadCommit":{"Sha1":"6e46582b6257c45565af62d3dcb1e28b07cc6be1","Message":"chore(reports): record final relay governance checks\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:34:17-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/430bc76299b40cbd23a017092df4278415cf934c...6e46582b6257c45565af62d3dcb1e28b07cc6be1","Len":7}...
|
1789882461
|
Edit
Delete
|
|
31367
|
5
|
5
|
5
|
116
|
0
|
0
|
refs/heads/main
|
0
|
{"Commits":[{"Sha1":"c532802a7 {"Commits":[{"Sha1":"c532802a7e66e404b7fb419d0c306f16d4418189","Message":"docs: record final workbench snapshot verification\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:40:30-07:00"},{"Sha1":"93711823877c51963f8cab3e99546ac851e1aa65","Message":"chore(workbench): publish verified relay acceptance snapshots\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:39:34-07:00"},{"Sha1":"1ae9f3c547fa78fe5c16ebfb14e8900ac48b4fba","Message":"chore(reports): close deployed relay evidence freshness\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:39:34-07:00"},{"Sha1":"c60315ec5d2e64faa4d6479023d4fc35270a6828","Message":"docs: record verified audit relay development deployment\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:39:19-07:00"}],"HeadCommit":{"Sha1":"c532802a7e66e404b7fb419d0c306f16d4418189","Message":"docs: record final workbench snapshot verification\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-19T22:40:30-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/6e46582b6257c45565af62d3dcb1e28b07cc6be1...c532802a7e66e404b7fb419d0c306f16d4418189","Len":4}...
|
1789882846
|
Edit
Delete
|