Update zerion extension

[zerts]

Description

AI functionality for Zerion Extension. Based on the London Hackathon project

Screencast

Zerts.Screenshot.2025-03-07.at.18.32-converted-converted.mp4

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for your contribution! 🎉

🔔 @qd-qd @zerts you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

You can expect an initial review within five business days.

[greptile-apps]

PR Summary

This PR adds comprehensive AI functionality to the Zerion extension, introducing new tools for blockchain interactions and wallet management along with AI evaluation tests.

• Several tools lack proper error handling for API failures and input validation, particularly in check-portfolio.ts, look-wallets.ts, and search-blockchain.ts
• Typos found in package.json tool descriptions: "breif" should be "brief" and "ususlly" should be "usually"
• The CHANGELOG.md entry for "Zerion AI Extension" is missing description of the actual changes/features
• The auto-detection of best chain functionality mentioned in comments for create-a-swap-link.ts is not implemented
• The 10-address limit in look-wallets.ts should be documented in the function's description

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

_{9 file(s) reviewed, 19 comment(s)
Edit PR Review Bot Settings | Greptile}

[zerts]

Hey @pernielsentikaer !
Do I need to do anything else about this pull request?
Just checking :))

[pernielsentikaer]

Our AI team will pick it up 😊

[pernielsentikaer]

Hi @zerts 👋

Can you look into the CI errors so we can continue the review 👋

[zerts]

Hi @zerts 👋

Can you look into the CI errors so we can continue the review 👋

Looking into it!

[zerts]

Hey @pernielsentikaer !
Not sure why, but after I run npm run publish, this branch was removed and a new pr was openned. Is this expected?
Looks like I filed something during the merge process 🫠
#19132

[pernielsentikaer]

It should normally just update this PR. Thanks for flagging 😊

[zerts]

@pernielsentikaer , thank you for the response.
What should I do with this?
Should I prepare new PR the same way this was? Or we can somehow restore this one? :)

[zerts]

I see! Thank you!