@rness/cli 0.20.0 → 0.21.0

package/README.md

@@ -31,6 +31,7 @@ Inside a workspace, every `rness` delegates to the copy pinned in
     rness status [<tab>] [--json]
     rness pulse create [<collection>] [-y]
     rness pulse sync
+    rness pulse note [--plan <path>] [--kind approach|deviation|blocker|done] [<text>]
     rness validate
     rness mcp
 
@@ -65,7 +66,7 @@ when dropped, red `?` when missing.
   `yellow` for `In progress`; `red` without a status) and its item there
   (`link`, the board filtered on its path; null without a pulse) — the
   board (`pulse`), and what a Claude Code session shows of the workspace,
-  worded by the CLI — the session-start banner, the status line entry, the
+  worded by the CLI — the session-start banner, the footer's label, the
   scope's plans `In progress` and the notes of the safety net (see
   "Hooks"). The plugin's mod reads it (see
   "The mod").
@@ -176,9 +177,11 @@ the pinned copy, and computes nothing itself:
   installed copy does not match, problems `validate` would report): those
   notes. The banner is not repeated there; the session-start line says it
   once, in the transcript.
-- **The status line**: `<scope> · <n> in progress`, with `⚠ <n>` when
-  there are notes. Claude Code draws it after the plugin's name:
-  `⚠ rness: web · 1 in progress` (2.1.289).
+- **A label in the prompt footer**, among the session modes (`focus`,
+  `memory paused`), dim: `rness · <scope> · <n> in progress`, with `⚠ <n>`
+  when there are notes. Not the pinned status line a plugin can set:
+  Claude Code draws every pinned line after a `⚠` in its warning colour
+  (2.1.291), the wrong sign for a line that informs.
 - **`/rness:status [tab]` as a pane** beside the conversation, a tab per
   collection, a row per document, its status in the colour Agent Pulse
   gives it (yellow in progress, green done, red blocked, gray draft or
@@ -205,13 +208,15 @@ It reads the snapshot again at session start, after an `Edit` or `Write`
 of a file under `.rness/`, and at the end of each turn, off the turn's
 path. The module runs the pinned copy at the one path `sync` writes into it
 for its place (`.rness` at the root, `../../.rness` in a clone), as the
-settings hooks do: never a copy a clone's own tree could hold. It loads
+settings hooks do: never a copy a clone's own tree could hold. Like them,
+it never installs: a pin that drifts from the installed copy is a note in
+the band, and `npm install` in `.rness` is the developer's. It loads
 where the plugin loads — a trusted folder, `claude -p` included — on a
 Claude Code that has mods: run by 2.1.280 and later, ignored without an
 error by 2.1.240 and 2.1.199, where the skills work as before (verified on
 2026-10-04). An older Claude Code is told so once per version and machine,
 in the session-start line: `rness: Claude Code 2.1.240 shows no rness band,
-status line or pane; 2.1.280 or later does — claude update`. The version
+footer label or pane; 2.1.280 or later does — claude update`. The version
 comes from `AI_AGENT`, which Claude Code sets (2.1.240 does); one that does
 not set it, or not in that form, is told nothing. The versions told are kept
 in `claude-code.json` beside the login (`~/.config/rness/` by default). Not in
@@ -240,7 +245,9 @@ workspace root's carry four Claude Code hooks, all run by the pinned copy:
   repository or nothing installed there, a `rness.json` rness refuses, a pin
   the installed copy does not match, the problems `rness validate` reports.
   A Claude Code too old for the plugin's mod gets one more line, once (see
-  "The mod"). After a compaction, the context only.
+  "The mod"). When a board keeps a journal and the scope has a plan in
+  progress, the model gets one more line: how and when to post a note (see
+  "Pulse"). After a compaction, the context only.
 - **Before an edit** (`PreToolUse` on `Edit|Write`): refused, with the
   reason for the model, when it would change what `sync` generates — a
   line of the block of an `AGENTS.md` or `CLAUDE.md` (the reason names the
@@ -254,10 +261,13 @@ workspace root's carry four Claude Code hooks, all run by the pinned copy:
 - **After an edit** (`PostToolUse` on `Edit|Write`): when the file is under
   `.rness/`, its front-matter problems — or those of `rness.json` — go back
   to the model, which fixes them in the same turn. Any other edit costs one
-  path check. Stale blocks are left to `sync`. With a pulse declared, the
-  edit is then marked on the board, broken or not; see "Pulse".
-- **At session end** (`SessionEnd`): with a pulse declared, clears the marks
-  this session set and syncs the board; see "Pulse". Without one, nothing.
+  path check. Stale blocks are left to `sync`. When a board declares
+  `mark` and holds the document, the edit is then marked on it, broken or
+  not; see "Pulse".
+- **At session end** (`SessionEnd`): when a board declares `clear-marks`,
+  clears the marks this session set and syncs; when one declares
+  `journal-summary`, posts the session's summary; see "Pulse". Without
+  either, nothing.
 
 Each hook is one fixed `sh` line: it runs
 `<.rness>/node_modules/@rness/cli/dist/bin/rness.js hook <event>` when that
@@ -269,7 +279,8 @@ own hooks stay where they are.
 
 Claude Code runs hooks from a committed settings file without asking each
 developer, including in `claude -p`. These four read `.rness/`, write
-nothing in the workspace and run no install. Only with a pulse declared do
+no file of the workspace and run no install; with a journal, the session
+start records the clone's `HEAD` in its git directory. Only with a pulse declared do
 they reach the network, through a detached `rness` process that uses your
 login; when that process fails, it writes why to `pulse.json` in rness's
 configuration directory (`~/.config/rness/` by default), which the next
@@ -284,10 +295,70 @@ status, it received the problem. The `sh` line is not verified on Windows.
     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
-document of `.rness/`, and sees when an agent is at work on one. rness
-writes the board; if it is not in rness, it does not belong there.
+A projection of rness's state on the organization's GitHub Projects,
+each declared in `rness.json`: first **Agent Pulse**, where the team sees —
+and reads — every document of `.rness/`, and sees when an agent is at work
+on one. rness writes the boards; if it is not in rness, it does not belong
+there.
+
+- **Boards declared in `rness.json`** (0.21.0): `projects` maps a name to
+  a board, written whole — its `number`, `collections`, `colors`,
+  `fields`, `labels`, `views`, and optionally `title`, `description`,
+  `readme` and `updates` (files of `.rness/`). What `rness.json` says is
+  the board; what it does not declare, the board does not have, but the
+  engine's own: one issue of `.rness` per document, found by its `Path`,
+  its `Status`, the label `rness`. Nothing knows Agent Pulse by name: it
+  is a board like any other, made from the preset `agent-pulse`, and the
+  example a team copies for another.
+  - `collections`: `"all"` (ADR, specs and plans with the contract's
+    statuses, then every other directory `rness status` finds, but those
+    another board holds), or directories, each with `statuses` —
+    `"contract"`, `"found"` or a list in order — a `label` and an optional
+    `field`, a select of its statuses alone.
+  - `fields`: each a `type` (`text`, `date`, `select`, `number`) and a
+    `from`: a front-matter key, or what rness knows — `$collection`,
+    `$status`, `$agent` (`working` while a session marks the card),
+    `$session`, `$sessions`, `$id` — or a list, the first present winning.
+    `Path`, `Status` and GitHub's own fields cannot be declared.
+  - `views`: each a `name` and a `layout` (`board`, `table`, `roadmap`),
+    optionally `collection` and `filter`; a board's `columns`, a table's
+    `fields`, a roadmap's `date`.
+  - `colors`: option → `gray`, `blue`, `green`, `yellow`, `orange`, `red`,
+    `pink` or `purple`; an option not named takes its kind's colour (a
+    status its tone, a collection pink). A colour changed is set at the
+    next sync, every card keeping its value.
+  - A board that `rness.json` declares wrongly is refused alone, by its
+    full key (`"projects.marketing.views[2].date" must name a date
+field`); the others sync. `validate` reports it, and also a collection
+    that is no directory of `.rness/`, one on two boards, a `readme` or
+    `updates` not there, a README that still declares (below). `readme`
+    and `updates` are paths within `.rness/`: a path out of it, or a file
+    that is a link leading out, is refused before anything is read.
+  - A view declared and missing is made; one whose filter or fields differ
+    is updated in place, keeping its id, sort and widths (GitHub returns a
+    filter as given and the fields in the project's order, read on
+    2026-10-06); one whose layout or columns differ is made again. A view
+    rness made and no longer declared is deleted; one the team made is
+    left, and said once per clone (`note view Roadmap is not declared:
+delete it on GitHub if unwanted`), as is a field no longer declared and
+    views out of the declared order (GitHub reorders none). A roadmap's
+    date is chosen in its settings: GitHub's API does not set it.
+  - **Presets and their revisions.** `pulse create` writes a board from a
+    preset, `agent-pulse` or `collection`, recording it (`"preset":
+"agent-pulse/1"`). When a later rness ships a newer revision, `rness
+sync` merges it into the board value by value: a value the team never
+    changed takes the new one, one it changed is kept, and said when the
+    revision changed it too (`kept projects.pulse.colors.Draft: kept orange,
+agent-pulse/2 gives blue`). Removing `preset` takes a board off the
+    merge. An upgrade commits the result, for the team to read before
+    pushing.
+  - **From 0.20 and before.** A board declared by its number
+    (`"pulse": 4`) is read as its preset, and `rness sync` — which `rness
+upgrade` runs — writes it whole; nothing changes on GitHub. A
+    collection's `README.md` that declared `description`, `statuses`,
+    `fields` or `labels` has them moved into its board and out of its front
+    matter (a value declared otherwise in both is refused, naming both).
+    Until then, `pulse sync` skips a board whose README still declares.
 
 - **Items**: one per document of `rness status`, an issue of
   `<org>/.rness` added to the project. GitHub shows it only to people who
@@ -377,8 +448,9 @@ Session → Working session`). A board per directory, named as
   that restricts OAuth apps must approve "Rness", as for its private
   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
