sqlite-web 0.7.2
gitea.db
action
Create
Query
access
access_token
action
action_artifact
action_run
action_run_index
action_run_job
action_runner
action_runner_token
action_schedule
action_schedule_spec
action_task
action_task_output
action_task_step
action_tasks_version
action_variable
app_state
attachment
auth_token
badge
branch
collaboration
comment
commit_status
commit_status_index
commit_status_summary
commit_sync_log
commit_sync_status
dbfs_data
dbfs_meta
deploy_key
email_address
email_hash
external_login_user
follow
gpg_key
gpg_key_import
hook_task
issue
issue_assignees
issue_content_history
issue_dependency
issue_index
issue_label
issue_pin
issue_user
issue_watch
label
language_stat
lfs_lock
lfs_meta_object
login_source
milestone
mirror
notice
notification
oauth2_application
oauth2_authorization_code
oauth2_grant
org_user
package
package_blob
package_blob_upload
package_cleanup_rule
package_file
package_property
package_version
project
project_board
project_issue
protected_branch
protected_tag
public_key
pull_auto_merge
pull_request
push_mirror
reaction
release
renamed_branch
repo_archiver
repo_hidden_file
repo_indexer_status
repo_license
repo_redirect
repo_topic
repo_transfer
repo_unit
repository
review
review_state
secret
session
sqlite_sequence
star
stopwatch
system_setting
task
team
team_invite
team_repo
team_unit
team_user
topic
tracked_time
two_factor
upload
user
user_badge
user_blocking
user_open_id
user_redirect
user_setting
version
watch
webauthn_credential
webhook
Toggle helper tables
Structure
Content
Query
Insert
Drop
Import
Export
Update row 31187 in action
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
refs/heads/main
TEXT
is_private
INTEGER NOT NULL (default 0
content
{"Commits":[{"Sha1":"4f36e22448f8fdf4611af3f5fa34305ae58769ef","Message":"test(contracts): 注册中心 plan 把 BLOCKED 判成了放行——裁决没批、候选自带 blocker,夹具都说通过\n\n前一轮(91216b5)补了入参体检的门禁覆盖。本轮按「公开方法 × 出口」再盘,查出的是\ngovernance/fixture-coverage.mjs 按设计查不到的一类:它只变异夹具已有用例的字段,\n夹具从没构造过的入口不会被发现。三个规则文件零改动,只动夹具评估器的可见性。\n\n1. plan 把 BLOCKED 判成放行。评估器原判据是 `\"reasons\" in r`;ManifestAdmissionResult 三个出口里\n BLOCKED 携带的是 blockers 不是 reasons,于是返回空数组 = ACCEPT。实测两种 BLOCKED 都被夹具判为通过:\n 候选自带 blockedBy([\"CHG-001\"])、所需裁决仍 pending([\"DECISION_PENDING:DEC-011\"])——\n 而它们明写着 activationAllowed: false / registryWriteAllowed: false。\n 同一文件下面的 upgrade 规则本来就写对了(... : [...d.blockers]),plan 与自己的兄弟规则不一致。\n\n2. 没有任何一条 plan 用例带合法快照。整条「有策略」分支(清单字段校验、裁决闸门、READY_FOR_REVIEW)\n 在门禁上根本不存在,唯一那条 N05 是「无策略即拒」。\n\n3. refresh 没有夹具规则:planner 第三个公开方法零门禁覆盖。\n\n修完之后覆盖度一度变差,这是对的。补上带快照的 plan 用例后,此前够不着的清单校验分支第一次被变异探针\n走到,fixture-coverage 随即报出 12 条「夹具与单测都没有」(SERVICES_REQUIRED / PERMISSIONS_REQUIRED /\nPRODUCED_FACTS_REQUIRED / CONSUMED_FACTS_REQUIRED / DEPENDENCIES_REQUIRED / MANIFEST_BLOCKERS_REQUIRED /\nMANIFEST_KIND_INVALID / OWNER_DOMAIN_REQUIRED 与 refresh 侧四条)——它们一直都在,只是之前没人能看见。\n连同 4 条「仅单测」一并钉住后回到 0 / 0。\n\n另修一处本轮自己的松懈:N42 的 reasons 写成了前缀 MANIFEST,任何 MANIFEST* 都能匹配,已改为确切原因码。\n\n一处明写不覆盖:plan() 的 DECISION_MISSING:\u003cid\u003e 按当前控制流不可达——缺一条必需裁决在 normalizePolicy\n装载时就抛 MANIFEST_DECISION_STATUS_INVALID:\u003cid\u003e,运行时工厂退回 deny-all。N39 钉这条真实路径,\nN49 钉装载侧原因码,不为不可达分支造用例。\n\n覆盖:夹具 41 → 70 例(正 7 / 反 63),定向测试 59 → 63 例,前一轮断言一条未改。\n变异探针(70 例 × 14 种脏值)38374 个变异点、0 处抛异常。\n\n未做(越界):C01.04 五个关键应用的固定版本消费(今 2 个 pin)与 C01.06 只读目录查询入口属接线,\n不在本轮;Catalog 登记未动。\n\n证据:pnpm --dir contracts build / typecheck 绿、check:generated 14 files / 12 schemas 无漂移、\nnode --test contracts/test/*.test.mjs 404/404、该套件夹具 70/70 失败 0、fixture-coverage 该套件 0 / 0。\n负向实测:把 N37 的 blocker 声明改成 CHG-999 → 门禁 exit 1 并点名该例,还原后 exit 0。\n本次不回绑任何 reports/。\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-18T16:21:01-07:00"}],"HeadCommit":{"Sha1":"4f36e22448f8fdf4611af3f5fa34305ae58769ef","Message":"test(contracts): 注册中心 plan 把 BLOCKED 判成了放行——裁决没批、候选自带 blocker,夹具都说通过\n\n前一轮(91216b5)补了入参体检的门禁覆盖。本轮按「公开方法 × 出口」再盘,查出的是\ngovernance/fixture-coverage.mjs 按设计查不到的一类:它只变异夹具已有用例的字段,\n夹具从没构造过的入口不会被发现。三个规则文件零改动,只动夹具评估器的可见性。\n\n1. plan 把 BLOCKED 判成放行。评估器原判据是 `\"reasons\" in r`;ManifestAdmissionResult 三个出口里\n BLOCKED 携带的是 blockers 不是 reasons,于是返回空数组 = ACCEPT。实测两种 BLOCKED 都被夹具判为通过:\n 候选自带 blockedBy([\"CHG-001\"])、所需裁决仍 pending([\"DECISION_PENDING:DEC-011\"])——\n 而它们明写着 activationAllowed: false / registryWriteAllowed: false。\n 同一文件下面的 upgrade 规则本来就写对了(... : [...d.blockers]),plan 与自己的兄弟规则不一致。\n\n2. 没有任何一条 plan 用例带合法快照。整条「有策略」分支(清单字段校验、裁决闸门、READY_FOR_REVIEW)\n 在门禁上根本不存在,唯一那条 N05 是「无策略即拒」。\n\n3. refresh 没有夹具规则:planner 第三个公开方法零门禁覆盖。\n\n修完之后覆盖度一度变差,这是对的。补上带快照的 plan 用例后,此前够不着的清单校验分支第一次被变异探针\n走到,fixture-coverage 随即报出 12 条「夹具与单测都没有」(SERVICES_REQUIRED / PERMISSIONS_REQUIRED /\nPRODUCED_FACTS_REQUIRED / CONSUMED_FACTS_REQUIRED / DEPENDENCIES_REQUIRED / MANIFEST_BLOCKERS_REQUIRED /\nMANIFEST_KIND_INVALID / OWNER_DOMAIN_REQUIRED 与 refresh 侧四条)——它们一直都在,只是之前没人能看见。\n连同 4 条「仅单测」一并钉住后回到 0 / 0。\n\n另修一处本轮自己的松懈:N42 的 reasons 写成了前缀 MANIFEST,任何 MANIFEST* 都能匹配,已改为确切原因码。\n\n一处明写不覆盖:plan() 的 DECISION_MISSING:\u003cid\u003e 按当前控制流不可达——缺一条必需裁决在 normalizePolicy\n装载时就抛 MANIFEST_DECISION_STATUS_INVALID:\u003cid\u003e,运行时工厂退回 deny-all。N39 钉这条真实路径,\nN49 钉装载侧原因码,不为不可达分支造用例。\n\n覆盖:夹具 41 → 70 例(正 7 / 反 63),定向测试 59 → 63 例,前一轮断言一条未改。\n变异探针(70 例 × 14 种脏值)38374 个变异点、0 处抛异常。\n\n未做(越界):C01.04 五个关键应用的固定版本消费(今 2 个 pin)与 C01.06 只读目录查询入口属接线,\n不在本轮;Catalog 登记未动。\n\n证据:pnpm --dir contracts build / typecheck 绿、check:generated 14 files / 12 schemas 无漂移、\nnode --test contracts/test/*.test.mjs 404/404、该套件夹具 70/70 失败 0、fixture-coverage 该套件 0 / 0。\n负向实测:把 N37 的 blocker 声明改成 CHG-999 → 门禁 exit 1 并点名该例,还原后 exit 0。\n本次不回绑任何 reports/。\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-18T16:21:01-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/73d03c062f82dc9e8b9a0e66e6e973ca9aca54cd...4f36e22448f8fdf4611af3f5fa34305ae58769ef","Len":1}
TEXT
created_unix
INTEGER
Update
Cancel