Upgrade to 1.0.0-rc879

Concerns: pushword/core, pushword/page-scanner, pushword/static-generator

Contents

queued is a new status

Only with background_task_handler: messenger. A generation or scan dispatched but not yet picked up by a consumer was reported as completed — by the admin screens and by the status field of GET /api/static/{host} and GET /api/page-scan. It now reports queued.

Affected: any client polling those endpoints. Treat queued like running — the pass has not started, keep waiting. POST on both endpoints now answers with the real starting status too, so a client learns it is queued without polling.

Route a command to its own transport

Optional. Every background task shares one message class, so one transport serves them first-come and a mass sweep can queue in front of an interactive task. Name a transport per command to give it its own lane — see Background Tasks.

pushword:
    background_task_transports:
        'pw:static': static