Repository navigation
eve#559: a solo verify run removes the Chief of Staff sessions it creates - #563
Merged
Merged
Conversation
A solo --only run left the Chief of Staff bootstrap session: its prompt carries no run token, so the token sweep skipped it. The end of a stack run now sweeps the slot's own project folders (exact encoded run-dir plus an existing slot directory), waiting on the Claude's exit through the reaper. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
… stack dir Review round 1. The slot prefixes are now verify-cos and the world projects only; a folder under a longer-named sibling directory (x1-world) is not ours; nothing is deleted unless the stack file sits in a directory named for its slot with the marker it names; a session's own <id>/ folder goes with its file. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Owner
Author
|
merge-check: approved, target, verified, contract, evidence, owner, weakening pass; ci NA. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #559
A solo
--onlystack run now removes the Chief of Staff's startup session and the project folder it made; before, a solo run onmainleft 3 entries (folder,memory/, a.jsonl) in 2 of 2 runs. The startup prompt carries no run token, so the token sweep never matched it; a full run was clean only because later sessions in the same folder carried the token. At the end of a stack run, every session file in the slot's own project folders goes, and a file whose Claude still runs is handed to the existing detached reaper.Fix attempts: 1 plus two review rounds (round 1 found a blocking sibling-slot match, fixed). Tokens: ~105k dev agent round 1, ~190k across two reviewers.
Ownership rule (deliberate): a folder is the slot's only if its name is the slot's encoded
verify-cosor a project dir under itsworld, and no longer-named sibling slot claims it. While a sibling slot likex1-worldexists,x1's ownworldproject folder stays (ambiguous). The README says so. The cleanup refuses unless the stack file sits in a directory named for its slot that holds itsmarker.json.Flakes seen on the way, not caused here: #556 (outside-thread), #558 is fixed (#560), a new one for ask-in-other-mode (4 of 4 solo pass, one slow full run).
Theoretical, not changed:
verify-skillscould hold a solo session without the token; a world project named like a sibling slot's folder.Review: round 2 fresh default-model reviewer, no blocking findings; two minors fixed in the last commit
Red on main: solo run on origin/main left 3 entries in the slot's project folder (2 of 2); the selftest sibling-slot cases fail without the rivals rule
Real-app check: solo run left 3 entries on main, 0 on the branch (3 of 3); a solo run beside a hand-made sibling slot left the sibling's dummy sessions untouched
Journey: full --stack run 41/0/0 on the head, nothing left in ~/.claude/projects for the slot
Harness weakening: none, no journey, assertion or timeout changed; the cleanup runs in a finally and cannot change a PASS
Main harness vs head: not applicable, no PASS decision changed
Break-and-restore: with the new cleanup call disabled the solo run left 3 entries again; with the rivals rule removed a selftest case goes red
Verified: 8f82e83 · repo-suite: selftest 18 cases ok, check:static ok, eslint 0 errors; playwright 732 passed on an earlier head (the product code is unchanged) · devboxverify: --stack full 41 pass 0 fail 0 blocked · real-app: solo and full runs leave 0 · log: /tmp/e559
🤖 Generated with Claude Code