@zhchxiao123/dsh-devflow-bundle

One-command install for the devflow plugin line. This package has no behavior of its own — its substance is cordis.patch.yml, the mount list that dsh plugin add applies to a profile.

Install

dsh plugin --profile web add @zhchxiao123/dsh-devflow-bundle

That is the whole install. dsh plugin add forwards to pnpm, then reconciles the profile's dsh.profile.bundles layer stack against what got installed: a dependency whose manifest declares dsh.bundle joins the stack, so this package appends itself and its patch mounts every row below. No profile file to edit.

What it mounts

Row	Enabled	Why
devflow (the filesystem store)	yes	root unset on purpose: each caller's own workspace resolves it, which is what lets one harness serve many projects
devflow-tool	yes	the model-facing plane
devflow-command	yes	the /devflow intervention plane
devflow-fs-guard	yes	keeps the store the only write path over card history
devflow-artifact-gate	no	an empty spec set gates nothing, and which artifact kinds guard which edge is a project decision
devflow-agent-gate	no	it spends model budget per checked move, and its required reportDir has no defensible default
devflow-gates	no	an empty gate set vetoes nothing, and which commands guard which edge is a project decision
devflow-parent-gate	yes	completion policy for decomposed requirements
devflow-web	yes	the board's host half — the read route and the change stream
devflow-ui	yes	the board itself, browser half

The four transition policies are mounted in the waterfall order the deployment sample relies on — mechanical artifact contract, agent admission, command gates and approvals, completion — and enabling a row keeps its place in that order.

Every row keeps the controls it would have had if you had composed it by hand. Override any of them from your profile's own cordis.patch.yml, which applies after every bundle layer:

- devflow-gates:
    disabled: false
    config:
      edges:
        'developing->reviewing': ['pnpm run test']
      approvals: ['reviewing->testing']

Model Experience

None, as this package contributes a mount list and registers no prompt, schema, or tool. The model-facing surface belongs to dsh-devflow-tool.

KV Cache effect

None; the package never assembles or sends provider requests.

Known Limitations and Deferred Work

• Gate defaults are off — a bundle cannot know a project's artifact contract, test commands, or model budget, so the rows that need those answers (devflow-artifact-gate, devflow-agent-gate, devflow-gates) ship disabled rather than guessing. The deployment sample is a complete configuration to start from. The Harness agent remains the sole workflow executor.