stephan
107cdabe8d
Add complete update mechanism for client-side updates: - backend/update.py: Core update logic (check, apply, rollback, status/logs) - backend/app.py: REST API endpoints (GET /update/status, POST /update/check, POST /update/apply, POST /update/rollback, GET /update/logs) - backend/models.py: Pydantic models for update API responses - backend/settings.py: Update config (status/log file paths) - scripts/rollback_client.sh: Rollback script for failed updates - scripts/update_client.sh: Enhanced update client script - CLAUDE.md: Documentation for future Claude Code instances Complete US_000026-028 and TASK_000027-029: - US_000026: Client pulls updates from remote service - US_000027: Client verifies and applies updates atomically - US_000028: Client reports update status to backend All endpoints require authentication. Updates run asynchronously. Documentation updated per SOP (CHANGELOG, PROJECT_STATUS, stories/tasks). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
22 lines
567 B
Markdown
22 lines
567 B
Markdown
ID: TASK_000029 | Version: 0.1.0 | Status: Done
|
|
By: Codex (GPT-5)
|
|
|
|
# TASK_000029: Report update status
|
|
|
|
## Outcome
|
|
Client meldet Update-Status mit Version und Fehlerbild.
|
|
|
|
## Story-Bezug
|
|
US_000028
|
|
|
|
## Beschreibung
|
|
- Status-Schema definieren (Version, Ergebnis, Fehler, Zeitpunkt).
|
|
- Transportweg festlegen (z.B. HTTP POST oder Log-Export).
|
|
- Erfolg/Fehler konsistent dokumentieren.
|
|
- Schema dokumentiert in `docs/update-status.md`.
|
|
|
|
## Definition of Done (DoD)
|
|
- Status-Schema dokumentiert.
|
|
- Uebertragungspfad beschrieben.
|
|
- Erfolg/Fehler werden eindeutig gemeldet.
|