Skip to content

Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure

TypeScript

docs(minikube): require consent for recertification

Alfredo Lopez24f081931ff5
diff --git a/.cursor/skills/minikube-t0-t1-t2/SKILL.md b/.cursor/skills/minikube-t0-t1-t2/SKILL.md
index 976e42a6b..79f2ce73f 100644
--- a/.cursor/skills/minikube-t0-t1-t2/SKILL.md
+++ b/.cursor/skills/minikube-t0-t1-t2/SKILL.md
@@ -56,6 +56,18 @@ Before running anything, verify ALL of these:
`pre-gate-sync` can restart every deployment; T2 then renews the hold
once, before Health/Playwright, and records `PortForwards=` evidence.
Without it an in-run sync leaves the hold on terminated pods.
+- [ ] When the same owned profile is reused after a HEAD change, the
+ orchestrator runs `pre-gate-sync` for a targeted change and refreshes
+ forwards after any restarted services. For `targeted-sync`, also supply
+ a bounded `T2_HEALTHCHECK_COMMAND` that exercises the affected
+ user-facing path.
+- [ ] Before a login-based health journey patches HCC or creates fault
+ fixtures, resolve its seeded test credential in-process. Source
+ `scripts/e2e/load-dotenv.sh` and `scripts/e2e/admin-credentials.sh`;
+ use `dotenv_load_canonical_root` and `e2e_resolve_admin_password`.
+ An explicit `E2E_USER_PASSWORD` may override the journey credential.
+ Never inspect, print, log, or persist `.env` contents, even for a
+ key-presence check. Fail before cluster mutation if resolution fails.
Shell contract-test rule: fixtures that exercise Git/lease state must use a
temporary repository via `scripts/tests/lib/minikube-fixture-repo.sh`. Keep the
@@ -113,6 +125,12 @@ Rules that override any shortcut idea:
- Never set `T2_RUN_T0=false` / `T2_RUN_T1=false` by hand to skip a lane that
was not certified on this HEAD; the harness refuses it unless the plan is
`already-synced`, and evidence must show the earlier green runs.
+- Before repeating a completed full T0/T1/T2 certification, propose the
+ repeat with its reason and expected cost and ask the user to decide. A
+ recommendation is not consent. If the user declines after HEAD changes,
+ preserve the prior evidence but report the new HEAD as uncertified. A
+ same-HEAD `minikube-t2-runtime` retry finishes an authorized run without
+ repeating T0/T1.
## Step 3 — T1 specifics (Real PostgreSQL)
diff --git a/AGENTS.md b/AGENTS.md
index cd2c881c6..f09a3117f 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -172,6 +172,26 @@ T2 with `make minikube-t2-runtime` (`T2_RUN_T0=false T2_RUN_T1=false`). That
path is valid only when the pre-gate marker already matches HEAD
(`already-synced`). Do not set those flags to skip an uncertified lane.
+Before repeating an already completed full T0/T1/T2 certification, propose
+the repeat with its reason and expected cost, then ask the user whether to run
+it. A recommendation alone does not authorize a repeat. This choice does not
+turn an earlier HEAD's evidence into certification for a newer HEAD: if the
+user declines, report the newer HEAD as uncertified. A same-HEAD
+`minikube-t2-runtime` retry to finish an authorized run is the supported
+recovery path, not a new full recertification.
+
+For branch-owned user-facing E2E health journeys, resolve the seeded test
+credential locally before patching HCC or creates fault-injection fixtures.
+Use `scripts/e2e/load-dotenv.sh` with `dotenv_load_canonical_root` and
+`scripts/e2e/admin-credentials.sh` with `e2e_resolve_admin_password`; an
+explicit `E2E_USER_PASSWORD` may override that journey's credential. Keep the
+resolved value in process memory. Never inspect, print, log, or persist `.env`
+contents, even to test whether a key exists. Missing credentials must fail
+preflight before mutating the owned profile. Use the profile's persisted
+ports and the exact `T2_PORT_FORWARD_COMMAND` hold when `pre-gate-sync` can
+restart a service; `targeted-sync` also requires a bounded
+`T2_HEALTHCHECK_COMMAND`.
+
The active profile mutation lock is `$T2_LOCK_ROOT/<profile>.lock`; stale-lock
reclaim coordination uses the sibling directory
`$T2_LOCK_ROOT/<profile>.reclaim`. A killed reclaimer may leave that sibling