Skip to content

refactor(integration): name a variant's framework under match - #535

Draft
edwinyjlim wants to merge 1 commit into
mainfrom
dag/m0-match-every-row
Draft

edwinyjlim wants to merge 1 commit into
mainfrom
dag/m0-match-every-row

Conversation

@edwinyjlim

Copy link
Copy Markdown
Member

What this does

A variant says which projects it serves in one place: match.

- id: nextjs-app-router
  match: { framework: nextjs, frameworkVariant: app-router }
  default: true
  • Every variant that serves a framework names it as match: { framework: … }. This covers the 38 routable rows of the variant table in context/skills/integration/config.yaml, and the variants of ai-observability and of the two integration-v2 step skills that list their own rows.
  • The build makes the framework:<id> menu tag, the menu's framework field and a pack's variant.json from match.
  • A variant with a framework key of its own fails the build, and so does a match that names no framework.
  • A group that borrows another group's variants takes the framework each one matches, and no other match key.
  • react-vite and php serve no detected framework, so they have no match.
  • default stays its own key. It marks the pack a framework's projects take when no other row is picked.

ai-observability uses framework for an LLM provider, such as openai. That value keeps publishing as the framework:openai tag it publishes today.

Verification

  • npm test: 454 tests pass.
  • The build passes.
  • A build of this branch was compared with a build of main, both from a clean checkout: every published file by content, every zip by its entries and their bytes, and both JSON files structurally. Nothing differs. The 302 skill zips, the 5 group JSON files, the prompts, the menu, the manifest, the MCP archive and the marketplace tree are the same.

Rollout

This waits on nothing. It changes no published file, so it needs no release of its own.

🤖 Generated with Claude Code

A variant says which projects it serves in one place, `match`. The build
makes the `framework:<id>` menu tag, the menu's `framework` field and a
pack's `variant.json` from it, and refuses a `framework` key beside it or a
`match` that names no framework. A group that borrows variants takes the
framework each one matches and no other match key.

The built skills, menu and manifest are unchanged.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@edwinyjlim
edwinyjlim added this pull request to stack #539 November 17, 2026 01:10
@github-actions

Copy link
Copy Markdown

🧙 Wizard CI

Run the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands:

Test all apps:

  • /wizard-ci all

Test all apps in a directory:

  • /wizard-ci ai-observability
  • /wizard-ci basic-integration
  • /wizard-ci feature-flags
  • /wizard-ci mcp-analytics
  • /wizard-ci replay-vision
  • /wizard-ci revenue
  • /wizard-ci self-driving
  • /wizard-ci warehouse
  • /wizard-ci warehouse-seeded

Test an individual app:

  • /wizard-ci ai-observability/anthropic
  • /wizard-ci ai-observability/google-adk
  • /wizard-ci ai-observability/groq
Show more apps
  • /wizard-ci ai-observability/manual-capture
  • /wizard-ci ai-observability/openai
  • /wizard-ci ai-observability/openai-agents
  • /wizard-ci ai-observability/opentelemetry
  • /wizard-ci ai-observability/vercel-ai
  • /wizard-ci basic-integration/android
  • /wizard-ci basic-integration/angular
  • /wizard-ci basic-integration/astro
  • /wizard-ci basic-integration/django
  • /wizard-ci basic-integration/fastapi
  • /wizard-ci basic-integration/flask
  • /wizard-ci basic-integration/flutter
  • /wizard-ci basic-integration/javascript-node
  • /wizard-ci basic-integration/javascript-web
  • /wizard-ci basic-integration/laravel
  • /wizard-ci basic-integration/next-js
  • /wizard-ci basic-integration/nuxt
  • /wizard-ci basic-integration/python
  • /wizard-ci basic-integration/rails
  • /wizard-ci basic-integration/react-native
  • /wizard-ci basic-integration/react-router
  • /wizard-ci basic-integration/sveltekit
  • /wizard-ci basic-integration/swift
  • /wizard-ci basic-integration/tanstack-router
  • /wizard-ci basic-integration/tanstack-start
  • /wizard-ci basic-integration/vue
  • /wizard-ci feature-flags/django
  • /wizard-ci feature-flags/next-js
  • /wizard-ci mcp-analytics/custom-dispatcher
  • /wizard-ci mcp-analytics/go-sdk
  • /wizard-ci mcp-analytics/python-sdk
  • /wizard-ci mcp-analytics/ruby-sdk
  • /wizard-ci mcp-analytics/rust-sdk
  • /wizard-ci mcp-analytics/typescript-sdk
  • /wizard-ci replay-vision/javascript-node
  • /wizard-ci replay-vision/next-js
  • /wizard-ci replay-vision/react-vite
  • /wizard-ci revenue/stripe
  • /wizard-ci self-driving/astro
  • /wizard-ci self-driving/fastapi
  • /wizard-ci self-driving/nuxt
  • /wizard-ci self-driving/react-router
  • /wizard-ci self-driving/sveltekit
  • /wizard-ci warehouse/monorepo-env
  • /wizard-ci warehouse/multi-source-next
  • /wizard-ci warehouse/stripe-node
  • /wizard-ci warehouse/zero-source
  • /wizard-ci warehouse-seeded/next-stripe
  • /wizard-ci warehouse-seeded/next-stripe-declined

Test against a wizard branch:

  • /wizard-ci all wizard:my-branch

Add wizard:<branch> to any command above to pin the wizard branch. It defaults to main.

Results will be posted here when complete.

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.

1 participant