Three ui-conversation spec conflicts resolve to master's SlotTestRuntime rewrites. Adaptation to the new outward session face: ISession gains the command verb (the composer chip and the /permission picker submit through it), FixtureSession grows the matching fail-loud stub plus the waitingApproval summary default, and the picker reads the projection through projections.faceOf (the ProjectionsFace shape) instead of the retired store getter.
@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.