ops-warden

coulomb/ops-warden

Fork 0

generated from coulomb/repo-seed

Commit Graph

Author	SHA1	Message	Date
tegwick	a10bbd2162	feat(WARDEN-WP-0021): T3-T5 — visibility, approve loop, runbook (scheduled worker complete) T4 (review→send loop): conservative tick persists structured drafts to state_dir/worker-drafts.json; `warden worker drafts` lists them, `warden worker approve <id> [--body …]` sends the reviewed draft as the reply + marks read + drops it. Escalated plans persist no draft. Live-verified end-to-end. T3 (visibility): `warden worker status` (pending drafts, triage count, last digest, timer state); best-effort notify-send nudge in the tick when drafts are pending. T5: wiki/playbooks/scheduled-worker.md (enable/disable, the approve loop, failure modes, conservative-only posture) + SCOPE note. WARDEN-WP-0021 finished: the conservative worker now runs on a systemd --user timer (enabled, every 15 min), triages new inbox messages into drafts you approve with one command, degrades gracefully, and stops with one command. 249 tests, lint clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-30 15:24:10 +02:00
tegwick	9dc1db0162	feat(WARDEN-WP-0021): T1+T2 — scheduled worker tick enabled (systemd --user timer) T1: systemd --user units (ops-warden-worker.{service,timer}) + scripts/install-worker-timer.sh (--enable opt-in, cron fallback documented) + examples/worker.env.example. Kill switch: `systemctl --user disable --now ops-warden-worker.timer` or WORKER_ENABLED=0. Installed and ENABLED — verified a real systemd run (Result=success, used the llm brain) and the timer is active (next run +15min). T2: hardened worker-tick.sh — State Hub /state/health precheck → graceful skip (exit 0) when unreachable; worker-run failure logged but never fails the unit (retry next tick). Verified hub-down skip and a live tick. Conservative tier only; nothing auto-sent. Kill switch is one command. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-30 15:19:23 +02:00
tegwick	22c5bd1bbb	feat(WARDEN-WP-0020): T4 scheduling tick + T5 SCOPE — worker complete T4 — scripts/worker-tick.sh: scheduled tick for the conservative worker. flock concurrency guard; short-lived kubectl port-forward to llm-connect (or LLM_CONNECT_URL, or rule-brain fallback). Ships disabled; header documents the cron entry. Schedules the conservative tier only (never auto-send). T5 — SCOPE records `warden worker` as an implemented capability: conservative triage default, full-auto opt-in, llm-connect brain, the four guardrails, schedulable tick. WARDEN-WP-0020 finished: the autonomous coordination worker — T1 scaffold, T2 llm-connect brain, T3 guarded executor, conservative tier (Option A), T4 scheduling, T5 docs. 245 tests, lint clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-30 00:41:04 +02:00

Author

SHA1

Message

Date

tegwick

a10bbd2162

feat(WARDEN-WP-0021): T3-T5 — visibility, approve loop, runbook (scheduled worker complete)

T4 (review→send loop): conservative tick persists structured drafts to
state_dir/worker-drafts.json; `warden worker drafts` lists them, `warden worker approve
<id> [--body …]` sends the reviewed draft as the reply + marks read + drops it. Escalated
plans persist no draft. Live-verified end-to-end.

T3 (visibility): `warden worker status` (pending drafts, triage count, last digest, timer
state); best-effort notify-send nudge in the tick when drafts are pending.

T5: wiki/playbooks/scheduled-worker.md (enable/disable, the approve loop, failure modes,
conservative-only posture) + SCOPE note.

WARDEN-WP-0021 finished: the conservative worker now runs on a systemd --user timer
(enabled, every 15 min), triages new inbox messages into drafts you approve with one
command, degrades gracefully, and stops with one command. 249 tests, lint clean.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-30 15:24:10 +02:00

tegwick

9dc1db0162

feat(WARDEN-WP-0021): T1+T2 — scheduled worker tick enabled (systemd --user timer)

T1: systemd --user units (ops-warden-worker.{service,timer}) + scripts/install-worker-timer.sh
(--enable opt-in, cron fallback documented) + examples/worker.env.example. Kill switch:
`systemctl --user disable --now ops-warden-worker.timer` or WORKER_ENABLED=0. Installed and
ENABLED — verified a real systemd run (Result=success, used the llm brain) and the timer is
active (next run +15min).

T2: hardened worker-tick.sh — State Hub /state/health precheck → graceful skip (exit 0) when
unreachable; worker-run failure logged but never fails the unit (retry next tick). Verified
hub-down skip and a live tick.

Conservative tier only; nothing auto-sent. Kill switch is one command.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-30 15:19:23 +02:00

tegwick

22c5bd1bbb

feat(WARDEN-WP-0020): T4 scheduling tick + T5 SCOPE — worker complete

T4 — scripts/worker-tick.sh: scheduled tick for the conservative worker. flock concurrency
guard; short-lived kubectl port-forward to llm-connect (or LLM_CONNECT_URL, or rule-brain
fallback). Ships disabled; header documents the cron entry. Schedules the conservative tier
only (never auto-send).

T5 — SCOPE records `warden worker` as an implemented capability: conservative triage
default, full-auto opt-in, llm-connect brain, the four guardrails, schedulable tick.

WARDEN-WP-0020 finished: the autonomous coordination worker — T1 scaffold, T2 llm-connect
brain, T3 guarded executor, conservative tier (Option A), T4 scheduling, T5 docs. 245 tests,
lint clean.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-30 00:41:04 +02:00

3 Commits