Ptah Operator 0.2.6 qualification evidence

The reviewed public evidence for the production qualification of Ptah Operator v0.2.6 under the frozen 0.2.0 profile (revision 48 targets). The acceptance record that cites it is support/acceptance/0.2.0.json on master (#242, #584).

The archive holds identities, verdicts, aggregate measurements and assessments:

• release/: the release manifest, checksums, attestation and cosign verification, the read-back comparison with the qualified draft, and the release scan with its exposure analysis.
• functional/: the 54-cell coverage audits of CI runs 39753549451 (linux/amd64) and 39753553357 (linux/arm64), with every cell's job ID and log hash.
• installation/: the published guide run fresh, with the monitoring deployment check, and over v0.2.5 on both architectures, and the two upgrade runs a probe defect refused (#706).
• capacity/: soak, backlog and overload at the support window's edges, each judged on exact manager API demand from per-request audit on all three API servers, with the completeness check, the driver summary, the demand while the API servers restarted after each measurement (#657), and the scripts that computed them.
• shipped-clients/: the four signed kubectl-ptah assets reading a real plan, schema and migration on measured labs.
• recovery/: the nine recovery cells on the published v0.2.6, Recovery cells runs 39916446006 and 39929447531 (the second ran the two cells the first lost to a probe defect, #708).
• profile/ and acceptance/: the frozen profile and the record itself.

Raw labs, kubeconfigs, keys, audit archives, encrypted recovery evidence and unsanitized logs are not here. They are stored age-encrypted on the evidence host, and their custody records are part of the acceptance record's evidence.

Verify: download every asset, then run sha256sum -c SHA256SUMS. index.json lists each member's size and SHA-256.