Documentation versions and compatibility

You are reading the documentation for @honua/sdk-js trunk development (package baseline 0.1.0-beta.0). Hosted pages are development documentation built from trunk, not immutable documentation for the package baseline. Every built page and the deployed versions.json identify the exact 40-character source commit. The version navigation in every hosted guide is generated from docs/versions.json, which is derived from package.json, .release-please-manifest.json, and released CHANGELOG.md entries. A version cannot appear in the selector unless those authoritative sources agree and the release tag exists in the authoritative GitHub repository.

Release documentation

The hosted guides and generated TypeDoc API are the development channel. The released prereleases did not publish immutable TypeDoc sites, so every release destination is explicitly labelled a source fallback: it opens the README at the exact release tag and links to canonical release evidence. Released code is never silently redirected to today's development API.

Compatibility and migration

• The exact Node and optional-peer ranges are published in versions.json from the current package metadata.
• There is no supported-prior line while the SDK has no GA stable release. The machine manifest records that state as not-applicable; the first stable line will establish a supported-prior designation policy.
• Stable and experimental entrypoint policy is defined in Install and choose an entrypoint and checked against the package exports.
• Breaking ArcGIS-to-Honua changes and replacement imports are documented in Migrate ArcGIS applications to Honua + MapLibre.
• Release-level changes are recorded in the tagged changelog.

When an archived guide lacks an equivalent page, use its tagged repository source and release notes. Do not combine code from an archived guide with the current API reference without following the migration notes.