fix(task-refactor): fix task-refactor e2e

[akulakum]

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

This pull request addresses

< DESCRIBE THE CONTEXT OF THE ISSUE >

by making the following changes

< DESCRIBE YOUR CHANGES >

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
  < 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

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: 0db2290e9c

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

Enable multi-login before widget initialization

Here basicSetup() has already initialized the widgets via the desktop pageSetup() path, which disables multi-login before SDK initialization; the sample app warns that changing samples:multi-login-enable-checkbox after SDK initialization has no effect (widgets-samples/cc/samples-cc-react-app/src/App.tsx lines 636-638). In filtered runs of just should test multi-session synchronization (or if the earlier reload test is skipped), agent1's SDK remains single-login while the second session is initialized, so the test depends on a previous reload to pass instead of being independently runnable. Enable multi-login before widget initialization or reload/reinitialize immediately after setting it.

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-713.d1b38q61t1z947.amplifyapp.com