Warn agents before archiving or deleting their worktree

[davdroman]

What problem does this solve?

The generated CLI skills document worktree archive and worktree delete, but do not warn agents that either operation can remove the current worktree from Supacode's active terminal set and close the calling surface. An agent can therefore archive or delete its own worktree before finishing checks, commits, integration, or reporting, leaving the task incomplete.

Proposed solution

Add a concise critical section to the generated CLI skill guidance telling agents to make archiving or deleting the current worktree their final operation. The guidance should require all edits, checks, commits, integration, and reporting to finish first, with no follow-up commands scheduled. It should also cover worktrees removed through Git once Supacode refreshes them.

Alternatives considered

None.

Supacode version

Current main.

Are you planning to build this yourself?

• I intend to open a pull request once this is approved and marked ready.

Before submitting

• I searched existing issues and this is not a duplicate.
• I understand feature pull requests are closed until the issue is marked ready.
• I agree to follow this project's Code of Conduct.

[github-actions]

Thank you for filing this. A maintainer will review it and follow up here.

Please do not start any work or open a pull request until this issue is labeled ready. That label is a maintainer's go-ahead: a pull request opened against an issue that is not yet ready is labeled invalid until then. You will get a comment here the moment it is marked ready.

See CONTRIBUTING.md for the full flow.