chore: add linting workflow

[TheMagamed78]

Add a basic GitHub Action to run flake8 linting on every push to ensure code quality and prevent syntax errors.

---

Note

Low Risk
Adds a new GitHub Actions workflow that runs flake8 on pushes/PRs; it only affects CI behavior and may introduce new lint failures but does not change runtime code.

Overview
Introduces a new GitHub Actions workflow (.github/workflows/lint.yml) that runs flake8 on every push and pull request.

The job sets up Python 3.9, installs flake8, and runs a narrow set of error checks (E9, F63, F7, F82) to catch syntax and undefined-name issues in CI.

^{Written by Cursor Bugbot for commit 33d4f99. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Python linter added to TypeScript-only project

Medium Severity

This workflow adds flake8 (a Python linter) to a TypeScript project that contains no Python files. The linting step will always pass without checking any actual code because flake8 only processes .py files. The PR's stated goal of "ensuring code quality and preventing syntax errors" cannot be achieved since the codebase is TypeScript. The project already has ESLint configured for TypeScript linting in .eslintrc.cjs and the release workflow runs pnpm lint.

 

[cursor]

Python linting workflow added to TypeScript-only repository

Low Severity

This workflow adds Python flake8 linting to a TypeScript/JavaScript repository that contains no Python files. The codebase is an npm package (@polymarket/clob-client) with TypeScript source files, and the existing workflow.yaml already runs pnpm lint for TypeScript via ESLint. This flake8 workflow will run on every push and pull request, consuming CI resources to lint non-existent Python code.