fix(setup): prevent guided setup exit in default directory

[ToddHebebrand]

Summary

• return success when Compose project-name preservation intentionally skips the default breeze directory
• add a regression guard that exercises the real guided-setup function from a directory named breeze
• run the new guard alongside the existing guided-setup CI check

Root cause

preserve_existing_compose_project_name used a bare return after a false [[ ... ]] condition. For the normal installation directory named breeze, that inherited exit status 1. Because main invokes the function under set -e, guided setup terminated silently immediately after preparing .env.

User impact

Guided setup now continues normally when run from the documented/default breeze directory, regardless of whether the user chooses to back up an existing .env.

Validation

• bash -n scripts/guided-setup.sh scripts/check-guided-setup-compose-rewrites.sh scripts/check-guided-setup-default-project.sh
• shellcheck scripts/guided-setup.sh scripts/check-guided-setup-compose-rewrites.sh scripts/check-guided-setup-default-project.sh
• bash scripts/check-guided-setup-compose-rewrites.sh
• bash scripts/check-guided-setup-default-project.sh
• actionlint -shellcheck= .github/workflows/ci.yml
• git diff --check origin/main...HEAD

[cloudflare-workers-and-pages]

Deploying breeze with    Cloudflare Pages

Latest commit:	1c882fc
Status:	✅  Deploy successful!
Preview URL:	https://d2edad28.breeze-9te.pages.dev
Branch Preview URL:	https://fix-guided-setup-default-dir.breeze-9te.pages.dev

View logs