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":"39b8a4e31ee1b00ff5da03fd301042d13d8d1203","Message":"ci(harness): 新增 governance-audit job 把 HIGH=0 锁为 PR/main 硬门禁\n\n.github/workflows/ci.yml:\n- 新增 governance-audit job: 跑 audit:prisma-zod-contract / audit:formrules-zod / audit:response-columns / audit:field-payload / audit:enum-consistency + pnpm harness report 聚合 dashboard\n- 单项审计 continue-on-error: true，最终判定权统一交给 harness-dashboard.summary.high+critical\n- HIGH+CRITICAL \u003e 0 直接 exit 1 阻塞 PR；上传所有 audit JSON artifact + 写 step summary 表格供 reviewer 直读\n- build job 的 needs 加入 governance-audit，确保 main 推送的镜像产物必经治理门禁\n\nCLAUDE.md: 同步追加\"CI 治理门禁经验\"段，明确\"绝不直接调高门禁阈值，要放宽改 adapter/audit severity 映射\"治理纪律。\n\n锁住本会话治理成果——6 类 audit 盲区填补 + 4 类真业务 P1/bug 收口，新 PR 引入新 HIGH 时立即被拦下。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","CommitterName":"luoguoguo","Timestamp":"2026-04-26T09:43:55-07:00"},{"Sha1":"fc67c3eb51e91a01749234e389fcda8c5769bec5","Message":"feat(harness): audit-response-columns 改 import-aware，自动反推真实数据源消除 46 处 view-API 错位误判\n\nscripts/audit-response-columns.ts:\n- 新增 extractApiModuleFromImports(filePath)：解析 view 顶部 `import { xxxApi } from '@/api/modules/\u003cx\u003e'` 取首个 API 模块名\n- 主流程构建 viewModule → apiModule 映射；audit 时优先用 apiModule 查找 Prisma model 与 service include，失败回退 view 目录名\n\n仓库实际有 46 处 view 目录-API 模块错位（attribution-models→attribution / abm-marketing→campaign-targets / social-matrix→marketing-matrix / approval-configs→approval-templates 等）；以前 audit 会把这 46 个 view 的列 prop 全部按错的 Prisma 表做比对，造成大量误报或漏报真 bug。改 import-aware 后自动用真实数据源做比对，不再需要手动加白名单。\n\nCLAUDE.md: 同步更新\"前端 view 目录与实际 API 模块错位经验\"段，记录 46 处实际错位案例与新增 import-aware 实现。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","CommitterName":"luoguoguo","Timestamp":"2026-04-26T09:40:34-07:00"},{"Sha1":"7e9897cf29abcfd1772faa00d204616200f0ab93","Message":"fix(schema): 收口 formrules-zod 9 项 MEDIUM，前后端 description/category/name 全栈对齐\n\n5 处 description Zod max 收紧（前端早就 maxlength=500，后端 2000 是历史遗留）:\n- attribution-models / customer-segmentation / lead-assignment / lead-scoring / store-configs:\n  description Zod max(2000) → max(500)，反向对齐前端 UX 上限\n\nai-agents skill-library FormRules 放宽到 Zod 上限:\n- skill-library/Form.vue: category FormRules max=50 → 100，对齐 Zod max(100)（category 50 字过紧）\n\nchannel-integrations Form 全栈对齐 Zod:\n- Form.vue: FormRules min=2/max=100 → min=1/max=200，maxlength=\"100\" → \"200\"\n  对齐 Zod min(1).max(200)，原 min=2 拒绝 1 字符是过度严格\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","CommitterName":"luoguoguo","Timestamp":"2026-04-26T09:36:20-07:00"},{"Sha1":"aba788bb6011125e1178d038c14f936480380368","Message":"docs(governance): 追加 P1-P6 治理经验补充段（dashboard/adapter/audit 盲区/字段错位/maxlength/grade 联动）\n\n新增 5 段经验补充（2026-04-26）:\n- Harness Dashboard / Adapter 一致性: dashboard 与 audit latest.json 时间戳必须同步；adapter 字段名严格对齐审计 JSON 真实 key；severity 按 audit raw severity 分级。\n- Prisma↔Zod 审计盲区: 4 类系统性盲区（嵌套子 schema 误匹配 / camel-snake 双计数 / .refine 后置约束 / service 层 auto-gen 字段）的识别与豁免规则。\n- 前端 view 目录与 API 模块错位: approval-configs/Index.vue 实际调 approvalTemplatesApi 这类目录-模块错位的治理路径与 audit 增强建议。\n- Form maxlength 同步: Zod .max(N) 改动必须同步 el-input maxlength；Zod 校验和 maxlength 是不同阶段（提交 vs 输入）。\n- Grade hasEventPublishing 与 moduleType 联动: BaseService 派生识别 + manifest moduleType 双重通路；CRUD 模块缺事件应补 publishEvent 而非加豁免。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","CommitterName":"luoguoguo","Timestamp":"2026-04-26T09:32:19-07:00"},{"Sha1":"744548892f552934566e0879669c2aeb0829fe7d","Message":"fix(schema): 收口 Prisma↔Zod 长度真 P1 + 同步前端 maxlength + 修 approval-configs 列名\n\n真 P1 收口（Zod max \u003e Prisma VarChar，DB 会拒绝写入）:\n- alliance-agreements.content: Zod max(10000) → max(5000) 对齐 Prisma VarChar(5000)\n- product-categories.description: Zod max(2000) → max(500) 对齐 Prisma VarChar(500)\n\n前端 maxlength 同步（formrules-zod HIGH 4 项收口）:\n- alliance-agreements/Form.vue: content maxlength=\"10000\"→\"5000\"\n- lead-scoring/Form.vue: field 字段 maxlength=\"100\", value 字段 maxlength=\"500\"\n- product-categories/Index.vue: 分类名 maxlength=\"200\"\n- supplier-center/Index.vue: 供应商名 maxlength=\"200\"\n\n真 bug 修复（response-columns HIGH 1 项）:\n- approval-configs/Index.vue: prop=\"objectType\" / row.objectType / 查询参数 objectType 全部改为 entityType。原列名在 Prisma model 不存在且 API 返回字段是 entityType，原列永远显示空——是真 bug 不是审计噪声。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","CommitterName":"luoguoguo","Timestamp":"2026-04-26T09:32:04-07:00"}],"HeadCommit":{"Sha1":"39b8a4e31ee1b00ff5da03fd301042d13d8d1203","Message":"ci(harness): 新增 governance-audit job 把 HIGH=0 锁为 PR/main 硬门禁\n\n.github/workflows/ci.yml:\n- 新增 governance-audit job: 跑 audit:prisma-zod-contract / audit:formrules-zod / audit:response-columns / audit:field-payload / audit:enum-consistency + pnpm harness report 聚合 dashboard\n- 单项审计 continue-on-error: true，最终判定权统一交给 harness-dashboard.summary.high+critical\n- HIGH+CRITICAL \u003e 0 直接 exit 1 阻塞 PR；上传所有 audit JSON artifact + 写 step summary 表格供 reviewer 直读\n- build job 的 needs 加入 governance-audit，确保 main 推送的镜像产物必经治理门禁\n\nCLAUDE.md: 同步追加\"CI 治理门禁经验\"段，明确\"绝不直接调高门禁阈值，要放宽改 adapter/audit severity 映射\"治理纪律。\n\n锁住本会话治理成果——6 类 audit 盲区填补 + 4 类真业务 P1/bug 收口，新 PR 引入新 HIGH 时立即被拦下。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@luoguoguodeMacBook-Pro.local","CommitterName":"luoguoguo","Timestamp":"2026-04-26T09:43:55-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/a67a4f5bf6bede6341ed368fb3af3caec8dcd71c...39b8a4e31ee1b00ff5da03fd301042d13d8d1203","Len":6}

TEXT

created_unix

INTEGER

Update row 1214 in action