fix: render tiny balances with typographic subscript

[tansawit]

Summary

This updates amount rendering so very small non-zero balances no longer appear as plain 0.000000 and instead use a true typographic subscript presentation for hidden leading zeros.

User impact

Users with tiny balances can now distinguish between zero and non-zero values across bridge, asset selection, transfers, send, portfolio, and fee-related amount surfaces. The subscript is rendered as real baseline-lowered text instead of Unicode subscript glyphs.

Root cause

Amount formatting previously relied on fixed decimal truncation, which collapsed many non-zero values to 0.000000. The initial follow-up approach encoded subscript into formatted strings, which coupled formatting output to UI parsing.

What changed

• Added structured amount formatting parts in lib/format to explicitly represent subscript segments.
• Added FormattedAmount to render amount text with a real <sub> element for hidden leading-zero counts.
• Added FormattedFeeList to unify fee amount rendering and remove duplicated fee mapping logic.
• Updated amount displays across bridge, deposit/withdraw, send, activity, portfolio, and fee views to use shared components.
• Made QuantityInput.ReadOnly placeholder state explicit (isPlaceholder required) to remove brittle ReactNode-to-number inference.
• Updated dropdown option typing to support ReactNode labels for formatted fee entries.

Scope notes

This keeps precision policy consistent with existing display constraints while making tiny-value formatting explicit and reusable through shared components.

Checks

• pnpm -C packages/interwovenkit-react test
• pnpm -C packages/interwovenkit-react typecheck

---

Note

Low Risk
CSS/layout-only changes that may affect scrolling and sizing across multiple screens, but don’t alter business logic or data flow.

Overview
Improves scroll behavior and overflow containment across the drawer by updating Scrollable styling (adds min-height: 0, momentum scrolling, and overscroll-behavior).

Wraps EnableAutoSign and TxRequest content in new .page flex containers and constrains the drawer’s routed content via a new .routes wrapper, reducing layout/scroll glitches when pages contain headers/footers inside the drawer.

^{Written by Cursor Bugbot for commit c37b01b. This will update automatically on new commits. Configure here.}

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/mobile-scroll-autosign-tx-approval

---

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

[cloudflare-workers-and-pages]

Deploying interwovenkit with    Cloudflare Pages

Latest commit:	5527ece
Status:	✅  Deploy successful!
Preview URL:	https://727520a5.interwovenkit.pages.dev
Branch Preview URL:	https://fix-mobile-scroll-autosign-t.interwovenkit.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying interwovenkit-staging with    Cloudflare Pages

Latest commit:	c37b01b
Status:	⚡️  Build in progress...

View logs

[cloudflare-workers-and-pages]

Deploying interwovenkit-testnet with    Cloudflare Pages

Latest commit:	5527ece
Status:	✅  Deploy successful!
Preview URL:	https://5bf4c36f.interwovenkit-testnet.pages.dev
Branch Preview URL:	https://fix-mobile-scroll-autosign-t.interwovenkit-testnet.pages.dev

View logs

[tansawit]

Closing this PR because it was opened from the wrong branch by mistake. The correct draft PR is #168.