GeezerVison

Summary

The maintainer no longer wants Dependabot opening version-update PRs. This removes .github/dependabot.yml, so the monthly grouped PRs for pip and GitHub Actions stop.

It also carries the ruff 0.16.9 → 0.16.10 bump from #103 (cherry-picked with Dependabot authorship kept). Removing the config can make Dependabot auto-close #103, and carrying the commit here means the upgrade lands either way. If #103 is merged first, this branch still merges cleanly because the two changes are identical.

After this, dependencies are bumped by hand with make lock and checked with make lock-check. SHA-pinned actions in .github/workflows/ are also updated by hand. Dependabot security alerts and security-update PRs are repository settings (Settings → Code security), and this file doesn't control them.

Change type

• Catalog resource or classification
• Bilingual editorial content
• Catalog export or consumer contract
• Tests, tooling, or workflow
• Governance or documentation

Evidence and scope

• Related issue: none; supersedes chore(deps-dev): bump ruff from 0.16.9 to 0.16.10 in the python-dependencies group #103
• Source or maintenance evidence: n/a
• Website consumer impact: none (no catalog, radar, or manifest changes)
• Intentionally out of scope: the Dependabot security-update repository settings; the pyproject.toml ruff floor stays at Dependabot's >=0.16.10

Validation

Run locally on this branch with ruff 0.16.10 installed from the dev lock:

• make check passes: ruff, pytest, validate_catalog.py, export_catalog.py --check --target both, render_readmes.py --check, build_content_manifest.py --check, verify_examples.py (5), verify_courses.py (12), verify_paths.py (2)
• make lock-check passes (locks match pyproject.toml)
• English and Chinese output remain consistent (no content changes)
• No secrets, generated reports, local build output, or analytics IDs were committed

Permissions and review

• I have the right to submit this contribution.
• I retained third-party notices and did not relicense third-party material.
• Human reviewers wrote or verified all resource descriptions and classifications.
• I read CONTRIBUTING.md and docs/CURATION_POLICY.md.