feat: add Search for the runtime's /v1/search endpoint

[claudespice]

What

Adds SpiceClient.Search(ctx, *SearchRequest), wrapping the runtime's /v1/search endpoint — vector similarity search, with optional Keywords for a hybrid lexical + vector ranking.

limit := 3
resp, err := spice.Search(ctx, &gospice.SearchRequest{
    Text:              "tokyo plane tickets",
    Datasets:          []string{"app_messages"},
    Limit:             &limit,
    AdditionalColumns: []string{"timestamp"},
})

Why

/v1/search works on a default spice run, but of the six client SDKs only spice.js could reach it. Go users had to hand-roll the HTTP call, including the response shape.

Part of aligning capabilities across the SDKs against the runtime's own API surface.

Two details the response types encode, taken from the runtime's wire format rather than the OpenAPI example (which is out of date on the first point):

• Matches holds a slice of values per column — one column can contribute several chunks to a single match.
• data, primary_key, and metadata are omitted by the runtime when empty, so each decodes to an empty map rather than being required.

Errors follow the pattern in datasets.go but also read the response body: the runtime explains search failures in plain text ("No data sources provided"), which a status code alone loses. Arguments the runtime would reject with a 400 — empty text, a Limit below 1 — are checked before the request so the error names the field to fix. An empty Datasets slice is omitted rather than sent, since the runtime 400s on an empty list.

Verification

• go build ./...
• go vet ./...
• gofmt -l . — clean
• go test -run TestSearch ./... — 11 tests pass (6 top-level, 7 subtests), driven by httptest so they need no live runtime
• Full go test ./... — not run; the rest of the suite requires a live runtime (spice run) and a cloud API key

The new tests are runtime-free, so TestSearch is added to the -run allowlist the Windows-native unit test job uses. They also run in the full post-install suite on the other platforms.

[Copilot]

🟡 Not ready to approve

Response map fields documented as decoding to empty maps will currently decode as nil when omitted, which can violate the intended API contract and surprise callers.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Pull request overview

Adds first-class Go SDK support for the Spice runtime /v1/search endpoint by introducing a typed SpiceClient.Search API, along with runtime-free unit tests and accompanying documentation/CI updates to keep capabilities aligned across SDKs.

Changes:

• Introduces SearchRequest, SearchResponse, and SearchMatch types plus SpiceClient.Search(ctx, req) to call POST /v1/search.
• Adds httptest-based unit tests covering request encoding, routing/method, response decoding, validation, and error surfacing.
• Documents Search usage in the README and updates the Windows unit-test allowlist to include TestSearch.

File summaries

File	Description
search.go	Implements the SpiceClient.Search method and associated request/response types for /v1/search.
search_test.go	Adds runtime-free tests for request/response behavior and error/validation handling.
README.md	Documents how to use Search and explains key request/response fields.
.github/workflows/go.yml	Extends the Windows-native unit test allowlist to run TestSearch.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 2
• Review effort level: Lite

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.