Check your installed executable with sonny version. The Docs badge identifies
the release used for this reference. A newer upstream tag does not update the
examples, screenshots or qualification results automatically.
Current reference and release observation
- Documentation baseline
v0.12.7, released 2026-10-24.- Baseline source commit
192e590345c6a4bf1ef8f72b043b318084ea84d6- Qualification record date
- 2026-10-25; in-progress; see issue-specific evidence and availability limits.
- Measured executable
- linux/amd64; SHA-256
45a7ae62c66c15693790de1905b72502b75e7889682e4e58cbb4e88756ba6879. This is the tested executable's digest, not an installation archive checksum. - Upstream tag observed
v0.12.8on 2026-10-25; tag observed; not qualified by this reference.- Observed tag's source
eaf885551c5834f4bee56ea48be7b9eff768c66d- Published upstream release record
- Not found at 2026-10-25T15:10:03Z. A tag alone does not establish an available release download.
The upstream observation distinguishes a source tag from a published release record. It is dated information, not a live release feed or a recommendation to upgrade. This site currently has one documentation baseline; it does not offer an archived-version selector. Older links are preserved within that reference. Development and newer release behavior need their own evidence.
The CLI archive , configuration records , format contracts and analysis schema identify their release and validation boundaries. Static validation, configuration acceptance, source tests and a completed controlled-provider run establish different things. Read each guide’s limitations before treating an example as a supported deployment.
Compatibility scope
| Surface or format | Evidence available for this baseline | Remaining limits |
|---|---|---|
| Linux amd64 CLI and TUI | Installed-binary help, local configuration checks, controlled-provider and terminal workflows. | Guide-specific failures remain documented. This does not qualify every terminal, OS or architecture. |
| Daemon and mesh | Versioned service guidance and disposable authenticated deployment checks. | Client compatibility, transfer/recovery and deployment prerequisites need the mesh guide and service migration guide . |
| Desktop, VS Code, controller and Neovim | Individual source/availability notes where provided. | No universal client-version or feature-parity guarantee. Full per-client reader qualification remains incomplete. |
| Recipes | A tested version-2 category fixture and the release-derived schema . | Schema version and Sonny executable version are different. Unknown-member warnings, composition and runtime boundaries remain relevant. |
| MCP servers | Pinned per-server source/transport/access records in the catalog . | There is no single version shared by every server. A build or protocol response does not certify external-account operations. |
| Lanning | Separate availability and operator guidance . | An approved release/deployment and tenant workflow must be qualified independently; no automatic compatibility or shared-memory promise. |
Use Licensing and access and the installation guide for the intended acquisition route. A source tag alone does not establish that a binary download is public, entitled, available for your platform or compatible with your existing state. Keep backup, migration and rollback requirements with the exact release you install.
Identify the deployed documentation build
Download this artifact’s build record when reporting a documentation problem. It records the website commit, its commit time, the documentation/source baseline, dated upstream observation and CI pipeline/job identifiers when present. Homepage and reference-file digests identify the rendered artifact that passed through the build workflow.
The record is generated offline after Hugo and vanity-page generation and verified before publishing. A local build reports whether its checkout was dirty; that commit alone cannot reproduce uncommitted edits. CI requires a clean checkout and checks that its commit identifier matches Git. The record contains no CI tokens or private download links.
Website commits and Sonny executable commits are separate identities. A preview deployment does not establish that production has the same build. Preview remains non-indexable; production metadata and deployment need their own verification. This build record is provenance, not a certification of all client or runtime workflows.