0.6.1

Gemini 3.8 Flash and GPT-6 Astra on the wire, plus the weekly peer sweep

The first cohort produced by the weekly maintenance sweep. Two new frontier models landed in the corpus within three days of their releases, every companion library moved a patch or a minor (the two agent-framework peers themselves, @openai/agents 0.17.0 and @google/adk 2.0.0, stayed put), and one new error shape gets a lossless home. The wire vocabulary is untouched — AGJSON_VERSION stays 1.0.0-draft.3.

Gemini 3.8 Flash — verified, and now the ADK capture default

gemini-3.8-flash went GA on 2026-09-02 with the same thinking knob and the same price as 3.7. The corpus carries a live trio for it (echo, MCP Apps card, thinking with thought summaries and signatures), captured through the unchanged @silverprotocol/google-adk facet on the unchanged @google/adk 2.0.0 peer, with @google/genai 2.21.0, whose only change is the new model id. The census found nothing new on the wire, and the token identity from draft.3 holds on every event. The e2e capture default for ADK moves to 3.8; consumers do not need to change anything.

GPT-6 Astra — captured on both OpenAI paths

gpt-6-astra (2026-09-03) reasons on every request, rejects temperature/top_p, and offers no dated snapshot. It is now a standing seed on both @silverprotocol/openai-agents (via @openai/agents 0.17.0 with the openai client at 7.10.0) and @silverprotocol/vercel-ai (ai 7.0.93). Neither facet needed a code change, and neither capture path sends the rejected parameters: the Vercel provider strips temperature/top_p for reasoning models, while the Agents SDK forwards whatever you set, so do not set them for Astra. What the captures showed:

  • The Vercel path streams a reasoning item with no text, normalized to reasoning.start/reasoning.end, and 13 reasoning tokens (the raw wire also echoes reasoningContext: "all_turns"); the Agents SDK path chose not to reason for the echo.
  • OpenAI stamps a new response-level attribute, access_programs.cyber, on every Astra response. It is program-tier metadata, not turn content, and is treated like service_tier.
  • The capture default for the OpenAI family stays gpt-5.6-sol for now (Astra lists at $10/$50 per MTok against Sol’s $4/$20 and cannot stop reasoning; the choice is with the founder).

One new lossless carry: misalignment errors

openai-node 7.10.0 adds error.misalignment (error_type, detailed_explanation, and a steer.message continuation instruction) beside the misalignment_policy_violation code on response.failed. The openai-agents facet now emits it verbatim as a turn-scoped ext.openai.misalignment event immediately before the turn.error it annotates — a safety classification a host should be able to show. Absent, nothing changes. The documented auto-stop only fires on persisted-reasoning, WebSocket, or compaction requests, so this is synthetic-tested.

Peer sweep

  • @anthropic-ai/claude-agent-sdk 0.3.261: user_message_uuids (every client uuid a merged or queued turn answered) now rides the same three channels as user_message_uuid; a few remote-session latency fields are recognised as router-plane. All six Claude seeds were refreshed at 0.3.261 with a clean census.
  • ai 7.0.93 trio: typed surface byte-identical; usage.raw now carries the provider’s complete usage object.
  • Toolchain: Vitest 5 (note for contributors: runs from packages/e2e must pass --config ../../vitest.config.ts; pnpm e2e:capture does), astro 7.3.1 on the site.

The compatibility tables on each npm page carry the dated evidence.