chore(sre): reconcile telegram source readiness

This commit is contained in:
Your Name
2026-07-19 01:24:44 +08:00
parent 52e40462cd
commit a509cb9970
2 changed files with 30 additions and 11 deletions

View File

@@ -753,7 +753,7 @@
"title": "Telegram 與 cockpit 只呈現 canonical lifecycle truth",
"owner_lane": "ProductExperience",
"risk": "medium",
"status": "in_progress",
"status": "source_implemented_runtime_pending",
"dependencies": [
"AIA-SRE-015"
],
@@ -767,17 +767,28 @@
"agent99-sre-alert-relay.ps1",
"scripts/reboot-recovery/deploy-agent99-via-windows99-ssh.sh",
"apps/api/src/services/failover_alerter.py",
"apps/api/src/services/telegram_gateway.py"
"apps/api/src/services/telegram_gateway.py",
"apps/api/src/services/notification_matrix.py",
"apps/api/src/services/agent99_sre_bridge.py",
"apps/api/src/services/agent99_telegram_lifecycle.py",
"apps/api/src/services/telegram_button_registry.py",
"apps/api/src/services/callback_dispatcher.py"
],
"executor": "canonical Telegram gateway",
"verifier": "delivery receipt plus desktop/mobile visible smoke",
"rollback": "suppress duplicate projection; retain incident ledger",
"exit_condition": "no alert is sprayed across groups/bots; every card states AI/provider/Agent action, executor, verifier and receipt truth; AlertChainBroken uses Alertmanager integration-scoped delivery counters stamped with the independently tested sole-webhook receiver contract plus host99 Agent99 exact-host read-only polling independent of the broken webhook; UI status polling never emits failover alerts",
"confirmed_truth": [
"source registry covers 11 products and 26 typed routes; only allowlisted P0/P1 operational routes resolve to the AwoooI SRE war room",
"unknown product, signal, severity or requested destination fails closed and active source contains no raw numeric Telegram destination default",
"Telegram automation cards distinguish durable AI/provider, Agent, executor, verifier and learning receipts from configured-but-unobserved components",
"information and controlled-action buttons are bound to registered callback actions instead of display-only ghost buttons"
],
"runtime_gaps": [
"the host99 Agent99 independent pull/reduced relay has no production deployment, freshness, dedupe or controlled-repair receipt",
"production Alertmanager exposes integration-only notification counters; the bounded check now passes after adding a scrape-time receiver_contract label, but apply, alert resolution and same-run learning receipts remain pending"
],
"next_action": "deploy the production-schema-compatible Alertmanager runtime scrape/canonical rules, the host99 Agent99 exact-host poller and the fixed DB dispatch entrypoint through the atomic 17-file bundle; verify receiver-contract freshness, dedupe and the current firing alert resolution; then reconcile every project/product/alert class against its typed domain and canonical Telegram destination"
"next_action": "deploy one exact source revision through the authorized release lane, then verify receiver-contract freshness, host99 Agent99 exact-host polling, dedupe, callback execution, current firing alert resolution and recipient-visible same-run delivery receipts; source tests must not be counted as runtime closure"
},
{
"id": "AIA-SRE-018",
@@ -821,12 +832,12 @@
"P1": 2
},
"by_status": {
"source_implemented_runtime_pending": 9,
"in_progress": 4,
"source_implemented_runtime_pending": 10,
"in_progress": 3,
"planned": 4,
"policy_active": 1
},
"source_implemented_items": 9,
"source_implemented_items": 10,
"runtime_closed_items": 0,
"program_completion_percent": 0,
"asset_coverage_status": "partial",