SQLite Web: gitea.db

id

Primary key. INTEGER NOT NULL

user_id

INTEGER

op_type

INTEGER

act_user_id

INTEGER

repo_id

INTEGER

comment_id

INTEGER

is_deleted

INTEGER NOT NULL (default 0

ref_name

TEXT

is_private

INTEGER NOT NULL (default 0

content

{"Commits":[{"Sha1":"0abd15c28dd2b92c583289934db660363b202fd4","Message":"chore(reports): check:evidence 回绑 @ 34fresh\n\n37 份已登记、34 份新鲜、0 error；余 3 份过期为需真实容器重跑的验收报告\n（runtime-acceptance / mainline-acceptance / revocation-sla，warn 按设计）。\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-18T00:28:32-07:00"},{"Sha1":"a4b3d356f9d2f7a831198787a5b19194f4f763c8","Message":"chore(reports): 双后端差分验收重跑回绑 @ 746f323\n\n本轮把 conformance-differential 从「未登记的聚合报告」订正为登记条目后，它第一次\n被新鲜度门禁判为过期——触发者正是同轮改到的 check-conformance-differential.mjs，\n说明登记的作用域是对的。真实 DB + Redis 重跑：7 checkpoints × 2 backends，\n逐字段 0 differences。\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-18T00:28:10-07:00"},{"Sha1":"746f323c203531c4ced5f3ca60ea29a4c53c7c4d","Message":"chore(reports): 工作台两份快照回绑 @ adda76a\n\nrunbook §7 的订正落在运维快照作用域内（docs/runbook.md），经 reports:rebind 在\nHEAD 的干净检出里重跑，两份同源快照一并带回。\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-18T00:27:33-07:00"},{"Sha1":"adda76acfd8fa046e1f2a320c15b5384b4ddef73","Message":"fix(runtime): 前置守卫失败不得覆盖验收报告，并补「一模块一库」检查\n\n按 docs/runbook.md §7 的配方逐字重跑 runtime 验收，当场复现两个缺陷。\n\n一、配方本身是错的。§7 只写了 DATABASE_URL 与 REDIS_URL，而七个模块的\nprisma/schema.prisma 各自写死 url = env(\"DATABASE_URL_\u003cMODULE\u003e\")。照它执行时，\n前两步 nestjs/fastify-migrate-deploy 会通过，第三步 migrate-status 才以\nPrisma P1012 \"Environment variable not found\" 失败——报错指向 wasm 校验，\n完全看不出是环境没配齐。§7 已补齐七个变量，并写明 prepare-mainline.mjs\n只供给主线验收要的 5 个（fact/permission/audit/owner/consumer），差的四个要自己建。\n\n二、更要紧的：那次失败把 runtime-acceptance.latest.json 覆盖成了 status:failed。\n775/775 那份真实结论就此丢失，靠 git checkout 才救回——差一点被当作真实回归提交上去。\n根因是三个 runner 都无条件 writeFileSync：前置守卫失败意味着**验收根本没跑**，\n此时写一份 failed 报告不是诚实，是用操作者的环境问题顶替代码的结论，\n并且顺手销毁了上一次真的跑过的证据。三个 runner 统一改为前置失败即退出、不碰报告：\n  check-runtime-acceptance      实测：报告 sha256 前后一致\n  check-ui-acceptance           实测：缺 REDIS_URL 时报告 sha256 前后一致\n  check-conformance-differential 实测：同上\n\n新增 preflightModuleDatabases + requiredModuleDatabaseEnvNames，把缺失的七个\n变量在动任何东西之前一次列清。变量名**现取自各模块 prisma/schema.prisma**，\n不写死清单：模块增减自动跟上，也避免抄错 ai-gateway 那个没有下划线的\nDATABASE_URL_AIGATEWAY。该检查只接进 runtime 验收——UI 与差分验收跑的是\n两个 app，不走一模块一库。\n\npnpm check 全链通过。\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-18T00:26:48-07:00"}],"HeadCommit":{"Sha1":"0abd15c28dd2b92c583289934db660363b202fd4","Message":"chore(reports): check:evidence 回绑 @ 34fresh\n\n37 份已登记、34 份新鲜、0 error；余 3 份过期为需真实容器重跑的验收报告\n（runtime-acceptance / mainline-acceptance / revocation-sla，warn 按设计）。\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-18T00:28:32-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/df678ac14f88628a7bc48ce3b53e248f1b257e8b...0abd15c28dd2b92c583289934db660363b202fd4","Len":4}

TEXT

created_unix

INTEGER

Update row 30882 in action