ContractSpec
ContractSpecOpen spec system
Menu

Choose your entry point

ProductTemplatesPricingDocsChangelogGitHub
Start with OSSExplore Studio
Back to changelog index

6.1.1

Apr 19, 2026 · 3 packages · 5 unique changes · 1 release entry

appsbundles

Release summaries

  • cli-onboard-guided-adoption

    Add a CLI-first onboarding workflow that reuses Connect adoption guidance, models guided onboarding through the surface runtime, generates managed AGENTS/USAGE guides, and exposes the same onboarding tracks through the CLI MCP surface and docs entrypoints.

    maintainer

    Maintainers get a single onboarding catalog and planner that powers CLI output, managed repo guides, Connect-compatible evidence, and the CLI MCP onboarding resources.

    integrator

    Integrators can bootstrap OSS adoption with track-aware guidance for contracts, UI design, knowledge, AI agents, and learning journeys without inventing a second Builder or Connect model.

    customer

    CLI users can run `contractspec onboard` to generate repo-local AGENTS/USAGE guidance, get recommended examples and next commands, and query the same onboarding information through MCP.

Migration guide

  • Use `contractspec onboard` as the primary OSS onboarding flow

    The CLI now provides a first-class onboarding command that should replace ad hoc “quickstart + create one spec” repo bootstraps.

    When: When documentation, scripts, or internal runbooks still point contributors directly to `contractspec create` as the first repo-local step.

    1. Run `contractspec onboard` at the repo root to generate or update the managed `AGENTS.md` and `USAGE.md` sections.
    2. Use `contractspec onboard <track...>` to focus onboarding on one or more tracks such as `knowledge` or `ai-agents`.
    3. Use `--example <key>` when you want the command to create a lightweight example stub under `.contractspec/examples/`.

  • Include the new `usage-md` setup target in setup automation

    `contractspec init` can now create or merge a managed `USAGE.md` section in addition to `AGENTS.md`.

    When: When custom setup wrappers or tests enumerate setup targets explicitly.

    1. Add `usage-md` anywhere setup target lists are pinned manually.
    2. Treat `USAGE.md` as the human-facing repo onboarding document and `AGENTS.md` as the AI-operator document.

Upgrade steps

  • Route onboarding through the existing Connect adoption layer

    assisted

    The onboarding flow now syncs and consults the existing adoption catalog before recommending new surfaces.

    Packages: @contractspec/app.cli-contractspec, @contractspec/bundle.workspace, @contractspec/bundle.library

    1. Use `contractspec connect adoption sync` to refresh the local adoption catalog outside the onboarding command when needed.
    2. Prefer `contractspec connect adoption resolve --family <family> --stdin` for custom tooling that needs the same reuse recommendations.

  • Use CLI MCP onboarding resources instead of hardcoded prompts

    manual

    The CLI MCP surface now exposes onboarding tracks, rendered artifacts, and next-command suggestions.

    Packages: @contractspec/app.cli-contractspec, @contractspec/bundle.workspace, @contractspec/bundle.library

    1. Read `onboarding://tracks` and `onboarding://track/{id}` for the canonical onboarding catalog.
    2. Call `onboarding_suggestTracks`, `onboarding_renderArtifacts`, and `onboarding_nextCommand` for repo-specific planning and guide rendering.

Unique release changes

  • - `contractspec init` can now create or merge a managed `USAGE.md` section in addition to `AGENTS.md`.

    3 packages · 3 occurrences

  • - Add a CLI-first onboarding workflow that reuses Connect adoption guidance, models guided onboarding through the surface runtime, generates managed AGENTS/USAGE guides, and exposes the same onboarding tracks through the CLI MCP surface and docs entrypoints.

    3 packages · 3 occurrences

  • - The CLI MCP surface now exposes onboarding tracks, rendered artifacts, and next-command suggestions.

    3 packages · 3 occurrences

  • - The CLI now provides a first-class onboarding command that should replace ad hoc “quickstart + create one spec” repo bootstraps.

    3 packages · 3 occurrences

  • - The onboarding flow now syncs and consults the existing adoption catalog before recommending new surfaces.

    3 packages · 3 occurrences

Impacted packages

  • @contractspec/app.cli-contractspec

    Layer: apps · 5 changes

  • @contractspec/bundle.library

    Layer: bundles · 5 changes

  • @contractspec/bundle.workspace

    Layer: bundles · 5 changes