mockllm

type Handler struct {
	// contains filtered or unexported fields
}

type Request struct {
	Protocol string
	Stream   bool
	Body     []byte
}

type Scenario struct {
	Name  string `json:"name,omitempty"`
	Steps []Step `json:"steps"`
	// Repeat replays the last step for every call past the end instead of
	// failing. It exists for the deployment smoke, which asserts on outcomes
	// rather than on how many turns reaching them took, and must stay opt-in:
	// everywhere else, a call past the end of the script is the finding.
	Repeat bool `json:"repeat,omitempty"`
}

type Server struct {
	*Handler
	// contains filtered or unexported fields
}

type Step struct {
	Text      string     `json:"text,omitempty"`
	ToolCalls []ToolCall `json:"tool_calls,omitempty"`
	Usage     *Usage     `json:"usage,omitempty"`
	// Status and Error make the step a provider failure instead of a reply.
	Status int    `json:"status,omitempty"`
	Error  string `json:"error,omitempty"`
	// DelayMS holds the reply back before writing it, so a run stays mid-turn
	// long enough for a suite to act on it. A failure step delays too: a
	// provider that fails slowly is what a timeout looks like from here.
	DelayMS int `json:"delay_ms,omitempty"`
}

type ToolCall struct {
	// ID is what the tool result will reference. Left empty, the handler names
	// it after its position so a scenario does not have to invent ids.
	ID   string         `json:"id,omitempty"`
	Name string         `json:"name"`
	Args map[string]any `json:"args,omitempty"`
}

type Usage struct {
	PromptTokens     int `json:"prompt_tokens"`
	CompletionTokens int `json:"completion_tokens"`
}