import org.hibernate.search.backend.impl.WorkVisitor

AFAICT there's some transformation required for the LuceneWorks, so there's a custom visitor impl https://github.com/infinispan/infinispan/blob/master/query/src/main/java/org/infinispan/query/indexmanager/LuceneWorkTransformationVisitor.java

import org.hibernate.search.bridge.builtin.impl.NullEncodingTwoWayFieldBridge;
import org.hibernate.search.bridge.builtin.impl.TwoWayString2FieldBridgeAdaptor;
import org.hibernate.search.bridge.util.impl.ContextualExceptionBridgeHelper;

Can those be 'promoted' to reusabe bridges along with CalendarBridge, UriBridge, et. al?

import org.hibernate.search.engine.impl.LuceneOptionsImpl;
import org.hibernate.search.engine.metadata.impl.DocumentFieldMetadata;

Infinispan Query has a modus operandi where schema is defined in a google protobuf message. LuceneOptionsImpl is used to produce Lucene Documents "by hand" without relying on @Indexed, @Field, etc. This is where all happens: https://github.com/infinispan/infinispan/blob/master/remote-query/remote-query-server/src/main/java/org/infinispan/query/remote/indexing/IndexingTagHandler.java

import org.hibernate.search.impl.SimpleInitializer

From the javadocs: "Initialization strategies might vary according to the integrating framework; when integrating with Infinispan (as Infinispan Query) no initialization is needed"
I supposed this can be promoted to spi level?

import org.hibernate.search.impl.SearchMappingBuilder;

Not sure about this one (how can it be replaced). It is being used inside a custom SearchConfiguration https://github.com/infinispan/infinispan/blob/master/query/src/main/java/org/infinispan/query/backend/SearchableCacheConfiguration.java#L56 Sanne Grinovero, any thoughts?

import org.hibernate.search.indexes.impl.DirectoryBasedIndexManager;
import org.hibernate.search.infinispan.impl.InfinispanDirectoryProvider;

There's a custom index manager implementation inside infinispan called org.infinispan.query.indexmanager.InfinispanIndexManager that relies
on DirectoryBasedIndexManager base class but overrides the BackendQueueProcessor and the DirectoryProvider with its own classes

import org.hibernate.search.util.logging.impl.Log;
import org.hibernate.search.util.logging.impl.LoggerFactory;

Those can be replaced by infinispan loggers, not sure why they are being used on infinispan side