Dispatch worktree leaves untracked agentic_os.egg-info, uv.lock, .claude - settle gitignore / uv.lock policy #79

New issue

Open

opened 2026-05-28 00:57:46 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-05-28 00:57:46 +00:00

Owner

Problem

The dispatch worktree .dispatch-worktrees/agentic-os/issue-149 ended in a state that coily dispatch reap refuses to clean - three untracked paths:

?? .claude/
?? agentic_os.egg-info/
?? uv.lock

Branch is already merged into origin/main. The work shipped. The untracked dirt is what blocks cleanup.

This is a sibling failure mode to coilysiren/coily#122 (which covers the .claude/lockdown-deny.sh + .claude/settings.json modified-files pattern). This one is untracked-files, and the file set is agentic-os-specific.

Fix

Three independent calls, all in this repo:

agentic_os.egg-info/ - Python build artifact, should be in .gitignore. Standard *.egg-info/ entry. Almost certainly just an oversight.
uv.lock - decide the policy. uv encourages committing lock files; if that's the call here, commit it and add a CI check that regeneration is a no-op. If not, gitignore it. Either way, "untracked and surprising" is the failure mode to remove.
.claude/ - upstream fix is coilysiren/coily#122 (dispatch should not touch .claude/* in worktrees at all). Once that lands, the worktree-side .claude/ won't materialize. Until then, adding .claude/ to this repo's .gitignore is the bandaid - flagged because the long-term answer lives in coily, not here.

Out of scope

The systemic dispatch-poisons-its-own-reap bug. Filed at coilysiren/coily#122.
Cleanup of the existing agentic-os/issue-149 worktree. Safe to git worktree remove --force once (1) and (2) are decided so the next dispatch doesn't reintroduce the same dirty state.

Context

Surfaced 2026-05-27 while inspecting eight stale dispatch worktrees. Six fit the coily#122 pattern. This one and gauntlet/issue-39 are the outliers. Gauntlet's a fully orphaned dir (no .git link, separate cleanup, not worth filing).

**Problem** The dispatch worktree `.dispatch-worktrees/agentic-os/issue-149` ended in a state that `coily dispatch reap` refuses to clean - three untracked paths: ``` ?? .claude/ ?? agentic_os.egg-info/ ?? uv.lock ``` Branch is already merged into `origin/main`. The work shipped. The untracked dirt is what blocks cleanup. This is a sibling failure mode to `coilysiren/coily#122` (which covers the `.claude/lockdown-deny.sh` + `.claude/settings.json` *modified*-files pattern). This one is *untracked*-files, and the file set is agentic-os-specific. **Fix** Three independent calls, all in this repo: 1. `agentic_os.egg-info/` - Python build artifact, should be in `.gitignore`. Standard `*.egg-info/` entry. Almost certainly just an oversight. 2. `uv.lock` - decide the policy. uv encourages committing lock files; if that's the call here, commit it and add a CI check that regeneration is a no-op. If not, gitignore it. Either way, "untracked and surprising" is the failure mode to remove. 3. `.claude/` - upstream fix is coilysiren/coily#122 (dispatch should not touch `.claude/*` in worktrees at all). Once that lands, the worktree-side `.claude/` won't materialize. Until then, adding `.claude/` to this repo's `.gitignore` is the bandaid - flagged because the long-term answer lives in coily, not here. **Out of scope** - The systemic dispatch-poisons-its-own-reap bug. Filed at coilysiren/coily#122. - Cleanup of the existing `agentic-os/issue-149` worktree. Safe to `git worktree remove --force` once (1) and (2) are decided so the next dispatch doesn't reintroduce the same dirty state. **Context** Surfaced 2026-05-27 while inspecting eight stale dispatch worktrees. Six fit the coily#122 pattern. This one and `gauntlet/issue-39` are the outliers. Gauntlet's a fully orphaned dir (no `.git` link, separate cleanup, not worth filing).

coilysiren referenced this issue from coilyco-bridge/coily

2026-05-28 00:59:59 +00:00

coily dispatch reap should handle orphaned worktree dirs - registration gone, dir survived #123

coilysiren added the

label

2026-05-31 01:54:06 +00:00

coilysiren added

and removed

labels

2026-05-31 07:00:05 +00:00