Broader deployment guide + security hardening beyond the MVP (post-MVP)

Context

Post-MVP residual workstream under Epic #11730. Epic #11720's Sub F1 #11727 realigns DeploymentCookbook.md + the deployment-relevant guide tree as needed for the MVP. Discussion #11718 + the #11720 lost-item audit noted there is broader stale-guide content + deployment security-hardening work beyond what the MVP strictly needs.

Gating Condition

Pursued post-MVP, for the stale-guide + security-hardening parts NOT already required by #11720 — Sub F1 #11727 owns the MVP-needed realignment; this workstream owns the remainder. Until then: captured intent, not active work.

Scope

• Stale deployment-guide content outside the #11720 MVP path.
• Deployment security hardening beyond the MVP baseline — e.g. broader reverse-proxy / auth hardening, secret-management depth, network-policy tightening, container-image hardening.

Acceptance Criteria

• Non-MVP stale deployment-guide content is identified + realigned, or explicitly deferred with rationale.
• A deployment security-hardening review beyond the MVP baseline is recorded, with findings either actioned or ticketed.

Out of Scope

• The #11720 MVP-needed guide realignment — owned by Sub F1 #11727.
• MVP-baseline deployment security (reverse-proxy / auth-proxy wiring, etc.) — owned by #11720.

Related

• Parent: #11730 (Post-MVP Residual Workstreams)
• Complements: #11727 (Sub F1 — MVP-needed guide realignment)
• Origin Discussion: #11718

Origin Session ID

8e1dc8ca-b5a5-4479-b3cf-31918eb4a5b2