feat(plugin-meetings): report new WASM runtime metrics

[antsukanova]

COMPLETES

Related to SPARK-844160

This pull request addresses

• Update js_sdk_wasm_runtime_performance telemetry to support the new WASM-only probe.
• Make the probe easier to validate by reporting its decision, reason, and measurements.
• This changes telemetry fields only.

by making the following changes

• Consume the result provided by @webex/web-capabilities@1.13.0.
• Report status, capability, reason, divRatio, sqrtRatio, addNsPerOp, and median timings.
• Send null measurement fields when the probe cannot complete a benchmark.
• Remove the old ratio, wasmMs, and jsMs fields.
• Keep reporting limited to once per page and ensure probe failures cannot prevent meeting creation.

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tooling change
• Internal code refactor

The following scenarios were tested

Automated testing

• yarn workspace @webex/plugin-meetings test:unit Passed
• yarn workspace @webex/plugin-meetings build Passed

Manual verification

• Verified telemetry containing completed benchmark measurements.
• Verified unknown results include a reason and null measurement fields.
• Verified telemetry is emitted only once.
• Verified probe failures do not prevent meeting creation.
• Verified existing meetings do not rerun the probe.

The GAI Coding Policy And Copyright Annotation Best Practices

• GAI was not used (or, no additional notation is required)
• Code was generated entirely by GAI
• GAI was used to create a draft that was subsequently customized or modified
• Coder created a draft manually that was non-substantively modified by GAI
• Tool used for AI assistance
  • Github Copilot
  • Other — Cursor
• This PR is related to
  • Feature
  • Defect fix
  • Tech Debt
  • Automation

I certified that

• I have read and followed the contributing guidelines
• I discussed changes with code owners prior to submitting this pull request
• I have not skipped any automated checks
• All existing and new tests passed
• I have updated the documentation accordingly

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d2cd24132c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-5159.d3m3l2kee0btzx.amplifyapp.com

[Kesari3008]

Do we intentionally want them to be null if these values are missing in measurements object because as per the logic they will be undefined anyways

[antsukanova]

Yes @Kesari3008, good comment, this was intentional. undefined fields will be omitted during JSON.stringify, while null explicitly indicates that the probe did not produce measurements and keeps the telemetry fields consistent across results.

[Kesari3008]

Minor comment to understand the intent there

[github-actions]

🎉 Your changes are now available!
Released in: v3.12.0-next.182
📖 View full changelog →

Packages Updated	Version
webex	3.12.0-next.182
@webex/plugin-meetings	3.12.0-next.126

Thank you for your contribution!
🤖 This is an automated message. For queries, please contact support.