fluncle 0.195.0 → 0.196.0

package/bin/fluncle.mjs

@@ -561,7 +561,7 @@ function parseVersion(version) {
 var currentVersion;
 var init_version = __esm(() => {
   init_output();
-  currentVersion = "0.195.0".trim() ? "0.195.0".trim() : "0.1.0";
+  currentVersion = "0.196.0".trim() ? "0.196.0".trim() : "0.1.0";
 });
 
 // src/update-notifier.ts
@@ -2443,7 +2443,7 @@ function parseVersion2(version) {
 var currentVersion2, latestReleaseUrl = "https://api.github.com/repos/mauricekleine/fluncle/releases/latest";
 var init_version2 = __esm(() => {
   init_output();
-  currentVersion2 = "0.195.0".trim() ? "0.195.0".trim() : "0.1.0";
+  currentVersion2 = "0.196.0".trim() ? "0.196.0".trim() : "0.1.0";
 });
 
 // ../../packages/registry/src/index.ts
@@ -3685,27 +3685,26 @@ var init_src = __esm(() => {
     },
     {
       exposedContent: [
-        "cut each pending operator-framed 9:16 clip out of its set video → ship to R2 (--no-agent, ffmpeg)"
+        "poll Twitch for the live set → POST the live state that lights the cross-surface callout (--no-agent)"
       ],
       kind: "cron",
-      name: "cron.studio-clip",
-      operatorNotes: "every 15m. Pure-trigger, zero LLM tokens: a deterministic ffmpeg cut driven by the fluncle CLI (`admin clips list` → `admin clips cut`), agent-scoped (list_clips + the agent-tier presign_clip_upload / finalize_clip_cut). Cuts the operator-framed 9:16 clips from the /admin/studio editor (keyed by Log ID) out of the set video → ships `<clipId>/footage.mp4` to R2 for the /admin/clips library + the clip drip-feed. The box runs the standalone bun BINARY (the npm thin client can't spawn ffmpeg). Source: docs/agents/hermes/scripts/clip-sweep.sh. Probed on /status as cron.studio-clip.",
-      probeConfig: { cadenceMs: 15 * MINUTE_MS, cronName: "fluncle-studio-clip", kind: "cron" },
-      statusDescription: "cuts set videos into 9:16 clips",
-      title: "Studio clips",
+      name: "cron.live",
+      operatorNotes: "every 1m, run by a rave-02 host systemd timer (docs/agents/hermes/live-timer/). Pure polling, zero LLM tokens. Mints/reuses a cached Twitch client-credentials app token, asks Helix whether the channel is streaming, and POSTs the raw state to the agent-tier record_live_state op — the Worker owns the transition detection and the crew callout. The poller is deliberately dumb and idempotent; auto-clear is READ-side (every surface treats a flag older than ~5m as offline), so a dead poller can never strand a permanent LIVE banner. Source: docs/agents/hermes/scripts/fluncle-live.sh. Probed on /status as cron.live.",
+      probeConfig: { cadenceMs: MINUTE_MS, cronName: "fluncle-live", kind: "cron" },
+      statusDescription: "watches for the live set",
+      title: "Live poller",
       weights: { status: "hidden" }
     },
     {
-      command: "fluncle admin clips drip-pause",
       exposedContent: [
-        "post the due, cut clips to Instagram on a jittered ~daily cadence via Postiz (--no-agent, Worker HTTP)"
+        "cut each pending operator-framed 9:16 clip out of its set video → ship to R2 (--no-agent, ffmpeg)"
       ],
       kind: "cron",
-      name: "cron.clip-drip",
-      operatorNotes: "every 20m. Pure HTTP trigger, zero LLM tokens. Admin tier (needs the Worker's Postiz key, which the box never sees — the box only triggers; the `finalize_clip_cut` / `record_health` precedent). The Worker checks the global kill switch FIRST (paused → no-op), then posts due clips bounded by a per-tick cap AND a rolling-24h IG cap. Every clip auto-enters the schedule at a jittered ~23-25h after the queue tail. The operator pauses/resumes with `fluncle admin clips drip-pause` / `drip-resume`. Source: docs/agents/hermes/scripts/clip-drip-sweep.sh. Probed on /status as cron.clip-drip.",
-      probeConfig: { cadenceMs: 20 * MINUTE_MS, cronName: "fluncle-clip-drip", kind: "cron" },
-      statusDescription: "drip-feeds set clips to Instagram",
-      title: "Clip drip-feed",
+      name: "cron.studio-clip",
+      operatorNotes: "every 15m. Pure-trigger, zero LLM tokens: a deterministic ffmpeg cut driven by the fluncle CLI (`admin clips list` → `admin clips cut`), agent-scoped (list_clips + the agent-tier presign_clip_upload / finalize_clip_cut). Cuts the operator-framed 9:16 clips from the /admin/studio editor (keyed by Log ID) out of the set video → ships `<clipId>/footage.mp4` to R2 for the /admin/clips library + the clip drip-feed. The box runs the standalone bun BINARY (the npm thin client can't spawn ffmpeg). Source: docs/agents/hermes/scripts/clip-sweep.sh. Probed on /status as cron.studio-clip.",
+      probeConfig: { cadenceMs: 15 * MINUTE_MS, cronName: "fluncle-studio-clip", kind: "cron" },
+      statusDescription: "cuts set videos into 9:16 clips",
+      title: "Studio clips",
       weights: { status: "hidden" }
     },
     {
@@ -3781,6 +3780,23 @@ var init_src = __esm(() => {
       title: "Database backup",
       weights: { status: "secondary" }
     },
+    {
+      exposedContent: [
+        "nightly hub-counts reconciliation — re-derives renderable_track_count / certified_finding_count for every label/album/artist and corrects only the rows that drifted (--no-agent)"
+      ],
+      kind: "cron",
+      name: "cron.reconcile-hub-counts",
+      operatorNotes: "04:10 Amsterdam (after the 04:00 reach snapshot, before the 04:40 demand tick), a rave-02 host systemd timer (docs/agents/hermes/reconcile-hub-counts-timer/). The SELF-HEALING BACKSTOP under keystone 2's maintained hub counts: they are moved as DELTAS by every edge-writing path (recompute-from-truth measured 27,400 ms at 150k hosted vs ~200 ms for the delta form), and a maintained counter drifts silently — a missed write path, a non-atomic bulk op, or an out-of-band write (the catalogue-prune skill deletes tracks straight out of the database). Keystone 2's own rollout proved it on day one: the deploy-window skew left 44 artists / 3 albums / 1 label wrong until a manual reconcile. A bare trigger (the funnel-snapshot shape): fires the AGENT-tier reconcile_hub_counts op once and the Worker runs two statements per table — a grouped `UPDATE … FROM (… GROUP BY fk)` guarded by a counts-DIFFER predicate (so rowsAffected IS the corrected-row count) plus a zero-truth pass for an entity whose last track vanished. The artists source is PINNED to `track_artists JOIN tracks` so orphaned edges never count. Idempotent; zero LLM tokens; no new secret. The corrected-row numbers are the operator's DRIFT AUDIT — journalctl -u fluncle-reconcile-hub-counts.service | grep AUDIT. Source: docs/agents/hermes/scripts/reconcile-hub-counts.*.",
+      probeConfig: {
+        cadenceMs: 24 * 60 * MINUTE_MS,
+        cronName: "fluncle-reconcile-hub-counts",
+        kind: "cron",
+        schedule: { time: "04:10", tz: "Europe/Amsterdam" }
+      },
+      statusDescription: "keeps the archive's counts adding up",
+      title: "Count check",
+      weights: { status: "hidden" }
+    },
     {
       command: "fluncle admin reach collect",
       exposedContent: [
@@ -6445,7 +6461,7 @@ ${response2.sessionKey}
 
   bun run --cwd apps/web wrangler secret put LASTFM_SESSION_KEY
 
-Also store it in 1Password (Fluncle vault) alongside the API key + shared secret.`);
+Also store it in your password manager alongside the API key + shared secret.`);
     return;
   }
   const response = await adminApiGet("/api/v1/admin/lastfm/auth/start");

package/package.json

@@ -31,5 +31,5 @@
     "url": "git+https://github.com/mauricekleine/fluncle.git"
   },
   "type": "module",
-  "version": "0.195.0"
+  "version": "0.196.0"
 }