Publish the final v1 documentation and release reconciliation #12

Outcome

Publish the final v1 documentation and release reconciliation after the Lifecycle Foundation and both MP catalog implementation waves have landed across the server and all three first-party clients.

This is the final substantial documentation PR in the coordinated delivery plan.

Scope

• Promote implemented lifecycle and operation APIs from Next to Current using released package and capability evidence.
• Reconcile every catalog disposition, API signature, default, presence rule, compatibility coordinate, validation qualifier, and workaround with the shipped products.
• Publish the final server, protocol artifact, .NET, Python, JavaScript/TypeScript, and exact-SA compatibility matrix.
• Publish migration and release guidance covering all coordinated v0.x waves and the v1 readiness boundary.
• Remove stale provisional language and links while preserving historical version availability on command entries.
• Complete final site, catalog, link, accessibility, and release-version validation.

Acceptance criteria

• Every Supported claim matches released server capability registration and all three released clients.
• No proposed API remains Next unless it is explicitly deferred beyond v1.
• Every retained command has a final public disposition and accurate version history.
• Compatibility guidance identifies exact server, protocol artifact, client package, SpatialAnalyzer target, and runtime prerequisites.
• Release and migration guidance matches the published artifacts and packages.
• All package, artifact, API, catalog, and source links resolve.
• Node.js 24 build, formatting, link, accessibility, catalog-completeness, and release-version checks pass.

Parent: #10