k0-board 0.4.0 → 0.6.0

package/CHANGELOG.md

@@ -6,6 +6,428 @@ All notable changes to this project are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.6.0]
+
+k0 gets an account and a cloud. The board still runs on your machine and keeps working with no
+network, but it now keeps a copy of itself in k0 Cloud, signs in with GitHub or Google, and numbers
+every story once for your whole account instead of once per repository; a board that existed before
+moves over once, after you have seen every old number beside its new one. k0 is in early access,
+and from this version on it is source-available under the Sustainable Use License rather than MIT.
+
+### Added
+
+- **k0 Cloud: your board keeps a copy of itself, and you sign in with GitHub or Google.** The board
+  still lives on your machine and works with no network at all; every few seconds it sends what
+  changed and fetches what your other machines changed, so it survives a lost laptop and reaches a
+  second one. Which terminal a session is in, the folder it works in and the commit it started at
+  never leave the machine, and nothing from your repositories goes up — not files, not commits.
+  k0 is in early access: once you are signed in the board says *You are on the list* and sends
+  nothing until your account has been approved, and it notices the approval by itself. The
+  sign-in screen only stands in front of the board when there is a way past it. A read-only board
+  on the web, and the page where accounts are approved, are coming with the site.
+- **A key is one number for your whole account.** `K150` is the same story in every repository and
+  on every machine, and the number comes from the cloud the moment the story is made. Without a
+  connection the story is made anyway with a provisional key, `K~3`, which becomes a real one —
+  file in `.k0/` renamed with it — as soon as the cloud answers again. Without an account the same
+  single counter is kept on your machine.
+- **Moving a board you already had to the account, once, when you say so.** The first time you
+  sign in on a machine whose board has stories, nothing is sent until the board has been moved:
+  the board shows every old key beside its new one, repository by repository, and how many plans,
+  prompts and decisions mention a key. On yes it keeps a copy of the whole board first, renumbers
+  everything in the order it was made, updates the keys written inside the text, renames the
+  files in `.k0/`, and leaves a list of every old key and its new one beside the copy. *Not now*
+  leaves the board exactly as it was.
+- **Who is signed in, and whether the cloud has everything, at the end of the top bar.** Your
+  picture and a dot: green when everything is in the cloud, amber while changes are waiting, grey
+  when the cloud cannot be reached and the board is carrying on by itself. Its menu has *Sync now*
+  and *Sign out*.
+- **`k0-board login` and `k0-board logout`**, and a *k0 Cloud* section in `k0-board doctor` saying
+  who is signed in, whether they have been let in, whether the board still has to be moved, and
+  how many changes are waiting.
+
+How far this has been tried: the whole road was run against the real cloud with a throwaway
+account — signing in, waiting to be let in, the move, a new story numbered by the cloud, and its
+rows arriving there — and the move was rehearsed on a copy of a real board of 938 stories across
+25 repositories. Signing in with GitHub or Google for real has not been tried yet, because neither
+is switched on in the cloud.
+
+### Changed
+
+- **A story moved to another repository keeps its key.** It used to be given a new one from the
+  repository it moved to; now that a key is one number for the whole account, there is nothing
+  there for it to collide with.
+
+- **k0 is now under the Sustainable Use License instead of MIT.** The code stays public, all of it,
+  and you can still use it, change it, and run it for yourself or inside your company; what the
+  license no longer allows is taking k0 and selling it to other people as a hosted service. It is
+  source-available, not open source, and k0 no longer calls itself that. Versions up to and
+  including 0.5.0 were released under MIT and remain under it. The manual and the security notes
+  also stop saying that k0 makes a single network request: it now has an account and a cloud of
+  its own, and they say so — two places, the cloud and the daily version check, and still nothing
+  else.
+
+### Fixed
+
+- **The new tests pass on Windows too.** Nothing about k0 itself changed.
+
+## [0.5.0]
+
+**The board tells you what to do next, and starts it.** Every story carries one button saying the
+one thing to do with it — *Discuss*, *Plan*, *Work*, or *Resume* on a terminal that was closed —
+and pressing it opens a terminal with the command already sent. Beside it, **Quick Start** opens an
+empty one and leaves the typing to you: the long way round and the short way in, and nothing else.
+You work there and come back when it is done. That is the whole shape of it: the board is the menu,
+the commands are the engine, and you no longer have to know ten commands by heart to find the way
+in.
+
+Underneath that, the board learns what the work is *about*. A post-it is now a **story** with a
+stable key of its own — `K42`, and it keeps it for life — and stories can sit under an **epic**, be
+split into tasks, wait on each other, and carry the **decisions** that were taken while they were
+discussed. A `.k0/` folder in each repository keeps a readable copy that survives a lost database,
+and a **counter-check** holds the finished work up against every decision, one by one, before
+anybody presses Done. None of it changes the board you already know: switch the backlog off and it
+is exactly the board it was.
+
+### Added
+
+- **What Claude points at in a session is one click away, while k0 is running.** Everything the
+  last reply named — an address, a folder, a document, an artifact the session published — sits in
+  a row just above the prompt, and one click opens it: the browser, Finder, the file viewer, or the
+  artifact's claude.ai page. Claude's reply itself is left exactly as it was drawn. It is a Claude
+  Code mod the installer offers together with the commands, so it works in every session on the
+  machine, and it does nothing at all while k0 is off.
+- **A button on every story saying what to do with it next, which opens the terminal on it.**
+  *Discuss* on something nothing has been decided about, *Plan* once it has been discussed, *Work*
+  once there is a plan, and *Resume* on a story whose terminal was closed — three words in the
+  order the work goes in, and a fourth that is not a command at all. Hover it and it says why this
+  and not something else. Pressing it opens a terminal with `/k0-plan K42` already in it and
+  already sent, rather than left sitting under the cursor. A story with a session running carries
+  no button, because the terminal is where the work is and a double click on the note goes there;
+  so does one waiting to be looked over, and one that is done. k0 works out which, and it is the
+  same reasoning `/k0-next` does — so the note, the row in the list and the command can never give
+  you three different answers. Only `/k0-work` counts as the work having begun: pressing *Discuss*
+  leaves the story where it was until the discussion moves it.
+- **Quick Start, the short way in.** It opens a terminal on the story with nothing in it and lets
+  you type there. It is the plain button on a story with no suggestion and a quiet link beside the
+  suggestion on one that has, and it is what the `+` offers next to *Discuss* when you write a new
+  story down.
+- **Notes on a story, which are yours and go nowhere.** Editing a story gives you a list to jot
+  things into; they sit on the post-it where you can read them and are never sent to Claude Code.
+  A story being written for the first time is not asked for them: at that moment there is nothing
+  to note down yet.
+- **The flag is put on from the note, in passing.** It was a checkbox in the pencil dialog, which
+  meant opening the dialog, ticking a box and saving for a mark you change your mind about twice a
+  day. It is now the glyph at the bottom corner of the post-it: invisible until the pointer is on
+  the note, one click on, one click off. A flagged note keeps it lit, takes its border, and its key
+  and title take the same colour — so you can tell a flagged one from across the room and not only
+  by a hairline.
+- **The repository menu is k0's own, with a search in it.** It was the system's dropdown, which on
+  macOS opens a panel from another application in the middle of a board made of paper and cannot
+  hold a search at all. It is now the same picker the new-story dialog has: type three letters,
+  press Enter.
+- **Epics, stories and tasks.** One post-it is one story. A story can belong to an epic, and a
+  story that turned out too big to close is split into tasks that inherit its context. Every one
+  of them gets a key — `K42` — that is never reused and never reassigned. That key is the only
+  name a story has: where it sits is the tree itself, which can be read.
+- **Decisions you can hold work against.** What was settled while a story was discussed is
+  written down one sentence at a time, numbered, and never rewritten — a decision that changes is
+  *superseded* by the one that replaced it, and both stay. An epic's decisions are inherited by
+  every story under it rather than copied into them, so reversing one reverses it everywhere at
+  once.
+- **The counter-check.** `/k0-verify` walks the finished work against every decision the story is
+  held to and records a verdict for each, with the evidence. It answers all of them or the run
+  does not count, and it never writes over the run before it. A story cannot be marked Done while
+  a decision the counter-check found broken has not been answered since — k0 names it, says which
+  run found it and what to do about it, instead of quietly letting it through.
+- **Nine commands you type.** `/k0-epic`, `/k0-story`, `/k0-discuss`, `/k0-split`, `/k0-plan`,
+  `/k0-work`, `/k0-verify`, `/k0-next`, `/k0-order`. **The installer offers to copy them into your
+  own `~/.claude/skills/` in one question**, together with `/k0-import` — and that question is the
+  whole setup, because Claude Code looks for a command in the repository you have open and in your
+  own skills folder and nowhere else. A command that was never copied out is a command that does
+  not exist, and the buttons on the board that offer to run one lead nowhere. If you are not sure
+  you said yes, run `npx k0-board@latest` again: it asks only about the ones that are missing.
+  They ask their questions in rounds, say how many rounds are left, stop when nothing more would
+  change the work, and write every round down before asking the next one — so a terminal that dies
+  at round three does not take the first three with it. Everything you say is stored in the
+  language you said it in.
+- **A flag, and what waits on what.** A story can be flagged — from the pencil, with the rest of
+  what you decide about a story — and it is drawn in the corner of the note with a border round
+  the note in the same colour, so a flagged story can be picked out from across the room. A story
+  can also be told to wait on another one. Waiting is a note and not a lock: nothing refuses to
+  start a story that is waiting, the note is simply marked and it sinks down the running order.
+  Opened in the list, a story says both directions: what it is waiting for, and what is waiting for
+  it — which is usually the real reason to finish one thing before another.
+- **Something that says what to pick up next.** `/k0-next` answers in one sentence, and the
+  answer is k0's rather than the model's — a live session first, then whatever has been sitting
+  in Review longest, then what is not waiting on unfinished work, then the flag. Ask twice and
+  you get the same answer.
+- **Two views of the same stories: Kanban and List.** The switch is in among the filters, because
+  it is the same kind of question — the state pills, the repository and the epic apply to both, so
+  changing shape never changes what is in scope. **Kanban** is the board you know, for working: one
+  column per repository, and a note now carrying its key, its epic as a coloured label, its flag
+  and what it waits on. **List** is for planning: the same stories as rows, three levels deep and
+  every repository at once, with a thin heading per repository and epics that open and close with
+  their progress bar and, while a discussion is running, which round it is on. Drag a row to
+  reorder it, or onto another epic to move it there — those are the two things the interface could
+  never do. Dragging never changes state.
+- **The whole of a story, beside the row rather than under it.** Click a row and it opens to the
+  side: the counter-check first, then why it exists, the rounds with their questions and answers,
+  the decisions with the verdict each one got, the plan, the checklist and the log, and a line
+  saying both what it waits for and what is waiting for it. Beside, so the rows you were comparing
+  it against do not scroll away. Click an epic and the epic opens the same way — the rounds it was
+  argued out in and the decisions every story under it is held to, which is the only place that
+  conversation can be watched, because it happens before a single story exists. It follows a
+  discussion while the discussion is happening, an epic's as well as a story's.
+- **The `+` makes an epic as well as a story.** It is a small menu now: **Story** is the dialog you
+  know, with one field added for the epic it belongs to — pick one this repository already has, or
+  type a name and it is made on the spot. **Epic** asks which repository and then opens a terminal
+  running `/k0-epic`, because an epic is what a discussion leaves behind and naming one before that
+  discussion has happened names something nobody has decided the shape of yet.
+- **A `.k0/` folder in each repository.** One file per epic and one per story, rewritten whenever
+  the story changes: the whole backlog in Markdown, readable in a diff and committable. A story's
+  file carries the decisions it inherited from its epic as well as its own, under the names the
+  counter-check uses — so a file that says `K7·D3` was broken also says, further up, what `K7·D3`
+  was. It is also the way back — k0 can rebuild a lost database from those files. Nothing of the
+  backlog is written anywhere else in your repository, and never in your `.gitignore`; the one
+  other thing that writes into a repository at all is the worktree below, and you have to ask
+  for it.
+- **Worktrees, from the board.** `/k0-work` opens a worktree for a session from the branch you
+  are standing on, works there, and brings its branch back as a single merge commit before
+  removing it. Never a push, never a pull request, and never a conflict resolved on your behalf.
+  It also never runs your tests in there, and says why.
+- **A What's New page.** After an update, a discreet dot appears next to `k0` in the top bar and
+  leads to a page that says what changed between the version you had and the one running now —
+  written by your own Claude, in your language, at the level of detail you ask for. It never
+  opens by itself, and the dot goes out when you have read it.
+- **k0 now makes one network request.** Once a day it asks the public npm registry whether there
+  is a newer `k0-board`, so the board can mention it. The package name is in the address and
+  nothing else: nothing about you, your repositories or your commits leaves the machine, nothing
+  is downloaded, and `"updateCheck": false` stops it opening a socket at all.
+- **All of it can be switched off**, from `~/.k0/config.json` — the file the idle timeout already
+  lives in, not the database, because a switch you would need `sqlite3` to reach is not a switch.
+  `"backlog": false` and the board is the board it always was: nothing extra on a note, no
+  next-step button, no Kanban/List switch in the bar, a `+` with no menu behind it, no `.k0/`
+  folder created anywhere, and every command says the backlog is turned off rather than reporting
+  an empty one — "there is nothing here" and "you turned this off" read the same, and only one of
+  them is worth acting on.
+  k0 re-reads the file when it changes, so nothing has to be restarted.
+- **`/k0-ultracode`: a story, or a whole epic, run by a manager with agents under it.** It cuts the
+  plan into assignments, gives each one to an agent working in a copy of the repository of its own,
+  brings the work back one piece at a time, and then — on your branch, never inside a worktree —
+  runs the tests, has the result read by an agent that wrote none of it, and walks the story past
+  every decision before starting the next one. It asks two questions at the start and never asks
+  again: how much rope (*interactive*, *checkpoint* or *autonomous*) and how hard (two, three or
+  five agents at a time, one repair attempt or two). Both answers go into the Log, so a terminal
+  closed halfway through is picked up on the same terms. It never pushes, never presses **Done** —
+  the stories come back in `Review`, counter-checked — and it stops rather than grinding on: the
+  repair attempts are spent, what is still broken is said out loud, and everything that works is
+  already merged. On the board it sits beside *Work* as a second, quieter word, and on an epic it
+  is in the epic's own panel.
+- **A Usage page: what your sessions consumed, a week at a time.** The icon with three bars in the
+  top bar opens it. It shows what each day would have cost at the API price list, stacked by model
+  (with a subscription you do not pay this, and the page says so), and splits the week by model and
+  effort, fast mode included; by the conversation, its subagents and workflow agents; by
+  repository; and by account. Every session is listed, the most expensive first, with its model
+  and effort, how long Claude actually worked on your turns, its tokens, its cost and how many times
+  a limit stopped it. A session that belongs to a story links to it, and the story opens on the
+  board. It costs no tokens and opens no connection: everything is read from the transcripts
+  Claude Code already keeps on your disk, the history a few megabytes at a time so the board never
+  stalls. Two things Claude Code does not keep are handled openly. Which account a reply came from
+  is only known from the moment k0 is running, so anything older says *Unknown account* rather than
+  being guessed. How full the five-hour and weekly limits are is only handed to the statusline, so
+  the manual has a few lines to add to yours; with them, the page draws each account's week and
+  estimates, marked `≈`, how much of it each session used. Tried on a copy of a real board with
+  four gigabytes of transcripts: the whole history was read in under half a minute without ever
+  holding the board up for more than a tenth of a second, and one session counted by hand matched
+  it reply for reply.
+
+### Changed
+
+- **The documents in `out/` are in the file viewer.** A folder of documents keeps what it makes in
+  `out/`, and k0 skipped that directory whole because in a code repository it is generated — so a
+  folder with twenty-one PDFs and a quiz page in it showed none of them, in the listing, in the
+  search by name, or in the files a pasted chat names. `out/`, `dist/` and `build/` are now walked
+  into like anywhere else, and the documents in them are listed like any others: the PDFs, the Word
+  files, and the pages you open with a double click. Only what a build leaves lying about stays
+  out. Where git is in charge git still decides — a directory your `.gitignore` names gives up its
+  finished documents and not its pages, because one real site's ignored `dist/` is four thousand
+  pages and none of them is the file you went looking for.
+
+- **A pasted chat finds a file it names even when the listing has not got it.** Writing
+  `out/report.html` in full used to come to nothing at all — not found, not counted, not even
+  reported as missing, because no file of that kind was in the listing to compare it with. Now the
+  names written out in full that the listing cannot place are checked against the disk, in one
+  question, and the ones that are really there come out in the results like any other file, in the
+  order the text names them.
+
+- **The machine chip says what k0 itself costs.** It measured the sessions and it measured Chrome,
+  and never the thing doing the measuring — which for a server that runs under launchd for weeks is
+  the one thing it should be least able to hide. Hovering it now also gives k0's own weight and CPU,
+  how many times a minute it asks git anything, how many queries it is holding, and how hard the
+  watching loop is currently running.
+
+- **A card is now a story, everywhere.** The word changed on the board, in the commands k0 ships
+  and in what k0 stores. Your board comes back exactly as you left it — same post-its, same
+  colours, same ages, same order — but what a post-it stands for now has room for what the work
+  is about.
+- **A story's state and its session's status are two different things.** Backlog · Discussed ·
+  Planned · Working · Review · Done is where the *work* is; Working · Planning · Planned · Ask ·
+  Idle is what the *session* is doing this second. They used to be one column fighting itself,
+  which is why ticking something off used to lose what the terminal was in the middle of.
+- **A story keeps every session it has had**, rather than only the last one. Starting a new
+  conversation on old work no longer throws away the record of what was tried before.
+- The ChangeLog page and its writer say *story* where they said *card*.
+- **The top bar is one row again.** Two views, a repository filter and seven state pills had pushed
+  it onto a second line: the four mode buttons at the end now stand two by two, and the memory chip
+  puts RAM, CPU and the closing time one under the other instead of writing them across.
+- **Driving mode resizes the terminals, not just their text.** A terminal you glance at from across
+  the room now takes the whole free screen while Driving is lit, and goes back to its usual size and
+  its usual text the moment you leave it — one gesture instead of large text left sitting in a small
+  window. The price, which used to be the other way round: a window you had dragged onto a second
+  screen comes back to the middle of the main one.
+
+- **The age at the bottom of a post-it stopped lying.** Starting a session used to leave the line
+  blank and the tooltip reading "Your turn for "; a story that had been started before inherited
+  the previous session's age and claimed five days the moment you pressed Start; a job you
+  reopened said "4 days" instead of "now"; and a backlog post-it jumped to "now" when something
+  moved it between two states that look identical on the board. All four were one line reading
+  the wrong entry in the story's history.
+- **A board that lost power while it was being brought forward opens again.** The first time this
+  version runs, it moves your board to the shape described above. That used to be one long step
+  with a single test in front of it: a machine that went down in the middle left a board that
+  would never open again, and a second attempt would have given every story a duplicate of every
+  session it had lived through. The move is now done in pieces that each stand on their own, and
+  k0 writes down that it has been done, so it cannot happen twice.
+- **A story moved to another repository is given a key from that repository**, instead of
+  carrying its old number into a repository that already has one.
+- **A story that had somehow been made its own parent can be thrown away again.** The board will
+  not make that shape now, and a board that already had one no longer refuses to delete it.
+- **Notes written under the title of a `.k0/` file stay there.** The folder's own README promises
+  that whatever you add above the first heading is left alone, and it was not: every rewrite ate
+  one more paragraph of it, and the rewrite after that ate the next, until there was nothing left
+  and nothing anywhere saying there ever had been. An epic lost them fastest, because an epic has
+  no post-it line of its own for k0 to have been aiming at.
+
+### Fixed
+
+- **The tests pass on Windows and Linux again**, where three of them depended on line endings, on
+  how Windows spells its temporary folder, and on two settings changes landing in different
+  milliseconds. Nothing about k0 itself changed.
+- **An open board no longer downloads fifty-six gigabytes a day.** It asked the server for
+  everything k0 knows once a second and got all of it — two thirds of a megabyte, six hundred
+  stories carrying their whole "Why" and their whole plan, most of them finished weeks ago and
+  hidden from view, none of which a post-it draws. The board now sends back a stamp of the answer
+  it is holding, and when the answer would be identical the server says so in a couple of hundred
+  bytes and sends nothing else; when something really changed, what goes out is only what the
+  board draws, compressed. The long texts arrive with the story's own panel, which is where they
+  were always read. A board on which nothing is happening also stops asking so often, dropping to
+  one round every four seconds until something moves or you come back to the tab.
+- **Building that answer stopped costing a disk scan and a query per story.** Every request listed
+  your home directory and asked the disk about each entry in it, for a list of repositories that
+  changes about once a week; that reading is now kept for half a minute. And the dependencies were
+  one statement per story per request — six hundred a second with a tab open — which is now one
+  statement for the whole board.
+- **The file viewer asks git every ten seconds instead of every three.** Each round runs two git
+  processes against the repository you are reading, and you are reading it, not watching it.
+
+- **k0 stops costing anything on a machine nobody is using.** The watching loop went round once a
+  second for ever — awake or asleep, looked at or not — and every round asked the database about
+  every story twice over and every repository on the board about its git state. On a real board
+  that was a couple of dozen git processes every five seconds, dead ones piling up faster than they
+  could be buried, and about five per cent of a processor core burnt around the clock, a third of
+  it inside SQLite's parser compiling the same queries again. Now the loop goes round every two
+  seconds while a session is running or you are in front of the board, and once a minute when there
+  is neither, waking at once on anything you press; the queries are compiled once and kept; git is
+  asked at most every half minute, and away from the board only about the repositories a session is
+  actually working in. Nothing you can see on the board changed.
+- **A board left open in a background tab stops asking.** Every tab polled the server once a second
+  whether or not anybody could see it, and because asking is how the server learns somebody is
+  watching, a single forgotten tab kept it walking the whole process table and questioning git
+  indefinitely. Both the board and the file viewer now pause while their tab is hidden, and take a
+  fresh reading the moment you come back — so the first look is never stale. The file viewer's git
+  polling stops with it.
+- **The breath on a working post-it no longer costs a repaint.** The faint pulse was an animated
+  blurred shadow, which a browser cannot compose and has to redraw sixty times a second, for every
+  working post-it, in every open tab. It is now drawn on a layer of its own with only its opacity
+  moving. It looks the same, except that the ring sits just inside the post-it's edge rather than
+  just outside it.
+- **Sessions that end are forgotten.** k0 kept a note of every session it had ever watched, holding
+  the tail of its transcript, and only ever let go of one when a story was deleted or a terminal
+  closed by hand — which is not how most sessions end. On a board that had seen a few hundred, that
+  was most of what the server was holding at rest.
+- **Clipboard images are swept while k0 is running, not only when it starts.** The sweep was called
+  once, at launch, on an app that starts at login and stays up for weeks, so it only ever tidied
+  away the session before. A folder of pasted screenshots had grown to 907 MB. It now runs every ten
+  minutes, and there is a ceiling on the whole folder as well as on the age of what is in it: one
+  screenshot off a large display is ten megabytes, so age alone was never a bound.
+- **A dev server k0 lost track of is not remembered as running.** Rows pointing at processes that
+  died while k0 was not running are cleared on the way up. A pid is a number the operating system
+  hands out again, and a stale row is one that eventually names somebody else's process.
+
+- **Sessions opened by k0 have Claude Code's task list again.** On a newer model such as Opus 5,
+  Claude Code starts without its task tools unless it is told otherwise, so a session asked to keep
+  a task per step was refused every time it tried. Every session k0 starts, new or resumed, now has
+  them, and `/k0-plan`, `/k0-work` and `/k0-verify` keep one task per phase, per step and per
+  decision. A session that was already open gets them by being resumed.
+- **Installing again brings your copies of the commands up to date.** They were copied into
+  `~/.claude/skills/` once and never again, so a command fixed in a later version kept running its
+  old text. Copies that differ from the ones in the package are now replaced, and the installer
+  names them.
+- **Double-clicking a post-it does something on every note, not on half of them.** It brought the
+  terminal to the front on a story that had one running and did nothing at all on any other, so it
+  was a gesture you could not rely on. It now goes where the work is: the terminal if one is
+  running, the conversation the closed terminal left behind, and a fresh session on a story that
+  never had one.
+- **"That window is gone" stopped being said about a session that is still running.** Closing a
+  Terminal window by hand leaves `claude` thinking inside it, and k0 went on holding a window id
+  that no longer answered — so a double click reported the session lost while it was working. k0
+  now looks the window up by the name it put on it, brings that one up and writes the id down; when
+  there is really nothing left to find, it says the window was closed and the session is still
+  running, and offers to open it again.
+- **The buttons on a post-it no longer break a word over two lines.** A label that did not fit the
+  268 pixels of a note was wrapped mid-phrase, which read as two buttons and made that note stand a
+  row taller than the ones beside it.
+- **A note written under a story's title is no longer eaten.** The `.k0/` copy dropped the first
+  paragraph above the first heading every time it rewrote a file, taking it for the standfirst k0
+  prints itself. An epic prints no standfirst, and neither does a story with an empty description
+  — so for those, what was quietly deleted was something a person had written. One paragraph per
+  rewrite, in the folder whose own README promises that what you add under the title is left alone.
+- **A `.k0/` folder no longer appears in a repository that has no backlog.** The sweep wrote the
+  README explaining the folder before asking whether there was anything to put in it, which on a
+  machine with eighteen checkouts meant eighteen folders nobody had asked for. It appears with the
+  first story now, and not before.
+- **git taking too long says so.** A command that ran out of time came back carrying git's own
+  command line instead of a sentence, because the timeout was recognised by a code that only the
+  synchronous calls set. It is the slowest and most confusing failure there is — a commit hook can
+  run for fifteen minutes — and it had the least readable answer.
+- **A story moved to another repository is numbered from one, not from three.** It was given its
+  key in its new home after it had already arrived there, so it counted itself.
+- **Changing mode no longer gives up halfway through, in silence.** k0 asked Terminal after every
+  window id it had ever recorded, one at a time; on a board of two hundred stories nearly all of
+  them named a window closed weeks ago, and the wait for those answers pushed the whole thing past
+  its own time limit. It was cut off mid-way: some terminals changed, the rest kept the size they
+  had, and the failure was read as "Terminal is not running" and never mentioned. k0 now asks once
+  for the windows that are open, which takes about a second whatever the board has been through —
+  and a pass that does fail says so in the log.
+- **Changing a story's title really does rename its session, running or not.** The field says the
+  title is also the session's name, and only the window's title bar kept the promise: a session
+  that was still running kept its old name inside Claude Code, and a session that had worked in a
+  worktree kept it for good, because the new name was written into a transcript that was not
+  there. Now a running session takes the new name the first time you look at it — with its window
+  in front of you and Claude Code sitting idle with nothing under the cursor, k0 types `/rename`
+  into it and presses Enter, and you see the command go by. It never brings the window up to do
+  that, because the keyboard is yours: a terminal jumping up while you type somewhere else took
+  your words with it, which is how the first version of this behaved on the author's Mac and why
+  it does not any more. What lands in the box is read back before Enter, and anything other than
+  the command is deleted rather than sent. A session that has ended gets the name wherever its
+  transcript is, worktree or not. On Linux and Windows the running session still waits for its
+  end, and `k0-board doctor` says so. Also fixed when the title is changed by a skill rather than
+  from the board, which used to rename nothing at all. Checked by hand on macOS on a session in a
+  Terminal window; the rest is covered by tests.
+- **Notes on a post-it keep their lines.** They are written one per line, and the post-it ran them
+  together — `- OMI - Locato` for two notes — so a list did not read like one. Each note now sits
+  on its own line, and the post-it shows three of them before trimming, the same as the prompt.
+
 ## [0.4.0]
 
 The file viewer stops being read-only, and stops being just a pile of documents. It now shows the