-  `"projects": { "pulse": <number> }` (and the `provider`) into `rness.json`,
+  refused) and no pulse yet. It creates the project and at once writes the
+  board whole, from the preset `agent-pulse`, into `projects.pulse` (and
+  the `provider`) in `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
@@ -409,13 +481,17 @@ 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
+  `rness status` — a project of its own, named after it, written whole
+  from the preset `collection` into `projects.<collection>` (0.21.0;
+  before, `"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
+  - `<collection>/README.md` is its README (`readme` in its board since
+    0.21.0, where `description`, `statuses`, `fields` and `labels` are
+    declared too: what follows is how a README declared them before,
+    which `rness sync` moves); 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
@@ -434,9 +510,25 @@ added to project`) may change a field of rness's items; the next sync
   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
+- **Hooks**, with `claude` in `agents`: what a session does to a board is
+  declared in its `hooks` (spec 0032, 0.21.0), each event — `session-start`,
+  `edit`, `session-end` — listing actions from a fixed catalogue:
+  `mark-in-progress` (the documents of the session's scope in the given
+  `collections` and `statuses`, `plans` and `In progress` by default),
+  `mark` (the document edited, on a board that holds it) and `clear-marks`
+  (the session's marks, then a sync). Marks are written through the
+  board's select from `$agent` and its text from `$session`, whatever their
+  names. A hook never runs a command `rness.json` names: the file is the
+  organization's and the hooks run on every developer's machine. The
+  preset `agent-pulse` declares all three, which is 0.20's behaviour;
+  removing `hooks` from a board turns its marking off, and a board without
+  them is only what `pulse sync` makes of the documents. For each event,
+  one detached `rness pulse run <event>` does every board's actions, in
+  the order of `projects`; a failure is recorded naming the board and the
+  action (`mark on Marketing failed: …`). `rness pulse mark`, which 0.20's
+  hooks started, stays, hidden, through 0.21.x. With Agent Pulse's preset:
+  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 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;
@@ -453,6 +545,40 @@ added to project`) may change a field of rness's items; the next sync
   `the pulse needs the project scope: run rness login` or
   `cannot reach GitHub: …`. Two sessions marking one plan both write; the
   last wins.
