@ultimat3/core 13.0.0 → 15.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ultimat3/core",
-  "version": "13.0.0",
+  "version": "15.0.0",
   "description": "Ultimate's foundation: errors, context, env, config, clock, ids, logging, telemetry, lifecycle",
   "license": "MIT",
   "type": "module",

package/src/schema-error-codes.ts

@@ -8,6 +8,7 @@
 // one place and not the other fails the build instead of quietly disagreeing at runtime.
 
 import { registerErrorCodes } from './error-codes';
+import { registerErrorRetry } from './error-retry';
 
 /** Mirrors `SCHEMA_ERROR_CODES` in `packages/schema/src/errors.ts`. Keep the titles identical. */
 export const SCHEMA_ERROR_CODE_TITLES: Readonly<Record<string, string>> = Object.freeze({
@@ -26,3 +27,23 @@ registerErrorCodes(
     Object.entries(SCHEMA_ERROR_CODE_TITLES).map(([code, title]) => [code, { title }]),
   ),
 );
+
+// And how each is RETRIED, here for the same tier reason the titles are here.
+//
+// Every one is LISTED rather than left to the default, which is the lesson `packages/jobs/src/
+// errors.ts` writes up for its own six terminal webhook codes: `classifyThrown` reads an
+// unregistered code as UNCLASSIFIED, so the attempt count governs and a schema refusal raised
+// inside a job body burns the whole retry policy re-proving an answer no attempt can change.
+//
+// Measured cost before this: `@ultimat3/scraping` spent FIVE browser launches on a page carrying
+// a `<div constructor="...">` — five navigations, five arrivals at a login — and dead-lettered
+// reporting that the browser went away, about a browser that answered perfectly.
+// `packages/scraping/src/cdp-target.ts` names the gap and says it cannot be closed from there.
+//
+// A value that does not match its schema does not match it on attempt five either.
+registerErrorRetry({
+  X_VALIDATION_FAILED: 'terminal',
+  X_SCHEMA_UNSUPPORTED: 'terminal',
+  X_SCHEMA_DISCRIMINANT_INVALID: 'terminal',
+  X_SCHEMA_DEFAULT_UNSHAREABLE: 'terminal',
+});