ci: existing Webpack workflow requires an undeclared interactive webpack-cli install #4

Observed failure

While validating the optional cross-platform gcloud-doctor integration in PR #3, the existing NodeJS with Webpack workflow failed independently of the diagnostic test matrix.

Run: https://github.com/Dimkox/gitmir-codex-control/actions/runs/34519399153
Failing Node 22 job: https://github.com/Dimkox/gitmir-codex-control/actions/runs/34519399153/job/103012834423

The Build step executes npm install followed by npx webpack. The log reports an implicit install of webpack, then requests installation of webpack-cli with a yes/no prompt and terminates with exit code 1. The diagnostic workflow for the same first feature commit passed all six Windows/macOS/Linux × Node 22.18.0/24.x jobs.

Existing configuration

.github/workflows/webpack.yml already contains these commands on the base master commit 12f9588e26771f6e873eb774fa32d95a63bd694b; it is unchanged in PR #3. The package has no webpack dependency and runs the dashboard directly with node server.ts. Its declared Node minimum is 22.18.0, whereas this workflow includes Node 18.x and 20.x.

This issue documents the observed run and the pre-existing configuration mismatch; it does not claim that a separate baseline run was executed in this investigation.

Proposed scope

Replace the generic Webpack template with checks that match the repository's actual execution model and supported Node versions. Do not add an unused bundler simply to satisfy the template. Confirm the full repository typecheck and dashboard smoke test before selecting the replacement commands.

Verify

1. The general repository CI uses supported Node versions and completes without interactive package installation.
2. The existing typecheck and an actual dashboard startup check execute successfully, or any existing defects are separately reproduced and reported rather than hidden.
3. npm run test:gcloud-doctor remains green on Windows, macOS and Linux.
4. No runtime dependency, cloud credential or secret is introduced solely for CI.

The unrelated workflow was intentionally not changed in the Google Cloud feature PR.