tegwick
17f2caee01
scripts/prod_automation_status.sh took a positional since value, so the
Makefile's own `SINCE=sunday` form passed the literal string into timestamptz:
all five sections errored while the run still looked like it produced a report.
Now `SINCE=` is accepted and the value is parsed and normalised to UTC up
front, failing fast with usage and exit 2 instead of five parse errors.
ACTIVITY-WP-0032 plans adoption of the glas-harness contract 1.0 reported in
GLAS-WP-0004. WP-0026 is finished, so this gets its own plan. The motivation is
concrete: ops_run.approach_hint binds at claim time, which produced a failed
run on 2026-08-17 ("no approach matched labels/definition") after it had
already consumed a claim and a lease.
T01 is deliberately blocking: our claim path is pull-based and the Glas
contract is a call, so the invocation shape is an architectural decision, not a
port. Two questions are outstanding with glas-harness.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| automation_inventory.py | ||
| automation_status.py | ||
| export_schemas.py | ||
| openbao-eso-token-apply.sh | ||
| prod_automation_status.sh | ||
| refresh_live_images.sh | ||
| schedule_coding_retro_dry_run.py | ||
| smoke_admin_sync_no_restart.py | ||
| smoke_issue_core_emission.py | ||
| smoke_test_schedule.py | ||
| sync_event_types.py | ||
| verify_daily_triage.py | ||