98 Commits

Author	SHA1	Message	Date
Your Name	c8a995aff2	feat(governance): archive duplicate km review drafts	2026-05-20 00:30:17 +08:00
Your Name	0cd6301d0e	feat(governance): expose km draft dedupe plan	2026-05-19 23:56:03 +08:00
Your Name	855716b5b8	feat(awooop): surface km review draft dedupe	2026-05-19 23:27:33 +08:00
Your Name	c99be252d3	feat(governance): surface km healthcheck dispatch	2026-05-19 21:07:55 +08:00
Your Name	61d82b3ad3	feat(web): surface automation evidence on homepage	2026-05-19 18:22:37 +08:00
Your Name	56a8085dcf	feat(awooop): surface ai provider route status	2026-05-19 13:45:04 +08:00
Your Name	784ebf49ef	feat(awooop): surface status chain in operator console	2026-05-19 10:13:33 +08:00
Your Name	64b34828a7	feat(drift): record remediation evidence	2026-05-19 09:13:58 +08:00
Your Name	0b5268a666	feat(drift): surface fingerprint state handoff	2026-05-19 00:39:49 +08:00
Your Name	fb9b0b3b7c	feat(awooop): record recurrence handoff proposals	2026-05-19 00:13:40 +08:00
Your Name	d1ebcdac10	feat(awooop): preview recurrence repair work items	2026-05-18 21:42:20 +08:00
Your Name	b50614528e	feat(awooop): surface recurrence repair work items	2026-05-18 20:30:43 +08:00
Your Name	7fa06731da	feat(awooop): link recurring alerts to repair work	2026-05-18 19:50:12 +08:00
Your Name	94f8c68b77	feat(awooop): show recurring alert links	2026-05-18 19:23:37 +08:00
Your Name	213523c77d	feat(awooop): surface source dossier coverage	2026-05-18 19:01:28 +08:00
Your Name	08a75f4b5a	feat(awooop): search callback reply evidence	2026-05-18 16:17:05 +08:00
Your Name	f3494e0bfb	feat(awooop): filter runs by callback reply state	2026-05-18 15:54:21 +08:00
Your Name	20d62ee0cf	feat(awooop): surface callback replies on run list	2026-05-18 15:24:39 +08:00
Your Name	1a16e083e7	feat(awooop): show callback reply states in timeline	2026-05-18 14:54:49 +08:00
Your Name	9d02ab8080	feat(awooop): surface mcp investigation evidence	2026-05-18 13:55:27 +08:00
Your Name	daf672aa1e	feat(awooop): show automation claim on work items	2026-05-18 10:12:51 +08:00
Your Name	902593f775	feat(awooop): surface legacy mcp evidence in run detail	2026-05-18 09:16:59 +08:00
Your Name	69f2ec5ec9	feat(awooop): add incident evidence headers	2026-05-17 23:37:53 +08:00
Your Name	76c302ab5f	feat(awooop): expose incident evidence links	2026-05-17 22:49:55 +08:00
Your Name	6868a9a93d	feat(awooop): link telegram alerts to incident runs	2026-05-17 22:17:21 +08:00
Your Name	665e72ba33	feat(awooop): filter runs by remediation evidence	2026-05-17 21:13:54 +08:00
Your Name	0592402779	feat(awooop): surface remediation evidence in run lists	2026-05-17 20:26:03 +08:00
Your Name	bc89940564	feat(awooop): link remediation evidence to run timeline	2026-05-15 02:31:46 +08:00
Your Name	65001da0d8	fix(telegram): preserve incident history html output	2026-05-14 23:33:43 +08:00
Your Name	475f2e452d	feat(frontend): expand incident timeline event details	2026-05-14 23:09:12 +08:00
Your Name	392cfb9025	feat(governance): surface remediation dry run history	2026-05-14 22:56:51 +08:00
Your Name	6aaaf87ade	feat(governance): persist remediation dry run history	2026-05-14 22:38:42 +08:00
Your Name	04fdaee83a	feat(governance): add remediation dry run entrypoint	2026-05-14 22:20:34 +08:00
Your Name	aa63ae5eca	feat(governance): surface verification remediation queue	2026-05-14 21:45:33 +08:00
Your Name	bad48dee04	feat(governance): explain verifier failures	2026-05-14 20:49:20 +08:00
Your Name	485c58d085	feat(governance): surface verification coverage	2026-05-14 20:28:53 +08:00
Your Name	809bc9670b	feat(governance): surface adr100 slo states	2026-05-14 19:57:32 +08:00
Your Name	e8c4512a40	feat(awooop): surface automation work chain	2026-05-14 18:08:13 +08:00
Your Name	77aace7515	feat(awooop): show inbound event dossiers	2026-05-13 21:59:16 +08:00
Your Name	e4203060f3	feat(awooop): surface automation quality overview	2026-05-13 16:23:47 +08:00
Your Name	c486087294	feat(awooop): surface gateway summary in details	2026-05-13 11:49:37 +08:00
Your Name	3df23112ef	fix(awooop): reconnect approval decisions to run timeline	2026-05-07 09:37:45 +08:00
Your Name	beba668a4c	feat(awooop): add run detail action panel	2026-05-07 09:25:49 +08:00
Your Name	f960a4a19b	fix(awooop): localize run detail timeline	2026-05-07 05:46:31 +08:00
Your Name	7f4f5b24ba	fix(awooop): clarify operator disposition lanes	2026-05-06 22:24:28 +08:00
Your Name	ea5ad040da	fix(telegram): clarify automation notification state	2026-05-06 20:59:58 +08:00
Your Name	a2c4b3d47e	fix(awooop): align console with flywheel execution metrics	2026-05-06 00:46:08 +08:00
Your Name	e45b055e0e	feat(governance): AI 治理事件處理鏈四軌交付（C/D/B/A） ... 【十二人專家團隊全景掃描 + 並行四軌實施】 統帥質疑「有讓 12-agent 一起協作嗎」後，依照團隊規則完成全鏈路交付： onboarder + critic + db-expert + debugger + frontend-designer 並行掃描， 找到 6 大 Gap，再由 fullstack-engineer × 4、refactor-specialist 協作落地。 【Track C — trust_drift 雙寫整併】 兩條獨立寫 event_type=trust_drift 路徑互不呼叫，下游 consumer 拿到雙份資料 無法判定 source-of-truth。整併保留 governance_agent.check_trust_drift（功能 更全：auto-deprecate + Telegram + PG），TrustDriftDetector 降為純統計 lib， W-6 watchdog 改呼叫 governance_agent。新增 TestSinglePgWritePerDriftScenario 驗證同一 drift 場景只觸發一次 PG 寫入。 變更： - apps/api/src/services/trust_drift_detector.py（lib only，不再寫 PG） - apps/api/tests/test_trust_drift_watchdog.py（W-6 改 mock governance_agent） 【Track D — governance_remediation_dispatch 派遣表】 ai_governance_events 是不可變 Event Sourcing，不能塞執行狀態。新建派遣表 作為投影層：1 event → 0..N dispatches，狀態可變、可重試、可審計。 - PgEnum 5 種 event_type + 7 階段狀態機（pending → dispatched → executing → succeeded/failed/cancelled/skipped） - 失敗重試 INSERT 新 row（不改舊 row 的 status，保留審計痕跡） - Partial unique index ux_grd_one_active_per_event 強制「同事件唯一活躍」 - 4 個複合 index 支援 worker poll、去重查詢、觀測面板 - FK 對應 ai_governance_events / playbooks / incidents / approval_records 全部 SET NULL（avoid cascade lock，但 governance_event 用 RESTRICT） 變更： - apps/api/src/db/models.py（GovernanceRemediationDispatch ORM class） - apps/api/migrations/governance_remediation_dispatch_2026-05-03.sql - apps/api/src/repositories/governance_remediation_dispatch_repo.py （6 個 async 函式 + 3 個自訂例外：DispatchAlreadyActive / InvalidStatusTransition / DispatchNotFound） - apps/api/src/models/governance_dispatch.py（DecisionContextV1 等 4 schema） - apps/api/tests/test_governance_remediation_dispatch.py（29 tests） 【Track B — /governance 頁面】 後端 PR1 三個 endpoint + 前端 PR2-5 完整三 Tab。 PR1 後端： - GET /api/v1/ai/governance/events（events_tab，含 event_type/severity/ 狀態/時間範圍篩選 + 分頁） - GET /api/v1/ai/governance/queue（queue_tab，含 graceful fallback： dispatch 表不存在時回 table_pending=True 不拋 500） - GET /api/v1/ai/governance/summary（slo_tab 30d 違反時序圖） - severity 映射規則寫死（critic 建議未來移 settings） PR2-5 前端： - /governance 路由 + AppLayout + Compliance Badge 橫幅 + PageTabs - SLO Tab：3 KPI 卡片（Syne 28px + StatusOrb + 7d sparkline）+ 30d 違反 stacked BarChart - Events Tab：篩選列 + 表格 + inline 展開行（JSON / 修復建議 / 派遣記錄） - Queue Tab：HITL 待辦卡片 + 信任度進度條 + 批准/拒絕按鈕（本 PR console.log） - Sidebar 加入「AI 治理」入口（ShieldCheck icon） - i18n 雙語完整（governance namespace + nav.governance） - 7 個新元件：slo-kpi-card / slo-violation-chart / events-table / events-filter-bar / event-detail-drawer / queue-item-card / queue-history-tabs 變更： - apps/api/src/api/v1/ai_governance.py（router） - apps/api/src/services/governance_query_service.py - apps/api/src/models/governance.py（Pydantic V2 schemas） - apps/api/tests/test_ai_governance_endpoints.py（21 tests） - apps/web/src/app/[locale]/governance/（page + 3 tabs） - apps/web/src/components/governance/（7 元件） - apps/web/messages/{zh-TW,en}.json（governance namespace） - apps/web/src/components/layout/sidebar.tsx（+1 行） - apps/api/src/main.py（router include） 【Track A — GovernanceDispatcher 決策融合】 把治理事件接到 remediation 執行器，走北極星方向決策融合（LLM × Playbook trust × MCP），符合「禁寫死規則」鐵律。 - 設計鐵律：DecisionFusionAdapter 是新增 wrapper，**不修改任何 Tier 3 檔** （decision_manager / learning_service / trust_engine），只 consume 既有 API - 三維融合公式：confidence = 0.4×llm + 0.3×playbook_trust + 0.3×mcp_consistency （權重加 TODO 標明未來由 AI 自學調整） - 三分支決策路徑： confidence ≥ 0.85 → auto_dispatch（status=dispatched） 0.65 ≤ confidence < 0.85 → pending_approval（HITL） confidence < 0.65 → skip + log - decision_context JSONB 完整記錄三維輸入快照（給未來 fine-tune 用） - poll 30s 掃 unresolved 事件，仿 governance loop 模式 - 重複事件擋去重（呼叫 get_active_for_event） 變更： - apps/api/src/services/governance_dispatcher.py - apps/api/src/services/decision_fusion_adapter.py - apps/api/tests/test_governance_dispatcher.py（14 tests） - apps/api/src/main.py（lifespan task 接 run_governance_dispatcher_loop） 【驗證】 1836 個 unit test 全過（29 skipped 為既有 PG integration env 問題） 【調度教訓 — 已記入 memory】 - vuln-verifier 應在 fullstack-engineer **之前**跑（避免並行讀到已修代碼誤判） - critic 雙輪審查不可省（第二輪抓到 NaN sentinel + Prom rule 連鎖） - 北極星「禁寫死規則」搭配 decision-fusion 確實實施 【未動 Tier 3 — 已驗證】 git diff 確認本 commit 完全沒改 decision_manager.py / learning_service.py / trust_engine.py，只新增 wrapper service consume 既有 API。 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-03 12:42:40 +08:00
Your Name	cc547736ab	feat(wave6-8): P2.1 fusion + P2.2 governance + P2.4 consensus + Wave 7/8 BLOCKER 修復 ... 承接 Wave 6/7/8 多 engineer 在 agent 限額前完成的代碼，補 commit 解 production HEAD 隱性 import error（decision_fusion 已被 decision_manager 引用但檔案 untracked）。 新增（後端核心）: - decision_fusion.py (562 行) — P2.1 方法 III（OpenClaw + Hermes + Elephant 三 LLM 融合） - aiops_timeline.py + aiops_timeline_service.py — critic B4 修復 /api/v1/aiops/timeline endpoint，DB 存取抽到 service 層遵守 leWOOOgo 積木化 - migrations/p2_decision_fusion_columns.sql + rollback — approval_records fusion 欄位 修改（後端整合）: - decision_manager.py — fusion 三斷鏈修補（critic B1+B2+B3）： · B1: 寫 _evidence_snapshot_ref 到 token.proposal_data · B2: fusion 前計算 complexity_score 並寫 token · B3: fusion composite 寫 token.proposal_data["decision_fusion"] - auto_approve.py — fusion + consensus 認識（critic B3+B5）： · composite > 0.7 → auto_execute_eligible bypass min_confidence · source=consensus_engine + score>=0.6 → 規則可信路徑 - consensus_engine.py — db-fix _save_consensus 重用 agent_sessions - governance_agent.py — db-fix _alert PG 寫入 ai_governance_events - approval_db.py — fusion 3 欄位 + 2 partial index + CheckConstraint - db/models.py — schema 對齊 migration - core/config.py — vuln #1 修復：OLLAMA_URL/_FALLBACK_URL field_validator 拒絕公網 IP + 外部域名，僅允許私網/loopback/K8s SVC 白名單 - core/feature_flags.py — P2 fusion + consensus flags - main.py — governance_agent lifespan 啟動 - failover_alerter.py — Wave8-X2: in-memory dedup fallback（Redis 拒絕後不 fail-open） - ollama_*.py — metrics 整合 + recovery 改善 - auto_repair_service.py — verifier 接線 新增（測試 2438 行）: - test_decision_fusion.py / test_governance_agent.py / test_consensus_integration.py - test_p2_db_fixes.py / test_wave8_fusion_fixes.py - test_config_url_validation.py（vuln #1 12 tests） - test_failover_alerter.py +Wave8-X2 in-memory dedup 補測 驗收: 116 tests pass (decision_fusion + wave8_fusion + config_url + consensus + governance + p2_db_fixes + failover_alerter) Conflict resolution: - 3 檔（config.py + auto_approve.py + decision_manager.py）git stash pop 衝突 保留 stashed (engineer 最終版)，補回 ValueError 「公網 IP」字樣對齊 test Note: 此 commit 解 production HEAD 隱性 import error 仍未修: vuln #4 prompt injection / debugger B14 quota fail-closed / B25-B26 drain_pending_tasks / B8 governance fail alert Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-Authored-By: Multiple Engineers (Wave 6/7/8) <noreply@anthropic.com>	2026-04-27 08:11:40 +08:00
OG T	f8c6dfc642	feat(web): Header ⌘K 搜尋提示按鈕 + sensor service file 補齊 ... Header: - 新增 ⌘K 入口按鈕（搜尋圖示 + "搜尋..." + ⌘K badge） - 點擊觸發 window keydown(meta+k) 開啟 CommandPalette - hover 變藍（UX 提示） Sensor: - 補齊 apps/sensor/awoooi-sensor.service（PYTHONUNBUFFERED=1 + --loop） Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-04-10 00:29:15 +08:00