internal/

Package aireview identifies webhook events from a "bot reviewer" (any account whose sender.type is "Bot") and exposes two orthogonal policies over that identity.

Package app is the composition root for notifycat.

Package botpr classifies pull requests opened by dependency-update bots (Dependabot, Renovate) so the notifier can render a compact Slack message instead of the standard "please review" format, and tell routine version bumps apart from security-advisory updates.

Package cleanup runs the scheduled, in-process pruning of stale rows from the slack_messages table.

Package config loads runtime configuration from a single config.yaml file.

Package digest posts the scheduled stuck-PR reminder: a per-channel summary of open PRs that nobody has touched since before today.

Package doctor runs end-to-end preflight diagnostics for a notifycat installation.

Package github is a minimal GitHub API client covering only the endpoints notifycat needs for validation.

Package githubhook authenticates and parses inbound GitHub webhook requests.

Package mappings owns the declarative repository → Slack-channel configuration: parsing mappings.yaml, the in-memory Provider used at runtime, and the mappings.lock cache that records which entries have been validated.

Package pullrequest holds the domain model for GitHub pull-request events and the handlers that update Slack in response.

Package reconcile backfills the closed_at column on slack_messages rows whose PR is no longer open on GitHub.

Package slack talks to the Slack Web API for the PR notifier: posting, updating, and deleting messages, adding emoji reactions, and composing the blocks of the notification.

Package smoke drives an end-to-end delivery test against a running notifycat stack.

Package store owns the database schema, GORM models, repositories, and the goose-driven migration runner.

Package validate verifies that a repository → Slack-channel mapping is usable end-to-end before GitHub fires a real PR event: the mapping row exists, the channel ID is well-formed, the Slack bot has the right scopes and is a member of the channel, and (when GitHub credentials are available) the webhook is subscribed to the events notifycat needs.