+- **Agent journal** (spec 0030, 0.21.0): how a plan was implemented, in
+  the agent's words. A board that holds `plans` declares
+  `{ "action": "journal", "to": "plan" | "repo", "limit": 5 }` at
+  `session-start`, and `journal-summary` at `session-end`. With a plan
+  `In progress` in the session's scope, the session start tells the model
+  to post a note — `rness pulse note`, or `rness_note` — when it chooses an
+  approach, deviates from the plan, is blocked, and when done: decisions
+  and their reasons, not steps. A note is a comment headed
+  `**Approach** · claude · 1a2b3c4d · \`feat/limits\` @ \`9f8e7d6\``
+(`--kind`titles it; the branch and commit are those of the session's
+repository), then the text, from the argument or stdin. With`"plan"`it goes to the plan's issue in`.rness`. With `"repo"`, to the plan's
+implementation issue in the repository the session works in: labelled
+`rness:plan`, found again by the last line of its body, made by the
+first note and made a sub-issue of the plan's. The note prints where it
+went (`acme/api#87`), for the pull request that completes the plan there
+to carry `Closes acme/api#87`and an earlier one`Refs acme/api#87`.
+GitHub closes the issue when a person merges that pull request into the
+default branch; rness closes nothing. A repository with its issues off,
+that refuses this login's write, or not under the organization on GitHub
+sends the note to the plan's issue, its first line saying why, and the
+next session start says so once. A session in `.rness/`or at the root
+writes on the plan's issue. With several plans in progress,`--plan`names one. Each note holds 1 to 4,000 characters; a session posts at most`limit` per plan (`journal full for this session: put the rest in the
+  pull request`); a note that looks like it holds a credential (`ghp_`,
+`gho_`, `github_pat_`, `AKIA…`, a private key, `xox…-`, `sk-…`) is
+refused, never redacted. The counts stay in the `.rness` clone's git
+directory (`rness/journal`), never pushed. At the session's end,
+`journal-summary`posts`**Session summary** · claude · 1a2b3c4d ·
+  47 min`, the branch and its commits since the session started (its
+`HEAD`, recorded in the clone's git directory, `rness/sessions/<id>`)
+and the branch's pull request: to each issue the notes went to, else to
+the one plan in progress when there is a commit; with neither, nothing.
+It counts toward no limit. Not verified against GitHub yet (2026-10-06):
+a sub-issue across repositories, and `Closes` on a pull request merged
+  into the default branch.
 - **One issue per document**: before making an issue, `pulse sync` reads
   the open issues of `.rness` labelled `rness` (one request per 100, and
   only when it has one to make). One whose body starts with the document's
@@ -496,7 +622,9 @@ repository, the board).
   detected provider this version cannot talk to. The order of keys is
   `contract`, `provider`, `org`, `agents`, `projects`, `repos`, `scopes`.
   The former `"pulse": { "project": <number> }` still reads, as
-  `"projects": { "pulse": <number> }`; both at once are refused.
+  `"projects": { "pulse": <number> }`; both at once are refused. Since
+  0.21.0 a board in `projects` is written whole, on several lines; a
+  number still reads, as its preset, until `rness sync` writes it whole.
 - 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.17.1 (supported:
@@ -507,22 +635,26 @@ github)`. `add`, `sync` and the local commands never refuse. `null` is not a
 
     rness mcp      # started by the agent over stdio, not by hand
 
