Yichen Jiang
bc0ecae21f
The dsh installation lists under `dsh.optionalBundles` the bundles it ships for a person to switch on. The plugin manager reports them as `optional`, and the Web plugin page shows them first, in a built-in group with an official tag, off until selected and never removable. Agent Teams ships this way, so a blank profile offers both of its layers. Default-product isolation, the workspace constraints, and the packed-install check accept that one dependency edge and nothing else experimental. A bundle's title and one-liner come from `dsh.title` and the new `dsh.description`, else from the package name and `description`. A dependency without a bundle patch is no longer listed unless the profile selects it. The install dialog asks for a package name or address; a guide under the field shows the three accepted forms with an example each and ends in a security warning, and the copy no longer speaks of a plugin ID.
7 lines
436 B
YAML
7 lines
436 B
YAML
# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
|
|
# side as of the last confirmed-consistent state. Both languages carry equal authority;
|
|
# after editing either side, bring the other along and re-record with:
|
|
# pnpm run verify-translation-pairing --write docs/user/develop/basic/publish.md
|
|
publish.md: da3a80a809a2e01b5f5914178a8d34e8c4453fc1
|
|
publish.zh.md: 3baa952d42c3a223b8ce1aeea326799e10cbe1f5
|