chore(designer): Remove code interpreter experimentation flags (#9055)

[Elaina-Lee]

Commit Type

• chore - Maintenance/tooling

Risk Level

• Low - Minor changes, limited scope

What & Why

Cherry-pick of #9055 to hotfix/v5.294.

Remove the code interpreter experimentation flags (enableCodeInterpreterConsumption, enableCodeInterpreterStandard) and their associated hooks. Code interpreter is now GA and should always be enabled for both consumption and standard workflows, so the feature gating is no longer needed.

Impact of Change

• Users: Code interpreter builtin tools will now always appear in the agent loop manifest for both consumption and standard SKUs, without requiring an experimentation flag.
• Developers: enableCodeInterpreterConsumption, enableCodeInterpreterStandard, useShouldEnableCodeInterpreterConsumption, and useShouldEnableCodeInterpreterStandard are removed.
• System: Removes async experimentation service calls from the getOperationManifest path for agent operations, simplifying the flow.

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in:
  • Removed corresponding test cases from experimentationFlags.spec.ts
  • Existing tests for enableAPIMGatewayConnection remain unchanged

Contributors

Screenshots/Videos

N/A

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: chore(designer): Remove code interpreter experimentation flags (#9055)
• Issue: None blocking. The title is descriptive, includes scope and intent. Minor nit: the (#9055) suffix references the original PR number and is optional — it may be redundant when the PR body already states this is a cherry-pick of chore(designer): Remove code interpreter experimentation flags #9055.
• Recommendation: Keep as-is or remove the (#9055) suffix for brevity. Example: chore(designer): Remove code interpreter experimentation flags.

---

✅ Commit Type

• Properly selected (chore).
• Only one commit type is selected in the PR body, which is correct.

---

✅ Risk Level

• The PR body selects Low and there is a risk:low label on the PR. The code diff shows removal of feature-flag checks and associated test updates across a few files (no large API changes). Based on the diff, low is appropriate.

---

✅ What & Why

• Current: "Cherry-pick of chore(designer): Remove code interpreter experimentation flags #9055 to hotfix/v5.294.

Remove the code interpreter experimentation flags (enableCodeInterpreterConsumption, enableCodeInterpreterStandard) and their associated hooks. Code interpreter is now GA and should always be enabled for both consumption and standard workflows, so the feature gating is no longer needed."

• Issue: None.
• Recommendation: Clear and concise; nothing to change.

---

✅ Impact of Change

• Impact is clearly described in the PR body:
  • Users: Code interpreter builtin tools will now always appear in the agent loop manifest for both consumption and standard SKUs.
  • Developers: Named functions/hooks are removed.
  • System: Removes async experimentation service calls from the getOperationManifest path.
• Recommendation: Good. Consider adding a short note if any downstream consumers rely on the experimentation flags externally (unlikely here but useful if applicable).

---

✅ Test Plan

• Test plan claims Unit tests added/updated and the code diff confirms updates to unit tests (experimentationFlags.spec.ts and standardOperationManifest.spec.ts were updated to reflect always-enabled behavior). Good.
• E2E tests were not added; this is acceptable for this change but consider if higher-level E2E coverage is desirable for agent/manifest behavior in future.

---

⚠️ Contributors

• The Contributors section is blank.
• Recommendation: Optionally add co-authors or reviewers who helped with the change (the commit message shows a co-author). Not required to merge, but nice for credit and traceability.

---

⚠️ Screenshots/Videos

• Marked as N/A which is appropriate for a non-UI change.

---

Summary Table

Section	Status	Recommendation
Title	✅	Optional: remove (#9055) for brevity
Commit Type	✅	No change needed
Risk Level	✅	Label and body match; low is appropriate
What & Why	✅	Clear and concise
Impact of Change	✅	Good detail; consider note on downstream consumers if any
Test Plan	✅	Unit tests updated as shown in diff; E2E optional
Contributors	⚠️	Consider adding co-authors/credits
Screenshots/Videos	⚠️	N/A is fine for this change

---

Final message
This PR is well-formed and meets the repository's PR body template. The risk label (risk:low) matches the change set and the code diff (feature-flag removal and associated test updates). Unit tests were updated accordingly in the diff. You can proceed with merging once any required approvals and CI checks complete.

Recommendations before merging (all optional/minor):

• Consider removing the (#9055) suffix in the title for cleanliness (optional).
• Optionally add contributors/co-authors in the Contributors section to credit reviewers/PMs/designers.
• Consider whether an E2E test is warranted for manifest changes (not required given current scope, but useful for future regression protection).

Thank you — this looks ready to merge after normal review/CI checks.

---

Last updated: Mon, 13 Apr 2026 23:50:46 GMT

[github-actions]

📊 Coverage Check

The following changed files need attention:

⚠️ libs/logic-apps-shared/src/designer-client-services/lib/standard/operationmanifest.ts - 16% covered (needs improvement)

Please add tests for the uncovered files before merging.