fix: surface permission reply API errors instead of recording silent failures

[ben-vargas]

Summary

replyToPendingApprovals called permissionApi.reply({...}) inside a try/catch but never inspected the resolved value. The provider creates OpenCode SDK v2 clients with responseStyle: "fields" and no throwOnError (see createManagedClientOptions in src/opencode-client-manager.ts), so API-level failures resolve as { data, error } rather than throwing. A failed permission reply was therefore silently recorded as replied (repliedApprovalIds.add(...)) with no warning, and the approval was never retried — OpenCode kept waiting on the permission request.

Fix

Same pattern as the question-handling fix in #33:

• Pass the permission.reply result through the existing extractSdkResult helper.
• When the result carries an error: log a warning, push it to the response warnings array, and skip adding the id to repliedApprovalIds so the next turn retries the reply.
• The thrown-error path is unchanged.

Tests

Added a unit test where mockClient.permission.reply resolves with { error: {...} }, asserting:

• the warning reaches both the injected logger and the doGenerate result's warnings array
• a second doGenerate with the same prompt calls permission.reply again (the failed approval id is not recorded as replied)

Verification

• npm test — 391 tests passing
• npm run typecheck — clean
• npm run lint — 0 errors, 7 pre-existing warnings (unchanged from main)
• npm run build — success