chore: bump version to 1.11.0

[Bre77]

Intent

Cut version 1.11.0 of tesla-fleet-api so ObservationFunnel (landed in PR #131, after the 1.10.1 version bump) becomes installable from PyPI. Pure release task: no library behavior changes, no refactoring, no funnel.py edits. Three commits are unreleased since 1.10.1: the funnel feature (#131), a CI lockfile-drift gate (#129), and a docs correction (#130). New feature, no breaking change, so 1.11.0 is the right bump. Followed the documented release process in AGENTS.md: bumped version in pyproject.toml and version in tesla_fleet_api/init.py, ran uv lock to regenerate uv.lock so its root package version matches (CI's uv sync --locked would otherwise fail the build), committed as 'Bump version to 1.11.0'. Verified ObservationFunnel imports cleanly from the public package surface (from tesla_fleet_api import ObservationFunnel). Ran the full release gate locally: ruff check/format, pyright strict, pytest (707 passed), uv build, and twine check on the built sdist/wheel — all clean. Searched the repo for any other version-string occurrences outside pyproject.toml/init.py/uv.lock and found none, so no other file needs to move in step. Do not create or push a git tag, do not publish, do not touch the pypi environment or run twine upload — publication is a separate, later action by others after this PR merges.

What Changed

• Bumped version in pyproject.toml and __version__ in tesla_fleet_api/__init__.py from 1.10.1 to 1.11.0.
• Regenerated uv.lock via uv lock so its root package version matches the bumped pyproject.toml, satisfying CI's uv sync --locked lockfile-drift gate.
• No source or behavior changes — this makes the ObservationFunnel feature (feat(funnel): add ObservationFunnel read-side listener mechanism #131), the CI lockfile-drift gate (ci: gate on lockfile drift and regenerate uv.lock for 1.10.1 #129), and the docs correction (docs: correct AGENTS.md release process to match actual PyPI environment config #130), all previously merged to main since 1.10.1, installable as a new PyPI release.

Risk Assessment

✅ Low: The change is a minimal three-line version bump (pyproject.toml, init.py, uv.lock) with no library code touched; version strings are consistent across all three files and ObservationFunnel is confirmed exported from the public package surface, matching the stated pure-release intent exactly.

Testing

Confirmed the 1.11.0 bump commit is exactly the described release-only change (pyproject.toml, init.py, uv.lock in lockstep, no other file touched), verified CI's uv sync --locked lockfile check passes, ran the funnel test suite (30/30 passed), and end-to-end demonstrated that from tesla_fleet_api import ObservationFunnel imports and works at version 1.11.0 — the concrete outcome the release exists to unblock. No tag was created/pushed and no stray version strings exist elsewhere, matching every stated constraint.

Evidence: ObservationFunnel importable from public package surface at v1.11.0

$ uv run python -c "from tesla_fleet_api import ObservationFunnel, __version__; print(__version__); print(ObservationFunnel); f=ObservationFunnel(); print(f.value('Locked'))"
version: 1.11.0
ObservationFunnel: <class 'tesla_fleet_api.funnel.ObservationFunnel'>
value Locked (unobserved): None

Evidence: uv sync --locked (CI's exact lockfile-drift gate)

+ tesla-fleet-api==1.11.0 (from file:///.../01M0P3PV49AB5JXD44GWFKHYPS)
... (resolved cleanly, no lockfile drift)

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

• git diff 49ae54d..HEAD (confirms minimal 3-line version-only diff)
• grep for version strings 1.10.1/1.11.0 across .py/.toml/.md/.cfg/.lock files (only the three expected occurrences)
• uv sync --locked (CI's lockfile-drift gate command)
• uv run python -c "from tesla_fleet_api import ObservationFunnel, __version__; ..." (public import surface + version check)
• uv run pytest tests/test_funnel.py -q (30 passed)
• git tag -l | grep 1.11.0 (confirms no tag created)
• git status --short before/after, reverting egg-info build artifacts from my own verification

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.