v5.0.1

Every worker now sets conduit_queue_depth for its own connector's work, dead letter and quarantine queues, visible and in flight, with the same labels conduit ops uses, so a Prometheus scrape of a worker shows queue depth as the v5.0.0 notes claimed.
The gauge is refreshed after a poll at most once every 10 seconds, three GetQueueAttributes calls per refresh, and those calls are counted in the run's SQS requests.
A unit test drives an idle worker against a stubbed SQS client to prove the gauge is set and the interval is respected, and a LocalStack test scrapes a running worker's /metrics endpoint and sees dead letters and a quarantined payload appear after they are enqueued.
The browser demo now plans 8 resources for a new connector, including module.queue.aws_sqs_queue.quarantine, and 26 for the shipped base stack, matching the real Terraform plan, and its dead letter lab sends a malformed record to the quarantine queue rather than the DLQ.
Tests are 168 unit and 31 LocalStack plus terraform, and the web self check runs 44 assertions.