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	113ecdfa77	feat: Package 4 Rechtliche Texte — DB-Persistenz fuer Legal Documents, Einwilligungen und Cookie Banner 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 46s Details CI / test-python-backend-compliance (push) Successful in 32s Details CI / test-python-document-crawler (push) Successful in 22s Details CI / test-python-dsms-gateway (push) Successful in 17s Details - Migration 007: compliance_legal_documents, _versions, _approvals (Approval-Workflow) - Migration 008: compliance_einwilligungen_catalog, _company, _cookies, _consents - Backend: legal_document_routes.py (11 Endpoints + draft→review→approved→published Workflow) - Backend: einwilligungen_routes.py (10 Endpoints inkl. Stats, Pagination, Revoke) - Frontend: /api/admin/consent/[[...path]] Catch-All-Proxy fuer Legal Documents - Frontend: catalog/consent/cookie-banner routes von In-Memory auf DB-Proxy umgestellt - Frontend: einwilligungen/page.tsx + cookie-banner/page.tsx laden jetzt via API (kein Mock) - Tests: 44/44 pass (test_legal_document_routes.py + test_einwilligungen_routes.py) - Deploy-Scripts: apply_legal_docs_migration.sh + apply_einwilligungen_migration.sh Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-03-03 08:25:13 +01:00

2 Commits