wooo/awoooi
1
1
Fork 0
Code Issues 2 Pull Requests 1 Actions 2 Packages Projects Releases Wiki Activity

docs(sre): record integration-ready Telegram batch

Browse Source
This commit is contained in:
Your Name
2026-07-19 06:31:45 +08:00
parent 93f9b4af44
commit a20de2cc62
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/operations/sre-k3s-controlled-automation-work-items.snapshot.json
View File

@@ -960,20 +960,22 @@
"rollback": "previous immutable image revision and ConfigMap source SHA",
"exit_condition": "source/test/CD/runtime/UI evidence all match one deployed SHA; gitea-native exact metrics are fresh and the retired legacy GitHub exporter is absent from production",
"confirmed_truth": [
"the local release candidate is merged with the latest observed gitea/main and passes the CD-equivalent non-integration API gate with 5666 passed and 23 skipped, including the 977-test changed-file suite; 4 focused web tests, web typecheck and JSON/YAML parsing also pass",
"the c0afb10861 release candidate was merged with its then-latest observed gitea/main and passed the CD-equivalent non-integration API gate with 5666 passed and 23 skipped, including the 977-test changed-file suite; 4 focused web tests, web typecheck and JSON/YAML parsing also passed",
"stale Telegram tests that required unobserved OpenClaw/NemoTron/ElephantAlpha labels, a promotional check/apply/verify/writeback string or an unreceipted 88 percent confidence were replaced by no-false-AI receipt and actual stage-state contracts; receipt-backed provider, Agent99 executor, verifier and KM/MCP evidence remain visible",
"the Solver, RecommendedAction schema and callback registry now agree that host/systemd actions use the controlled provider and host_ansible_reconcile typed route instead of generic SSH fallback",
"exact source SHA c0afb10861cbb76bc232fad3bbeea0d675cd9b80 was fast-forward pushed once to gitea/main and created the single CD run 5384; no empty commit, retry carrier or force push was used",
"CD run 5384 reached terminal Failure at 2026-07-19T05:05:37+08:00; gitea/main remained c0afb10861cbb76bc232fad3bbeea0d675cd9b80 with no deploy-marker successor",
"production delivery-closure readback generated at 2026-07-19T05:07:28+08:00 still reported runtime build e614f061f781c6e20a3964875d7ab3c28cf91190, so the candidate is not production-visible"
"production delivery-closure readback generated at 2026-07-19T05:07:28+08:00 still reported runtime build e614f061f781c6e20a3964875d7ab3c28cf91190, so the candidate is not production-visible",
"read-only fetch at 2026-07-19T06:30:36+08:00 confirmed tested functional Telegram vertical-slice head 93f9b4af44 was exactly 0 commits behind and 7 commits ahead of gitea/main c0afb10861; its focused verifier/coverage/work-order regressions pass 71 tests, ledger tests pass 9 tests, and the prior AwoooP UI typecheck/JSON/format/desktop/mobile checks remain source evidence only"
],
"runtime_gaps": [
"no program item is runtime closed for this source SHA",
"gitea-native exact target is missing while legacy GitHub exporter runtime drift remains",
"the exact candidate has a terminal failed CD but no deploy marker, production runtime match, visible UI/Telegram receipt or same-run KM/RAG/MCP/PlayBook acknowledgement",
"authenticated CD logs are unavailable in this lane, so the failed step and sanitized final error remain missing; another carrier would be an unproven retry"
"authenticated CD logs are unavailable in this lane, so the failed step and sanitized final error remain missing; another carrier would be an unproven retry",
"the Telegram vertical-slice batch is integration-ready against current gitea/main but intentionally remains local until the separately owned CD 5384 failure is reproduced or proven transient"
],
"next_action": "the CI/CD owner must capture CD 5384 failed-step evidence and either reproduce a deterministic failure locally or prove a transient runner fault before one corrected carrier; after a successful deploy marker, require production API/runtime/UI/Telegram readback plus same-run KM/RAG/MCP/PlayBook acknowledgements"
"next_action": "the CI/CD owner must capture CD 5384 failed-step evidence and either reproduce a deterministic failure locally or prove a transient runner fault; only then normal-push the current 0-behind Telegram batch once, and after a successful deploy marker require production API/runtime/UI/Telegram readback plus same-run KM/RAG/MCP/PlayBook acknowledgements"
}
],
"rollups": {