fix(compiled-languages-rule-fine-tuning): Updates the rules to acoomo…

[vnsamy-code]

Thank you so much for making this, I enjoyed working with this tool. 🙏

---

PR tldr;

Basically the RULES at the moment does a tdd-guard block loop on compile errors from compiled languages like Swift/Go/Java etc., This PR adjusts the rules file to accomodate the compiled languages.

I was bit torn between updating the RULES vs having a custom instructions.md file, but then chose the former based on the bare minimum type information need for the compiled languages.

---

Add a test => (1) fails => add the type in the compiled language => tdd guard blocks calling 'over implementation.'
We cannot escape this loop unless we turn off guard off momentarily with tdd-guard off and you let the type finish and continue the TDD loop. No data/test.json file created and loop continues.

Also see: https://github.com/nizos/tdd-guard/pull/80/files#diff-5774d006611631734758deb6a9dfeb2e8d1cc694f425c0d343bc3e35b4f32d67R31

Local test results with -- Go:

1. Compile error failure captured in the test.json file.

COMPILE_FAILURE_test.json

2. Adds a type with fields (anticipatory violation)

3. Takes a step back and does a bare minimum type implementation. Fields added after the next failure. Guided.

STOPPED_AT_COMPILE_SAFE_ASSERT_FAILURE.json

4. Final step with bare minimum to pass the test.

PASS_test.json

---

AI Generated instructions below:

TESTING_COMPILED_LANGUAGE_SUPPORT.md

AI Generated Sample Project guided by tdd-guard:

todo-app.zip