chore(release): enter rc pre mode and promote the v1 stable set

[johnleider]

Release-candidate preparation for v1.0.0, following the final beta (1.0.0-beta.5).

Prerelease tag: beta → rc

changeset pre exit + changeset pre enter rc, committed together. The consumed-changesets ledger carries over, so previously shipped beta content does not re-enter the rc changelog. Once this merges, the changesets action regenerates the Version Packages PR against rc — expected version for @vuetify/v0 / @vuetify/paper is 1.0.0-rc.6 (the prerelease counter continues from beta.5; it is not per-tag). Publishes land under the rc npm dist-tag; latest is untouched until the first stable release.

Maturity: promote the v1 stable set

maturity.json promotes 10 composables from preview to stable — the API commitment for 1.0:

• Selection family: createModel, createSelection, createSingle, createStep, createGroup, createNested
• Registration: createRegistry
• Plugin trio: useTheme, useStorage, useBreakpoints

They join the already-stable foundation (createContext, createPlugin, createTrinity) and observers (useIntersectionObserver, useMutationObserver, useResizeObserver): 16 stable composables + 17 stable utilities. since values are untouched (they track first-ship, not stability). Also backfills useReducedMotion since: null → "1.0.0-beta.2", its actual first-published version.

A changeset is included so the promotion is the headline of the 1.0.0-rc.6 changelog entry.

SKILL.md regeneration

pnpm skill output committed: the 10 new (stable) marks, plus one line of pre-existing drift it caught (DataTable was added to maturity.json as a draft component on Jun 25 but the generator hadn't been re-run — it now appears in the Planned list).

[pkg-pr-new]

Open in StackBlitz

commit: 3450d4d