v0.27.0

Production, free.

For a script going into production. Other screenwriting apps charge for these tools; in Drafter they're free, like everything else. Your file stays plain Fountain, which any Fountain app opens.

• Lock pages and scene numbers. From the Production tab, lock the script.
  • A page that grows after the lock becomes an A-page (12A, 12B), and pages that shrink fold together (13-14), so the page numbers everyone else is using stay put.
  • A new scene between 5 and 6 shows as 5A on screen, in every export, and on the command line.
  • Omit scene marks a cut scene OMITTED, so no number shifts.
• Revisions in color. Start a revision set in the industry's order (Blue, Pink, Yellow, Green…). Every line whose words changed gets an asterisk in the margin, on screen and in print.
• Revised pages (PDF). Send out only the pages that changed: the current revision, all of them, or a page range. Each page carries a header such as "Blue Revision — 9 November 2026" and, if you like, a tint the color of its revision paper.
• A breakdown of every scene, as CSV for a spreadsheet or as PDF. It lists the scene number, INT/EXT, location, time, length in eighths of a page, the page it starts on, the cast, and the synopsis.
• Sides (PDF). Pick a character and their scenes are ticked; untick any not shooting that day. You get just the pages those scenes are on, with the other scenes on them crossed out.
• Every paged export prints the locked pages: the PDF, the web page (HTML), the e-book (EPUB), plain text, and drafter build on the command line. The full PDF has a Revision marks option for which marks print.
• Where to find it: the Production tab, Export, and the desktop app's File → Export. The Production help page explains each term once, in plain words.

Full details: CHANGELOG.

Downloads: the Windows x64 installer, the Linux .deb and AppImage, and Drafter for Claude (drafter-mcp-0.27.0.js, with its SHA-256).

v0.26.2

An About menu, and reports by email.

The top bar's Help menu is now two: Help for learning Drafter (the tour, the guides, the samples), and About for Drafter itself: About Drafter, What's new, Privacy, Licences, Technical details, Report a problem…, Suggest an idea…, and Check for updates…. On a phone, About folds into More actions so File keeps its place.

• Reports by email, no GitHub account needed. On drafter.dev, Report a problem… and Suggest an idea… can now Send email: the report, exactly as its preview shows, and a reply address if you give one, go to Drafter's maker through the site's own small server function. It sends only when you press the button, and never your script. Open on GitHub and your own email app are still there. What a report sends.
• Nothing stops your typing. A script whose file the browser hasn't let Drafter read yet stays editable; a missing file says your script is safe and offers Save to a new file… or Keep working without the file.
• Warnings in plain words. The status bar says Autosave: on, not guaranteed, or off, and the alerts, help pages, and the desktop app's close and update questions say the same.
• Reload and Restart don't ask needlessly. When autosave has your changes, Reload (and the desktop app's Restart) for a new version writes the last of your typing and reloads, with no question; it asks only when autosave isn't working.
• Drafter's settings block is out of sight. The /* drafter … */ lines at the end of a script are hidden in the editor and kept from being deleted; the file still has them.
• Up to date: Electron 45.2.1, pdf.js 6.5, and the MCP SDK 2.4.0 behind Drafter for Claude.

Full details: CHANGELOG.

Downloads: the Windows x64 installer, the Linux .deb and AppImage, and Drafter for Claude (drafter-mcp-0.26.2.js, with its SHA-256).

v0.26.1

Send your novel out.

A novel now exports as a standard manuscript, the format agents, editors, and contests ask for: Export → Manuscript (PDF)… or Manuscript (Word)… (also in the Drafter menu, the palette, and the desktop app's File → Export). How it works.

• A short box first. Manuscript details asks for the title page's details once (title, byline, legal name, contact lines, the header's surname and short title, the font) and keeps them in the book, so the next export asks nothing new. Every field is optional; a blank one is left off the page.
• The standard format. 12 pt Times-style or Courier, double-spaced, 1-inch margins, every paragraph indented. A title page with your contact details and "about 87,000 words"; the running header Surname / SHORT TITLE / page from page 2; each chapter a third of the way down a new page; a part on a page of its own; # between scenes; END after the last line; footnotes as endnotes.
• The Word file opens in Word and Pages with no question, its page numbers in the header. It uses Word's own Double spacing, so it runs to about a tenth more pages than the PDF.
• Private, as always. Both files are made on your device; nothing is sent anywhere. The details live only in your book's file and the files you export.

