Make it easier to teardown worktree container resources

We use worktrees for every session that spin up a pile of container resources and it would be great to automate their teardown in a way that be compatible with other agentic platforms too. I've tried to do this with skills but results have been patchy!

Manual clean up is difficult when the worktree names are randomised and the "path" copy facility is truncated and within a menu. Because all I can see is the first part of the path, I can't see the session's worktree name to manually tear it down in my container controller.

It would be great if these names were meaningful (eg reflected the session name) to make identifying them in the container program easier. With lots of open worktrees, it's hard to know which is which:

Even better if the Copilot app was container-aware, offering to take down worktree resources once the PR is merged. Again, I've tried to automate this with skills but overall getting the app to perform an action after a PR merge seems difficult / unreliable.

(Love the product and in awe of your innovation speed!)

---
| Field | Value |
| --- | --- |
| App version | 1.1.10 |
| OS | macOS 26.6.1 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 12 |

The issue names no files, tests, or entry points. Start by locating the worktree lifecycle and the app's PR-merge handling, then determine how container resources are identified and managed across supported agentic platforms. Done should include a defined approach for meaningful worktree names and reliable resource teardown after a merged PR.

Written by the indexing model from the issue text.