Skip to content

Clarify cleanup restart continuations#828

Merged
chubes4 merged 1 commit into
mainfrom
issue-826-cleanup-continuation-output
Jun 27, 2026
Merged

Clarify cleanup restart continuations#828
chubes4 merged 1 commit into
mainfrom
issue-826-cleanup-continuation-output

Conversation

@chubes4

@chubes4 chubes4 commented Jun 27, 2026

Copy link
Copy Markdown
Member

Summary

  • Add explicit continuation evidence when cleanup intentionally restarts a stage from offset 0 after changing the candidate set.
  • Include a human-readable reason, mutation progress delta, and next command label so the restart does not look like a loop.
  • Extend the abandoned cleanup orchestrator smoke test to cover the output contract.

Fixes #826

Tests

  • php tests/smoke-abandoned-cleanup-orchestrator.php
  • php tests/smoke-cleanup-eligible-drain.php
  • php tests/bounded-cleanup-processed-candidates.php
  • php tests/cleanup-remaining-work-summary.php
  • php tests/workspace-compact-output.php
  • php -l inc/Workspace/WorkspaceAbandonedCleanupOrchestrator.php
  • php -l tests/smoke-abandoned-cleanup-orchestrator.php

AI assistance

  • AI assistance: Yes
  • Tool(s): openai/gpt-5.5 via OpenCode
  • Used for: Implementing the cleanup continuation output change, updating focused tests, and running verification.

@chubes4 chubes4 merged commit e54e784 into main Jun 27, 2026
4 of 5 checks passed
@chubes4 chubes4 deleted the issue-826-cleanup-continuation-output branch June 27, 2026 02:16
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.

cleanup continuation should not look like it is looping at offset zero

1 participant