docs/qa/solid-full-coverage-2026-10-30.md

Solid component coverage verification — 30 October 2026

This expands the ten libraries added in issue #69. Their catalogs, coverage records, pinned sources, licenses, rebuild commands, and individual reproduction gaps are under data/solid-libraries/<slug>/. The website uses the existing catalog presentation; the preview bundles retain each library's component and demonstration styles.

LibraryDocumented component IDsAvailable previewsUnavailable
Kobalte46460
SolidUI55550
shadcn-solid48480
Zaidan58580
hope-ui10100
RockSolid26260
Nikala UI78780
TorchUI99990
MagicUI Solid76760
Mystic UI27270
Total5235230

TorchUI's navigation has 100 rows but uses the name Table Panel for both a component and a recipe. The single catalog ID points to the component; its variants link identifies the separate recipe. TorchUI's Table View preview renders the underlying DataTable shown on its official page, with a disclosure that the TableView wrapper itself is not yet implemented. MagicUI Solid Tweet Card uses clearly labeled sample content in the original card.

Preview follow-up — 31 October 2026

  • TorchUI's current repository head is the pinned revision 2bd057316175457ff1e5103b961867cf388bf73f, and the latest published @torch-ui/solid remains 0.6.20. Its integrity-checked npm archive has no TableView in its JavaScript or type declarations. The live documentation script matches the retained SHA-256 and still says the wrapper is not available; its separate DataTable example is not a TableView implementation.
  • The original Tweet Card source fetches live post data and inserts text with innerHTML. Col mounts its original MagicTweet export with fixed sample content, a generated avatar and the licensed Backlight video excerpt. The sample avoids fetching or redistributing the live post; the component source, stylesheet, frame sandbox and CSP remain unchanged. Loading/error states and in-frame external links are not reproduced.

Boundaries

  • Kobalte is headless and its previews use the official demonstration CSS. Its I18n Provider has no official visual example; its preview composes the documented provider and locale hook and states that adaptation. Image and Hover Card omit the separately hosted GitHub avatar because its redistribution permission is unverified; Image retains its original fallback.
  • TorchUI Skeleton and User Card retain their own initials fallbacks because one documented avatar returns HTML and the other has no verified redistribution permission.
  • TorchUI's original three-column Board is wrapped in a keyboard-accessible horizontal scroll region on narrow screens. The component's layout and styling are unchanged.
  • hope-ui uses the pinned unpublished Solid 2 beta source. Other libraries use their own pinned Solid runtimes and dependencies.
  • SolidUI, shadcn-solid, Zaidan and Nikala Sidebars keep their state in memory because the opaque sandbox blocks their preference cookies. Nikala's mobile trigger uses the visible sidebar's collapse state. Zaidan Dialog names Cancel and associates the portalled fields and Save control with its local example form; it dispatches a local submit event when an MCP Apps host blocks native form submission.
  • SolidUI and Zaidan omit unverified external profile images and show their original avatar fallbacks. MagicUI Solid Avatar Circles uses labeled generated sample avatars, and Hero Video Dialog uses a licensed sample image and video; both retain the original components and styles.
  • SolidUI and shadcn-solid OTP Field and Zaidan Input OTP disable password-manager displacement inside the sandbox to avoid clipped-input overflow while retaining their slot styling.
  • MagicUI Solid Confetti uses its documented globalOptions to disable the worker in the preview. The original animation runs on the main thread without relaxing the sandbox or changing its CSS.
  • On narrow screens, TorchUI's Mega Menu preview reflows its navigation, stacks the original menu columns and allows the panel to scroll within the frame.
  • Mystic UI previews use the upstream Tailwind variant; its website displays Panda stories. Some external profile images and posters cannot be redistributed, so their source URLs remain blocked and the affected previews disclose the missing assets.
  • MagicUI Solid Backlight uses a two-second, 720p/30 fps licensed excerpt: 43,852,026 bytes original, 392,139 bytes delivered. TorchUI Video uses a 10.083-second, 640×268/24 fps licensed excerpt: 90,190,341 bytes original, 152,632 bytes delivered. Both retain source and delivered SHA-256 hashes and conversion details in their asset records. MCP Apps reads these through bounded resources; standalone HTML embeds the same verified bytes within the 2 MB inline budget.
  • MagicUI Solid Video Text reuses the unchanged 722,190-byte original WebM already retained by Col. The matching CodePen upload and its current user-content grant are recorded in data/solid-libraries/magicui-solid/ocean-permission.json; uploader authority is warranted by CodePen's terms, but the filmmaker and terms in force at upload were not independently identified.
  • MagicUI Solid's Lens and Pixel Image examples use WebP conversions: 398,795 to 128,990 bytes and 900,059 to 121,382 bytes, respectively. TorchUI's photo changes from 12,854 to 8,790 bytes; a 20,538-byte frame from the licensed film replaces its 89,072-byte poster to avoid logos excluded from the Spring website's CC BY license. Original and delivered hashes, attribution, and conversions are recorded in each asset manifest.
  • SolidUI's photo changes from 93,607 to 38,630 bytes in WebP. Zaidan's gradient avatar changes from 4,086 to 350 bytes losslessly; its three photos change from 112,379 to 93,800 bytes, 90,328 to 63,180 bytes, and 99,240 to 81,138 bytes. The photos retain their recorded source attribution and disclose their lossy conversions.
  • Kobalte's repository logo changes losslessly from 8,373 to 3,198 bytes; its decoded RGBA pixels are unchanged.
  • Browser checks cover the pinned examples and stated interactions, not every variant, browser engine, assistive technology, or downstream application's installed dependencies. The local MCP Apps host is a protocol fixture, not a third-party client.

