teleo-infrastructure/docs/reports/leo-working-state-20260709/argus-kb-state-current.md
twentyOne2x 34b45365ec
Some checks are pending
CI / lint-and-test (push) Waiting to run
Add Leo direct-claim preflight probes
2026-07-10 04:50:04 +02:00

38 lines
1.1 KiB
Markdown

# Argus KB State Probe
Generated UTC: `2026-07-10T02:48:11.734733+00:00`
Mode: `argus_kb_state_readonly_http_probe`
Status: `pass`
Base URL: `http://77.42.65.182:8081`
## Fetch Sources
- `kb_proposals`: `supplied_base64_json`
- `metrics`: `supplied_base64_json`
- `vital_signs`: `supplied_base64_json`
## Checks
- `approved_need_apply_payload`: `True`
- `approved_proposals_visible`: `True`
- `http_readback_ok`: `True`
- `kb_proposals_endpoint_read_only`: `True`
- `no_worker_applyable_approved_proposals`: `True`
## Approved Proposal State
- Total: `3`
- Status counts: `{"approved": 3}`
- Review state counts: `{"approved_needs_apply_payload": 3}`
- Worker-applyable count: `0`
- Read-only endpoint: `True`
## Proposal IDs
- `14fa5ecc-ac7a-41c1-807d-a2e85b936617`
- `ac036c9d-20a0-4ffe-881f-57d6b7bacf22`
- `a64df080-8502-42e2-98f4-9bbdecb8da73`
## Claim Ceiling
This is public Argus HTTP diagnostics evidence only. It proves the diagnostics surface can see approved KB proposals and their applyability state; it does not prove Docker/Postgres row counts, gateway systemd state, Telegram-visible reply quality, or production apply execution.