cursedops 0.19.5 → 0.19.6

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "cursedops",
-	"version": "0.19.5",
+	"version": "0.19.6",
 	"description": "The build-and-ops answers this generation's apps wrote independently and identically: finding a generation's roots — and printing a command that runs when pasted — without knowing a path, the generation's whole-tree laws run over one repo from a checkout or a worktree, macOS launchd agent install/replace/remove and the live port a job serves, the scaffolding and verdicts of a deployed smoke (origin probe, the smoke's own environment, a network that lies about DNS, a settled version), the static-serving helpers eight apps copied — the path-traversal guard among them — the API floor that keeps an unmatched /api/... from ever being answered with the app shell, the commit and dirty flag a checkout-served process reports, the Cloudflare Worker deploy toolkit four apps copied (the deploy sequence, exact-set secrets over a pipe, origin-first rollback, the curl edge fetch, the row-for-row D1 import proof, the billed-CPU tail check around a deploy's walk and smoke, and each app's worker:secrets and worker:smoke main as one function of its data), the relay a Worker fronts a Mac-bound app with (the Durable Object, the frames, the Mac's dialer and key rotation — lifted from station for roms — and the signed-in stage walk's skeleton and the relay app's whole worker:deploy), the Worker import-graph and await-port checks every Worker app's suite runs over its own source, and the public-surface ratchet three published libraries each carried a forked copy of. Mechanism only — no app knows its name from here. Bun, zero runtime dependencies (typescript is an optional peer, for public-surface only), ships source.",
 	"type": "module",
 	"scripts": {

package/src/workerSecrets.ts

@@ -97,7 +97,7 @@ export const SECRET_PUT_ATTEMPTS = 3;
  * Reads of the account after the puts before a set that is not exact is believed. A read changes
  * nothing, so asking again can only replace a stale answer with a current one — see {@link syncSecrets}.
  */
-export const SECRET_READBACK_ATTEMPTS = 5;
+export const SECRET_READBACK_ATTEMPTS = 8;
 
 /**
  * Apply `plan`: put every value, delete every extra, then READ THE ACCOUNT BACK and fail unless it
@@ -113,6 +113,9 @@ export const SECRET_READBACK_ATTEMPTS = 5;
  * listed both secrets, both puts said ok, and the list read straight after answered NOTHING — a
  * green deploy stopped as "secrets NOT attached". The same script run again a minute later read
  * both. The LAST read is the verdict, so a set that is really wrong is still a red.
+ * Eight reads, pausing 2 s more each time, wait 56 s: on 2026-10-24 (ship run 20-24-05) photos'
+ * FIRST put of FAMILY_PEOPLE_TOKEN said ok and five reads over 20 s never listed it, so the deploy
+ * stopped as "secrets NOT attached"; `--check` a few minutes later read it held.
  */
 export async function syncSecrets(
 	plan: SecretPlan,