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 30905 from action
id
30905
user_id
5
op_type
5
act_user_id
5
repo_id
76
comment_id
0
is_deleted
0
ref_name
refs/heads/main
is_private
0
content
{"Commits":[{"Sha1":"ea965ed90
{"Commits":[{"Sha1":"ea965ed902a9807d07d7d89fc173668804c6294c","Message":"chore(reports): 内核准入门禁首轮 8 处诚实红 回绑 @ ee6d5a9\n\nclean 绑定（worktreeDirty:false）——工作区里三份 reports/ui-*.latest.json 的改动\n早于本批次，且 report-provenance 按设计忽略 latest 报告，不影响本次绑定。\n\nK4 七处（声明为 true，evidenceSources 无机器回执）：\n- kernel.digital-employee-core.industryIndependent ← 只有 scripts/check-kernel-boundaries.mjs\n- kernel.digital-employee-core.crossProductRequired ← 只有下游夹具 .ts\n- kernel.digital-employee-core.dualBackendGoverned ← 一份 ADR + 两个脚本\n- pack.generative-ai 的 industryIndependent / dualBackendGoverned ← 源码文件与目录\n- pack.enterprise-fact-consumer 的两项同上\n\nK3 一处：tests/kernel-downstream-fixture/src/index.ts 只有命名空间导入。\n\n未一并修 evidenceSources。改指某份已存在的报告能立刻转绿，但只有当那份报告确实判过\n该条时才是真修：dual-backend-parity 是全仓级判定、不按组件出结论，改指它等于把自证\n换个地方做。哪份报告承接哪一条属 Owner 裁定，不随本次实现一并决定。\n\nK5 观测（不计红）：跨产品具名消费面 5 个符号——ProductManifestInput、\nProductManifestComposition、ProductRuntimeContractCatalog、\nProductDataContractImplementation、ProductEventContractImplementation，\n全部来自 product-manifest.ts；33/38 个模块零跨产品消费，含 tenant.ts 的 65 个导出与\ntool.ts 的 99 个。该数字只作边界收缩决策的输入，不构成「应移出 CORE」的判定。\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:52:16-07:00"},{"Sha1":"ee6d5a98aa6d372d2fc2ea81f328d55cc15511f9","Message":"feat(governance): 内核准入证据门禁 K1—K5，判据从声明下沉到导出清单与证据形态\n\nkernel.boundaries.json 的 admissionEvidence 是四个手写 true，evidenceSources\n只列了路径，没有「该判据确实被机器判过」的回执。实测两处后果：\n\n- CORE 声明 crossProductRequired: true，其证据源 tests/kernel-downstream-fixture/\n src/index.ts 是 10 个 import * as + 判非空 + 一个 typeof === \"function\" 的\n 命名空间冒烟测试——28 个契约模块全空它也照样通过。它能证明包可安装可加载，\n 不能证明任何一个模块跨产品必需\n- 归属粒度是文件：owns.contractModules 是文件名清单，于是\n packages/contracts/src/tenant.ts 一个 1075 行 / 65 导出的文件，把租户策略、\n JWT 验签、自建权限、work 域业务判定四类一起带进了 CORE\n\n手法同 check:platform-provenance（那一条把判据从 package.json 的声明下沉到\npnpm-lock.yaml 的解析结果）。五条判据：\n\n K1 EXPORT_LOCK_DRIFT 组件所辖契约模块的直接导出集合须与\n kernel.exports.lock.json 一致。只认直接声明，\n barrel 的再导出不算拥有——否则 index.ts 会「拥有」全仓\n K2 EXPORT_OWNERSHIP_AMBIGUOUS 同一导出名不得被两个组件同时拥有。拆分契约模块时\n 最容易「复制一份留在原处」，这条守住它\n K3 EVIDENCE_NAMESPACE_ONLY crossProductRequired 的证据源若只有命名空间导入、\n 无任何具名导入，按构造无法证明符号级必需性\n K4 EVIDENCE_NOT_BACKED 声明为 true 的每项须至少有一份机器回执\n （reports/*.json 或 *.lock.json）。脚本路径与文档路径\n 不是回执：只证明文件存在，不证明该判据被判过。\n 声明为 false 的项不要求回执\n K5 CROSS_PRODUCT_UNCONSUMED observed，不计红。CORE 模块未被产品消费不等于不该在\n CORE（OS 自己的两个后端在用）；把观测项当红盘会逼出\n 「为了绿而乱改归属」的反向激励\n\n自检 pnpm check:kernel-admission:self-test 共 10 条，含 1 条基线正例与 2 条防过度\n判红（声明 false 不因无回执计红、零跨产品消费只出 observed）——对照组是为了防\n「只会红的假门禁」。\n\n锁基线 38 个模块 / 779 个导出（CORE 30 + generative-ai 7 + fact-consumer 1）。\n首次签发只固化「现在是什么」，不代表归属正确。\n\ncheck-all 末位注册，理由同 check:platform-provenance：本门禁自引入起即为已知诚实红，\nfail-fast 语义下排前面会让其余门禁全部不执行。pnpm check 因此从 27 步变 28 步且末步红，\n前 27 步照常产出证据。\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:52:01-07:00"}],"HeadCommit":{"Sha1":"ea965ed902a9807d07d7d89fc173668804c6294c","Message":"chore(reports): 内核准入门禁首轮 8 处诚实红 回绑 @ ee6d5a9\n\nclean 绑定（worktreeDirty:false）——工作区里三份 reports/ui-*.latest.json 的改动\n早于本批次，且 report-provenance 按设计忽略 latest 报告，不影响本次绑定。\n\nK4 七处（声明为 true，evidenceSources 无机器回执）：\n- kernel.digital-employee-core.industryIndependent ← 只有 scripts/check-kernel-boundaries.mjs\n- kernel.digital-employee-core.crossProductRequired ← 只有下游夹具 .ts\n- kernel.digital-employee-core.dualBackendGoverned ← 一份 ADR + 两个脚本\n- pack.generative-ai 的 industryIndependent / dualBackendGoverned ← 源码文件与目录\n- pack.enterprise-fact-consumer 的两项同上\n\nK3 一处：tests/kernel-downstream-fixture/src/index.ts 只有命名空间导入。\n\n未一并修 evidenceSources。改指某份已存在的报告能立刻转绿，但只有当那份报告确实判过\n该条时才是真修：dual-backend-parity 是全仓级判定、不按组件出结论，改指它等于把自证\n换个地方做。哪份报告承接哪一条属 Owner 裁定，不随本次实现一并决定。\n\nK5 观测（不计红）：跨产品具名消费面 5 个符号——ProductManifestInput、\nProductManifestComposition、ProductRuntimeContractCatalog、\nProductDataContractImplementation、ProductEventContractImplementation，\n全部来自 product-manifest.ts；33/38 个模块零跨产品消费，含 tenant.ts 的 65 个导出与\ntool.ts 的 99 个。该数字只作边界收缩决策的输入，不构成「应移出 CORE」的判定。\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:52:16-07:00"},"CompareURL":"luoanwu/digital-employee-os/compare/c433d57b4aae2249bd19a085d1c520bf6baedf55...ea965ed902a9807d07d7d89fc173668804c6294c","Len":2}
...
created_unix
1789718112
Delete
Cancel