Skip to content

feat(wow): curated adapter compatibility resolver and runtime reuse (#142) - #148

Merged
EagleFox31 merged 10 commits into
mainfrom
feat/142-wow-adapter-resolver
Oct 10, 2026
Merged

EagleFox31 merged 10 commits into
mainfrom
feat/142-wow-adapter-resolver

Conversation

@EagleFox31

Copy link
Copy Markdown
Contributor

Summary

Closes #142. Implements offline, non-executing adapter resolution for the nine sources introduced in #139 and approved by the default-deny governance boundary in #140.

Added

  • ui-registry/wow-adapters.json + versioned JSON schema: one reviewed integration hint per source, strict interface kinds, possible animation runtime hints, and executable:false/autoInstall:false.
  • ui-registry/wow-resolver.mjs: pure fail-closed resolver joining the source inventory, consumer configuration, centrally reviewed source policy and adapter metadata.
  • Clear split between technicalFit (native, adapt, reference-only) and final decision (native, adapt, reference-only, unsupported), with license policy always applied first.
  • Optional external MCP service advisory without requiring/using it; guidance sources cannot supply executable components.
  • Runtime hints (motion, gsap, three) reuse observed installed runtimes; no new installation/duplicate runtime.
  • scripts/wow-frontend-plan.mjs now includes adapterResolutions while preserving the existing source plan output from [Feature] Add WOW Frontend agent skill — search before build, render before done #141.
  • Comprehensive tests test/wow-frontend-adapters.test.mjs, included through the existing npm run test:ui-registry CI gate.
  • docs/wow-source-adapters.md and updates to the skill and registry README.

Safety / architecture

  • No extra UI registry; ui-registry/registry.json stays canonical for native components.
  • All nine live external sources still reference-only, current central approval list stays empty.
  • Synthetic tests show that even a centrally reviewed registry-install mode is manual only, and native Tailwind registry adoption is blocked for plain-CSS consumers.
  • No npm install, remote script, network fetch, hosted plugin call, source copy, Cloudflare deployment, consumer mutation or PostgreSQL changes.
  • No changes to PR Add PostgreSQL migration gate to Worker releases #74, CI global config, package manifest, or current native UI components.

CI / Definition of Done

The PR must pass the existing Impact-Aware CI UI Registry contract/security/resolver suite, AppFactory typecheck and React/Vite webapp smoke builds. The skill remains a planning workflow, not proof of rendered visual QA. Future actual browser QA is tracked in Project Automation #99; Commerce Factory pilot in AppFactory #143.

@EagleFox31
EagleFox31 merged commit 0ab983a into main Oct 10, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Add curated UI source adapters and stack compatibility resolver

1 participant