Following my recent question Customizing ODT output from mk4ht oolatex and a improved process alternative described here: Use ODT Template for make4ht (which makes use of direct formatting by using existing / created styles stored in a odt document/template) I'd like to ask what needs to be done on the tex/compilation side with make4ht to connect a style in the odt template to a custom command or environment in a latex file.
For example:
I create a style called test in a odt file called basic.odt.

I compile a tex file (see below for MWE) with "C:\texmfs\install\miktex\bin\make4ht.exe" -f odt+odttemplate "test.tex" "odttemplate=./refTemplates/basic.odt" which compiles my tex file with make4ht with a pointer to the template odt file.
MWE:
\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{xcolor}
\definecolor{specialtextcolor}{rgb}{0,0,1}
\newenvironment{test}
{\par\begin{color}{specialtextcolor}}
{\end{color}}
\begin{document}
This is a normal paragraph.
\section{Custom style access test}
test text in the first level of section hierarchy
more text
\medskip
\begin{test}
This is a test environment.
\end{test}
\medskip
more text
\end{document}
The main concern is that the output files don't reflect that they used the test style.
The first point to clarify:
What does make4ht require to let the lua script take over and extract the required css formatting from the style in the template odt file? I was hoping to use these odt template files and move away from the Configure commands in the cfg files, which I never successfully modified to work for other styles (see quote example in Customizing ODT output from mk4ht oolatex... I couldn't even rename all instances in tex and cfg files from
quotetocmdquotewithout compile errors).Since certain styles (like section) are accessible without any interface cfg manually created or customized I assume either
a) no custom cfg files are needed and my test commands/environments are to minamalistic or b) these have already been pre-configured (like in a class or sty file)? If it is the latter where are these documented or stored so I can learn from these pre-existing examples?

make4htshould be available in few days in distributions. – michal.h21 Jan 23 '19 at 11:35zip not recognized as an internal or external commandNeither the zip error or any further messages about xtpipes are in the log file. – EngBIRD Jan 23 '19 at 12:59zipis necessary for the ODT file building. – michal.h21 Jan 23 '19 at 13:03miktex-zippackage? – michal.h21 Jan 23 '19 at 13:05miktex-zip-binmiktex-bzip2-bin-2.9andmiktex-zzip-bin-2.9– EngBIRD Jan 23 '19 at 13:38miktex-zipcommand work? It should be detected bymake4htwhen normalzipis not present. What version ofmake4htdo you have? (make4ht -v) – michal.h21 Jan 23 '19 at 13:49miktex-zip -visThis is Zip 3.0 (July 5th 2008), by Info-ZIP.. The results ofmake4ht -vismake4ht version {{version}}. I'm guessing it may be necessary to aliasziptomiktex-zipbecausezipreturns'zip' is not recognized as an internal or external command, operable program or batch file.– EngBIRD Jan 23 '19 at 16:01make4htshould usemiktex-zipif it cannot findzip, so that's strange. anyway, simplest solution is to provide a zip command, as you said. – michal.h21 Jan 23 '19 at 17:39The process tried to write to a non existent pipe.I don't see any missing pipe packages, so I must have a problem as you initially suspected with xtpipes. – EngBIRD Jan 23 '19 at 18:45zipcommand anyway. I don't have access to Windows so I cannot test it no Miktex myself. Maybe you should delete the development version ofmake4ht, as the version included in Miktex worked – michal.h21 Jan 23 '19 at 18:49