Use a Plugin Package

Packaged plugins are the deployment-oriented way to run executable providers.

Reference The Package

integrations:
  example:
    plugin:
      package: ./dist/example-provider.tar.gz
      config:
        greeting: Hello from packaged plugin

plugin.package accepts:

• a local directory
• a local .tar.gz
• an HTTPS URL (.tar.gz)

Init It

gestaltd init --config ./config.yaml

This validates the manifest, selects the current platform artifact, installs the package in-place, and records the prepared result in gestalt.lock.json.

Validate The Prepared Config

gestaltd validate --config ./config.yaml

Validation uses the prepared plugin state instead of re-resolving the package every time.

Start From Locked State

gestaltd serve --locked --config ./config.yaml

That is the normal production path for packaged plugins.

Refresh A Remote Package

If plugin.package points at an HTTPS URL and the remote archive changes, rerun:

gestaltd init --config ./config.yaml

Remote packages are intentionally refreshed during explicit init.