@xemahq/biome-host-api-client 0.3.27 → 0.3.29

package/dist/custom-fetch.js

@@ -223,14 +223,66 @@ const customFetch = async (url, options) => {
     }
 };
 exports.customFetch = customFetch;
-async function parseBody(response) {
-    const contentType = response.headers.get('content-type');
-    if (contentType?.includes('application/json')) {
-        return response.json();
+/**
+ * Does this media type carry JSON?
+ *
+ * ── THE OUTAGE THIS FIXES ────────────────────────────────────────────────
+ *
+ * This used to be `contentType?.includes('application/json')`, and EVERY error
+ * this fleet returns failed that test. The platform's `GlobalExceptionFilter`
+ * emits RFC 9457 problem documents and sets the media type explicitly —
+ * `.type(PROBLEM_DETAILS_CONTENT_TYPE)` before `.json()`, so it cannot be
+ * overridden — and that constant is `application/problem+json`, which does NOT
+ * contain the substring `application/json`: after `application/` comes
+ * `problem+json`.
+ *
+ * So every non-2xx body fell through to `response.text()` and reached the
+ * caller as an UNPARSED STRING. `ClientError.body` is typed `unknown`, so
+ * nothing complained; every consumer that reads a machine-readable code off an
+ * error — `error.body.code`, `error.body.details.code` — silently read
+ * `undefined` instead, for every error, in every service.
+ *
+ * Measured in production on 2026-09-15: skill-registry-api's
+ * `resolveOrNull()` absorbs `RELEASE_CHANNEL_NOT_FOUND` into `null` by exactly
+ * that read. With the code unreadable the absorb never fired, a routine "no
+ * pointer on this channel" 404 became a 500 on `GET /skills` and
+ * `GET /describe-objects`, and agent-session-api's `apply_control_bundle` step
+ * aborted EVERY session launch in the organisation — 7,871 failed resolutions
+ * an hour. A fix written for that exact page months earlier was present in the
+ * running image and could not help, because the classifier it repaired was
+ * being handed a string.
+ *
+ * ── WHY THE STRUCTURED SUFFIX, NOT A SECOND SUBSTRING ────────────────────
+ *
+ * Adding `|| includes('application/problem+json')` would fix this one media
+ * type and leave the next one — `application/vnd.api+json`, and anything else
+ * a service legitimately emits. RFC 6839 defines `+json` as the structured
+ * syntax suffix meaning "this is JSON"; that is the actual rule, so it is the
+ * rule implemented. Parameters are stripped first, because
+ * `application/problem+json; charset=utf-8` is the same media type.
+ */
+function isJsonMediaType(contentType) {
+    if (contentType === null) {
+        return false;
     }
+    const essence = contentType.split(';')[0]?.trim().toLowerCase() ?? '';
+    return essence === 'application/json' || essence.endsWith('+json');
+}
+async function parseBody(response) {
+    // 204 FIRST, and deliberately — this ORDER is carried from `develop`, which
+    // fixed the same defect independently and got this half right where `main`
+    // did not. A 204 carries no body, so `response.json()` on one throws
+    // SyntaxError; and a 204 whose headers STILL declare a JSON content type is
+    // ordinary, because the framework sets the header before the handler returns
+    // nothing. With the JSON branch first, a documented `undefined` becomes a
+    // thrown parse error. Pinned by a case in `transport-problem-json.test.cjs`.
     if (response.status === 204) {
         return undefined;
     }
+    const contentType = response.headers.get('content-type');
+    if (isJsonMediaType(contentType)) {
+        return response.json();
+    }
     return response.text();
 }
 function parseRetryAfter(value) {

package/dist/models/contributionKind.d.ts

@@ -37,6 +37,7 @@ export declare const ContributionKind: {
     readonly 'opencode-plugin': "opencode-plugin";
     readonly capability: "capability";
     readonly 'resource-ownership': "resource-ownership";
+    readonly 'resource-kind': "resource-kind";
     readonly 'resource-definition': "resource-definition";
     readonly 'stage-machine': "stage-machine";
     readonly 'search-type': "search-type";
@@ -44,5 +45,6 @@ export declare const ContributionKind: {
     readonly 'canonical-object-type': "canonical-object-type";
     readonly 'resource-role': "resource-role";
     readonly 'ingestion-source': "ingestion-source";
+    readonly 'notification-descriptor': "notification-descriptor";
     readonly 'contribution-kind': "contribution-kind";
 };

package/dist/models/contributionKind.js

@@ -36,6 +36,7 @@ exports.ContributionKind = {
     'opencode-plugin': 'opencode-plugin',
     capability: 'capability',
     'resource-ownership': 'resource-ownership',
+    'resource-kind': 'resource-kind',
     'resource-definition': 'resource-definition',
     'stage-machine': 'stage-machine',
     'search-type': 'search-type',
@@ -43,5 +44,6 @@ exports.ContributionKind = {
     'canonical-object-type': 'canonical-object-type',
     'resource-role': 'resource-role',
     'ingestion-source': 'ingestion-source',
+    'notification-descriptor': 'notification-descriptor',
     'contribution-kind': 'contribution-kind',
 };

package/dist/models/problemDetailsDto.d.ts

@@ -4,6 +4,9 @@
  * OpenAPI spec version: 0.1.1
  */
 import type { ProblemFieldIssueDto } from './problemFieldIssueDto.js';
+/**
+ * RFC 9457 problem document. The declared members are the reserved core; extension members are TOP-LEVEL and OPEN, owned by the refusing plane.
+ */
 export interface ProblemDetailsDto {
     /** Absolute URI identifying the refusal TYPE. Derived one-to-one from `code`, so a caller may branch on either and can never be told two different things. Never `about:blank`. */
     type: string;
@@ -21,4 +24,5 @@ export interface ProblemDetailsDto {
     traceId?: string;
     /** Field-level issues, when the refusal is about the request body. */
     errors?: ProblemFieldIssueDto[];
+    [key: string]: unknown;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xemahq/biome-host-api-client",
-  "version": "0.3.27",
+  "version": "0.3.29",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "files": [
@@ -19,7 +19,7 @@
     "service": "biome-host-api",
     "biome": "biome-host",
     "target": "server",
-    "generator": "@xemahq/api-client-generator@0.19.0",
+    "generator": "@xemahq/api-client-generator@0.21.0",
     "source": "openapi.public.json"
   },
   "license": "LicenseRef-Xema-BSL-1.1",