[BeeHiveTeam]

Closes #130

What was wrong

prepareTokenSend checked for an empty token with String(input).trim(), and String() throws on an object that cannot become text. Native tool calling passes the model's arguments to handleAction as parsed JSON (src/nativeToolLoop.mjs:76), so {"toString": null} as the token made the loop report Error: Cannot convert object to primitive value where every other bad value gets a Refused: with a reason.

The change

The empty check is total. An identifier that cannot be read is not blank, so it reaches resolveToken, whose existing catch refuses it as invalid token "<unprintable>": Cannot convert object to primitive value — the reason the read path has given since #123. Blank strings are still no token specified. Nothing else in the send path changes.

Verified

Through prepareTokenSend, in test/send-token.test.mjs, with a getMetadata seam that fails the test if it is called:

• {"toString": null} and an object with no prototype are refused with the read path's exact reason.
• "" and " " are still no token specified.
• "USDC" still prepares.

Red, then green:

• On main (3027c41): the two unreadable cases fail (they throw); the blank and USDC cases pass, as they should.
• Mutations: treating the unreadable object as blank fails both unreadable cases; dropping the blank check fails the blank case; rewriting !String(input).trim() as String(input).trim() === "" passes.
• End to end, send_token through dispatchNativeCall and the loop's own catch: {"toString": null} → Refused: invalid token "<unprintable>": … (was Error: Cannot convert object to primitive value); {} and "USDC" unchanged.

npm test 633/633 and npm run build on Node 22. One of eight full runs had a single failure that did not reproduce in the other seven; it was not in send-token.test.mjs, whose cases are pure and ran green in every run.