A node's worker label is worker, so a device is only a paired one

- NodeDef `device`/`device_policy` become `worker`/`worker_policy`, the
  issue `ignored_device` becomes `ignored_worker`, and the SDK's `@node`
  takes `worker=` and `worker_policy=`
- FlowStore._migrate renames the keys in published and draft documents
  once, bumping their version; a queued run's `needs` reads the old key
- placement passes the label as `label`, client regenerated
- docs: worker placement wording, MCP issuer without DOMAIN, device rows in
  the CLI data directory and the API table, device links in compose comments

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/interface/dashboards.md

@@ -322,10 +322,10 @@ face, and the editor marks it **Poor fit for round**.
 | Gesture | Effect |
 |---|---|
 | Swipe left / right | next / previous face of this dashboard; stops at either end |
-| Swipe up / down | next / previous dashboard of the panel (`/panel/{id}` only); stops at either end |
+| Swipe up / down | next / previous dashboard of the device (`/panel/{id}` only); stops at either end |
 | Page dot | that face |
 | PageDown / PageUp | next / previous face |
-| Shift+PageDown / Shift+PageUp | next / previous dashboard of the panel |
+| Shift+PageDown / Shift+PageUp | next / previous dashboard of the device |
 | Arrow keys | turn the ring, not the page |
 
 A swipe carries the page with the finger ([Swiping](#swiping)); a drag that
@@ -423,7 +423,7 @@ angle, which is what the browser's reveal amounts to.
 
 ### Swiping
 
-Faces are swiped sideways and a panel's dashboards up and down, with the page
+Faces are swiped sideways and a device's dashboards up and down, with the page
 under the finger, as a tile view moves.
 
 | Part | Value |

docs/interface/flow-editor.md

@@ -68,7 +68,7 @@ yielding regularly can run longer than its timeout. Empty or `0` means no
 limit, the default.
 
 **Resources** selects a shared worker pool, a named flavor or custom CPU,
-memory and GPU requirements. Placement by `device` and `device_policy` is
+memory and GPU requirements. Placement by `worker` and `worker_policy` is
 configured through the API or flow JSON; see [Remote workers](../code/workers.md).
 
 ### Code and reuse

docs/interface/portal.md

@@ -92,7 +92,7 @@ proxy on that route must support WebSockets.
   the portal to be online. It also deletes the users the portal let in; the
   account that enrolled and every superuser stay.
 - To replace the pairing, use **Connect with a new code**. Remote users and
-  panels may need to pair again.
+  devices paired through the portal may need to pair again.
 
 If the instance is removed at the portal, or its code is renewed there, the
 status reads **Removed at the portal** and the instance stops dialling. Connect