Slash-command provider — data types#

SlashCommandSpec {
  name              string   // MUST — the command's name, without the leading "/". MUST be unique
                              // across every direct-invoke command declared by every provider in
                              // the session — a name collision at config-load time is a hard error.
  description       string   // MUST — shown in the frontend's hotkey_hints region and wherever
                              // else the frontend surfaces available commands
  input_schema      JSONSchema  // MUST — common subset per model/data-types.md#tool-schema;
                              // describes the shape of SlashCommandCall.arguments
  kind              tool.v1.ToolKind        // MUST — reused verbatim, see "Reused tool.v1 types" below
  risk              tool.v1.RiskClass       // MUST — reused verbatim
  concurrency       tool.v1.ConcurrencySpec // MUST, except for kind == interactive — reused verbatim
  streaming         bool     // MUST — true if Invoke may emit intermediate events (output_chunk,
                              // progress, partial_result) before the terminal event; false if
                              // Invoke always emits exactly one terminal event with no lead-up
  default_timeout   Duration?  // SHOULD — the deadline the kernel applies to Invoke for this
                              // command absent an agent.hcl override; omitted means the kernel's
                              // own global default applies instead
  idempotent        bool     // MUST — true iff re-running this command with identical arguments
                              // cannot produce a different end state than running it once; see
                              // tool/conformance.md#the-idempotent--retry-interaction
  // No output_schema: unlike a tool operation, a direct-invoke command is never presented to the
  // model as a callable tool — it dispatches without a model turn — so there is no LLM-facing
  // structured-output contract to validate its result against.
}

SlashCommandCall {
  id             string   // MUST — kernel-assigned, echoed in every emitted event for correlation
  name           string   // MUST — matches a SlashCommandSpec.name from this provider's
                          // GetCapabilities response
  arguments      JSON     // MUST — already-parsed JSON conforming to that SlashCommandSpec's
                          // input_schema
  call_context   CallContext  // MUST be set by the kernel — pluggableharness.common.v1.CallContext.
                          // Carries session_id/turn_id, echoed by the plugin on its own
                          // KernelCallbackService.Emit/Log calls for attribution, and
                          // working_directory — the session's cwd at call time.
}

SlashCommandEvent = oneof {
  output_chunk    { stream: tool.v1.OutputStream, data: bytes }
  progress        { message: string, fraction_complete: float? }
  partial_result  { payload: JSON }   // incremental structured output, e.g. progress lines as emitted
  exit_status     { exit_code: int, signal: string? }  // process-backed commands only
  result          tool.v1.ToolResult          // terminal, success — reused verbatim
  error           tool.v1.ToolError           // terminal, failure — reused verbatim, see
                                               // conformance.md#error-taxonomy
}