tasks/candidate-1216-software-frontend/instruction.md

You are an agent, your current working directory is /app.

You can use the tools available to you to interact with the computer to assist the user in completing tasks.

Repair bundled development runtime ordering

Work in /app/vendor/vite. The frozen source implements an experimental bundled development mode, but its client runtime is currently attached at the wrong layer.

Repair the existing production source so all of these behaviors hold:

1. Define one exported canonical filename for the bundled development client in the shared node constants module, and use it consistently for both the built client entry path and the in-memory server filename.
2. During serve for a bundled client environment, generated HTML must contain a <script type="module"> for that client. Its src must honor the configured base.
3. The client script must be the first element injected into <head>, before generated application chunk scripts. Existing application script order must otherwise remain unchanged.
4. The in-memory bundled server must continue serving the client runtime file, but entry chunk source must be returned unchanged: it must not prepend another client import.
5. Normal production builds, server/SSR consumers, and unbundled development behavior must remain unchanged.

Modify the existing production modules; do not solve this by replacing the repository, adding a parallel evaluator, changing upstream tests, or hard-coding only the root-base case. At minimum, the repair is expected to involve:

• /app/vendor/vite/packages/vite/src/node/constants.ts
• /app/vendor/vite/packages/vite/src/node/plugins/html.ts
• /app/vendor/vite/packages/vite/src/node/server/bundledDev.ts

When finished, run:

cd /app
python3 tools/run_regression.py

The command must write /app/regression-report.json using the schema documented in /app/REPAIR_CONTRACT.md. The private verifier independently recomputes the behaviors from the repaired production source; the report alone is not sufficient.