imccyu
728d28e7e4
Two real branches gain assertions (effectivePermissionPreset's backward scan over non-preset events; the popup options() throw when the projection vanished between availability and open — a sync throw, not a rejection). The empty ui-permission node half joins the ui-model entry on the client-lane coverage debt list (same pure-UI plugin shape, same TODO).
@deepseek-ai/dsh-client-ui-permission
English | 中文
Permission preset selection plugin, browser half: the /permission popupSelect contribution (registered through ctx.command). The contribution is hostBacked — the host's /permission command owns the slash-menu row, the argued path (/permission <preset> switches directly), and the durable lifecycle logging; this entry supplies only the bare-invocation picker: one flat preset list with the current value marked active, where a pick submits the /permission <preset> command line. Options and the active mark read the session's permissions projection (the same host-computed select the composer chip renders), so both surfaces share one read source and one write path, and the pushed projection frame is the single confirmation both follow. The contribution is available exactly while the projection key is present; a permission-less composition shows no picker.
The /client export surface is the plugin body (apply/inject).
Model Experience
Indirectly, through the host /permission command the picker submits: a switch appends the whole-value knob events (permission/preset, sandbox/mode, approval/policy), which select the sandbox mode and approval policy later tool calls resolve. Picker interaction adds no prompt content.
KV Cache effect
No direct invalidation; the knob consumers own any request-prefix changes.
Known Limitations and Deferred Work
- No keyless snapshot exercises the picker yet — the popup flow is covered by unit specs over fake faces; the assembled-transcript scenario rides the deferred approval/preset e2e work.