Should flag "death throws" when "death throes" is intended

"Death throes" (violent movements or intense pain right before dying) is often written with the much more common word "throws":
- Finally, the sensor has been in it's **death throws** of tons of sensor errors and I just haven't gotten around to changing it yet.
- It's all in its **death throws**.
- might be 'hanging onto' the old master IP when it is in its **death throws**.
- There is a point where nobody cares about your **death-throws**.

But there are also false positives that are not rare:
- After a successful handshake, a worker **death throws** WorkerCrashedError
- a single transient daemon **death throws** away an entire long run
- Red screen of **death throws** error: 'undefined is not a function (evaluating 'this2.props.myTextAction({prop:'value', value: value})')

No file or test entry point is named in the issue, so first locate the existing rule or test for confusing-word and phrase corrections. Add coverage for intended “death throes” uses, including the hyphenated form, while preserving the listed verb constructions as non-matches; done means the intended cases are flagged without those false positives.

Written by the indexing model from the issue text.