feat: safe-improvements → main — Render deployment, CI/CD fixes, workflows

[romanchaa997]

Summary

Merges all improvements from safe-improvements branch into main.

Changes included:

• ✅ Working Render deployment (audityzer.onrender.com — status: ok, v1.1.3)
• ✅ Fixed Dockerfile (single-stage Node 20 Alpine, health check, dumb-init)
• ✅ Restored and fixed all GitHub Actions workflows (23 files)
• ✅ Added workflow_dispatch to CodeQL workflow
• ✅ Fixed CI/CD pipeline (ci-fast, codeql, audityzer-security, deploy-railway)
• ✅ Added outreach templates for DeFi/Web3 protocols
• ✅ render.yaml configured for auto-deploy
• ✅ server.js with /health endpoint

Deploy

• Live: https://audityzer.onrender.com
• Health: https://audityzer.onrender.com/health

Note: Merge conflicts exist — manual resolution required after PR creation.

---

Summary by cubic

Stabilizes multi‑target deploys (Render, Railway, and Kubernetes via DOCR + ArgoCD), hardens CI/security gates, and ships a FastAPI audit/report API that stores PDFs in MinIO plus the React Native app. Also fully removes submodules, adds security‑headers and conflict‑resolve workflows, fixes audityzer.io DNS, sets CNAME for audityzer.com, updates web/mobile deps, and adds monitoring, social publishing, and a Perplexity SoT registry.

• CI/CD & Infra

  • Deploys: Render + Railway + K8s (DOCR images, ArgoCD sync) with TLS, nginx rate limits, Prometheus scrape; DOCR build/push workflow.
  • Workflows: fast CI; CodeQL with manual trigger; Slither/Foundry scans + weekly Optimism scan; health/SSL monitors; security‑headers; social auto‑publish; DNS automations (fix audityzer.io, generic adder); S3 build backups; merge‑conflict resolver jobs.
  • Repo/ops: complete submodule removal and .gitmodules drop; hardened .dockerignore; single‑stage Node 20 Alpine Dockerfile (non‑root + dumb-init); simplified docker-compose (API + MinIO + Prometheus + Grafana); CNAME for audityzer.com; updated issue templates and Code of Conduct.

• Features & Docs

  • FastAPI service: /api/v1/audit, /api/v1/report, /health; async fixes and input caps; PDF reports via report.py with explicit MinIO creds; e2e results and secrets setup docs.
  • Apps & agents: React Native app; parallel analysis agent pipeline; IoT seismic anomaly detector; CI plugins for GitHub/GitLab/CircleCI/Jenkins; Perplexity SoT registry and ADR; GTM, domain runbook, productization roadmap, and execution summary.
  • Deps: bump @solidjs/start to 1.3.2, vite to 8.x, axios to 1.15.0, aiohttp to 3.13.4.

^{Written for commit e926a01. Summary will update on new commits. Review in cubic}

[romanchaa997]

PR Review — #153: feat: safe-improvements → main

Status: Open — mega PR merging safe-improvements into main (86 commits)

Scope: This is the primary integration PR aggregating all the recent work: Render deployment, CI/CD fixes, GitHub Actions workflow overhauls, API improvements, and various infrastructure changes.

Key observations:

• 86 commits — this is a very large batch merge. Many of the individual PRs (fix(ci): fix YAML syntax error in ci-cd-clean.yml - add run: to Notif… #167-Refactor audit logic and improve fix(api): fix async blocking - use a… #173, docs: add AuditorSEC TRL-4 block + BRAVE1 roadmap table + dual-use #156, etc.) are sub-PRs that feed into safe-improvements first
• This PR is referenced by most of the other open PRs in this list
• 54 conversation comments indicate active discussion

Blockers to watch before merging to main:

1. All sub-PRs targeting safe-improvements should be merged first (PRs fix(ci): fix YAML syntax error in ci-cd-clean.yml - add run: to Notif… #167-Refactor audit logic and improve fix(api): fix async blocking - use a… #173)
2. The merge conflicts in safe-improvements branch (e.g., from Refactor audit logic and improve fix(api): fix async blocking - use a… #173, fix: sync netlify.toml with main to resolve merge conflict #170) need to be resolved
3. CI checks need to pass on safe-improvements before this can merge to main
4. Protected ref restrictions on main need to be satisfied

Recommendation: This PR should be the last to merge, after all the smaller safe-improvements targeting PRs are resolved. Prioritize fixing the blocked PRs (#172, #171, #169, #168) and resolving merge conflicts (#173, #170) before attempting to merge this into main.