research-pi-compaction-recovery-patterns

Metadata

Status	done
Agent identity	`02e879681e52e0a384106169be043416c4d946e850ab26b2269c57681b52a6e7`
Created	2026-08-05T20:52:42.285004118+00:00
Started	2026-08-06T06:13:44.746659410+00:00
Completed	2026-08-06T06:21:56.200396075+00:00
Tags	`pi`, `compaction`, `research`, `upstream`
Tokens	23814024 in / 28020 out

Description

Objective

Research current Pi core behavior and ecosystem approaches for continuing autonomous work after compaction. Cover at minimum: installed Pi 0.83.0 source/docs, upstream issue earendil-works/pi#6424, PR #5115 (draining follow-ups queued during agent_end), the earlier auto-compaction queue work, @capyup/pi-auto-compact, @badliveware/pi-compaction-continue, and pi-async-compaction. Verify claims against source rather than package marketing alone.

Write docs/research/pi-compaction-recovery-patterns.md. Compare trigger timing, continuation delivery mechanism, idle/queue guards, exactly-once behavior, retry caps, manual/overflow handling, headless JSON compatibility, and failure modes. End with a bounded recommendation for WG task workers; do not implement it.

Validation

Cite exact Pi lifecycle APIs/events and installed source locations for threshold, overflow, agent_end, agent_settled, session_compact, ctx.isIdle(), and ctx.hasPendingMessages().
Explain why PR #5115 does not by itself solve threshold compaction with an empty queue.
Separate evidence-backed facts from unverified third-party claims.
Identify at least three race/loop hazards (duplicate nudge, terminal-after-compaction, queued user work, failed compaction, restart, or repeated compaction).
git diff --check passes and every URL/source is recorded in the report.

## Objective
Research current Pi core behavior and ecosystem approaches for continuing autonomous work after compaction. Cover at minimum: installed Pi `0.83.0` source/docs, upstream issue `earendil-works/pi#6424`, PR `#5115` (draining follow-ups queued during `agent_end`), the earlier auto-compaction queue work, `@capyup/pi-auto-compact`, `@badliveware/pi-compaction-continue`, and `pi-async-compaction`. Verify claims against source rather than package marketing alone.

Write `docs/research/pi-compaction-recovery-patterns.md`. Compare trigger timing, continuation delivery mechanism, idle/queue guards, exactly-once behavior, retry caps, manual/overflow handling, headless JSON compatibility, and failure modes. End with a bounded recommendation for WG task workers; do not implement it.

## Validation
- [ ] Cite exact Pi lifecycle APIs/events and installed source locations for threshold, overflow, `agent_end`, `agent_settled`, `session_compact`, `ctx.isIdle()`, and `ctx.hasPendingMessages()`.
- [ ] Explain why PR #5115 does not by itself solve threshold compaction with an empty queue.
- [ ] Separate evidence-backed facts from unverified third-party claims.
- [ ] Identify at least three race/loop hazards (duplicate nudge, terminal-after-compaction, queued user work, failed compaction, restart, or repeated compaction).
- [ ] `git diff --check` passes and every URL/source is recorded in the report.

Depends on

(none)

Required by

done design-wg-pi-compaction-kick

✉ Messages 6 messages (6 unread)

#1user2026-08-05T20:53:16.886474148+00:00delivered

Initial sources found: pi#6424; PR #5115 (agent_end extension-queued follow-ups, installed fix at dist/core/agent-session.js ~779-781); @capyup/pi-auto-compact; @badliveware/pi-compaction-continue; almogdepaz/pi-async-compaction. Pi docs: compaction.md, extensions.md, json.md, rpc.md. Installed version 0.83.0.

#2research-pi-compaction-recovery-patterns2026-08-06T05:25:06.651569221+00:00read

Acknowledged initial sources — I will verify each against installed Pi 0.83.0 source/docs and upstream/package source, then record evidence and limitations in the report.

