Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@v3/internal/commands/build_assets/Taskfile.tmpl.yml`:
- Around line 28-39: The install:frontend:deps:bun task only lists bun.lockb as
a source, so dependency changes in Bun's text lockfile (bun.lock) won't
retrigger installs; update the Taskfile.tmpl.yml task named
install:frontend:deps:bun to include both "bun.lock" and "bun.lockb" in the
sources array (in addition to package.json) so the freshness detection watches
either lockfile and re-runs bun install when either changes.
- Around line 54-65: The task install:frontend:deps:yarn currently lists
generates: node_modules which fails with Yarn PnP; update the task to remove or
replace generates and add a status check that succeeds if either the PnP runtime
file exists or node_modules exists (e.g. a shell status like "sh: test -f
.pnp.cjs || test -f .pnp.js || test -d node_modules") so Taskfile freshness is
correct for both Yarn v2+ PnP and classic linkers; keep the existing dir,
sources and cmds and only change the generates -> status portion in the
install:frontend:deps:yarn task.

In `@v3/internal/templates/_common/Taskfile.tmpl.yml`:
- Line 4: Replace the hardcoded APP_NAME value ("wails3app") with the template
variable that injects the generated project name so downstream tasks (wails3
update build-assets, server binary naming, and Docker tag defaults) use the
actual project name; update the APP_NAME entry in Taskfile.tmpl to reference the
project-name template placeholder used elsewhere (the same placeholder used for
binary/Docker naming) so generated projects get their correct name.

---

Nitpick comments:
In `@v3/internal/commands/build_assets/Taskfile.tmpl.yml`:
- Around line 12-13: Validate PACKAGE_MANAGER in the Taskfile template by adding
requires.vars.enum entries for the tasks that dynamically use it (the task
entries that call install:frontend:deps:{{.PACKAGE_MANAGER}},
frontend:run:{{.PACKAGE_MANAGER}} and dev:frontend:{{.PACKAGE_MANAGER}}) so
unsupported values fail fast; update the Taskfile.tmpl.yml task definitions
around the dynamic dispatch points to include requires.vars.enum with the
allowed string options (e.g., "npm", "yarn", "pnpm") and apply the same guard
for the other occurrences referenced (lines around the install:frontend:deps,
frontend:run and dev:frontend dispatchers).

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@v3/internal/commands/build_assets/Taskfile.tmpl.yml`:
- Line 326: The log line contains a duplicated echo token ("echo echo \"Building
for device: UDID={{.Opn}}.UDID{{.Cls}} SCHEME={{.Opn}}.SCHEME{{.Cls}}
PROJECT={{.Opn}}.PROJECT{{.Cls}}\""); remove the extra leading "echo" so the
command is a single echo that prints the template string—locate the template
line containing the duplicated echo and edit it to use one echo while keeping
the {{.Opn}} and {{.Cls}} placeholders intact.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@v3/internal/commands/build_assets/Taskfile.tmpl.yml`:
- Around line 12-13: The task dispatchers in Taskfile.tmpl.yml use
{{.PACKAGE_MANAGER}} without a fallback, causing unresolved task names for
projects whose root Taskfile doesn't define PACKAGE_MANAGER; update each
dispatcher occurrence (e.g., the dispatch strings used by
install:frontend:deps:{{.Opn}}.PACKAGE_MANAGER{{.Cls}},
frontend:run:{{.Opn}}.PACKAGE_MANAGER{{.Cls}}, and
frontend:dev:{{.Opn}}.PACKAGE_MANAGER{{.Cls}}) to include an inline default
fallback (| default "npm") so the generated dispatch becomes
install:frontend:deps:{{.Opn}}.PACKAGE_MANAGER | default "npm"{{.Cls}} (and
similarly for the other two dispatchers) to preserve backward compatibility.