Multiple `@enum` annotations in a single comment causes unexpected output

	/***
	 * Piece flag for `Spring.UnitScript.Explode`.
	 * 
	 * @enum SHATTER integer
	 * @enum EXPLODE integer
	 * @enum EXPLODE_ON_HIT integer
	 * @enum FALL integer
	 * @enum SMOKE integer
	 * @enum FIRE integer
	 * @enum NONE integer
	 * @enum NO_CEG_TRAIL integer
	 * @enum NO_HEATCLOUD integer
	 * @enum RECURSIVE integer
	 */

---Piece flag for `Spring.UnitScript.Explode`.
---
---@enum SHATTER integer
---
---integer
---
---integer
---
---integer
---
---integer
---
---integer
---
---integer
---
---integer
---
---integer
---
---integer
SHATTER = {}

Start by locating the annotation parsing entry point that handles repeated @enum lines, then compare the C-style comment with the generated Lua shown in the issue. Done means the multiple enum annotations produce the intended Lua output rather than the repeated blank and integer entries shown.