coulomb/ops-warden
4
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions
ops-warden/workplans/ADHOC-2026-06-27.md
tegwick 030362085a
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
fix(workplans): qualify ad-hoc identifiers with the repository prefix 
`ADHOC-YYYY-MM-DD` is unique per date but not per repository, so any two repos
opening an ad-hoc on the same day collide. The 2026-08-26 fleet projection
reset refused 9 records for exactly this reason.

Canon (work-record-types_v0.1, CUST-WP-0066) settled the form as
`{PREFIX}-WP-ADHOC-YYYY-MM-DD`, filename unchanged, and grandfathered existing
ids on the condition they are never *silently* re-derived. This is the explicit
migration that clause allows for.

The hub id is derived from the record id, so a changed id is a different
record: stale state_hub_*_id fields are dropped and fix-consistency re-derives.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-28 00:28:23 +02:00

1.5 KiB
Raw Blame History

id type title domain repo status owner topic_slug created updated
WARDEN-WP-ADHOC-2026-06-27 workplan Ad Hoc Tasks — 2026-06-27 infotech ops-warden finished claude custodian 2026-06-27 2026-06-27

Ad Hoc Tasks — 2026-06-27

Low-risk opportunistic fixes completed directly during the consolidation session.

T01 — Fix stale warden CLI install + make it usable outside the repo

id: WARDEN-WP-ADHOC-2026-06-27-T01
status: done
priority: medium

issue-core reported (msg 70bcf238) that the warden CLI on ~/.local/bin lacked the route subcommand, forcing a uv run warden fallback.

  • Root cause: uv tool install had reused a cached wheel (version stayed 0.1.0), so the installed warden.cli predated the route/access/policy subcommands. uv cache clean ops-warden + uv tool install . --reinstall fixed it.
  • Deeper cause: even rebuilt, warden route/policy failed outside a checkout because the catalog + posture descriptors live in registry/ at repo root, outside the package. Bundled registry/ into the wheel via hatch force-include → warden/_registry, and added a packaged-data fallback in find_catalog_path / find_posture_path (after the repo walk, so source runs still prefer the repo's registry/ as the single source of truth).
  • Verified warden route list / warden policy list work from /tmp; 200 tests pass, lint clean.