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
Delete row 31219 from action
id
31219
user_id
5
op_type
5
act_user_id
5
repo_id
116
comment_id
0
is_deleted
0
ref_name
refs/heads/main
is_private
0
content
{"Commits":[{"Sha1":"b90d7a151
{"Commits":[{"Sha1":"b90d7a151e5e9451fa12fb6e883b8898552124df","Message":"chore(reports): C 组三份真实验收回绑 @ 8a621fd —— 在 adversarial 隔离栈上跑，共享底座与 ms23 均未触碰\n\nC 组（runtime-acceptance / mainline-acceptance / revocation-sla）需要真实 PG + Redis + Redpanda。\nms23 那套 35 分钟前刚被并行会话用过（容器 Exited），按 docs/持久主线本地验收.md「同名 project 即使\n容器刚启动也不能直接 up 覆盖，该名称已占用时应协调或选择已有获准且无人使用的测试环境」，改用\nadversarial（PG 55473 / Redis 56382 / Broker 59095，2026-09-12 获准、闲置 3 天、其 Broker 已在故障\n注入白名单）。全程 docker start 既有容器，未 compose up 覆盖任何 project。\n\n结果（均在干净检出 8a621fd 上产出，worktreeDirty=false）：\n runtime-acceptance passed 1001 tests（地板 775）、tenantRlsEnforced=1、双后端差分 0\n mainline-acceptance passed\n revocation-sla partial p95 5027ms / max 5041ms / 20 samples——远低于 MS-3 的 30s；\n partial 来自 employmentScope 链仍 pending-scope-consumer-enforcement，\n 以及生产投送/负载/staging 四项 unverified，是既定状态不是失败\n conformance-differential 作为 runtime 验收的副产物一并刷新（同样已登记 severity=warn）\n\n过程中一处失败是我搭环境搭错的，记下来免得下次再犯：首轮 e2e/identity-profile 断言\n`elevated=false` 实测 true——mainline:prepare 只为 fact/permission/audit/owner/consumer 建非超级用户\n角色，identity/credential/scope/aigateway 四个库是我用管理员 platform 手建的，identity 的连接因此是\n特权角色。REASSIGN OWNED 不适用（platform 持有系统对象），改为重建该库并 OWNER 给\nplatform_identity_test_app、以该角色重新 deploy 迁移后转绿。credential / scope 没有\nprisma:migrate:deploy 脚本是对的——它们是 state=shape 模块，按仓纪律不得有迁移。\n\n隔离与收尾：凭据只经仓外 0600 文件（/tmp/c3-mainline.env、/tmp/c3-env.sh），不入仓、不打印；\n验收在独立 worktree 里 pnpm install 自己的 node_modules，不软链主检出，避免与并行会话抢 .prisma；\nadversarial 三容器跑完恢复为 Exited（与我接手前一致）。主检出里并行会话另有十余份报告 WIP，一份没碰。\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-18T17:45:56-07:00"},{"Sha1":"a178ba36c65d82fab8106fa7395dd65f927876ad","Message":"docs(治理): 云端治理段补 2026-09-19 实测——分支保护已整个消失，而计费仍未恢复\n\n推送本会话提交时实测到两条与在案记录对不上的事实：\n\n① main 的分支保护整个没了，不是摘掉那条必需检查而已：\n gh api .../branches/main/protection → 404 \"Branch not protected\"。\n 镜像因此重新推得动，直推 54e6324..12093b8 成功并已核对 github/main 与本地一致；\n 「镜像停在 3308542」这句作废。谁摘的、何时、为什么未知，gh 查不到保护变更历史。\n 本会话未恢复保护、未改动任何 GitHub 设置——不知原委时自行配回去，风险大于留着不动。\n\n② 计费没解决，原记录前半截仍成立：该次直推触发的 run 35410044850 三 job failure、\n 五 skipped，注解逐字仍是 recent account payments have failed。\n\n故「镜像推得动」≠「远端验过了」：这批提交在 GitHub 上一次门禁都没跑过，远端只是有了代码。\n\n第三条是写给下一个人的：本条与同段「不要靠摘必需检查绕过」的口径现在对不上现实，须由\n仓库管理权限持有者二选一收口——恢复保护，或把「为什么现在不设保护」写成显式裁决并给\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-18T17:45:16-07:00"}],"HeadCommit":{"Sha1":"b90d7a151e5e9451fa12fb6e883b8898552124df","Message":"chore(reports): C 组三份真实验收回绑 @ 8a621fd —— 在 adversarial 隔离栈上跑，共享底座与 ms23 均未触碰\n\nC 组（runtime-acceptance / mainline-acceptance / revocation-sla）需要真实 PG + Redis + Redpanda。\nms23 那套 35 分钟前刚被并行会话用过（容器 Exited），按 docs/持久主线本地验收.md「同名 project 即使\n容器刚启动也不能直接 up 覆盖，该名称已占用时应协调或选择已有获准且无人使用的测试环境」，改用\nadversarial（PG 55473 / Redis 56382 / Broker 59095，2026-09-12 获准、闲置 3 天、其 Broker 已在故障\n注入白名单）。全程 docker start 既有容器，未 compose up 覆盖任何 project。\n\n结果（均在干净检出 8a621fd 上产出，worktreeDirty=false）：\n runtime-acceptance passed 1001 tests（地板 775）、tenantRlsEnforced=1、双后端差分 0\n mainline-acceptance passed\n revocation-sla partial p95 5027ms / max 5041ms / 20 samples——远低于 MS-3 的 30s；\n partial 来自 employmentScope 链仍 pending-scope-consumer-enforcement，\n 以及生产投送/负载/staging 四项 unverified，是既定状态不是失败\n conformance-differential 作为 runtime 验收的副产物一并刷新（同样已登记 severity=warn）\n\n过程中一处失败是我搭环境搭错的，记下来免得下次再犯：首轮 e2e/identity-profile 断言\n`elevated=false` 实测 true——mainline:prepare 只为 fact/permission/audit/owner/consumer 建非超级用户\n角色，identity/credential/scope/aigateway 四个库是我用管理员 platform 手建的，identity 的连接因此是\n特权角色。REASSIGN OWNED 不适用（platform 持有系统对象），改为重建该库并 OWNER 给\nplatform_identity_test_app、以该角色重新 deploy 迁移后转绿。credential / scope 没有\nprisma:migrate:deploy 脚本是对的——它们是 state=shape 模块，按仓纪律不得有迁移。\n\n隔离与收尾：凭据只经仓外 0600 文件（/tmp/c3-mainline.env、/tmp/c3-env.sh），不入仓、不打印；\n验收在独立 worktree 里 pnpm install 自己的 node_modules，不软链主检出，避免与并行会话抢 .prisma；\nadversarial 三容器跑完恢复为 Exited（与我接手前一致）。主检出里并行会话另有十余份报告 WIP，一份没碰。\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-18T17:45:56-07:00"},"CompareURL":"luoanwu/enterprise-platform/compare/12093b843ef69d300370e5da16fcca3399c14d40...b90d7a151e5e9451fa12fb6e883b8898552124df","Len":2}
...
created_unix
1789778893
Delete
Cancel