Implement MP Catalog Wave B in the JavaScript/TypeScript client #11

Outcome

Implement every Briosa-selected operation from MP Catalog Wave B through the accepted JavaScript/TypeScript public API in one substantial code PR.

Included top-level SA groups

• Cloud and Mesh Operations
• Construction Operations
• GD&T Operations
• Instrument Operations
• Relationship Operations (remaining 59 exact-target observations)
• Robot Calibration Appliance Node Operations
• Robot Operations

Relationship Operations boundary

Wave A owns the 55 exact-target Relationship Operations contracts already published in briosa-docs#16 and implemented through spatialanalyzer/briosa#154. Wave B dispositions and implementations cover only the remaining 59 observed Relationship Operations commands.

Scope

• Consume and lock the target-qualified Wave B protocol artifact from Implement MP Catalog Wave B for SA 2026.1.0529.7 briosa#155.
• Implement all selected operations, handwritten domain values, named results, presence/default mappings, typed failures, capability checks, cancellation, and API-surface tests for the included groups.
• Preserve the documentation-first signatures and MP-recognizable names without exposing generated request/result types.
• Do not create APIs for excluded, deferred, or SDK-unavailable commands.
• Keep the entire wave in one client PR; do not create per-command or per-group PRs.
• Update supporting examples and package metadata in the same implementation PR.
• Complete final package, compatibility, migration, and release validation for the full v1 surface.

Acceptance criteria

• Every selected Wave B server operation is represented idiomatically and matches the published JavaScript/TypeScript API documentation.
• No non-selected command is exposed as supported client API.
• Generated transport types do not leak through public parameters, results, errors, or discovery models.
• Presence, defaults, output cardinality, collections, typed failures, cancellation, recovery, and replay behavior satisfy the shared contract.
• Capability subsets and missing required outputs fail through the handwritten boundary.
• Build, lint/format, package, API-surface, unit, and shared conformance checks pass for the entire wave.
• The final package covers the complete supported v1 server surface and is ready for coordinated release.

Server implementation: spatialanalyzer/briosa#155
Documentation-first contract: spatialanalyzer/briosa-docs#22
Parent: #3