chore: add production templates (CI/CD, Docker, K8s, n8n, LangGraph)

[Copilot]

Adds production-ready deployment templates, integration API skeleton with provider adapters, n8n workflows, and infrastructure manifests to enable deployment and automation orchestration.

Changes

CI/CD & Infrastructure

• .github/workflows/ci.yml - Lint, test, build pipeline
• .github/workflows/cd-staging.yml - Automated staging deployment
• docker-compose.prod.yml - Multi-container production stack
• .env.prod.example - Production environment template
• k8s/langgraph-deployment.yaml - Kubernetes deployment with health checks
• k8s/hpa.yaml - Horizontal pod autoscaling (2-10 replicas, 70% CPU target)

Integration API (FastAPI)

• integration/api/server.py - Core API with /health, /ready, /v1/graph/run endpoints
• integration/api/providers/kiro_provider.py - kiro.ai webhook adapter
• integration/api/providers/lindy_provider.py - lindy.ai webhook adapter
• integration/api/routes/integrations.py - Provider routing and health checks
• integration/api/Dockerfile - Multi-stage Python 3.11 image

n8n Workflows

• n8n/workflows/main_orchestrator.json - Entry webhook → LangGraph trigger
• n8n/workflows/langgraph_trigger.json - HTTP request to integration API
• n8n/credentials/credentials_template.json - API key placeholders
• n8n/README.md - Import and configuration instructions

Documentation

• docs/deployment.md - Docker Compose, Kubernetes deployment steps with example commands
• docs/observability.md - Prometheus metrics, health check endpoints
• docs/runbook.md - Troubleshooting common deployment issues
• docs/integrations.md - Provider setup (kiro.ai, lindy.ai) with curl examples

Project Configuration

• requirements.txt - FastAPI 0.109.1, uvicorn, testing dependencies
• pyproject.toml - PEP 621 metadata, Black/mypy/pytest config
• .gitignore - Excludes __pycache__, .env, build artifacts
• README.md - Added deployment templates notice

Next Steps

1. Configure .env.prod with actual credentials
2. Add GitHub secrets: GHCR_TOKEN, KUBECONFIG
3. Import n8n workflows from n8n/workflows/
4. Deploy via docker-compose -f docker-compose.prod.yml up or kubectl apply -f k8s/

Security

Fixed FastAPI ReDoS vulnerability (CVE): Updated from 0.109.0 to 0.109.1 across all dependency files.

---

Note: Contains placeholder values (TODO markers) for secrets and organization-specific configuration. PR left as draft pending credential setup.

Original prompt

Create a draft pull request on a new branch prod-templates that adds production-ready templates, CI/CD, infrastructure manifests, n8n workflows, an integration API skeleton, provider adapters (kiro.ai, lindy.ai), and documentation to the Stacey77/Rag7 repository. Target base branch: main.

Files to add (templates/stubs with TODOs for secrets or project-specific values):

1. CI and CD workflows

• .github/workflows/ci.yml
• .github/workflows/cd-staging.yml

2. Environment and Docker

• .env.prod.example
• docker-compose.prod.yml

3. Kubernetes manifests

• k8s/langgraph-deployment.yaml
• k8s/hpa.yaml

4. Documentation

• docs/deployment.md
• docs/observability.md
• docs/runbook.md
• docs/integrations.md

5. n8n sample workflows

• n8n/workflows/main_orchestrator.json
• n8n/workflows/langgraph_trigger.json
• n8n/credentials/credentials_template.json
• n8n/README.md

6. Integration API skeleton

• integration/api/Dockerfile
• integration/api/server.py (FastAPI skeleton: /health, /ready, /v1/graph/run)
• integration/api/requirements.txt
• integration/api/providers/kiro_provider.py
• integration/api/providers/lindy_provider.py
• integration/api/routes/integrations.py

7. Project metadata

• requirements.txt
• pyproject.toml

Additional requirements:

• Update README.md with a short notice about new deployment templates (do not otherwise change existing content).
• Leave PR as draft if any secrets placeholders remain.
• Do not assign reviewers.
• PR body must include motivation, list of files added, and next steps: update .env.prod, add GHCR token & kubeconfig secrets, import n8n workflows, run docker-compose or deploy to k8s.

Ensure files are syntactically valid and include basic working templates, health endpoints, and example curl commands in docs. Commit all files on branch prod-templates and open a draft PR titled: "chore: add production templates (CI/CD, Docker, K8s, n8n, LangGraph)" against main.

Do not modify files outside adding the notice to README.md. Leave TODOs and placeholders where credentials or organization-specific values are required.

Success criteria:

• Draft PR opened against main with all files added
• Files syntactically valid (YAML/JSON/Python)
• Docs provide clear next steps for configuration and deployment

This pull request was created as a result of the following prompt from Copilot chat.

Create a draft pull request on a new branch prod-templates that adds production-ready templates, CI/CD, infrastructure manifests, n8n workflows, an integration API skeleton, provider adapters (kiro.ai, lindy.ai), and documentation to the Stacey77/Rag7 repository. Target base branch: main.

Files to add (templates/stubs with TODOs for secrets or project-specific values):

1. CI and CD workflows

• .github/workflows/ci.yml
• .github/workflows/cd-staging.yml

2. Environment and Docker

• .env.prod.example
• docker-compose.prod.yml

3. Kubernetes manifests

• k8s/langgraph-deployment.yaml
• k8s/hpa.yaml

4. Documentation

• docs/deployment.md
• docs/observability.md
• docs/runbook.md
• docs/integrations.md

5. n8n sample workflows

• n8n/workflows/main_orchestrator.json
• n8n/workflows/langgraph_trigger.json
• n8n/credentials/credentials_template.json
• n8n/README.md

6. Integration API skeleton

• integration/api/Dockerfile
• integration/api/server.py (FastAPI skeleton: /health, /ready, /v1/graph/run)
• integration/api/requirements.txt
• integration/api/providers/kiro_provider.py
• integration/api/providers/lindy_provider.py
• integration/api/routes/integrations.py

7. Project metadata

• requirements.txt
• pyproject.toml

Additional requirements:

• Update README.md with a short notice about new deployment templates (do not otherwise change existing content).
• Leave PR as draft if any secrets placeholders remain.
• Do not assign reviewers.
• PR body must include motivation, list of files added, and next steps: update .env.prod, add GHCR token & kubeconfig secrets, import n8n workflows, run docker-compose or deploy to k8s.

Ensure files are syntactically valid and include basic working templates, health endpoints, and example curl commands in docs. Commit all files on branch prod-templates and open a draft PR titled: "chore: add production templates (CI/CD, Docker, K8s, n8n, LangGraph)" against main.

Do not modify files outside adding the notice to README.md. Leave TODOs and placeholders where credentials or organization-specific values are required.

Success criteria:

• Draft PR opened against main with all files added
• Files syntactically valid (YAML/JSON/Python)
• Docs provide clear next steps for configuration and deployment

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.