Unused Concepts don't show up in the union type

If you create a `Condition` but don't use it in the evaluator, it breaks the resulting `LudiekCondition` union. It seems there needs to be at least a public method on the `LudiekEvaluator` that uses `Condition` as an argument for it to end up in the final union.

This is a very dangerous bug as any consuming concept can completely break the type system, leading to hard to debug situations

Look at how the LudiekCondition union type is generated, likely in a type generation or code analysis module. Examine the Condition concept definition and the LudiekEvaluator to understand the linkage. The fix likely involves ensuring unused Condition concepts are still included in the union, possibly by modifying the type generation logic.

Written by the indexing model from the issue text.