feat: 30.2 — unified api surface

[vieiralucas]

Summary

Update Ruby SDK to match the unified proto API from Story 30.1:

• Proto: Copied new service.proto and regenerated Ruby code. BatchEnqueue RPC removed. EnqueueRequest now contains repeated EnqueueMessage. AckRequest/NackRequest use repeated AckMessage/NackMessage. ConsumeResponse only has repeated Message messages.
• enqueue: Wraps single message in EnqueueMessage, sends via unified Enqueue RPC, parses per-message EnqueueResult (with typed EnqueueError).
• enqueue_many: Replaces batch_enqueue. Same semantics, no "batch" prefix. Returns Array<EnqueueResult>.
• ack/nack: Wrap in repeated AckMessage/NackMessage, parse first AckResult/NackResult with typed error codes.
• consume: Only reads repeated messages field (singular message field removed from proto).
• Batcher: Uses unified Enqueue RPC for all batch sizes (no more BatchEnqueue split).
• BatchEnqueueResult -> EnqueueResult: Renamed, no "batch" prefix.
• Version bumped to 0.4.0.

Test plan

• TestEnqueueResult unit tests pass (success/error result construction)
• TestEnqueueMany integration tests pass (multiple, single, empty, mixed success/failure)
• TestAutoBatching integration tests pass (single, concurrent, nonexistent queue)
• TestLingerBatching integration tests pass
• TestDisabledBatching integration tests pass
• TestBatchModeValidation unit tests pass
• TestCloseFlush integration tests pass
• TestClient integration tests pass (enqueue/consume/ack, nack redeliver, nonexistent queue)
• TLS/auth tests unaffected

---

Summary by cubic

Updates the Ruby SDK to the unified proto API (Story 30.2), replacing batch RPCs with a single Enqueue path and adding typed, batched Ack/Nack. Introduces enqueue_many, renames the batch result to EnqueueResult, improves batcher/error handling, and bumps to v0.4.0.

• New Features

  • Unified proto: EnqueueRequest takes repeated EnqueueMessage; ConsumeResponse only has messages; typed error codes for enqueue/ack/nack; StreamEnqueue RPC scaffolded.
  • Client API: added enqueue_many; enqueue wraps a single EnqueueMessage; ack/nack send batched requests, parse typed errors, and raise RPCError when no result is returned.
  • Batcher: always uses Enqueue; centralized result/error handling; minor refactors and lint fixes.

• Migration

  • Replace batch_enqueue(...) with enqueue_many(...).
  • Replace BatchEnqueueResult with EnqueueResult.
  • consume now only reads the messages field.
  • ack/nack keep the same call shape but now raise typed errors (and RPCError if the server returns no result).

^{Written for commit 88a334a. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 9 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="lib/fila/client.rb">

<violation number="1" location="lib/fila/client.rb:155">
P2: A nil result silently returns success instead of raising an error. Since this sends exactly one message, receiving zero results is an error condition. This is inconsistent with `enqueue_single` which correctly raises `RPCError` when result is nil.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}