Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure
TypeScript
Merge remote-tracking branch 'origin/dev' into fix/issue-533-sdk-only
Alfredo Lopezee623be37020
diff --cc control-api/package-lock.jsonindex 5c1be0f11,5d430cb4d..cf4cd86cf--- a/control-api/package-lock.json+++ b/control-api/package-lock.json@@@ -1,12 -1,12 +1,12 @@@{"name": "clerum-control-api",- "version": "0.1.544",- "version": "0.1.524",++ "version": "0.1.545","lockfileVersion": 3,"requires": true,"packages": {"": {"name": "clerum-control-api",- "version": "0.1.544",- "version": "0.1.524",++ "version": "0.1.545","dependencies": {"@clerum/display-field": "file:../packages/display-field","@clerum/image-policy": "file:../packages/image-policy",diff --cc control-api/package.jsonindex f29d153cb,fa90332bd..de15299f8--- a/control-api/package.json+++ b/control-api/package.json@@@ -1,6 -1,6 +1,6 @@@{"name": "clerum-control-api",- "version": "0.1.544",- "version": "0.1.524",++ "version": "0.1.545","description": "Internal Clerum control plane REST API + UI for managing CRDs and secrets","main": "dist/main.js","engines": {diff --cc docs/testing/codex-subscription-validation.mdindex f414205de,f414205de..312ab128b--- a/docs/testing/codex-subscription-validation.md+++ b/docs/testing/codex-subscription-validation.md@@@ -40,3 -40,3 +40,104 @@@ npm test -- --run integration/codex-subLive upstream is the Playwright connection lane (`codex-subscription-connection.spec.ts`)against a signed-in Control UI. There is no standalone`e2e-codex-subscription-real-upstream.sh` script.++++## Plugin Workload SDK Desktop lanes++++Three Desktop/Electron journeys exercise `codex-subscription` through the++Plugin Workload SDK. Each has its own spec and its own Make target, because++their preconditions are mutually exclusive. None of them starts Minikube or++creates grants — the T2/T3 profile lane must have provisioned those already.++++### Happy path++++```bash++E2E_PLUGIN_SDK_WRITE_CONFIRM=1 \++E2E_PLUGIN_SDK_EXPECT_PROVIDER=codex-subscription \++CONTROL_UI_BASE_URL=http://127.0.0.1:<random-control-ui-port> \++CONTROL_API_BASE_URL=http://127.0.0.1:<random-control-api-port> \++EXTERNAL_REST_API_BASE_URL=http://127.0.0.1:<random-external-rest-port> \++RPC_PROXY_BASE_URL=http://127.0.0.1:<random-rpc-port> \++KUBECONTEXT=<branch-profile-context> \++make test-e2e-plugin-workload-sdk-desktop++```++++`E2E_PLUGIN_SDK_EXPECT_PROVIDER` is **mandatory and has no default**. It++declares which provider the run is meant to exercise, and the precondition++asserts the live recipe declares exactly that one. Without it the spec used to++accept `openai`, `claude` or `codex-subscription` and skip its Codex assertions++when the recipe was not Codex — so a run against the OpenAI recipe that++`seed-e2e-data.sh` provisions by default went green while proving nothing about++Codex. Declare the provider you intend to evidence; a mismatch now fails the++precondition instead of quietly narrowing the run.++++### No-grant guard lane++++`plugin-workload-sdk-no-grant-guard.spec.ts` is the regression test for the++symptom of issue #533: a Codex recipe whose execution binding is missing must++report `awaiting_policy`, never `validated`. It is mutually exclusive with the++happy path — that one requires the recipe to reach `validated`, this one++requires it not to.++++```bash++E2E_PLUGIN_SDK_WRITE_CONFIRM=1 \++E2E_PLUGIN_SDK_NO_GRANT_RECIPE_NAME=<codex-recipe-without-binding> \++E2E_PLUGIN_SDK_NO_GRANT_APP_TITLE=<its-app-title> \++CONTROL_UI_BASE_URL=http://127.0.0.1:<random-control-ui-port> \++CONTROL_API_BASE_URL=http://127.0.0.1:<random-control-api-port> \++EXTERNAL_REST_API_BASE_URL=http://127.0.0.1:<random-external-rest-port> \++RPC_PROXY_BASE_URL=http://127.0.0.1:<random-rpc-port> \++KUBECONTEXT=<branch-profile-context> \++make test-e2e-plugin-workload-sdk-desktop-no-grant++```++++Both variables above are **mandatory**: the spec has no default recipe and fails++loudly when either is missing, and it refuses to run against the happy path's++recipe even if pointed at it. `E2E_PLUGIN_SDK_NO_GRANT_RECIPE_NAMESPACE` is the++one optional knob and defaults to `sandbox-recipes` — set it explicitly when the++ungranted fixture lives elsewhere, or the lane will look for the right recipe++name in the wrong namespace. This target takes no++`E2E_PLUGIN_SDK_EXPECT_PROVIDER`: no provider is supposed to be reached, so++there is none to declare. **Provisioning a Codex recipe with no execution++binding is operator work** — the lane will not create one, and a lane that++cannot find its fixture fails rather than skipping.++++### Codex fallback lane++++`plugin-workload-sdk-codex-fallback.spec.ts` closes acceptance criterion 8 of++issue #533: a real journey where an eligible Codex failure reaches the++authorized non-Codex fallback. It runs against the **granted** happy-path++recipe, because the fallback needs a working ordered target list.++++```bash++E2E_PLUGIN_SDK_WRITE_CONFIRM=1 \++E2E_PLUGIN_SDK_EXPECT_PROVIDER=codex-subscription \++CONTROL_UI_BASE_URL=http://127.0.0.1:<random-control-ui-port> \++CONTROL_API_BASE_URL=http://127.0.0.1:<random-control-api-port> \++EXTERNAL_REST_API_BASE_URL=http://127.0.0.1:<random-external-rest-port> \++RPC_PROXY_BASE_URL=http://127.0.0.1:<random-rpc-port> \++KUBECONTEXT=<branch-profile-context> \++make test-e2e-plugin-workload-sdk-desktop-codex-fallback++```++++**This lane mutates cluster state.** It scales `control-plane/codex-llm-proxy`++to zero replicas so the primary target fails with a class the failover engine++accepts, then restores it to one. The restore runs twice — in the spec's++`finally` and again in a Make-level `EXIT` trap — and both report loudly on++failure. If you ever see `[E2E-GUARD] FAILED to restore++control-plane/codex-llm-proxy`, restore it before running any other lane on++that profile: every Codex journey after it would fail for the wrong reason.++++`E2E_PLUGIN_SDK_EXPECT_PROVIDER` must be exactly `codex-subscription`; the++target rejects any other value, because a non-Codex primary would make the++journey vacuous. The recipe knobs are shared with the happy path and carry++**silent defaults** — `E2E_PLUGIN_SDK_RECIPE_NAME` defaults to++`evenfire-prompt-notify-app`, `E2E_PLUGIN_SDK_RECIPE_NAMESPACE` to++`sandbox-recipes`, and `E2E_PLUGIN_SDK_APP_TITLE` to `Prompt & Notify`. Set++them explicitly whenever your fixture differs, or the lane looks for the wrong++app in the Desktop catalog and fails at the card locator rather than at a++precondition.++++The grant must expose **at least two ordered prompt targets**, Codex first and++a non-Codex provider second. The spec asserts that before injecting the fault:++a single-target grant would let the journey pass while proving nothing, so it++fails as a precondition instead.