Kaoru0822andClaude Opus 5.5 f7250fe35f fix(kuna): say why Kuna cannot answer instead of a generic message (#4113) ...

Kuna capability gaps such as "no code at this address" or "no function node
at this address" were built without a user message, so MCP and the CLI
showed only "This analysis is unavailable for the current target. Choose
another analysis or target." and kept the reason in details. One Kuna
helper now presents the reason as the message for every such gap, and the
unsupported-operation reason names call relationships and xrefs, which Kuna
now answers.

Refs #1957

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-15 07:37:20 -07:00

..

acceptance

perf(tests): reuse CLI compilation for exported binding checks

2026-10-15 19:00:04 +08:00

boundary

fix(kuna): say why Kuna cannot answer instead of a generic message (#4113)

2026-10-15 07:37:20 -07:00

composition

fix(managed): project metadata with empty names without a display label (#3853)

2026-10-14 22:22:59 -07:00

conformance

test(ghidra): align MIPS verifier ABI and snapshot expectations

2026-10-15 22:00:16 +08:00

evaluation

fix(hopper)!: verify current Linux releases with the publisher key

2026-10-15 12:15:55 +08:00

fixtures

fix(browser): bound CDP handshakes and command responses (#3555)

2026-10-15 15:55:29 +09:00

process-global

fix(apktool): own the version probe's process group and keep its timeout typed (#3808)

2026-10-14 21:37:52 -07:00

support

perf(tests): reuse CLI compilation for exported binding checks

2026-10-15 19:00:04 +08:00

ciTestSequencer.ts

ci: finish main validation and balance complete test costs

2026-10-13 18:54:05 +08:00

processOwnershipRunner.ts

test(process): retire native caches at worker teardown

2026-10-09 04:12:49 +08:00