* feat(i18n): key translation pairing records by heading section Replace the whole-file blob hashes in *.i18n.yaml with one entry per heading section that still holds language-specific content, keyed by the English heading-slug path. Blocks identical across the pair (generated table rows, code blocks, shared regions) stay out of the hash, so edits to different sections and identical regenerations merge with Git's default text merge, including on GitHub. Remove the dsh-translation-pairing merge driver, its resolver command and installer wiring; gen-translation-brief recovers last-confirmed text from commit history. Migrate all active records, archive the superseded Agent Note, and record the replayed conflict reduction in the new one. * test(i18n): refresh translation prompt snapshot for the terminology note * feat(i18n): exclude only code blocks and generated regions from pairing records Replace byte-equality masking with an explicit rule: a record hash skips fenced code blocks and BEGIN/END GENERATED regions, the two kinds of content the pairing gate already requires to be identical on both sides. Move generated data into regions written into both pages: gen-config-catalog renders both languages and the record with per-package regions labelled by code identifiers; gen-module-graph keeps its table in a region; gen-doc-graphs splices the event matrix regions into the Chinese page. Add a generic region splice beside the region grammar.
description, kind
| description | kind |
|---|---|
| Save active profile configuration and apply it through Loader. | package-reference |
@deepseek-ai/dsh-config-editor
English | 中文
Summary
Save plugin configuration in the active profile’s patch and apply it immediately. Writes validate the complete candidate before touching disk and serialize with profile changes and HMR. Invalid values and higher-layer overrides leave the file unchanged.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
Mount this service in a profile application with Loader and profileContext. It has no configuration fields.
- id: config-editor
name: '@deepseek-ai/dsh-config-editor'
Use settings for forms restricted to live fields. Callers that edit complete configuration can use ctx.configEditor.edit(); ordinary fields retain Loader’s normal lifecycle.
Understand the implementation
Implementation internals — click to expand
The editor reconciles external changes before deriving a candidate, locks the profile manifest alongside other profile operations, and atomically replaces its config override. It preserves YAML comments and !!js expressions outside replaced values. A failed reconciliation restores the prior document and reloads the prior patches.
No invariant companion is published: the editor keeps no independent configuration projection. Loader and the persisted profile patch own configuration state.
Further Exploration
- Profile loading — patch composition.
- HMR — reload coordination.
- Settings — schema-derived forms.
Model Experience
Indirectly, through configuration values consumed by model-facing plugins.
KV Cache effect
Consumers that change request prefixes determine cache effects.
Known Limitations and Deferred Work
- Edits target the active profile patch. Home patches and command-line overlays are read for precedence but are not write targets.
- A complete config override preserves ordinary fields but pins their current raw values at the profile layer.
- Only uniquely addressed entries owned by the profile’s root Include are editable.
Dev Note
Working context for maintainers — click to expand
None.