# 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. # # This row's `config` is also the base layer of the plugin's settings namespace # (`import-copilot-files`), which the same plugin serves to the GUI's # Settings → Plugins → plugin-configuration tab. Editing `paths` there takes # effect without a restart; leaving it here is what a deployment without that # card, or a pinned one, 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. For example: # paths: # - ~/.copilot # - D:\NEVSTOP-LAB\shared-ai-config # - \\server\team\.ai paths: - '~/.copilot'