Crate agent_profile 

agent-profile — select and launch profiles for multiple coding agents.

The authoritative design is agent-profile-implementation-spec-v3.md at the repository root. Each module below is one layer of the spec §4 architecture. SP0 (the scaffold) creates them empty; later sub-projects fill them in.

agent-profile owns profile selection. The coding agent owns authentication and agent-specific configuration. (spec §1)

Modules

adapter

Agent adapters: the adapter trait and registry (spec §2, §4, §38), capability and evidence metadata (spec §3, §28), profile presence (spec §8), lazy initialization (spec §9) and argument conflicts (spec §21). SP2 design §4-§6.

cli

CLI grammar: launch syntax, wrapper options and reserved command words (spec §5; SP1 design §4) and the repository commands (SP3 design §7).

config

The application root (spec §7), config.toml strict reads (spec §17) and locked, atomic writes (spec §18, §18.1).

doctor

doctor: the check model and the host and repository checks (SP5c design §4, §5.1, §5.2, §6).

error

Structured errors and their exit codes (spec §33).

exe

Executable discovery (spec §20): an explicit configured override, then the absolute entries of PATH.

json

The serialisable view layer behind --json (SP5b design §3.1 to §3.7).

launch

LaunchPlan (spec §4), environment overrides (spec §22), launch semantics (spec §23, §24) and the launcher API (spec §25).

lifecycle

The profile lifecycle: materializing and deleting what an adapter owns for a profile (SP5a design §3).

name

Profile-name validation (spec §6) and the reserved command words (spec §5.3).

output

Human output: the dry-run and --verbose report (spec §26, SP1 design §7.4, SP2 design §7.3), the repository command reports (SP3 design §7.5) and redaction (spec §22). JSON output (spec §32) is built in json (SP5b).

repo

Repository discovery (spec §13) and canonical repository identity (spec §14). SP3 design §5.

repositories

The repositories report: every stored repository mapping, classified by whether it still applies (SP5b design §4). Classification never fails; a mapping that cannot be examined is reported, not raised.

resolve

The single profile resolver shared by every command (spec §12, SP3 design §4.3).