[ShadowOfTime1]

Closes #124

get_token_balance answered a token it couldn't resolve with the bare Unknown token ... text. isRefusal() was false for it, so a scripted run finished with exit 0 after a balance read that never happened. The send path already wraps the same explanation as Refused: ... (cli.mjs), so the balance read now does the same in runAction. The known-symbol and contract-address guidance is unchanged, and so is the empty-catalog wording, just prefixed.

Tests:

• test/tools.test.mjs: "NOT_A_TOKEN", "", 0 and false are refusals through both runAction and native dispatchToolCall, and each still carries "Use a token contract address" and the known-symbol list.
• test/native-tools-cli-exit.test.mjs: a new unknown-token scenario in the shimmed model runs the real dist/cli.mjs. The model reads NOT_A_TOKEN, gets the refusal, then replies normally, and the process still exits 1 with the Refused: Unknown token "NOT_A_TOKEN" line in the transcript.
• The Answer an unreadable token identifier instead of throwing on it #123 control "an unknown symbol keeps the existing missing-token message rather than becoming a refusal" and the empty-catalog test now expect the refusal, since this issue changes exactly that. Everything else in them stays: MON is still native, a padded address still resolves, and Answer an unreadable token identifier instead of throwing on it #123's unreadable-value handling is untouched. Parser and send path are unchanged.

Without the one-line change, the four affected tests fail.

Verification: npm run build and npm test. The changed tests all pass. Locally the MCP subprocess tests fail on my machine, the same 12 on clean main as on this branch, so they are environment-related and not touched here.

[portdeveloper]

lgtm, thanks