`_parse_fukui` (added in #123) stops parsing the `Fukui functions:` table at the first line that doesn't split into exactly 4 whitespace-separated tokens. xtb writes this data only to stdout (verified: a clean-directory `--vfukui` run writes no dedicated Fukui file, only `charges`/`wbo`/`xtbrestart`/`xtbtopo.mol`), so this is unavoidably a stdout-scraping parser -- but the token-count-only check is looser than it needs to be: a coincidental 4-token line immediately following the table (before the blank line that actually ends it) would be silently misparsed as a data row instead of correctly ending the table.
Tighten the row/end-of-table check to also verify the last 3 tokens actually parse as floats, not just that there are 4 of them.
`_parse_fukui` (added in #123) stops parsing the `Fukui functions:` table at the first line that doesn't split into exactly 4 whitespace-separated tokens. xtb writes this data only to stdout (verified: a clean-directory `--vfukui` run writes no dedicated Fukui file, only `charges`/`wbo`/`xtbrestart`/`xtbtopo.mol`), so this is unavoidably a stdout-scraping parser -- but the token-count-only check is looser than it needs to be: a coincidental 4-token line immediately following the table (before the blank line that actually ends it) would be silently misparsed as a data row instead of correctly ending the table.
Tighten the row/end-of-table check to also verify the last 3 tokens actually parse as floats, not just that there are 4 of them.