[doubledare704]

Refs #1004.

ERROR entries in the short test summary don't say which phase they came from. For a test whose call passed but whose teardown raised, -rE shows:

ERROR test_repro.py::test_ok - ValueError: boom in teardown

which, next to 1 passed, 1 error, makes it look like a different test errored. show_xfailed already renders XFAIL at teardown of <nodeid>; this does the same for errors coming from _get_line_with_reprcrash_message:

FAILED test_repro.py::test_bad - assert 0
ERROR at teardown of test_repro.py::test_ok - ValueError: boom in teardown
ERROR at teardown of test_repro.py::test_bad - ValueError: boom in teardown
ERROR at setup of test_repro.py::test_s - ValueError: boom in setup

This is the first prerequisite listed in #1004 (comment). Counts are unchanged; only the summary line text changes. Call failures and collection errors render exactly as before (the prefix is only added for setup/teardown).

Things worth a look in review:

• Anything parsing ERROR <nodeid> out of the short summary will now see ERROR at <phase> of <nodeid>. Hence improvement rather than bugfix; happy to change the category if you'd prefer to flag it more strongly.
• The longer prefix leaves less room for the reprcrash message at narrow widths, so it gets truncated sooner. test_teardown_with_test_also_failing now only matches the line prefix for that reason.

Added test_error_extra_reporting_shows_phase and updated the two existing expectations in test_terminal.py and acceptance_test.py.

• Include new tests or update existing tests when applicable.
• Allow maintainers to push and squash when merging my commits.
• If AI agents were used, they are credited in Co-authored-by commit trailers.
• Create a new changelog file in the changelog directory.
• Add yourself to AUTHORS in alphabetical order.

🤖 Generated with Claude Code

Why this change adds the phase only for setup and teardown?

A failed call is always reported as FAILED and a failed setup/teardown as ERROR (default pytest_report_teststatus), so FAILED already implies the phase while ERROR was ambiguous between setup and teardown. It also matches the existing ERROR at {when} of header in the ERRORS section and the XFAIL summary format, and leaves FAILED lines (the most commonly parsed) untouched.