@oro-ai/sdk 1.0.71 → 1.0.72

package/dist/index.d.mts

@@ -3129,9 +3129,7 @@ type HealthCheckResponse = ({
     [key: string]: unknown;
 });
 type HealthCheckError = unknown;
-type DeepHealthCheckResponse = ({
-    [key: string]: unknown;
-});
+type DeepHealthCheckResponse = (unknown);
 type DeepHealthCheckError = unknown;
 type ListSuitesResponse = (Array<SuitePublic>);
 type ListSuitesError = unknown;
@@ -3948,13 +3946,21 @@ declare const healthCheck: <ThrowOnError extends boolean = false>(options?: Opti
  * Deep Health Check
  * Deep readiness check that exercises the SQLAlchemy pool (ORO-1121).
  *
- * Acquires a session and runs SELECT 1 with a hard timeout. If the
- * pool is wedged (phantom-checked-out slots) or RDS is unreachable
- * from this task, the check fails fast and the ALB pulls the task
- * out of rotation; ECS replaces it. The ALB's own per-check timeout
- * is the ultimate ceiling, so the inner timeout must be smaller.
+ * Acquires a session and runs SELECT 1 with a hard timeout, retrying
+ * once on failure to ride out transient pool stalls or one-shot
+ * network blips (ORO-1168). If the pool is wedged (phantom-checked-out
+ * slots) or RDS is unreachable across both attempts, the check fails
+ * and the ALB pulls the task out of rotation after its own
+ * unhealthy_threshold_count consecutive failures.
+ *
+ * On final failure we return 503 directly via `JSONResponse` instead
+ * of raising `HTTPException`. The status to the ALB is identical, but
+ * the Sentry FastAPI integration only captures *exceptions* — so this
+ * path no longer triggers the "new unhandled error" PD rule on a
+ * transient blip. Sustained DB-unreachable is correctly surfaced by
+ * the ALB target-health alarm, not the Sentry new-issue rule.
  */
-declare const deepHealthCheck: <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<unknown, ThrowOnError>) => _hey_api_client_fetch.RequestResult<DeepHealthCheckResponse, unknown, ThrowOnError>;
+declare const deepHealthCheck: <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<unknown, ThrowOnError>) => _hey_api_client_fetch.RequestResult<unknown, unknown, ThrowOnError>;
 /**
  * List all suites
  * Get all problem suites, ordered by version descending (newest first).

package/dist/index.d.ts

@@ -3129,9 +3129,7 @@ type HealthCheckResponse = ({
     [key: string]: unknown;
 });
 type HealthCheckError = unknown;
-type DeepHealthCheckResponse = ({
-    [key: string]: unknown;
-});
+type DeepHealthCheckResponse = (unknown);
 type DeepHealthCheckError = unknown;
 type ListSuitesResponse = (Array<SuitePublic>);
 type ListSuitesError = unknown;
@@ -3948,13 +3946,21 @@ declare const healthCheck: <ThrowOnError extends boolean = false>(options?: Opti
  * Deep Health Check
  * Deep readiness check that exercises the SQLAlchemy pool (ORO-1121).
  *
- * Acquires a session and runs SELECT 1 with a hard timeout. If the
- * pool is wedged (phantom-checked-out slots) or RDS is unreachable
- * from this task, the check fails fast and the ALB pulls the task
- * out of rotation; ECS replaces it. The ALB's own per-check timeout
- * is the ultimate ceiling, so the inner timeout must be smaller.
+ * Acquires a session and runs SELECT 1 with a hard timeout, retrying
+ * once on failure to ride out transient pool stalls or one-shot
+ * network blips (ORO-1168). If the pool is wedged (phantom-checked-out
+ * slots) or RDS is unreachable across both attempts, the check fails
+ * and the ALB pulls the task out of rotation after its own
+ * unhealthy_threshold_count consecutive failures.
+ *
+ * On final failure we return 503 directly via `JSONResponse` instead
+ * of raising `HTTPException`. The status to the ALB is identical, but
+ * the Sentry FastAPI integration only captures *exceptions* — so this
+ * path no longer triggers the "new unhandled error" PD rule on a
+ * transient blip. Sustained DB-unreachable is correctly surfaced by
+ * the ALB target-health alarm, not the Sentry new-issue rule.
  */
-declare const deepHealthCheck: <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<unknown, ThrowOnError>) => _hey_api_client_fetch.RequestResult<DeepHealthCheckResponse, unknown, ThrowOnError>;
+declare const deepHealthCheck: <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<unknown, ThrowOnError>) => _hey_api_client_fetch.RequestResult<unknown, unknown, ThrowOnError>;
 /**
  * List all suites
  * Get all problem suites, ordered by version descending (newest first).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oro-ai/sdk",
-  "version": "1.0.71",
+  "version": "1.0.72",
   "description": "Official TypeScript SDK for the ORO Bittensor Subnet API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/sdk.gen.ts

@@ -22,11 +22,19 @@ export const healthCheck = <ThrowOnError extends boolean = false>(options?: Opti
  * Deep Health Check
  * Deep readiness check that exercises the SQLAlchemy pool (ORO-1121).
  *
- * Acquires a session and runs SELECT 1 with a hard timeout. If the
- * pool is wedged (phantom-checked-out slots) or RDS is unreachable
- * from this task, the check fails fast and the ALB pulls the task
- * out of rotation; ECS replaces it. The ALB's own per-check timeout
- * is the ultimate ceiling, so the inner timeout must be smaller.
+ * Acquires a session and runs SELECT 1 with a hard timeout, retrying
+ * once on failure to ride out transient pool stalls or one-shot
+ * network blips (ORO-1168). If the pool is wedged (phantom-checked-out
+ * slots) or RDS is unreachable across both attempts, the check fails
+ * and the ALB pulls the task out of rotation after its own
+ * unhealthy_threshold_count consecutive failures.
+ *
+ * On final failure we return 503 directly via `JSONResponse` instead
+ * of raising `HTTPException`. The status to the ALB is identical, but
+ * the Sentry FastAPI integration only captures *exceptions* — so this
+ * path no longer triggers the "new unhandled error" PD rule on a
+ * transient blip. Sustained DB-unreachable is correctly surfaced by
+ * the ALB target-health alarm, not the Sentry new-issue rule.
  */
 export const deepHealthCheck = <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<unknown, ThrowOnError>) => {
     return (options?.client ?? client).get<DeepHealthCheckResponse, DeepHealthCheckError, ThrowOnError>({

package/src/generated/types.gen.ts

@@ -3291,9 +3291,7 @@ export type HealthCheckResponse = ({
 
 export type HealthCheckError = unknown;
 
-export type DeepHealthCheckResponse = ({
-    [key: string]: unknown;
-});
+export type DeepHealthCheckResponse = (unknown);
 
 export type DeepHealthCheckError = unknown;