feat: Svelte action + Solid directive (v0.5)

[jlc488]

numkey shipped Vue and React adapters only; its sibling kokey now covers four frameworks, so this closes the gap in the "-key family".

Svelte (@devslab/numkey/svelte)

use:numkey action — options object, decimals shorthand (use:numkey={2}), or nothing (data-numkey* attributes). Imports nothing from svelte, so there is no peer dependency at all.

bind:value works via the new bind() resync option: Svelte registers its binding listener before the action runs, so a reformat re-dispatches input and the second (idempotent) pass lets the binding read the formatted value. That means bind:value holds the display value — onValue reports the canonical one, mirroring React's onValueChange. It dedupes, since the resynced event re-enters the listener.

Solid (@devslab/numkey/solid)

use:numkey directive reactive to a signal (createRenderEffect + onCleanup), plus a useNumkey ref factory. No resync needed — Solid delegates input at the document level, so the element-level formatting listener runs first and onInput already reads the formatted value. solid-js is an optional peer.

Docs

Svelte/Solid sections in both READMEs, a framework entry-point table, and a proper Roadmap section — numkey only had a stray "Roadmap: Indian lakh grouping" note line, so v0.2–v0.5 are now recorded as shipped with lakh grouping left demand-gated.

Verification

• 10 new tests (100 passing), typecheck + build green (new dist/svelte.*, dist/solid.*).
• vitest.config.ts aliases solid-js to its browser dev build — vitest otherwise resolves the node/SSR build, which has no reactivity. Solid also batches updates inside createRoot, so the reactive test drives the signal from outside the root.
• One test expectation was corrected during the run rather than the code: on an integer field . is not a decimal mark, so 1234567.89 → 123,456,789 — the documented parse('1.5') === '15' contract.