@gatedflow/dsh

DeepSeek Harness adapter for the gatedflow engine: the gf_* tools, the gate panel UI, the anti-bypass guard, and filesystem persistence.

The engine core (@gatedflow/engine) is framework-agnostic and contains no LLM; this package is the thin, typed wiring layer over the harness services.

Usage

Two rows in two planes. The engine row is per-preset (tools are per-session registrations); the gateway row is host-plane (the webServer route registry and the browser panel are process-global):

# An agent preset (agent.cordis.yml) — engine + gf_* tools per session.
- id: gatedflow
  name: '@gatedflow/dsh/host'
  config:
    stateDir: ~/.gatedflow        # shared subflow root (read-only)
    gateDeadlineSecs: 1800        # default gate timeout
    shellTimeoutMs: 120000        # default shell step timeout
    auditTailLines: 500           # bounded audit tail
    subagentProvider: spawn       # subagents provider for agent steps

# The Host composition (cordis.patch.yml insert) — panel transport + UI.
# The bare package name is REQUIRED: dsh-client-modules discovers the
# browser half through `${entryName}/package.json`, so a subpath name
# (e.g. `@gatedflow/dsh/gateway`) is never scanned.
- id: gatedflow-gateway
  name: '@gatedflow/dsh'

The gateway row registers GET /gatedflow/gates and POST /gatedflow/decide on the host webServer and anchors the browser half, which ships through the package's dsh.client declaration — no separate client row is needed. The client half registers the gate panel in conversation.input.dock, polls GET /gatedflow/gates, and posts human decisions to /gatedflow/decide, which reach the engine directly through the shared transport hub.

Without the gateway row the engine and tools still work — only the panel is missing (gates are then followed through gf_status instead).

Config

Field	Default	Meaning