release: sync SDK + MCP to omnigraph-server v0.9.0

[aaltshuler]

Syncs the SDK and MCP server to the released omnigraph-server v0.9.0, building on the v0.8.1 sync commit (this branch contains it, so merging this supersedes #14, #15, and #16).

What's in it

• omnigraph.serverVersion + both package versions pinned to 0.9.0; spec/openapi.json and generated types regenerated from the v0.9.0 tag via the scripted pipeline (no hand-patching)
• New binding: loadNdjson() for the one new 0.9.0 endpoint, POST /load/ndjson (strict bounded graph-level NDJSON batch, application/x-ndjson). The transport gains a rawBody option — verbatim payload with explicit Content-Type, bypassing the JSON + case-conversion pipeline — with a test pinning that the NDJSON body and user-schema keys pass through untouched
• MCP version-pin assertions moved to 0.9.0

Verification

• check-drift: spec matches upstream at v0.9.0
• check-versions: all packages target 0.9.0
• check-coverage: 18/18 spec operations bound (3 intentionally unbound), query params validated
• typecheck + build clean; SDK 87 tests green, MCP 14 tests green

Notably, 0.9.0's wire surface is otherwise additive over the 0.8.1 sync — no existing binding changed shape. The 0.9.0 behavior changes (newest-first commit listings, strict append, keyed-write 413 bounds, 503 recovery_required) are server-side semantics the SDK already models via the error taxonomy.

Greptile Summary

This release synchronizes the SDK and MCP packages with omnigraph-server v0.9.0.

• Pins package and advertised server versions to 0.9.0.
• Regenerates the OpenAPI-derived types for the v0.9.0 API surface.
• Adds loadNdjson with verbatim application/x-ndjson transport support.
• Updates SDK and MCP tests for the new version and load endpoint.

Confidence Score: 4/5

The PR is not yet safe to merge because v0.9.0 resource-limit and recovery-required responses remain indistinguishable from generic internal failures.

The generated contract now declares HTTP 413 and 503 responses, but the shared runtime error dispatcher has no mappings or public error classes for either condition and therefore converts both into InternalServerError.

Files Needing Attention: packages/sdk/src/errors.ts, packages/sdk/src/index.ts

Important Files Changed

Filename	Overview
packages/sdk/src/client.ts	Adds the graph-scoped loadNdjson binding and forwards branch, source branch, and mode as query parameters.
packages/sdk/src/transport.ts	Adds a raw request-body path that preserves NDJSON bytes and sets an explicit content type.
packages/sdk/src/generated/types.gen.ts	Regenerates the API models and operation declarations from the omnigraph-server v0.9.0 specification.
packages/sdk/src/types.ts	Exposes camel-cased graph-batch output types and the hand-written LoadNdjsonInput contract.
packages/sdk/test/client.test.ts	Adds coverage for the loadNdjson URL, content type, verbatim payload, and response conversion.
packages/mcp/src/version.gen.ts	Updates the MCP package version reported during initialization to 0.9.0.

Sequence Diagram

sequenceDiagram
    participant Caller
    participant SDK as Omnigraph SDK
    participant Transport
    participant Server as omnigraph-server v0.9.0
    Caller->>SDK: loadNdjson(input)
    SDK->>Transport: POST /load/ndjson + query options
    Transport->>Server: application/x-ndjson body (verbatim)
    Server-->>Transport: GraphBatchLoad response
    Transport-->>SDK: camel-cased result
    SDK-->>Caller: GraphBatchLoad

Loading

_{Reviews (2): Last reviewed commit: "test: exercise loadNdjson end-to-end and..." | Re-trigger Greptile}

[greptile-apps]

Actionable errors become internal failures

When v0.9.0 returns a 413 resource-limit response or a 503 recovery-required response, fromResponse() has no mapping for either status and produces InternalServerError, preventing callers from distinguishing a request that must be split or a recovery operation that must be resolved from a generic server failure.