| content |
{"Commits":[{"Sha1":"4652ce0fd {"Commits":[{"Sha1":"4652ce0fd0569840e5cab90e091be88f7173a7f9","Message":"fix(compose): 开发基座补顶层 name，停止与另外六个仓共用 project `api-nestjs`\n\n本文件没有顶层 name，compose 便按**所在目录名**推导 project 名。它在每个仓里的路径都是\napps/api-nestjs/，于是 7 个仓推导出同一个 `api-nestjs`，共用 `api-nestjs_pgdata` /\n`_redisdata` 与同名容器——后 up 的那个直接接管先起者的容器与卷。这类冲突单仓内部永远\n判不出来，只有横着比多份 compose 才看得见，已经咬过一次（C-15）。\n\n现改为 `name: ${COMPOSE_PROJECT_NAME:-device-cloud}`，默认取本仓 package.json 的 name，\n仍可用 COMPOSE_PROJECT_NAME 覆盖。实测 `docker compose config` 解析出的卷已变为\n`device-cloud_*`。\n\n数据风险已先核过再改：本机 260 个卷里**没有任何 `api-nestjs_*`**，\n`docker ps -a --filter label=com.docker.compose.project=api-nestjs` 零命中——\n这份 compose 在本机从未以默认推导名起过，没有旧卷需要迁移。（只证明本机；\n别的机器若直接 up 过，改名后首次 up 会建新空卷，旧卷需自行迁移。）\n\n工作区门禁 `平台治理/基础/scripts/check-workspace-consistency.mjs` 的\nL9 COMPOSE_PROJECT_COLLISION 在 7 个仓全部补齐后由 ISSUES 转 CLEAN（exit 0，0 issues）。\n处置依据：裁决 N-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:13:31-07:00"},{"Sha1":"50f4399dc7bb4ef9be6f97aa60a8e3148667c3e2","Message":"chore(governance): 在 clean HEAD 上重跑静态门禁，证据第一次绑定当前提交\n\n迁移后本仓 19 份 reports/*.latest.json 无一绑定当前 HEAD，全部生成于 2026-08-26 /\n09-10 的旧树，按证据纪律一律按 STALE 对待——也就是说当前 HEAD 的质量一直是未知数。\n\n本次在 clean HEAD (bda8349) 上逐条重跑全部静态门禁：12 通过 / 2 失败，14 份报告\nprovenance 全部 gitSha=bda8349 且 worktreeDirty=false。\n\n两条失败都是跨仓耦合，不是本仓静态问题：\n- check-evidence-current：os-product-runtime 的 upstream 指向基座 checkout 状态\n- check-os-product-compat：产品兼容性需要基座侧路径\n\n不跑需实例的门禁（runtime / UI / 容器 / 灾备），那些要 DATABASE_URL 与浏览器，\n按证据等级\"静态 \u003c 真实 DB \u003c 浏览器\"，本次只提升到静态一级。\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-15T00:34:03-07:00"},{"Sha1":"bda8349f3440331dc74da6a4a41880607201d63d","Message":"chore: refresh governance evidence reports\n\nRegenerate reports/*.latest.json from the latest local gate run\n(contract-consumers, device-boundaries, dual-backend-parity,\nmigrations, naming, os-product-compat, schema-sync,\nstatemachine-write-guard, validation-source, evidence-current).\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-14T19:51:44-07:00"},{"Sha1":"7307924582aa9ace4042b51463833ebd9bc9d17e","Message":"feat: harden device cloud governance\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-08-25T17:19:11-07:00"},{"Sha1":"49e97bd63c64e1d0484db4acffd63d40ab27bbbe","Message":"feat: implement governed device cloud V1\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-08-25T08:46:32-07:00"}],"HeadCommit":{"Sha1":"4652ce0fd0569840e5cab90e091be88f7173a7f9","Message":"fix(compose): 开发基座补顶层 name，停止与另外六个仓共用 project `api-nestjs`\n\n本文件没有顶层 name，compose 便按**所在目录名**推导 project 名。它在每个仓里的路径都是\napps/api-nestjs/，于是 7 个仓推导出同一个 `api-nestjs`，共用 `api-nestjs_pgdata` /\n`_redisdata` 与同名容器——后 up 的那个直接接管先起者的容器与卷。这类冲突单仓内部永远\n判不出来，只有横着比多份 compose 才看得见，已经咬过一次（C-15）。\n\n现改为 `name: ${COMPOSE_PROJECT_NAME:-device-cloud}`，默认取本仓 package.json 的 name，\n仍可用 COMPOSE_PROJECT_NAME 覆盖。实测 `docker compose config` 解析出的卷已变为\n`device-cloud_*`。\n\n数据风险已先核过再改：本机 260 个卷里**没有任何 `api-nestjs_*`**，\n`docker ps -a --filter label=com.docker.compose.project=api-nestjs` 零命中——\n这份 compose 在本机从未以默认推导名起过，没有旧卷需要迁移。（只证明本机；\n别的机器若直接 up 过，改名后首次 up 会建新空卷，旧卷需自行迁移。）\n\n工作区门禁 `平台治理/基础/scripts/check-workspace-consistency.mjs` 的\nL9 COMPOSE_PROJECT_COLLISION 在 7 个仓全部补齐后由 ISSUES 转 CLEAN（exit 0，0 issues）。\n处置依据：裁决 N-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:13:31-07:00"},"CompareURL":"","Len":8}... |