You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(core): record a backup_done activity row when a run completes (#160)
## Summary
- New `backup_done` Info activity row written at the all-ops-succeeded
point of a cycle (same site as `deep_verify_done`), with `file_count` =
files uploaded (bundles count their members via `exec_progress_from`)
and `bytes` = bytes uploaded.
- Scoping mirrors #149's scan rows: ALWAYS for a manual Run Now (the
feed now reads scan started -> scan complete -> uploads -> Backup
complete, even when nothing needed uploading), scheduled ticks only when
the run actually executed ops - idle 10-minute ticks add no noise.
- A run with failed ops writes no completion row (it defers the
timestamp advance and stays due for retry; claiming completion would be
a lie).
- The summary/telemetry aggregates filter to
`upload_done`/`bundle_upload`, so this byte-carrying row cannot
double-count.
- Locale: `activity.events.backup_done` = "Backup complete".
## Testing
- 3 new orchestrator tests: totals on a worked scheduled cycle;
idle-scheduled quiet but manual-with-nothing logs 0/0; failed ops
suppress the row.
- `cargo test -p driven-core --lib` 359/359; clippy clean; label vitest
+ prettier + eslint green.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01JLB3E2Jm7knNJd37fVpH8X
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
0 commit comments