Release v0.1.13

v0.1.13

Token inputs accept hex strings

Every tool that takes an MDToken (decompile_by_token's token, and method_token on decompile_method, find_callers, find_references, find_callees, find_overrides, search_members, get_method_il, patch_method_il, revert_method_il, force_return, nop_method) now accepts a 0x-prefixed hex string in addition to a decimal uint. A leading # is tolerated too.

This removes a needless conversion step: dnSpy's UI shows tokens as hex (0x06000001), and this server's own signature/ambiguity/error messages emit #0x06000001 — so a token copied straight from either now works as-is, instead of having to be converted to decimal first.

• Additive and backward compatible: decimal tokens work exactly as before.
• The token parameters' JSON Schema is widened to ["integer", "string"] so MCP clients don't reject a hex string at validation time.

Thanks to @r0x5a (#22).

Internal

• Test harness now discovers dnSpy's actual extension directory instead of hardcoding it, and prints a diagnostic on startup timeout. No effect on the shipped extension.