@rness/cli 0.17.1 → 0.17.3

package/README.md

@@ -98,7 +98,11 @@ the files a given agent needs, for the agents the team declares in
   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
+  by `sync --check` and written back by `sync`. The plugin's manifest,
+  `.claude-plugin/plugin.json`, also carries the agent-plugins.org
+  `$schema`, the author, homepage, repository, licence and keywords, so a
+  scanner that looks for an Agent Plugins manifest finds one; Claude Code
+  reads the same file. 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
@@ -114,7 +118,8 @@ the files a given agent needs, for the agents the team declares in
   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.
+  when a choice is expensive to reverse — but writes nothing without a yes,
+  except `/rness:done` on a plan whose last task has just passed.
   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
@@ -122,7 +127,13 @@ the files a given agent needs, for the agents the team declares in
   `{ 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.
+  edit made without a skill leaves none. The agent moves a status with the
+  work (a plan `In progress`, then `Completed`; a specification
+  `Implemented`) and whenever the developer says so; accepting an ADR or
+  approving a specification stays the developer's unless they asked it to
+  go ahead. Each skill ends in a commit of the files the agent alone
+  changed, added by name; a file someone else changed too is left
+  uncommitted and named. No skill pushes.
 - 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
@@ -565,6 +576,37 @@ 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.3 — the packages name the product; the plugin manifest for scanners
+
+- `homepage` of `@rness/cli`, `create-rness` and `@rness/create` is
+  `https://rness.dev`; `repository` and `bugs` stay on GitHub. That is
+  how a scanner tells an official package from a fork;
+  `pnpm check:versions` checks it with the versions.
+- `.claude/skills/rness/.claude-plugin/plugin.json`, written by the Claude
+  target, carries the agent-plugins.org `$schema`, the author, homepage,
+  repository, licence and keywords. `rness sync` rewrites it once in each
+  repository; commit it there.
+- `skills/rness/SKILL.md` at the root of the repository: when to use Rness
+  and how to install and run it, for `npx skills add rness-dev/rness`
+  and skills.sh.
+
+## 0.17.2 — the lifecycle skills move statuses and commit their files
+
+- `/rness:adr`, `/rness:spec`, `/rness:plan` and `/rness:done` let the
+  agent move a status as the work does — a plan `In progress` as its tasks
+  start, `Completed` once they pass, a specification `Implemented` with its
+  last plan — and whenever the developer says so. Accepting an ADR or
+  approving a specification stays the developer's unless they asked the
+  agent to go ahead. `/rness:done` closes a plan whose last task has just
+  passed without asking first.
+- Each of them ends in a commit of the files the agent alone changed, in
+  their repository, added by name. A file that had uncommitted changes
+  before the agent's first edit, or that someone else changed since, is
+  left out and named. Nothing is pushed. Until now they committed nothing,
+  which left their files for someone else to find.
+- `rness upgrade` rewrites the four skills under `.claude/skills/rness/`;
+  commit them in each repository, as its next steps list.
+
 ## 0.17.1 — pulse shows it is at work
 
 - `pulse create` and `pulse sync` show a transient line while they write a

package/dist/bin/rness.js

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

package/dist/{chunk-GAZDKEOH.js → chunk-MMPMXYZU.js}

@@ -508,7 +508,7 @@ function parseRepoSpec(spec, org, host) {
 }
 
 // src/version.ts
-var VERSION = "0.17.1";
+var VERSION = "0.17.3";
 
 // src/core/pm.ts
 import { execFile as execFile2 } from "child_process";
@@ -4315,8 +4315,21 @@ import { dirname as dirname4, join as join14 } from "path";
 var PLUGIN = ".claude/skills/rness";
 var PLUGIN_JSON = `${JSON.stringify(
   {
+    $schema: "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
     name: "rness",
-    description: "The rness workspace in Claude Code: /rness:status, /rness:adr, /rness:spec, /rness:plan, /rness:done."
+    description: "The rness workspace in Claude Code: /rness:status, /rness:adr, /rness:spec, /rness:plan, /rness:done.",
+    author: { name: "rness-dev", url: "https://rness.dev" },
+    homepage: "https://rness.dev",
+    repository: "https://github.com/rness-dev/rness",
+    license: "MIT",
+    keywords: [
+      "rness",
+      "agents",
+      "claude-code",
+      "adr",
+      "specification",
+      "plan"
+    ]
   },
   null,
   2
@@ -4345,6 +4358,17 @@ then \`npx @rness/cli status\` (q to close), then \`fg\`; or in another
 terminal, from the workspace's \`.rness/\`: \`${localRunner(pm)} rness status\`._
 `;
 }
