@rness/cli 0.6.0 → 0.6.2

package/README.md

@@ -147,6 +147,36 @@ 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.2 — no dialog for the root CLAUDE.md
+
+- Opening Claude Code in a repository of the workspace no longer asks "Allow
+  external CLAUDE.md file imports?". The workspace root `CLAUDE.md` carried
+  `@AGENTS.md`; Claude Code loads that file from every repository below it,
+  where the import points outside the working directory. `rness sync` now
+  writes the global block into the root `CLAUDE.md` itself; a line that is
+  exactly `@AGENTS.md` is dropped there, the rest of the file is kept. The
+  `CLAUDE.md` of each repository keeps its `@AGENTS.md`.
+- The root files are not in any repository: run `rness sync` once after the
+  upgrade, on every machine. The blocks in the repositories are unchanged.
+- `sync --check` and `validate` cover the root `CLAUDE.md`. At the root, a
+  symlink between `CLAUDE.md` and `AGENTS.md` is left as it is and the other
+  file is still written.
+- The scaffold's `validate.yml` uses `actions/checkout@v7` and
+  `actions/setup-node@v7`, as the rness repositories do. A workspace created
+  before keeps its own file.
+
+## 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`
@@ -317,12 +347,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-NY3WV7X5.js";
+} from "../chunk-7TOHFPW6.js";
 
 // src/bin/rness.ts
 import { pathToFileURL } from "url";