Skip to content

Phase 3: remove legacy dual paths and release v3.0.0 #137

Description

@olliethedev

Context

Final phase of the v3.0.0 core simplification, after all plugin sweeps in #136 land. v3.0.0 is not yet published to npm, so all breaking removals batch into this release. This PR should be reviewable as "deletions only" — no migrations happen here.

During phases 1–2 the old and new paths coexist so main stays green; this issue deletes the old paths.

Deletion checklist

Provider / context:

Templates / examples:

Tests:

  • Delete E2E/unit tests that exercise removed paths; verify new-path coverage is complete across all three frameworks

Docs:

  • Rewrite installation guide against factories/providers only (manual glue moves to an "advanced" appendix or is dropped)
  • Update all plugin MDX pages (override tables, auth examples)
  • Write v2 → v3 migration guide in docs/content/docs/breaking-changes.mdx covering: yar route context (already documented), removed override fields, removed guard callbacks, removed identity props, new provider setup
  • Update agent skills (btst-client-plugin-dev, btst-integration, btst-build-config) to new patterns

Verification / release:

  • rg sweep: no references to removed fields/props/callbacks anywhere in the monorepo
  • pnpm build && pnpm typecheck && pnpm lint && pnpm test green; all three codegen E2E suites green
  • Publish @btst/stack 3.0.0 to npm (gate: everything above complete)

Depends on

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions