@rness/cli 0.5.3 → 0.6.1

package/README.md

@@ -6,8 +6,12 @@ Not an agent — no LLM loop.
 
 ## Install
 
-    npm create rness           # prompts for the organization, then the repositories for your workspace
+    npm create rness           # asks how to start: a GitHub organization, or a blank workspace
     npm create rness acme      # the organization github.com/acme, no first prompt
+    pnpm create rness demo --blank   # ./demo with no GitHub step; npm: npm create rness demo -- --blank
+    pnpm create rness          # the same with pnpm, yarn or bun: `.rness/` is
+    yarn create rness          # installed with the manager that ran the command
+    bun create rness
     npm i -g @rness/cli        # the command is `rness`
     npx @rness/cli --help
 
@@ -17,6 +21,7 @@ Inside a workspace, every `rness` delegates to the copy pinned in
 ## Commands
 
     rness create [<org>] [--repos a,b] [--pm npm|pnpm|yarn|bun] [--ssh|--https] [--skip-install] -y
+    rness create <name> --blank [--pm npm|pnpm|yarn|bun] [--skip-install] -y
     rness add <repo> [--scopes apps/web,packages/ui] [--ssh|--https] -y
     rness sync [--all] [--scope <name>] [--check] [--pull] -y
     rness upgrade [<version>] -y
@@ -29,6 +34,12 @@ Inside a workspace, every `rness` delegates to the copy pinned in
 confirmation in a terminal; pass `-y`/`--yes` in scripts. `sync --check`
 writes nothing and exits 1 when a block is out of date — use it in CI.
 
+`create --blank` needs no GitHub organization, account or login: it writes
+`<name>/.rness/` (a `rness.json` without `"org"`, committed), an empty
+`<name>/org/` and the root `AGENTS.md` and `CLAUDE.md`. Only the install of
+`.rness/` goes to the network. Bring repositories in with
+`rness add <owner>/<repo>` or a git URL — a bare name needs an `"org"`.
+
 ### Log in
 
     rness login     # shows a code and https://github.com/login/device
@@ -136,6 +147,37 @@ its content does.
 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.6.1 — hints you can type
+
+- Every hint that names a command to run (`not cloned: …`, `run … sync`,
+  `run … login`, `… upgrade <version>`) spells rness the way it was
+  launched: `npx @rness/cli`, `pnpm dlx @rness/cli`, `yarn dlx @rness/cli`
+  (npx on Yarn 1), `bunx @rness/cli`, or `rness` when it was typed directly.
+  The next steps of `create` follow the same rule; `--pm`, which chooses what
+  `.rness/` installs with, no longer decides them.
+- Under `rness-dev` (`RNESS_NO_DELEGATE=1`), `create` writes its first blocks
+  from the sources rather than through the copy it just installed.
+- Blocks are unchanged: no `rness sync` is needed after upgrading.
+
+## 0.6.0 — a workspace without GitHub
+
+- `rness create <name> --blank` writes `<name>/.rness/` (a `rness.json`
+  without `"org"`, committed), an empty `<name>/org/` and the root
+  `AGENTS.md` and `CLAUDE.md`, with no login, SSH test or GitHub request.
+  With `npm create`, flags go after `--`: `npm create rness demo -- --blank`.
+- In a terminal, `create` with no organization and no `--repos` first asks
+  how to start: from a GitHub organization, as before, or a blank local
+  workspace.
+- A `rness.json` without `"org"` is no longer a warning in `sync`, `add` and
+  `validate`. In such a workspace `rness add <repo>` exits 2 and asks for
+  `<owner>/<repo>` or a git URL: it used to take the directory name as the
+  owner, a repository that almost never exists.
+- The next steps `create` prints are written with the package manager that
+  ran it: `npx @rness/cli`, `pnpm dlx @rness/cli`, `yarn dlx @rness/cli`
+  (npx on Yarn 1), `bunx @rness/cli`, and `<pm> create rness <org>` for
+  teammates. They said `rness …`, a command `npm create` never installs.
+- Blocks are unchanged: no `rness sync` is needed after upgrading.
+
 ## 0.5.3 — catching up no longer depends on the global install
 
 - After a pull that moved the pin, the next `rness` command installs it. That
@@ -287,12 +329,16 @@ To reach it from a workspace elsewhere on the machine, link it once:
     ln -s "$PWD/scripts/dev.mjs" ~/.local/bin/rness-dev   # from the repository root
     cd ~/somewhere/acme && rness-dev validate
 
-`create` is never delegated, so it always runs these sources — and it refuses
-to run inside a workspace, so call it from an empty directory.
+`create` is never delegated, so it always runs these sources — the blocks it
+writes at the end included, even once it has installed the pinned copy — and
+it refuses to run inside a workspace, so call it from an empty directory.
 
 `pnpm verdaccio` is the other loop: a local registry that serves this build as
 a real package, for what only shows up through an install (`npm create rness`,
-the pinned copy, a version bump). It is slower, and its caches have to be
-forgotten on every redeploy, which `deploy` now does.
+the pinned copy, a version bump). Each `pnpm verdaccio deploy` publishes a
+version of its own — `0.6.1-dev.<time>` for sources at 0.6.0 — so a new
+workspace pins exactly that build and no cache serves an older one under its
+number. To try it in a workspace that exists, run `rness upgrade <version>`
+inside it; the deploy prints the line.
 
 Node ≥ 24. MIT.

package/dist/bin/rness.js

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