@ultimat3/cache 19.2.0 → 19.3.2

package/CLAUDE.md

@@ -306,6 +306,12 @@ Tier 1. Tagged caching + THE invalidation graph.
   cause name the keys that are actually set. Names only — all four keys can hold a credential.
 - A remote driver takes an injected `fetch` so a test never unseals the network; the loopback
   proof in `purge-fastly.test.ts` is the only place the default one runs.
+- **The purge URL in a `fix:` goes through `renderFixShellArg`** (`As of 2026-09-06`).
+  `purgePost`'s transport failure names `curl -sS -m 5 -o /dev/null <url>`, a command a reader
+  pastes, and the URL is operator data from `.env.production` (`purge-env.ts`) — so `$(…)` and a
+  backtick in it substitute before `curl` is reached. An ordinary endpoint travels verbatim; the
+  URL is in the `detail` either way, which is read rather than run. `renderFixLiteral` cannot
+  stand in: its double quotes leave `$(…)` live.
 
 ## Files
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ultimat3/cache",
-  "version": "19.2.0",
+  "version": "19.3.2",
   "description": "Tagged caching: request memo, LRU, Redis, CDN — one invalidation graph",
   "license": "MIT",
   "type": "module",
@@ -31,6 +31,6 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@ultimat3/core": "19.2.0"
+    "@ultimat3/core": "19.3.2"
   }
 }

package/src/purge-http.ts

@@ -3,7 +3,7 @@
 // forces. Kept apart from the drivers because "which failure can succeed unchanged" is one
 // judgement, and two copies of it would drift into two answers for the same 429.
 
-import { renderThrowable } from '@ultimat3/core';
+import { renderFixShellArg, renderThrowable } from '@ultimat3/core';
 import { CacheDriverUnavailableError, CachePurgeFailedError } from './errors';
 
 /** Just the call. `typeof fetch` also carries `preconnect`, which no test double should have to. */
@@ -192,7 +192,10 @@ export async function purgePost(input: PurgePostInput): Promise<Response> {
       driver: input.driver,
       detail: `${reason} — nothing left this host for ${input.url} (egress, DNS or TLS)`,
       retryable: true,
-      fix: `curl -sS -m 5 -o /dev/null ${input.url}`,
+      // The endpoint comes from `.env.production` (`purge-env.ts`), so it is operator data in a
+      // COMMAND position: `$(…)` and a backtick substitute before `curl` is reached. The URL is
+      // already in the `detail` above, which is read rather than pasted.
+      fix: `curl -sS -m 5 -o /dev/null ${renderFixShellArg(input.url, '<the purge endpoint the cause names>')}`,
     });
   }
 }