REST and CLI management

All management clients use the same authority. The primary REST surface is:

GET  /v1/plugins
GET  /v1/plugins/{id}
GET  /v1/plugins/{id}/why
GET  /v1/plugins/{id}/events
GET  /v1/plugins/{id}/support-bundle
POST /v1/plugins/commands

The exact JSON request is governed by contracts/v2/plugin-command.schema.json. Read the current plugin revision before mutation, generate a unique command ID, and send the expected revision. Never synthesize fields not accepted by the schema.

{
  "command_id": "cmd-001",
  "expected_revision": 7,
  "operation": "enable",
  "plugin_id": "dev.formless.binance-market",
  "arguments": {}
}

The example illustrates command semantics; validate it against the repository schema used by your Host version before sending. Authentication is required. Do not place bearer tokens in shell history or documentation.

formless-pluginctl exposes the same operations for operators. Use its built-in help from the installed release so flags match the exact Host build:

formless-pluginctl --help