Audit remediation: security hardening and phase gates

[fraware]

Summary

• Harden security posture: exec-safe subprocesses, metrics bearer auth, fail-closed Redis budget/rate limits, authenticated Redis in compose, and patch path deny policy.
• Complete service implementations for Freestyle all-pass quorum, static analysis analyzers, fuzzing runners, attestation stores, Lean no-sorry/proof discovery, and Morph HTTP unification.
• Wire Temporal heal-loop SHA tracking, Phase 3 optional gates/observability, soak/cost harnesses, expanded CI matrix, and dependency overrides for known vulnerable transitives.

Test plan

• pnpm install --frozen-lockfile
• pnpm --filter @self-healing-ci/exec-safe test
• pnpm --filter @self-healing-ci/temporal-worker test
• pnpm --filter @self-healing-ci/github-app test
• Confirm Redis requires REDIS_PASSWORD via docker-compose
• Confirm metrics routes reject requests without METRICS_AUTH_TOKEN
• Review CI matrix on this PR

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[gitguardian]

⚠️ GitGuardian has uncovered 2 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
34880974	Triggered	Generic Password	f9c599b	docker-compose.yml	View secret
34880974	Triggered	Generic Password	f9c599b	docker-compose.yml	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.}