activity-core

Author	SHA1	Message	Date
tegwick	21dc228cb1	fix(ops_run): unique triggering_event_id per cron fire All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 2s Details Build and Publish Container Image / build-and-push (push) Successful in 21s Details Cron schedules always passed trigger_key="scheduled", so ops_run idempotency collapsed every weekday into one key. After the first fire, create_ops_run was a silent no-op, the claim loop starved, and dual-clock host timers produced empty FI briefs. Map scheduled fires to run_id (or scheduled:{iso}) via emit_triggering_event_id; log duplicate skips; document the contract.	2026-08-05 15:30:00 +02:00
tegwick	6ce77a72bb	Document ACTIVITY-WP-0026-T07 railiance deploy checklist. All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 2s Details Add deploy-ops-run-queue-railiance.md (image, migrate 0007, smoke, dual-path residual), wire OPS_RUN_* into runtime ConfigMap, and cross-link runbook/README. T07 stays open until prod smoke is executed.	2026-08-03 19:30:00 +02:00
tegwick	15eb3a2066	Implement ACTIVITY-WP-0026 ops_run claim queue (T01–T06). All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 2s Details Build and Publish Container Image / build-and-push (push) Successful in 52s Details Add durable claimable ops_runs table, emit dual-write on TaskSpec, REST claim/lease/complete/fail API, ops status visibility, and consumer docs aligned with ACT-ADR-005. T07 railiance rollout remains deploy-side.	2026-08-03 19:22:50 +02:00

3 commits