Pacenote v0.5.17

The Overview shows the tasks you handled over the last 14 days, and your settings move from .env into one JSON file, ~/.pacenote/settings.json, with the variable names gone from the app's screens.

brew update && brew upgrade --cask pacenote

The upgrade quits the running app first and reopens it, once. Its first start moves ~/.pacenote/.env into settings.json and keeps the old file as .env.bak.

Tasks you handled

Per day. With Todo on, the Overview counts the tasks you handled on each of the last 14 days, beside how many are still open.
How they ended. In Claude Code or Codex (a session for the task, or closed by one), closed in Slack (a reply, a check mark), or marked done. Dismissed as already done counts; not for you or not worth it does not.
How long they took. The median time from a task's message to when it was handled.

Settings in settings.json

One file, grouped like Settings. slack, answers, sandbox, ops, tasks, history and logs: switches are true or false, numbers are numbers, lists are arrays. The docs' Settings file page maps every setting to its place.
Moved once, by itself. The first start of the app or Pace moves .env into settings.json and keeps the old file as .env.bak, readable by you alone. Comments in .env stay only there.
Environment variables still win. A variable set when Pacenote starts overrides the file, as before. Settings the screens do not show go under env, by their variable name.
A broken file is not overwritten. If the JSON does not parse, Pace does not start and says why, and Settings will not save over it.
Labels, not variables. Settings, Pace's issues and the sandbox's checks name a setting by its label instead of SLACK_BOT_TOKEN and the like.

Going back to 0.5.16 needs .env.bak renamed to .env: older versions do not read settings.json.