Update Armnet organization references

README.md

@@ -25,6 +25,9 @@ no auth setup, no Docker.** Pick a task, paste (or select) a policy repo id, pre
 - **Auto-scored** per-rollout success from the instrumented BusyBox — no human
   judges, and the scene resets itself between rollouts.
 - **Shared**: everyone who opens the Space follows the same eval in real time.
+- **Queue-aware**: while the cell is busy, submitters can queue another
+  20-rollout eval. The public queue is capped at 10 jobs and shows policy repo
+  IDs only for Armnet eval images; unrelated jobs appear as `other job`.
 - **Leaderboard**: every run is recorded and pooled by policy repo + revision,
   ranked by the 95% lower-bound success rate (so more rollouts only help a
   genuinely good policy — spamming evals can't game it).
@@ -39,8 +42,12 @@ environment when it routes a job.
 
 | Task | Slug | Dataset | Reference policy |
 | --- | --- | --- | --- |
-| Push the green button | `push_green_button` | [`villekuosmanen/busybox_push_green_button`](https://huggingface.co/datasets/villekuosmanen/busybox_push_green_button) | [`…_push_green_button_diffusion`](https://huggingface.co/villekuosmanen/busybox_push_green_button_diffusion) |
-| Flip left switch off | `busybox_left_toggle_down` | [`villekuosmanen/busybox_flip_left_switch_off`](https://huggingface.co/datasets/villekuosmanen/busybox_flip_left_switch_off) | [`…_flip_left_switch_off_diffusion`](https://huggingface.co/villekuosmanen/busybox_flip_left_switch_off_diffusion) |
+| Push the green button | `push_green_button` | [`armnet/busybox_push_green_button`](https://huggingface.co/datasets/armnet/busybox_push_green_button) | [`…_push_green_button_diffusion`](https://huggingface.co/armnet/busybox_push_green_button_diffusion) |
+| Flip left switch off | `busybox_left_toggle_down` | [`armnet/busybox_flip_left_switch_off`](https://huggingface.co/datasets/armnet/busybox_flip_left_switch_off) | [`…_flip_left_switch_off_diffusion`](https://huggingface.co/armnet/busybox_flip_left_switch_off_diffusion) |
+
+Either task-specific dataset can be replaced with
+[`armnet/busybox_multitask`](https://huggingface.co/datasets/armnet/busybox_multitask)
+for language-conditioned multi-task training.
 
 Adding a third is one entry in `TASKS` in `config.py`. The only hard requirement
 is that it **resets itself** — a task needing a human to tidy up between rollouts
@@ -50,7 +57,7 @@ can't be run unattended by the public.
 
 Gradio has no built-in database and a Space's disk is ephemeral, so the
 leaderboard is stored in a Hugging Face **dataset** repo (`ARMNET_DEMO_LEADERBOARD_REPO`,
-default `villekuosmanen/armnet-demo-leaderboard`): one JSONL line per completed
+default `armnet/armnet-demo-leaderboard`): one JSONL line per completed
 run, reloaded on restart. Reads are public; **writing new runs needs `HF_TOKEN`**
 (the same token used to pull gated policies).
 
@@ -71,7 +78,9 @@ submission endpoint is planned so external users can submit without that token.
 1. The Space submits a job to the armnet orchestrator (baked-in demo API key)
    naming only the embodiment (`lerobot/so-101`) and the selected task's slug,
    passing the policy repo id as a job arg (`use_rerun=True` turns on the video
-   feed). No cell is named in the submission — the task is what routes it.
+   feed). No cell is named in the submission — the task is what routes it. If
+   the cell is occupied, the job waits in the shared queue and the Space adopts
+   it for live display when the scheduler dispatches it.
 2. The orchestrator resolves that task to its **environment** (`busybox`) and
    routes the job to a cell assigned that environment. Cells are assigned an
    environment in the FMS, not a task, and serve every task within it — so if no
@@ -95,7 +104,8 @@ Set these in **Settings → Variables and secrets**:
 | `ARMNET_API_KEY` | **yes** | Orchestrator API key for the demo (a low-privilege throwaway key). Provided as a secret — nothing is baked into the repo. |
 | `HF_TOKEN` | recommended | The Space stores it once as a named orchestrator secret (`ARMNET_DEMO_HF_SECRET_NAME`, default `hf_token`) under the demo user and the eval references it as `$HF_TOKEN` to pull a gated policy; it also authenticates leaderboard writes. Without it the leaderboard is read-only and gated policies won't load. |
 | `ARMNET_DEMO_N_EPISODES` | no | Rollouts per run (default 20). |
-| `ARMNET_DEMO_LEADERBOARD_REPO` | no | HF dataset repo backing the leaderboard (default `villekuosmanen/armnet-demo-leaderboard`). |
+| `ARMNET_DEMO_MAX_QUEUED_JOBS` | no | Fleet-wide queued-job cap shown and enforced by the Space (default 10). |
+| `ARMNET_DEMO_LEADERBOARD_REPO` | no | HF dataset repo backing the leaderboard (default `armnet/armnet-demo-leaderboard`). |
 | `ARMNET_DEMO_CELL_LABEL` | no | Name shown next to the availability light (default `Cell 1`). |
 | `ARMNET_DEMO_CELL_STATUS_POLL_S` | no | How often the shared availability lights refresh (default 5s). One process-wide poll per task, not per viewer. |
 | `DEBUG_ARMNET_ORCHESTRATOR_URI` | no | Override the orchestrator URL (default: the one compiled into `armnet-client`). |
@@ -136,8 +146,8 @@ Space. Because the tag is a hash of the build context, a commit that leaves the
 eval runtime alone resolves to an image that already exists, so the build is
 skipped and the Space is left running exactly what it was.
 
-It needs two repo settings: an `ARMNET_DEMO_SPACE_ID` variable holding
-`<owner>/<space>`, and an `HF_TOKEN` secret with write access to it.
+The workflow targets `armnet/armnet-eval` and needs the repository's `HF_TOKEN`
+secret to have write access to that Space.
 
 To do it by hand — to test a change before it lands on `main`, say: