JSON protocol

Every command prints exactly one JSON value to stdout and exits 0. A runtime failure prints a single {"error": "..."} value and exits 1, so stdout is always valid JSON. (Clap usage errors for unknown flags/subcommands still go to stderr with exit 2.)

Real example — opening the repo’s tests/fixtures/raw-x64.bin:

$ binscout load tests/fixtures/raw-x64.bin
{"annotations":0,"arch":"x86_64","binary":"tests/fixtures/raw-x64.bin","blocks":1,"content_hash":13197063251454239466,"db_path":"tests/fixtures/raw-x64.rsdbg.redb","entry":null,"entry_hex":null,"format":"raw","functions":1,"insns":3,"reason":null,"size":3,"strings":0,"supported":true,"version":"0.2.1","xrefs":0}

functions and xrefs paginate with --offset/--limit; strings pages with --start/--limit (--offset is a deprecated alias that warns). Limits cap server-side at 1024 rows. xrefs returns a {"total", "xrefs"} envelope where total is the filter-matched count before paging, so large result sets page without scanning blind. Its per-row offset field is the byte offset of the hit, not the page position. disasm and ir decode at most 1 MiB per call and report trailing bad bytes in error_at instead of failing, so the valid prefix is always usable.