fix: guard handle_sdk_message against non-map JSON

[pshoukry]

Summary

The Claude CLI can emit non-map JSON values (true, [1,2,3], 42, …) on stdout alongside the normal stream-JSON output — for example, when a hook callback fails and a Zod schema validation error is logged. ClaudeCode.CLI.Control.classify/1 falls through to {:message, json} for any non-map, so without a guard the subsequent ClaudeCode.Adapter.Port.handle_sdk_message/2 clauses call json["type"] — which invokes Access.get/3 on the non-map and crashes the Port GenServer with a FunctionClauseError, aborting the in-flight session.

Fix

Add a when not is_map(json) clause to handle_sdk_message/2 that logs and drops the offending chunk so the session continues:

defp handle_sdk_message(json, state) when not is_map(json) do
  Logger.warning("Dropping non-map SDK message: #{inspect(json)}")
  state
end

Test

New integration test in port_integration_test.exs that uses the existing MockCLI helper to stream true, [1,2,3], and 42 between a system message and the final result, then asserts the session completes and returns the expected %ResultMessage{}. Full suite (1492 tests) passes.

Repro context

This was hit in a downstream SDK consumer when a hook returned an unexpected shape and the CLI printed Zod validation diagnostics on stdout. Without the guard the entire session terminates the moment that line is processed — even though the actual model output is fine and the result message arrives right after.

[guess]

@pshoukry thanks for the PR!

Looks like dialyzer is failing. I'm thinking we could maybe do this check one level higher at process_line and not even try to classify if json is not a map. Then we won't incorrectly classify it as an sdk message to begin within.

Something like this:

{:ok, json} when is_map(json) ->
    case Control.classify(json) do ...

{:ok, non_map} ->
    Logger.warning("Dropping non-map CLI output: #{inspect(non_map)}")
    state

{:error, _} ->
    Logger.debug("Non-JSON CLI output: ...")
    state

What do you think?

[pshoukry]

@guess sounds good, please check.

[pshoukry]

@guess I applied the fix as you suggested. please check.

[guess]

@pshoukry looks like a test is failing

[pshoukry]

The error looked to me like a network error and I wasn't sure if that passed before. I will take a deeper look.

[pshoukry]

@guess I pushed a fix vs the flaky test that fails locally and pushed again. I think rerunning the test suite would have passed since this error seems to be intermittent.