Hardware Thread.
You're not the first to find this under documented, but it's trivial to find with a web search.
It's a term relatively unique to RISC-V. Terms like CPU or core got fuzzy in recent times from things like hyper threading. AIUI, the term was used to not strictly require a complete execution unit, but any combination of magic that makes software think there are independent units. If you had a way to store eight register files (and probably a little extra state, such as whether it's WFI) and ran one opcide from each on each eighth opcode, you might convince software you had eight HARTs.
You'd die on a multithreaded benchmark or even real world use and the experience would be incredibly terrible, but I think that's approximately allowed. (That might be vaguely useful if you were simulating a chip on bigger metal or you chose something less extreme or you interleaved based on memory misses or something less dumb than round robin or such.