Skip to content

fix: preserve idle tasks during explicit account maintenance - #34

Merged
SergioTCG merged 2 commits into
mainfrom
fix/account-maintenance
Oct 17, 2026
Merged

SergioTCG merged 2 commits into
mainfrom
fix/account-maintenance

Conversation

@SergioTCG

@SergioTCG SergioTCG commented Oct 17, 2026 •

Copy link
Copy Markdown
Owner

Scope

Fix the three account-maintenance holds without releasing unfinished work or terminating automation-created conversations.

  • Exact, idempotent release of completed automation bootstrap ownership retains external-key receipt, session, channel, collaborators and late-prompt deduplication.
  • Explicit local-owner idle Claude task maintenance uses full-journal checkpoints, stable native idle/process-tree proof, mutation fences and restart recovery without replay.
  • Pending reply deliveries block maintenance; fresh PID/tmux liveness is required for release; proved preflight rejection cannot strand an untouched task.
  • Canonical resume-argument comparison tolerates obsolete legacy display fragments without accepting real settings changes.
  • Ordinary bulk updates, automatic rotation and running/dormant reserved work remain excluded. No manifest change.

Validation and review

Complete AGENTS.md suite passed: npm ci, audit (zero vulnerabilities), 707 tests, documentation/branding, JavaScript syntax, Pi offline models, ShellCheck. Isolated managed Pi smoke passed. Automated read-only review completed; all three concrete findings were accepted, fixed and regression-tested. No speculative expansion.

Controlled maintenance

After exact-head CI, roll the existing daemon only, then migrate exactly three owner-requested Claude sessions. Preserve task journals, settings, native/channel identities and whitelists; verify unrelated provider PIDs/tmux names. Private backups and rollback/account-maintenance-20261017 retain the previous live commit. Restore shadow mode after migration; no automatic rotation activation.

@SergioTCG

Copy link
Copy Markdown
Owner Author

Automated read-only review completed. All three concrete findings are accepted and fixed: pending reply text/file/failure delivery now blocks checkpoints; released automation receipts still deduplicate delayed bootstrap echoes; ownership release requires fresh PID and tmux liveness despite cached ancestry. Added regression coverage for each. Also reject dormant reserved-task maintenance and distinguish a proved preflight rejection from an uncertain restart so untouched work is not stranded behind a recovery fence. No broader refactor or automatic-rotation expansion. Final complete validation and exact-head CI must pass before controlled merge/roll.

@SergioTCG
SergioTCG merged commit fb87357 into main Oct 17, 2026
3 checks passed
@SergioTCG

Copy link
Copy Markdown
Owner Author

Controlled canary completed on the merged commit fb87357. Exactly three requested Claude account handovers committed with verified target identity. Completed bootstrap ownership was released without stopping or unbinding its retained channel. Both reported task journals, including gates, reports and work generations, are byte-for-byte unchanged. All 31 previously live providers remain live; unrelated PIDs/tmux names, native/channel identities, settings and whitelists are unchanged. Configuration was restored byte-for-byte to shadow monitoring mode and the single daemon rolled again successfully. Automatic rotation remains disabled. No manifest change or extra provider/channel launch.

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.

2 participants