v0.21.0

• The agent journal (spec 0030, see "Pulse"): a board declares journal at session-start and journal-summary at session-end. The agent posts notes on the plan it implements — rness pulse note, or rness_note of rness mcp — to the plan's issue in .rness, or to an implementation issue in the repository it works in, a sub-issue of the plan's, which the pull request closes. The session's end posts a summary: its commits, its pull request, its duration. The preset agent-pulse declares neither: nothing changes until a board does.
• Boards are declared in rness.json (spec 0031, see "Pulse"): each one's collections, statuses, colours, fields, labels and views, written whole. Agent Pulse is the preset agent-pulse, no longer a special case of the code. pulse create writes the board it makes; rness sync (which rness upgrade runs) writes a board declared by its number whole, moves a collection's README declarations into its board, and merges a newer revision of a preset value by value. Views are updated in place where GitHub allows; a view rness made and no longer declared is deleted, the team's are said once. Nothing changes on GitHub for a board 0.20 made. For the package's API: Projects is Record<string, number | BoardDeclaration>; BoardDeclaration and parseBoard are exported.
• A board's readme and updates stay within .rness/: a path out of it, or a link leading out, is refused before anything is read.
• What a session does to a board is declared in its hooks (spec 0032): mark-in-progress, mark and clear-marks, from a fixed catalogue; a hook never runs a command rness.json names. The preset agent-pulse declares today's three, so nothing changes on GitHub. The hooks start rness pulse run <event>; rness pulse mark stays, hidden, through 0.21.x, for sessions started before an upgrade.
• upgrade run by a workspace's pinned copy installed with pnpm no longer ends on mod directory not found next to the @rness/cli package. After its commit it lists the files to commit in the clones, and that list read the plugin's mod from the folder of the copy running it, which the install had just removed. The list now takes the paths alone. The upgrade itself was complete: 0.20.0 to 0.20.1 printed the error after its commit. An upgrade from 0.20.1 still prints it, since the copy that runs it is the old one; pnpm dlx @rness/cli upgrade runs the new one.

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

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