Full details: CHANGELOG.

Downloads: the Windows x64 installer, the Linux .deb and AppImage, and Drafter for Claude (drafter-mcp-0.26.1.js, with its SHA-256).

v0.26.0

A place to draft a novel, and a File menu.

Novel joins Screenplay and Stage play: a comfortable place to draft a book, in plain Markdown that any app opens. How it works.

• Chapters and sections. # for a chapter, ## or *** for a section, # Part One for a part.
• The Outline and Cards list every chapter and section with its words, a status (To do, Draft, Revised, Done), a synopsis, and a word target. Alt+arrow keys or a drag reorders them, text and all, in one undo step.
• Focus shows one chapter or section at a time (Ctrl+Alt+F, ⌘⌥F on a Mac). The rest of the book is hidden, never removed: saves, drafts, and exports still write the whole book.
• Counts and targets for the book and for each chapter or section, and Stats by chapter.
• Drafter for Claude reads a novel's parts, chapters, and sections, with their words, status, synopsis, and target.

The manuscript PDF and Word file follow in v0.26.1.

Also new:

• A File menu. The top bar's Open button is now File: New, the guided starters, Open, Open as screenplay, Save As, Revert to Saved, your scripts in this browser, and the samples.
• Save As beside Save. The arrow next to Save has Save As…, Revert to Saved, and History.
• Export → Fountain. Saves a copy of your script and leaves you working on your own file.
• A shorter Drafter menu, with the script's own things: its template, History, drafts and cuts, its exports, Stats, and Settings.
• A quieter first visit. The recovery-copy warning waits until the welcome has closed.
• The help pages' links are four dropdowns (Help, Writing, Files, About) in place of a long row.

Full details: CHANGELOG.

Downloads: the Windows x64 installer, the Linux .deb and AppImage, and Drafter for Claude (drafter-mcp-0.26.0.js, with its SHA-256).

v0.25.1

Your script stays with you, and an audit shows it.

This release comes from two audits, both recorded in the README's Audit record:

• A privacy audit. Nothing about a script is stored in the cloud, and Drafter uses no AI. A full writing session on drafter.dev sent the script in no request.
• A red/blue team audit. Four attackers tried to break Drafter, and every finding was checked and fixed.

What it fixed:

• Final Draft exports no longer carry notes you chose to leave out. Before, Final Draft printed them as script text.
• The desktop app asks before a page opens any address but Drafter's own links.
• A crafted Markdown file can no longer freeze the app, or stall the Preview and exports.
• drafter.dev's visit counter gets page views only. It's Plausible: privacy-first, with no cookies and no ads.
• The browser no longer keeps a Story map's logline or a synopsis in its form history. Its own spellcheck is off, as Chrome's and Edge's enhanced modes send text to Google or Microsoft.
• drafter build never writes through a planted link. Drafter for Claude lists a folder even with a huge file in it.

New:

• Contrast. A button in the top bar has a slider for the Source and one for the Script, in light and dark. Under each is its WCAG 2.1 contrast ratio. Both start near the highest.
• Typewriter sounds (Settings → Writing, off by default). A key's clack as you type, and the bell at each new line. They're named apart from Typewriter scrolling everywhere.
• Copy technical details (Help). Your version, system, browser, and setup, for a bug report or a feature request. Never your script.
• Hide the script's title in the tab (Settings). Browsers keep a tab's title in their history.

Full details: CHANGELOG.

Downloads: the Windows x64 installer, the Linux .deb and AppImage, and Drafter for Claude (drafter-mcp-0.25.1.js, with its SHA-256).

v0.25.0

Classic Mode. For writers who'd rather not learn Fountain's marks. Click Classic in the top bar's Fountain | Classic switch, or use Settings, the command palette, or Mod+Alt+0. Then the script types the way many screenwriting apps work:

• Enter and Tab move from element to element. Enter after a heading gives Action, after a name gives Dialogue, and after a speech gives the next name. Tab turns Action into a name, and a speech into a parenthetical.
• Names and places fill themselves in from the first letter.
• Capitals and marks are done for you. Headings, names, and transitions capitalise themselves.
• The left side looks like a script. The marks are hidden, and each element sits where a page puts it.
• On a phone, a Next button above the keyboard does what Tab does.

Your file stays plain Fountain. It holds exactly what you could have typed by hand, so nothing is locked in. Fountain Mode stays the default, and switching changes nothing you've written. The Classic Mode help page has every key.

Also in this release:

• On phones narrower than 480px, the top bar shows Drafter's mark instead of the full name, so Save and Export stay on the bar.
• A Markdown quote nested thousands deep no longer stops the Source pane from updating.

Full details: CHANGELOG.

Downloads: Windows x64 installer, Linux .deb and AppImage, and Drafter for Claude (drafter-mcp-0.25.0.js with its SHA-256).

v0.24.3

Self-hosting. Run Drafter's web app from your own computer or server, so nothing loads from drafter.dev.

git clone https://github.com/cschweda/drafter.git
cd drafter
docker compose up -d

Then open http://localhost:8080. It sends drafter.dev's security headers, has no analytics, and stores no scripts: your work stays in your browser and your files. It runs as an unprivileged user on a read-only filesystem, reachable only from its own computer unless you add your own HTTPS proxy.

For privacy alone, the desktop app is usually the better choice. The README and the Self-hosting help page cover the steps, the downsides, and when each makes sense.

Also in this release:

• publish.sh uses npm's browser approval.
• pnpm install sets the Git hooks only in a Git work tree.

Full details: CHANGELOG.

Downloads: Windows x64 installer, Linux .deb and AppImage, and Drafter for Claude (drafter-mcp-0.24.3.js with its SHA-256).

v0.24.2

Drafter for Claude. A local, read-only MCP server, drafter-mcp, lets Claude Desktop, Claude Code, or any app that speaks MCP read the scripts, drafts, and cuts in folders you choose: storyboards, reader's notes, character arcs, ideas from your cuts, and continuity across a series. Drafter itself never calls an AI.