Verification

  • The prior 521 available previews passed Chromium checks in light and dark themes. The added Table View DataTable example also passed both themes at desktop and mobile widths, with its exact documented rows, columns, stylesheet and limitation checked. The final Kobalte sweep exercised each recorded interaction and verified both Image fallbacks after its delay.
  • Each previously available preview passed through the local MCP Apps protocol host; Kobalte, hope-ui, RockSolid, and Video Text were checked in both themes. The rebuilt TorchUI group passed 42/42 MCP Apps and 84/84 desktop/mobile standalone checks, including Board keyboard scrolling. After the poster substitution, Video passed both themes in MCP Apps and desktop/mobile standalone HTML with frame network access blocked; its frame decoded, disclosure appeared, and video played. The sample Tweet Card passed the same formats, themes and network restriction; its video played and the complete card fit the frame. The two video excerpts played through verified resource reads and standalone HTML; Video Text played its unchanged WebM in both formats.
  • npm run typecheck passed. npm test built the combined git.cafe-base checkout and passed all 427 tests with no skips; its explicit test paths exclude the retained upstream TorchUI setup fixture from Col's test discovery. The isolated checkout used a temporary Turbopack root to resolve linked dependencies; the committed configuration was unchanged. An earlier root-checkout run passed 422 tests, although Turbopack could not persist its cache because that cache disk was full.
  • After lossless baseline packing, npm test passed all 428 tests without skips on the project's required Node 24.22.1, including the production build and TypeScript check. The isolated checkout again used a temporary Turbopack root; the committed configuration was unchanged.
  • A shared asset URL is resolved from the owning component's manifest. Focused tests confirm the React Magic UI Lens retains its original image while the Solid port uses its disclosed conversion. The affected tailwind-merge release uses its authenticated npm entry from an already-allowed CDN. React Lens uses the original, locally bundled Motion release and retains its original mask and radius; in Chromium, Escape can reopen the magnifier while the pointer stays over it.
  • The React recovery bundle passed all 66 Magic UI light/dark MCP Apps checks, including Lens, Border Beam and Magic Card; Lens also passed four standalone desktop/mobile theme checks. Cult UI Texture Card passed in both themes. The ten additional Cult UI previews previously blocked by esm.sh now use their pinned Radix packages in a shared, authenticated dependency graph; they passed 20 MCP Apps and 40 standalone desktop/mobile theme checks with the direct Radix CDN package endpoints deliberately blocked. Each check verifies the active theme, original stylesheet, available images and one demo interaction; the four canvas demos also have visible, nonzero-sized canvases. The texture demo additionally verifies its selected background decodes and its rendered opacity changes.
  • The ten retained baseline artifacts are losslessly Brotli-packed; their decoded SHA-256 hashes match their pre-packing bytes. Subsequent documented example corrections were rebuilt separately, and all 523 preview CSS hashes remain unchanged.
  • The work is submitted as a linked stack of pull requests. Earlier source snapshots are inactive until the final integration, and each pull request is measured against its target branch. Land the stack in order; git.cafe retargets the next pull request when its predecessor lands.
  • After review fixes, all 26 RockSolid previews passed in both themes in standalone HTML and MCP Apps (52/52 per format). The 35 TorchUI previews sharing changed bundles passed the same two-theme checks (70/70 per format), including menu, validation, keyboard and IME interactions under the restrictive host CSP.

Review follow-up — 1 November 2026

  • After the sidebar fixes, the 69 Nikala previews sharing the changed bundle passed 138/138 checks per format in light and dark; the original-demo sandbox sweep passed 156/156 checks. At 390px, the sidebar measured 272px expanded and 56px collapsed in both themes.
  • The 53 affected Hope, RockSolid and TorchUI previews passed 106/106 checks per format in light and dark. After further Hope calendar and RockSolid tab fixes, the 17 previews sharing those rebuilt bundles passed another 34/34 per format. The affected SolidUI, shadcn-solid and Zaidan bundles, mobile sidebar interactions, and Zaidan Dialog pointer and Enter submissions were also checked in both formats and themes.
  • The rebuilt shared styles remained unchanged. Hope's direct range endpoints and mouse/keyboard variants, RockSolid's disabled-tab behavior and component lifecycle variants, and TorchUI's original-package trigger types received focused checks. The original source snapshots and preview sandbox remain unchanged.