coulomb/ops-warden
4
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions
ops-warden/workplans/ADHOC-2026-06-29.md
repo-manager 529feeac49
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
repo.work.assign_missing_identifiers 
source: repo-manager
reason: deterministic projection registration

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a058f3-8ba0-7692-a042-9a870fc3d663
2026-09-01 00:51:59 +02:00

1.7 KiB
Raw Blame History

id type title domain repo status owner topic_slug created updated state_hub_workstream_id
WARDEN-WP-ADHOC-2026-06-29 workplan Ad Hoc Tasks — 2026-06-29 infotech ops-warden finished claude custodian 2026-06-29 2026-06-29 13fa845f-852e-55ec-a2a5-2296996e0216

Ad Hoc Tasks — 2026-06-29

T01 — Joint-smoke mode for the deployed flex-auth (assist FLEX-WP-0007 T4)

id: WARDEN-WP-ADHOC-2026-06-29-T01
status: done
priority: medium
state_hub_task_id: "62540533-f4ca-5176-9237-32adbeb292ee"

flex-auth (msg ea00620b) asked ops-warden to help close FLEX-WP-0007 T4 (joint OpenBao

  • policy-gate production smoke). Their deployed runtime is reachable on CoulombCore via the flex-auth-coulombcore tunnel at 127.0.0.1:18090, but policy_gate_production_smoke.sh spawned its own local flex-auth binary — so it never exercised the deployed runtime.
  • Added FLEX_AUTH_EXTERNAL=1 mode to scripts/policy_gate_production_smoke.sh: skips the local serve/load-registry and runs the allow/deny/vault paths against the already-running deployed flex-auth, with a /healthz precheck that fails fast with a "is the flex-auth-coulombcore tunnel up?" hint (verified: clean exit 2 when down).
  • Verified the committed production_registry_snapshot.json is current (rebuilt from ~/.config/warden/inventory.yaml, diff-clean; 4 actors).
  • Answered flex-auth's three questions and handed the operator the exact CoulombCore runbook (see reply). Remaining T4 steps are operator-gated and cannot run from the workstation: mint a scoped VAULT_TOKEN (ops-warden holds no standing token by design), run the joint smoke on CoulombCore, then flip policy.enabled: true.