pax-beehive / dsh-hub

DSH Hub Preset workflow

Use the installed dsh-hub CLI as the sole local execution authority.

Discover and assess

1. Search Plugins with dsh-hub search <query> --json or Presets with
   dsh-hub profile search <query> --json.

2. When a publisher has just released a version, run
   dsh-hub sync <package> --json to index it immediately instead of waiting
   for the scheduled npm scan. It reports the Hub slug and latest version.

3. Inspect a Plugin through `dsh-hub info <package> --version <selector>
   --json`. Report the resolved exact version, source, DSH compatibility,
   runtime surfaces, and security assessment.

4. Before recommending a Preset change, run `dsh-hub profile doctor
   [slug] --profile <name> --jsonanddsh-hub profile diff [slug]
   --version <version> --profile <name> --json` when a remote target exists.

Install a Plugin

1. Create a plan with `dsh-hub install <package> --version <selector>
   --profile <name> --plan --json`.

2. Present the exact install source and version, security assessment, target
   Profile, and current-state precondition.

3. Obtain explicit confirmation for that plan ID.
4. Run dsh-hub operation apply <plan-id> --json and report the final event.

Install or upgrade

1. For first application, create the plan with `dsh-hub profile apply <slug>
   --version <version> --profile <name> --plan --json`. For an existing
   Preset, use `dsh-hub profile upgrade [slug] --version <version>
   --profile <name> --plan --json` so the review includes a diff.

2. Show the user the target Profile, exact Preset Release, ordered Plugins,
   exact Plugin versions, required local inputs, and current-state precondition.

3. Obtain explicit confirmation for that plan ID.
4. Run dsh-hub operation apply <plan-id> --json.

5. Report the final NDJSON event. Never claim success before
   operation.completed.

Run dsh-hub profile doctor --profile <name> --json after apply or upgrade and
report any remaining local or remote drift.

Plans expire after 30 minutes and fail if the target changed after planning.
Create a fresh plan when either condition occurs.

Share the current Preset

1. Create a plan with `dsh-hub profile share <slug> --profile <name>
   --version <semver> --plan --json`.

2. Present the exact runtime, ordered layers, versions, patch, declared input
   keys, and local Preset hash. Stop on file:, link:, workspace: or
   another unpublished local Plugin source.

3. Obtain explicit confirmation and apply the returned plan ID through
   dsh-hub operation apply <plan-id> --json.

Never upload environment values, credentials, session data, logs, or Plugin
code.

Recover

Use dsh-hub profile history --profile <name> --json to inspect revisions.
Create the rollback with `dsh-hub profile rollback [revision] --profile <name>
--plan --json`, present the selected complete revision, then obtain explicit
confirmation before applying its plan ID. Rollback restores Profile files and
installed dependencies; it does not reverse Plugin data migrations or external
effects.