+var STATUS_RULE = `Move a status yourself when the work calls for it, and whenever the
+developer says so: a plan \`In progress\` as you start its tasks,
+\`Completed\` once they pass; a specification \`Implemented\` with its last
+plan; a document \`Superseded\` by the one that replaces it. Accepting a
+decision \u2014 an ADR \`Accepted\`, a specification \`Approved\` \u2014 is the
+developer's, unless they asked you to go ahead with the work.`;
+var COMMIT_RULE = `Commit each file you changed, in its own repository, and only the files
+you alone changed: add them by name, never \`git add -A\` nor \`commit -a\`.
+A file that had uncommitted changes before your first edit (\`git status\`
+tells you), or that someone else changed since, stays uncommitted: say
+which. Never push.`;
 var LIFECYCLE2 = [
   {
     name: "adr",
@@ -4381,9 +4405,12 @@ Writing:
   \`Claude\`: for example \`Claude Opus 5.5\`.
 - The rness hook checks every edit under \`${rness}/\`: fix what it reports.
 
-After writing: give the path and the Decision section, and say the ADR
-stays \`Proposed\` until the developer accepts it. Change a status only when
-the developer says so. Do not commit.
+After writing: give the path and the Decision section. The ADR stays
+\`Proposed\` until it is accepted.
+
+${STATUS_RULE}
+
+${COMMIT_RULE}
 `
   },
   {
@@ -4422,9 +4449,13 @@ Writing:
   \`Claude\`: for example \`Claude Opus 5.5\`.
 - The rness hook checks every edit under \`${rness}/\`: fix what it reports.
 
-After writing: give the path and the summary. It stays \`Draft\` until the
-developer moves it (\`Proposed\` for review, \`Approved\` to plan it). No plan
-here: \`/rness:plan NNNN\` once approved. Do not commit.
+After writing: give the path and the summary. It starts \`Draft\`:
+\`Proposed\` for review, \`Approved\` to plan it. No plan here:
+\`/rness:plan NNNN\` once approved.
+
+${STATUS_RULE}
+
+${COMMIT_RULE}
 `
   },
   {
@@ -4466,8 +4497,13 @@ Writing:
   \`Claude\`: for example \`Claude Opus 5.5\`.
 - The rness hook checks every edit under \`${rness}/\`: fix what it reports.
 
-After writing: give the path and the list of tasks. It becomes \`Ready\` when
-the developer agrees. Do not commit.
+After writing: give the path and the list of tasks. It starts \`Draft\`, and
+becomes \`Ready\` once the developer agrees with it or asks you to carry it
+out.
+
+${STATUS_RULE}
+
+${COMMIT_RULE}
 `
   },
   {
@@ -4481,8 +4517,9 @@ Arguments: \`$ARGUMENTS\`.
 
 1. The plan: the one named, else the one \`In progress\`. Several or none:
    ask.
-2. If the developer did not ask to close it in so many words, propose it in
-   a single line and wait for a yes.
+2. The developer asked to close it, or its last task has just passed in
+   this session: close it. Otherwise propose it in a single line and wait
+   for a yes.
 3. Read the plan, its specification and \`${rness}/CONVENTIONS.md\`.
 4. Evidence first. For each task, what shows it done: a test, a build, a
    command's output in this session. A task without evidence: run its
@@ -4504,7 +4541,9 @@ Arguments: \`$ARGUMENTS\`.
    blocker written in it. Say what remains.
 7. The rness hook checks every edit under \`${rness}/\`: fix what it reports.
 
-After: list the files changed and the statuses moved. Do not commit.
+After: list the files changed and the statuses moved.
+
+${COMMIT_RULE}
 `
   }
 ];
@@ -9579,4 +9618,4 @@ export {
   OWN_COMMANDS,
   catchUp
 };
-//# sourceMappingURL=chunk-GAZDKEOH.js.map
+//# sourceMappingURL=chunk-MMPMXYZU.js.map