Pushes the canonical fragment library to the connected browser extension and waits for its ack, so a pipeline seeds (or replaces) the fragment set that later machine:extension:run and machine:extension:sequence steps reference by id. The fragments are plain workflow JSON files in the extension's wire schema, one workflow per file.