Drop docs/test-only entries from changelog

Docs and test changes aren't user-visible, so they don't need a
changelog entry. The ASYNC300 behaviour change stays.

Author: claude

docs/changelog.rst

@@ -9,8 +9,6 @@ Unreleased
 - Autofix for :ref:`ASYNC910 <async910>` / :ref:`ASYNC911 <async911>` no longer inserts checkpoints inside ``except`` clauses (which would trigger :ref:`ASYNC120 <async120>`); instead the checkpoint is added at the top of the function or of the enclosing loop. `(issue #403) <https://github.com/python-trio/flake8-async/issues/403>`_
 - :ref:`ASYNC910 <async910>` and :ref:`ASYNC911 <async911>` now accept ``__aenter__`` / ``__aexit__`` methods when the partner method provides the checkpoint, or when only one of the two is defined on a class that inherits from another class (charitably assuming the partner is inherited and contains a checkpoint). `(issue #441) <https://github.com/python-trio/flake8-async/issues/441>`_
 - :ref:`ASYNC300 <async300>` no longer triggers when the result of ``asyncio.create_task()`` is returned from a function. `(issue #398) <https://github.com/python-trio/flake8-async/issues/398>`_
-- Document using ruff's ``lint.external`` setting to preserve ``# noqa: ASYNC...`` comments when running ruff alongside flake8-async. `(issue #310) <https://github.com/python-trio/flake8-async/issues/310>`_
-- Tests: each ``tests/eval_files/*.py`` fixture is now checked with ``compile()`` so that accidental semantic errors (e.g. ``lambda: await foo()``) in fixtures are caught. Files that intentionally contain such constructs are marked with ``# NOCOMPILE``. `(issue #268) <https://github.com/python-trio/flake8-async/issues/268>`_
 
 25.7.1
 ======