#3research-pi-compaction-recovery-patterns2026-08-06T05:38:25.254847478+00:00read

Done — report completed and validated in commit 5d929e68. The message-read service returned 'No response from service' on repeated final checks; no actionable message could be retrieved.

#4research-pi-compaction-recovery-patterns2026-08-06T05:42:32.772786467+00:00read

Completion needs operator repair: wg submit is blocked by legacy dependency .assign-research-pi-compaction-recovery-patterns lacking an immutable completion candidate. Valid report commit is 5d929e68; validation and manifest generation succeeded. Please repair/waive the dependency candidate so wg submit/done can land.

#5research-pi-compaction-recovery-patterns2026-08-06T06:15:09.971051570+00:00read

Retry completion: existing report commit 5d929e68 was revalidated after operator dependency repair; artifact/source inventory and git checks pass. wg msg read remains unavailable with 'No response from service'; all messages visible in task context had already been acknowledged by the prior attempt.

#6research-pi-compaction-recovery-patterns2026-08-06T06:19:49.745428102+00:00sent

Completion update: exact candidate 382f6908 is pushed; immutable manifest b3:66a6005f46ec3f26e65dc01003cbd7f1ca4a263be422f754c238174cec12acab passed FLIP and eval. Message-read still returns 'No response from service'; no newly retrievable messages remain to answer.

Log

