yt-briefing 0.3.0 → 0.3.2

package/.claude/skills/yt/SKILL.md

@@ -24,6 +24,7 @@ out = JSON.parse(`bun run src/yt-sweep.ts --reset`)   // Bash — first call: --
 while true:
   out.status:
     "done"          → sweep finished — tell the user, stop
+    "error"         → setup/config problem (e.g. missing API key) — show `out.error` to the user verbatim, stop
     "rate_limited"  → transcript fetch blocked (usually a blocked egress IP) — tell the user, stop; recovery in README.md → Proxy
     "rating_needed" → steps A–E
 ```

package/dist/lib/skill-install.js

@@ -17,7 +17,7 @@
  */
 import { readFileSync, writeFileSync, mkdirSync } from 'node:fs';
 import { join, resolve } from 'node:path';
-import { PKG_ROOT } from "./paths.js";
+import { PKG_ROOT, DATA_DIR } from "./paths.js";
 /** Compiled output dir — what a baked (dist) skill command points the runtime at. */
 const DIST_DIR = join(PKG_ROOT, 'dist');
 /** True when the installer itself is running under Bun (vs plain Node). */
@@ -39,8 +39,11 @@ export const AGENTS = {
 /**
  * The shipped SKILL.md. `dist=false` (default) returns it verbatim — the `bun run src/X.ts`
  * dev form, correct only when cwd is the package AND the runtime is Bun. `dist=true` rewrites
- * the engine commands to `"<process.execPath>" "<abs>/dist/X.js"` — this machine's runtime
- * (Node or Bun) against the compiled build, so it runs from any cwd.
+ * for the consumed case: engine commands become `"<process.execPath>" "<abs>/dist/X.js"` (this
+ * machine's runtime, Node or Bun, against the compiled build, so they run from any cwd), and the
+ * bare `data/…` paths the agent reads (e.g. `data/config.json`) become the absolute `DATA_DIR`.
+ * In dev the agent's cwd IS the package so `data/` resolves; when consumed, DATA_DIR moves to
+ * `<project>/.yt-briefing/data`, so the dev-relative paths would miss — hence the rewrite.
  */
 export function skillBody(dist = false) {
     const raw = readFileSync(SOURCE, 'utf8');
@@ -50,7 +53,8 @@ export function skillBody(dist = false) {
     const cmd = (base) => `"${exe}" "${join(DIST_DIR, base + '.js')}"`;
     return raw
         .replace(/bun run src\/yt-sweep\.ts/g, cmd('yt-sweep'))
-        .replace(/bun run src\/yt-rating\.ts/g, cmd('yt-rating'));
+        .replace(/bun run src\/yt-rating\.ts/g, cmd('yt-rating'))
+        .replace(/data\//g, DATA_DIR + '/');
 }
 /** Write the skill into `dir` (created if needed). Returns the SKILL.md path written. */
 export function installSkill(dir, dist = false) {

package/dist/yt-sweep.js

@@ -542,5 +542,12 @@ if (reset) {
     clearRest();
     clearPrefetch();
 }
+// Fatal config check, foreground only (the detached --fill / --prefetch children already
+// exited above). A missing YouTube Data API key makes EVERY channel expansion throw the same
+// error, which the per-channel `catch` collapses to 0 items — surfacing as a misleading
+// `status:"done"` ("no new videos"). Fail fast with a clear, actionable error instead.
+if (!process.env.YT_BRIEFING_YOUTUBE_API_KEY) {
+    emit({ status: 'error', error: 'YT_BRIEFING_YOUTUBE_API_KEY is not set — add a YouTube Data API v3 key to .yt-briefing/.env (see README → first run / .env.example).' });
+}
 const queue = loadQueue() ?? buildQueue();
 await advance(queue);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yt-briefing",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "A self-learning YouTube briefing engine: it sweeps the channels you follow, filters noise in two stages (title, then transcript), summarizes the rest in your language, and adapts to your ratings — one video at a time.",
   "type": "module",
   "bin": {