fix: respect dry-run during project setup

[penalosa]

Summary

• Pass --dry-run to framework autoconfig and accepted Wrangler config conversion for cf deploy, cf workers versions create, and cf workers triggers deploy.
• When setup would be needed, report planned changes and stop before building or uploading.
• Check that existing project files remain unchanged in the dry-run regression test.

Setup paths

1. prepareProject detects whether cf is already configured. If it is, no setup runs.
2. Otherwise, if a Wrangler config exists, cf offers to convert it with the cf migrate codemod. maybeMigrateWranglerProject returns true only after the user accepts and that conversion command completes, including in dry-run mode.
3. If the conversion did not run, configureProject calls framework autoconfig to set up the detected project.
4. In a dry run, either selected setup path returns setupNeeded. The build stops because those setup changes were not applied. For an already configured project, the build still runs and deploy-helpers performs its upload or trigger dry run. --prebuilt skips project preparation and the build.

Validation

• pnpm check
• pnpm test src/__tests__/lib/autoconfig-migration.test.ts src/__tests__/commands/migrate.test.ts src/__tests__/commands/deploy/index.test.ts src/__tests__/commands/triggers-deploy.test.ts (72 passed)
• pnpm test src/__tests__/commands/deploy/index.test.ts src/__tests__/commands/triggers-deploy.test.ts src/__tests__/commands/versions-upload.test.ts (68 passed)

Scope

Configured projects still run their build during a deploy dry run, so build output may change. cf build has no dry-run flag and retains its existing setup behavior.

Related to #112.

[pkg-pr-new]

npm i https://pkg.pr.new/cf@166

commit: e551802

[ask-bonk]

LGTM

github run

[github-actions]

cf --help startup

	mean	stddev	min	max
PR	326.6 ms	3.9 ms	320.0 ms	335.3 ms
base	382.6 ms	4.9 ms	376.5 ms	396.5 ms

Δ (PR vs base): ↓ -55.9 ms (-14.6%)

Measured with hyperfine on ubuntu-latest (3 warmup runs, 20 timed runs). CI numbers carry ±a few ms of runner jitter; treat small deltas as noise.

[ask-bonk]

LGTM

github run

[ask-bonk]

LGTM

github run

[ask-bonk]

LGTM

github run

[petebacondarwin]

I feel like I am being dumb here and not really understanding the stages of autoconfig and migration (and the difference between the two). So I am marking this review as inconclusive as I don't feel I can make a positive or negative call without more knowledge.

[ask-bonk]

LGTM

github run

[petebacondarwin]

OK I think this is a bit clearer 😄