docs: highlight agent UI deprecation and code-first rollout date

[keydunov]

Move the code-first agent configuration callout to the top of the AI overview page and reframe it as a deprecation notice for UI configuration. Call out that deployments created after April 30, 2026 have it enabled by default, while existing deployments must set CUBE_CLOUD_AGENTS_CONFIG_ENABLED=true manually.

Made-with: Cursor

Check List

• Tests have been run in packages where changes have been made if available
• Linter has been run for changed code
• Tests for the changes have been added if not covered yet
• Docs have been added / updated if required

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cubed3	🟢 Ready	View Preview	May 1, 2026, 12:03 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[claude]

Claude finished @keydunov's task in 34s —— View job

---

Code Review

• Gather context and read changed files
• Review the diff against origin/master
• Provide code review feedback

---

Summary: Clean, focused docs change. The callout is correctly promoted from an <Info> to a <Warning> and moved to the top of the page where users will see it immediately. The content accurately reflects the deprecation and the two-track rollout (new vs. existing deployments).

Feedback:

1. Looks good overall. The change is minimal and well-scoped — it replaces the old informational note with a prominent deprecation warning at the top of the page, which is the right placement for a deprecation notice.

2. Minor wording suggestion (non-blocking): The first sentence says UI configuration is "deprecated" but doesn't mention when it will be removed. If there's a planned removal date, adding something like "UI configuration will be removed in version X.Y" would help users plan their migration. If no date is set yet, the current wording is fine.

3. Content accuracy check: The date "April 30, 2026" in the warning aligns with today's date (May 1, 2026), meaning newly created deployments should already have this enabled by default. This is consistent and timely.

4. No security, performance, or testing concerns — this is a documentation-only change with no code impact.

Verdict: LGTM — ship it. The optional wording improvement about a removal timeline can be addressed in a follow-up if needed.