toga-ai 1.0.663 → 1.0.664

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "toga-ai",
3
- "version": "1.0.663",
3
+ "version": "1.0.664",
4
4
  "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
5
5
  "keywords": [
6
6
  "claude",
@@ -28,6 +28,23 @@ pushes that skill describes. It does not authorize publishing anything else in t
28
28
 
29
29
  Force-pushing is never automatic in any repo, including the knowledge repo.
30
30
 
31
+ ## Claude never creates git worktrees
32
+
33
+ Claude **must never** run `git worktree add` (or otherwise create a git worktree) in any
34
+ repo, for any developer, under any circumstances — **including** to isolate a hotfix from the
35
+ branch the developer currently has checked out. There is no approved use of worktrees.
36
+
37
+ Worktrees strand the developer: their editor and terminal end up pinned inside the worktree
38
+ directory (`C:\WWW\_hotfix\...`) with no obvious way back to their normal checkout, and
39
+ cleaning it up needs worktree-specific commands (`git worktree remove`) most developers do
40
+ not expect.
41
+
42
+ To work on a branch **other** than the one checked out, use the normal single-checkout flow:
43
+ make the edits on the current branch, or tell the developer which branch is needed and let
44
+ them switch (`git checkout` / `git switch`) — Claude does **not** switch branches itself
45
+ either (see *Claude never rewrites code because a branch changed*). Present diffs/patches and
46
+ let the developer commit, PR, and deploy.
47
+
31
48
  ## Claude never rewrites code because a branch changed
32
49
 
33
50
  Many developers work across many projects and switch branches constantly. A change that is