Skip to content

fix: bound emergency cleanup task results - #981

Merged
chubes4 merged 1 commit into
mainfrom
fix/980-bounded-emergency-cleanup-results
Jul 29, 2026
Merged

fix: bound emergency cleanup task results#981
chubes4 merged 1 commit into
mainfrom
fix/980-bounded-emergency-cleanup-results

Conversation

@chubes4

@chubes4 chubes4 commented Jul 28, 2026

Copy link
Copy Markdown
Member

Closes #980.

Summary

  • Project recurring emergency-cleanup logs and completed job results to bounded operational evidence instead of persisting full candidate plans.
  • Preserve trigger reasons, selected and scheduled counts/IDs, planned and measured recovery totals, action-required evidence, and compact capacity snapshots.
  • Keep full reports unchanged for explicit workspace ability and CLI callers.

Verification

  • php tests/workspace-disk-emergency-cleanup-durable-result.php
    • 4+ MiB fixture; log context: 970 bytes; completed result: 906 bytes; both enforced at <= 8,192 bytes.
  • PHP lint passed for inc/Tasks/WorkspaceDiskEmergencyCleanupTask.php and tests/*.php.
  • Full suite passed except two pre-existing standalone/environment failures: artifact-cleanup-live-process-guards.php requires Linux /proc process scanning, and worktree-cleanup-patch-equivalence.php lacks its GitCheckout bootstrap dependency.

AI Assistance

AI assistance disclosure: openai/gpt-5.6-sol using OpenCode implemented and tested the bounded result change. Chris remains responsible for every line.

@chubes4
chubes4 merged commit 77035cd into main Jul 29, 2026
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.

Emergency cleanup task persists megabyte reports in every log and job

1 participant