chore: declare Python 3.14 classifier

[ltsyk]

Summary

Declare Python 3.14 in package classifiers (tox already lists py314; issue #793).

Fixes #793

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit fcceda3. Configure here.}

[ltsyk]

Removed the accidental tox.ini.bak that snuck into the branch; the PR now only adds the 3.14 classifier (and the intentional tox.ini envlist update).

[beliaev-maksim]

can you please also update CI file to include it in the tests, as well as CHANGES file

[beliaev-maksim]

also need to enable it in CI

[ltsyk]

Thanks — added a CHANGES entry for 3.14. tox already has py314; I also tried to add 3.14 to .github/workflows/ci.yml but this token cannot update workflow files. A maintainer with workflow scope will need to add '3.14' to the test matrix there.

[ltsyk]

Thanks — I added a CHANGES note for Python 3.14 support. tox envlist already includes py314. I cannot update .github/workflows/ci.yml from this token (workflow files 404); please add '3.14' to the CI test matrix when you can.

[markstory]

Suggested change

	* Added ``match`` parameter to ``add_callback` method
	* Added ``match`` parameter to ``add_callback`` method

[ltsyk]

Applied, thanks.

[sentry]

Bug: The changelog documents a keep_headers argument for _recorder.record and Recorder.dump_to_file, but the feature is not implemented, causing a TypeError when used.
_{Severity: MEDIUM}

Suggested Fix

Either implement the keep_headers functionality or remove its documentation from the CHANGES file. To implement it, add the keep_headers parameter to the record and dump_to_file function signatures. Then, modify the _remove_default_headers function to check against the keep_headers list and prevent the specified headers from being stripped.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: CHANGES#L5-L8

Potential issue: The changelog file documents a new `keep_headers` argument for the
`_recorder.record` and `Recorder.dump_to_file` functions, intended to preserve specific
headers. However, this feature is not implemented in the code. The function signatures
for `record` and `dump_to_file` do not accept a `keep_headers` argument. Consequently,
any attempt to use this documented feature, such as
`_recorder.record(keep_headers=['Date'])`, will result in a `TypeError` at runtime
because the function receives an unexpected keyword argument. The header stripping logic
is also hardcoded and does not account for this parameter.