wildcrane-runner 0.6.2 → 0.6.4

package/README.md

@@ -30,12 +30,16 @@ names, and falls back to the previous one if the new one does not start.
   once a day the Runner removes a project unused for 7 days or no longer in your account — its
   whole `cache/<project>/`, or only a linked folder's `.akb/` — unless a job runs there, a
   delivery is paused there, or its last sync failed.
-- **Runner files**: `~/.wildcrane/bin/` holds the downloaded versions and the `akb` shim.
+- **Runner files**: `~/.wildcrane/bin/` holds the downloaded versions and the `akb` shims.
 - **Periodic agents**: in each project folder it also runs the board's own agents (reflect,
   describe-project, review-dismissals, prune-memory) and each workflow's scheduled agents, when
   due by this computer's clock — on your runtime, so they use its quota.
-- **akb**: tasks started from WildCrane run akb's workflows with the copy of `akb` the Runner
-  carries (`dist/akb/`), on whichever of those the task's runtime names.
+- **akb**: tasks started from WildCrane run akb's workflows, on whichever of those the task's
+  runtime names, with the version WildCrane names, else the copy the Runner carries (`dist/akb/`).
+  Each registration may name a new one: it downloads from npm in the background to
+  `~/.wildcrane/bin/akb/<version>/`, and takes over at the next task step once its contract matches
+  and it answers `--version`. One that fails is never tried again (`bin/akb/state.json`); a version
+  not chosen for 7 days is removed. No npmjs access means staying on the version in use.
 
 ## Development