ec601ca13d
Machine-produced by `pnpm run rescope-vendor --apply` plus the regeneration it prints: `pnpm install` for the lockfile, `pnpm run gen-third-party-notices`, `verify-translation-pairing --write` for the touched bilingual pairs, `gen-doc-graphs`, and one typert snapshot whose ids embed character offsets. `pnpm run rescope-vendor --check` verifies the result. Renames nine vendored packages (cordis, cosmokit, schemastery and the six @cordisjs plugins) and every reference that resolves them: manifest names and dependency keys, module specifiers including declare-module merges, cordis.yml plugin names, tsconfig paths, every Markdown fence, and `docs/` prose. Directory names, upstream versions, and dependency ranges are unchanged, so vendor/README.md still reads as an upstream snapshot; its manifest table gains an upstream-name column so THIRD_PARTY_NOTICES keeps MIT attribution pointed at each fork's origin. The tutorial tier follows the rename end to end: its yaml fences named plugins the Loader can no longer resolve, its `ts ignore-check` fences disagreed with the compiled fences beside them, and its prose quoted both. The contracts that told readers to keep upstream names — the root convention and the vendoring cookbook's tree comment and manifest invariant — now say to rescope instead. Two rules read `@deepseek-ai/` as "another workspace plugin": the client bundle purity gate now names the vendored libraries a browser bundle inlines, and the files where a bare `cordis` is an agent-preset id keep that product data.
@deepseek-ai/dsh-client-ui-permission
English | 中文
Permission browser surfaces for two different lifetimes. The General-settings row reads the explicitly exposed permission Settings descriptor, derives its options from the host's dynamic defaultPreset enum, and writes one settings.mutate path operation with the descriptor revision. Its observable rides the slot system's hooks compartment, so the renderer owns React hook binding; a push invalidation refetches the descriptor. This value applies only when a later session is created; changing it does not switch the current session. Choosing Full access requires an explicit risk acknowledgement before the row writes it.
The current-session surface remains a popupSelect DECORATION hung on the host /permission command (ctx.command.decorate). A decoration is not a second command — the host command keeps its slash-menu row, the argued path (/permission <preset> switches directly), and the durable lifecycle logging; the decoration replaces only the bare invocation with the picker: one flat preset list with the current value marked active and kebab-case preset names rendered as title-case labels (workspace-write → Workspace Write, the composer chip's display transform twin), 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 current-session surfaces share one read source and one write path, and the pushed projection frame is the single confirmation both follow. The decoration is available exactly while the projection key is present; a permission-less composition shows neither picker nor Settings row.
The /client export surface is the plugin body (apply/inject).
Model Experience
Indirectly, through the permission facts written by its two surfaces: the Settings row causes a future session to start with whole-value knob events (permission/preset, sandbox/mode, approval/policy), while the /permission picker appends the same facts when it switches the current session; those events select the sandbox mode and approval policy later tool calls resolve, and 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
- The Settings row is Web-only — non-Web clients may still switch the current session through
/permission, but do not receive this browser contribution.