@gentbajko/slopify 2.5.0 → 3.0.1

package/dist/tutorials/Backups.md

@@ -0,0 +1,121 @@
+# Backups
+
+A backup is one `.tar` file with everything you made in Slopify: every project with its files and history, your library, templates, schedules, channels and settings. Make one by hand at any time with **Export everything**, or let Slopify write one every day. Bring one back with **Import a backup**. Provider keys are never included.
+
+**Where to find it:** **Settings → Backup & storage** (Export everything, Import a backup) and **Settings → Backups** (daily backups, Back up now).
+
+## What a backup holds
+
+| Included | Left out on purpose |
+|---|---|
+| Every project with its files and history, and its channel | Provider keys |
+| Automatic review verdicts and run cost of each project | The Notification URL |
+| Prompts, intros and outros, with their history | The Studio extension's pairing |
+| Document themes and uploaded fonts | The tutorial's progress |
+| Templates, schedules and Play drafts | The daily backups' folder and status |
+| Channels: brand kit, series brief, episode memory and AI disclosure settings, cast with pictures, end screen images, episode summaries, existing videos, and the last **Keep only titles containing** filter | The telemetry machine id |
+| Channel links and the provider defaults a new Play form starts with | State that only matters while this install runs: the queue, plan-limit waits |
+| AI use marks: voices marked as a real person, image prompts marked photorealistic, projects with real footage | |
+| Settings and usage history | |
+| The trash: trashed items come back still in the trash, with their original date | |
+
+After an import you add your provider keys again in [Providers and keys](Providers-and-Keys).
+
+## Export everything (a backup right now, downloaded)
+
+1. Finish or pause any running project. Nothing is copied while a project is being made, because its files are still being written.
+2. Open **Settings → Backup & storage**.
+3. Press **Export everything**.
+4. Your browser downloads `slopify-backup-YYYY-MM-DD.tar`. Progress shows in the browser's downloads. A backup can be many gigabytes.
+
+You can also run **Export everything** from the `Ctrl+K` palette while on Settings.
+
+## Import a backup
+
+Importing adds to this install and replaces nothing.
+
+1. Finish or pause any running project.
+2. Open **Settings → Backup & storage**.
+3. Press **Import a backup** and choose the `.tar` file made with Export everything or a daily backup. (A `.zip` made with **Export backup** in older versions also works, up to 100 MB.)
+4. Wait while it uploads and imports. Slopify says "Backup imported." with what it added.
+
+How an import merges:
+
+- Projects already here are skipped.
+- A name that is already taken arrives with "(imported)" after it.
+- Schedules arrive paused, so nothing starts by surprise. Resume them on **Calendar → Schedules**.
+- Channels merge by id. The default channel "My channel" takes the backup's settings only while this install's default is untouched; otherwise yours is kept. Cast members, pictures, episode memories and existing videos come into the channel that is here. A video title the channel already has is skipped.
+- A prompt's history comes with the prompt when the prompt itself came in.
+- Pictures stored in the database are checked against their SHA-256 hash on import.
+
+If the import fails, Slopify says: "The backup wasn't imported. Check it is a file made with Export everything (.tar) or Export backup (.zip), then try again."
+
+## Turn on daily backups
+
+Daily backups are off by default, because each backup holds every project's video and can fill a disk.
+
+1. Open **Settings → Backups**.
+2. Turn **Back up automatically** on.
+3. Set **Time of day**, **Keep last** and optionally **Folder** (see below).
+4. Press **Save**.
+
+| Setting | What it does | Default |
+|---|---|---|
+| **Back up automatically** | Turns the daily backup on or off. **Back up now** works either way. | Off |
+| **Time of day** | When the daily backup runs, in this browser's time zone. Pick a time the computer is usually on and idle. | 03:00 |
+| **Keep last** | How many of Slopify's own backups stay in the folder. After each new backup, the oldest beyond this number are deleted. | 5 (from 1 to 30) |
+| **Folder** | Where backups are written. Empty uses the **Backups** folder beside your projects: `Documents/Slopify/Backups` on a new install. Point it at another disk or a synced folder to keep copies away from this disk. | Empty |
+
+The screen shows the last backup's time and size, the result of the last attempt (with **Why the last backup stopped** when it failed), and when the next one runs.
+
+### When the daily backup runs
+
+- A timer checks once a minute. At most one automatic backup runs per day, once the day's time has passed.
+- Turning backups on, or changing the time, waits for the next time of day. Use **Back up now** for one at once.
+- If Slopify was off at the time, it backs up about two minutes after it starts, unless a backup already succeeded in the last 20 hours.
+- A failed backup is tried again an hour later, until the next day's time.
+- A backup waits while projects are being made. It shows "Waiting for … to finish", looks again every ten minutes, and starts by itself once those projects finish or pause.
+
+## Back up now
+
+1. Open **Settings → Backups**.
+2. Press **Back up now**. Slopify says "Backup started. Its result shows here when it finishes."
+
+It writes the same file into the backup folder. It says which projects it is waiting for, if any, and is refused while another backup is being written.
+
+## Where the files go and what they are called
+
+- Daily backups are named `slopify-backup-YYYY-MM-DDTHHMMSSZ.tar` (the time is UTC). Export everything downloads are named `slopify-backup-YYYY-MM-DD.tar`.
+- Slopify only ever deletes its own daily backup files. An Export everything download, a renamed copy, or anything else in the folder is never touched.
+- Installs from before 3.0 keep backups inside the projects folder (`~/Slopify/Projects/Backups` for Docker, `<data dir>/projects/Backups` natively). **Settings → Backup & storage → Your files → Move to Documents/Slopify** takes the backups along. See [Where your files live](Where-Your-Files-Live).
+- A folder you choose must be a full path, and may not be inside the projects folder (other than its `Backups` folder) or Slopify's own staging, logs or model folders.
+- In [Docker](Docker), a folder outside the projects folder exists only inside the container's private volume; the screen says so. Keep the default to see backups on your computer.
+
+## Safety
+
+- A backup is written under a hidden `.partial` name and renamed only when it is complete, so a crash, a full disk or a stop never leaves a file that looks finished.
+- Free space is checked first. A backup that would not fit fails with the sizes.
+- Backup files are readable by your user only.
+- An update waits for a backup that is being written.
+- Every failure is explained on **Settings → Backups** with what to change, for example free space, lower **Keep last**, or pick another **Folder**.
+
+## Other storage tools on Backup & storage
+
+- **Clean orphan files** deletes files that no project, draft or template uses any more. Slopify also does this each time it starts.
+- **Keep outputs only** on a finished project deletes its working files and keeps the finished outputs.
+
+Both are explained in [Where your files live](Where-Your-Files-Live).
+
+## Tips
+
+- Before moving to a new computer or between Docker and a native install, press **Export everything** and import the file on the other side. See [Uninstalling and moving](Uninstalling-and-Moving).
+- Point **Folder** at a synced or external disk so a disk failure doesn't take your backups with it.
+- Keep **Keep last** low if your projects are large.
+
+## Related pages
+
+- [Where your files live](Where-Your-Files-Live)
+- [Uninstalling and moving](Uninstalling-and-Moving)
+- [Settings reference](Settings-Reference)
+- [Trash](Trash)
+- [Docker](Docker)

