Add temp-local-stack option to the debug environment switcher

[IliaMManolov]

What

Adds a temp-local-stack option to Developer > Switch Environment that points the app at the Railway-hosted instance of the offline local stack (local-stack-backend in the edison-watch project's demo environment, https://local-stack-backend-demo.up.railway.app), so devs can test against the shared offline stack without running docker locally.

Companion to Edison-Watch/shared#18, which defines the TEMP_LOCAL_STACK_CONFIG URLs this option resolves to; this PR needs a shared package version containing that change.

Changes

• "temp-local-stack" added to DEBUG_ENV_NAMES; the menu radio item, env:changed renderer reload, MCP re-apply, and URL resolution all come from the existing generic code.
• The two hardcoded env-name checks (getBuildDefaultEnv, getDebugEnvOverride) are replaced with an isDebugEnvName() guard derived from DEBUG_ENV_NAMES, so future env additions are one-line.
• Menu label reads temp-local-stack (railway offline).
• No renderer changes needed: useAuth's env sync only special-cases dev, so the new name flows through to localStorage and the shared CONFIGS lookup.

Notes

• MCP base URL is empty for this env until the FastMCP port (3000) gets a public Railway domain; server status will show offline and MCP client configs are not rewritten when switched to it. Auth and dashboard work.
• Sign-in: local GoTrue signup is open, so any email/password works; the seeded admin@local adopts the owner row.

Verified

npm run typecheck (node + web) passes with the rebuilt shared package. The auth path was smoke-tested end-to-end against the live Railway instance (signup, password grant, get-api-key).

🤖 Generated with Claude Code

---

Summary by cubic

Adds a new temp-local-stack option to Developer > Switch Environment so devs can point the app at the shared Railway offline stack without running Docker. Also fixes a GitHub Releases race by pre-creating a draft release and publishing only after assets upload, making releases reliable.

• New Features

  • Added temp-local-stack to DEBUG_ENV_NAMES with menu label "temp-local-stack (railway offline)".
  • Replaced hardcoded env checks with isDebugEnvName() derived from DEBUG_ENV_NAMES.
  • Resolves URLs via shared TEMP_LOCAL_STACK_CONFIG (requires updated shared package).

• Bug Fixes

  • Prevented electron-builder release race by pre-creating a draft in release.yml and release-demo.yml.
  • Uploads assets into the draft, then publishes (demo always; release only when publish=true) to ensure beta.yml/latest.yml are present and avoid partial releases.

^{Written for commit fb917af. Summary will update on new commits.}

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[cubic-dev-ai]

1 issue found across 4 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/main/infra/setupConfig.ts">

<violation number="1" location="src/main/infra/setupConfig.ts:27">
P1: Selecting `temp-local-stack` can persist the new env without actually resolving its Railway URLs, because the locked `@edison-watch/shared@0.1.0` does not contain that config. Updating the shared package/lockfile with the companion config keeps the new menu option from silently pointing at the previous environment.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P1: Selecting temp-local-stack can persist the new env without actually resolving its Railway URLs, because the locked @edison-watch/shared@0.1.0 does not contain that config. Updating the shared package/lockfile with the companion config keeps the new menu option from silently pointing at the previous environment.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/main/infra/setupConfig.ts, line 27:

<comment>Selecting `temp-local-stack` can persist the new env without actually resolving its Railway URLs, because the locked `@edison-watch/shared@0.1.0` does not contain that config. Updating the shared package/lockfile with the companion config keeps the new menu option from silently pointing at the previous environment.</comment>

<file context>
@@ -22,15 +22,21 @@ if (DRY_RUN) console.log("[dry-run] Dry-run mode enabled - config files will not
-export const DEBUG_ENV_NAMES = ["demo", "release", "dev"] as const;
+// "temp-local-stack" = Railway-hosted offline stack (local-stack-backend in the
+// edison-watch demo project); URLs come from the shared TEMP_LOCAL_STACK_CONFIG.
+export const DEBUG_ENV_NAMES = ["demo", "release", "dev", "temp-local-stack"] as const;
 export type DebugEnvName = (typeof DEBUG_ENV_NAMES)[number];
 
</file context>