[Chore] @vuetify/v0/browser subpath ships no type declarations (attw UntypedResolution)

[johnleider]

Summary

are-the-types-wrong flags the @vuetify/v0/browser export with UntypedResolution ("No types"): ./browser maps to ./dist/browser/index.js, but dist/browser/ ships only index.js — no .d.ts. A TypeScript consumer importing @vuetify/v0/browser gets no types.

Location

• packages/0/package.json exports: "./browser": "./dist/browser/index.js" (no types condition).
• dist/browser/ contains index.js only.
• Surfaced by the new repo:exports CI check (publint + attw), which currently baselines this via attw --pack ./packages/0 --profile esm-only --exclude-entrypoints browser so the guard lands green while still catching new untyped/broken exports on every other entrypoint.

Decision needed

1. Emit a .d.ts for the browser entry + add a types condition to the ./browser export, then drop --exclude-entrypoints browser from repo:exports; or
2. Accept it as intentional (the browser bundle is for <script>-tag use, not TS imports) and keep the documented exclusion.

Low priority — the browser entry is primarily for direct-browser use. Tracked so the baseline exclusion is a conscious decision, not a silent gap.