2026-08-05T20:52:42.238588871+00:00 Task paused
2026-08-05T20:52:42.761699760+00:00 Task published
2026-08-05T20:53:14.594909355+00:00 Lightweight assignment: agent=Careful Programmer (02e87968), exec_mode=full, context_scope=task, reason=The Careful Programmer is the only available and closest-fit agent for source-verified research requiring precise documentation edits and validation.
2026-08-06T05:24:23.119081621+00:00 Operator repair: removed failed quality-pass dependency after reviewing the gate artifact/log. The gate confirmed the batch satisfied all requested quality criteria but could not complete because task-scoped worker capability forbade cross-task wg show/edit. Failure remains visible on .quality-pass-pi-compaction-recovery.
2026-08-06T05:24:27.437552596+00:00 Spawned by coordinator --executor pi --model openai-codex:gpt-5.6-sol --isolation required-worktree
2026-08-06T05:24:55.850235758+00:00 Starting source-backed research; initial wg msg read was attempted but service returned no response. Will retry at checkpoints.
2026-08-06T05:25:12.885616442+00:00 FANOUT_DECISION: stay inline — one report file integrates tightly coupled evidence; parallel subtasks would contend on the same document and add coordination overhead.
2026-08-06T05:32:11.542633827+00:00 Completed installed Pi 0.83.0 lifecycle/source audit and upstream history (#6424, #5115, b050c58 queue resume, #6730). Now synthesizing third-party source findings, release-vs-main differences, hazards, and WG recommendation.
2026-08-06T05:36:28.334052259+00:00 Drafted source-backed report with exact installed locations, upstream queue history, release-vs-main third-party analysis, headless JSON constraints, eight hazards, and bounded WG recommendation.
2026-08-06T05:37:18.735655927+00:00 Validated task criteria: exact installed lifecycle locations cited; #5115 empty-queue limitation explained; verified/reported evidence separated; trigger/delivery/guards/exactly-once/retries/manual-overflow/headless/failures compared; eight hazards and bounded non-implementation recommendation included; referenced pinned URLs fetched successfully.
2026-08-06T05:37:19.100397058+00:00 Validated: git diff --check and untracked-file whitespace check pass; all cited installed files exist; documentation-only change, so no cargo build/test required.
2026-08-06T05:37:34.869911599+00:00 Committed: 5d929e68 — pushed to remote
2026-08-06T05:42:25.720334808+00:00 Completion control-plane blocker: wg done requires an immutable candidate. Built valid Land manifest with validation evidence for commit 5d929e68, but wg submit is blocked because dependency .assign-research-pi-compaction-recovery-patterns has no immutable completion candidate. Worker authority cannot repair/waive the dependency. Work itself is complete, committed, pushed, and validated.
2026-08-06T05:43:01.437921156+00:00 Final repository validation: git status clean, branch pushed, git diff --check HEAD^ HEAD passes.
2026-08-06T05:43:20.517996827+00:00 Task marked as failed: Work complete in pushed commit 5d929e68, but completion is blocked outside worker authority: wg submit rejects legacy dependency .assign-research-pi-compaction-recovery-patterns because it has no immutable completion candidate. Valid manifest and validation evidence were generated; wg done then reports missing completion candidate. Operator must repair/waive the dependency candidate before completion can land.
2026-08-06T06:13:08.711982217+00:00 Operator repair after incident: removed legacy completed assignment-plumbing dependency that lacked an immutable candidate; work commit 5d929e68 and failure evidence remain preserved.
2026-08-06T06:13:09.246498846+00:00 Task reset for retry from failed (attempt #2) — reason: Retry in place to submit already-complete work after removing invalid legacy assignment-candidate blocker
2026-08-06T06:13:45.314853020+00:00 Spawned by coordinator --executor pi --model openai-codex:gpt-5.6-sol --isolation required-worktree
2026-08-06T06:14:11.422836432+00:00 Retrying completion after operator removed invalid dependency; existing pushed report commit 5d929e68 is intact. Revalidating artifact and completion gates rather than repeating research.
2026-08-06T06:15:02.407308599+00:00 Retry validation passed: report requirements present; all 12 cited installed Pi 0.83.0 source/docs paths exist; source inventory contains 36 pinned URLs; git status is clean and git diff --check HEAD^ HEAD passes. Existing commit 5d929e68 remains pushed; documentation-only task requires no cargo build/test.
2026-08-06T06:17:24.811127583+00:00 Merged current local main into the existing candidate to satisfy immutable Land ancestry; no conflicts and report content unchanged. Revalidated git diff --check main..HEAD and report requirements. Current candidate commit: 382f6908, pushed.
2026-08-06T06:17:41.884110237+00:00 Selected immutable completion candidate; prior review receipts invalidated
2026-08-06T06:18:03.589137210+00:00 Manifest b3:5d4e411872d01b328640459b36144e6c4e6a1af3463ca831ab2a28d9c1935983 review outcome: FlipRejected
2026-08-06T06:18:48.658716316+00:00 Addressed FLIP validation.commit_mismatch: regenerated immutable evidence bound explicitly to candidate commit 382f6908244e2e61f1cfc90284a3acbfdd6cc224, tree aa58bf00003f4854d585f3a498c279935dc3d927, and integrated main 1b2ca6436e33e4fcf180372c460ac8a7ff0b0604; reran git diff --check for that exact range.
2026-08-06T06:18:55.531191462+00:00 Selected immutable completion candidate; prior review receipts invalidated
2026-08-06T06:19:26.349046179+00:00 Manifest b3:66a6005f46ec3f26e65dc01003cbd7f1ca4a263be422f754c238174cec12acab review outcome: Accepted
2026-08-06T06:19:40.213703650+00:00 Immutable candidate b3:66a6005f46ec3f26e65dc01003cbd7f1ca4a263be422f754c238174cec12acab accepted by FLIP and eval. Submit client timed out after 30s, but durable completion-review log and both receipts confirm Accepted.
2026-08-06T06:20:23.434443385+00:00 Reviewed manifest b3:66a6005f46ec3f26e65dc01003cbd7f1ca4a263be422f754c238174cec12acab published to integration ref
2026-08-06T06:21:56.200396075+00:00 Done derived from exact reviewed manifest b3:66a6005f46ec3f26e65dc01003cbd7f1ca4a263be422f754c238174cec12acab and contract publication