p2-11-nuxt

Public GitHub evidence ↗

# p2-11-nuxt — Batch 4 result: RED (stopped early at upgrade)

Source: bogdan0083/nuxt3-realworld-app @ 67ae3c71454ab544d975fe4283cb27e15ea50e34 (Nuxt 3.4.21).
Owned fork: https://github.com/j4groupfounders/j4-p2d-nuxt
Framework: Nuxt 3.4.21 -> 3.21.11 (latest stable 3.x; Nuxt 4 was available but a major-version frontend migration was judged out of scope for this hop).
Preregistration: harness commit 7f235c8 (before any upgrade branch existed).
Baseline: https://github.com/j4groupfounders/j4-p2d-nuxt/actions/runs/37579062385 — 21/21 project tests (vitest, `tests/integration` + `tests/unit`), no skips; boots and `/`, `/login`, `/register` match the frozen surface.

## Outcome
**RED** — criterion 1 (project tests) failed on the upgrade branch: 13/21 tests failed after bumping to Nuxt 3.21.11. Framework boot/build itself succeeded (`nuxt build` is clean); the failures are entirely in the project's own integration tests, which mount the whole app via `@nuxt/test-utils`'s `mountSuspended()` against MSW-mocked endpoints. Representative failures: components mount with empty content (`Cannot call text on an empty DOMWrapper`), API-mocked lists render 0 items instead of the fixture count, and route-guard assertions return the wrong path. This is consistent with a `@nuxt/test-utils` major-version incompatibility (the project pinned 3.12.0, which predates Nuxt 3.21's internal `@nuxt/vite-builder` API; bumping test-utils to 4.3.3 then required cascading bumps to `vitest` 1.4->5.x and `happy-dom`, each of which surfaced a new peer/runtime error), not an application-logic regression from the Nuxt version bump itself.
6 CI runs total (2 baseline, 4 upgrade attempts); **5.38 actual job-minutes**. No paid services/model API calls, no upstream contact, no human edits to application or test logic — only devDependency version bumps (`@nuxt/test-utils`, `vitest`, `happy-dom`) made to chase the test harness compatibility, all itemised here and left in place on the (red) upgrade branch for Batch 5 to pick up or revert.
Seeded-fault stage (criterion 4) was not reached: the project's own-test gate must pass first per PROTOCOL.md criterion 1.

## Batch 5 handoff
- Treat this as a devtooling-upgrade problem, not a Nuxt-runtime problem: the app itself builds and presumably serves fine on 3.21.11 (confirmed boot-level only, not characterized against fixtures since tests never went green).
- Next step: read `@nuxt/test-utils` v4's migration guide for `mountSuspended`/environment-registration changes rather than chasing further peer-version bumps blind; consider pinning `@nuxt/test-utils` to the newest 3.x line (last version supporting the old mounting API) paired with Nuxt 3.21, instead of jumping to test-utils 4.x.
- Seeded fault list (not yet exercised): `j4_mutations.json` in this directory — login/register heading and link-text mutations, index "Your feed" label.