The fingerprint, named tree and package versions move from mesh-sdk into the indexer's internal/fingerprint (ADR 0593 §2). The indexer publishes each reached mesh Go module's package digests from the forge's listing in its new packages state, keeps the imports a done build reports, and writes the import form only when an input differs from the build that reported them (§4), so the form change costs no rebuild and a package merge moves only its importers (§3). Candidates take the same form against the group's member heads (D1-D4). Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL