pytest filter drops the duration line, so a 3-second run and a 10-minute run look identical

Start by locating the Rust pytest filter implementation and its inline filter tests, then trace how the pytest summary is reduced to the current pass/fail line. Preserve the elapsed duration for both passing and failing summaries, and verify the output matches the examples in this issue.

rtk 0.49.0, Homebrew, macOS arm64 (Darwin 27.0.0), Python 3.11.8, pytest 7.4.0.

What happens

rtk pytest drops pytest's summary line, so the elapsed time is gone from the output.

$ cat test_slow.py
import time

def test_fast():
    assert 1 == 1

def test_slow():
    time.sleep(3)
    assert 2 == 2

$ rtk proxy pytest test_slow.py | tail -3
test_slow.py ..                                                          [100%]

============================== 2 passed in 3.04s ===============================

$ rtk pytest test_slow.py
Pytest: 2 passed

Same on the failing path:

$ rtk pytest test_fail.py
Pytest: 0 passed, 1 failed

Failures:
1. [FAIL] test_boom
     test_fail.py:4: in test_boom
     assert 1 == 2
     E   assert 1 == 2

No duration anywhere.

Why this one hurts

I run pytest through the Claude Code hook, so the model only ever sees the filtered output. A tool result carries no timing of its own, the model cannot tell a call that took 0.2s from one that took 10 minutes. Pytest's summary line was the only place that number existed, and the filter removes it.

The practical effect is that a suite which quietly goes from 12s to 10 minutes reads exactly the same as before. Nothing in the agent's context says anything changed, so nobody looks into it.

Other filters already keep it

This looks like an oversight in the pytest filter, not a project-wide policy. From the inline filter tests in the 0.49.0 binary:

• gradle: expected = "BUILD SUCCESSFUL in 8s\n7 actionable tasks: 7 executed"
• gradle (failing): expected = "> Task :app:test\n3 tests completed, 1 failed\nBUILD FAILED in 12s"
• cargo: expected = " Finished release [optimized] target(s) in 45.23s\n Binary: target/release/my-crate (5.2MB)"

and vitest parses Duration\s+([\d.]+)(ms|s), ctest parses Total Test time (real) = ([\d.]+) sec, dotnet captures a Duration: group.

Suggestion

Put the seconds back on the summary line:

Pytest: 2 passed in 3.04s
Pytest: 0 passed, 1 failed in 1.02s

That is roughly 3 tokens, and it is the only timing signal an agent gets for the whole run.

Workaround does not exist today

A project-local .rtk/filters.toml cannot patch this, since pytest is routed to the Rust module. Trusted and confirmed applied, output unchanged:

schema_version = 1

[filters.pytest-keep-duration]
description = "keep pytest duration line"
match_command = "pytest"
strip_ansi = true
keep_lines_matching = ["passed in", "failed", "error"]
max_lines = 20

$ rtk trust -y
    pytest-keep-duration pytest
  Enabled — revoke with `rtk untrust`.
Filters will now be applied.

$ rtk pytest test_slow.py
Pytest: 2 passed

That part is #3904, so I am not asking for it here. Just the duration line.