v0.3.0 — install and mount in one command

v0.3.0 — install and mount in one command

dsh-llm-antigravity now ships its own profile layer, so installing it no longer
means hand-editing a patch file.

Install

dsh plugin --profile web add git+ssh://git@github.com/zhangzhangco/dsh-llm-antigravity.git

Then restart the profile — dsh.profile.bundles is only re-read at boot.

Alternatively, use the dsh-llm-antigravity-0.3.0.tgz attached to this release:

dsh plugin --profile web add /path/to/dsh-llm-antigravity-0.3.0.tgz

What changed

• cordis.patch.yml is part of the package. It carries the
  llm-antigravity insert row, so dsh plugin add appends the package to
  dsh.profile.bundles on its own. Before this release the row had to be written
  into the receiving machine's profile by hand.
• dsh.bundle.patch declared in package.json, and the file is listed in
  files. Without it the package installs as a plain dependency — present, but
  not a profile layer.
• README: one-command quick start, a "Why GitHub and not npm" section, and
  reworked tarball / linked-folder instructions.

Upgrading from 0.2.x

The hand-written row and the row this bundle now provides use the same loader
entry id, and duplicate loader entry ids are fatal at boot — DSH throws
duplicate loader entry id: llm-antigravity and the profile does not start.

So delete the insert row for llm-antigravity from your own
~/.dsh/profiles/<profile>/cordis.patch.yml and keep only your per-machine
overrides as an id-targeted patch:

- id: llm-antigravity
  config:
    textOnly: false
    skipPermissions: true

An id-targeted patch replaces the whole config value; the schema fills in
every key you leave out, so a partial override is enough. Check the composed
tree without booting anything:

dsh --profile web --dump-config

Fresh installs default to text-only

The package ships with the plugin's own defaults: textOnly: true (a tool-less
agent, so read / write / execute / network are out of reach) and
skipPermissions: false (approval kept). Flipping either one is a per-machine
decision — see "Upgrading from 0.2.x" above for where to put it. Note that with
skipPermissions: true, Antigravity's tools run outside the harness sandbox,
so DSH's permission mode does not constrain them.