Release & Support
This section defines how to interpret the documentation over time.
The site currently documents Latest, which tracks the current public development branch. There is no version selector because the project has not published a documentation snapshot for a tagged release yet. The first tagged release should create the first immutable versioned snapshot; until then, the site must not imply that unreleased APIs belong to a stable numbered release.
| Question | Page |
|---|---|
| How do I get help or file an actionable issue? | Get Help and File an Issue |
| Which artifact/software combinations are meaningful? | Compatibility |
| Which boundaries are known today? | Limitations / Known Issues |
| How do I diagnose a failure after first run? | Troubleshooting |
| What has shipped? | Release Notes |
| How do I move between released contracts? | Migration Guide |
| How will an interface be retired? | Deprecation Policy |
Support claims remain exact: model ID/revision, configuration, runtime path, target, software cohort, and evidence level all matter.