History

Chinesezjc 0567727410 Merge remote-tracking branch 'origin/master' into feat/todo-multi-in-progress # Conflicts: # apps/cli/config/base.cordis.yml # packages/client/ui-conversation/README.i18n.yaml		2026-08-07 11:27:24 +08:00
..
base	Merge remote-tracking branch 'origin/master' into feat/todo-multi-in-progress	2026-08-07 11:27:24 +08:00
headless	Merge remote-tracking branch 'origin/master' into feat/profile-plugin-management	2026-08-06 20:03:22 +08:00
web-app	fix: address review round two	2026-08-07 00:05:42 +08:00
README.i18n.yaml	refactor(cli)!: namespace the profile and bundle manifests under dsh.profile and dsh.bundle	2026-08-06 17:28:30 +08:00
README.md	refactor(cli)!: namespace the profile and bundle manifests under dsh.profile and dsh.bundle	2026-08-06 17:28:30 +08:00
README.zh.md	refactor(cli)!: namespace the profile and bundle manifests under dsh.profile and dsh.bundle	2026-08-06 17:28:30 +08:00

README.md

bundle/ — profile plugin bundles

English | 中文

Profile bundles: npm packages whose manifest declares "dsh": { "bundle": { "patch": "./cordis.patch.yml" } }, making them installable patch layers for dsh --profile compositions (profile contract). A bundle's substance is its patch list; some also ship runtime glue plugins their patch mounts.

Package	Role	ctx key
`base/`	The shared dsh core every profile applies first	— (patch only)
`web-app/`	Browser surface: web patch layer + runtime glue plugin	mounts rows
`headless/`	One-shot task mode over base + web-app	mounts `headless-runner`

In-box bundles resolve from the dsh installation; out-of-tree bundles install into a profile through dsh plugin --profile <name> add <package>.