muster

type Config struct {
	// Tools maps a tool name, as muster exposes it (x_<server>_<tool>, or
	// core_auth_login), to its sequence of answers: the Nth call gets the
	// Nth answer and the last one repeats.
	Tools map[string][]ToolResponse `yaml:"tools"`
	// Login is the userinfo answer's email; e2e-engineer@example.com when
	// left out.
	Login string `yaml:"login"`
	// Bearer is an access token the MCP endpoint accepts besides the ones it
	// issued: the scenario's keyring token.
	Bearer string `yaml:"bearer"`
	// RefreshToken is a refresh token the token endpoint accepts besides the
	// ones it issued: the scenario's keyring refresh token.
	RefreshToken string `yaml:"refreshToken"`
}

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

type ToolResponse struct {
	// Args, when given, are arguments the call must carry with these values
	// (compared as JSON); a call that does not is answered with a tool error
	// naming the difference, so the scenario fails visibly.
	Args map[string]any `yaml:"args"`
	// Result is the tool's answer: a mapping or list becomes the structured
	// content (and the JSON text content), a string the text content.
	Result any `yaml:"result"`
	// Error makes the answer a tool error with this text.
	Error string `yaml:"error"`
}