Move hooks example from README into lesson 15 (Programmatic Mode)

Agent-Logs-Url: https://github.com/instil/github-copilot-tutorial/sessions/836790b1-5069-4596-8b3f-94c23e92d1b5

Co-authored-by: calebwilson706 <71669491+calebwilson706@users.noreply.github.com>

Author: Copilot

README.md

@@ -62,15 +62,3 @@ The tutorial is built using three Copilot CLI features:
 - **Hooks** (`.github/hooks/`) — State persistence, context injection, and exercise validation
 
 The tutorial itself is built using these three features working together.
-
-### Hooks in Action
-
-The `.github/hooks/` directory shows real hook usage:
-
-| Hook | Script | Purpose |
-|------|--------|---------|
-| `sessionStart` | `session-start.sh` | Bootstrap `tutorial/state.json` on first run |
-| `userPromptSubmitted` | `prompt-context.sh` | Write the current lesson to `tutorial/current-lesson.md` so Copilot always has the right context |
-| `preToolUse` | `pre-tool-use.sh` | Auto-approve edits to `tutorial/state.json` so navigation agents don't trigger permission prompts |
-
-The `preToolUse` hook is a practical example of using `permissionDecision: "allow"` (available since Copilot CLI v1.0.18) to suppress approval prompts for trusted, repetitive operations — here, the lesson-progress updates that happen every time you say "next" or "skip".

tutorial/lessons/15-programmatic-mode.md

@@ -28,6 +28,30 @@ cat error.log | copilot -p "explain this error and suggest a fix" > summary.txt
 git diff main | copilot -p "review these changes for bugs"
 ```
 
+### Hooks for automation
+
+Hooks let you run scripts at key moments in Copilot's lifecycle — before and after tool use, when a session starts, or when a prompt is submitted. This is useful for automating repetitive decisions in CI or unattended workflows.
+
+A practical example lives in this tutorial itself. Navigation agents write to `tutorial/state.json` on every lesson transition. Rather than prompting for permission each time, a `preToolUse` hook auto-approves those writes:
+
+```json
+// .github/hooks/hooks.json
+{
+  "preToolUse": [{ "type": "command", "bash": "bash .github/hooks/pre-tool-use.sh" }]
+}
+```
+
+```bash
+# .github/hooks/pre-tool-use.sh
+INPUT=$(cat)
+FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.path // .parameters.path // .path // empty')
+if [ "$FILE_PATH" = "tutorial/state.json" ]; then
+  echo '{"permissionDecision": "allow"}'
+fi
+```
+
+Returning `permissionDecision: "allow"` from a `preToolUse` hook suppresses the approval prompt entirely — key for any automation where you trust the operation and want zero interruptions.
+
 ### Scoping permissions
 
 When running in automation, lock down what Copilot can do: