@nledford/omp-coord 0.2.0 → 0.2.1

package/.omp-plugin/marketplace.json

@@ -7,7 +7,7 @@
       "name": "omp-coord",
       "source": "./",
       "description": "Shared subagent caps, build and test queues, claims, pause, a decision log and messages across omp sessions working in one project on one machine.",
-      "version": "0.2.0",
+      "version": "0.2.1",
       "author": { "name": "Nathaniel Ledford" },
       "homepage": "https://github.com/nledford/omp-coord",
       "repository": "https://github.com/nledford/omp-coord",

package/CHANGELOG.md

@@ -6,6 +6,16 @@ Add each user-visible change under Unreleased as it lands, in one of: Added, Cha
 
 ## [Unreleased]
 
+## [0.2.1] - 2026-10-26
+
+### Added
+
+- Releases are published to npmjs.com as `@nledford/omp-coord`, with provenance: `omp plugin install @nledford/omp-coord` needs no token or `.npmrc`.
+
+### Fixed
+
+- On Linux, where `/proc` cannot be read (some hardened containers), a timed-out job now falls back to signalling its process group instead of failing.
+
 ## [0.2.0] - 2026-10-26
 
 ### Added
@@ -36,6 +46,7 @@ Add each user-visible change under Unreleased as it lands, in one of: Added, Cha
 - An SQLite event log per scope, with retention.
 - Packaging as an omp plugin, with a marketplace catalog; queued commands run on omp's own Bun.
 
-[Unreleased]: https://github.com/nledford/omp-coord/compare/v0.2.0...HEAD
+[Unreleased]: https://github.com/nledford/omp-coord/compare/v0.2.1...HEAD
+[0.2.1]: https://github.com/nledford/omp-coord/compare/v0.2.0...v0.2.1
 [0.2.0]: https://github.com/nledford/omp-coord/compare/v0.1.0...v0.2.0
 [0.1.0]: https://github.com/nledford/omp-coord/releases/tag/v0.1.0

package/README.md

@@ -1,5 +1,10 @@
 # omp-coord
 