package/dist/tutorials/Calendar.md

@@ -0,0 +1,103 @@
+# Calendar
+
+The calendar shows the coming four weeks on one screen: what needs you, every scheduled run with the topic and title it will use, the projects running or finished on their day, and the batch queue. You can drag a topic to another day, move it to another schedule, add topics, and accept or reject topics Slopify suggested.
+
+**Where to find it:** **Calendar** in the sidebar. It has two tabs: **Coming weeks**, described here, and **Schedules**, where you create, edit, pause and resume the schedules themselves (see [Schedules](Schedules)).
+
+## What the calendar shows
+
+The calendar starts on this week's Monday and shows four weeks, Monday to Sunday.
+
+- **Scheduled runs**, each with the project title it will make. A run shows **Queued** when a topic is lined up, **Needs a topic** when its topic is still waiting for your approval or for generation, and **Paused** when its schedule is paused.
+- **Needs you**, above the weeks: every project that is waiting on you or ready to upload (see below).
+- **Projects** running or finished on their day, with their state: **Running**, **Paused**, **Waiting**, **Failed**, **Done with problems**, **Done** or **Canceled**. A project waiting for a CLI plan says so, for example **Waiting for Codex limits (resets at 14:00)**.
+- **Batch queue**: projects waiting to start (see below).
+- **Suggested topics**, beside the weeks, for schedules that hold generated topics for approval.
+
+The calendar follows the channel picked in the sidebar, or shows every channel. See [Channels](Channels).
+
+## Needs you
+
+Above the weeks, **Needs you** lists what cannot move on without you, then what is ready to upload. Its heading counts them, for example "2 waiting for you · 1 ready to upload". It is hidden when there is nothing.
+
+| Item | Status | Button |
+| --- | --- | --- |
+| A failed project | **Failed** | **Open to fix** |
+| A project you paused | **Paused** | **Open to continue** |
+| A project held at a review checkpoint, or with an automatic review that flagged an item and waits for **Overrule** or **Redo** | **Waiting for your review** | **Open to review** |
+| A finished video not marked uploaded | **Ready to upload** | **Prepare upload** |
+
+The bundled samples never show here. A press anywhere on an entry opens its project. See [Reviews and Checkpoints](Reviews-and-Checkpoints) and [Publishing to YouTube](Publishing-to-YouTube).
+
+## The batch queue
+
+Videos started together, such as extra videos queued from Play, run one at a time. **Batch queue** lists them in the order they run, numbered (**1 in line**, **2 in line**, …), each marked **Running now**, **Waiting its turn** or **Paused**. Its heading says how many are waiting to start. Pausing a queued project holds the whole queue; when one fails or is cancelled, the next one starts. The batch queue is only shown on the calendar; Projects links here and has a **Queued** filter. It is hidden when nothing is queued.
+
+## Switch between weeks and a list
+
+Use **Calendar view** at the top:
+
+- **Weeks** (the default) shows the four weeks as a grid.
+- **List** shows the same runs day by day, with buttons to move each topic.
+
+This browser remembers your choice.
+
+## Move a topic to another day
+
+**With a mouse:** drag the topic onto another day of the same schedule's runs. The topic takes that run.
+
+**With the keyboard:** focus the topic and press `Alt+Left` or `Alt+Up` to move it earlier, `Alt+Right` or `Alt+Down` to move it later.
+
+**In the list view:** press the move-earlier or move-later arrow button on the topic's row.
+
+Earlier and later swap the topic with its neighbour in the same schedule's queue, so it takes the other's run. No schedule runs outside its own times, so a topic can only land on a day where its schedule has a run. A drop the calendar can't carry out (a day with no run, or a run with no queued topic) says why.
+
+## Move a topic to another schedule
+
+- **With a mouse:** drop the topic onto another schedule's run. It joins that schedule's queue at that place.
+- **In the list view:** open the **Move to…** menu on the topic's row and pick the schedule. The topic goes to the end of that schedule's queue and takes its next free run.
+
+The topic now runs with the other schedule's template.
+
+## Add topics
+
+1. Press **Add to calendar**.
+2. Pick the **Schedule** the topics join. Only active and paused schedules are listed, each with the number of topics already queued.
+3. Type or paste **Topics, one per line**. Blank lines are skipped.
+4. Press **Add N topics** (the button counts them). **Keep the calendar as it is** closes the form without adding anything.
+
+The topics go to the end of the schedule's queue, in order, and take its next free runs. Each topic fills the schedule's topic keyword; every other keyword keeps its every-run value. To give topics their own values, edit the schedule's topics as a table on the **Schedules** tab (see [Schedules](Schedules)).
+
+If you have no schedule yet, the calendar offers **Create a schedule**.
+
+## Accept or reject suggested topics
+
+Schedules set to **Generate and hold for approval** list their suggestions under **Suggested topics**, one block per schedule.
+
+- **Queue** adds a topic to the end of that schedule's queue.
+- **Reject** drops it for good; it is never suggested again.
+- **Queue all** adds every suggestion of that schedule, in order.
+- **Suggest topics now** asks the schedule's LLM for more at once (one LLM call).
+
+While Slopify is asking, the panel says so and the topics appear when it finishes. If the last try failed, the panel says so with the reason. When nothing is waiting it says **No suggestions are waiting.**
+
+Editing a suggestion's words before approving it is done under **Topics waiting** on the schedule itself.
+
+## The Schedules tab
+
+**Schedules**, the calendar's second tab, is where the schedules themselves live: the list with **Edit**, **Pause** or **Resume** and **Delete** on each row, **New schedule**, and the picked schedule's detail with its queued topics, topics waiting for approval and run history. The number beside the tab counts the schedules that aren't deleted. Links to the old schedules page open this tab. See [Schedules](Schedules).
+
+## Tips
+
+- Use the list view if dragging is fiddly, for example on a touch screen or a narrow window.
+- A browser notification for new suggestions opens the calendar's **Suggested topics** when you click it. See [Notifications](Notifications).
+- `Ctrl+K` → **Add to calendar** works from any screen: it opens the calendar with the form. `G` then `C` goes to the calendar.
+- To change a schedule's queued topics one by one (rename, reorder, remove), use the **Schedules** tab. See [Schedules](Schedules#edit-the-queued-topics-in-place).
+- To start one video right now instead of waiting for a run, use [Play](Play-Overview).
+
+## Related pages
+
+- [Schedules](Schedules)
+- [Templates](Templates)
+- [Channels](Channels)
+- [Home and Projects](Home-and-Projects)

