Skip to content

v0.19.0

Choose a tag to compare

@sasan1200 sasan1200 released this 10 Oct 00:16
· 16 commits to main since this release
v0.19.0
23a0abd

Added

  • Canonical HTTP integration guide with explicit published/development boundaries
    and native HTTP consumer examples checked against the packed candidate.

  • RawHttpApiClient.consumeResponse for consuming a response while retaining
    caller cancellation and the HTTP request deadline.

  • Optional RuntimeRunErrorDetails on run statuses, failed stream events, and
    facade stream outcomes, carrying observed provider code/type/reason strings.
    Codex response/stream and Claude Messages stream mappings preserve available
    details alongside existing diagnostic messages and lifecycle behavior.

  • waitForRun, RunWaitOptions, and RunWaitResult from the root and
    contracts: bounded sequential retrieval of an existing run with a local
    deadline, poll budget, and caller cancellation. Stopped waits retain the last
    observed run; backend work and in-flight HTTP requests are not cancelled.

  • Opt-in requireCompletedRun, requireRunText, requireCompletedStream, and
    requireStreamText helpers from the root and core/runtime. They enforce
    observed completion and required text with typed run errors, retain original
    error causes, preserve explicit empty output, and leave provider behavior
    unchanged. Development examples demonstrate answer services and streaming.

  • Run outcome error vocabulary: ApiClientErrorType.Run and
    ApiClientErrorCode.RunFailed, RunCancelled, RunIncomplete, and
    RunOutputMissing. These additive codes distinguish execution failures,
    cancellation, unobserved completion, and absent required output without
    changing provider return values.

Removed

  • Breaking in 0.19.0: remove the discontinued Gemini provider,
    its runtime/files subpath exports, and its capability declarations. Gemini
    configuration is not redirected to AGY; migrate explicitly with AGY service
    configuration or another supported provider. Historical published declarations
    remain in versioned references.

Fixed

  • Generate new-release contract evidence from the inspected npm declarations
    without requiring a pre-existing source manifest. Preserve strict validation
    for unrelated missing evidence files and release identity mismatches.

  • Release dry-run reports reject detached manifests that differ from archive
    provenance. Archive inspection and hashing use the same captured bytes.

  • Host ingestion checks accept the canonical docs/api-client/v{VERSION}
    release archive layout, preserve root and single-folder layouts, reject
    ambiguous documentation roots, and clean up failed extraction attempts.
    Documentation releases require this check before asset upload and dispatch.

  • Preserve caller-supplied HttpApiError cancellation reasons through JSON and
    gateway Fetch helpers instead of converting them into GatewayHttpError.

  • Classify JSON HTTP failures by parse-error identity instead of diagnostic
    message text. Paths containing returned invalid JSON no longer bypass
    GatewayHttpError status and backend-code handling.

  • Accept mixed-case JSON content types in gateway JSON and form-data response
    parsing instead of rejecting valid JSON responses as protocol mismatches.

  • Configure half-duplex for ReadableStream HTTP request bodies so native Node
    Fetch can send streamed uploads through core and gateway clients.

  • Forward Fetch integrity, keepalive, mode, priority, referrer, and referrer-policy
    controls through core and gateway HTTP requests instead of silently discarding
    them. Add optional matching fields to HttpApiRequestInit.

  • Preserve existing query strings and URL fragments in withQuery instead of
    adding a second ? or placing request parameters after the fragment.

  • Preserve Fetch's redirect policy through core and gateway HTTP requests,
    so explicit manual and error policies prevent following redirects.

  • Preserve HEAD and OPTIONS when converting Fetch requests instead of
    silently sending GET. Extend HttpApiHttpMethod with both methods.

  • Release unread successful response bodies in Claude Managed Agents environment,
    session, resource, memory-store, memory, vault, and credential deletion helpers.
    Preserve bodyless acknowledgements and successful results if disposal rejects.

  • Release unread successful response bodies in gateway status acknowledgements
    and Hermes approval resolution, including its gateway alias. Body cleanup
    preserves successful acknowledgements and caller-owned raw streams.

  • Keep library JSON response body reads inside the HTTP request lifetime so
    caller cancellation and deadlines remain active during consumption.

  • Keep gateway JSON, blob, and form-data response body reads inside the HTTP
    request lifetime so caller cancellation and deadlines remain active. Raw
    gateway responses retain caller-owned stream lifetimes.

  • Preserve Fetch RequestInit.headers when converting with toHttpRequestInit,
    including records, tuple lists, and Headers instances. An explicit second
    argument retains its existing replacement behavior.

  • Omit engine-generated response excerpts from HTTP invalid-JSON error messages
    so truncated credentials cannot bypass the redacted body preview. Preserve
    response status and the original body on HttpApiError.

  • Reuse dependency parsing and resolution within ownership guardrail scans to
    reduce scan timeouts. Each scan uses fresh caches; boundary assertions and
    timeout limits are unchanged.

  • Merge HTTP header names case-insensitively. Request overrides replace client
    defaults, configured credentials retain precedence, and explicit idempotency
    keys and content types no longer become comma-joined duplicates.

  • Forward caller headers to the run-start request in streamHermesChatRun
    and its streamGatewayChatRun alias, keeping routing and tenant headers
    consistent with the subsequent event stream.

  • Keep Hermes chat run-start deadlines and caller cancellation active during
    response parsing. Remove chat stream abort listeners and dispose subscriptions
    when the stream completes, fails, or its consumer throws.

  • Publish a fresh tarball from the verified release checkout rather than the
    pinned documentation reference artifact. Keep stable docs verification and
    npm publication inputs separate.

  • Keep HTTP timeouts and caller cancellation active through JSON, blob, file,
    and batch-result body reads. Raw responses retain caller-owned stream lifetimes.

  • Detach Claude, Codex, and AGY stream abort listeners on completion and failure.

  • Preserve explicitly empty Codex text in run statuses, batch results, and
    completed stream snapshots; missing text remains distinct from an empty answer.

  • Pin patched development dependencies for Dependabot alerts #40–#42:
    source-map-js 1.2.2, katex 0.18.2, and smol-toml 1.9.0.

  • Include the versioned offline documentation tree in the npm package.

  • Codex run statuses, successful batch responses, and completed stream events
    now normalize native message output_text content when the response has no
    string output_text field. Text is concatenated in wire order without added
    separators; explicit text (including an empty string), failure states, and
    non-text items retain their existing handling.

