fix: make git hooks opt-in only — do not modify hooks when disabled

Remove the else branch that actively called GitHooksService.disableHooks()
for every user where gitHooksEnabled was false (the default). This was a
breaking change that silently modified core.hooksPath to point at an empty
directory, disabling any existing git hooks (husky, lefthook, pre-commit, etc.).

When gitHooksEnabled is false (default), the action now does nothing
regarding hooks — exactly matching the behavior on main before the hooks
feature was added. The hooks feature only activates when users explicitly
set gitHooksEnabled: true.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: frostebite

dist/index.js

@@ -102,17 +102,14 @@ async function runMain() {
         }
       }
 
-      // Git hooks
+      // Git hooks — opt-in only. When disabled (default), do not touch hooks at all.
       if (buildParameters.gitHooksEnabled) {
         const { GitHooksService } = await import('./model/orchestrator/services/hooks/git-hooks-service');
         await GitHooksService.installHooks(workspace);
         if (buildParameters.gitHooksSkipList) {
           const environment = GitHooksService.configureSkipList(buildParameters.gitHooksSkipList.split(','));
           Object.assign(process.env, environment);
         }
-      } else {
-        const { GitHooksService } = await import('./model/orchestrator/services/hooks/git-hooks-service');
-        await GitHooksService.disableHooks(workspace);
       }
 
       await PlatformSetup.setup(buildParameters, actionFolder);