Prepare AWS Chaos Engineering Framework 2.0.2

[fusiontechstrategies]

Summary

• prepare version 2.0.2 as a distribution and release-integrity patch
• add an exact standalone runtime, normalized wheel, normalized source distribution, SPDX 2.3 SBOM, checksums, and release evidence
• pin direct runtime, development, and build inputs, including direct Botocore declaration
• add Linux, Windows, macOS, reproducibility, isolated-install, archive, and release-identity gates
• add tag-only automation that can create only a draft GitHub release

Safety impact

• no live AWS behavior is added or broadened
• plan mode remains the default
• all validation is offline with EC2 metadata access disabled
• no AWS credentials or account access were used
• the release workflow has no manual trigger, publication command, or registry upload

Local validation

• 101 tests plus 4 parameterized subtests passed on Python 3.10.21, 3.12.10, and 3.14.7
• 52.59% coverage passed the enforced 50% gate on all three versions
• two Python 3.12 builds and independent Python 3.10 and 3.14 builds produced the same six assets byte for byte
• wheel and source distributions installed independently and matched source bytes
• Ruff, Bandit, pip check, three dependency audits, Twine, Actionlint, YAML, markdownlint, relative-link, and ASCII-punctuation gates passed
• staged and full-history Gitleaks reported zero findings
• Trivy reported zero high or critical vulnerabilities, misconfigurations, secrets, or SBOM findings
• repository code-scanning, Dependabot, and secret-scanning alert counts were zero before submission

Release boundary

This pull request does not create a tag or release. A later tag must point to an approved GitHub-verified protected-main commit. Tag automation can create only a draft for separate maintainer review.