Allow extras to be kept in user output

[mskarlin]

We previously filtered these out when the embeddings, etc. were removed.

[Copilot]

Pull Request Overview

This PR updates the user-output filtering logic to preserve any extra fields on Context models and adds a test to verify that behavior.

• Switch filter_content_for_user to use model_dump(exclude={"text"}), preserving all extras on Context
• Add extra_field to a test context and assert it survives the filter

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
tests/test_agents.py	Added extra_field when constructing a context and asserted it is retained after filtering
paperqa/types.py	Replaced manual field listing with **c.model_dump(exclude={"text"}) to carry through extras

Comments suppressed due to low confidence (2)

paperqa/types.py:241

• The docstring for filter_content_for_user says it filters out extra items, but the new implementation preserves extras. Please update the docstring to reflect that extras are now kept.

    def filter_content_for_user(self) -> None:

tests/test_agents.py:973

• This assertion only checks that extra_field is non-null. Consider asserting the actual value (e.g., == "extra_value") to catch cases where the field is wrong or partially populated.

    assert response.session.contexts[0].extra_field is not None  # type: ignore[attr-defined]

[jamesbraza]

Can you add an assertion message here as informal docs, something like , "Extra fields should be propagated so we can XYZ"