breakpilot-compliance

Author	SHA1	Message	Date
Sharang Parnerkar	8ec8af4c2d	chore: remove all gitea remote references; single origin push only Some checks failed Build + Deploy / build-admin-compliance (push) Failing after 45s Details Build + Deploy / build-backend-compliance (push) Successful in 13s Details Build + Deploy / build-ai-sdk (push) Successful in 40s Details Build + Deploy / build-developer-portal (push) Successful in 12s Details Build + Deploy / build-tts (push) Successful in 11s Details Build + Deploy / build-document-crawler (push) Successful in 14s Details Build + Deploy / build-dsms-gateway (push) Successful in 12s Details Build + Deploy / trigger-orca (push) Has been skipped Details CI/CD / loc-budget (push) Successful in 21s Details CI/CD / guardrail-integrity (push) Has been skipped Details CI/CD / go-lint (push) Has been skipped Details CI/CD / python-lint (push) Has been skipped Details CI/CD / nodejs-lint (push) Has been skipped Details CI/CD / test-go-ai-compliance (push) Successful in 48s Details CI/CD / test-python-backend-compliance (push) Failing after 38s Details CI/CD / test-python-document-crawler (push) Successful in 31s Details CI/CD / test-python-dsms-gateway (push) Successful in 27s Details CI/CD / sbom-scan (push) Has been skipped Details CI/CD / validate-canonical-controls (push) Successful in 19s Details There is only one remote (origin). Removed all occurrences of: - git push gitea / git push origin main && git push gitea main - "Pushing to gitea (external)" in deploy.sh - # gitea: git@gitea.meghsakha.com:... remote comment in docs-src/index.md - "Push auf gitea triggert" → "Push auf origin triggert" in docs - Clone URL updated to ssh://git@coolify.meghsakha.com:22222/... in README.md and CONTRIBUTING.md Web UI URLs (gitea.meghsakha.com/...) are unchanged — those are still valid. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-04-19 16:16:12 +02:00
Benjamin Admin	393eab6acd	feat: Package 4 Nachbesserungen — History-Tracking, Pagination, Frontend-Fixes All checks were successful CI / go-lint (push) Has been skipped Details CI / python-lint (push) Has been skipped Details CI / nodejs-lint (push) Has been skipped Details CI / test-go-ai-compliance (push) Successful in 36s Details CI / test-python-backend-compliance (push) Successful in 31s Details CI / test-python-document-crawler (push) Successful in 23s Details CI / test-python-dsms-gateway (push) Successful in 18s Details Backend: - Migration 009: compliance_einwilligungen_consent_history Tabelle - EinwilligungenConsentHistoryDB Modell (consent_id, action, version, ip, ua, source) - _record_history() Helper: automatisch bei POST /consents (granted) + PUT /revoke (revoked) - GET /consents/{id}/history Endpoint (vor revoke platziert für korrektes Routing) - GET /consents: history-Array pro Eintrag (inline Sub-Query) - 5 neue Tests (TestConsentHistoryTracking) — 32/32 bestanden Frontend: - consent/route.ts: limit+offset aus Frontend-Request weitergeleitet, total-Feld ergänzt - Neuer Proxy consent/[id]/history/route.ts für GET /consents/{id}/history - page.tsx: globalStats state + loadStats() (Backend /consents/stats für globale Zahlen) - page.tsx: Stats-Kacheln auf globalStats umgestellt (nicht mehr page-relativ) - page.tsx: history-Mapper: created_at→timestamp, consent_version→version - page.tsx: loadStats() bei Mount + nach Revoke Dokumentation: - Developer Portal: neue API-Docs-Seite /api/einwilligungen (Consent + Legal Docs + Cookie Banner) - developer-portal/app/api/page.tsx: Consent Management Abschnitt - MkDocs: History-Endpoint, Pagination-Abschnitt, History-Tracking Abschnitt - Deploy-Skript: scripts/apply_consent_history_migration.sh Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-03-03 11:54:25 +01:00

2 Commits