bridge: instrument calculateMaxForBridge

[Makyl]

Summary

This PR instruments calculateMaxForBridge through the SDK's standard public-operation boundary.

Bridge max calculations now emit initiated, success, failure, and performance analytics, while failures are reported to OTel with the correct public operation name. The existing public method signature, result shape, and error behavior remain unchanged.

Changes

• Add the calculateMaxForBridge analytics lifecycle triplet and stable performance operation label.
• Add calculateMaxForBridge to the exported OTel OperationName union.
• Route the public client method through a typed operation-boundary wrapper with destination, token, and source-chain context.
• Add focused client coverage for success, failure, performance naming, OTel operation naming, and result/error preservation.
• Extend the public analytics taxonomy lock and operation-name type-surface assertion.
• Add the existing bridge-max method to the architecture's public-client inventory.

Testing

• npm test
• npm run typecheck
• npm run lint

Risk / Impact

• The exported analytics taxonomy and OperationName union are extended additively.
• calculateMaxForBridge now emits the lifecycle telemetry already used by other public operations.
• No NexusClient method signature, bridge-max calculation, result shape, or thrown error changes.
• Error details remain exclusive to OTel and are not added to PostHog failure payloads.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nexus-sdk	Ready	Preview, Comment	Jul 29, 2026 3:33pm