fix(cc-widgets): bump SDK for EP-DN blind transfer fix (CAI-8329)

[akulakum]

COMPLETES https://jira-eng-sjc12.cisco.com/jira/browse/CAI-8329

This pull request addresses

Customers reported that blind transfer remains enabled when Agent 1 merges an EP-DN consult into conference before Agent 2 accepts. Performing blind transfer in that state can leave Agent 2 stuck ringing (production issue, 17+ hours).

The SDK fix is already merged in webex-js-sdk#5121. CC widgets consume transfer/consult visibility from SDK uiControls via the MobX store — no widget-layer logic change is required for this defect. This PR bumps the linked @webex/contact-center SDK version so cc-widgets consumers pick up the corrected UI control computation.

Repro flow (Agent 1):

1. Inbound call with customer
2. Consult to EP-DN (Agent 2)
3. Merge to conference before Agent 2 answers (Agent 2 still ringing)
4. Before fix: Blind transfer visible on main leg → using it causes stuck ringing
5. After fix: Blind transfer hidden; Exit Conference and main-leg controls shown correctly

by making the following changes

• Bump @webex/contact-center in @webex/cc-store from 3.12.0-next.87 → 3.12.0-next.96 (includes SDK PR #5121)
• Refresh yarn.lock for the dependency update

SDK behavior consumed by widgets (no cc-components / cc-task code changes):

• Hides main.transfer when EP-DN consult is merged to conference before a second agent joins main
• Shows Exit Conference immediately after merge on the main leg
• Restores main-leg mute, end, and recording controls

Related SDK PR: webex/webex-js-sdk#5121

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

• The testing is done with the amplify link

Automated

• yarn workspace @webex/cc-store test:unit (pending CI)
• yarn test:cc-widgets (pending CI)

Manual (EP-DN consult → merge before Agent 2 accepts) — to verify after Amplify deploy

• Agent 1: blind transfer not shown on main leg after conference merge during EP-DN consult
• Agent 1: Exit Conference visible and enabled immediately after merge
• Agent 1: main-leg mute, end, and recording controls visible and enabled
• Agent 1: no consult card / active leg remains main
• Agent 2: no stuck ringing when Agent 1 does not perform blind transfer

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 (e.g., refactoring was performed by GAI on manually written code)
• Tool used for AI assistance (GitHub Copilot / Other - specify)
  • Github Copilot
  • Other - Cursor
• This PR is related to
  • Feature
  • Defect fix
  • Tech Debt
  • Automation

Checklist before merging

• I have not skipped any automated checks
• All existing and new tests passed
• I have updated the testing document
• I have tested the functionality with amplify link

---

Make sure to have followed the contributing guidelines before submitting.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: be084dda53

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update the store spec for the SDK bump

This changes the installed SDK to 3.12.0-next.96, but the canonical store spec still documents 3.12.0-next.82 in both its Stack and Requires sections (store-spec.md:47,86). Update those claims in this commit so consumers and reviewers do not rely on an obsolete SDK boundary.

AGENTS.md reference: AGENTS.md:L68-L68

Useful? React with 👍 / 👎.

[aws-amplify-us-east-2]

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

Access this pull request here: https://pr-732.d1b38q61t1z947.amplifyapp.com