Deckle 1.3.0

Added

• A queue for the assistant. Give it a job and it works in the background
  while you carry on writing: Assistant queue in the command palette, or the
  third tab beside Tasks and Bookmarks. Runs execute one at a time by default,
  or up to four at once if you'd rather several went in parallel.

  Every run writes into an Assistant inbox folder, which is the safety
  boundary: inside it the assistant works freely, and anything outside stops the
  run and shows you the same diff the chat panel would. Deleting always stops,
  wherever it is. A run that genuinely can't proceed can ask you a question and
  park until you answer it.

  The queue makes it plain which runs need you — a badge on the tab counts only
  those, because "three things are running" is not something you have to act on.
  Finished runs list the notes they wrote, and any run can be resumed (carrying
  on with what it had already done) or run again from scratch. A run interrupted
  by closing the tab says so, and offers to carry on.

  Runs are stored in your library under .deckle/runs/, so they survive a
  reload and travel with your notes.

Deckle 1.2.0

Added

• Assistant memory. The assistant can now remember what it learns about how
  you work — kept as ordinary Markdown files in .deckle/memory/ inside your
  library, so it syncs, backs up and exports with your notes, and opens in any
  editor. Read, edit, pin and delete any of it from Assistant memory in the
  command palette; turn the whole thing off in the assistant's settings.

  Only a one-line index goes into every message. Bodies are fetched when they
  are relevant to what you asked, within a token budget, so a large memory does
  not quietly become a large bill. Recording something it already knows updates
  the existing memory instead of adding a near-duplicate.

  Memory writes are the one kind of write the assistant makes without asking:
  they touch no note, and the panel is the receipt.

Deckle 1.1.0

Added

• An About box. The version was only in the keyboard sheet, which is no help
  unless you already know the shortcut. About Deckle — in the editor menu and
  the command palette — names the version, the library you have open, and which
  of the three backends is holding it, with links to this changelog and the
  source.

Deckle 1.0.0

The first tagged release. Deckle has been running and deployable for a while;
what is new is that a given build can now be named, pinned, and rolled back to.

Nothing about the app itself changes when you upgrade to it, but what
:latest means does — see below.

Added

• Versioning. Deckle follows Semantic Versioning from this release on. The
  version is shown in the keyboard sheet (?), logged at server startup, and
  returned by GET /api/v1/health as version, so a bug report or an agent can
  name the build it is talking to. The API's OpenAPI document reports it as
  info.version.
• Released image tags. :1.0.0 never moves, :1.0 takes fixes, :1 takes
  fixes and features but never a breaking change, and :latest follows the
  newest release.
• This changelog.

Changed

• :latest now means the newest release, not the newest commit. It used to
  be republished on every push to main, so docker compose pull took whatever
  had merged most recently, finished or not. If you were relying on that to
  track development, switch to :edge — otherwise there is nothing to do, and
  your next pull becomes a considered release rather than a branch tip.

Deprecated

• The pre-rename NIB_* configuration names and the .nib data folder are
  still read, and will keep being read for the whole 1.x series. They will
  be removed no earlier than 2.0.0. Rename NIB_* to DECKLE_* in your .env
  whenever it suits; the server logs which deprecated names it honoured at
  startup.

The app, as of 1.0.0

For anyone arriving here first, this release contains: live WYSIWYG Markdown
editing over plain .md files; three storage backends (a folder on disk, the
browser's private storage, or a volume on your own server) behind one interface;
a folder tree with drag-and-drop, spring-loaded folders and a Move to another
folder… dialog; import of Markdown files, folders and ZIPs into a folder you
choose; a Todoist-style task planner and bookmark collections stored inside the
library; per-note version history and a recycle bin; an AI assistant that can
search and edit the library with every change shown as an approvable diff;
a command palette; light and dark mode with seven palettes; a responsive layout
with drawers on a phone; and a token-authenticated REST API at /api/v1
described by a self-served OpenAPI 3.1 document.