[alexandre-vl]

Summary

• The beta gave the engine it starts production's edge, sign-in client and callback port, whatever the environment said.
  • Take ZERON_EDGE_URL (and ZERON_WORKOS_CLIENT_ID, ZERON_CALLBACK_PORT) naming a self-hosted edge, as zeron itself reads them in crates/cli/src/env.rs.
  • An engine the app started on ~/.zeron loaded the session zeron login had kept there for that edge and handed it to production.
  • Production turned it down, and the engine signed out, deleting session.json.
  • So Zeron 0.3.0 signed a self-hosting user out each time it started the engine.
• The beta now reads the engine's own variables the way env.rs does: production's, unless they name another edge, client or port. An edge alone keeps production's client and port. Zeron.app's engine is started with those.
• Unchanged:
  • Nothing of staging's is built in.
  • The development variables (ZERON_ZGX_*) still reach nothing in the beta.
  • The manager still refuses an engine whose edge isn't the one the environment names.
• auth::production() is now #[cfg(test)]: it has no non-test callers left.
• Worth a close look: the beta now takes its edge from the process environment. That's the same trust zeron and the engine already place in these variables. The engine-side change, a session used only by the edge that issued it, is engine: a saved session is used only by the edge and client that issued it #1390.

Test plan

• cargo test --locked --features beta --bin zeron-zgx -- endpoint_tests engine::manager::tests (apps/zgx) on Linux:
  • New: a_beta_build_is_production_unless_the_engines_variables_say and a_beta_build_starts_the_engine_against_the_edge_zeron_s_variables_name. Both pass, and both fail with the beta's endpoint_with put back to production().
  • Existing: a_beta_build_manages_zeron_app_s_engine fails on Linux both before and after this change (manager.rs:482). It writes macOS's engine name, Zeron Engine, beside the executable, while Linux looks for zeron-engine. CI runs apps/zgx's tests without beta, so it never runs there.
• The same tests as a development build (no beta): 5 passed.
• cargo clippy --locked --all-targets, with and without beta: no warnings in the files touched.
• Not done: a packaged beta run end to end against a self-hosted edge.

[alexandre-vl]

The red checks come from zeron/zgx and GitHub's macOS runners, not this change.

• zgx / zgx-linux: plugins::official::tests::zeron_v2_is_in_step_with_the_default has failed since c153906 changed apps/zgx/ui/screens/panel/init.luau but not Zeron v2's copy. zgx: Zeron v2's panel gets the active-tab wash fix, so the v2 staleness test passes #1382 brings v2 in step. Other PRs into zeron/zgx fail it the same way, e.g. Plugins: a plugin's service gets zeron.db, the same file its windows open #1380 and Plugins: a service measures text as its window's canvas does #1367. The other 661 apps/zgx unit tests passed, this change's own included, and so did all 1358 Luau UI tests.
• zgx / zgx-macos has no result. The hosted runner lost communication with the server during apps/zgx unit tests, as the same job's runner did on Plugins: a plugin's service gets zeron.db, the same file its windows open #1380 and CI for zeron/zgx: integration branch, zgx suite on plan and admission, faster betas #1357. On engine: a saved session is used only by the edge and client that issued it #1390 and Linux: the engine an app starts outlives the app's systemd unit #1391, the same job on the same base fails zeron_v2_is_in_step_with_the_default and tests that need zgx's shader fill pipeline, which Metal fails to compile on the macos-26-arm64 runner image.
• CI runs apps/zgx's tests without the beta feature, so the beta tests this change adds and updates don't run there. The test plan lists how they ran.