@monoflake/sdk 2026.1005.1 → 2026.1005.3

package/dist/cache/src/index.d.ts

@@ -50,10 +50,10 @@ export declare const NAMED = "public, max-age=3600";
 /**
  * What a key whose bytes cannot change earns.
  *
- * Content addressing is the usual reason -- a hashed name cannot denote different bytes, so a
- * cached copy is correct forever and needs no invalidation. It is not the only one: a Latin font
- * subset keeps the year on a written promise that re-subsetting renames it, which is why this is
- * named for the property rather than for the hash that normally carries it.
+ * Content addressing is the reason -- a hashed name cannot denote different bytes, so a cached
+ * copy is correct forever and needs no invalidation. Named for the property rather than the hash,
+ * since an exception with a promise of its own could earn it too; none does today -- see
+ * spec/architecture/artifacts.md.
  */
 export declare const UNCHANGING = "public, max-age=31536000, immutable";
 /**

package/dist/cache/src/index.js

@@ -40,10 +40,10 @@ const NAMED = `public, max-age=${NAMED_LIFE}`;
 /**
 * What a key whose bytes cannot change earns.
 *
-* Content addressing is the usual reason -- a hashed name cannot denote different bytes, so a
-* cached copy is correct forever and needs no invalidation. It is not the only one: a Latin font
-* subset keeps the year on a written promise that re-subsetting renames it, which is why this is
-* named for the property rather than for the hash that normally carries it.
+* Content addressing is the reason -- a hashed name cannot denote different bytes, so a cached
+* copy is correct forever and needs no invalidation. Named for the property rather than the hash,
+* since an exception with a promise of its own could earn it too; none does today -- see
+* spec/architecture/artifacts.md.
 */
 const UNCHANGING = `public, max-age=${UNCHANGING_LIFE}, immutable`;
 /**

package/dist/src/index.js

@@ -5,7 +5,7 @@ import { INFRA, PANEL_PORT } from "@monoflake/urls";
 * The platform's addresses, and the whole map as everything above infra reads it: the platform's
 * own declared here, the author's from `canmi` and infra's from `@monoflake/urls`, composed into
 * one shape so a caller asks one place and the Rust mirror has one source. See
-* web's spec/architecture/layers.md, "Addresses are split by who owns the name".
+* the workspace's spec/architecture/layers.md, "Addresses are split by who owns the name".
 */
 /**
 * The repositories whose deploy runs the hook passes to the nodes, as GitHub names them: the two

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@monoflake/sdk",
-  "version": "2026.1005.1",
+  "version": "2026.1005.3",
   "description": "Addresses and clients for the platform.",
   "keywords": [
     "cloudflare-workers",