v1.10.0

Studio 1.10.0

Upgrade impact: No action required. Workers keep working on the fleet shared secret; the
new enrollment path is opt in. SHS_MAX_UPLOAD_SIZE_MB defaults to 1024 and only refuses
what was already too large to store.

Components: api 1.8.0, ui 1.5.1, workers 1.11.0, console 1.9.1 (unchanged).

New

• Workers can enroll with their own revocable credential. A super admin mints a
  single-use join token scoped to named queues, the worker exchanges it once for its own
  credential, and that credential bounds which queues the worker may claim. Revoking one
  credential cuts off one machine and leaves the rest of the fleet alone.
• A worker from outside the deployment waits for approval. Registering with the shared
  secret from a machine that is not part of the deployment files a pending request instead
  of joining. Approve or reject it under Infrastructure > Workers; approving hands that
  worker its own credential.
• Refused credential requests are recorded. Every refusal in the worker credential gate
  writes an access-denied audit event naming the worker, the job and the reason.

Fixed

• Wait for Webhook parks the run and resumes on the callback, instead of occupying a
  worker while it waits.
• Uploads are bounded. The API refuses a request body over SHS_MAX_UPLOAD_SIZE_MB with
  a 413 naming the limit.
• Files with the same name keep their own bytes. Library uploads are stored under their
  resource id, replacing a file writes the new file beside the old one so copies that share
  it are untouched, and deleting a step's copy leaves the library file in place.
• Storage totals count every file under an organization's folder.
• Stale worker rows clear once a deregistered worker passes the retention window.
• Open notification sockets stop holding a database connection for the life of the socket.
• The worker enrollment panels refresh with the Infrastructure page, so a new pending
  request appears without reloading the browser.

Catalog

• shs/core 1.0.1: the Wait for Webhook step runs inline in the API.
• Provider docs: the YouTube token check uses the OAuth Playground, and the super-admin doc
  carries the upload size row.