dsh-trellis

Trellis is a cross-host task orchestration layer, but the DSH session model, subagent dispatch, and settings surface differ structurally from Codex or Claude Code. dsh-trellis is an optional companion plugin that closes the gap: each conversation turn carries the current workflow-state breadcrumb automatically, every DSH window gets an isolated active-task pointer, subagent dispatch shifts from background polling to event-driven fail-closed settlement, and configuration editing moves from hand-editing yaml to a staged web panel.

Five capability layers stand out. At agent/pre-step the plugin parses the [workflow-state:*] blocks in .trellis/workflow.md and injects them into the session context, with digest-based deduplication, automatic re-injection after compression, and an opt-out via the no-trellis keyword. A managed DSH_TRELLIS_CONTEXT_ID is derived from the native session header so that forwarded subagents never bleed into the parent task, and each headless invocation retains its own identity. Once installed, Trellis roles can use DSH continuable background subagents; trellis_wait listens on the subagent/end event and treats error, max-tokens, and refusal as fail-closed by design, while rc.8 idle-parent sessions are woken by the native settlement notice without any manual wait call. The /trellis-status and /trellis-finish commands provide read-only inspection and a safe shutdown checklist whose output never enters model history; true archiving goes through the skill-surface finish-work command. Finally, the DSH rc.8 settings panel exposes all six configuration items for staged editing, with savings guarded by namespace revision fencing and a read-back confirmation, applied instantly, and the card persists even after the plugin is disabled for one-click re-enable.

It is aimed at developers who already work on the Trellis platform and use DSH as their daily host. It does not change Trellis CLI behaviour or replace trellis init --dsh; it simply aligns Trellis scheduling semantics with the DSH session model so that parallel subagent dispatch, event-based settlement, AbortSignal inheritance, and configuration hot-reload all run natively. Without the plugin the workflow transparently falls back to synchronous foreground dispatch. Both paths forbid sleep or polling, and the Trellis CLI never auto-installs any DSH plugin.