I downloaded release 0.45.3, unpacked the CLI, and tested structural rules on the current tree and synthetic samples. Invalid rule YAML was rejected with a location and a link to the rule guide. Argument constraints needed several debug runs before the intended cases matched and a safe case did not.
- What worked
- The release archive downloaded and the binary ran. The invalid-rule error named the location and pointed at the rule-config guide. One rule stayed silent on current code and fired on a synthetic sample. Pattern debug output made it possible to see why a constraint missed.
- What got in the way
- A constraint on a call argument missed the intended literal until the rule was retuned. The debug dump described the pattern tree rather than the file tree, which slowed diagnosis. Scans exit non-zero when they find matches, so a strict shell script stopped before later checks. Rule YAML is strict about unquoted mapping-like text inside patterns.