Remove unused validation types and clarify cycle detection semantics

[Copilot]

Addresses review feedback asking whether the suggestion was about code hygiene, code improvement, or test coverage, and whether cycle detection is correct.

Answer: This is a code hygiene fix. Cycle detection is correct by design—indirect cycles are allowed, only direct self-reference is rejected.

Changes

• Remove unused ValidateM type alias (was never used in implementation)
• Remove unused emptyEnv function (was never called)
• Remove unused ValidationEnv type entirely (planned for cycle detection but unnecessary since indirect cycles are intentionally allowed)

Cycle Detection Semantics

-- Direct self-reference → rejected with SelfReference error
"[a | a]"  -- ❌ Invalid

-- Indirect cycles → allowed by design  
"[a | b], [b | a]"  -- ✅ Valid

All 18 semantics tests pass, confirming validation logic works correctly.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.