fix: yield withdraw polishes

[gomesalexandre]

Description

Spotted those when once again testing the feature with akschual funds as a user and this didn't look right:

• Information overload when withdrawing, i.e doesn't make sense to see APY, est. yearly returns, or interest accrual explainers when withdrawing - did keep the immediate/delayed exit explainer as it does make absolute sense for withdraws
• Also noticed a bug when all is currently being unstaked (e.g for ATOM, but really for any with delayed unstaked that need to be finalized): able to click unstake but shouldn't be able to, as there's nothing to unstake

This PR fixes both!

Issue (if applicable)

closes #

Risk

Low - UI-only changes: filtering explainers by action type and disabling unstake button when no active balance.

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

No protocol/transaction changes. Affects yield position card UI and withdraw/exit modal explainers.

Testing

Engineering

• Navigate to a yield position with all balance in exiting/pending state (e.g. ATOM staking)
• Confirm Unstake button is disabled with tooltip: "No active balance available to unstake."
• Confirm Unstake button is enabled when there IS active staked balance
• Open withdraw/exit modal and confirm APY, est. yearly returns, and interest accrual explainers are hidden
• Confirm the immediate/delayed exit explainer still shows in withdraw modal
• Open deposit/enter modal and confirm all explainers still show as before

Operations

• 🏁 My feature is behind a flag and doesn't require operations testing (yet)

Screenshots (if applicable)

Summary by CodeRabbit

• New Features

  • Added context-aware yield transaction explanations that adapt based on enter/exit actions.
  • Enhanced tooltip messaging when exit actions are unavailable due to insufficient balance.

• UI/UX Improvements

  • Optimized display of APY and earnings estimates during yield entry.
  • Improved clarity on disabled state reasons for exit functionality.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR introduces an action prop to the YieldExplainers component to enable filtering of explainers based on relevance to specific yield operations ('enter', 'exit', 'claim'). The action prop is threaded through yield-related components, a relevance field is added to explainer items for filtering, the exit button in YieldPositionCard gains tooltip logic for disabled states, and a new translation key is added.

Changes

Cohort / File(s)	Summary
Translation Addition src/assets/translations/en/main.json	Added new translation entry noActiveBalanceToExit with message for unstaking scenarios.
YieldExplainers Core src/pages/Yields/components/YieldExplainers.tsx	Added action prop and relevance field to ExplainerItem type; implemented filtering logic to display explainers matching action relevance ('enter', 'exit', 'both'); updated component memoization dependencies.
YieldExplainers Usage src/pages/Yields/components/YieldForm.tsx, src/pages/Yields/components/YieldEnterModal.tsx, src/components/MultiHopTrade/components/Earn/EarnConfirm.tsx	Passed action prop to YieldExplainers invocations; in YieldForm, added conditional rendering for APY and earnings blocks when action === 'enter' and restructured stat layout from Box to VStack.
Exit Button Enhancement src/pages/Yields/components/YieldPositionCard.tsx	Wrapped exit action button with Tooltip; added computed isExitDisabled and exitDisabledTitle based on yield status and active balance; preserves enter action flow unchanged.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• feat: yield improvements following CR #11729: Directly related; modifies the same YieldExplainers component and call sites (YieldForm, YieldEnterModal, EarnConfirm) plus translation entries.
• fix: yields polish one #11742: Related through YieldPositionCard.tsx modifications for exit-button tooltip and disable logic.
• feat: partial yield.xyz toggle #11704: Related through YieldExplainers component signature and filtering behavior updates.

Suggested reviewers

• 0xApotheosis

Poem

🐰 A rabbit hops through yields with care,
Filtering explainers here and there,
Enter, exit, claim—each path so clear,
With relevance whispers, no more fear! 🌱

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'fix: yield withdraw polishes' is related to the changeset, which makes UI improvements to yield position cards and withdraw/exit modals, but 'polishes' is vague and doesn't clearly convey the main changes (filtering explainers by action, disabling unstake button without balance).	Consider a more specific title like 'fix: filter yield explainers by action and disable unstake without balance' to better describe the key changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat_yield_unstaking_polish

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@src/pages/Yields/components/YieldExplainers.tsx`:
- Around line 76-90: The current action mapping in the YieldExplainers component
maps 'claim' into the 'exit' path causing claim flows to surface exit/unbonding
explainers; update the logic in YieldExplainers to handle 'claim' explicitly (or
narrow the YieldExplainersProps to exclude 'claim') — e.g., compute a distinct
actionRelevance for 'claim' and adjust the useMemo filter that calls
getYieldExplainers(selectedYield) so that when action === 'claim' it either
returns an empty array or filters for a 'claim' relevance value (and update
getYieldExplainers metadata if needed); reference YieldExplainers,
actionRelevance, selectedYield, and getYieldExplainers to locate and modify the
behavior.

[NeOMakinG]

https://jam.dev/c/5d0005a2-bb95-4b93-be96-e7dd82a07b4d