-A local, read-only MCP server over the workspace's `.rness/`, for an agent to
-find what applies to the repository it works in and where a subject was
-decided:
+A local MCP server over the workspace's `.rness/`, for an agent to find what
+applies to the repository it works in and where a subject was decided. It
+is read-only but for `rness_note`, listed only when a board keeps a journal
+as the server starts (Claude Code starts it with the session):
 
-| Tool                                   | Returns                                                                                                                                             |
-| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `rness_context({ scope? })`            | the scope of the working directory (or the one named) and what applies to it: standards, decisions, specifications, plans — id, status, title, path |
-| `rness_list({ collection, status? })`  | every document of a collection, across scopes, optionally of one status                                                                             |
-| `rness_read({ path })`                 | one file of `.rness/`, 256 KiB at most; nothing outside it                                                                                          |
-| `rness_search({ query, collection? })` | the documents that match, most matching first, with the matching lines                                                                              |
+| Tool                                          | Returns                                                                                                                                             |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `rness_context({ scope? })`                   | the scope of the working directory (or the one named) and what applies to it: standards, decisions, specifications, plans — id, status, title, path |
+| `rness_list({ collection, status? })`         | every document of a collection, across scopes, optionally of one status                                                                             |
+| `rness_read({ path })`                        | one file of `.rness/`, 256 KiB at most; nothing outside it                                                                                          |
+| `rness_search({ query, collection? })`        | the documents that match, most matching first, with the matching lines                                                                              |
+| `rness_note({ text, session, kind?, plan? })` | a note of the agent's journal posted to GitHub, as `rness pulse note` posts it; the issue it went to (see "Pulse")                                  |
 
 - MCP over stdio, one message per line: the `2026-07-28` revision and the
   earlier ones that open with `initialize` (`2025-11-25` back to
   `2024-11-05`). No MCP SDK, no added dependency.
 - `.rness/` is read again on each call, so an edit shows at once. Nothing is
-  written.
+  written, but by `rness_note`, which posts with your login. It takes the
+  session as an argument (`claude · 1a2b3c4d`, as the session start spells
+  it): the server's environment names none.
 - With `claude` in `agents`, `sync` registers it in each clone:
   `.mcp.json` gets `mcpServers.rness`, which runs the pinned copy
   (`node ../../.rness/node_modules/@rness/cli/dist/bin/rness.js mcp`). A
