v0.22.0

• One word for the view, whatever the provider (spec 0033, see "Boards"): rness board push replaces rness pulse sync, rness note replaces rness pulse note, and the hooks start rness board run. rness.json names its boards boards; projects and the older pulse still read, and rness sync (which rness upgrade runs) renames the key. pulse stays the name of the board rness ships, Agent Pulse.
• A board comes to exist by its declaration and a push: there is no create. A board of boards without a number, or a preset by name ("pulse": "agent-pulse", "marketing": "collection"), is created by rness board push once asked (-y off a terminal), its number then written into rness.json.
• rness pulse … still runs, hidden, as its new command, and says so on stderr; it goes in a later minor. rness pulse mark, kept through 0.21.x for 0.20's hooks, now exits 0 and does nothing. Spec 0031's eject is not built and will not be: every board is written whole.
• The session-start notice is rness: board not updated — …, its record board.json (one 0.21 left in pulse.json is said once), and messages name boards: boards need a GitHub login: run rness login.
• Upgrade with npx @rness/cli@latest upgrade, which runs the new copy throughout: a 0.21 copy cannot read boards (unknown key "boards").
• For the package's API: Manifest.projects is Manifest.boards (Boards, a record of BoardEntry: a number, a preset's name, or a BoardDeclaration, whose number is null until the board is created).

Full changelog: https://github.com/rness-dev/rness/blob/main/packages/cli/README.md

npm create rness           # a new workspace
pnpm rness upgrade 0.22.0  # an existing one, from .rness/