Feature Request: Align with and take inspiration from JulienBreux/antigravity-sdk-go

Description & Motivation

Take a close look at JulienBreux/antigravity-sdk-go and compare features, response types, tool calling interfaces, hooks, triggers, and runtime abstractions to see if there are gaps or areas for improvement in our Ruby SDK (antigravity-ruby-sdk).

Key Areas to Investigate & "Scopiazzare" (Borrow/Incorporate):

1. Response & Tool Call Parity:
   • Verify compatibility of Gemini/Antigravity response parsing, streaming responses, and structured tool calls.
   • Check how tool definitions and parameter schemas are mapped and validated.
2. Architecture & Modular Subsystems:
   • hooks/: Lifecycle hooks for agent runs (pre-tool, post-tool, on-error, on-completion).
   • triggers/: Event-driven or condition-based triggers for starting/resuming agent loops.
   • connections/ & conversation/: Stateful session management, multi-turn history handling, and transport abstractions.
3. Runtime & Harness Management:
   • How localharness discovery, environment fallbacks (ANTIGRAVITY_HARNESS_PATH vs local bin/ vs system PATH), and zero-python bootstrapping are handled.
4. Developer Experience & DX:
   • Idiomatic Ruby DSL equivalents for the patterns Julien Breux introduced in Go.

Goal / Acceptance Criteria

• Audit Go SDK vs Ruby SDK feature parity.
• Identify missing abstractions (e.g., hooks, triggers, schema helpers).
• Add missing capabilities to antigravity-ruby-sdk to keep the Ruby implementation best-in-class!

Created automatically by Ermete Bottazzi 🪽🚛 on behalf of Riccardo.

Start by comparing the Ruby SDK with JulienBreux/antigravity-sdk-go, focusing on response parsing, streaming, tool calls, hooks/, triggers/, connections/, conversation/, and localharness handling. Document feature parity and missing abstractions, then use the acceptance criteria to determine whether the audit and any agreed capabilities are complete.