cursedops 0.19.3 → 0.19.6

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "cursedops",
-	"version": "0.19.3",
+	"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/launchd.ts

@@ -171,6 +171,16 @@ export interface PlistSpec {
 	throttleInterval?: number;
 	processType?: string;
 	startCalendarInterval?: CalendarInterval;
+	/**
+	 * Run every this many seconds — "every five minutes", which a calendar key cannot say.
+	 *
+	 * 🔴 Exclusive with {@link startCalendarInterval}: launchd accepts a plist carrying
+	 * both without complaint and honors ONE, which is how a "daily" backup in this fleet
+	 * became a job that never fired. {@link renderPlist} throws rather than render that.
+	 */
+	startInterval?: number;
+	/** Run when any of these paths changes (a drop folder, a file another job writes). */
+	watchPaths?: readonly string[];
 	/**
 	 * The provenance comment written at the top of the file.
 	 *
@@ -206,6 +216,12 @@ function integers(record: Record<string, number>, indent: string): string {
  * those two being wrong is an app that either never starts or never stops.
  */
 export function renderPlist(spec: PlistSpec): string {
+	if (spec.startInterval !== undefined && spec.startCalendarInterval) {
+		throw new Error(`${spec.label}: startInterval and startCalendarInterval are exclusive — launchd silently honors one of the two; pick one`);
+	}
+	if (spec.startInterval !== undefined && !(Number.isInteger(spec.startInterval) && spec.startInterval > 0)) {
+		throw new Error(`${spec.label}: startInterval must be a positive whole number of seconds (got ${spec.startInterval})`);
+	}
 	const lines: string[] = [];
 	lines.push(`\t<key>Label</key>`, `\t<string>${escapeXml(spec.label)}</string>`);
 	lines.push(`\t<key>ProgramArguments</key>`, `\t<array>`);
@@ -219,6 +235,12 @@ export function renderPlist(spec: PlistSpec): string {
 		const defined = Object.fromEntries(Object.entries(spec.startCalendarInterval).filter(([, value]) => typeof value === "number")) as Record<string, number>;
 		lines.push(`\t<key>StartCalendarInterval</key>`, `\t<dict>`, integers(defined, "\t\t"), `\t</dict>`);
 	}
+	if (spec.startInterval !== undefined) lines.push(`\t<key>StartInterval</key>`, `\t<integer>${spec.startInterval}</integer>`);
+	if (spec.watchPaths && spec.watchPaths.length > 0) {
+		lines.push(`\t<key>WatchPaths</key>`, `\t<array>`);
+		for (const path of spec.watchPaths) lines.push(`\t\t<string>${escapeXml(path)}</string>`);
+		lines.push(`\t</array>`);
+	}
 	if (spec.runAtLoad !== undefined) lines.push(`\t<key>RunAtLoad</key>`, `\t<${spec.runAtLoad}/>`);
 	if (spec.keepAlive !== undefined) lines.push(`\t<key>KeepAlive</key>`, `\t<${spec.keepAlive}/>`);
 	if (spec.throttleInterval !== undefined) lines.push(`\t<key>ThrottleInterval</key>`, `\t<integer>${spec.throttleInterval}</integer>`);
@@ -404,6 +426,17 @@ export async function answering(
 	}
 }
 
+/**
+ * Does the app on this Mac's `port` answer its health route? {@link answering}, tightened.
+ *
+ * `/healthz` and `response.ok` rather than `/` and `< 500`: an app that serves its SPA shell
+ * to anyone answers `/` with only something static mounted, and a health route is the one that
+ * needs the server. Six apps' `service.ts` wrote this same probe by hand (forge task 3683).
+ */
+export async function healthzAnswering(port: number, { timeoutMs = 45_000, stepMs = 500, path = "/healthz" } = {}): Promise<boolean> {
+	return await answering(`http://127.0.0.1:${port}${path}`, { timeoutMs, stepMs, accept: (response) => response.ok });
+}
+
 /**
  * The `PORT` a `launchctl print` dump says the job is handed, or `null`.
  *

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,