Bilal Godil 1ede37281f Don't ship env-var conflict-throw in generated customer SDK ... The generated env.ts getters ship inside @hexclave/stack / @hexclave/react and are read on a hot, side-effect-free path by SDK consumers. The conflict-detection helper added with the HEXCLAVE_* rename made those getters throw when both a HEXCLAVE_* and STACK_* spelling were set to different values — a breaking change to env-var reading for SDK users. Revert the generated getters to a plain || dual-read chain (prefer HEXCLAVE_*, fall back to legacy STACK_*, empty-as-unset), with no throw. Conflict detection stays in our own non-shipped infra only (packages/shared getEnvVariable/ getProcessEnv, dashboard inline env, CLI auth, docker entrypoint). Order-preserving dedup of the candidate list is kept so HEXCLAVE_API_URL no longer emits its STACK_URL aliases twice.		2026-06-16 17:56:47 -07:00
..
generate-env.ts	Don't ship env-var conflict-throw in generated customer SDK	2026-06-16 17:56:47 -07:00
merge-quetzal-translations.ts	feat(hexclave): PR 3 — native @hexclave/* source rename + delete dual-publish wiring (#1482)	2026-05-29 15:21:59 -07:00
process-css.ts	feat(hexclave): PR 3 — native @hexclave/* source rename + delete dual-publish wiring (#1482)	2026-05-29 15:21:59 -07:00