Ship an executable local Docker topology for the capacity suite

[rmcdaniel]

Problem

Capacity suite v1 declares a reproducible local-docker-amd64-v1 infrastructure profile, but the public benchmark surface does not include a topology or launcher that creates it. The collector requires callers to supply nine pre-existing container identities through CAPACITY_CONTAINER_*. The profile names images and CPU/memory limits, but does not provision or fully verify Server configuration, database and Redis configuration, networking, storage, architecture, kernel/container-engine identity, or the SDK worker and load-generator environment.

As a result, a first-time operator cannot recreate the standard local profile from the versioned suite inputs, and materially different environments can be labeled with the same infrastructure profile identity.

Acceptance criteria

• Provide a source-controlled launcher or Compose-equivalent topology for every component in local-docker-amd64-v1, with exact images, resource limits, networking, storage, and required Server/database/Redis configuration.
• Build or install the pinned PHP, Python, and Rust adapters and start their declared worker/client roles without manual container assembly.
• Pass resolved container identities to the collector automatically and support deterministic cleanup.
• Derive and verify the runtime attributes carried by the profile identity, including architecture, container engine/runtime policy, database and Redis versions/configuration, and durable storage assumptions; fail closed on drift.
• Add a bounded no-provider-spend smoke path that provisions the profile, executes a representative cell, emits a non-publishable qualified result, and tears the topology down.

Delete when

Delete when a clean supported host can reproduce the documented bounded local benchmark from versioned repository inputs alone and a mismatched runtime cannot claim the standard profile identity.