ci(sdk-python): trigger CI on main branch and restore badge to main

Adding main to the push trigger ensures a workflow run exists on main
after each merge, so the shields.io badge can resolve a real status
instead of showing "no status".

Author: Fabien83560

.github/workflows/ci.yml

@@ -2,7 +2,7 @@ name: CI
 
 on:
   push:
-    branches: [dev]
+    branches: [main, dev]
   pull_request:
     branches: [main, dev]
 

README.md

@@ -3,7 +3,7 @@
 **API observability & intelligence for FastAPI/Starlette — local-first, privacy-first.**
 
 [![PyPI version](https://img.shields.io/pypi/v/apiforgepy?color=0066FF)](https://pypi.org/project/apiforgepy/)
-[![CI](https://img.shields.io/github/actions/workflow/status/APIForge-Organisation/sdk-python/ci.yml?branch=dev&label=CI)](https://github.com/APIForge-Organisation/sdk-python/actions)
+[![CI](https://img.shields.io/github/actions/workflow/status/APIForge-Organisation/sdk-python/ci.yml?branch=main&label=CI)](https://github.com/APIForge-Organisation/sdk-python/actions)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green)](LICENSE)
 [![Python](https://img.shields.io/badge/python-%3E%3D3.11-brightgreen)](https://python.org)