crew-lint

Install ruff and mypy with pip, then run `ruff check .` for linting and `ruff format --check .` for formatting. Add mypy only where type annotations already exist, since enabling it on an unannotated legacy codebase produces thousands of unread findings.

Add the linter command as a path-scoped rule in `.crew/verify.json`, mapping file globs like `**/*.py` to the check commands. Path scoping keeps gates fast so a Python change never waits on unrelated tooling like terraform init.

Use phpstan starting at `--level=1` and raise the level one step at a time as separate tickets, plus phpcs with the PSR12 standard for style. Starting phpstan at level 8 on legacy code produces an unreadable wall of findings and the gate gets disabled.

Baseline the existing debt instead of fixing it in the same change: use ruff per-file ignores, phpstan's `--generate-baseline`, or PSScriptAnalyzer's settings file. The gate starts green on day one, and the baseline burns down as its own tickets.

Yes, install it with `Install-Module -Name PSScriptAnalyzer` and run `Invoke-ScriptAnalyzer -Recurse`. Fail the gate on Error severity only at first, since Warning on legacy scripts usually yields hundreds of findings; promote Warning once errors reach zero.