Update Learning Hub for Copilot CLI v1.0.35–v1.0.37 changes (#1546)

- copilot-configuration-basics.md:
  - Add continueOnAutoMode config setting (v1.0.35)
  - Document --name/--resume=<name> for named sessions (v1.0.35)
  - Add /session delete, delete <id>, delete-all subcommands (v1.0.35)
  - Add session picker sort order (press 's', v1.0.37)
  - Update /ask to note markdown rendering including tables (v1.0.37)
  - Update /statusline to mention 'changes' line-count toggle (v1.0.36)
  - Add /keep-alive command (now available without experimental mode, v1.0.36)

- using-copilot-coding-agent.md:
  - Document /remote on and /remote off subcommands and status display (v1.0.36)

- automating-with-hooks.md:
  - Add note on location-based permission persistence enabled by default (v1.0.37)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

website/src/content/docs/learning-hub/automating-with-hooks.md

@@ -3,7 +3,7 @@ title: 'Automating with Hooks'
 description: 'Learn how to use hooks to automate lifecycle events like formatting, linting, and governance checks during Copilot agent sessions.'
 authors:
   - GitHub Copilot Learning Hub Team
-lastUpdated: 2026-04-27
+lastUpdated: 2026-04-28
 estimatedReadingTime: '8 minutes'
 tags:
   - hooks
@@ -239,6 +239,8 @@ automatically before the agent commits changes.
 
 The `PermissionRequest` hook fires when the CLI shows a permission prompt to the user — for example, when the agent wants to run a shell command for the first time. Unlike `preToolUse` (which can block specific tool *calls*), `PermissionRequest` intercepts the permission approval UI itself, making it ideal for **headless and CI environments** where no one is available to click "Allow".
 
+> **Location-based persistence (v1.0.37+)**: Permission approvals are now persisted by directory by default — once you approve a permission for a given working directory, that approval carries over to future sessions started in the same directory. You no longer need to re-approve the same tools every time. Use `PermissionRequest` hooks to automate approvals in CI, and rely on the persisted approvals for interactive local sessions.
+
 When your hook script exits with code `0`, the permission request is **approved**. Exit with a non-zero code to **deny** it (the user will still see the prompt).
 
 ```json