package/dist/tutorials/Cast-Library.md

@@ -0,0 +1,112 @@
+# Cast Library
+
+A channel's cast is its recurring characters, creatures, places and objects. Each member has a name, a description and up to four reference pictures. Whenever a video's title or an image's brief names a member, its pictures go with that image request, so the member looks the same in every image and every episode. A cast member can also have a voice for multi-voice videos.
+
+**Where to find it:** **Channels** → a channel → **Cast** tab. **Add to cast** opens the editor beside the list.
+
+## Add a cast member
+
+1. Open **Channels**, pick the channel, and open the **Cast** tab.
+2. Press **Add to cast**.
+3. Fill in the fields (see the table below). At least give it a **Name**: "Name it first, then give it reference pictures."
+4. Press **Add to cast**. The member is saved and the picture section opens.
+5. Add one to four reference pictures: upload them or generate them (below).
+
+To change a member later, press **Edit** on it, change what you need and press **Save**. To remove one, press its delete button and confirm with **Delete from cast**.
+
+## Fields
+
+| Field | What it does | Limit |
+|---|---|---|
+| **Kind** | Character, creature, place or object. A generated reference picture of a character or creature is portrait (9:16), of a place or object landscape (16:9), and its starting prompt asks for the whole figure, place or object in view. It doesn't change how the member is matched. | |
+| **Name** | The name matched against video titles and image briefs, as whole words, ignoring case. | Up to 200 characters |
+| **Aliases** | Other names that count as this member, such as plurals and titles ("the Queen of the Nile"). Type one and press `Enter` to add it. | Up to 20 |
+| **Description for the image model** | What the member looks like, in a sentence. It goes to the image model with the member's pictures for every image that names it, and starts the prompt of a generated picture. | Up to 2,000 characters |
+| **Reference pictures** | Pictures sent with every image whose brief, or the video's title, names this member. | Up to 4, PNG or JPEG up to 10 MB each |
+| **Cast voice** | How this member speaks in multi-voice runs (see below). | |
+
+## How names are matched
+
+A name or alias matches as a **whole word, ignoring case**:
+
+- "Hypatia" is found in "Hypatia's school" and "(Hypatia)".
+- "Hypatia" is **not** found in "Hypatian" or "Hypatias".
+
+So add plurals and other spellings as aliases.
+
+Which images get which members:
+
+- Each image's own brief picks its members.
+- The establishing image and the thumbnail also take the members the video's title mentions.
+- At most four members go with one image.
+- When the establishing image is on, the member pictures go after it.
+
+## Add reference pictures
+
+### Upload a picture
+
+1. Open the member in the editor.
+2. Under **Reference pictures**, press **Upload a picture** and choose a PNG or JPEG up to 10 MB.
+
+### Generate a picture
+
+1. Under **Make a picture**, pick an **Image provider** and **Image model**.
+2. Check **Picture to make**. It starts from the name, the description and a request for a plain background. Edit it as you like (up to 4,000 characters).
+3. Press **Generate a picture**. Wait until "Making the picture…" finishes.
+
+Each press is one image call on that provider, billed at its price for one image. A plain background with the whole figure in view makes the best reference.
+
+To remove a picture, press its delete button. A member with no picture is not sent with any image.
+
+## Which image providers use the pictures
+
+| Provider | What happens |
+|---|---|
+| Codex, OpenAI, Google, and fal.ai edit models (FLUX.2 and Nano Banana 2 edit) | The member's pictures are sent as input pictures. |
+| Models that take no input pictures (Replicate, other fal.ai models) | The member is described in words instead, from its description. |
+
+See [Images](Play-Images) and [Providers and keys](Providers-and-Keys).
+
+## Give a cast member a voice
+
+In multi-voice formats (audiobook, podcast, radio drama, interview) a cast member can speak with the same voice in every episode.
+
+1. In the member's editor, under **Cast voice**, pick a **Voice provider**, **Voice model** and **Voice**. The list shows voices that speak the channel's language. If it says "No voices. Add one in Settings.", add a voice in **Settings → Voices** first.
+2. Pick a **Pace**: 0.8, 0.9, 1 (normal), 1.1 or 1.2.
+3. Press **Save**.
+4. On Play, pick the member under **Speakers**. They read with this voice, model and pace.
+
+Leave the provider empty for no voice. A run keeps the voice it started with. See [Multiple voices](Multiple-Voices).
+
+### Make a member one of the channel's hosts
+
+A channel's regular presenters can join every new podcast or interview on their own.
+
+1. In the member's editor, give it a voice (above).
+2. Turn on **One of the channel's hosts**. Without a voice it warns: "A host joins new podcasts and interviews only with a voice. Pick one under Voice above."
+3. Press **Save**. The cast list shows **Host** beside the member.
+
+When you pick **Podcast** or **Interview** on Play for a draft of this channel with no speakers yet, the speakers start with the channel's hosts that have a voice. You can still add or remove speakers on the draft. Projects already made are not changed.
+
+A picture that fails to generate because a CLI is signed out shows the same **Copy sign-in command** and **Check again** buttons as a project. See [Recovery and Retries](Recovery-and-Retries#sign-a-cli-in-again).
+
+## What happens to finished videos
+
+A run keeps the cast as it was when it started. Editing the cast later never makes a finished video outdated. Only images that actually mention a member change their fingerprint, so only they would be remade if you remake the project's images.
+
+## Backups
+
+Cast members and their pictures travel in a backup made with **Export everything**. When you import one, members come into the channel that is here. If a restored project's cast picture is missing, Slopify says so when that image is made again. See [Backups](Backups).
+
+## Tips
+
+- Upload or generate a picture with the whole figure on a plain background. Busy backgrounds leak into every image.
+- Keep the description short and visual: colours, shape, clothing, one distinctive feature.
+- Add the plural and possessive-free forms as aliases ("pharaohs", "the Queen"). Matching is whole-word only.
+
+## Related pages
+
+- [Channels](Channels)
+- [Images](Play-Images)
+- [Multiple voices](Multiple-Voices)
+- [Providers and keys](Providers-and-Keys)

package/dist/tutorials/Channels.md

@@ -0,0 +1,148 @@
+# Channels
+
+A channel is one series: its brand kit, series brief, cast, templates and schedules. Every template belongs to one channel, and every run from it uses that channel's look, cast and language. Use channels when you make more than one kind of video, so each series keeps its own look and its own topic ideas.
+
+**Where to find it:** **Channels** in the sidebar. On Play, the **Channel** picker sits under the title. The channel picker in the sidebar filters what Home, Projects and the Calendar show.
+
+## The default channel
+
+Every install has one default channel, **My channel**. Everything made before channels existed (templates, schedules, projects) belongs to it, unchanged. The default channel can't be deleted.
+
+## The Channels page
+
+The list shows each channel with **Open**, **Rename** and **Delete** (not on the default channel), and a line such as "Default · 3 templates · 5 in the cast". A press anywhere on a row picks it. Beside the list, on a wide screen, **About <channel>** sums up the picked channel: its templates and cast counts, its series brief (or "No series brief yet. Open the channel to say what it covers.") and its brand kit's intro, outro, document theme and end screen text, with **Open channel**.
+
+## Create a channel
+
+1. Open **Channels** and press **New channel**.
+2. Type a **Channel name** (up to 200 characters). It stays inside Slopify and doesn't have to match your YouTube channel.
+3. Press **Create channel**.
+4. Open the new channel and fill in its **Brand** tab (below).
+
+To rename a channel, press **Rename** on it, change the name and press **Rename channel**. To delete one, press **Delete channel**: its cast goes with it, and its videos move to the default channel and keep what they were made with. A channel that still has templates can't be deleted; move them to another channel first (see [Templates](Templates#move-a-template-to-another-channel)).
+
+## Which channel a video is in
+
+- On Play, pick the **Channel** under the title. A draft opened from a template starts in that template's channel; a new draft starts in the default one.
+- A template saved from Play lands in the draft's channel, or the one you pick in **Save a setup**.
+- A schedule belongs to the channel of the template it runs, so moving the template moves its schedules.
+
+## Show one channel's work
+
+The channel picker in the sidebar (**Current channel**) makes Home, Projects and the Calendar show only that channel's work. **All channels** shows everything. It only filters what you see; projects and schedules of other channels keep running. This browser remembers your choice.
+
+## The channel's tabs
+
+A channel page has six tabs: **Brand**, **Cast**, **Templates**, **Schedules**, **Episodes** and **Existing videos**.
+
+### Brand
+
+**YouTube AI disclosure.** Studio's **AI use** answer for this channel's videos and Shorts, given by Prepare upload and the Studio extension. It saves as soon as you pick.
+
+| Option | What it does |
+|---|---|
+| **Automatic** (default) | Says Yes only in YouTube's three cases: a voice marked as imitating a real person, real footage altered, or photorealistic AI pictures from an Image prompt marked as such. Otherwise No. |
+| **Always Yes** | Always answers Yes. |
+| **Always No** | Always answers No. |
+
+Mark voices in **Settings → Voices** and Image prompts in **Library → Prompts**. See [Publishing to YouTube](Publishing-to-YouTube).
+
+**Series brief.** What the channel covers, its style and what makes a topic worth a video. Topic generation reads it for every schedule of this channel that has no brief of its own. It doesn't change how videos are written. Up to 10,000 characters. See [Schedules](Schedules#topics-that-find-themselves).
+
+**Language of new projects.** The language this channel's new projects are written and narrated in when Play or the template picks none. It applies even with the brand kit off, since it is not styling. Pick voices that speak it. Not set means English. Projects already made keep their language. See [Other languages](Other-Languages).
+
+**Brand kit.** The look every template of this channel gets unless it sets its own. Every field is optional, each fills only what a template leaves at its default, and a blank field adds nothing.
+
+| Field | What it does |
+|---|---|
+| **Caption font** | The subtitle font for videos whose template leaves the font at Default. Fonts you upload in the subtitle font picker on Play appear here. |
+| **Caption colour** | Subtitle text colour as `#` and six hex digits, such as `#FFFFFF`. |
+| **Caption outline** | The colour of the line around each subtitle letter, such as `#000000`. A dark outline keeps light captions readable on bright pictures. |
+| **Title font** | The font of chapter cards and the end screen, for videos whose template sets no title style. |
+| **Title colour** | The text colour of chapter cards and the end screen, such as `#FFD700`. |
+| **End screen text** | A line shown centred over the last 5 seconds of every video, such as "Subscribe for more". Up to 200 characters. Blank shows none. |
+| **Intro** / **Outro** | An entry from **Library → Intros & Outros**, narrated before or after the body of every video whose template has none. Each is narrated with the video's voice, so each costs one voice request per video (plus a text call for an LLM entry), and it shows in the estimate. See [Intros and outros](Intros-and-Outros). |
+| **Document theme** | The look of the PDF for videos whose template picks no theme. A saved theme that was deleted is skipped. |
+| **Ambient sound** | Rain, Fireplace or Wind under the long video's narration, with its level (−40 to −6 dB, default −18), fade-in (0 to 30 s, default 3) and tail (0 to 30 s, default 6). Used when the template leaves its own ambient sound on "The channel's". A channel can't hold your own audio file. |
+
+**Channel links.** This channel's named links, such as `Patreon` or `Discord`, that a YouTube description fills when it names them in braces (`{{Patreon}}`). See [Channel links](#channel-links).
+
+Press **Save channel** when you are done.
+
+To keep one video exactly as its template was saved, untick **Use the channel's brand kit** on Play or in Edit project. The cast and language still apply. Nothing in the kit reaches a project that already started; a project keeps what it was started with.
+
+### Cast
+
+Recurring characters, creatures, places and objects, each with reference pictures that go with every image that names them. A cast member with a voice can also be one of the channel's hosts: a new podcast or interview on Play then starts with them as its speakers. See [Cast library](Cast-Library).
+
+### Templates
+
+The channel's templates. Each has a channel picker: choosing another channel moves the template, and every schedule that runs it, to that channel. Their next runs use the new channel's brand kit, cast and series brief. Projects already made keep what they were made with.
+
+### Schedules
+
+The schedules that run this channel's templates, with their status and next run. Edit them on **Calendar → Schedules**; see [Schedules](Schedules).
+
+### Episodes (episode memory)
+
+With **Episode memory** on, every finished video of the channel leaves a short summary, and new episodes about the same things read it so they agree with what came before.
+
+How it works:
+
+1. When a video of this channel finishes, one short call to its text model writes a summary of up to 150 words: what the episode covered, the facts it stated, who appeared and what happened to them. The call shows on the project's **Run cost**. Finishing the same article again asks nothing, and a failed call never touches the project.
+2. When a new episode's article (or multi-voice script) is written by Slopify, the summaries of up to 5 related earlier episodes are added to its writing prompt under "Earlier episodes".
+3. An episode is related when it features a cast member the new title or keywords mention (strongest), or shares words of its title. Words most of the channel's titles share, such as a template's fixed prefix, and one- or two-letter words don't count. An episode with the very same title is a remake, not an earlier episode, and is left out.
+4. The summaries are copied into the project when it starts, so later edits never make a finished video outdated.
+
+On the tab:
+
+- **Open** a summary to read or edit it. Your edited text is kept, even if the video finishes again.
+- **Delete** removes a summary from later prompts. The video itself is not changed.
+
+Default: on for new channels. Channels that existed before 3.0 start with it off.
+
+### Existing videos
+
+Titles this channel published before or outside Slopify. Topic generation and its duplicate checks skip them, as they skip the videos made here.
+
+**Paste titles:**
+
+1. Type or paste titles into **Paste titles**, one per line.
+2. Press **Add titles**. A title already listed (in any case) is skipped.
+
+**Import a YouTube Studio CSV:**
+
+1. In YouTube Studio, open **Analytics → Content → Advanced mode** and export the table as a CSV (comma-separated values).
+2. In Slopify, press **Import a YouTube Studio CSV…** and choose the file. It is read on this machine.
+3. Slopify lists every title with a tick, all ticked. It finds the title column by its header ("Video title", else "Title", else "Content") and skips Studio's "Total" row.
+4. If the export holds several series, type into **Keep only titles containing…** (for example a series name, any case). Only titles holding that text stay ticked. **Tick all** and **Untick all** reset the ticks, and you can tick each title by hand.
+5. Press **Add N ticked titles**. The import says how many were added and how many were skipped as already listed.
+
+The filter text is remembered for this channel's next import. **Remove** deletes one title, and **Remove all** clears the list.
+
+## Channel links
+
+Each channel keeps its own named links, under **Channel links** on its **Brand** tab. Write a link's name in braces in a description prompt or a description, such as `{{Patreon}}`, and it is filled with this channel's link when the description is shown, copied or downloaded.
+
+1. Open **Channels** → the channel → **Brand**.
+2. Under **Channel links**, press **Add link**, type the **name** (for example `Patreon`) and the URL (`https://…`). **Remove** takes one off.
+3. Press **Save channel**.
+
+Names match whatever their case or spacing. `{{Previous video}}` works the same way, but a project can set its own on its **YouTube** section (**Previous video for this project**, then **Save links**), which wins over the channel's. A placeholder with no link stays as typed, and the YouTube section says "No link is saved for {{…}}, so it stays as typed." with where to add it.
+
+Links saved in **Settings → Channel links** before channels had their own still fill the default channel's descriptions until you save its Brand tab; that Settings section now only points here (**Open the default channel's links**). Channel links travel in backups with their channel. See [YouTube description](YouTube-Description) and [Publishing to YouTube](Publishing-to-YouTube).
+
+## Tips
+
+- Give each series its own channel, even if you upload them to one YouTube channel. The brand kit, cast and topic ideas stay separate.
+- Import your existing videos before turning on topic generation, so Slopify doesn't suggest what you already made.
+- Edit an episode summary when it gets a fact wrong. Later episodes will follow your version.
+
+## Related pages
+
+- [Cast library](Cast-Library)
+- [Templates](Templates)
+- [Schedules](Schedules)
+- [Play video and style](Play-Video-and-Style)
+- [Publishing to YouTube](Publishing-to-YouTube)
+- [Other languages](Other-Languages)

