v0.6.0: strengthen backup integrity

README.md

@@ -18,7 +18,9 @@ For a practical step-by-step manual with recommended backup workflows, recovery
 - Dry-run mode for planning large backups.
 - Filters for favorites, media type, date, estimated size, and excluded albums.
 - Failure tracking with `failures.jsonl` and `retry-failed`.
+- Deduplicated failure management with `failures list`, `failures clear`, and `retry-failed --clear-on-success`.
 - Verification, reporting, and diff commands for backup integrity.
+- Status command for quick backup summaries.
 - Script-friendly exit codes and optional JSON summaries.
 - 100% test coverage for the Go CLI and parsing layers.
 
@@ -219,6 +221,26 @@ photoscli retry-failed --out ./backup
 
 This is useful after transient iCloud or network failures.
 
+Use `--clear-on-success` to remove successfully retried assets from `failures.jsonl`.
+
+### `failures`
+
+Lists or clears deduplicated failure records.
+
+```bash
+photoscli failures list --out ./backup
+photoscli failures clear --out ./backup
+```
+
+### `status`
+
+Shows a quick backup summary.
+
+```bash
+photoscli status --out ./backup --manifest sqlite
+photoscli status --out ./backup --manifest sqlite --json
+```
+
 ## Export Flags
 
 Common flags for `export` and `backup-all`:
@@ -297,7 +319,7 @@ Logged events include session start/end, completed exports, skipped assets, and
 
 ## Failure Tracking
 
-Failed exports are appended to:
+Failed exports are deduplicated by asset ID and stored in:
 
 ```text
 failures.jsonl
@@ -309,6 +331,12 @@ Retry them with:
 photoscli retry-failed --out ./backup
 ```
 
+Clear successful retries automatically:
+
+```bash
+photoscli retry-failed --out ./backup --clear-on-success
+```
+
 Use `--retry N` during normal exports to handle transient iCloud or network failures automatically.
 
 ## Configuration File