KSPM public evidence only

This archive contains 10 sanitized result files, this guide and a hash manifest.
It contains no source code, credentials or raw private captures.
The complete reproducible source is in kspm-controller-security-lab.zip.

Published source commit: 7678f84c8f63ef391f894a06ca39e60c49916787
https://github.com/j-dahl7/kspm-controller-security-lab/commit/7678f84c8f63ef391f894a06ca39e60c49916787

Start with results/run2-post-rollout-evidence.json for the October 9 result.
The registry finding retained its assessment/resource identity while naming a
verified post-rollout pod. The root-filesystem finding was absent from complete
ARM/ARG exports, its previous address returned 404, and the portal had no match.
No explicit Healthy or resolved root-filesystem record was observed.

results/review-addendum-facts.json records the 32-export/33-sighting audit,
timing bounds and retained zero-replica ReplicaSet. Repeated sightings are not
distinct findings. The isolated single-pod service test was inconclusive; run 2
did not perform scaling or post-hardening replacement. Secure Score was not measured.

The result files are dated snapshots. Pre-publication review flags in the
October 9 verification record describe that earlier review, not current
publication status. Later operational and cleanup outcomes have their own dates.
Literal pod names are replaced by documented aliases; private source hashes
remain intact. Hashes detect byte changes, not independent provider authenticity.

Both owned resource groups were verified absent on October 12 at 14:49:51 UTC.
This later teardown is separate from the October 8-9 Defender observations.
No subscription reactivation, billing change or cluster restart was performed.
The USD 50 allowance was not an Azure-enforced cap or a measured final invoice.
