@rness/cli 0.15.1 → 0.17.0

package/README.md

@@ -29,7 +29,7 @@ Inside a workspace, every `rness` delegates to the copy pinned in
     rness logout
     rness context [--scope <name>] [--json]
     rness status [<tab>]
-    rness pulse create [-y]
+    rness pulse create [<collection>] [-y]
     rness pulse sync
     rness validate
     rness mcp
@@ -119,9 +119,10 @@ the files a given agent needs, for the agents the team declares in
   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.
+  `{ id: <session id>, agent: <model> }` to `sessions:` in the front matter
+  of what it writes or closes. The agent is the model it runs as, as Claude
+  Code names it (`Claude Opus 5.5`): no variable gives it to a skill. 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
@@ -170,8 +171,9 @@ status, it received the problem. The `sh` line is not verified on Windows.
 
 ### Pulse
 
-    rness pulse create      # once per organization: the board, then a first sync
-    rness pulse sync        # as often as wanted
+    rness pulse create            # once per organization: the board, then a first sync
+    rness pulse create marketing  # a collection's own project (0.17.0)
+    rness pulse sync              # every declared project, as often as wanted
 
 A projection of rness's state on the organization's GitHub Projects: a
 project named **Agent Pulse**, where the team sees — and reads — every
@@ -234,17 +236,22 @@ in its Settings`.
   collection fields' options: every contract status plus the ones found in
   `.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), `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
+  filter), `Agent` (`working`), `Working session` (`claude · 1a2b3c4d`,
+  plus the agent type for a subagent: the session working on the document
+  now, cleared when it ends), `Path`, and `Session history` — the
+  document's `sessions:` (see "Agent targets"), each `Claude Opus 5.5 ·
+<id>` (the id alone for an entry without its agent), 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
+  `Session history` at its next sync; one from 0.15 has its `Session` and
+  `Sessions` renamed in place, values and views kept (`renamed field
+Session → Working session`). 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
   by `Status`, which holds them all for the `All` table). `pulse sync`
-  remakes a board built by an earlier version (its URL changes once); a `Working` table, filtered on `Agent: working`. A first view named `View 1` (GitHub's default) becomes `All` when no `All` exists, on create and on sync, showing Title, Collection, Status and Session. Options are coloured (statuses by lifecycle: blue proposed, purple approved, yellow in progress, red blocked or rejected, yellow superseded, green done, gray abandoned; collections and `working` too); a sync recolours rness's options and leaves other options' colours alone. rness does
+  remakes a board built by an earlier version (its URL changes once); a `Working` table, filtered on `Agent: working`. A first view named `View 1` (GitHub's default) becomes `All` when no `All` exists, on create and on sync, showing Title, Collection, Status and Working session. Options are coloured (statuses by lifecycle: blue proposed, purple approved, yellow in progress, red blocked or rejected, yellow superseded, green done, gray abandoned; collections and `working` too); a sync recolours rness's options and leaves other options' colours alone. rness does
   not set the project's visibility: the project gets GitHub's default for a
   new organization project, which is private (`public: false`). Verified
   with Claude Code 2.1.284 on 2026-09-29.
@@ -262,7 +269,7 @@ in its Settings`.
   repositories.
 - **`pulse create`** needs an `org` in `rness.json` (a blank workspace is
   refused) and no pulse yet. It creates the project and at once writes
-  `"pulse": { "project": <number> }` (and the `provider`) into `rness.json`,
+  `"projects": { "pulse": <number> }` (and the `provider`) into `rness.json`,
   then adds the fields, options and views, and runs a first sync; its
   `created` lines say what it added. If a step after the project fails, it
   exits 1 with the pulse declared, and `rness pulse sync` completes the
