v2.0.0 — Projects are files

Projects are files now. On the desktop, a project is a .tms9918 file you keep
wherever you want it — beside the assembly in a game's repository, most usefully —
that opens by double-click and goes through version control with everything else.
The web editor is unchanged and still lives at
acwright.github.io/TMS9918-EDITOR,
with its project list and its browser storage exactly as they were.

If you are upgrading from 1.6

The first launch says what is about to happen and copies your projects out of the
app's browser storage into ~/Documents/TMS9918 Editor, then puts them in Recent
Documents so they are one click away.

Nothing is moved. The originals stay in the app's browser storage until you press
Remove Browser Copies, and only copies that were actually written are ever removed.
A name already taken in that folder gets a number, and a project that could not be read
is named and skipped rather than dropped silently. If a copy goes wrong, the originals
are still there.

Downloads

Platform	File	First run
macOS (Apple silicon)	tms9918-editor-2.0.0-mac-arm64.dmg	Signed and notarized — opens with no Gatekeeper prompt
Windows (x64)	tms9918-editor-2.0.0-win-x64.exe	Unsigned installer, so SmartScreen warns — More info → Run anyway
Linux (x64)	tms9918-editor-2.0.0-linux-x86_64.AppImage	chmod +x, then run
Linux (x64)	tms9918-editor-2.0.0-linux-amd64.deb	sudo apt install ./tms9918-editor-2.0.0-linux-amd64.deb

The document app

• Double-click a .tms9918 file and the editor launches straight into it — cold, or
  into the app already running. Drop one on the window and it opens. The file carries its
  own icon and its own named type, so Finder calls it a TMS9918 Editor Project.
• A start screen instead of a project list: New Project…, New from Sample ▸,
  Open…, and Recent Documents, which are also in File ▸ Open Recent ▸. Quit with a
  document open and relaunching returns to it.
• A File menu that reads like a document app's — New Project…, New from Sample ▸,
  Open…, Open Recent ▸ │ Close Document, Save, Save a Copy… │ Reveal in Finder (Show in
  Explorer on Windows, Show in Files on Linux).
• Esc closes the document and returns to the start screen.
• The app holds one document at a time. Comparing two charsets means closing one;
  multiple windows are the next thing on the list.

It lives in a git repository properly

• The file is written to be read by git diff — one screen row per line, one character
  per line, a stable key order. A commit shows the eight bytes you changed, not one
  2000-character line.
• An idle editor does not dirty your working tree. A project nobody edited is not
  rewritten.
• A git checkout under a clean document reloads it in place and says so quietly. One
  under unsaved edits asks, naming both versions, and writes nothing until you answer.
• Autosave cannot overwrite a checkout. Every write states what it expects to find on
  disk and is refused if the file moved — measured against a real repository, with the
  autosave firing 500 ms into a branch switch and the checkout still whole afterwards.
• A document deleted behind the app's back is reported rather than silently recreated.

What you lose, said plainly

There is no project list on the desktop, because the file manager is one. Rename,
duplicate and delete are Finder or Explorer operations now, not buttons in the app.
File ▸ Save a Copy… covers branching off a variant. This is the trade the whole release
rests on and it is a real one.

Also

• Files downloaded from the web app — .tms9918.json — still open, through Open… or by
  dropping them on the window. They are deliberately not double-clickable: Windows
  associates on the last extension only, so claiming that one would claim .json
  system-wide.
• A Download from either build is now named after the project, with the bare extension.
• The web project manager now says where projects live and what clearing browsing data
  does to them.
• Share links made in the browser resolve against the published web app rather than the
  desktop app's internal URL — a 1.6 defect.

Verified, and not

Both macOS builds were run out of their own dmgs: notarized and Gatekeeper-accepted, the
double-click path opens a document and the next launch returns to it, recents are recorded,
and a document opened and left alone stayed byte-identical. The Windows and Linux
double-click is declared and not driven — the packages carry the association, but running
the NSIS installer is a real Windows job.