Skip to content

docs: record worktree adoption implementation status #594

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
frankgilson-lab wants to merge 1 commit into from
Closed

docs: record worktree adoption implementation status #594

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/IMPORTING_FROM_ANOTHER_TOOL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,3 +53,14 @@ The tool that owns the worktree remains responsible for its archive and deletion
## Conductor imports

The bulk `runpane import conductor` workflow is planned as a follow-up to the core adoption support. Until then, enumerate active Conductor workspaces and call `panes adopt` for each one. Pane already reads `conductor.json` for project scripts, but adoption deliberately does not run setup/build scripts.

## Implementation status

Core adoption support is implemented on the `warrior` branch as of commit
`4f4c3826` (September 3, 2026). The implementation adds persisted worktree
ownership with database migration `007_add_worktree_ownership.sql`, RunPane
adoption and preview handlers, resume staging, external-worktree lifecycle
guards, sidebar ownership labeling, and generated CLI contract updates.

The focused validation suite passes with 107 tests passing and 1 skipped. Main
and frontend TypeScript checks and the blocking Oxlint gate also pass.