Deliver final advanced governance, ownership, and reporting feature set

[Suhaskumard]

Motivation

• Provide a final, integrated set of governance and research features so the platform can evaluate and act on commit risk with configurable merge policies and ownership analysis.
• Surface explainable heuristic risk scores and provide front-end views for managers/researchers to inspect policy decisions and blast-radius impacts.
• Offer simple CSV reporting and an API catalog so teams can wire the service into CI/policy workflows and research experiments.

Description

• Added backend endpoints for governance, simulation, ownership, analytics, research and reporting including GET/PUT /api/merge-gate/policy, GET /api/merge-gate/evaluate/{commit_id}, POST /api/predict/what-if, POST /api/webhooks/github/commit, GET /api/ownership/blast-radius/{commit_id}, GET /api/reports/semester, and retained analytics endpoints such as GET /api/dashboard/summary and GET /api/analytics/failure-trends (backend/app/main.py, backend/app/*).
• Implemented deterministic heuristic scoring with risk_engine.py, added Pydantic schemas in schemas.py, and seeded demo data and dependency graph in data.py to support explainability and API responses.
• Extended the frontend with new pages and components: Ownership Lab, Merge Control Center, Commits list, Commit Deep Dive, Dashboard, Manager/Research/Admin/CI views, Navbar and KpiCard, plus an API helper getJson and layout/styles to wire the UI to the new endpoints (frontend/app/*, frontend/components/*, frontend/lib/api.ts).
• Added supporting artifacts including AI-engine stub (ai-engine/risk_model.py), PostgreSQL-ready schema (database/schema.sql), docs (docs/api-catalog.md, docs/architecture.md, docs/roadmap.md), an updated README.md, and a GitHub Actions CI workflow (.github/workflows/ci.yml).

Testing

• Ran python -m compileall backend/app which completed successfully and validated Python source syntax in backend/app.
• Attempted a Playwright screenshot of the new /merge-control page which failed with ERR_EMPTY_RESPONSE because the frontend server was not running in this environment, so UI rendering and end-to-end checks could not be validated.
• CI workflow (.github/workflows/ci.yml) was added to run backend syntax checks and a frontend npm build, but the workflow was not executed in this environment.

---

Codex Task