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":"693800ceaf834b217a01466e19579af6a23925cf","Message":"chore(reports): 治理层门禁报告回绑 @ 87ec431\n\n清树重跑 run-foundation-gates：阻断性 11/11 通过，仅记录 2（工作区一致性\nL9 / L12）。三份报告 worktreeDirty=false，绑定 87ec431。\n\n（订正：本条信息初次写成「回绑 @ 9a5b3c0」，那是提交前预估的 SHA，实际\n实现提交是 87ec431。报告内容的绑定一直是对的，错的只是信息里的那串字。）\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-17T16:40:15-07:00"},{"Sha1":"87ec4315c77935405e16314c11789ddb6ae45e5a","Message":"feat(governance): G6 流外出口必须写复核期，缺失或过期即判红\n\n补上前一提交记为「仍缺一道」的缺口，不留登记而不建。\n\n根因：门禁消费登记的 G4 只断言 wireInWhen 非空，从不校验它是否已成立。\n流外出口是这份登记唯一的豁免口，而豁免口自己没有到期判据——用来防静音的\n机制在自己身上静音了。实锤就是前一提交处理的那条：check-domain-layer 的\n接入条件「D5 与 D9 清零」早已双双成立，G4 全绿，无人发现。\n\nG6 OUT_OF_FLOW_UNREVIEWED：流外条目必须写 conditionReviewBy（YYYY-MM-DD），\n缺失、格式不对或已过期即判红；当天不算过期；只对流外生效，阻断位条目每轮\n都在跑，不需要复核期。6 例负向覆盖这五种形态。\n\n守日期而不守条件是有意的：接入条件多半含人的判断（「框架同步波次扩散后」\n「再有派生仓开仓时」），机器判不了；能机器化的是「必须有人按期回来看一眼」。\n与同日落的域分层基线 B4 同形——缓期不是豁免。\n\n两条现存流外条目各自写了复核期与理由：\n- check-workspace-consistency 2026-10-31：L9 / L12 挂在活裁决 N-11 / C-14\n  上，六周内应有进展。\n- audit-platform-openings 2026-12-31：触发事件罕见，现存派生仓 0 个\n  （派生仓状态.json 只剩 missing 1 + retired 18），不是六周尺度的事。\n\n台账 C-19 由「仍缺一道」改为已补，落点写明。\n\n证据：治理层 378 例 0 失败（新增 6 例负向）、阻断性门禁 11/11、\n工作区一致性仍 2 条（L9 / L12）。报告在脏树上产出，不随本提交。\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-17T16:40:01-07:00"}],"HeadCommit":{"Sha1":"693800ceaf834b217a01466e19579af6a23925cf","Message":"chore(reports): 治理层门禁报告回绑 @ 87ec431\n\n清树重跑 run-foundation-gates：阻断性 11/11 通过，仅记录 2（工作区一致性\nL9 / L12）。三份报告 worktreeDirty=false，绑定 87ec431。\n\n（订正：本条信息初次写成「回绑 @ 9a5b3c0」，那是提交前预估的 SHA，实际\n实现提交是 87ec431。报告内容的绑定一直是对的，错的只是信息里的那串字。）\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-17T16:40:15-07:00"},"CompareURL":"luoanwu/platform-governance/compare/eca16cecb1b0e54e66d69268589ffa59c2fe6eff...693800ceaf834b217a01466e19579af6a23925cf","Len":2}

TEXT

created_unix

INTEGER

Update row 30725 in action