@nanocollective/roster 0.1.0-alpha.20 → 0.1.0-alpha.21

package/README.md

@@ -33,6 +33,11 @@ first finished run, most of it writing what the business is and the staff member
 Everything the portal does is also a command, on the same files. Nothing changes anything
 without `--apply`.
 
+**`roster` here means either of these.** With nothing installed, run commands through npx:
+`npx @nanocollective/roster@latest upgrade`. Or install it once with
+`npm install -g @nanocollective/roster` and type `roster upgrade`. When you run through npx,
+the commands roster suggests are printed the npx way, so they can be pasted as they are.
+
 ```bash
 roster init --org acme          # ops repo, org layer, merge base
 roster hire cto                 # scaffold a staff member: repo, workflows, labels, peers

package/dist/cli.js

@@ -5401,6 +5401,30 @@ function short3(e) {
   return line.length > 200 ? `${line.slice(0, 199)}\u2026` : line;
 }
 
+// src/lib/bin.ts
+var NPX = "npx @nanocollective/roster@latest";
+function bin(env = process.env, argv1 = process.argv[1] ?? "") {
+  if (env.ROSTER_BIN) return env.ROSTER_BIN;
+  if (env.npm_command === "exec" || /[\\/]_npx[\\/]/.test(argv1)) return NPX;
+  return "roster";
+}
+var COMMAND = /\broster(?= (?:init|hire|app|credential|run|doctor|fix|portal|prompt|upgrade|retire|lint|brief|export|help)\b)/g;
+function withBin(text, name = bin()) {
+  return name === "roster" ? text : text.replace(COMMAND, name);
+}
+function rewriteOutput(name = bin()) {
+  const raw = process.stdout.write.bind(process.stdout);
+  if (name === "roster") return (text) => void raw(text);
+  for (const stream of [process.stdout, process.stderr]) {
+    const write = stream.write.bind(stream);
+    stream.write = ((chunk, ...rest) => write(
+      typeof chunk === "string" ? withBin(chunk, name) : chunk,
+      ...rest
+    ));
+  }
+  return (text) => void raw(text);
+}
+
 // src/lib/browser.ts
 import { spawn } from "child_process";
 function shouldOpen(env, isTTY, noOpen) {
@@ -7496,7 +7520,7 @@ function json(res, data) {
     "content-type": "application/json; charset=utf-8",
     "cache-control": "no-store"
   });
-  res.end(JSON.stringify(data));
+  res.end(withBin(JSON.stringify(data)));
 }
 function hireFlags(params) {
   const num = (k) => params.get(k) ? Number(params.get(k)) : void 0;
@@ -7900,11 +7924,24 @@ var HELPS = {
   export: exportHelp
 };
 async function main(argv) {
+  const raw = rewriteOutput();
   const [command, ...rest] = argv;
   if (!command) return portalCommand([]);
   if (command === "help" || command === "--help" || command === "-h") {
     const topic = rest[0];
-    process.stdout.write(topic && HELPS[topic] ? HELPS[topic] : HELP);
+    if (!topic || !HELPS[topic]) {
+      const name = bin();
+      if (name !== "roster") {
+        raw(
+          `
+  Run these as ${name} <command>, or install it: npm install -g @nanocollective/roster
+`
+        );
+      }
+      raw(HELP);
+      return 0;
+    }
+    process.stdout.write(HELPS[topic]);
     return 0;
   }
   const run6 = COMMANDS[command];

package/docs/commands.md

@@ -6,6 +6,11 @@ sidebar_order: 8
 
 # Commands
 
+**`roster` here means either of these.** With nothing installed, run commands through npx:
+`npx @nanocollective/roster@latest upgrade`. Or install it once with
+`npm install -g @nanocollective/roster` and type `roster upgrade`. When you run through npx,
+the commands roster suggests are printed the npx way, so they can be pasted as they are.
+
 Every command that changes anything prints a plan and changes nothing unless you pass
 `--apply`. `lint`, `prompt`, `export`, `brief`, `doctor` and `fix` never change anything.
 `portal` is the exception: it is interactive, and each change there is a button you press after

package/docs/getting-started.md

@@ -144,6 +144,9 @@ member on their next run.
 
 The same road, command by command. Each prints its plan and changes nothing without `--apply`.
 
+`roster` below means `npx @nanocollective/roster@latest`, unless you have installed it with
+`npm install -g @nanocollective/roster`.
+
 ```bash
 roster init --org acme --apply        # the ops repo, and its Actions access
 roster brief discover                 # a brief for org/business.md; write priorities.md too

package/docs/upgrading.md

@@ -10,9 +10,9 @@ The framework writes templates out. A tenant runs its own copies. So the two dri
 `roster upgrade` is what reconciles them without eating your edits.
 
 ```bash
-roster upgrade                 # what would change
-roster upgrade --apply         # do it
-roster upgrade --check         # exit non-zero if anything is pending (for CI)
+npx @nanocollective/roster@latest upgrade           # what would change
+npx @nanocollective/roster@latest upgrade --apply   # do it
+npx @nanocollective/roster@latest upgrade --check   # exit non-zero if anything is pending (for CI)
 ```
 
 ## How it decides

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nanocollective/roster",
-  "version": "0.1.0-alpha.20",
+  "version": "0.1.0-alpha.21",
   "description": "An agent-run org, powered by GitHub. Scaffold AI staff members whose brain is a repo.",
   "type": "module",
   "bin": {

package/templates/portal/js/views/staff.js

@@ -219,13 +219,9 @@ export function viewStaff(m) {
 
     box.append(el("div", { className: "planhead", textContent: "Then, on the new card" }));
     box.append(
-      line(
-        "todo",
-        "GitHub App, or roster app " + s.handle + " --apply: creates it, sets its secrets, and " +
-          "opens the install page with the repos already ticked",
-      ),
+      line("todo", "Create their GitHub App, then install it on the repos it opens with ticked"),
       line("todo", "Write the charter"),
-      line("todo", "Run once now, or roster run " + s.handle + " --apply: the run that proves the wiring"),
+      line("todo", "Run once now, to check everything works"),
     );
     for (const w of plan.warnings ?? []) box.append(line("warn", S.data.staff.length ? w : portalWords(w)));