| event_payload |
{"ref":"refs/heads/main","befo {"ref":"refs/heads/main","before":"2ef8d2fea20dcc03a7397ed3fc71312b675a70d9","after":"34aab5dea31113ee2688fd236eea3f382402027e","compare_url":"https://gitea.g-hi.com/luoanwu/digital-employee-os/compare/2ef8d2fea20dcc03a7397ed3fc71312b675a70d9...34aab5dea31113ee2688fd236eea3f382402027e","commits":[{"id":"34aab5dea31113ee2688fd236eea3f382402027e","message":"chore(reports): runtime 30/30 + 静态 28/28 回绑 @ 47e6fe3；锚点随批次刷新\n\n三级证据本批首次同时绑定 clean HEAD `47e6fe3`（worktreeDirty:false）：\n\n· runtime 30/30 步、**747 tests / 0 failures**、行为矩阵 **204/204**（地板 204）；\n 七包测试、迁移 deploy/status、auth-startup、db-credential-separation、tracing、\n dependency-resilience、capacity、write-capacity、multi-instance 全通过。\n 747 = 735 + 本批 12 例，与 b71b745 前置写下的预测值一致——预测被实测证实，\n 不是反过来改文档迁就。\n· 静态 28/28。\n· 依赖 pnpm audit --prod --audit-level high = 0 high / 3 moderate（收尾清单硬条目）。\n\nauth-startup 现有**三类拒启各 2/2**：无验签器、显式 demo、**生产缺 APP_ID**。第三类是本日\n新增，`missingAppIdRejected: 2` 是两个后端都真的起不来的机器回执——它抓到的正是本批自己\n第一版的惰性解析缺陷，不是事后补的装饰。\n\n跑了三轮 runtime，如实记账：\n ① 红在 auth-startup —— 真缺陷（惰性 APP_ID），已修（47e6fe3 的父提交）；\n ② 实质全绿但红在收尾 docs-truth 的快照锚点滞后 —— 锚点停在 3949dcc 而 HEAD 已走两步，\n 打穿 C232 的 +1 自指窗。修复提交已把锚点折进去指向其父提交；\n ③ 30/30 全绿，即本提交回绑的这一份。\n第 ② 轮暴露的是我自己的流程错：改变用例数的批次天然要两轮，但锚点该在每个提交里跟着走，\n不该等到最后一个提交才想起来——C241 写的就是这条，这次仍然踩了。\n\n本提交按 C241 把锚点指向父提交 47e6fe3；证据新鲜度里 runtime 与 auth-startup 两行同步回绑。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","url":"https://gitea.g-hi.com/luoanwu/digital-employee-os/commit/34aab5dea31113ee2688fd236eea3f382402027e","author":{"name":"juhailaoluo pro","email":"hillao@juhailaoluodeMacBook-Pro.local","username":""},"committer":{"name":"juhailaoluo pro","email":"hillao@juhailaoluodeMacBook-Pro.local","username":""},"verification":null,"timestamp":"2026-09-18T17:38:01-07:00","added":[],"removed":[],"modified":["CLAUDE.md","reports/agent-adapters.latest.json","reports/auth-startup.latest.json","reports/capacity-envelope.latest.json","reports/contract-consumers.latest.json","reports/db-credential-separation.latest.json","reports/dependency-resilience.latest.json","reports/docs-truth.latest.json","reports/dual-backend-behavior.latest.json","reports/dual-backend-parity.latest.json","reports/fixtures.latest.json","reports/fork-readiness.latest.json","reports/governance-docs.latest.json","reports/governance.latest.json","reports/kernel-admission.latest.json","reports/kernel-boundaries.latest.json","reports/kernel-downstream.latest.json","reports/kernel-extensions.latest.json","reports/kernel-packages.latest.json","reports/list-bounds.latest.json","reports/llm-eval.latest.json","reports/migrations.latest.json","reports/mobile-export.latest.json","reports/multi-instance.latest.json","reports/naming.latest.json","reports/operations.latest.json","reports/platform-dependency-provenance.latest.json","reports/product-acceptance-runtime.latest.json","reports/product-acceptance.latest.json","reports/product-extension-runtime.latest.json","reports/product-migrations-runtime.latest.json","reports/product-migrations.latest.json","reports/product-sql-runtime.latest.json","reports/report-transaction-lock.latest.json","reports/rls.latest.json","reports/runtime-acceptance.latest.json","reports/runtime-governance.latest.json","reports/schema-sync.latest.json","reports/statemachine-write-guard.latest.json","reports/tracing.latest.json","reports/validation-source.latest.json","reports/write-capacity.latest.json"]},{"id":"47e6fe38803a863e867b9f8a6141540da75736ee","message":"fix(kernel-repin): APP_ID 改为装配期强制解析——惰性解析让生产「起得来但每个请求 500」\n\n本批 runtime 第一轮就红在 auth-startup，抓到的是我自己引入的缺陷，不是环境问题：\n\n首版 appId() 是**惰性**的（第一次请求才解析）。于是生产缺 APP_ID 时进程**正常启动**，\n随后 /api/health 与每个业务请求各 500 一次——栈顶就是 request-context 插件。内核对\nresolveAppId 写明的语义是「生产缺失即抛错，起不来好过匿名运行」，惰性版把它退化成\n「运行但全错」，而且把一个配置错误伪装成运行时故障。假绿五形态里的「假健康读模型」\n换了个方向：健康检查自己 500，但进程活着、编排层看不出是配置问题。\n\n改法：\n· appId() 解析失败时包一层稳定归因码 `[APP_ID_REQUIRED]`（与 C51 的 AUTH_VERIFIER_REQUIRED、\n C153 的 secret 读取同款——门禁判定归因码，不去匹配内核的中文消息）；\n· 新增 assertRequestContextStartup()，在**四个入口**启动期强制解析：\n NestJS create-app.ts / Fastify app.ts（紧挨 assertTenantAuthStartup）\n + 两个 dispatcher 的 main()（contextFromJob 同样以 APP_ID 标识来源应用）；\n· check:auth-startup 增加**第三类拒启负例**：生产 + required + 有 verifier、但显式拿掉\n APP_ID → 必须起不来。指标 missingAppIdRejected 入棘轮（floor 2）；\n· 八个启动生产入口的 runner 显式提供 APP_ID——它们本来就该像真实编排那样配齐环境，\n 这不是放宽判据：判据是「缺了要拒启」，由上面那条负例证明，不是靠别的 runner 顺带不配。\n\n绊网加厚：check:dual-backend 的 RequestContext 断言由 7 条扩到 14 条，覆盖四个入口的启动闸、\n两份持有模块的归因码，以及那条负例本身——防惰性解析回潮（它在 typecheck 和行为矩阵下都是绿的）。\n\n第一轮 runtime 的其余结果（报告已随失败轮作废，此处只作判断依据，不作证据引用）：\n21 个步骤 status=0，**testsPassed=747——与上一提交前置的预测值一致**，两个 request-context\n验收文件各 6 例都在里面；唯一红的是 auth-startup。行为矩阵未执行（在 auth-startup 之后）。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","url":"https://gitea.g-hi.com/luoanwu/digital-employee-os/commit/47e6fe38803a863e867b9f8a6141540da75736ee","author":{"name":"juhailaoluo pro","email":"hillao@juhailaoluodeMacBook-Pro.local","username":""},"committer":{"name":"juhailaoluo pro","email":"hillao@juhailaoluodeMacBook-Pro.local","username":""},"verification":null,"timestamp":"2026-09-18T17:14:16-07:00","added":[],"removed":[],"modified":["CLAUDE.md","apps/api-fastify/src/app.ts","apps/api-fastify/src/dispatcher.ts","apps/api-fastify/src/lib/request-context.ts","apps/api-nestjs/src/common/request-context.ts","apps/api-nestjs/src/create-app.ts","apps/api-nestjs/src/dispatcher.ts","docs/planning/内核退回pin立项-2026-09-18.md","reports/baseline.json","scripts/check-auth-startup.mjs","scripts/check-capacity-envelope.mjs","scripts/check-db-credential-separation.mjs","scripts/check-dependency-resilience.mjs","scripts/check-dual-backend-parity.mjs","scripts/check-multi-instance.mjs","scripts/check-redis-auth-live.mjs","scripts/check-tracing.mjs","scripts/check-write-capacity.mjs","scripts/governance-report.mjs"]},{"id":"b71b745a36f3b4786d177604aa7034bf5a43ba39","message":"chore(reports): 静态 28/28 回绑 @ 3949dcc；数字前置到本批实测值\n\n静态 28 份报告在实现提交上重新生成并回绑（`check:kernel-admission` 42 模块 / 751 导出、\n`check:kernel-boundaries` 147/147 受管面 / 245/245 锁定文件、`check:dual-backend` 负探针 2/2）。\n\nCLAUDE.md 动态数字随本批改动前移：\n own-tests 92 → 94 （+2 个 request-context 验收文件，C70 只计 git 已跟踪，\n 故必须在实现提交落地后才数得到）\n own-test-cases 738 → 750 （+12 例，与 governance.latest.json 实测一致）\n tests-passing 735 → 747 （**这一个是预测值**：735 + 本批 12 例，尚未被 runtime 实测）\n\n「tests-passing 写在实测之前」是本仓已知的结构性自指，不是抄数：任何改变用例数的批次\n都会在自己第一次 runtime 的收尾 docs-truth 上红——C231/C244 把该复验放在 canonical 报告\n写下之后，而正确数字只有跑完才知道。两条出路都要跑两轮 runtime（先跑得数再改文档，或\n先写预测再跑），这里选后者，好处是 runtime 报告能直接绑定 clean HEAD。\n**若下一轮实测不等于 747，以报告为准修正本行，不反过来迁就文档。**\n\n快照锚点按 C241 指向实现提交 3949dcc。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","url":"https://gitea.g-hi.com/luoanwu/digital-employee-os/commit/b71b745a36f3b4786d177604aa7034bf5a43ba39","author":{"name":"juhailaoluo pro","email":"hillao@juhailaoluodeMacBook-Pro.local","username":""},"committer":{"name":"juhailaoluo pro","email":"hillao@juhailaoluodeMacBook-Pro.local","username":""},"verification":null,"timestamp":"2026-09-18T16:59:31-07:00","added":[],"removed":[],"modified":["CLAUDE.md","reports/agent-adapters.latest.json","reports/contract-consumers.latest.json","reports/docs-truth.latest.json","reports/dual-backend-parity.latest.json","reports/fixtures.latest.json","reports/fork-readiness.latest.json","reports/governance-docs.latest.json","reports/governance.latest.json","reports/kernel-admission.latest.json","reports/kernel-boundaries.latest.json","reports/kernel-downstream.latest.json","reports/kernel-extensions.latest.json","reports/kernel-packages.latest.json","reports/list-bounds.latest.json","reports/llm-eval.latest.json","reports/migrations.latest.json","reports/mobile-export.latest.json","reports/naming.latest.json","reports/operations.latest.json","reports/platform-dependency-provenance.latest.json","reports/product-acceptance.latest.json","reports/product-migrations.latest.json","reports/report-transaction-lock.latest.json","reports/rls.latest.json","reports/runtime-governance.latest.json","reports/schema-sync.latest.json","reports/statemachine-write-guard.latest.json","reports/ui-acceptance.latest.json","reports/ui-fastify-acceptance.latest.json","reports/ui-nestjs-acceptance.latest.json","reports/validation-source.latest.json"]},{"id":"3949dcccd743f991487c1438db85ddb11277cc4c","message":"feat(kernel-repin): RequestContext 从 HTTP 层贯通——两后端回显 x-request-id / x-trace-id\n\nB2c-2 与 B3″ 的共同前置（立项 §5.2）。形状与解析全部取自 contracts `request-context.ts`\n（转发自 `@juhai/kernel` 0.22.0），本仓只写 AsyncLocalStorage、APP_ID 解析与两个框架各自的\n入口适配——不复制第二份判定。\n\n修的是一个真缺陷，不只是搬代码：本仓此前**不回显任何相关性标识**，调用方拿到 500 之后\n没有任何能交给运维去查日志的句柄。现在固定回显 x-request-id；有合法 traceparent 时另回\nx-trace-id。入站 requestId 合法即沿用（跨服务相关性的唯一意义），非法即丢弃重生成——不把\n外部字符串反射进响应头与日志。\n\n装配（两侧必须最先，鉴权在其后才能 enrich，响应头回显要覆盖其后所有分支）：\n NestJS create-app.ts 第一个 app.use（先于 trace 中间件）\n Fastify app.ts 第一个 register（先于 setErrorHandler 与既有 hook）\n\n与既有 rls-context 并存、刻意不合并：那一份持有 RLS 执行身份（tenant/system 两态），\n这一份持有请求可追溯性。失败语义不同，合成一个 store 会让「租户缺失」与「上下文缺失」\n不可区分。\n\n⚠️ 部署侧同批改动：resolveAppId 在生产缺 APP_ID 时抛错拒绝启动，\ndeploy/production/compose.yml 的 x-api-environment 与 x-dispatcher-environment 两个锚点\n都已写入 APP_ID。漏掉任一个，对应进程起不来——不能等下一批补。\n\n为什么额外建绊网：行为矩阵**结构上证明不了这条**。x-request-id 是实例噪声，被显式排除在\n22 个稳定响应头白名单之外（两端值必然不同），所以删掉任一侧的装配点，矩阵 204 例仍全绿。\n补两层：\n · check:dual-backend 新增 7 条 targeted 断言（含装配顺序、两个 compose 锚点各一）\n + 一个受控断线负探针；dualBackendParityNegativeProbes 由 1 收紧到 2；\n · 两侧各 6 例真实 HTTP 验收 request-context.acceptance.test.ts，断言集逐条对等：\n 无头生成 / 合法沿用 / 非法重生成 / traceparent 取 trace-id / 畸形不猜 / 404 也回显。\n\n负向实测（已恢复现场）：注释掉 Fastify 的 register → 该侧 6/6 精确红；注释掉 NestJS 的\napp.use → 该侧 6/6 精确红。\n\n本批没做、也不声称：outboxContext() 与 decisionContext() 目前**零调用方**——把 context\n写进 outbox 行是 B3″，接进权限判定是 B2c-2（仍卡 ADR 0011 裁决）。本批只交付「上下文在\n请求入口真实存在、可被下游取用、且对外可见」。\n\n边界归属：新增 3 个源码文件按 CORE 归属，kernel.boundaries.lock 重签，受管面 146→147、\n锁定文件 242→245，CLAUDE.md 同步。baseline 只收紧本批真正改变的那个字段\n（dualBackendParityNegativeProbes 1→2）——其余若干地板确实落后于现值（ownTests 83 vs 92、\nrlsProtectedTables 65 vs 67 等），那是另一件事，不在本批顺手扫掉。\n\n证据：typecheck 13/13；pnpm check 28/28；两侧 request-context 验收各 6/6（真实 DB\ndigital_employee_os_acceptance_20260918 @127.0.0.1:55470 + redis :6404/3）。\nruntime 整轮与报告回绑在下一提交。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","url":"https://gitea.g-hi.com/luoanwu/digital-employee-os/commit/3949dcccd743f991487c1438db85ddb11277cc4c","author":{"name":"juhailaoluo pro","email":"hillao@juhailaoluodeMacBook-Pro.local","username":""},"committer":{"name":"juhailaoluo pro","email":"hillao@juhailaoluodeMacBook-Pro.local","username":""},"verification":null,"timestamp":"2026-09-18T16:56:13-07:00","added":["apps/api-fastify/src/lib/request-context.ts","apps/api-fastify/src/plugins/request-context.ts","apps/api-fastify/test/request-context.acceptance.test.ts","apps/api-nestjs/src/common/request-context.ts","apps/api-nestjs/test/request-context.acceptance.test.ts"],"removed":[],"modified":["CLAUDE.md","apps/api-fastify/src/app.ts","apps/api-nestjs/src/create-app.ts","deploy/production/compose.yml","docs/planning/内核退回pin立项-2026-09-18.md","kernel.boundaries.json","kernel.boundaries.lock.json","reports/baseline.json","scripts/check-dual-backend-parity.mjs"]}],"total_commits":0,"head_commit":{"id":"34aab5dea31113ee2688fd236eea3f382402027e","message":"chore(reports): runtime 30/30 + 静态 28/28 回绑 @ 47e6fe3；锚点随批次刷新\n\n三级证据本批首次同时绑定 clean HEAD `47e6fe3`（worktreeDirty:false）：\n\n· runtime 30/30 步、**747 tests / 0 failures**、行为矩阵 **204/204**（地板 204）；\n 七包测试、迁移 deploy/status、auth-startup、db-credential-separation、tracing、\n dependency-resilience、capacity、write-capacity、multi-instance 全通过。\n 747 = 735 + 本批 12 例，与 b71b745 前置写下的预测值一致——预测被实测证实，\n 不是反过来改文档迁就。\n· 静态 28/28。\n· 依赖 pnpm audit --prod --audit-level high = 0 high / 3 moderate（收尾清单硬条目）。\n\nauth-startup 现有**三类拒启各 2/2**：无验签器、显式 demo、**生产缺 APP_ID**。第三类是本日\n新增，`missingAppIdRejected: 2` 是两个后端都真的起不来的机器回执——它抓到的正是本批自己\n第一版的惰性解析缺陷，不是事后补的装饰。\n\n跑了三轮 runtime，如实记账：\n ① 红在 auth-startup —— 真缺陷（惰性 APP_ID），已修（47e6fe3 的父提交）；\n ② 实质全绿但红在收尾 docs-truth 的快照锚点滞后 —— 锚点停在 3949dcc 而 HEAD 已走两步，\n 打穿 C232 的 +1 自指窗。修复提交已把锚点折进去指向其父提交；\n ③ 30/30 全绿，即本提交回绑的这一份。\n第 ② 轮暴露的是我自己的流程错：改变用例数的批次天然要两轮，但锚点该在每个提交里跟着走，\n不该等到最后一个提交才想起来——C241 写的就是这条，这次仍然踩了。\n\n本提交按 C241 把锚点指向父提交 47e6fe3；证据新鲜度里 runtime 与 auth-startup 两行同步回绑。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","url":"https://gitea.g-hi.com/luoanwu/digital-employee-os/commit/34aab5dea31113ee2688fd236eea3f382402027e","author":{"name":"juhailaoluo pro","email":"hillao@juhailaoluodeMacBook-Pro.local","username":""},"committer":{"name":"juhailaoluo pro","email":"hillao@juhailaoluodeMacBook-Pro.local","username":""},"verification":null,"timestamp":"2026-09-18T17:38:01-07:00","added":[],"removed":[],"modified":["CLAUDE.md","reports/agent-adapters.latest.json","reports/auth-startup.latest.json","reports/capacity-envelope.latest.json","reports/contract-consumers.latest.json","reports/db-credential-separation.latest.json","reports/dependency-resilience.latest.json","reports/docs-truth.latest.json","reports/dual-backend-behavior.latest.json","reports/dual-backend-parity.latest.json","reports/fixtures.latest.json","reports/fork-readiness.latest.json","reports/governance-docs.latest.json","reports/governance.latest.json","reports/kernel-admission.latest.json","reports/kernel-boundaries.latest.json","reports/kernel-downstream.latest.json","reports/kernel-extensions.latest.json","reports/kernel-packages.latest.json","reports/list-bounds.latest.json","reports/llm-eval.latest.json","reports/migrations.latest.json","reports/mobile-export.latest.json","reports/multi-instance.latest.json","reports/naming.latest.json","reports/operations.latest.json","reports/platform-dependency-provenance.latest.json","reports/product-acceptance-runtime.latest.json","reports/product-acceptance.latest.json","reports/product-extension-runtime.latest.json","reports/product-migrations-runtime.latest.json","reports/product-migrations.latest.json","reports/product-sql-runtime.latest.json","reports/report-transaction-lock.latest.json","reports/rls.latest.json","reports/runtime-acceptance.latest.json","reports/runtime-governance.latest.json","reports/schema-sync.latest.json","reports/statemachine-write-guard.latest.json","reports/tracing.latest.json","reports/validation-source.latest.json","reports/write-capacity.latest.json"]},"repository":{"id":76,"owner":{"id":5,"login":"luoanwu","login_name":"","source_id":0,"full_name":"","email":"law@g-hi.com","avatar_url":"https://gitea.g-hi.com/avatar/627574a890388a2aadc80ab38d22f3a0","html_url":"https://gitea.g-hi.com/luoanwu","language":"","is_admin":false,"last_login":"0001-01-01T00:00:00Z","created":"2026-01-30T16:28:30+08:00","restricted":false,"active":false,"prohibit_login":false,"location":"","website":"","description":"","visibility":"public","followers_count":0,"following_count":0,"starred_repos_count":0,"username":"luoanwu"},"name":"digital-employee-os","full_name":"luoanwu/digital-employee-os","description":"","empty":false,"private":false,"fork":false,"template":false,"mirror":false,"size":90066,"language":"","languages_url":"https://gitea.g-hi.com/api/v1/repos/luoanwu/digital-employee-os/languages","html_url":"https://gitea.g-hi.com/luoanwu/digital-employee-os","url":"https://gitea.g-hi.com/api/v1/repos/luoanwu/digital-employee-os","link":"","ssh_url":"git@gitea.g-hi.com:luoanwu/digital-employee-os.git","clone_url":"https://gitea.g-hi.com/luoanwu/digital-employee-os.git","original_url":"","website":"","stars_count":0,"forks_count":1,"watchers_count":1,"branch_count":3,"open_issues_count":0,"open_pr_counter":0,"release_counter":0,"default_branch":"main","archived":false,"created_at":"2026-08-20T14:46:28+08:00","updated_at":"2026-09-19T07:35:06+08:00","archived_at":"1970-01-01T08:00:00+08:00","permissions":{"admin":true,"push":true,"pull":true},"has_code":true,"has_issues":true,"internal_tracker":{"enable_time_tracker":true,"allow_only_contributors_to_track_time":true,"enable_issue_dependencies":true},"has_wiki":true,"has_pull_requests":true,"has_projects":true,"projects_mode":"all","has_releases":true,"has_packages":true,"has_actions":true,"ignore_whitespace_conflicts":false,"allow_merge_commits":true,"allow_rebase":true,"allow_rebase_explicit":true,"allow_squash_merge":true,"allow_fast_forward_only_merge":true,"allow_rebase_update":true,"allow_manual_merge":false,"autodetect_manual_merge":false,"default_delete_branch_after_merge":false,"default_merge_style":"merge","default_allow_maintainer_edit":true,"avatar_url":"","internal":false,"mirror_interval":"","object_format_name":"sha1","mirror_updated":"0001-01-01T00:00:00Z","topics":[],"licenses":[]},"pusher":{"id":5,"login":"luoanwu","login_name":"","source_id":0,"full_name":"","email":"5+luoanwu@noreply.localhost","avatar_url":"https://gitea.g-hi.com/avatar/627574a890388a2aadc80ab38d22f3a0","html_url":"https://gitea.g-hi.com/luoanwu","language":"","is_admin":false,"last_login":"0001-01-01T00:00:00Z","created":"2026-01-30T16:28:30+08:00","restricted":false,"active":false,"prohibit_login":false,"location":"","website":"","description":"","visibility":"public","followers_count":0,"following_count":0,"starred_repos_count":0,"username":"luoanwu"},"sender":{"id":5,"login":"luoanwu","login_name":"","source_id":0,"full_name":"","email":"5+luoanwu@noreply.localhost","avatar_url":"https://gitea.g-hi.com/avatar/627574a890388a2aadc80ab38d22f3a0","html_url":"https://gitea.g-hi.com/luoanwu","language":"","is_admin":false,"last_login":"0001-01-01T00:00:00Z","created":"2026-01-30T16:28:30+08:00","restricted":false,"active":false,"prohibit_login":false,"location":"","website":"","description":"","visibility":"public","followers_count":0,"following_count":0,"starred_repos_count":0,"username":"luoanwu"}}... |