package buildstep

// ModuleTree is what a merge holds of one module directory, as a build module's preview answers it (novox/hq ADR 0484
// clause 3, as ADR 0593 §2 changes it): its git tree id, the sha256 of its module.json, the sha256 of each lock file it
// has (go.sum, package-lock.json), and, of a module whose every artifact names its paths, each named path's git object
// id at the commit. The indexer alone computes from them (the named tree, the fingerprint); the build module's runner
// (mesh-build-go's buildstep.ModuleTrees) fills them.
type ModuleTree struct {
	Tree     string            `json:"tree"`
	Manifest string            `json:"manifest"`
	Locks    map[string]string `json:"locks,omitempty"`
	Paths    map[string]string `json:"paths,omitempty"`
	// Packages are no longer filled (ADR 0593 §2): kept so a preview written before still decodes.
	Packages []string `json:"packages,omitempty"`
}