chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

seamless-cli@0.4.0

Minor Changes

• 7409238: seamless init --<example> selects a use-case starter by its registry alias (e.g. seamless init --oauth), skipping the web prompt. Aliases are defined in the templates registry, so adding an example needs no CLI change. Unknown flags list the available examples, and the interactive web prompt now presents the available examples.
• fcac569: Scaffold web and api starters from the seamless-templates registry instead of hardcoded per-framework generators. The CLI now reads the registry to build its prompts, downloads the selected templates from the templates monorepo at a pinned ref, and applies each template's env contract. Adding a new framework is a templates-repo change, not a CLI change. Set SEAMLESS_TEMPLATES_DIR to scaffold from a local checkout, or SEAMLESS_TEMPLATES_REF to pin a different ref.
• 27a6ec1: seamless verify now conformance-tests every web template in the registry. It runs the API and adapter layers once, then builds, serves, and drives each web template in turn, scoping the browser suite to the flows the template's manifest declares (verify.flows, e.g. ["oauth"]). React specs are tagged by feature (@login, @oauth) so a template runs only its relevant flows; a template with no declared flows runs the full suite. SEAMLESS_REACT_DIR still overrides with a single template.

Patch Changes

• fbcc17e: Bump the verify adapter to @seamless-auth/express@^0.6.0 (the stable release that includes the
  registration-session and non-JSON-response fixes), so the released conformance run tests against
  the current published packages.
• 57c7819: Point the conformance harness at the seamless-templates monorepo. seamless verify now resolves the React web template from ../seamless-templates/templates/web/react-vite by default (still overridable with SEAMLESS_REACT_DIR), and the reusable verify-conformance.yml workflow checks out seamless-templates (input templates-ref) instead of the standalone starter repo.
• c41e68b: seamless verify now resolves the web template to conformance-test from the seamless-templates registry (the first runnable web template) instead of a hardcoded path. SEAMLESS_REACT_DIR still overrides with a direct template path, and SEAMLESS_TEMPLATES_DIR points at a local templates checkout. Running the browser suite against every web template is a follow-up.