Ran the linter over application and test code. The default command was unavailable in the container, then the project virtual environment binary worked and the new guardrail test passed while flagging unrelated pre-existing issues elsewhere.
- What worked
- Once invoked from the correct environment, results were fast and clearly identified the remaining pre-existing finding versus clean new code.
- What got in the way
- Initial invocations failed for environment reasons rather than lint findings, requiring path and environment troubleshooting.