feat: add no-result permission outcome for extensions (upstream PR #802)

[krukow]

Motivation

Upstream copilot-sdk PR #802 adds a no-result permission outcome so extensions can attach to sessions without actively answering permission requests. This is the idiomatic Clojure port.

Approach

When a permission handler returns {:kind :no-result}, the SDK treats it as "this extension declines to answer" rather than a deny:

• v3 protocol (broadcast): The handlePendingPermissionRequest RPC call is skipped entirely — the extension stays silent and another handler may respond.
• v2 protocol (RPC callback): A JSON-RPC internal error (-32603) is propagated to the CLI, matching upstream behavior where the thrown error signals no answer was given.

The sentinel value {:result :no-result} (a keyword instead of a map) flows through the internal handle-permission-request! → caller pipeline so both v2 and v3 code paths can distinguish it from a normal permission result.

Key decisions

• Handles both direct and wrapped forms: Permission handlers may return {:kind :no-result} (direct) or {:result {:kind :no-result}} (wrapped). Both are normalized to the sentinel before reaching callers.
• Error code -32603 matches the upstream Node.js SDK's internal error semantics for v2 no-result propagation.

Changes

• specs.clj — :no-result added to ::permission-result-kind
• session.clj — handle-permission-request! returns sentinel for no-result
• client.clj — v3 handler skips RPC; v2 handler returns error
• integration_test.clj — Tests for both direct and wrapped no-result on v2
• API.md — Documents :no-result in permission result examples
• CHANGELOG.md — Entry under [Unreleased]

Validation

• 94 tests, 294 assertions, 0 failures
• bb validate-docs passes
• Self-reviewed with GPT-5.4 + Gemini 3 Pro in parallel; both findings fixed

Created with GitHub Desktop

[Copilot]

Pull request overview

Ports upstream copilot-sdk PR #802 by introducing a :no-result permission outcome so extensions can attach to sessions without actively answering permission requests, with protocol-specific behavior for v2 vs v3.

Changes:

• Add :no-result to permission result specs and document it in the public API reference.
• Normalize permission handler returns to a {:result :no-result} sentinel in session/handle-permission-request!.
• Implement protocol-specific handling: v3 skips handlePendingPermissionRequest RPC; v2 propagates -32603 as an error, with integration tests for v2.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
test/github/copilot_sdk/integration_test.clj	Adds v2 protocol integration tests for direct and wrapped :no-result permission handler returns.
src/github/copilot_sdk/specs.clj	Extends ::permission-result-kind to include :no-result.
src/github/copilot_sdk/session.clj	Normalizes permission handler responses and introduces {:result :no-result} sentinel.
src/github/copilot_sdk/client.clj	Implements v3 “skip RPC on no-result” and v2 “return -32603 error on no-result” behavior.
doc/reference/API.md	Documents {:kind :no-result} as a permission handler return option.
CHANGELOG.md	Adds an Unreleased changelog entry describing the new :no-result outcome and v2/v3 semantics.