feat(deploy): add Helm chart and Kubernetes guide [BACKLOG]

[however-yir]

Problem

Docker Compose is useful for local evaluation, but production-oriented users need a Kubernetes deployment path with explicit configuration and operational defaults.

Status: BACKLOG

Not implementing in current cycle. Requires:

• Cluster access for testing
• Secrets management strategy (external-secrets vs sealed-secrets)
• Ingress controller selection
• Resource limits profiling from production metrics

Deferred until

• Production deployment targets are confirmed
• Observability stack (Tempo/Grafana) integration is finalized
• Multi-tenant isolation model is documented

Original scope

• Add a minimal Helm chart for the application and frontend.
• Document external dependencies for MySQL, Redis/RabbitMQ, pgvector, and observability.
• Provide secure configuration guidance for secrets and tenant settings.

Acceptance criteria

• Helm chart renders with default values.
• Kubernetes guide is added under docs/.
• Deployment notes include secrets, probes, resources, and rollback guidance.

[however-yir]

Update: Deferred — scope exceeds current implementation capacity

Helm chart and Kubernetes deployment guide were evaluated but deferred for the following reasons:

• Production Kubernetes deployment requires cluster-specific decisions (ingress controller, cert management, secrets backend) that vary significantly across organizations
• Docker Compose deployment is functional and covers local evaluation and staging needs
• A generic Helm chart risks being either too opinionated or too bare to be useful

Recommendation: Revisit when a target Kubernetes environment is identified. The existing docs/deployment-enterprise.md covers production deployment guidance at the Docker/systemd level.

Keeping this issue open for future work.