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":"553813dbe9541b78f89eca3151c117473b8444f4","Message":"chore(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-15T03:43:16-07:00"},{"Sha1":"cfe7f98accc01c95ed0c024d4e2d28e8ceb6ecfa","Message":"docs(governance): 企业控制面梳理与两份框架变更请求的增补落盘（另一会话的工作区改动）\n\n本提交内容不是本会话所写，是基础设施侧会话留在工作区的 6 个文档改动，按\"提交推送\"\n一并落盘。内容自洽、交叉引用齐备，且已静置 34 分钟（其 03:07 提交后未再动）：\n\n- 企业控制面/README.md：能力框状态表重构为\"只记已验证的事实与仍缺的，不记计划\"，\n  并加一句关键澄清——\"派生目录里现在剩下的是脚手架\"这句只对目录成立，不等于规则\n  也没了：18 个仓的独有规则已全部迁出真源仓（模块域 6 处、契约包域 9 处）\n- 基础设施文档/docs/企业控制面完整梳理-2026-09-15.md、采纳形态覆盖度对照-2026-09-14.md：\n  横向盘点与 G-* 缺口判据的增补\n- 工程基础框架/框架变更请求-治理报告结论字段-2026-09-15.md、迁移指纹分类-2026-09-14.md\n- 平台治理/基础/派生仓状态.json\n\n`派生仓状态.json` 是门禁读的数据真源，落盘前跑了全套：306 测试 301 通过 0 失败。\n\n本会话未改动其中任何一个字。若对方其实仍在编辑，按本仓惯例以后续提交订正，\n不 rebase 已推送内容。\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-15T03:43:11-07:00"},{"Sha1":"241fc27b274606dee0b3198bb9d855e5a65a17c3","Message":"feat(governance): 本门禁补 11 条自证探针 —— D11 那把尺子先量自己\n\nD11 判别人\"有没有证明过自己会红\"，而本门禁自己一条负向探针都没有。按它自己的\n判据，它属于\"未经验证\"那一档。\n\n夹具测试不能替代探针：测试跑的是构造输入，探针跑的是**本工作区真实数据的形状**。\n两者失效的方式不同——测试挂了没人能提交，探针哑了说明判定对真实数据不成立，\n而那正是 U-31（:503 单方向）/ U-33（:781 前提写死）/ U-36（\"跑不起来\"记成\"0 例\"）\n的共同死法。\n\n11 条探针成对设计，正向要报、反向不得报（只做一半等于没测）：\n  d2 倒挂要报 / 公用应用持有不得报\n  d5 DEC 全批仍 draft 要报 / 有未决 DEC 不得报\n  d9 必填差异要报 / 只差 description 不得报\n  d8 源码改动要让证据失效 / 只动 reports/ 不得失效\n  另有 d9 副本分叉、d11 哑探针、d4 无事实出口四条单向\n\n造不出探针时（本工作区缺相应数据）记 `skipped` 并写明原因，**绝不记\ndetected: false**——那会把\"跑不起来\"伪装成\"门禁没抓到\"，正是 U-36 批评的谎报。\nskipped 条目不带 detected 字段，collectProbes 不收，D11 也就不会把它算成哑探针。\n\n哑探针报 D0 让本门禁自己失败，不只是写进报告——探针哑火意味着判定能力丢失，\n比它报出的任何一条都严重。\n\n实测 11 条全部命中，0 哑 0 跳过；夹具 51/51。\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-15T03:39:59-07:00"}],"HeadCommit":{"Sha1":"553813dbe9541b78f89eca3151c117473b8444f4","Message":"chore(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-15T03:43:16-07:00"},"CompareURL":"luoanwu/platform-governance/compare/a8c2c315c5987714bc084f534c364ca525639562...553813dbe9541b78f89eca3151c117473b8444f4","Len":3}

TEXT

created_unix

INTEGER

Update row 30163 in action