v1.0.0: Stable Selfhosted Release

[DeepZone]

Motivation

• Finalize the v0.9.2-rc line into a stable v1.0.0 release while preserving the read-only routing safety model and avoiding any new features or DB migrations.
• Clean and align visible versioning across backend, API, and frontend UI so runtime consumers and docs show a single authoritative v1.0.0 value.
• Remove stale pre-release wording in public docs and ensure runtime strings are English-only for production UX consistency.

Description

• Bumped package/app versions to 1.0.0 and API-visible strings to v1.0.0 (backend pyproject.toml, backend/app/main.py, backend/app/api/routes_system.py, backend/app/core/system_status.py, and frontend/package.json).
• Reworked frontend version sourcing: Layout now accepts appVersion (passed from system?.version) and displays it with a fallback of v1.0.0, and hardcoded v0.9.2-rc strings were removed from App.tsx, Layout.tsx and the About view.
• Documentation cleanup and release framing: updated README.md (badges and "Current Release" text), rewrote ROADMAP.md for a release-oriented structure, added top section to RELEASE_NOTES.md for v1.0.0, and updated operations docs (docs/operations/security.md, upgrades.md, release-checklist.md, troubleshooting.md).
• English-only verification: translated remaining German runtime strings in backend runtime code paths (services and core evaluation/recommendation outputs) without changing business logic, and updated one test expectation to match the new visible version.
• Ensured no private/local IPs were introduced; verified frontend/vite.config.ts uses VITE_API_PROXY_TARGET with a safe default of http://backend:8000.

Testing

• Ran backend unit tests: cd backend && pytest -q produced a green run (102 passed, multiple non-blocking warnings).
• Built frontend artifacts: cd frontend && npm run build completed successfully and produced a production build.
• Ran upgrade/deployment helpers: python backend/scripts/check_upgrade_path.py failed in this environment due to a local alembic upgrade head subprocess error, and python backend/scripts/check_deployment_health.py --base-url http://localhost:8000 --check-setup failed due to the backend not running in this session.
• Performed static/runtime scans to confirm version replacements, no committed private/local IP addresses, and that appVersion is injected into the UI with a v1.0.0 fallback.

---

Codex Task