analysis: root cause analysis for #59 (worktree teardown deletes branch-committed skills)#60
Closed
stempeck wants to merge 1 commit into
Closed
analysis: root cause analysis for #59 (worktree teardown deletes branch-committed skills)#60stempeck wants to merge 1 commit into
stempeck wants to merge 1 commit into
Conversation
Root cause analysis for the worktree-teardown skill-deletion bug (GitHub issue #59, bead af-6bc9e66f), produced by the rootcause-all formula. Artifacts under .analysis/af-6bc9e66f/. Synthesized root cause: cleanupMergedSkills infers what to delete from name-collision with the live factory .claude/skills/ instead of recording merge provenance, so branch-committed skills whose names collide with a factory skill are destroyed on teardown. Selected fix: gate deletion on git-tracked status (git ls-files) in the worktree; preserve tracked dirs. Co-Authored-By: Claude <noreply@anthropic.com>
|
agentfactory seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Owner
Author
|
Resolved. |
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.
Summary
Root cause analysis for #59, produced by the
rootcause-allformula. This PR carries the analysis artifacts only (under.analysis/af-6bc9e66f/) — it is not the code fix, so it does not close the issue.cleanupMergedSkills(internal/worktree/worktree.go:507-522) decides what to delete by inferring provenance from a name collision with the live factory.claude/skills/, instead of recording what the lifecycle actually merged in — so branch-committed skills whose directory name collides with a factory skill getos.RemoveAll'd on teardown. Identified as the 4th recurrence of the anti-pattern ADR-017 forbids.cleanupMergedSkillsso all teardown paths inherit the fix. Also resolves the ordering hazard (concern feat: Eliminate Manual File Moves After agent-gen #7) with no separate change.cleanupMergedSkills+trackedSkillDirs, a regression test, enforcement-level classification (the fix is an Interlock), and verification steps.See
.analysis/af-6bc9e66f/rootcause_analysis.mdfor the synthesized findings and solution; per-concern investigations are in the siblingrootcause_concern_*.mdfiles.Next step
Implementation of the selected solution (intended for the
ultra-implementpass).Relates to #59.
🤖 Generated with Claude Code