Milestones
List view
## Outcome Release Leia 2.0.0 as an implementation modernization of the existing Markdown-driven testing product: rewrite the maintained source in strict TypeScript ESM, use Bun as the repository runtime and toolchain, publish CommonJS and ESM artifacts to npm, and modernize the CLI and documentation while keeping existing Leia scenario workflows working the same way. ## Prerequisites - Complete #57, #59, and #60 on `main` before starting milestone implementation. These are 1.x predecessor issues, not 2.0 milestone members. - After those changes land, complete #61 to create and protect `2.x` from the verified 1.x branch point. ## Delivery strategy - Keep `main` available for bounded 1.x maintenance while milestone pull requests target the protected `2.x` branch. Forward-port applicable 1.x fixes until the final freeze. - Treat 2.0 as breaking for its development toolchain, source architecture, package contract, and any explicitly documented interface changes. Existing Markdown scenarios and supported test workflows should retain their observable behavior unless a separate approved decision changes them. - Establish the Bun, TypeScript, and ESM foundation once, then port the Markdown compiler and CLI/runner as independently reviewable subsystems. - When the milestone is complete, freeze 1.x, reconcile the final `main` delta into `2.x`, validate a release candidate, merge `2.x` into `main`, and publish 2.0.0. - No due date is inferred. ## Completion conditions - The protected `2.x` integration branch and pull-request routing are established from the completed 1.x prerequisite baseline. - The currently pending discovery, parsing, and generation tests plus a focused end-to-end scenario form a small regression baseline that passes before and during the rewrite. - The repository has one Bun-owned development baseline, a committed Bun lockfile, strict TypeScript configuration, ESM source modules, typechecking, linting, tests, build and watch scripts, and supported CI execution. - Leia's discovery, parsing, and generation pipeline and its CLI, shell, and test-runner pipeline are ported to typed ESM source with the regression baseline passing. - The canonical build produces clean CommonJS and ESM distribution artifacts plus TypeScript declarations and source maps, with package metadata and installed-artifact tests matching the approved 2.0 runtime contract. - The CLI preserves supported workflows while adopting the approved Lando-branded Tanaab presentation. - README and companion documentation cover installation, quick start, scenario syntax, CLI and programmatic use, CommonJS and ESM consumption, Bun-based development, migration from 1.x, and the 1.x support sunset. - The final release task verifies the supported matrix and packed artifacts, merges `2.x` into `main`, publishes 2.0.0 to npm and GitHub, and verifies the published result. ## In scope - Protected `2.x` branch setup after the 1.x prerequisites. - A focused behavior baseline for existing Leia scenario workflows. - Bun runtime and package-manager workflows for repository development. - Strict TypeScript ESM source and typed internal boundaries. - Compiler and runner subsystem ports. - CommonJS and ESM npm artifacts, declarations, package exports, CLI packaging, and installed-artifact validation. - Lando-branded CLI presentation and Canon-style documentation. - Release-candidate validation, cutover to `main`, npm publication, and post-publication verification. ## Out of scope - Implementing #57, #59, or #60 as part of this milestone. - Preserving CommonJS source, Node as the 2.0 repository runtime, the old dependency graph, or other superseded implementation details. - A broad redesign of Leia's Markdown scenario language, plugin system, or product purpose. - Unrelated new product features. - Indefinite parallel maintenance of 1.x after 2.0.0 is published. ## Verification and release evidence Each implementation task completes through a linked pull request or, for #61, verified repository settings. The final release task records the resolved Bun and supported consumer runtimes, clean-checkout installation, module-consumer smokes, packaged CLI execution, scenario results, exact tarball contents, changelog and migration guidance, merge SHA, npm package version and dist-tags, and post-publication installation evidence.
No due date•9/9 issues closed