Files
deepseek-harness/packages/boot
imccyu 0e2097ac18 docs(boot): describe the interception layer in the generation note and README
The generation note and the app-boot README no longer claim that runtime lookup hides the shared position or recognizes profile projections: generation entries occupy their package names at $DSH_HOME/profiles/node_modules and every other name sees that directory as an ordinary ancestor. Pairing records re-recorded.
2026-09-19 14:39:44 +08:00
..
2026-09-17 21:11:19 +08:00
2026-09-17 21:11:19 +08:00

description, kind
description kind
The boot package group: how dsh app bins start — environment loading, profile and patch layers, clear startup failures, and app-owned command lines. package-group

boot/ — shared app-bin boot glue

English | 中文

Summary

The boot group launches profile applications and manages their installed composition. app-boot resolves configuration and starts the Loader, cmdline supplies application arguments, and plugin-manager exposes current-profile operations shared with the CLI. Each package README owns its details.

Table of Contents

Packages

Package Role ctx key
app-boot Boots a dsh app from a cordis.yml: loads .env, applies profile and patch layers, and reports startup failures clearly (library for the bins)
cmdline Lets the app own its flags, --help, and exit code; passes everything after the launcher's flags through verbatim cmdlineArgs, appExit
hmr Coordinates module and configuration reloads with package mutations hmr
plugin-manager Manages current-profile plugins and bundle packages through shared CLI operations pluginManager

  • dsh app — the dsh bin that consumes these helpers for its boot sequence.

  • Profile bundles — installable patch layers that dsh --profile compositions mount.

  • dsh-home-paths — the harness-home resolver both packages build on.

  • dsh-cmdline — how an app owns its flag family instead of the launcher.

  • Profile management — service methods and result records.

Dev Note

None.