@@ -291,6 +298,33 @@ unchanged`.
   as the team's item. A workflow someone turns on (`Item closed`, `Item
 added to project`) may change a field of rness's items; the next sync
   writes it back.
+- **A collection's own project** (0.17.0): `rness pulse create <collection>`
+  gives a directory of `.rness/` whose documents carry a status — a tab of
+  `rness status` — a project of its own, named after it, declared as
+  `"projects": { "pulse": 4, "marketing": 5 }`. Agent Pulse keeps every
+  other collection and the `Working` table; the collection's items leave
+  it (`deleteProjectV2Item`, their issues untouched) once its project
+  holds them. `pulse sync` syncs the collections' projects, then Agent
+  Pulse. The project is written from the collection's files, one way:
+  - `<collection>/README.md` is its README; its front matter may give
+    `description:` (the short description), `statuses:` (the columns, in
+    order, each there even when empty), `fields:` (each a name, a `type` —
+    `text`, `date`, `select`, `number` — and `from`, the front-matter key
+    of the documents that fills it, or a list of keys, the first present
+    one winning; a `select` may give `options:`) and `labels:` (`directory`,
+    the subdirectory a document sits in, or a front-matter key). A date
+    field adds a `Calendar` roadmap; which date it draws is set once in the
+    view's settings: GitHub's API does not set it.
+  - `<collection>/updates/<date>.md` are its status updates: `health`
+    (`on-track`, `at-risk`, `off-track`, `complete` or `inactive`),
+    optionally `start_date` and `target_date`, the text below. Each is posted once, in
+    the order of the names, and updated when its file changes; a deleted
+    file leaves its update.
+
+  rness adds no field or label of its own to a collection's project, and
+  none of this reaches Agent Pulse: a workspace that declares no collection
+  keeps its board as 0.16 made it.
+
 - **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
@@ -349,10 +383,12 @@ repository, the board).
   GitLab host reads as `gitlab`, any other host — or no repository — as
   `github`. Nothing to change: `pulse create` writes it, and refuses a
   detected provider this version cannot talk to. The order of keys is
-  `contract`, `provider`, `org`, `agents`, `pulse`, `repos`, `scopes`.
+  `contract`, `provider`, `org`, `agents`, `projects`, `repos`, `scopes`.
+  The former `"pulse": { "project": <number> }` still reads, as
+  `"projects": { "pulse": <number> }`; both at once are refused.
 - 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.15.1 (supported:
+  `provider "gitlab" is not supported by @rness/cli 0.17.0 (supported:
 github)`. `add`, `sync` and the local commands never refuse. `null` is not a
   value: an absent key means none.
 
@@ -529,6 +565,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.17.0 — a collection on its own GitHub Project
+
+- `rness pulse create <collection>` gives a collection of `.rness/` a
+  project of its own; `rness pulse sync` syncs every declared project. The
+  collection's `README.md` gives the project its README, short
+  description, columns, fields and labels, and `updates/` its status
+  updates. See "Pulse".
+- `rness.json` names the projects in `"projects": { "pulse": 4 }`; the
+  former `"pulse": { "project": 4 }` still reads, and is written in the new
+  form whenever rness writes the file. A CLI older than 0.17.0 refuses
+  `projects`: move the pin first (`rness upgrade`).
+- For the package's API: `Manifest.pulse` is now `Manifest.projects`.
+- A workspace that declares no collection's project sees no change on
+  Agent Pulse. Blocks are unchanged.
+
+## 0.16.0 — Working session and Session history; the agent in the history
+
+- Agent Pulse's session fields are renamed so that the names say what
+  they hold: `Session` becomes `Working session` (the session working on
+  a document now) and `Sessions` becomes `Session history` (every session
+  that changed it). The first `pulse sync` with 0.16.0 renames them in
+  place: values, ids and views stay. Until then, marks use whichever name
+  the board has. See "Pulse".
+- `Session history` names each session's agent: `Claude Opus 5.5 ·
+1e9cb41b-…`. The lifecycle skills now record `{ id, agent }` in
+  `sessions:`; a bare id, as 0.15 wrote it, still reads, and shows alone.
+  `rness upgrade` rewrites the four skills: commit `.claude/skills/rness/`
+  in each repository. See "Agent targets".
+- Blocks are unchanged.
+
 ## 0.15.1 — upgrade names every file to commit
 
 - `rness upgrade`'s next steps name every file the new version's sync

package/dist/bin/rness.js

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