Codealong 0.12.0

Codealong now runs in the background, so quitting the app leaves the sessions it runs and your schedules going, and the main window comes back where you left it.

What's new

• Codealong keeps going when you quit the app. The engine now runs as a server of its own, which carries the sessions Codealong starts itself and their side conversations, your schedules, automatic reviews and linked devices. Quitting the app leaves them running, and the codealong command works with the app closed, starting the server when nothing answers (codealong server start and codealong server stop look after it). An update that changes only the windows keeps those sessions going through the restart.
• The main window comes back where you left it. It opens at the place and size you left it, however Codealong ended, a restart for an update included, and no longer shows somewhere else first.
• Edit a schedule in place. codealong schedule edit <schedule> changes a schedule with the options schedule add takes, only what you give it, so it keeps its id, its runs and its notes.

Fixes

• A schedule moved to another time starts afresh. Changing when a schedule runs, or what a watch looks at, from the command or the Schedules view's Edit, no longer runs a late run at the old pace or takes what was already there for new.
• Usage stays up when Claude's usage endpoint turns a read away. The last numbers are kept and shown dimmed for up to an hour after a relaunch, rather than nothing; with nothing kept, the chip says Rate limited.
• Run on more commands. A block with no language that runs a script from a folder (scripts/deploy.sh check) or a program in a bin folder now offers Run beside Copy.