[rekram1-node]

Problem

Several AI gateway, experimental, media, and protocol modules duplicated inline Schema.Record(...) definitions (JsonObject, ProviderMetadata, ProviderOptions), manual HttpContext construction from HttpClientResponse, and manual totalTokens summation instead of reusing the shared helpers in protocols/shared.ts, schema/options.ts, and route/executor.ts.

Change

Reuse JsonObject, ProviderMetadata, ProviderOptions, ProviderShared.totalTokens, and responseHttp across system-one.ts, vercel-ai-gateway.ts, realtime.ts, route/media-protocol.ts, media.ts, and protocols/venice-chat.ts.

 packages/ai/src/
 ├── experimental/
 │   ├── realtime.ts          # RequestExecutor.responseHttp(res)
 │   └── system-one.ts        # JsonObject, ProviderMetadata, RequestExecutor.responseHttp, ProviderShared.totalTokens
 ├── media.ts                 # responseHttp(response) via route/executor-service.ts
 ├── protocols/
 │   └── venice-chat.ts       # [JsonObject] rest schemas
 ├── providers/
 │   └── vercel-ai-gateway.ts # ProviderMetadata, ProviderOptions, JsonObject, RequestExecutor.responseHttp
 └── route/
     ├── executor-service.ts  # hosts leaf responseHttp + headerDetails to avoid schema/media cycle
     ├── executor.ts          # re-exports responseHttp
     └── media-protocol.ts    # RequestExecutor.responseHttp(response)

Target	Before	After
Rest record schemas (system-one, vercel-ai-gateway, venice-chat)	[Schema.Record(Schema.String, Schema.Any | Schema.Unknown)]	[JsonObject]
Nested provider metadata (system-one, vercel-ai-gateway)	Schema.Record(Schema.String, Schema.Record(Schema.String, Schema.Unknown))	ProviderMetadata
Evaluation providerOptions (vercel-ai-gateway)	Schema.Record(Schema.String, Schema.Unknown)	ProviderOptions
Response HTTP context (system-one, vercel-ai-gateway, realtime, media-protocol, media)	new HttpContext({ url, status, headers })	RequestExecutor.responseHttp(res) / responseHttp(res)
Usage token total (system-one)	inline input_tokens + output_tokens	ProviderShared.totalTokens(...)

Out of scope

• Changing wire schemas or runtime behavior of evaluation, realtime, media, or Venice chat routes.

[opencode-agent]

This looks sound to me. I checked each replaced inline schema against the shared definition, and they match: JsonObject and ProviderOptions are Record(String, Unknown), and ProviderMetadata is the same nested record. ProviderShared.totalTokens(in, out, undefined) also matches the old inline sum. responseHttp now turns header values into strings, as the executor path already did. Moving it into executor-service.ts doesn't create a new import cycle. In packages/ai, bun run typecheck passes and bun test gives 1826 pass, 0 fail.

Public API: unchanged. route/index.ts still re-exports only responseHttp and Service from executor.ts, so headerDetails stays internal.