• Ten read-only tools and seven prompts (storyboard, shot list, reader's notes, character arc, ideas from cuts, continuity, previously on).
• Only the folders you name, never hidden files; every file judged by what's inside it, as Open does; notes and the boneyard left out unless you ask; every answer under 40,000 characters; each request stopped at 10 seconds.
• Get it: npx -y drafter-mcp@0.24.2 --folder <your scripts folder>, or download drafter-mcp-0.24.2.js below and check it against drafter-mcp-0.24.2.js.sha256. Setup for Claude Desktop and Claude Code: https://drafter.dev/docs/drafter-for-claude/

Also in this release:

• A click on a note shows it in the Source, line numbers on or off.
• Check for updates shows that it's working, and says when a new version is downloading.
• drafter.dev (the website only) measures visits with Plausible, privacy-focused analytics with no cookies. The downloaded app has no analytics at all.
• The browser tests now run, and must pass, on every pull request.

Full details: CHANGELOG.

Downloads: Windows x64 installer, Linux .deb and AppImage, and Drafter for Claude (drafter-mcp-0.24.2.js with its SHA-256).

v0.24.1

Story map, and the security audit's fixes. Export → Story map makes one dark, phone-first page that answers "What are you writing?" in pictures: the shape of the story, its people, and every scene so far, with a few lines of dialogue. It runs no code and fetches nothing, and your notes never go in. The desktop app takes a dropped file only from a real drop, and every pull request is checked on GitHub.

Added

• Story map: one page that answers "What are you writing?" in pictures, to send by text or email to anyone who doesn't read scripts. Export → Story map… (the toolbar's Export menu, the Drafter menu, the palette, and the desktop app's File → Export) opens Make a story map, a short dialog whose choices start sensible, so Enter makes the page. It saves one file, <title> – story map.html.
  • What's on it: the title, your name with "What I'm writing" under it, the logline, how far along it is, and big numbers (pages, running time, scenes, characters, places); the shape of the story along its pages, coloured by time of day or by act, with inside and outside, day and night, and how long the scenes run; the characters, ranked by screen time, with cards for the eight who lead (a hook from their introduction, where they appear, and a line of their own) and who shares the most scenes; every scene in order, with where and when, its length, a one-line summary, who is in it, and now and then a line of dialogue; the places, sized by time spent there; and your setups joined to their payoffs. Every chart has Show as a table. No screenwriting words: Inside and Outside, minutes and pages.
  • The dialog: In progress or Finished, an optional planned length in pages, the logline, the line under your name, the sentence that explains the page, what goes in (scene summaries, lines of dialogue, and threads on; your contact off), and, folded away, the lines Drafter picked (untick one, or Pick another from the same scene) and each lead's hook. The logline is written to the title page as Logline: (it never prints in the script), the planned length and edited hooks to the metadata block, and the other choices are kept per script in this browser. On a phone the dialog is a sheet.
  • Lines of dialogue are picked for you, about one scene in four, at most 12, 3 to 18 words each. [[Quote]] in a speech always puts it in; [[No quote]] keeps it out. Use in story map and Never use in story map write them for the speech at the cursor, in one undo (the palette, and the desktop app's Edit and right-click menus).
  • Gaps, shown as unfinished, not broken: an act with nothing in it, a planned scene (a heading with no action or dialogue), a to-do note (the mark only, never its words), and the pages still to write when you give a planned length. One sentence sums it up and never says more than the numbers. Finished leaves the planned scenes out and says "The end".
  • Acts only when you mark them (# sections, or headings that start with "Act"); otherwise the scenes are one run, "The story". A one-act play reads "A one-act play in progress". An early draft (under 10 pages or 6 scenes) keeps the shape simple.
  • Stage plays: settings in place of places; an interval between Acts 1 and 2 when there are two acts or more, moved with [[Interval]] or turned off with [[No interval]]; and who's on stage, a bar per character from entrance to exit with a plain sentence ("Dev enters halfway"), and the pairs who share the stage most.
  • Private and safe: notes are never included (only Setup and Payoff names, with Threads on), nor the boneyard, to-do text, revision marks, or the script itself. The page has no JavaScript, a security policy that lets it load nothing, and its fonts inside (Anton, Archivo, and Courier Prime, all under the SIL Open Font License, listed on the Third-party licences page). It is dark on screen, prints light, and a 120-page script's is about 250 KB.
  • A Story map help page, linked from Help, What is Drafter?, and What's new.
• drafter build script.fountain --story-map map.html writes the same page from the command line, with the dialog's starting choices and no contact; --status in-progress or --status finished says which. A Drafter draft file shows its draft's number and ID; any other file is Draft 01 with the SHA-256 of its text.
• Four new trap documents (262 in all): hostile titles, names, places, and lines in a story map, a 100,000-character name, a 10,000-character marked line, and a name said 50,000 times. Every inert trap's story map is checked to stay inert.
• docs: a second clean-room audit, 1 November 2026 (docs/clean-room-audit-2026-11-01.md), over everything since the first (v0.3.1 to v0.24.0, and the Story map plan): no copied code, no screenwriting package, no GPL code shipped, and every Final Draft, Highland, and Fade In test file synthetic. It compares itself with the first audit check by check, and lists two small fixes (a film catchphrase back in one test, and an unrecorded source for 18 Final Draft element names). The first audit is now docs/clean-room-audit-2026-10-27.md. A new index, docs/AUDITS.md, lists every security, clean-room, and accessibility audit, newest first, linked from the README, Developing Drafter, and SECURITY.md.
• What is Drafter? links Audits from Can I trust this? and from its technical links.
• docs: Drafter's first formal security audit, 1 November 2026 (docs/security-audit-2026-11-01.md), of the web app, the desktop app, the command line, the build, and the security claims in the docs: no exploitable hole, and nothing leaves the device. To fix: turn on GitHub's private vulnerability reporting. It compares itself with the earlier security reviews, area by area, and is listed in docs/AUDITS.md, SECURITY.md, and the README.

Changed

• Every pull request is checked automatically on GitHub (lint, build, every test suite, the trap documents, and the browser tests in Chromium), Dependabot's included.
• The spellcheck's budget for a check after a one-letter edit is 150 ms, generous enough for a shared CI machine, as its own comment intends.
• The outline's twenty-thousand-run Markdown property test has a minute to finish, not the default five seconds.
• The pull-request checks skip the tests with a fixed time limit, which the release gates still run; the tests that compare a script with one 4 or 8 times its size run everywhere.
• The tests that copy the fonts, dictionaries, and icons into the web app have half a minute each (set with vi.setConfig, which the linter accepts).
• The pull-request checks require lint, the build, every unit test, the trap documents, and the typechecks; the browser tests run too, on macOS and Linux, shown but not required, since a shared runner is too slow for them to be reliable (DEFERRED tracks it). The full browser suite stays a release gate. On CI, Playwright also writes an HTML report, kept with a failed run. The browser-test jobs build the packages first, since some tests read them.
• A second clean-room audit (1 November 2026, docs/clean-room-audit-2026-11-01.md), with an index of every audit, newest first (docs/AUDITS.md). What it asked for is done: a film line and a film's names in tests are original now, and the Final Draft settings names say where they come from.
• docs/DEPENDENCIES.md names every workspace edge its rows had missed (history, lint, the editor package, and the command line) and two tools: axe in the desktop tests, and the Mermaid command line the diagrams are drawn with (through npx, never installed).
• shares (whole percents that add up to 100) moved from the app's Stats code to @drafter/cast, so the story map and the Stats tab round alike. @drafter/fountain gains setTitleField, and a title page holding only Logline: is a title page. @drafter/notes reads the whole-note marks [[Quote]], [[No quote]], [[Interval]], and [[No interval]] (wholeMarkOf). @drafter/render-html-file exports cspHash, base64, fontKind, and langOf.
• Requests to the export worker go one at a time, so the story map dialog's look at the lines never collides with an export already running.
• The Story map design (docs/drafter-story-map-design.md), approved with mockups for a screenplay and a stage play, is in the repository; Story map ships in v0.24.1.
• The desktop build makes the history package and the packages it needs before the desktop tests, which read it from its source.
• The desktop menu test for Report a Problem… types the report before it looks for the version info, which the preview shows once there is something to send.

Security

• Desktop: a dropped file is granted only when the preload saw the browser's own drop event and told the main process; the page then claims it by an opaque id, once, and can no longer hand the main process a path for a drop (security audit F2).
• CI: the Linux, Windows, and Mac jobs check out with persist-credentials: false, as publish already did, so no job leaves its token in .git/config. The workflow stays contents: read, with contents: write on publish alone, which makes the release (security audit F7).
• Dependabot: weekly version updates for npm and GitHub Actions, minor and patch grouped into one PR each (.github/dependabot.yml). Dependabot alerts and security updates are on in the repository's settings (security audit F4).
• Nuxt 4.6.3 (from 4.6.2), which clears its five advisories (the dev server's file reads and config, and server/middleware dot segments; none reached drafter.dev, a static site). pnpm audit --prod goes from 25 advisories to 20; the rest are in build and dev-server tooling (security audit F3).
• Technical details no longer says the app has no v-html: Drafter's own code has none, and the one library component that does, Nuxt UI's palette, has its label slot replaced with text. The palette test now also searches inside th...

v0.24.0

Drafts and Cuts. Start new draft keeps your script as Draft 01, 02, and so on, each with an ID of its own, and Draft by draft shows how it changed. Cuts keeps everything you cut, for good, to browse for ideas, and replaces Deleted scenes. The desktop app now writes <script>.cuts.md and a <script> drafts folder beside your script, without asking (for Boca.fountain: Boca.fountain.cuts.md and Boca drafts/); Chrome and Edge ask once for the script's folder, and other browsers keep them in the browser, with Export drafts and cuts.

Added

• Drafts. Start new draft… (the Drafter menu, the command palette, the Drafts list, and the desktop app's File menu) keeps your script as it is now as a numbered draft, with an optional note such as "sent to Sam for notes", and you carry on writing the next one. Drafts are numbered Draft 01, Draft 02, and so on; a number is never used twice, and Drafter never starts a draft by itself. Any script works this way, including one written before this release or opened from Final Draft, Highland, or Fade In: what is there becomes Draft 01. Freezing text that hasn't changed since the last draft asks first.
• Every draft has an ID worked out from its exact text (SHA-256), shown as seven characters such as a3f9c2e. Typing four or more of them in the command palette finds the draft, in any of your scripts.
• The Drafts list (Drafts…, or the "Draft 03" in the status bar) shows each draft, newest first, with its ID, date, words, note, and a line such as "Draft 03 begins — builds on Draft 02 (a3f9c2e)". Read opens a draft read-only beside your script, to copy from; Compare shows what changed against now or another draft; Restore as a new draft keeps what you have as a draft first, then brings the old text back as the draft you are writing, in one undo; and each has Copy full ID and Edit note…. Its filter finds a draft by number ("2", "02", "draft 2"), ID, or note. Drafts can't be deleted, and they show in History above the snapshots.
• Draft by draft… shows how the work changed, one draft to the next: for each step, its note and date, the words added or taken out, the scenes (or chapters and sections) added, cut, and changed, and how much of the text is new. Open a step in Compare and walk with Previous step and Next step; beside the changes, "Cut while writing Draft 02" lists that step's cuts, with Show in Cuts.
• Cuts. Cuts… keeps everything you cut, for good, in screenplays, stage plays, and Markdown documents alike: a whole scene, chapter, or section; a whole speech, action paragraph, transition, paragraph, or list item taken out of one that is still there, at any length; and any run of 12 or more words taken out, or replaced by quite different words. Typo fixes, small rewordings, and moved text are not cuts. Cuts are found each time a snapshot is kept, never as you type, and restoring, opening, or reloading a script makes none.
• The Cuts list is for browsing for ideas. Group cuts by Scene (or Section), so a scene trimmed over several drafts reads as one group, or by Draft. Each cut says when it was cut and in which draft ("Cut while writing Draft 03"), and has Put back (where it was: a scene between its old neighbours, a passage after the line it followed), Insert at cursor (at the next scene or paragraph after your cursor), and Copy. One undo takes back a Put back or an Insert. A cut you put back stays listed, marked. The filter finds words, headings, and draft numbers, and the list stays quick with thousands of cuts. In Compare, a scene or section that is gone has Find in Cuts.
• Cut before drafts. The first time v0.24.0 runs, it looks once through the snapshots you already have, in the background, and keeps what was cut there too, marked "Cut before drafts".
• Drafts and cuts as plain files beside your script. For Boca.fountain: a folder Boca drafts with Boca – Draft 01.fountain and so on (each your script as it was, with the draft's number, ID, date, and note in a short block at the end that other Fountain apps don't print), and Boca.fountain.cuts.md, a readable Markdown file of every cut. A draft file is never written over and none is ever deleted; the cuts file is read and merged before it is written again. Save As writes the whole set beside the new file and leaves the old one. The Drafts and Cuts lists always say where they are: "Saved beside Boca.fountain." or "In this browser only."
  • The desktop app writes them beside the script, always (an unsaved script's when it is first saved).
  • Chrome and Edge on a computer ask once, at your first new draft, for the folder that holds the script ("Keep drafts and cuts next to Boca.fountain?"), check that it does, and remember it for that script. Not now keeps them in the browser, and the lists' Keep next to Boca.fountain… asks again.
  • Firefox, Safari, and phones keep them in the browser. Export drafts and cuts, in both lists and in every browser, downloads Boca drafts and cuts.zip.
• Two computers. Opening a script, or coming back to Drafter after a while away, reads its drafts folder and cuts file and adds what another computer kept, through Dropbox, Google Drive, OneDrive, or any synced folder: every cut once, and every draft. If both computers started a Draft 04, both are kept ("Draft 04 (from another computer)", written as Boca – Draft 04 (2).fountain), and a draft file changed in another program is listed as "changed outside Drafter". Opening a draft file itself opens it read-only, as it was frozen, says "This is Draft 03 of Boca.", and offers Open a copy to keep writing (Save asks where to keep the copy; the draft file is never changed) and Open Boca instead.
• When they can't be written beside the script, the Drafts and Cuts lists say so instead of "Saved beside": "Couldn't write beside Boca.fountain: the disk is full.", with how to put it right, said once. One draft file that can't be written doesn't stop the rest, or the cuts file. A cut in the cuts file Drafter can't read (damaged by hand, say) is kept in the file as it is, never dropped, and a script renamed outside Drafter says once that its drafts and cuts now go under the new name.
• A help page, Drafts and cuts (Help, and the desktop app's Help menu), in plain words.
• 14 more trap documents, for hostile and damaged draft and cuts files (258 in all).
• .gitignore also allows a .env.sample (as well as .env.example); every other .env file stays out of the repository.
• Report a problem… and Suggest an idea…, in Help, the search, About, and the desktop app's Help menu. A dialog asks for a title and a few lines (what happened and what you expected, or what you'd like), adds your version info if you leave it on, and shows exactly what will be sent. Open on GitHub opens GitHub's new-issue page with it filled in, through new issue forms (.github/ISSUE_TEMPLATE/bug.yml, idea.yml, and config.yml), and you submit it there with a free GitHub account. Drafter sends nothing itself and never includes your script. A report is never lost: Copy report, Write an email, and Open on GitHub each put the whole report on the clipboard (the preview, never trimmed, and selectable to copy by hand), and say so, since a long one is trimmed to fit the link or the email; and the report is kept on this device until you choose Clear, through a closed tab, a reload, or a restart. Offline, it says to copy it and file it later. No GitHub account? Email cschweda@gmail.com from your own email app (the desktop app hands that one address to the email app, and no other mailto:). About has a contact line, and the help index and Privacy say what leaves your device, and when.
• An animated banner at the top of the README: the script page fans out into the colored revision pages, once. It's an SVG with CSS only, so it plays on GitHub, and it holds still for anyone who asks their computer for less motion.

Changed

• Cuts replaces Deleted scenes, in the More menu, the command palette ("deleted scenes" still finds it), the Drafter menu, History, and the phone's More. It keeps passages and Markdown sections as well as scenes, keeps them for good, and puts a cut back by its old neighbours' headings rather than from a snapshot.
• Drafter's database gains two tables, drafts and cuts. Every script, snapshot, and setting from v0.23 is kept as it is, and a tab of v0.23 left open still reads it.
• Drafter keeps a snapshot just before it starts a draft ("Before starting a draft") and before Restore as a new draft keeps your text as a draft, so cuts made just before are kept, with the draft they were made in.
• The Saving and your browser help page's Deleted scenes section is now Drafts and Cuts, and points to the new page; Why Drafter and Technical details say where drafts and cuts are kept.
• SECURITY.md's fallback is an email now: if GitHub's private report isn't there, email cschweda@gmail.com with the details, never a public issue. The README's Security section, What is Drafter?, and the new dialog say the same.

Removed

• Deleted scenes, replaced by Cuts (above). Its tab, its command, and its pane are gone; the command palette's "deleted scenes" opens Cuts.
• The P and H keys in the Deleted scenes list (Put back, and History of this scene). Each cut's Put back, Insert at cursor, and Copy are ordinary buttons in the Tab order.
• History of this scene from that list. A cut is kept apart from the snapshots, so it has no scene history to open; History of this scene is still in a scene's menu in the Outline, the Cards, and the Structure strip, and in the command palette.
• Compare that version with now, from the same list: Find in Cuts goes the other way, from Compare to the cut.

Fixed

• Nothing you cut ages out any more. Deleted scenes could list a s...