fix(runtime): treat null env as run mismatch

[roodboi]

Summary

• treat a stored base env (null) as a mismatch when hack run --env ... targets a different overlay
• keep --no-deps disabled unless the live stack env matches the requested env
• add a regression test for base-vs-overlay run behavior

Verification

• bun test tests/project-run-command.test.ts
• bun run typecheck
• bun x ultracite check src/commands/project.ts tests/project-run-command.test.ts

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3a0dd44

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3a0dd44e80

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Compare runtime env against effective run env

The new mismatch check treats any stored non-null runtime env as incompatible when --env is omitted, because handleRun passes requestedEnvName as envName ?? null and resolveComposeEnvOverrides can still select a non-base default overlay. In that common env.defaultOverlay case, this condition makes hack run stop using --no-deps even when the live stack env actually matches the effective env, causing unnecessary dependency startup on every run.

Useful? React with 👍 / 👎.