@@ -691,6 +823,60 @@ 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.21.0 — boards declared in rness.json; what a session does to a board, declared; the agent's journal
+
+- 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.
+
+## 0.20.1 — the workspace's line in the prompt footer, without a warning sign; the mod never installs the pin
+
+- The workspace's line in Claude Code moves from the pinned status line to
+  the prompt footer, among the session modes, dim and without a sign:
+  `rness · web · 1 in progress`, `⚠ <n>` at its end when notes need action.
+  Claude Code draws every pinned line a plugin sets after a `⚠` in its
+  warning colour, the wrong sign for a line that informs. `rness status
+--json`'s `statusLine` carries the leading `rness` again. VS Code and
+  mobile surfaces, which draw no session modes, show no line; the
+  `/rness:status` pane stays.
+- The mod no longer installs the pin from inside Claude Code. It ran
+  `status --json` with catch-up on, so in a workspace whose pin drifts each
+  refresh ran `npm install` in `.rness`, without asking, and replaced a
+  local copy. It now runs with `RNESS_NO_DELEGATE=1`: the drift is a note
+  in the band, as the settings hooks report it.
+
 ## 0.20.0 — the status pane opens a document; ↑/↓ select, Tab changes the tab; Agent Pulse's colours and links
 
 - `/rness:status` in Claude Code: each row's status in Agent Pulse's colour;

package/dist/bin/rness.js

@@ -1,12 +1,14 @@
 #!/usr/bin/env node
 import {
   OWN_COMMANDS,
-  VERSION,
   catchUp,
   findDelegate,
-  reportError,
   run
-} from "../chunk-WIZHU4WT.js";
+} from "../chunk-T5PINUCP.js";
+import {
+  VERSION,
+  reportError
+} from "../chunk-D3D2WCGW.js";
 
 // src/bin/rness.ts
 import { pathToFileURL } from "url";

