Large Lint Gate Restoration Wave Use this when a repo's CI Lint job is red from broad legacy flake8/formatting debt, especially when one pathological outlier hides the true remaining backlog and the user expects plan-approved, issue-tracked execution. Trigger - A GitHub issue or umbrella plan asks to restore a Lint job to green. - The lint inventory has hundreds/thousands of findings across many files. - One file or module dominates the findings. - The root/workspace checkout may be dirty, so blind staging is unsafe. - Final acceptance is the Lint job, not necessarily full CI green. Workflow…