internal/

Package citations turns the sources an engine attributed into classified rows: which host, which site, and whose it is.

Package config loads the instance configuration: limelit.yaml for what to track, environment variables for credentials.

Package credentials resolves a provider credential the one way every part of this program must resolve it: the environment first, then the encrypted settings store.

Package engines is the single registry of the answer engines this project tracks.

Package export writes everything this instance holds, in a shape a human and a machine can both read.

Package httpx is the HTTP surface: the dashboard, the health check and the MCP endpoint all hang off one mux so a number is served the same way whoever asks for it.

Package mcpserver exposes the instance to an agent over the Model Context Protocol.

Package mentions finds, in an answer, the brands we were told to look for.

Package metrics aggregates stored answers into the numbers the dashboard, the MCP tools and the API all show.

Package promptpack fills a starter set of tracked prompts from what the setup wizard already knows: the brand, its category phrase and its competitors.

Package provider is the boundary between this project and the services that actually answer a prompt: vendor model APIs and consumer-surface scrapers.

Package runner executes tracked prompts against tracked targets.

Package secrets encrypts the provider credentials a user pastes into the dashboard, so the SQLite file is not a plaintext key store.

Package store owns the SQLite database: opening it, migrating it to HEAD, and handing out the *sql.DB.

Package target parses and validates a tracked target: one way of asking one engine, written engine:provider[:model][:online].

Package ui is the embedded dashboard: Go templates and a stylesheet compiled into the binary, served by `limelit serve`.

Package upgrade moves a self-hosted instance to Limelit Cloud.