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":"df678ac14f88628a7bc48ce3b53e248f1b257e8b","Message":"chore(reports): check:evidence 回绑 @ e9d0779\n\n37 份已登记（+2：runtime-governance error、conformance-differential warn）、34 份新鲜、\n11 份未登记且全部有处置说明、evidenceUnaccounted=0。3 条 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:14:15-07:00"},{"Sha1":"e9d07790cee2a6780ecc755cb6b6efe70890a727","Message":"feat(governance): 未登记的报告也要逐条记账——把散文口径搬成机器判据，并订正两处误归类\n\ncheck:evidence 的 SCOPE_UNDECLARED 是 info，本身不拦任何东西。于是「未登记作用域」\n这一类可以无声增长，而它恰恰是新鲜度门禁完全看不见的那部分：实测 48 份报告里 13 份\n在此，占 27%。这 13 份为什么不登，此前只写在 evidence-scopes.json 的 note 散文里，\n没有任何机器核对——明天多出一份新报告，它会自动落进这个黑箱，全链门禁一片绿。\n\n按例外机制的同一纪律（G-13：自带出口）把口径搬成逐条登记的 undeclared：\n  UNDECLARED_UNACCOUNTED  报告存在，既无作用域也无账（新洞的唯一入口，判红）\n  UNDECLARED_STALE        账指向的报告已登记作用域，或文件已不存在（判红）\n  UNDECLARED_INCOMPLETE   缺 report/class/reason/recordedAt/resolveBy，或 class 非法\nclass 只允许 self / aggregate / provenance-missing / one-off-snapshot / no-generator。\n记账不是豁免：后两类的出口只有「补生成脚本后转正式登记」或「退役该报告」二选一。\n\n逐份走读生成脚本时发现 note 的 ③「聚合报告」类有两处归错，两份因此一直不受监控：\n  runtime-governance        不聚合任何报告，直接走读 apps/ 源码与两份 prisma schema\n                            判租户接线、outbox 事务、直写发布；纯静态零容器 → error\n  conformance-differential  在 apps/api-nestjs 真跑 vitest，用例同时 import 了\n                            NestJS 与 Fastify 两个后端的装配；要真 DB → warn\n两份均已转入 entries（35 → 37 条），③ 实际只剩 governance 与 governance-status。\n\nclass=self 不查文件存在性：本门禁的报告是判定跑完之后才写的，判定当时它可以合法地\n不存在。这是集成用例抓出来的——起初一视同仁地查，临时仓第一次运行就被自己判红。\n\n门禁测试 277 → 283（新增 6 条负向用例，含「新报告悄悄落进 reports/ 必须判红」的\n集成证明）。pnpm check 全链通过；check:evidence 37 份已登记、34 份新鲜、11 份未登记\n且全部有处置说明、0 份无说明。余 3 份过期是注释提交 c9e0f59 落进验收作用域所致，\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-18T00:13:43-07:00"}],"HeadCommit":{"Sha1":"df678ac14f88628a7bc48ce3b53e248f1b257e8b","Message":"chore(reports): check:evidence 回绑 @ e9d0779\n\n37 份已登记（+2：runtime-governance error、conformance-differential warn）、34 份新鲜、\n11 份未登记且全部有处置说明、evidenceUnaccounted=0。3 条 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:14:15-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/c9e0f59d11a533e7e5e3386f80eff8fb6d6ba6c8...df678ac14f88628a7bc48ce3b53e248f1b257e8b","Len":2}

TEXT

created_unix

INTEGER

Update row 30872 in action