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>
This commit is contained in:
2026-06-30 00:41:04 +02:00
parent d0261ebb52
commit 22c5bd1bbb
3 changed files with 61 additions and 7 deletions

View File

@@ -4,7 +4,7 @@ type: workplan
title: "ops-warden worker — autonomous coordination via llm-connect"
domain: infotech
repo: ops-warden
status: active
status: finished
owner: claude
topic_slug: custodian
planning_priority: high
@@ -134,25 +134,32 @@ state_hub_task_id: "3a71965e-42d5-4258-9761-aced804c88e7"
```task
id: WARDEN-WP-0020-T04
status: todo
status: done
priority: medium
state_hub_task_id: "7f77ea6d-c281-42c5-ad25-2a0bb9fd68de"
```
- [ ] Wire cron or activity-core to `warden worker run --once`. Ships **disabled**; enabled
only after a clean dry-run shakedown. Concurrency guard (no overlapping runs).
- [x] `scripts/worker-tick.sh` — scheduled tick for the conservative worker. `flock`
concurrency guard (no overlapping runs); brings up a short-lived kubectl port-forward
to llm-connect (or honors `LLM_CONNECT_URL`, or falls back to the rule brain offline).
Ships **disabled**; the header documents the cron entry to enable it (every 15 min).
Dry-shakedown done (the conservative live run + the rule-brain tick both verified).
Schedules the **conservative** tier only — never the auto-send path.
### T5 — Docs / SCOPE / INTENT
```task
id: WARDEN-WP-0020-T05
status: todo
status: done
priority: medium
state_hub_task_id: "6e7ae317-7f8b-468a-bb5c-b08093ed43a0"
```
- [ ] Record the scope expansion: ops-warden gains an autonomous coordination worker.
Document the guardrails as a security-model statement; update SCOPE/INTENT.
- [x] SCOPE: recorded the coordination worker (`warden worker`) as an implemented
capability — conservative triage default, full-auto opt-in, llm-connect brain, the
four guardrails, schedulable tick. The guardrails + the conservative-by-default
posture are documented as the worker's security-model statement (here + in the
build-stage decision 813899f9).
---