yt-briefing 0.9.0 → 0.9.1

package/README.md

@@ -1,11 +1,11 @@
 # yt-briefing
 
 Save hours on YouTube. yt-briefing watches the channels you follow so you don't have to. For
-each new video it distills the essence in your own language — every point that matters, with
+each new video it gives you a short briefing in your own language — every point that matters, with
 only the filler cut, so nothing important is lost. Reading it takes a fraction of the time the
 video would, so you stay on top of everything and only watch what's actually worth it.
 
-It also gets better the more you use it. You give each briefing a quick rating, worth my time
+It also gets better the more you use it. You give each summary a quick rating, worth my time
 or not, and from that it learns what to keep showing you and what to drop. Over time the queue
 becomes yours: less noise, more of what you care about.
 
@@ -77,12 +77,12 @@ npx yt-briefing list                                        # show the current l
 
 ## One-off: transcribe a single video
 
-Just want one video distilled — no channels, no queue, no rating? Run `/yt-transcribe` and
+Just want one video summarized — no channels, no queue, no rating? Run `/yt-transcribe` and
 paste a URL or video ID. It pulls that video's transcript and writes a journalist-grade
-briefing in the language you chose at setup (the same `output_lang` as `/yt`). Want a one-off in
+summary in the language you chose at setup (the same `output_lang` as `/yt`). Want a one-off in
 another language? Just say so when you run it (e.g. `/yt-transcribe <url> in German`) — it
 won't change your setup. `--lang pl|en` is separate — it picks which caption track to fetch,
-not the language it's written in.
+not the summary language.
 
 The skill is installed alongside `/yt` by `init` / `install-skill`. From the plain CLI:
 
@@ -128,11 +128,11 @@ OpenAI (`https://api.openai.com/v1`), or a local Ollama (`http://localhost:11434
 
 ## Why an API, not the agent's native model
 
-The filtering and the briefings go through a plain OpenAI-compatible API call from the engine,
+The filtering and the summaries go through a plain OpenAI-compatible API call from the engine,
 not through the coding agent's own model. Two reasons.
 
 Speed. The engine works ahead in the background. It expands channels in parallel and starts
-on the next video's briefing while you rate the current one, so the following step is usually
+summarizing the next video while you rate the current one, so the following step is usually
 ready with no wait. An agent's turn-by-turn loop cannot prefetch like that, and every step pays
 its own cold start, which adds up across a whole queue.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yt-briefing",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "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": {