Fix inline JSON being incorrectly detected as tool call

The bug was caused by mark_tool_calls_consumed() being called after
displaying each chunk, which advanced last_consumed_position to the
end of the current buffer. When the next chunk arrived with JSON,
the unchecked_buffer started at position 0 of the slice, causing
is_on_own_line() to return true (position 0 is always "on its own line").

Removed the problematic mark_tool_calls_consumed() call from the
"no tool executed" branch. The remaining call after actual tool
execution is correct and necessary.

Added integration test that verifies inline JSON in prose is not
detected as a tool call.

crates/g3-core/src/lib.rs

@@ -2432,11 +2432,6 @@ Skip if nothing new. Be brief."#;
                                     self.ui_writer.print_agent_response(&filtered_content);
                                     self.ui_writer.flush();
                                     current_response.push_str(&filtered_content);
-
-                                    // Mark parser buffer as consumed up to current position
-                                    // This prevents tool-call-like patterns in displayed text
-                                    // from triggering false positives in has_unexecuted_tool_call()
-                                    parser.mark_tool_calls_consumed();
                                 }
                             }
                         }