coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(ops): surface pre-record schedule failures
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Container Image / build-and-push (push) Successful in 26s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06bfe-2a55-7ed3-bacd-879977b099bf
This commit is contained in:
tegwick 2026-09-04 21:09:35 +02:00
parent fc38ca0fdf
commit 9394c40e3a
5 changed files with 45 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/runbook.md
View file

@ -368,9 +368,12 @@ schedules, use the prod helper (SSH to the host; no k3s API tunnel is required):
./scripts/prod_automation_status.sh 2026-07-18T22:00:00+00:00
```
The script SSHes to `railiance01` (see `~/.ssh/config`), queries
`activity_runs` via `kubectl -n activity-core exec actcore-app-db-0`, and prints
per-activity counts plus non-high-frequency fire rows. It never prints secrets.
The script SSHes to `railiance01` (see `~/.ssh/config`), runs the repository's
deterministic status engine inside the worker, queries `activity_runs` via
`kubectl -n activity-core exec actcore-app-db-0`, and prints per-activity counts
plus non-high-frequency fire rows. The deterministic verdict catches an
expected schedule fire that failed before `activity_runs` was written instead
of letting it disappear from the SQL-only table. It never prints secrets.
Manual equivalent: