{"agent":"claude","input":"Migrate this repository's CI from Travis to GitHub Actions. Read .travis.yml and follow every command it runs through the Makefile and any task runner down to the real shell commands. Read the files that state the supported Python version (Pipfile, pyproject.toml, runtime.txt, setup files) and note any disagreement with the Travis matrix. Before writing a workflow, run each CI step here and record its exit code and the last lines of output, twice: once with dependencies installed from the lockfile on the Python version the project declares, and once installed the way .travis.yml installs them. If the two differ, explain why. For each Python version in the matrix, check whether actions/setup-python can provide it on a current Ubuntu runner by reading the actions/python-versions manifest, and drop versions that cannot be set up or that the project does not support, saying which and why. For every step that passes, check that it is able to fail. Then write .github/workflows/ci.yml: least-privilege permissions, a concurrency group, dependency caching, an install that uses the lockfile, one step per check, and the coverage upload adapted for Actions with the secret it needs named in the description. Validate the file with actionlint. Delete .travis.yml and update the README badge. Do not fix failing tests or lint findings; list each one with its output as a known failure. Open a pull request whose description says, step by step, what the workflow is expected to report on its first run.","resources":[{"url":"https://github.com/your-org/your-app"}]}