editing-cordis-compositions

Copy a shipped preset with the roster service's copy(from, id, name) into the user root under $DSH_HOME/.agent-presets/, then edit the copy's agent.cordis.yml and preset.yml. Never edit shipped presets in place; the copy is loadable and lands in the writable root.

A consumer row left outside its provider's isolate realm resolves the host registry, which the preset never populated, so the row never activates. Mount-validate with standingKeyFor(id); it reports rows that did not activate and the service they were waiting for.

Add a customSkillDirs entry to the preset's skill-filesystem row pointing at its own skills/ directory, resolved relative to baseUrl so it stays relocatable. Preset-bundled skills are not auto-discovered; without this entry the agent never sees them.

No. A service published without an isolate realm lands in the process-global realm, so the second session mounting the preset collides with the first and the mount is rejected. Wrap the provider and all its consumers in one group with an isolate realm.

In dsh-in-ellamaka the @deepseek-ai/* scope is reserved for the official closure; packages borrowing that scope without living in the closure cannot resolve. Author self-owned plugins under a scope you control, such as @wopal/* or your organization's scope.

Anything shared across sessions belongs host-side: registries, persistence, session query, sandbox and approval stack, model route, and the subagent registry. A preset holds only what one session contributes, such as its tool plugins, persona, and compaction policy.