Gemini permissions — read and toggle

[varkart]

Goal

Surface and toggle Gemini CLI permission/scope settings. Parity with Claude permissions (#26, #27).

Gemini permission fields

Gemini settings.json may contain tool-use scopes and extension permissions. Research exact schema from latest Gemini CLI release before implementing.

Steps

1. Read Gemini CLI source/docs for current permission schema
2. Add Permission entries to gemini manifest
3. Read permissions in Gemini detector
4. Surface in Gemini tool detail (same UI pattern as Claude)
5. Write changes via Read → Diff → Patch → Write with backup

Acceptance criteria

• Gemini permissions shown in tool detail
• Toggle writes to correct config section only
• Backup taken before write
• Audit event written
• No secrets exposed

[varkart]

Status: Infrastructure done, UI on hold

Backend engine + Gemini manifest are wired (PR #108, branch feat/gemini-permissions). Permissions section is hidden from the UI until UX is redesigned.

What's built

• Configurable allow_key/deny_key in PermissionsSpec so Gemini's tools.allowed/tools.exclude works without code changes
• Gemini [permissions] manifest section added
• IPC param bug fixed (toolId → agentId)
• PermissionsSection + PermissionsDetailPanel + permissions-detail view all wired — just not rendered

Blocked on: UX redesign

The current section shows nothing when there are 0 rules, gives no context about what a rule is, no examples, no per-agent documentation of available tool names. Needs:

• Short explanation of what permissions control (tool authorization — skip or block prompts)
• Common rule examples per agent (Bash(git:*), WebSearch, etc.)
• Quick-add presets
• Per-agent tool name reference (Claude and Gemini use different tool name formats)