diagnostics

type AgentCheck struct {
	Status       Status   `json:"status"`
	Name         string   `json:"name"`
	Binary       string   `json:"binary,omitempty"`
	Protocol     string   `json:"protocol,omitempty"`
	PingResponse string   `json:"ping_response,omitempty"`
	Message      string   `json:"message,omitempty"`
	Details      []string `json:"details,omitempty"`
	Tip          string   `json:"tip,omitempty"`
}

type AuditPathStatus struct {
	OK      bool     // true when every component this path needs is healthy
	Reasons []string // one line per failing component (e.g. "claude: not found in PATH")
}

type CheckResult struct {
	Status  Status   `json:"status"`
	Message string   `json:"message,omitempty"`
	Details []string `json:"details,omitempty"` // verbose-only diagnostic details
	Tip     string   `json:"tip,omitempty"`     // remediation hint shown at all verbosity levels
}

type Deps struct {
	DB *database.DB
	// DBErr carries the error from opening the database when DB is nil. The
	// CLI populates this so checkDatabase can surface real connect failures
	// (refused, auth failed, unknown host) instead of "not configured".
	DBErr error
	// ConfigErr carries the error from loading the configuration file when
	// Settings fell back to defaults. doctor exists to REPORT broken state, so a
	// config it could not read must be a failed check here rather than a log line
	// nobody sees next to a report that says everything is fine.
	ConfigErr error
	// ConfigPath is the file the CLI actually resolved, so a report run with
	// --config names the file it read rather than the default location. Empty
	// falls back to the default path.
	ConfigPath string
	Queue      queue.Queue
	Settings   *config.Settings
	// ProbeBrowserLaunch, when set, makes the chromium check actually launch the
	// resolved browser headless (catching a binary that passes --version but
	// crashes on real startup). It spawns a browser process (~1-2s), so only the
	// one-shot CLI paths (doctor, first-run init) enable it; the server
	// /diagnostics endpoint leaves it off to stay a cheap, poll-safe readout.
	ProbeBrowserLaunch bool
}

type FixResult struct {
	Key     string `json:"key"`
	Label   string `json:"label"`
	Success bool   `json:"success"`
	Message string `json:"message"`
}

type Report struct {
	Status           Status                  `json:"status"` // "ready", "degraded", "not_ready"
	Timestamp        string                  `json:"timestamp"`
	Config           *CheckResult            `json:"config"`
	Database         *CheckResult            `json:"database"`
	Initialized      *CheckResult            `json:"initialized"`
	Queue            *CheckResult            `json:"queue,omitempty"`
	Agent            *AgentCheck             `json:"agent"`
	Browser          *CheckResult            `json:"browser"`
	SessionsDir      *CheckResult            `json:"sessions_dir"`
	EmbeddedBinaries map[string]*CheckResult `json:"embedded_binaries,omitempty"`
	Audit            *CheckResult            `json:"audit,omitempty"`   // omitted when audit integration is disabled
	Piolium          *CheckResult            `json:"piolium,omitempty"` // soft check — feature-gates audit --driver=piolium
	Tools            map[string]*ToolCheck   `json:"tools"`
	TemplatesDir     *CheckResult            `json:"templates_dir"`
	NucleiTemplates  *CheckResult            `json:"nuclei_templates"`
}

type Status string

type ToolCheck struct {
	Status  Status   `json:"status"`
	Path    string   `json:"path,omitempty"`
	Message string   `json:"message,omitempty"`
	Details []string `json:"details,omitempty"`
	Tip     string   `json:"tip,omitempty"`
}