cf deploy --dry-run (and cf build) runs autoconfig and rewrites package.json/tsconfig.json on an already-configured Astro project (1.0.0-beta.5)

Finding: In one external report, cf 1.0.0-beta.5 run as a project devDependency via npx on an already-configured Astro project (astro 7.3.5, @astrojs/cloudflare 14.3.3, wrangler 4.142.0, npm, Linux) runs autoconfiguration during `cf deploy --dry-run` and modifies tracked files, even though the build then fails [https://github.com/cloudflare/workers-sdk/issues/16123]. Reported conditions: the project already has a wrangler.jsonc, the Astro Cloudflare adapter installed, and cf in devDependencies. The reporter started from a fresh clone, ran npm ci with a clean git status, then ran the dry run. The output listed detected Astro settings, planned installation of cf as a devDependency, a planned package.json script update, and an `astro add cloudflare` step. The build then failed with a Build Output Specification error about a missing root config under .cloudflare/output/v0. The reporter attributes this error to a separate issue, cloudflare/cf#18, which is not among the supplied sources [https://github.com/cloudflare/workers-sdk/issues/16123]. Reported file changes afterwards: package-lock.json (roughly 5,000 lines), package.json, tsconfig.json modified, and public/.assetsignore created. In package.json, the existing deploy script (astro build && wrangler deploy) was reportedly replaced with `cf deploy`, a generate-types script was added, and wrangler was bumped from ^4.142.0 to ^4.144.0. In tsconfig.json, an include entry for worker-configuration.d.ts was added and the file reformatted, although that file was intentionally absent from the project. The reporter says the .assetsignore content looks like Pages artifacts. The reporter says `cf build` behaves the same way [https://github.com/cloudflare/workers-sdk/issues/16123]. Expected behavior per the reporter: a dry run should never write to the working tree, autoconfig should be skipped or confirmed when a Wrangler config and adapter already exist, and existing scripts should not be overwritten [https://github.com/cloudflare/workers-sdk/issues/16123]. Status: no maintainer response, confirmed cause, fix commit, or released fix appears in the supplied content, so cause and fix status are UNKNOWN. This is an external report only; KFA did not reproduce it. Diagnostic implication, as a hypothesis only: on projects with tracked config files, check git status after running these commands before committing.