package/dist/bin/rness.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../src/bin/rness.ts","../../src/core/node-version.ts"],"sourcesContent":["#!/usr/bin/env node\nimport { pathToFileURL } from 'node:url'\n\nimport { run } from '../cli.ts'\nimport { OWN_COMMANDS, catchUp } from '../core/catch-up.ts'\nimport { findDelegate } from '../core/delegate.ts'\nimport { MIN_NODE_LABEL, isSupportedNode } from '../core/node-version.ts'\nimport { reportError } from '../report.ts'\nimport { VERSION } from '../version.ts'\n\n// `rness context | head`: once the reader has its lines it closes the pipe and\n// every further write emits EPIPE on stdout. Nothing is left to deliver, so end\n// quietly with success. This is the one process.exit() in the code base — it\n// runs only when there is no output left to drain (see main() below).\nprocess.stdout.on('error', (e: NodeJS.ErrnoException) => {\n  if (e.code === 'EPIPE') process.exit(0)\n  throw e\n})\n\n// Set process.exitCode rather than calling process.exit(): process.exit()\n// terminates before Node drains an async stdout pipe, truncating piped output\n// at the ~64 KiB pipe buffer (breaks `rness context --json | jq`, `$(...)`).\nasync function main(): Promise<number> {\n  if (!isSupportedNode(process.versions.node)) {\n    process.stderr.write(\n      `rness needs Node ${MIN_NODE_LABEL} or newer (running ${process.version})\\n`\n    )\n    return 1\n  }\n  const argv = process.argv.slice(2)\n  const skipDelegation =\n    OWN_COMMANDS.includes(argv[0] ?? '') ||\n    process.env['RNESS_NO_DELEGATE'] === '1'\n  // A pin that moved is installed first, and the fresh copy runs the command\n  // as its own process (spec 0008 §4).\n  const handedOff = await catchUp(argv)\n  if (handedOff !== null) return handedOff\n  const delegate = skipDelegation\n    ? null\n    : await findDelegate(process.cwd(), VERSION)\n  if (delegate !== null) {\n    const broken = (reason: string): Error =>\n      new Error(\n        `@rness/cli ${delegate.version} pinned in ${delegate.root}/.rness is not installed correctly (${reason}); reinstall in .rness/`\n      )\n    if (process.env['RNESS_DEBUG'] === '1') {\n      process.stderr.write(\n        `rness: delegating to @rness/cli ${delegate.version} (${delegate.entry})\\n`\n      )\n    }\n    let mod: Record<string, unknown>\n    try {\n      mod = (await import(pathToFileURL(delegate.entry).href)) as Record<\n        string,\n        unknown\n      >\n    } catch (e) {\n      throw broken(e instanceof Error ? e.message : String(e))\n    }\n    if (typeof mod['run'] !== 'function')\n      throw broken('dist/index.js does not export run')\n    const delegateRun = mod['run'] as (argv: string[]) => Promise<unknown>\n    const code = await delegateRun(argv)\n    return typeof code === 'number' ? code : 1\n  }\n  return run(argv)\n}\n\nmain()\n  .then((code) => {\n    process.exitCode = code\n  })\n  .catch((e: unknown) => {\n    process.exitCode = reportError(e)\n  })\n","/** The runtime floor of the published CLI (ADR 0010): Node 22.17, the line where `fs.glob` is stable. */\nexport const MIN_NODE = { major: 22, minor: 17 } as const\nexport const MIN_NODE_LABEL = `${MIN_NODE.major}.${MIN_NODE.minor}`\n\nfunction component(version: string, index: number): number {\n  const n = Number.parseInt(version.split('.')[index] ?? '', 10)\n  return Number.isNaN(n) ? -1 : n\n}\n\nexport function nodeMajor(version: string): number {\n  return Math.max(component(version, 0), 0)\n}\n\n/** True from `MIN_NODE` on: a newer major, or the same major from its minor. */\nexport function isSupportedNode(version: string): boolean {\n  const major = component(version, 0)\n  const minor = component(version, 1)\n  if (major < 0 || minor < 0) return false\n  if (major !== MIN_NODE.major) return major > MIN_NODE.major\n  return minor >= MIN_NODE.minor\n}\n"],"mappings":";;;;;;;;;;;AACA,SAAS,qBAAqB;;;ACAvB,IAAM,WAAW,EAAE,OAAO,IAAI,OAAO,GAAG;AACxC,IAAM,iBAAiB,GAAG,SAAS,KAAK,IAAI,SAAS,KAAK;AAEjE,SAAS,UAAU,SAAiB,OAAuB;AACzD,QAAM,IAAI,OAAO,SAAS,QAAQ,MAAM,GAAG,EAAE,KAAK,KAAK,IAAI,EAAE;AAC7D,SAAO,OAAO,MAAM,CAAC,IAAI,KAAK;AAChC;AAOO,SAAS,gBAAgB,SAA0B;AACxD,QAAM,QAAQ,UAAU,SAAS,CAAC;AAClC,QAAM,QAAQ,UAAU,SAAS,CAAC;AAClC,MAAI,QAAQ,KAAK,QAAQ,EAAG,QAAO;AACnC,MAAI,UAAU,SAAS,MAAO,QAAO,QAAQ,SAAS;AACtD,SAAO,SAAS,SAAS;AAC3B;;;ADNA,QAAQ,OAAO,GAAG,SAAS,CAAC,MAA6B;AACvD,MAAI,EAAE,SAAS,QAAS,SAAQ,KAAK,CAAC;AACtC,QAAM;AACR,CAAC;AAKD,eAAe,OAAwB;AACrC,MAAI,CAAC,gBAAgB,QAAQ,SAAS,IAAI,GAAG;AAC3C,YAAQ,OAAO;AAAA,MACb,oBAAoB,cAAc,sBAAsB,QAAQ,OAAO;AAAA;AAAA,IACzE;AACA,WAAO;AAAA,EACT;AACA,QAAM,OAAO,QAAQ,KAAK,MAAM,CAAC;AACjC,QAAM,iBACJ,aAAa,SAAS,KAAK,CAAC,KAAK,EAAE,KACnC,QAAQ,IAAI,mBAAmB,MAAM;AAGvC,QAAM,YAAY,MAAM,QAAQ,IAAI;AACpC,MAAI,cAAc,KAAM,QAAO;AAC/B,QAAM,WAAW,iBACb,OACA,MAAM,aAAa,QAAQ,IAAI,GAAG,OAAO;AAC7C,MAAI,aAAa,MAAM;AACrB,UAAM,SAAS,CAAC,WACd,IAAI;AAAA,MACF,cAAc,SAAS,OAAO,cAAc,SAAS,IAAI,uCAAuC,MAAM;AAAA,IACxG;AACF,QAAI,QAAQ,IAAI,aAAa,MAAM,KAAK;AACtC,cAAQ,OAAO;AAAA,QACb,mCAAmC,SAAS,OAAO,KAAK,SAAS,KAAK;AAAA;AAAA,MACxE;AAAA,IACF;AACA,QAAI;AACJ,QAAI;AACF,YAAO,MAAM,OAAO,cAAc,SAAS,KAAK,EAAE;AAAA,IAIpD,SAAS,GAAG;AACV,YAAM,OAAO,aAAa,QAAQ,EAAE,UAAU,OAAO,CAAC,CAAC;AAAA,IACzD;AACA,QAAI,OAAO,IAAI,KAAK,MAAM;AACxB,YAAM,OAAO,mCAAmC;AAClD,UAAM,cAAc,IAAI,KAAK;AAC7B,UAAM,OAAO,MAAM,YAAY,IAAI;AACnC,WAAO,OAAO,SAAS,WAAW,OAAO;AAAA,EAC3C;AACA,SAAO,IAAI,IAAI;AACjB;AAEA,KAAK,EACF,KAAK,CAAC,SAAS;AACd,UAAQ,WAAW;AACrB,CAAC,EACA,MAAM,CAAC,MAAe;AACrB,UAAQ,WAAW,YAAY,CAAC;AAClC,CAAC;","names":[]}
+{"version":3,"sources":["../../src/bin/rness.ts","../../src/core/node-version.ts"],"sourcesContent":["#!/usr/bin/env node\nimport { pathToFileURL } from 'node:url'\n\nimport { run } from '../cli.ts'\nimport { OWN_COMMANDS, catchUp } from '../core/catch-up.ts'\nimport { findDelegate } from '../core/delegate.ts'\nimport { MIN_NODE_LABEL, isSupportedNode } from '../core/node-version.ts'\nimport { reportError } from '../report.ts'\nimport { VERSION } from '../version.ts'\n\n// `rness context | head`: once the reader has its lines it closes the pipe and\n// every further write emits EPIPE on stdout. Nothing is left to deliver, so end\n// quietly with success. This is the one process.exit() in the code base — it\n// runs only when there is no output left to drain (see main() below).\nprocess.stdout.on('error', (e: NodeJS.ErrnoException) => {\n  if (e.code === 'EPIPE') process.exit(0)\n  throw e\n})\n\n// Set process.exitCode rather than calling process.exit(): process.exit()\n// terminates before Node drains an async stdout pipe, truncating piped output\n// at the ~64 KiB pipe buffer (breaks `rness context --json | jq`, `$(...)`).\nasync function main(): Promise<number> {\n  if (!isSupportedNode(process.versions.node)) {\n    process.stderr.write(\n      `rness needs Node ${MIN_NODE_LABEL} or newer (running ${process.version})\\n`\n    )\n    return 1\n  }\n  const argv = process.argv.slice(2)\n  const skipDelegation =\n    OWN_COMMANDS.includes(argv[0] ?? '') ||\n    process.env['RNESS_NO_DELEGATE'] === '1'\n  // A pin that moved is installed first, and the fresh copy runs the command\n  // as its own process (spec 0008 §4).\n  const handedOff = await catchUp(argv)\n  if (handedOff !== null) return handedOff\n  const delegate = skipDelegation\n    ? null\n    : await findDelegate(process.cwd(), VERSION)\n  if (delegate !== null) {\n    const broken = (reason: string): Error =>\n      new Error(\n        `@rness/cli ${delegate.version} pinned in ${delegate.root}/.rness is not installed correctly (${reason}); reinstall in .rness/`\n      )\n    if (process.env['RNESS_DEBUG'] === '1') {\n      process.stderr.write(\n        `rness: delegating to @rness/cli ${delegate.version} (${delegate.entry})\\n`\n      )\n    }\n    let mod: Record<string, unknown>\n    try {\n      mod = (await import(pathToFileURL(delegate.entry).href)) as Record<\n        string,\n        unknown\n      >\n    } catch (e) {\n      throw broken(e instanceof Error ? e.message : String(e))\n    }\n    if (typeof mod['run'] !== 'function')\n      throw broken('dist/index.js does not export run')\n    const delegateRun = mod['run'] as (argv: string[]) => Promise<unknown>\n    const code = await delegateRun(argv)\n    return typeof code === 'number' ? code : 1\n  }\n  return run(argv)\n}\n\nmain()\n  .then((code) => {\n    process.exitCode = code\n  })\n  .catch((e: unknown) => {\n    process.exitCode = reportError(e)\n  })\n","/** The runtime floor of the published CLI (ADR 0010): Node 22.17, the line where `fs.glob` is stable. */\nexport const MIN_NODE = { major: 22, minor: 17 } as const\nexport const MIN_NODE_LABEL = `${MIN_NODE.major}.${MIN_NODE.minor}`\n\nfunction component(version: string, index: number): number {\n  const n = Number.parseInt(version.split('.')[index] ?? '', 10)\n  return Number.isNaN(n) ? -1 : n\n}\n\nexport function nodeMajor(version: string): number {\n  return Math.max(component(version, 0), 0)\n}\n\n/** True from `MIN_NODE` on: a newer major, or the same major from its minor. */\nexport function isSupportedNode(version: string): boolean {\n  const major = component(version, 0)\n  const minor = component(version, 1)\n  if (major < 0 || minor < 0) return false\n  if (major !== MIN_NODE.major) return major > MIN_NODE.major\n  return minor >= MIN_NODE.minor\n}\n"],"mappings":";;;;;;;;;;;;;AACA,SAAS,qBAAqB;;;ACAvB,IAAM,WAAW,EAAE,OAAO,IAAI,OAAO,GAAG;AACxC,IAAM,iBAAiB,GAAG,SAAS,KAAK,IAAI,SAAS,KAAK;AAEjE,SAAS,UAAU,SAAiB,OAAuB;AACzD,QAAM,IAAI,OAAO,SAAS,QAAQ,MAAM,GAAG,EAAE,KAAK,KAAK,IAAI,EAAE;AAC7D,SAAO,OAAO,MAAM,CAAC,IAAI,KAAK;AAChC;AAOO,SAAS,gBAAgB,SAA0B;AACxD,QAAM,QAAQ,UAAU,SAAS,CAAC;AAClC,QAAM,QAAQ,UAAU,SAAS,CAAC;AAClC,MAAI,QAAQ,KAAK,QAAQ,EAAG,QAAO;AACnC,MAAI,UAAU,SAAS,MAAO,QAAO,QAAQ,SAAS;AACtD,SAAO,SAAS,SAAS;AAC3B;;;ADNA,QAAQ,OAAO,GAAG,SAAS,CAAC,MAA6B;AACvD,MAAI,EAAE,SAAS,QAAS,SAAQ,KAAK,CAAC;AACtC,QAAM;AACR,CAAC;AAKD,eAAe,OAAwB;AACrC,MAAI,CAAC,gBAAgB,QAAQ,SAAS,IAAI,GAAG;AAC3C,YAAQ,OAAO;AAAA,MACb,oBAAoB,cAAc,sBAAsB,QAAQ,OAAO;AAAA;AAAA,IACzE;AACA,WAAO;AAAA,EACT;AACA,QAAM,OAAO,QAAQ,KAAK,MAAM,CAAC;AACjC,QAAM,iBACJ,aAAa,SAAS,KAAK,CAAC,KAAK,EAAE,KACnC,QAAQ,IAAI,mBAAmB,MAAM;AAGvC,QAAM,YAAY,MAAM,QAAQ,IAAI;AACpC,MAAI,cAAc,KAAM,QAAO;AAC/B,QAAM,WAAW,iBACb,OACA,MAAM,aAAa,QAAQ,IAAI,GAAG,OAAO;AAC7C,MAAI,aAAa,MAAM;AACrB,UAAM,SAAS,CAAC,WACd,IAAI;AAAA,MACF,cAAc,SAAS,OAAO,cAAc,SAAS,IAAI,uCAAuC,MAAM;AAAA,IACxG;AACF,QAAI,QAAQ,IAAI,aAAa,MAAM,KAAK;AACtC,cAAQ,OAAO;AAAA,QACb,mCAAmC,SAAS,OAAO,KAAK,SAAS,KAAK;AAAA;AAAA,MACxE;AAAA,IACF;AACA,QAAI;AACJ,QAAI;AACF,YAAO,MAAM,OAAO,cAAc,SAAS,KAAK,EAAE;AAAA,IAIpD,SAAS,GAAG;AACV,YAAM,OAAO,aAAa,QAAQ,EAAE,UAAU,OAAO,CAAC,CAAC;AAAA,IACzD;AACA,QAAI,OAAO,IAAI,KAAK,MAAM;AACxB,YAAM,OAAO,mCAAmC;AAClD,UAAM,cAAc,IAAI,KAAK;AAC7B,UAAM,OAAO,MAAM,YAAY,IAAI;AACnC,WAAO,OAAO,SAAS,WAAW,OAAO;AAAA,EAC3C;AACA,SAAO,IAAI,IAAI;AACjB;AAEA,KAAK,EACF,KAAK,CAAC,SAAS;AACd,UAAQ,WAAW;AACrB,CAAC,EACA,MAAM,CAAC,MAAe;AACrB,UAAQ,WAAW,YAAY,CAAC;AAClC,CAAC;","names":[]}