feat(plugin): add optional askPermission to ToolContext

[nielpattin]

Add optional askPermission to plugin ToolContext

Summary

• Plugins can now call ctx.askPermission() to request user confirmation before sensitive operations
• Made the property optional to avoid breaking existing plugins

Details

This hooks into the existing Permission.ask() system so plugins get the same permission UX as built-in tools.

Example usage in a plugin:

execute: async(ctx,input)=>{if(ctx.askPermission){awaitctx.askPermission({tool: "dangerous-tool",message: `About to delete ${input.path}`,})}// proceed with operation}

Testing

• Existing plugins (without askPermission) still work
• New plugins can opt-in to permission prompts

Checklist

• Types are backward compatible (optional property)
• No breaking changes for existing plugins

Demo:

(Ignore the skill tool mention, it's just a plugin that use the same format as the native skill support)

WindowsTerminal_roeVGaFi3l.mp4

Used locally on nielpattin/opencode-skillful

[eXamadeus]

Copied from my comment:

I think the changes #6042 (this PR) proposes should probably be done through the SDK. The caveat is that #12042 needs to merge first. Then the Permission.ask endpoint would need to be exposed like #12046 does for Question.ask.