test(harness): mount hand-written wrappers into the document too, and unmount them

[IgorShevchik]

Linked issue

Closes #513.

Type of change

• Documentation (updates to the documentation or readme)
• Bug fix (a non-breaking change that fixes an issue)
• Enhancement (improving an existing functionality)
• New feature (a non-breaking change that adds functionality)
• Chore (updates to the build process or auxiliary tools and libraries)
• Revert (undoing a merged change — retitle this PR revert(Scope): ...)
• Breaking change (fix or feature that would cause existing functionality to change)

No src/ changes — test harness only.

Description

#512 attached the cases renderEach builds. The 293 hand-written mountSuspended calls across 112 files stayed detached, which is what kept the dialog family in console-gate.ts's register with nothing left to fix in it.

None of the 293 call sites is edited. Each project sets the default where it already had a seam:

project	seam
vue	its existing shim, test/utils/mount.ts
nuxt	a resolveId in vitest.config.ts pointing @vue/test-utils at the new test/utils/attach-mount.ts

A call site that wants a detached tree still can — both seams take the caller's attachTo when it gives one, and both treat an explicit undefined as "no opinion". @nuxt/test-utils/runtime is deliberately not redirected: mockNuxtImport and mockComponent are macros keyed on that specifier and would stop being transpiled. No spec imports both, which is why aliasing the Vue package rather than the Nuxt one is safe.

enableAutoUnmount(afterEach) in both setup files is the other half, and is not optional: attaching without it leaves every case's tree in document.body, and reka-ui's focus scope from an earlier case then steals the focus a later one just set. Removing that one call reddens 50 of Modal's 60 tests. componentRender no longer unmounts by hand, because one mechanism is better than two.

Two things only became reachable once trees were in the document

getComputedStyle returns a real declaration instead of an empty one, and reka-ui's usePresence keeps it in a ref, which deep-wraps it in a proxy. happy-dom's getters check their receiver, so Drawer threw TypeError: Receiver must be an instance of class CSSStyleDeclaration four times per run — uncaught, so it failed the run without failing a test. Same shape as Countdown's ref-wrapped Immediate in #512, this time in third-party code. test/utils/patchComputedStyle.ts hands the declaration back with markRaw; removing that call brings all four back.

reka-ui's hideOthers puts the trigger inside an aria-hidden region while a popup is open and leaves it focusable, which axe reports as aria-hidden-focus in Select and Table. Measured on both configurations by reading the DOM rather than through axe:

	aria-hidden on the trigger	trigger focusable	hidden ancestor
portal: false	yes	yes	—
portal: true (production)	no	yes	[data-v-app]

So the arrangement is the same either way; the rule stops firing only because axe(wrapper.element) cannot see an ancestor above its own root. The rule is disabled in those two cases with that measurement recorded beside it, and with the note that this does not mean the condition is absent. Whether it is a real defect for screen-reader users or the ordinary price of a focus-trapped popup was raised with the maintainer, who decided against an issue and against an upstream report.

What it bought, honestly

	before	after
register entries	37	25
distinct files listed	24	19
console messages	366	569
tests logging	56	44

The dialog-family group is gone entirely: every nuxt entry in it went quiet, and its vue entries remain only because the plain-Vue test router does not declare the routes those fixtures navigate to.

Message volume moved the other way, and that is not a regression being hidden: DropdownMenu and ContextMenu now really mount their menu content, so reka-ui's textValue warning fires once per item rather than once per test. Same third-party causes, more items reaching them. Both files stay registered either way, so this does not change what the gate lets through.

Review

/review plus the five-reviewer panel. Findings acted on, all in this PR:

• The gate had stopped watching before teardown ran. enableAutoUnmount(afterEach) was registered before installConsoleGate(), and vitest runs same-level afterEach hooks last-registered-first — so the gate restored console and made its check while the wrapper was still mounted. Probed with a component that warns from onUnmounted: it passed. The calls are swapped, the probe now goes red, and the suite stays green. This was a blind spot introduced by this PR's first commit.
• The reason given for disabling aria-hidden-focus was false — it claimed the violation is absent under portal: true. Re-measured directly on the DOM; see the table above. Corrected everywhere it was written down.
• main was merged in. The branch was cut before chore(sync): close the ledger's decision vocabulary and guard its shape #515 and would have reverted it.
• attach-mount.ts took attachTo from a plain spread, so attachTo: undefined behaved differently in the two projects.
• The alias guard compared importer with endsWith('test/utils/attach-mount.ts'); on Windows that never matches and the module resolves to itself. Now a resolved-path comparison.
• Benchmarks inherit both defaults, and afterEach never fires in bench mode — 711 iterations, 0 afterEach calls, every wrapper retained. disableAutoUnmount() at the top of the bench file, with a note that timings are not comparable to ones recorded before mounts were attached.
• Four comments still credited componentRender with the unmounting it no longer does, one contradicting a paragraph thirty lines below it.

One claim from the first commit message does not hold: that Vue warns on a second app.unmount(). Two reviewers measured it independently on the pinned versions — it does not. The reason componentRender leaves teardown to enableAutoUnmount is that one mechanism beats two, not that one.

Snapshots

Six files moved; the corpus is unchanged at 26.4 MB. The #454 baseline is regenerated at 292 groups / 880 entries. The entries that joined it are reference renders rather than props that stopped rendering — DashboardSearch > renders with groups passes the shared fixture that already carries groups, the same shape as DropdownMenu > with items in #512.

Gate

lint, typecheck, 320 test files / 7490 tests, test:module, vitest bench, and coverage 71.89 / 69.93 / 71.19 / 71.44 against thresholds of 70 / 68 / 70 / 70.

Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.