@rness/cli 0.13.0 → 0.15.0

package/README.md

@@ -60,11 +60,15 @@ when dropped, red `?` when missing.
   screen back. Read-only.
 - Off a terminal — a pipe, CI, an agent's tool — Markdown: a table per tab.
 - From Claude Code, `/rness:status [tab]` shows those tables (see "Agent
-  targets"). For the view itself: `Ctrl+Z` suspends Claude Code, run
-  `npx @rness/cli status` (or `rness status` with a global install), `q`,
-  then `fg` resumes it — the skill ends with that line. Nothing started from inside
-  Claude Code gets the terminal, so the view cannot open from there
-  (verified with Claude Code 2.1.284 on 2026-09-29).
+  targets"). Nothing started from inside Claude Code gets the terminal, so
+  the view cannot open from there (verified with Claude Code 2.1.284 on
+  2026-09-29). Two ways to reach it, and the skill ends with both: in the
+  same terminal, `Ctrl+Z` suspends Claude Code, run `npx @rness/cli status`
+  (or `rness status` with a global install), `q`, then `fg` resumes it
+  (Unix only); or in another terminal, from the workspace's `.rness/`, with
+  the manager it installs with — `pnpm rness status`, `npx rness status`,
+  `yarn rness status` or `bunx rness status` — which runs the pinned copy
+  without the network (verified with each manager on 2026-09-30).
 
 ### Agent targets
 
@@ -91,11 +95,33 @@ the files a given agent needs, for the agents the team declares in
   which registers the MCP server; see "MCP server". The same settings file
   carries three hooks, and so does `.claude/settings.json` at the workspace
   root, which `sync` writes on every machine; see "Hooks". Both places also
-  get a Claude Code plugin, `.claude/skills/rness/`, with one command:
-  `/rness:status [tab]`, the tables of `rness status`. rness owns those
-  files whole — an edit by hand is reported by `sync --check` and written
-  back by `sync` — and nothing in them depends on the version. Claude Code
-  loads the plugin once the folder is trusted, in a session started there.
+  get a Claude Code plugin, `.claude/skills/rness/`, with five commands:
+  `/rness:status [tab]`, the tables of `rness status`, and the lifecycle
+  skills below. rness owns those files whole — an edit by hand is reported
+  by `sync --check` and written back by `sync`. Nothing in them depends on
+  the version; the last line of the status skill names the workspace's
+  package manager, so changing `packageManager` in `.rness/package.json`
+  leaves it stale until the next `sync`. Claude Code loads the plugin once
+  the folder is trusted, in a session started there.
+- **The lifecycle skills**: `/rness:adr [subject | NNNN]` records a decision
+  as an ADR, `/rness:spec [subject | NNNN]` writes a specification,
+  `/rness:plan <spec>` turns an approved specification into a plan, and
+  `/rness:done [plan]` closes a piece of work — each task checked on
+  evidence, then the plan `Completed`, its specification `Implemented`, and
+  the documents the work made inaccurate corrected. Each is a procedure
+  loaded into the conversation, not a file generator: after a decision has
+  been discussed, `/rness:adr` writes it from the conversation; otherwise
+  it asks, one question at a time. The skill stays in the conversation for
+  the next turns, and the file carries the work to the next session
+  (`/rness:adr 0010` reopens it). The agent may start one itself — an ADR
+  when a choice is expensive to reverse — but writes nothing without a yes.
+  The rules stay in `.rness/CONVENTIONS.md`; the skills only add the steps.
+  A new document takes the collection's first status (`Proposed` for an
+  ADR, `Draft` otherwise) and the next number of the local checkout; two
+  branches can pick the same one. Each skill records its session: it adds
+  the Claude Code session id to `sessions:` in the front matter of what it
+  writes or closes — an edit made without a skill leaves none. No skill
+  commits.
 - rness owns values, not files: what is missing is added, nothing else is
   touched, and a file it cannot parse is reported, never rewritten.
   `sync --check` and `validate` report a missing value. Removing an agent
