Release FlashDreams v0.2.0

[jmccaffrey-nv]

Goal

Ship v0.2.0 with Runtime V2, migrated model integrations, flashdreams.accelerated, the crazy robotaxi demo, clearer documentation, and a repeatable open-source release process.

Changelog

• Document all user-visible changes since the last release.
• Call out breaking changes and migration steps.
• Credit contributors.
• Prepare concise GitHub release notes.

Runtime V2 and integrations

• Make Runtime V2 the default for new models and demos.
• Migrate all integrations included in v0.2.0.
• Add a smoke test for each supported integration.
• Document the status of integrations remaining on V1.
• Publish one canonical integration guide.

flashdreams.accelerated

• Define the supported public API.
• Verify clean installation and imports.
• Document hardware, software, and fallback requirements.
• Pass CPU and GPU tests.
• Validate one integration using the accelerated path.

Crazy robotaxi demo

• Ship a runnable Runtime V2 demo.
• Document one tested launch command and the controls.
• Add a smoke test.
• Verify licenses for models, code, and assets.
• Capture release media.

Documentation

• Test all prominent launch commands.
• Create one canonical quickstart.
• Create one clear entry point for adding a model or demo.
• Remove or link duplicated guidance.
• Shorten integration docs to setup and usage essentials.
• Use consistent names and commands throughout.

Open-source release process

• Verify licenses, notices, and package metadata.
• Update contribution and pull-request guidance.
• Document the release procedure and required CI checks.
• Build and test artifacts from a clean environment.
• Tag v0.2.0 and publish the release.
• Verify the published artifacts.

Done when

• Supported integrations run on Runtime V2 and pass smoke tests.
• flashdreams.accelerated installs and works as documented.
• The robotaxi demo runs from its documented command.
• New contributors can quickly find the integration guide.
• Changelog, CI, licensing, and release checks are complete.

Target date: TBD
Release owner: TBD
Milestone: v0.2.0

[fangjunzhou]

Is there any plan for migrating cuda graph dispatch to make it part of flashdreams.accelerated v0.2.0? This can be part of #478

I'm recently trying to build my own cuda graph dispatch wrapper and I'm considering if I should just use flashdreams.