Preserve remote template build configuration

[leaanthony]

Summary

• Preserve a remote template's build/config.yml during wails3 init instead of overwriting it with the default build assets.
• Support remote templates that provide build/config.yaml by copying it to the CLI's canonical build/config.yml path.
• Warn users on the CLI that copied remote configuration should be reviewed.
• Reject symbolic-link configuration files and add focused tests.

Root cause

wails3 init extracted the remote template and then regenerated build assets, which replaced the template's build/config.yml and discarded template-specific development settings such as frontend watch exclusions.

Closes #5065

Validation

• CGO_ENABLED=0 GOCACHE=/tmp/wails-go-cache go test ./internal/commands
• GOCACHE=/tmp/wails-go-cache go test ./internal/templates
• git diff --check

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8137ffd5-3a4f-490e-b93d-dc8f102d18ab

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}