fix(task-refactor): add explicit on/off methods to ITask interface

[akulakum]

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

This pull request addresses

1. Missing on()/off() type declarations on ITask interface

As part of the task-refactor, the SDK's ITask interface extends Node's EventEmitter for on()/off() methods, but consumers like CC Widgets whose tsconfig.json restricts type resolution to "types": ["jest"] cannot resolve @types/node — resulting in TS2339: Property 'on'/'off' does not exist on type 'ITask' errors on every task.on() / task.off() call.

2. Named exports unreachable from the SDK's main entry point

The SDK's package.json maps "main" and "exports" to dist/webex.js, which only exported the Webex class as default. All named exports (TASK_EVENTS, getDefaultUIControls, AGENT_EVENTS, ContactCenter, etc.) were properly defined in dist/index.js but unreachable at runtime for consumers using import { TASK_EVENTS } from '@webex/contact-center'.

TypeScript compilation passed because types resolved from dist/types/index.d.ts, masking the fact that the runtime values were undefined. This caused the CC Widgets' addEventListeners() to crash silently on agent:dnRegistered, meaning no task event listeners (task:incoming, agent:stateChange, etc.) were ever registered — breaking incoming task rendering, modal popups, and RONA state updates.

by making the following changes

Fix 1: Self-contained ITask event methods

• Added explicit on() and off() method declarations directly on the ITask interface, making it self-contained so consumers no longer depend on @types/node to resolve EventEmitter methods
• Used (...args: any[]) => void for the listener parameter to match Node's EventEmitter signature and avoid type narrowing issues with existing consumer callbacks

Fix 2: Re-export named exports from webex.js

• Added export * from './index' in src/webex.js so that all named exports from index.ts (enums, functions, classes, and constants) are forwarded through the main entry point (dist/webex.js)
• This ensures import { TASK_EVENTS, getDefaultUIControls, AGENT_EVENTS } from '@webex/contact-center' resolves correctly at runtime, not just at compile time

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

< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

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 - Please Specify
• This PR is related to
  • Feature
  • Defect fix
  • Tech Debt
  • Automation

I certified that

• I have read and followed 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

---

Make sure to have followed the contributing guidelines before submitting.

[Kesari3008]

Why do we need this change ? If this was a problem then how did we have widgets working till now ?

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cdcdbab86e

ℹ️ 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]

Keep CONSULT_FAILED from leaving active consult state

The new CONSULT_FAILED transition in CONSULTING moves initiators directly to HELD and clears pending retry state. Voice.endConsult() now emits CONSULT_FAILED on API errors, so a transient failure (timeout/5xx) can push the machine out of CONSULTING even though the consult leg is still active server-side. This desynchronizes UI/state (consult controls disappear, retry-on-CONSULTING_ACTIVE is bypassed) and can leave the task in the wrong lifecycle state until another backend transition corrects it.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Clear transferRequested when transfer API call fails

This sets transferRequested before the transfer API call completes, but the new catch path does not clear it when the request fails locally (e.g., network error or immediate HTTP rejection with no websocket TRANSFER_FAILED). That leaves transferRequested=true in context and later guards like shouldWrapUpOrIsInitiator can misclassify unrelated TRANSFER_SUCCESS events as locally initiated, causing incorrect wrapup/transition behavior.

Useful? React with 👍 / 👎.