@@ -209,7 +235,11 @@ in its Settings`.
   `.rness/`, in lifecycle order, at most 50), `Collection` (one option per tab of
   `rness status`; not `Type`, which is GitHub's own issue-type field and
   filter), `Agent` (`working`), `Session` (`claude · 1a2b3c4d`, plus the
-  agent type for a subagent) and `Path`. A board per directory, named as
+  agent type for a subagent), `Path` and `Sessions` — the document's
+  `sessions:` (see "Agent targets"), joined by `, `, written by sync and
+  never cleared: which sessions wrote a specification or implemented a plan,
+  after they ended (`claude --resume <id>` reopens one on the machine it ran
+  on). A board made before 0.15.0 gains `Sessions` at its next sync. A board per directory, named as
   `rness status` names its tab, filtered on its `Collection`, its columns
   that collection's own steps: each collection has its own status field
   (`ADR status`, `Specs status`, …; a directory without statuses is columned
@@ -264,7 +294,9 @@ added to project`) may change a field of rness's items; the next sync
 - **Hooks**, with `claude` in `agents` and a pulse declared: session start
   marks the `In progress` plans of the session's scope `Agent: working`, with
   the session; an edit of a document of `.rness/` marks it — one the agent has just written, with no item yet, gets its issue first
-  through a sync, and an edit of any other file of `.rness/` costs no sync;
+  through a sync, and so does one whose status the edit changed, so its
+  card moves within seconds rather than at the session's end; an edit that
+  leaves the status alone, or of any other file of `.rness/`, costs no sync;
   the hooks' syncs run one at a time, an edit's skipped while another runs,
   the session end's waiting its turn; session end clears
   the marks of that session (its subagents' included) and syncs. Each one
@@ -279,7 +311,7 @@ added to project`) may change a field of rness's items; the next sync
   `cannot reach GitHub: …`. Two sessions marking one plan both write; the
   last wins.
 - **Rate**: rness sends one request at a time. A new document costs an
-  issue, its addition to the board, up to four fields, then its body. An
+  issue, its addition to the board, up to five fields, then its body. An
   unchanged document costs nothing but its share of the listing, which
   reads every item's body. On one of GitHub's rate limits rness waits as
   long as GitHub says (`waiting  60 s — GitHub's rate limit`), 10 minutes
@@ -313,7 +345,7 @@ repository, the board).
   `contract`, `provider`, `org`, `agents`, `pulse`, `repos`, `scopes`.
 - A provider _written_ in `rness.json` that this version cannot talk to
   (`gitlab`) is refused by `validate`, `create`, `login` and `pulse`:
-  `provider "gitlab" is not supported by @rness/cli 0.13.0 (supported:
+  `provider "gitlab" is not supported by @rness/cli 0.15.0 (supported:
 github)`. `add`, `sync` and the local commands never refuse. `null` is not a
   value: an absent key means none.
 
@@ -490,6 +522,36 @@ per repository, the files to commit there.
 Exit codes: 0 success, 1 failure, 2 usage — or a refusal without a TTY.
 `RNESS_DEBUG=1` adds stack traces; `RNESS_NO_DELEGATE=1` skips the delegation.
 
+## 0.15.0 — Agent Pulse follows a status change; the sessions are kept
+
+- An edit that changes a document's status syncs Agent Pulse at once: its
+  card moves within seconds, not at the session's end. An edit that leaves
+  the status alone still costs nothing. See "Pulse".
+- `sessions:` in a document's front matter lists the Claude Code sessions
+  that wrote or changed it. The lifecycle skills add theirs; the board
+  shows them in a new field, `Sessions`, which a session's end never
+  clears. A board gains the field at its first sync with 0.15.0. See
+  "Pulse" and "Agent targets".
+- `rness upgrade` rewrites the four lifecycle skills; commit
+  `.claude/skills/rness/` in each repository.
+- Blocks are unchanged.
+
+## 0.14.0 — the lifecycle skills; `/rness:status` names a second terminal
+
+- The `rness` plugin of Claude Code gains `/rness:adr`, `/rness:spec`,
+  `/rness:plan` and `/rness:done`: the workspace's lifecycle as procedures
+  the developer or the agent starts, which write nothing without a yes. See
+  "Agent targets".
+- `/rness:status` ends with two ways to the full-screen view: `Ctrl+Z` in
+  the same terminal, or another terminal from `.rness/` —
+  `pnpm rness status`, or the command of the workspace's package manager.
+  See "Status".
+- `rness upgrade` syncs, so it writes the four skills and rewrites
+  `plugin.json` and the status skill; then commit `.claude/skills/rness/` in
+  each repository, as its next steps list. Until then `sync --check` and
+  `validate` report them.
+- Blocks are unchanged.
+
 ## 0.13.0 — Agent Pulse: each document an issue of `.rness`, its content on the card
 
 - Each item of Agent Pulse is an issue of `<org>/.rness`, labelled

package/dist/bin/rness.js

@@ -6,7 +6,7 @@ import {
   findDelegate,
   reportError,
   run
-} from "../chunk-4VTYSPZW.js";
+} from "../chunk-HGT7BIWK.js";
 
 // src/bin/rness.ts
 import { pathToFileURL } from "url";