+[![CI](https://github.com/nledford/omp-coord/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/nledford/omp-coord/actions/workflows/ci.yml)
+[![npm](https://img.shields.io/npm/v/@nledford/omp-coord)](https://www.npmjs.com/package/@nledford/omp-coord)
+[![omp](https://img.shields.io/badge/omp-%E2%89%A5%2018.12-blue)](https://github.com/can1357/oh-my-pi)
+[![License: MIT](https://img.shields.io/github/license/nledford/omp-coord)](LICENSE)
+
 An [omp](https://github.com/can1357/oh-my-pi) plugin, plus a small command-line runner, that lets several omp sessions on one machine, working in the same project, share one set of agent caps and build/test queues, and talk to each other.
 
 - **Shared agent caps.** Subagents count against pools (for example 8 `work` and 2 `short` slots) shared by every session in the project. A spawn over the cap is refused through omp's spawn check, so the cap does not depend on agents remembering to take and free slots.
@@ -16,7 +21,7 @@ Each session gets a letter and shows `coord B · work 5/8 · short 1/2` in omp's
 ## Quick start
 
 ```sh
-omp plugin install "git+ssh://git@github.com/nledford/omp-coord.git"
+omp plugin install @nledford/omp-coord
 ```
 
 Then put a `.omp-coord.json` in the project's top folder:
@@ -36,7 +41,7 @@ Every omp session started in that folder or below now shares 6 agent slots, and
 
 | | |
 |---|---|
-| [Install](docs/install.md) | Plugin install over SSH or the marketplace, updating, the `omp-coord` command. |
+| [Install](docs/install.md) | From npm, GitHub, the marketplace or GitHub Packages; updating; the `omp-coord` command. |
 | [Configuration](docs/configuration.md) | Every `.omp-coord.json` field. |
 | [Agent slots](docs/agent-slots.md) | How caps, the line, holds and nested agents work. |
 | [Queues](docs/queues.md) | `omp-coord run`, order, lanes, time limits, agents' commands. |

package/docs/install.md

@@ -2,43 +2,50 @@
 
 Requires omp 18.12 or later. No dependencies at runtime: the extension and the runner use the Bun built into omp.
 
-## From GitHub Packages
+## From npm
+
+```sh
+omp plugin install @nledford/omp-coord
+omp plugin install @nledford/omp-coord@0.2.0   # a given release
+```
+
+Releases are published to npmjs.com from the release workflow, with [provenance](https://docs.npmjs.com/generating-provenance-statements) that ties each package to the commit and workflow that built it (from 0.2.1 on). A machine set up for GitHub Packages (below) maps the `@nledford` scope to GitHub, so this command installs from there instead.
 
-Each release is published as the npm package `@nledford/omp-coord` to GitHub Packages. It is private like the repository, and GitHub Packages asks for a token even for public packages, so each machine needs one-time setup: a token that can read packages, and the `@nledford` scope pointed at GitHub's registry in `~/.npmrc`.
+## From GitHub
 
 ```sh
-gh auth refresh --scopes read:packages      # once: let the GitHub CLI's token read packages
-cat >> ~/.npmrc <<EOF
-@nledford:registry=https://npm.pkg.github.com
-//npm.pkg.github.com/:_authToken=$(gh auth token)
-EOF
+omp plugin install github:nledford/omp-coord
 ```
 
-Then install a release, or the newest one:
+Or through omp's marketplace, which this repository also serves:
 
 ```sh
-omp plugin install @nledford/omp-coord@0.2.0
-omp plugin install @nledford/omp-coord
+omp plugin marketplace add nledford/omp-coord
+omp plugin install omp-coord@omp-coord
 ```
 
-## From GitHub
+## From GitHub Packages
 
-Over SSH. The repository is private for now, and the `github:` shorthand and HTTPS URLs fail without credentials; `github:nledford/omp-coord` works once it is public:
+Each release is also published to GitHub Packages. GitHub Packages asks for a token to install any npm package, public ones included, so each machine needs one-time setup: a token that can read packages, and the `@nledford` scope pointed at GitHub's registry in `~/.npmrc`.
 
 ```sh
-omp plugin install "git+ssh://git@github.com/nledford/omp-coord.git"
+gh auth refresh --scopes read:packages      # once: let the GitHub CLI's token read packages
+cat >> ~/.npmrc <<EOF
+@nledford:registry=https://npm.pkg.github.com
+//npm.pkg.github.com/:_authToken=$(gh auth token)
+EOF
 ```
 
-Or through omp's marketplace, which this repository also serves:
+Then install a release, or the newest one:
 
 ```sh
-omp plugin marketplace add git@github.com:nledford/omp-coord.git
-omp plugin install omp-coord@omp-coord
+omp plugin install @nledford/omp-coord@0.2.0
+omp plugin install @nledford/omp-coord
 ```
 
 ## Updating
 
-`omp plugin upgrade @nledford/omp-coord` moves a package or git URL install to the newest release or commit; `omp plugin upgrade omp-coord@omp-coord` moves a marketplace install once a release has raised the catalog's version. Bun remembers the commit a git URL resolved to, so installing a git URL again can bring back an older commit; to pin a release over git, add its tag: `…/omp-coord.git#v0.2.0`. [CHANGELOG.md](../CHANGELOG.md) lists what each release changed.
+`omp plugin upgrade @nledford/omp-coord` moves a package or git install to the newest release or commit; `omp plugin upgrade omp-coord@omp-coord` moves a marketplace install once a release has raised the catalog's version. Bun remembers the commit a git install resolved to, so installing from git again can bring back an older commit; to pin a release, add its tag: `github:nledford/omp-coord#v0.2.0`. [CHANGELOG.md](../CHANGELOG.md) lists what each release changed.
 
 ## From a checkout
 

package/package.json

@@ -1,9 +1,6 @@
 {
   "name": "@nledford/omp-coord",
-  "version": "0.2.0",
-  "publishConfig": {
-    "registry": "https://npm.pkg.github.com"
-  },
+  "version": "0.2.1",
   "files": [
     "src",
     "docs",
@@ -16,7 +13,7 @@
   "author": "Nathaniel Ledford",
   "repository": {
     "type": "git",
-    "url": "https://github.com/nledford/omp-coord.git"
+    "url": "git+https://github.com/nledford/omp-coord.git"
   },
   "keywords": [
     "omp",

package/src/adapters/cli/cli.ts

@@ -14,7 +14,7 @@
  * 2 a usage or configuration error.
  */
 import { randomBytes } from "node:crypto";
-import { mkdirSync, readdirSync, readFileSync, statSync } from "node:fs";
+import { mkdirSync, readdirSync, statSync } from "node:fs";
 import { constants, userInfo } from "node:os";
 import { join } from "node:path";
 import { parseArgs } from "node:util";
@@ -24,6 +24,7 @@ import { EXIT_TIMED_OUT, runJob } from "../../app/job-runner.ts";
 import { type Config, ConfigError, findConfigFile, loadConfig } from "../../config.ts";
 import { MAX_PRIORITY } from "../../domain/queues.ts";
 import { osLoad } from "../os/load.ts";
+import { groupRunning } from "../os/process-group.ts";
 import { BoardStore, stateDir } from "../sqlite/store.ts";
 import { formatFindings, formatInterrupted, formatNotes, formatStats, formatStatus } from "../text/report.ts";
 import { startBeacon, unixLiveness } from "../unix/beacon.ts";
@@ -309,32 +310,6 @@ function signalNumber(signal: NodeJS.Signals): number {
   return constants.signals[signal] ?? 1;
 }
 
-/**
- * Whether process group `pgid` still has a member that has not exited. A signal to the group succeeds while it holds
- * only zombies, which is what an exited command's children become in a container whose first process never reaps
- * orphans; on Linux, /proc tells them apart. Elsewhere (macOS has no /proc; launchd reaps orphans) the signal decides.
- */
-function groupRunning(pgid: number): boolean {
-  try {
-    process.kill(-pgid, 0);
-  } catch {
-    return false;
-  }
-  if (process.platform !== "linux") return true;
-  for (const entry of readdirSync("/proc")) {
-    if (!/^\d+$/.test(entry)) continue;
-    try {
-      // /proc/<pid>/stat: "pid (comm) state ppid pgrp …"; comm may contain spaces and parentheses.
-      const stat = readFileSync(`/proc/${entry}/stat`, "utf8");
-      const [state, , pgrp] = stat.slice(stat.lastIndexOf(")") + 2).split(" ");
-      if (Number(pgrp) === pgid && state !== "Z") return true;
-    } catch {
-      // The process ended while being read.
-    }
-  }
-  return false;
-}
-
 if (import.meta.main) {
   try {
     process.exitCode = await main(Bun.argv.slice(2));

package/src/adapters/os/process-group.ts

@@ -0,0 +1,44 @@
+/**
+ * Whether a process group still has a member that has not exited, for stopping a timed-out job's whole group.
+ *
+ * A signal to the group succeeds while it holds only zombies, which is what an exited command's children become in a
+ * container whose first process never reaps orphans. On Linux, /proc tells them apart. Elsewhere (macOS has no /proc;
+ * launchd reaps orphans), or when /proc cannot be read, the signal decides.
+ */
+import { readdirSync, readFileSync } from "node:fs";
+
+/** The state and process group of a process, from the text of `/proc/<pid>/stat`. */
+export function parseProcStat(stat: string): { state: string; pgrp: number } | undefined {
+  // "pid (comm) state ppid pgrp …": comm may contain spaces and parentheses, so fields start after the last ")".
+  const close = stat.lastIndexOf(")");
+  if (close === -1) return undefined;
+  const [state, , pgrp] = stat.slice(close + 2).split(" ");
+  const group = Number(pgrp);
+  return state && Number.isInteger(group) ? { state, pgrp: group } : undefined;
+}
+
+export function groupRunning(pgid: number): boolean {
+  try {
+    process.kill(-pgid, 0);
+  } catch {
+    return false;
+  }
+  if (process.platform !== "linux") return true;
+  let pids: string[];
+  try {
+    pids = readdirSync("/proc").filter(entry => /^\d+$/.test(entry));
+  } catch {
+    return true;
+  }
+  for (const pid of pids) {
+    let stat: string;
+    try {
+      stat = readFileSync(`/proc/${pid}/stat`, "utf8");
+    } catch {
+      continue; // ended while being read, or hidden
+    }
+    const p = parseProcStat(stat);
+    if (p?.pgrp === pgid && p.state !== "Z") return true;
+  }
+  return false;
+}