Skip to content

feat: prune work-summary update history, keep 3 backups (1.6.0) - #247

Merged
Ponpon55837 merged 2 commits into
mainfrom
feat/prune-summary-history-1.6.0
Oct 16, 2026
Merged

Ponpon55837 merged 2 commits into
mainfrom
feat/prune-summary-history-1.6.0

Conversation

@Ponpon55837

Copy link
Copy Markdown
Owner

Summary

  • Empty previous/resulting work-summary JSON of session_work_summary_updates rows older than 7 days (API server start + hourly). Request and row are kept, so idempotency conflicts still work. No migration (schema stays 30), no VACUUM.
  • Replay of a pruned key returns work_summary_updated with duplicate: true and the current work summary (no previousWorkSummary) instead of not_found.
  • Backup retention (manual / automatic / session-deletion) is now 3.
  • Docs, CHANGELOG, docs/releases/1.6.0.md, version bump to 1.6.0.

Test

lint, format, typecheck, storage/server/mcp tests pass (one Windows-only symlink EPERM test fails locally, unrelated).

🤖 Generated with Claude Code

…6.0)

Empty previous/resulting work summaries of session_work_summary_updates rows older than 7 days (server startup + hourly), replay pruned idempotency keys from the current work summary, lower backup retention to 3, bump to 1.6.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Ponpon55837
Ponpon55837 enabled auto-merge October 16, 2026 02:08
…scrolls

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Ponpon55837
Ponpon55837 merged commit 0673d5d into main Oct 16, 2026
4 checks passed
@Ponpon55837
Ponpon55837 deleted the feat/prune-summary-history-1.6.0 branch October 16, 2026 05:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant