feat: animate execution page

[yolodevz]

Which Linear task is linked to this PR?

Why was it implemented this way?

Explain the reasoning behind the implementation. Were there alternative approaches? Why was this solution chosen?

Visual showcase (Screenshots or Videos)

If applicable, attach screenshots, GIFs, or videos to showcase the functionality, UI changes, or bug fixes.

Checklist before requesting a review

• I have performed a self-review and testing of my code.
• This pull request is focused and addresses a single problem.
• If this PR modifies the Widget API or adds new features that require documentation, I have updated the documentation in the public-docs repository.

[github-actions]

Hey! This is your new endpoint: https://c075c283.widget-animateexe.pages.dev

[github-actions]

Hey! This is your new endpoint: https://92a25e64.widget-animateexe.pages.dev

[github-actions]

Hey! This is your new endpoint: https://d64097a4.widget-animateexe.pages.dev

[github-actions]

Hey! This is your new endpoint: https://c1f03285.widget-animateexe.pages.dev

[github-actions]

Hey! This is your new endpoint: https://a40669b3.widget-animateexe.pages.dev

[effie-ms]

Do we need to merge this config for Claude?

[effie-ms]

Same file as on Transaction details? Could we make it reusable, if so?

[effie-ms]

Could we drop this index file, from this config and in the directory?

[effie-ms]

Do we need to filter it out from the released/published packages as well?

[effie-ms]

Could you check how stable this dependency is? Otherwise there is no use from this memoization :)

[github-actions]

Hey! This is your new endpoint: https://fac35a66.widget-animateexe.pages.dev

[github-actions]

Hey! This is your new endpoint: https://9251e4a1.widget-animateexe.pages.dev

[vinzenzLIFI]

🤖 The following is an extract from the QA Agent Analysis of this PR. Sharing these findings early so they can be addressed before QA execution begins.

---

Code Inspection Findings

🔴 Must address before merge

staggerQueue singleton breaks multi-widget isolation (staggerQueue.ts:2-4)
let pending, let lastFlushAt, and let timer are module-level globals — a single shared queue across all widget instances on a page. When two LiFiWidget instances execute routes concurrently, Widget B's enqueueStaggered call overwrites Widget A's pending callback. Widget A's route update is silently dropped. Needs either per-instance queue isolation or an explicit decision to drop multi-widget support with documentation.

WidgetEvent.RouteExecutionUpdated is now a breaking change for integrators
emitter.emit(RouteExecutionUpdated …) is now called inside enqueueStaggered, so intermediate events fired within the 1200 ms window are silently dropped. Pre-PR: one event per SDK callback. Post-PR: at most one event per 1200 ms, with intermediate ones lost. Integrators tracking per-step progress via this event will silently stop receiving updates — they won't notice until production. Needs a CHANGELOG entry or migration note before merge.

.claude/launch.json accidentally committed
VS Code debug config was included in the diff. Reviewer already flagged it with no response yet — worth resolving before further review rounds.

---

🟡 Should fix

getTransactionLink missing useCallback defeats memoization (useExplorer.ts:60, StepActionRow.tsx)
getTransactionLink is defined inline without useCallback, producing a new function reference on every render. useMemo in useExecutionRows lists it as a dependency, so the memo recomputes on every render. On the transaction page with active timer re-renders this means continuous row re-derivation. Flagged in an open review thread — hasn't been resolved yet.

---

🔵 Worth noting

visibility: hidden in StaggeredRevealTypography has no timeout fallback (StaggeredRevealTypography.tsx:36)
Text is invisible until document.fonts.ready resolves. The promise does resolve on font failure in all modern browsers, so this is safe in practice — but a code comment explaining the assumption would help future readers.

Index-based AnimatePresence keys on route restart (ChecklistSection.tsx:59)
key={\row-${index}`}` is stable for append-only growth but on a route restart, FAILED rows are removed and then re-added at the same indices — producing spurious enter animations. Low visual impact, easy to fix with stable IDs derived from action type or txHash.

---

Full test plan including 19 test cases, automation guide, and exit criteria available on request.