internal/

Package config loads LocalOps' own server-side configuration - not to be confused with the client SDK's config (client.Config), which configures how an *external* app talks to this server.

Package health runs the periodic sweep that turns "no heartbeat in a while" into a Slack alert (README §8: a stuck task is a good candidate to raise through the same alerting path as watcher failures), and backs the plain GET /health liveness endpoint.

Package notifications implements the generic, undebounced "force notify" path: any script or caller that has already decided a message is worth sending posts it here, and it goes straight to Slack (via internal/notify) with no state machine, no threshold, no transition detection - that's the whole point of it existing alongside Watchers.

Package notify owns LocalOps' one piece of outbound notification: Slack (README §13.4).

Package scheduler implements the minimal recurring-task mechanism from README §17: fixed-interval schedules that create a normal Task when due.

Package server wires the REST API (README §14) on top of Echo.

Package slack verifies inbound Slack requests (slash commands).

Package storage owns the single SQLite database connection and applies migrations.

Package system exposes basic host health (README §11): CPU, RAM, disk, uptime, load.

Package tasks implements the generic task model (README §4, §9): a small fixed set of fields plus an arbitrary JSON `details` blob, persisted with a lifecycle event history.

Package watchers implements the Watcher model (README §13): standing up/down conditions (an SSH tunnel, a reachability ping, a systemd service) that don't fit the Task lifecycle because they have no natural end - only state transitions matter.