feat(solid): the Solid substrate with the Dialog primitive

[ivanbanov]

What

The Solid substrate, targeting Solid 2.0 (solid-js + @solidjs/web at ^2.0.0-rc.1):

• @dunky.dev/solid-dialog — the compound Dialog (Trigger, Portal, Backdrop, Viewport, Content, Title, Description, Close), same anatomy and behavior contract as the React binding, with the connected api as a fine-grained store.
• @dunky.dev/solid-use-focus-trap / @dunky.dev/solid-use-scroll-lock — the Solid lifecycle wrappers over the framework-free DOM utils.
• @dunky-dev/solid storybook harness (pnpm dev:solid, port 6008, storybook-solidjs-vite), with the story set mirroring the React one.
• Scaffold templates under scripts/templates/packages/solid — pnpm scaffold <name> now stamps Solid too.
• Workspace wiring: a second vitest project (vite-plugin-solid lives with the substrate), a Solid tsconfig project (jsxImportSource: "@solidjs/web"), and a per-package tsdown babel config so the dist is compiled by babel-preset-solid.

Solid-specific decisions

• Bindings merge inside the JSX spread so a machine transition re-translates them. children never rides that spread: a re-evaluated spread re-creates the children it carries, and a child that writes to the machine on mount (Title's presence) loops machine -> spread -> remount -> machine. Every part strips it and renders {props.children} explicitly.
• Two-phase effects compute eagerly, before refs fill — useFocusTrap re-reads its target at apply time, and the backdrop handle shared between sibling parts is a plain mutable box, not a signal (the layer walk reads it in the same settle that mounts the backdrop).
• Content's initialFocus accepts an element or an accessor resolved at open time — the Solid idiom for a ref variable that fills during render.
• The dialog context uses a null default so the root's parent-depth lookup stays non-throwing (a Solid 2.0 default-less context throws on unprovided reads).

Blocked on

• feat(solid): Solid 2 integration state-machine#32 must merge and publish @dunky.dev/solid-state-machine first (including the normalize fix that stringifies boolean aria-* values — Solid 2.0 renders boolean attributes as presence/absence). The lockfile is deliberately not committed until then; local dev uses an uncommitted pnpm-workspace.yaml override that links @dunky.dev/solid-state-machine straight to that branch checkout. The ^0.4.0 dependency ranges assume the fixed-group publish version — adjust if it differs.

Verified

• 190 tests across both vitest projects (49 dialog tests ported 1:1 from the React binding), typecheck, lint, format, knip (at main's baseline), pnpm build (dist compiled to @solidjs/web templates, publint clean), and the storybook build.

🤖 Generated with Claude Code

[ivanbanov]

Status sync (2026-08-21) — this PR has a hard upstream dependency: dunky-dev/state-machine#32.

@dunky.dev/solid-state-machine is still unpublished (npm returns 404; PR #32 is open, unmerged). Because of that, all six CI checks fail at the install step, not on this code:

[ERR_PNPM_OUTDATED_LOCKFILE] Cannot install with "frozen-lockfile"
because pnpm-lock.yaml is not up to date with <ROOT>/packages/solid/package.json

The lockfile stays uncommitted on purpose — it cannot resolve a package that does not exist on the registry. CI goes green only after #32 merges and publishes; nothing in this branch can fix it before then.

Local dev now links the adapter straight from the state-machine solid worktree instead of a packed tarball, via an uncommitted pnpm-workspace.yaml override:

overrides:
  "@dunky.dev/solid-state-machine": "link:<path-to>/state-machine/packages/solid"

Everything passes against that link: build, lint, format, typecheck, changeset status, and 190 tests (53 in the solid vitest project, 137 in the default one). Branch is synced with main and carries #45.

Unblock checklist, once #32 publishes: drop the override, pnpm install, commit the lockfile, and correct the ^0.4.0 ranges in packages/solid/dialog/package.json and the scaffold template if the published version differs.