# dsh-import-copilot-files bundle patch # # This file is the `dsh.bundle.patch` layer of the package: when the plugin is # installed through the official DSH CLI — # # dsh plugin --profile add dsh-import-copilot-files # # or from a git repo: # dsh plugin --profile add github:NEVSTOP-LAB/dsh-import-copilot-files # # — the CLI appends this bundle to the profile stack and this patch inserts # the plugin row. The row's module name is the package name, resolved through # the profile's node_modules. # # The plugin publishes no service, so it sits loose in the host composition # rather than behind an `isolate` realm; registering on the host plane is what # makes its contributions global, i.e. visible to every session and preset. # # The row's `id` is the Loader entry id, and since dsh 0.1.7 that id is also the # settings entry `dsh-settings` derives this plugin's configuration form from — # the plugin's own `Config` schema is the settings document, so there is no # namespace to register. The browser half (`lib/client.js`) and `index.js` both # spell this id literally, and `npm run verify:settings` compares the three # against this file, which is where the id actually comes from. # # This row's `config` is also the form's `base` layer (`paths` is the one field # the GUI edits; it is declared `.volatile()` so a committed change reaches # discovery without re-composing the row). Leaving it here is what a deployment # without the settings provider, or one that cannot resolve schemastery, runs on. - insert: - id: dsh-import-copilot-files name: 'dsh-import-copilot-files' config: # Rendered-instructions budget, in bytes, per injection. maxBytes: 65536 # Project roots scanned: the session cwd plus this many levels below it. scanSubdirectories: 1 # Configuration directories outside the workspace. Each entry IS the # `.github`-equivalent directory: it holds `copilot-instructions.md`, # `instructions/` and `skills/` directly, so there is no `.github` under # it and `scanSubdirectories` does not apply to it. Absolute paths, or # paths relative to the session cwd; a leading `~` is the user's home # directory, which is what makes the default entry the per-user Copilot # home (`[user]\.copilot`) on every machine. The one field the GUI edits; # a save lands as an override of this row in the profile's own patch # layer. For example: # paths: # - ~/.copilot # - D:\NEVSTOP-LAB\shared-ai-config # - \\server\team\.ai paths: - '~/.copilot'