@wm-coders/dsh-custom-first-control-prompt

Configuration

- id: custom-first-control-prompt
  name: '@wm-coders/dsh-custom-first-control-prompt'
  config:
    sections:
      - name: house-rules
        order: -50
        text: |
          …stable system text…
    history:
      - user: …
        assistant: …
    includeSubagents: false

Key	Default	Meaning
sections	—	Ordered system-prompt fragments; absent or empty registers nothing.
sections[].name	required	Entry name; the registry sees custom-first-control-prompt:.
sections[].order	required	Render position among all sections. Factory convention: harness identity −100, persona 0, tool guidance 100–199; values below 0 prepend ahead of the persona.
sections[].enabled	true	false keeps the entry in configuration without registering it.
sections[].text	required	Static section text; keep it free of volatile values — any change breaks prefix reuse from the first changed token.
history	—	Ordered user/assistant reference exchanges injected ahead of every ordinary conversation request; both texts must be non-empty and free of reserved tags (case-insensitive: , , ``, <custom-history and all closing tags). Absent or empty injects nothing.
includeSubagents	false	false skips sessions whose header meta marks subagent origin.

Invalid configuration fails plugin load naming the offending entry: empty text, duplicate section names, or a non-finite order. Per-entry section problems (blank/duplicate name, bad order, empty text) and per-pair history problems (empty text, embedded reserved tags) degrade to skipping that entry with a warning instead of failing the plugin tree.