fix: reject unknown token symbols with error instead of allowing continuation (Vibe Kanban)

[MinaraAgent]

Summary

• Modified lookupToken() in src/utils.ts to throw an Unknown token error when a token cannot be resolved, instead of returning the raw input and allowing the flow to continue
• Removed the previous behavior that would warn and return { address: tokenInput } for unknown tokens
• Updated the catch block to properly re-throw "Unknown token" errors and throw a clear error for any other lookup failures

Changes Made

src/utils.ts - Modified the lookupToken() function:

• Before: When no token was found, the function would log a warning (for ticker inputs) and return { address: tokenInput }, allowing invalid tokens to proceed through the flow
• After: Throws Error("Unknown token: ${tokenInput}") immediately when token lookup fails, preventing invalid tokens from reaching the confirmation step

Why This Matters

Previously, when a user entered a fictional/unknown token symbol like $FAKETOKEN, the CLI would:

1. Warn that no token was found
2. Pass the invalid token through to the confirmation screen
3. Only fail at execution time

Now, the CLI:

1. Throws an error immediately during token lookup
2. The error is caught by wrapAction() and displayed cleanly to the user
3. Process exits with code 1, preventing any further action

This affects all commands that use lookupToken():

• swap
• transfer
• withdraw
• limit-order

Testing

• TypeScript compilation passes (tsc --noEmit)
• Manual testing with fictional token symbols will now show: ✖ Unknown token: $FAKETOKEN

---

This PR was written using Vibe Kanban

[gemini-code-assist]

Code Review

This pull request updates project dependencies and modifies the lookupToken utility in src/utils.ts to throw errors instead of returning partial data when a token cannot be found. Review feedback suggests refining the error handling to distinguish between API failures and missing tokens for better user clarity. Additionally, the catch block should be updated to avoid masking prompt cancellations or other system errors as 'Unknown token' issues, which currently interferes with the CLI's ability to exit gracefully.