Let repo init use the target server default environment

[brynary]

Summary

• stop pinning the generated hello workflow to the local sandbox provider
• let environment resolution fall through to the target server default
• update the repo init integration snapshot for the minimal workflow config

This prevents a freshly initialized project from failing when the selected remote server disables the local provider and supplies a remote default environment.

Testing

• cargo nextest run -p fabro-cli --test it repo_init
• cargo +nightly-2026-04-14 fmt --check --all
• cargo +nightly-2026-04-14 clippy --workspace --all-targets -- -D warnings
• cargo insta pending-snapshots
• git diff --check

[Copilot]

Pull request overview

Adjusts fabro repo init so the generated “hello” workflow does not force the local environment, allowing environment selection to fall through to the target server’s configured default (avoiding failures when local is disabled on a remote server).

Changes:

• Stop generating [run.environment] / [environments.local] blocks in the default hello workflow’s workflow.toml.
• Update the repo-init integration test snapshot to match the minimal workflow config.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
lib/crates/fabro-cli/tests/it/cmd/repo_init.rs	Updates the workflow.toml snapshot to remove the pinned local environment config.
lib/crates/fabro-cli/src/commands/repo/init.rs	Generates a minimal workflow.toml that leaves environment resolution to defaults (e.g., server default).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.