TaskWindow v0.2.8

Extension and daemon. Coming from 0.2.7: taskwindow update for the daemon;
the extension now comes from the Chrome Web Store (see below).

Changed

One click in Chrome: the extension is on the Web Store. Setup used to
end with Developer mode, Load unpacked and a folder picker, because Chrome
demands those for an unpacked extension. taskwindow install now opens the
store listing
instead, and "Add to Chrome" is the whole Chrome side. Chrome then keeps the
extension current on its own, so taskwindow update only updates the daemon,
and an extension a version behind the daemon is reported as Chrome's to catch
up on rather than as something to run. Already loaded unpacked? Remove that
copy in chrome://extensions before adding the store one; taskwindow doctor
says which kind is connected. --extension <zip> keeps the unpacked route for
development.

Pairing happens without a code. A store install has no folder for the
installer to leave a setup code in, so the extension pairs by identity
instead: Chrome stamps its fixed extension id on every request as the origin,
which no other extension or web page can forge, and the daemon returns its
token to that origin alone. Unpacked builds keep the one-time code; manual
pairing with taskwindow pair is unchanged.

Added

Setup recovers from a Web Store build that cannot pair itself. Chrome
serves whatever version last passed review, which can trail a release by
weeks, and a build older than self-pairing leaves taskwindow install
waiting out its five minutes for a connection that was never coming. After a
quiet minute the installer now prints a pairing code and where to paste it,
then keeps waiting — so the recovery is ten seconds instead of a dead wait
and a puzzled taskwindow doctor. Nothing is printed when the extension
pairs on its own, and never on the unpacked path, where a second code would
invalidate the one the installer just wrote.

The extension explains itself on first install, when there is something
to explain. Right after "Add to Chrome" the extension checks for the daemon.
Found one — the installer is driving and pairing is silent — it opens
nothing. Found none, the user came from the store listing first, so a setup
guide opens with the two commands to run; it turns green by itself once the
daemon is up, and Settings links to it for later.

Install

Run npm install -g taskwindow@latest, then taskwindow install. The guided installer configures the daemon and selected coding agents and opens the Chrome Web Store listing; the extension pairs on its own after "Add to Chrome" and Chrome keeps it updated.

Manual archives are attached below (the extension zip is for taskwindow install --extension <zip>, the unpacked development route). Run taskwindow doctor for connection diagnostics or taskwindow pair for manual recovery.

See the README for the full guide.