internal/

Package appini parses Gitea/Forgejo app.ini into the bits gitea2forgejo cares about: paths, DB config, storage config, security keys.

Package cleanup removes the on-disk artifacts left behind by `gitea2forgejo dump` (local work_dir) and the remote source scratch directory (via SSH + docker exec when Docker was used).

Package client wraps the Gitea SDK for both Gitea (source) and Forgejo (target).

Package config loads the gitea2forgejo YAML configuration and resolves "env:VAR" references.

Package dump harvests the source instance into a manifest and (eventually) on-disk tarballs.

Package initcmd implements `gitea2forgejo init` — it SSHes to the source host, reads the Gitea app.ini, extracts as many config.yaml fields as possible, and writes a ready-to-run config file.

Package manifest is the shared inventory type written by `dump` and read by `supplement` / `verify`.

Package migrate is the top-level orchestrator that runs the whole Gitea → Forgejo migration end-to-end.

Package preflight runs read-only checks before a migration: versions, SSH reachability, DB connectivity, disk space, and the SECRET_KEY warning.

Package remote provides SSH exec + SFTP file ops against source/target hosts.

Package restore performs Phase 2 (ingest) on the target Forgejo host.

Package selfupdate queries GitHub Releases for a newer version of gitea2forgejo and replaces the running binary when the operator accepts.

Package verifydump inspects a dump in work_dir and answers "is this safe to restore?" by cross-checking the on-disk artifacts against the harvested source manifest.