detect

type ComposeEnv struct {
	// File is the absolute path to the compose YAML.
	File string
	// Project is the `podman compose -p` project name — unique per env file
	// so parallel test targets never collide on container/network names.
	Project string
	// ID is the parsed identifier, e.g. "go.internal" or "pnpm".
	ID string
	// Ports are the env-var names the compose file binds on the HOST side of
	// a `ports:` mapping (e.g. POSTGRES_PORT, GRPC_PORT) — exactly the ports
	// the host test process talks to. The runner allocates a free TCP port
	// for each so parallel targets never collide, replacing setup-env.sh's
	// node/get-port-please randomisation.
	Ports []string
	// Refs is every ${VAR} the compose file interpolates (host-exposed or
	// not). The runner fills known test defaults (POSTGRES_USER/PASSWORD/DB/
	// HOST) for any it references, so an internal-only postgres — which has
	// no host port and thus no entry in Ports — still gets credentials.
	Refs []string
	// Profiles maps a compose `profiles: ["x"]` value to the service name
	// that carries it (e.g. "rest" → "service-json-keys-rest"). `run` uses
	// this to know which compose service to bring up when a target is
	// requested in dockerised mode (`podman compose --profile x up <svc>`).
	Profiles map[string]string
	// Services lists every compose service declared under `services:`, in
	// source order. The runner uses it to compute the set of services to
	// bring up at env-up time — in global mode it skips any sibling service
	// that is also being run from its own repo (avoiding duplicates).
	Services []string
}

type Kind string

type Target struct {
	Kind Kind

	// Name is the unit's short identity within its directory, e.g. the module
	// name (go), the script name "build:rest" (pnpm), or "rest.Dockerfile"
	// (podman). It is NOT unique on its own — pair it with RelDir.
	Name string

	// Service is the owning repo/module short name (e.g. "service-json-keys").
	// Set for `run` targets so the UI can disambiguate identically-named
	// entrypoints across services (a "rest" exists in every service). Empty
	// for build/test where Name+RelDir already suffice.
	Service string

	// RelDir is the target's directory relative to the scan root ("." for the
	// root itself). Used for display grouping and de-duplication.
	RelDir string

	// Dir is the absolute working directory the command executes in.
	Dir string

	// Detail is a one-line, human-readable summary shown under the target in
	// the menu and report (the resolved image tag, the script body, …).
	Detail string

	// Cmd and Args are the exact process to spawn, executed with Dir as CWD.
	Cmd  string
	Args []string

	// Env, when non-nil, is a podman-compose environment that must be up
	// before the command runs and torn down after. Only test targets set it.
	Env *ComposeEnv

	// ComposeService is the compose service name that would run this target
	// dockerised — populated by `run` detection when the target's name
	// matches a profile in its env's compose file (e.g. "rest" →
	// "service-json-keys-rest"). Empty means dockerised mode cannot run this
	// target (one-shots like migrations / rotate-keys / init have no compose
	// service); the runner falls back to local exec for those.
	ComposeService string
}