Yichen Jiang
a21644af59
The Gateway serves the goal domain as Remote endpoints, and a Remote method picks its receiver Service from a generated descriptor — `clear(agent, ref)` takes its agent as a PARAMETER, so the invocation is direct and the receiver resolves on the host. Behind the preset's entry-local realm there was nothing to resolve, and every browser goal call answered `service-unavailable`: the composer's Clear goal button left the bar on screen. That is the `bash-env` criterion read from the other side. Injection is not the only host relationship a Service can have; being READ from a host row is one too. The registry is keyed by session, so one host instance serves every session exactly as it did before presets. The preset keeps the model-facing tool, which is the choice a preset is for. Also reverts the cold-transcript presenter resolve: resuming an agent to reach its presenters made the context meter drop its cache and token counts on every cold-opened session, trading one silent degradation for another. The card degradation it addressed is diagnosed and still open.
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>.