# dsh-my-go agent preset — Sisyphus orchestration (agent-plane composition).
#
# This file is an AGENT-PLANE composition, following the same conventions as
# the builtin `standard` preset (and internal experimental presets):
#  - service rows MUST sit inside a group carrying an `isolate` realm;
#  - the delegation group (subagent tools) resolves the HOST subagents
#    registry and needs `isolate: workflowEngine` (one realm for the rows
#    that reach it);
#  - the broker host plugin is a local mjs row (self-contained preset).
#
# Copy this directory to ~/.dsh/.agent-presets/dsh-my-go/ to install.
#
# The model-facing "orchestration instructions" are a system-prompt section
# named `dsh-my-go:orchestration`; they teach Sisyphus the four tools and the
# QA rules from AGENTS.md.

# ── identity ────────────────────────────────────────────────────────────────
# Persona and orchestration instructions are registered dynamically by the
# broker (tools/broker.mjs) based on agent type — Sisyphus gets the full
# persona + orchestration rules, sub-agents get a minimal persona only.

- id: agent-instructions
  name: '@deepseek-ai/dsh-agent-instructions'
  config:
    maxBytes: 65536

# ── shell ───────────────────────────────────────────────────────────────────
- id: tool-bash
  name: '@deepseek-ai/dsh-tool-bash'
  disabled: !!js process.platform === 'win32'

- id: tool-pwsh
  name: '@deepseek-ai/dsh-tool-pwsh'
  disabled: !!js process.platform !== 'win32'

# ── filesystem ──────────────────────────────────────────────────────────────
- id: tool-fs
  name: '@deepseek-ai/dsh-tool-fs'

- id: tool-fs-search
  name: '@deepseek-ai/dsh-tool-fs-search'
  config:
    sampleOverCapGlobResults: false

# ── background jobs / skills / goals / plan / compaction ────────────────────
- id: tool-jobs
  name: '@deepseek-ai/dsh-tool-jobs'

- id: skill-filesystem
  name: '@deepseek-ai/dsh-skill-filesystem'

- id: tool-skill
  name: '@deepseek-ai/dsh-tool-skill'

- id: tool-goal
  name: '@deepseek-ai/dsh-tool-goal'

- id: planning
  name: cordis:group
  group: true
  isolate:
    planMode: true
  config:
    - id: plan-mode
      name: '@deepseek-ai/dsh-plan-mode'
      config:
        section: |
              You are in plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement — including an answer confirming something you asked — approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.

              Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.

              The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.

              Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.

              Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.

              When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.

- id: compaction
  name: cordis:group
  group: true
  isolate:
    compaction: true
    toolResultPruner: true
  config:
    - id: compaction-basic
      name: '@deepseek-ai/dsh-compaction-basic'
    - id: command-compact
      name: '@deepseek-ai/dsh-command-compact'
    - id: tool-result-pruner
      name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
      config:
        thresholdChars: 8192
        headChars: 4096
        tailChars: 1024

# ── delegation (subagent tools + broker host) ───────────────────────────────
# The subagents registry lives on the HOST; these rows resolve it. The broker
# host plugin (local mjs) registers the orchestration tools and model binding
# into this preset's scope, so both Sisyphus and its children see them
# (children are restricted from go_work/continue/forward by the broker).
- id: delegation
  name: cordis:group
  group: true
  isolate:
    workflowEngine: true
  config:
    - id: tool-subagent-control
      name: '@deepseek-ai/dsh-tool-subagent-control'

    - id: tool-subagent-list-agents
      name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'

    - id: tool-subagent
      name: '@deepseek-ai/dsh-tool-subagent'
      config:
        provider: spawn
        toolName: subagent
        backgroundMode: continuable

    - id: tool-subagent-fork
      name: '@deepseek-ai/dsh-tool-subagent'
      config:
        provider: fork
        toolName: subagent_fork
        backgroundMode: continuable

    - id: workflow-worker-thread
      name: '@deepseek-ai/dsh-workflow-worker-thread'
      config:
        provider: spawn

    - id: tool-workflow
      name: '@deepseek-ai/dsh-tool-workflow'

    - id: tool-ralph
      name: '@deepseek-ai/dsh-tool-ralph'
      config:
        subagentProvider: spawn
        maxRounds: 64

# ── broker (orchestration tools + prompt section) ───────────────────────────
# Deliberately OUTSIDE the delegation group: this row only CONSUMES the host
# `tools` / `subagents` / `systemPrompt` registries (it publishes nothing), so
# it needs no isolate realm — and its `systemPrompt.section()` must land in the
# agent's scope, which an `isolate` realm would hide from the assembly.
- id: broker
  name: './tools/broker.mjs'

# ── remaining model-facing rows ─────────────────────────────────────────────
- id: tool-ask-user
  name: '@deepseek-ai/dsh-tool-ask-user'

- id: tool-todo
  name: '@deepseek-ai/dsh-tool-todo'
  config:
    allowParallelInProgress: true

- id: tool-web
  name: '@deepseek-ai/dsh-tool-web'
  config:
    fetch: false
    searchTimeoutMs: 60000

# ── tool mask ────────────────────────────────────────────────────────────────
# Hides environment-specific tools from this preset's catalog — applies to
# Sisyphus and every sub-agent on the preset. The mask list lives in
# ./tool-mask.mjs (DEFAULT_DENY, per-name try/catch so an absent tool cannot
# fail the mount); override it wholesale with a `config.deny` array on this
# row to match your own deployment.
- id: tool-mask
  name: ./tool-mask.mjs