Changed

  • Qualify consumer guidance by available exports rather than assuming development
    APIs remain unreleased in future documentation assets.

  • Pin the published documentation baseline independently of the working package
    version. Release preparation retains verified historical docs; release assets
    are generated from the exact published npm artifact.

  • Add a complete React consumer request workflow with validated handler
    responses, pending and failed run IDs, local cancellation, and stale-response
    protection. Seven mounted UI tests exercise the installed package and
    documented server handler against stable and development artifacts.

  • Make the provider-file guide demonstrate reusable clients, persisted upload
    IDs, and explicit cleanup with validated deletion receipts. Add seven
    runnable file lifecycle tests against the pinned stable package and
    development pack, with typed input and protocol errors in the helpers.

  • Make the documented text-stream helper reject completed streams without
    observed text using run_output_missing, while preserving supplied empty
    snapshots. Add runnable streaming tests against the pinned stable package
    and development pack for snapshots, deltas, partial failures, and gaps.

  • Make the documented batch collector distinguish pending work from terminal
    batches without results, retain batch context, and reject ambiguous result
    IDs with a typed error. Add runnable Claude/Codex collection fixtures checked
    against the pinned stable package and development pack.

  • Add runnable consumer contract tests for the server handler, checked against
    the exact published package and the development pack. The testing guide
    covers answer/progress states, input validation, safe failures, and client
    cleanup through the public provider and facade entry points.

  • Add an executable authorized background-run workflow with separate read and
    cancellation permissions, per-poll authorization, retained wait outcomes,
    and packed-consumer checks for denied access and explicit cancellation.

  • Answer and streaming examples use typed errors with retained run identity;
    error guidance shows guards, safe caller messages, and protected diagnostics.

  • Replace CLI-style documentation demos with reusable answer services, server
    handlers, streaming callbacks, background-run retrieval, and batch collection.
    Provider setup now returns usable clients with explicit application ownership.

  • Documentation checks now validate runtime-provider HTTP verbs and full route
    shapes, including wrapped HTTP lines. Gemini route labels show collection
    segments explicitly, and Codex batch routes include the input-file upload.

  • Reorganized consumer documentation around provider setup, execution workflows,
    failure handling, and upgrades; retained exhaustive declarations behind a
    reference index.

  • Replaced stale provider links and conflicting release guidance, and added
    executable quickstart and workflow examples with documentation link checks.