@@ -339,7 +761,10 @@ here is everything that had to change for it to be somebody else's tool as well.
 - The personal fixtures k0 grew up on. `test/clean.test.mjs` now fails the build if any of them
   come back.
 
-[Unreleased]: https://github.com/alessio-ragni/k0-board/compare/v0.3.0...HEAD
+[Unreleased]: https://github.com/alessio-ragni/k0-board/compare/v0.6.0...HEAD
+[0.6.0]: https://github.com/alessio-ragni/k0-board/compare/v0.5.0...v0.6.0
+[0.5.0]: https://github.com/alessio-ragni/k0-board/compare/v0.4.0...v0.5.0
+[0.4.0]: https://github.com/alessio-ragni/k0-board/compare/v0.3.0...v0.4.0
 [0.3.0]: https://github.com/alessio-ragni/k0-board/compare/v0.2.0...v0.3.0
 [0.2.0]: https://github.com/alessio-ragni/k0-board/compare/v0.1.2...v0.2.0
 [0.1.2]: https://github.com/alessio-ragni/k0-board/compare/v0.1.1...v0.1.2

package/LICENSE

@@ -1,21 +1,86 @@
-MIT License
+# License
+
+Versions of k0 (the `k0-board` package) up to and including 0.5.0 were released under the MIT
+License and remain available under it. Everything released after 0.5.0 is licensed as follows.
 
 Copyright (c) 2026 Alessio Ragni
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+The licensor is Alessio Ragni. The software is k0, published on npm as `k0-board`, together with
+its source code at https://github.com/alessio-ragni/k0-board. All third party components
+incorporated into the software are licensed under the original license provided by the owner of
+the applicable component. Everything else is available under the Sustainable Use License as
+defined below.
+
+## Sustainable Use License
+
+Version 1.0
+
+### Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+### Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide, non-sublicensable, non-transferable license
+to use, copy, distribute, make available, and prepare derivative works of the software, in each case subject
+to the limitations below.
+
+### Limitations
+
+You may use or modify the software only for your own internal business purposes or for non-commercial or
+personal use. You may distribute the software or provide it to others only if you do so free of charge for
+non-commercial purposes. You may not alter, remove, or obscure any licensing, copyright, or other notices of
+the licensor in the software. Any use of the licensor’s trademarks is subject to applicable law.
+
+### Patents
+
+The licensor grants you a license, under any patent claims the licensor can license, or becomes able to
+license, to make, have made, use, sell, offer for sale, import and have imported the software, in each case
+subject to the limitations and conditions in this license. This license does not cover any patent claims that
+you cause to be infringed by modifications or additions to the software. If you or your company make any
+written claim that the software infringes or contributes to infringement of any patent, your patent license
+for the software granted under these terms ends immediately. If your company makes such a claim, your patent
+license ends immediately for work on behalf of your company.
+
+### Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these
+terms. If you modify the software, you must include in any modified copies of the software a prominent notice
+stating that you have modified the software.
+
+### No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in these terms.
+
+### Termination
+
+If you use the software in violation of these terms, such use is not licensed, and your license will
+automatically terminate. If the licensor provides you with a notice of your violation, and you cease all
+violation of this license no later than 30 days after you receive that notice, your license will be reinstated
+retroactively. However, if you violate these terms after such reinstatement, any additional violation of these
+terms will cause your license to terminate automatically and permanently.
+
+### No Liability
+
+As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will
+not be liable to you for any damages arising out of these terms or the use or nature of the software, under
+any kind of legal claim.
+
+### Definitions
+
+The “licensor” is the entity offering these terms.
+
+The “software” is the software the licensor makes available under these terms, including any portion of it.
+
+“You” refers to the individual or entity agreeing to these terms.
+
+“Your company” is any legal entity, sole proprietorship, or other kind of organization that you work for, plus
+all organizations that have control over, are under the control of, or are under common control with that
+organization. Control means ownership of substantially all the assets of an entity, or the power to direct its
+management and policies by vote, contract, or otherwise. Control can be direct or indirect.
+
+“Your license” is the license granted to you for the software under these terms.
+
+“Use” means anything you do with the software requiring your license.
+
+“Trademark” means trademarks, service marks, and similar rights.