Repository navigation
GA 2/11 · control-plane security + cost fixes (Helm JWT/LANTERN_ENV, scope escalation, startup guards, metering, caching, idempotency) - #277
Conversation
… to production; add values-prod
…; fail closed on Slack signing, Twilio auth off, claude-code in prod
…thropic streaming system prompts, per-request LLM idempotency keys
…x workflowEngine env nil in helm values; gofmt
🔎 Codex cross-audit (agent:audit)Blocking Findings
Other Finding
I did not run the full test suite; this was a diff audit only. |
🛡️ Vuln scan — ❌ vulnerable dependency found |
|
🔒 Reviewer verdict: BLOCKING — Security-hardening and metering fixes look correct, but the new values.yaml LANTERN_ENV=production default breaks the documented Kind dev deploy (values-dev.yaml wasn't updated to opt out), crash-looping control-plane/workflow-engine on missing prod secrets. |
🔷 Gemini cross-audit (agent:audit-gemini)Summary of Audit Findings for
|
…class inputs values.yaml defaults LANTERN_ENV=production (secure by default), and Helm merges maps, so values-dev.yaml inherited it and the kind control-plane and workflow-engine fataled on prod-only guards (scheduler addr, gRPC TLS, prod secrets). The dev overlay now sets LANTERN_ENV=development for both. Staging/prod are prod-class but the chart had no way to pass the scheduler address or TLS material the guards require. The control-plane deployment gains extraEnv/extraVolumeMounts/extraVolumes, and values-staging/prod document the required inputs with a commented example.
🛡️ Vuln scan — ❌ vulnerable dependency found |
Part 2 of 11 of the GA next-gen stack (supersedes #255–#275). History rewritten (range-limited, master untouched) to drop a 43 MB build binary committed by mistake; part 11 fixes every confirmed Codex cross-audit finding. Base:
ga3/01-scheduler-modelrouter. Merge in order with a merge commit (not squash).Context, verification and needs-human list: #254 and
docs/roadmap/2026-10-nextgen-sandbox-and-harness.md.Commits in this part: