Plan: Fix worktree reuse path destroying committed agent work#

Summary#

Remove git reset --hard origin/master from the worktree reuse path in WorktreeService.createWorktree(). The reset silently destroys agent commits made during prior phases (e.g., execute → address_review). The reuse path should only run git fetch origin to update remote refs, preserving the branch's existing HEAD.

Files#

Steps#

1. In src/worktree/worktree.service.ts, remove the git reset --hard origin/master exec call from the if (worktreeReused) block (lines 103-106). Keep the git fetch origin call (line 103) and the surrounding log/comment. Remove or update the now-incorrect invariant comment (lines 98-102).
2. In src/worktree/worktree.service.spec.ts, update the test 'reuses an existing valid worktree without removal, runs fetch+reset' (line 145): rename to reflect fetch-only behavior, assert that NO reset call is made (expect(resetCall).toBeUndefined()), and retain the assertion that fetch is called in the worktree directory.
3. Run npm run test and npm run lint to verify all tests pass and no lint errors are introduced.

Verification#

• Unit test explicitly asserts reset --hard is NOT called when a valid worktree is reused.
• All existing worktree tests continue to pass (fresh create, invalid removal, branch attach paths unaffected).
• npm run lint passes with zero warnings.

Risks#

• None significant — the change is a 3-line deletion with a corresponding test update. The fresh-create and branch-attach paths are untouched.