# The rickylabs bundle patch: the coordinator layer, applied as ONE insert over whatever
# the base bundles already put on the profile root.
#
# GENERATED FROM packages/dsh-app/src/bundle.ts. Edit that file and re-render; a hand edit
# here is reverted by the next `pnpm run build`, and `bundle.test.ts` fails in the meantime.
#
# The insert carries no `id`, so cordis appends these rows at the root of the entry list
# rather than nesting them into a group. Nothing here addresses a base row: this bundle adds
# services, it does not reconfigure dsh's own.
#
# Row order carries no load semantics; activation is service-availability driven.

- insert:
    # The `ctx.subagents` seam (E3 · #33). Claimed empty here on purpose: this row exists so
    # that a provider package has something to attach to, and so that the failure mode of a
    # deployment with no providers is `no-providers` from `selectProvider` rather than a
    # missing-service crash at the first dispatch.
    #
    # It injects `harnessTelemetry` (E9 · #83) and stays PENDING without it. Empty is not the
    # same as unwatched: what this row provides is wrapped for telemetry and marked as wrapped,
    # and `selectProvider` refuses to dispatch through a registry holding a provider that is not
    # (#208). Registration replaces the registry rather than passing through the wrapper, so the
    # refusal — not the wrapping — is what a provider package cannot get around by forgetting.
    - id: harness-subagents
      name: '@rickylabs/dsh-app/plugins/subagents'

    # The board projector (E6 · #36), configured. GitHub holds board truth and dsh projects
    # the live view (decision 3), so what this service owns is the taxonomy — the lane prefix
    # and the priority order — while the caller owns the issues and the clock.
    - id: harness-board
      name: '@rickylabs/dsh-app/plugins/board'

    # Workflow definitions and the evaluator independence policy (E6 · #36). The policy is
    # configuration because #72 named two, not because both are equally good: the default is
    # the stronger one, and choosing the weaker is a decision a deployment has to write down.
    - id: harness-coordinator
      name: '@rickylabs/dsh-app/plugins/coordinator'

    # The run sink and snapshot builder (E9 · #39) — the `status ?` killer. Resolving the
    # observability paths at boot rather than per call is the point: a snapshot taken after a
    # log rotation must read the same directory the sink was writing to.
    - id: harness-telemetry
      name: '@rickylabs/dsh-app/plugins/telemetry'

    # The explicit routing document selection (#271). A deployment may replace this whole
    # document in its profile patch. No missing-document fallback exists.
    - id: harness-routing
      name: '@rickylabs/dsh-app/plugins/routing'
      config:
        document: "@rickylabs/routing/config/routing.v1.json"

    # The three token-metered destinations — lm-studio, llama-rocm, openrouter (E2 · #176) —
    # registered on `ctx.llm`, which `@deepseek-ai/dsh-llm` owns and the composed profile
    # already mounts. It injects `llm` and `harnessRouting`, staying PENDING without either.
    #
    # Base URLs only. A credential is never a profile key: a profile is committed and a
    # credential must not be, so `OPENROUTER_API_KEY` is read from the daemon's environment at
    # dispatch. The `ctx.subagents` seam above is a different meter — quota windows, not
    # tokens — and the two are kept apart deliberately.
    - id: harness-llm
      name: '@rickylabs/dsh-app/plugins/llm'