dsh-visualizer

Configuration

The bundle layer already inserts the loader row, so overriding config takes a flat id-targeted patch entry in the profile's own patch layer (~/.dsh/profiles//cordis.patch.yml). Don't wrap it in insert: — that appends a second row instead of overriding the installed one. Values validate against the schema at load, and a mistake fails the mount loudly. Every option has a schema default, so an override block only lists the fields being changed. The complete option list, at current defaults:

- id: dsh-visualizer
  config:
    maxHtmlBytes: 262144    # default; per-call render limit, in UTF-8 bytes
    guideTool: true         # default; set false to use only the render tool
    guideModules: [chart, diagram, mockup, interactive, art]   # default; subset to teach and serve;

guideModules narrows both guide surfaces at once. The standing system-prompt roster lists only those types' one-liners, and the JIT tool's argument enum accepts only those ids, so a disabled type is rejected at the argument boundary before any code runs. guideTool: false skips the second tool registration; the render tool and the standing prompt section are unaffected. Unknown module ids or an empty guideModules fail the plugin load. Defaults are on, all five types (chart, diagram, mockup, interactive, art).