package/dist/tutorials/Costs-and-Run-Cost.md

@@ -0,0 +1,136 @@
+# Costs and Run Cost
+
+Slopify shows what a run is likely to cost before you start it, what it actually cost once it ran, and, for runs on a command-line plan, what the same work would have cost with API keys and how much of your plan it used. All figures are in US dollars, from the providers' published prices.
+
+**Where to find it:** Play → **Estimated cost** in the right rail; a project → **Run cost** tab; Home → **This week**; Settings → **Usage**.
+
+## Where costs come from
+
+- Every successful provider call is recorded against its project with what it used: tokens in and out (and how many were cached) for text, characters for narration, images per model, seconds of animated video, and how long the call took.
+- Each call is priced when it finishes, from the model catalogue (see [Models](Models)). The rates are stored with the call, so a later price change never rewrites a finished run.
+- A model the catalogue has no price for, or a call whose provider reported no usage, is counted as unknown, never as free. Per-minute voices are left unpriced rather than guessed.
+- Failed calls are not charged here. Taxes and credits included in your provider plan are not counted.
+
+Your provider bills you directly; Slopify never handles payment. The figures are for planning and checking, not a bill.
+
+## Command-line runs: $0 on your plan
+
+Claude Code, Codex and Gemini bill your subscription, not per call. So their calls show as **$0 on your plan**. Beside that, Slopify shows what the same tokens would have cost through the API ("via API"), priced as the same model from the catalogue: Claude models as Anthropic's, Codex models as OpenAI's, Gemini models as Google's.
+
+There is no API figure for a model the catalogue does not list, for a CLI's default model, or for Codex images. The screens say so ("no API price is listed", "API price unknown").
+
+See [AI-CLIs](AI-CLIs#plan-limits-and-waiting-them-out) for the plan limits themselves.
+
+## Before you start: Estimated cost on Play
+
+The right rail on Play shows **Estimated cost** once the setup is complete. Until then it says "The estimate appears once the setup is complete."
+
+| Part | What it shows |
+|---|---|
+| **Estimated total** | The likely range for this run (or all the runs on the page), for example "$0.42 – $0.61". |
+| **Known subtotal** | Shown instead of the total when some stage has no price; a line below says how many stage charges have unavailable pricing. |
+| **Cost by stage** | Fold-out list: each stage's range and what it assumes. A CLI stage reads "$0 on your plan · ~$X via API". |
+| CLI steps line | "CLI steps: $0 on your plan · ~$X via API" for everything on a plan. |
+| Catalogue date | "Catalogue verified <date>". With several videos, rows show combined costs. |
+
+**Expected article words per video** drives the estimate for generated articles (and how many images **More images for long videos** adds). About 150 words is one minute. Default: 1500. Once the article is written, its real length is used.
+
+The estimate is what the providers are likely to charge, from their published prices. Actual usage can differ, and the estimate does not cap spending.
+
+## While a run is going: Cost so far
+
+On a running project, the side panel shows **Cost so far**:
+
+- **spent**: what has been paid to providers so far ("known, spent" when some calls have no price).
+- **same work via API**: the API equivalent of the CLI calls.
+- One meter per plan window a CLI reported, such as "Codex: 14% of your weekly limit". The meter turns amber once the plan is at 80% or more.
+
+When a CLI's plan is used up, the run waits instead of failing: the status reads **Waiting for limits**, for example "Waiting for Codex limits (resets at 14:00)". The run carries on by itself when the plan resets.
+
+## After a run: the run cost line
+
+When a run has ended, one line at the top of its project page, under the title, sums it up: for example `This run cost $0.42 · ~$3.10 via API · 12 min end to end`. A failed or cancelled run says **Spent so far**, and calls without a known price add "plus unpriced calls". **See cost by stage** opens the full breakdown below. The line doesn't show while the run is going, or when it spent nothing.
+
+## After a run: the Run cost tab
+
+1. Open the project from **Projects** or **Home**.
+2. Choose **Cost** in the section rail (or **See cost by stage** on the run cost line).
+
+If nothing has been spent yet, it says "Nothing has been spent yet. The cost of each provider call appears here as the run makes it."
+
+### Summary
+
+| Figure | What it is |
+|---|---|
+| **paid to providers** | The total cost of this project's calls. Reads "known cost, paid to providers" when some calls have no price, with a line "Plus N calls the model catalogue has no price for." |
+| **same work via API** | The API equivalent of the calls that ran on a CLI plan. |
+| Plan meters | One per plan window a CLI reported, for example "3% of weekly Codex limit". Hover or read the line below for the level it is at now. |
+| **end to end** | How long the whole run took. |
+
+Lines under the summary:
+
+- "CLI calls: $0 on your plan · ~$1.20 via API", when any call ran on a plan.
+- "This run used ~3% of your weekly Codex limit (now at 41%, resets Mon 09:00)." Codex reports whole percents, so a short run can read "under 1%".
+- When a CLI reported nothing (Gemini, or a Docker host helper older than the app), it says the share is not known.
+
+### By stage
+
+**Cost by stage**: what each stage has cost so far, from every provider call it made, retries and remakes included.
+
+| Column | What it shows |
+|---|---|
+| **Stage** | Research, Article, Audio, Images, Thumbnail, Video, Document. |
+| **Cost** | What you paid. "$0 on plan" for CLI stages; "Unknown" when no call in it has a price; "$0.40 + unknown" when some do not. |
+| **Via API** | The API equivalent for CLI calls, or "No API price". |
+| **Usage** | Tokens in and out (and cached), characters, images, seconds of video. |
+| **Time** | How long the stage ran. |
+
+### By model
+
+**Cost by model**: the same spending split by provider and model, with **Cost**, **Via API**, **Usage** and **Calls**. A CLI model shows the API model it was priced as, in brackets after "as". The CLI's own default model shows as "default model".
+
+The last lines give the total usage and stage time, and "Priced from the model catalogue of <date> when each call finished."
+
+## Across all projects: Home → This week
+
+Home's **This week** section, since Monday:
+
+- **videos made**.
+- **spent**, followed by "· ~$X via API" and "· N calls without a price" when they apply.
+- One bar per CLI plan: how much of its weekly limit is used, from the tool's last reading. The bar turns amber at 80%.
+
+It includes calls that belong to no project: a schedule's topic suggestions, a channel's episode summaries and a cast member's picture. These never appear on a project's Run cost tab. The channel picker at the top of Home narrows the numbers to one channel. See [Home-and-Projects](Home-and-Projects).
+
+## Your usage totals: Settings → Usage
+
+Settings → **Usage** shows this install's own counters, worked out on this computer from its event log:
+
+| Counter | What it counts |
+|---|---|
+| **Videos made** | Videos finished. |
+| **Hours of audio** | Narration made, in hours. |
+| **Images made** | Images drawn. |
+| **Tokens used** | Text tokens, in and out. |
+| **Projects** | Projects made. |
+
+Below them, **Tokens by stage** lists **Stage**, **Provider · model**, **Tokens in** and **Tokens out**. A fresh install says "Numbers appear after your first run." The last line shows the install's machine ID and Slopify version.
+
+The same counters, anonymised, feed the public totals on slopify.stream. They never include your keys, prompts, keywords, titles, text or files.
+
+To jump there, press `Ctrl+K` and run **Open usage and costs**. The old `/usage` address also opens this section.
+
+## Tips
+
+- Set **Expected article words per video** close to what your prompt really writes; it is the biggest lever on the estimate for a generated article.
+- Compare the **Via API** column with your plan's price to see whether a subscription or a key is cheaper for how you work.
+- If a total says "known cost", check which model has no price in [Models](Models) and add one to your catalogue file if you know it.
+
+## Related pages
+
+- [Models](Models)
+- [AI-CLIs](AI-CLIs)
+- [Providers-and-Keys](Providers-and-Keys)
+- [Play-Outputs](Play-Outputs)
+- [Project-Page](Project-Page)
+- [Home-and-Projects](Home-and-Projects)
+- [Settings-Reference](Settings-Reference)