chore: v2.8.16 — Oh My Pi login sharing: a pane's key is listed before it starts

omp's gateway re-reads its clients file only every 10 s, and an omp that
starts while its key is refused fails model discovery once and hangs for
good. omp-share.js now keeps four keys queued in the clients file (hashes
only; the keys in <data dir>/omp-share/tokens.json, 0600): a new pane takes
one already listed (AGENTHUB_OMP_KEY), a fresh one joins the queue, and a
gone pane's key leaves at the next sync.

server/lib/pty-run.js

@@ -490,13 +490,12 @@ function spawnRun(args) {
       : null;
   const paneCred = require("./auth").newPaneToken();
   // A member's omp on the host's shared omp login (omp-share.js): its
-  // models.yml points at the loopback gateway, keyed by this pane's token.
+  // models.yml points at the loopback gateway, with a key already listed there.
   const ompShare =
     tool === "omp"
       ? require("./omp-share").forSpawn(
           require("./run-as").accountForLane(laneId),
-          runIdForLane(laneId, slot),
-          paneCred?.hash
+          runIdForLane(laneId, slot)
         )
       : null;
   if (forkSession === true) {