Merge pull request #33 from copilot-community-sdk/docs/add-task-complete-custom-tool-kinds-89d11169fa16a9de

[docs] Update documentation for features from 2026-02-26

Author: krukow

CHANGELOG.md

@@ -17,6 +17,8 @@ All notable changes to this project will be documented in this file. This change
 
 ### Added (documentation)
 - Microsoft Foundry Local BYOK provider guide in `doc/auth/byok.md`: quick start example, installation instructions, and connection troubleshooting (upstream PR #461).
+- `doc/reference/API.md`: added `:copilot/session.task_complete` to the Event Reference table (from upstream PR #544 sync).
+- `doc/reference/API.md`: added permission kind reference table (`:shell`, `:write`, `:mcp`, `:read`, `:url`, `:custom-tool`) in the Permission Handling section.
 
 ### Added (upstream PR #329 sync)
 - Windows console window hiding: CLI process is spawned with explicit PIPE redirects ensuring the JVM sets `CREATE_NO_WINDOW` on Windows — no console window appears in GUI applications. Equivalent to upstream `windowsHide: true` (upstream PR #329).

doc/reference/API.md

@@ -885,6 +885,7 @@ copilot/tool-events
 | `:copilot/hook.start` | Hook invocation started |
 | `:copilot/hook.end` | Hook invocation finished |
 | `:copilot/system.message` | System message emitted |
+| `:copilot/session.task_complete` | Task completed by the session agent |
 
 ### Example: Handling Events
 
@@ -1170,6 +1171,17 @@ Use `approve-all` to opt into approving everything:
                {:on-permission-request copilot/approve-all}))
 ```
 
+The `:permission-kind` field in permission requests identifies the type of action requiring approval:
+
+| Permission Kind | Description |
+|----------------|-------------|
+| `:shell` | Shell command execution |
+| `:write` | File system write operation |
+| `:mcp` | MCP tool invocation |
+| `:read` | File system read operation |
+| `:url` | URL fetch / HTTP request |
+| `:custom-tool` | SDK-registered custom tool invocation |
+
 For fine-grained control, provide your own handler. When the CLI needs
 approval, it sends a JSON-RPC `permission.request` to the SDK. Your
 `:on-permission-request` callback must return a map compatible with the