[IvanGirderboot]

What changed

Adds an ignore block to .yamllint for .cache/ and .venv/, matching the existing exclude_paths in .ansible-lint.

Why

CONTRIBUTING.md sets up a .venv/ in the repo root and then asks contributors to run yamllint .. Without an ignore, yamllint goes into the virtualenv and reports errors from installed third-party packages (97 results locally). So the documented pre-submit check fails even when the tracked tree is clean. CI isn't affected because its checkout has no .venv/.

Validation

• python3 scripts/qa.py — passed
• yamllint . — exit 0 (previously exit 1 from .venv/ contents); the only remaining output is existing line-length warnings in tracked files
• ansible-lint — exit 0 (existing warnings only)
• Relevant playbook(s) pass ansible-playbook --syntax-check (playbooks/site.yml)
• A second Ansible run was checked for unexpected changes when live hardware/software was exercised — N/A, this is lint configuration only

Tested hardware/OS and commands used: linting only on a Linux (WSL2) contributor checkout with yamllint 1.38.0; no hardware exercised.

Release/user impact

None. No role, default, port, variable, or hardware assumption changes.

Documentation and secrets

• Public variable changes are reflected in examples/docs and docs/variables.md is regenerated — N/A, no variable changes
• No real credentials, private inventory, event-only secrets, or sensitive artifacts are included
• Upstream-derived code/configuration retains required attribution and licensing information — N/A

🤖 Generated with Claude Code