@turri-dev/cli 0.1.1 → 0.1.2-next.48dacfc

package/dist/regenerate/shell.js

@@ -72,7 +72,8 @@ function watch() {
     const script = [
         `while kill -0 ${process.pid} 2>/dev/null; do sleep 2; done`,
         `[ -f '${file}' ] || exit 0`,
-        `while read -r group; do kill -KILL -- "-$group" 2>/dev/null; done < '${file}'`,
+        // No `--` after the signal: dash, /bin/sh on Debian and Ubuntu, reads it as a process id and kills nothing.
+        `while read -r group; do kill -KILL "-$group" 2>/dev/null; done < '${file}'`,
         `rm -f '${file}'`,
     ].join("\n");
     try {

package/docs/development.md

@@ -29,6 +29,19 @@ in `src/` beside them. `npm pack` and `npm publish` run it first (`prepack`), an
 the launcher and extension beside itself, whichever they are. To try the package as users get it:
 `npm pack`, then `npm install -g ./turri-dev-cli-<version>.tgz`.
 
+## Publishing
+
+`.github/workflows/publish.yml` publishes `@turri-dev/cli`, after the typecheck and the suite pass:
+
+- every push or merge into `main` publishes a prerelease under the `next` dist-tag - the patch after the `latest` on
+  npm, with the commit's sha: `0.1.2-next.<sha>`. `latest` is not touched; `npm install -g @turri-dev/cli@next` gets it.
+- a GitHub Release tagged `vX.Y.Z`, published by hand, publishes `X.Y.Z` as `latest` (or under `next`, if the release
+  is marked a pre-release). The tag is the version: it is set in the runner and never committed, so `package.json`'s
+  version on `main` is stale by design.
+
+The workflow signs in to npm with npm's trusted publishing (OIDC), not a token: the package's settings on npmjs.com
+trust `turri-oss/turri`, the workflow `publish.yml` and the environment `npm`. Renaming the workflow file breaks it.
+
 ## Layout
 
 | path | what it is |

package/docs/installation.md

@@ -22,14 +22,15 @@ turri               # pi, with turri's tools, skills and themes loaded
 ```
 
 The package is `@turri-dev/cli` - npm keeps the name `turri` back, as too like another
-package's - and the command it puts on your PATH is `turri`.
+package's - and the command it puts on your PATH is `turri`. `npm install -g @turri-dev/cli@next` gets the latest
+prerelease instead, built from the last commit on `main`.
 
 ## From a clone
 
 To work on turri itself, put the clone on your PATH instead:
 
 ```bash
-git clone git@github.com:plainlang/turri.git && cd turri
+git clone git@github.com:turri-oss/turri.git && cd turri
 npm install
 npm link              # puts `turri` on your PATH, pointing at this clone
 ```

package/package.json

@@ -1,14 +1,14 @@
 {
   "name": "@turri-dev/cli",
-  "version": "0.1.1",
+  "version": "0.1.2-next.48dacfc",
   "license": "MIT",
   "type": "module",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/plainlang/turri.git"
+    "url": "git+https://github.com/turri-oss/turri.git"
   },
-  "homepage": "https://github.com/plainlang/turri#readme",
-  "bugs": "https://github.com/plainlang/turri/issues",
+  "homepage": "https://github.com/turri-oss/turri#readme",
+  "bugs": "https://github.com/turri-oss/turri/issues",
   "description": "An agent that builds code from ***plain specifications, with harness-enforced review and conformance gates.",
   "engines": {
     "node": ">=22.19"