[jeffreyaven]

Bring the merged quantum-safe signing migration and v0.13 verification notice back into dev so the normal feature -> dev (development registry) -> main (production registry) flow contains the same implementation. dev is an ancestor of main with no unique commits; no provider source files differ. Direct fast-forward is prohibited by branch protection, so use a merge commit through this PR, preserving signing/v0.1.0-alpha01 and existing history. No provider artifacts should be published by this code-only sync. Provider publication still requires the forthcoming v0.13 binary. No force push or protection bypass.

[gitguardian]

⚠️ GitGuardian has uncovered 6 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
38381033	Triggered	Generic High Entropy Secret	9e727c4	providers/src/lambda/v00.00.00000/services/instances.yaml	View secret
38381034	Triggered	Generic High Entropy Secret	9e727c4	providers/src/lambda/v00.00.00000/services/audit.yaml	View secret
36408823	Triggered	Azure SAS URL	bf3e324	providers/src/github/v00.00.00000/services/repos.yaml	View secret
38381035	Triggered	Generic High Entropy Secret	9e727c4	providers/src/lambda/v00.00.00000/services/audit.yaml	View secret
6108696	Triggered	RSA Private Key	41c8be1	providers/src/cloudflare/v00.00.00000/services/custom_certificates.yaml	View secret
36408824	Triggered	Azure SAS URL	bf3e324	providers/src/github/v00.00.00000/services/repos.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[jeffreyaven]

All build, signing, corpus audit, AOT/regression and CodeQL checks passed. The main-to-dev sync is currently held because GitGuardian reports six findings while scanning 46 historical commits included in the sync. No provider source files differ between the two branch tips. I am not overriding the failed security check or rewriting published/tagged history. The GitGuardian findings need triage before this sync can safely merge.