internal/

Package build assembles the docker build context for a project: the generated Dockerfile, the launcher script, and any skill/agent files COPYed by the generated build.

Package builtins ships byre's built-in skills embedded in the binary and materializes them into ~/.byre/skills/ so they are loadable (and inspectable and editable) like any hand-dropped skill.

Package commands implements the byre subcommands.

Package config loads and resolves byre's configuration cascade:

complete.go owns the flows that finish an editing session: save/assemble, dirty tracking behind the quit confirm, and the $EDITOR round-trip.

Package deliver implements `byre deliver`: getting files from the host into a running box's /inbox over an exec stream (no mount, no host-side state).

Package gen renders the byre Dockerfile from a resolved configuration.

Package lock provides a per-project setup mutex via an advisory file lock.

Package onboard implements byre's first-run picker: when `byre develop` runs in a project with no byre.config, it lets the user choose a template × agent (with their favourites pre-selected) and writes the choice to byre.config — and, optionally, saves it as their default (favourites) in default.config.

Package project derives byre's per-project identity and on-disk locations.

Package runner drives a container engine (Docker or Podman) via its CLI.

Package skills loads skill bundles from ~/.byre/skills/<name>/ and resolves their contributions to the layers byre controls: build (per-skill Dockerfile block), runtime (mounts/env/caps/run_args), state (named volumes), agent context, and — for agent skills — the launch command.