# rest — 106.4s exact, anchored on tests/test_table.py (38.9s).
#
# Seconds are per FILE and EXACT, from docs/probes/ci-durations-4core.txt — every
# phase of every test on the 4-core public runner, run 32754826551. The older
# tables in docs/probes/ were taken on the 2-core box a PRIVATE repository gets,
# AND at `--durations-min=0.05`, and both halves of that were wrong for this cut:
# the leg order inverted when the cores doubled, and the 50ms floor hid 37s of
# the suite on exactly the leg that had 1103 tests. Modelling that hidden cost
# was tried and the fit did not hold — see docs/probes/ci-speed.md § 0b. The
# threshold is zero here, so there is nothing left to model.
#
# The cut is what a longest-first pass makes of those numbers, and it lands at
# 106.4-106.5s a leg: a 0.1s spread, against 93.0-119.8s on the cut it replaces.
# `tests/test_editor.py` is 101.6s of the 106.4s it sits in, so this is 5s off
# the floor and there is nothing further to win by moving files.
#
# **Balance is not what to spend the next hour on.** Runs of the SAME lists put a
# leg 44s apart — `views` measured 76.57s and 120.37s across four — so no re-cut
# is visible in one run, and four were not enough to separate this cut from the
# one it replaced (120.4s against 122.8s, in either direction depending on which
# runs you take). What would actually move the gate is the floor, and the floor
# is one file.
#
# NO LONGER "everything else". It is the table, the query language, the hover
# card and the resolved cascade, plus what balances them. The name is kept
# anyway: renaming a matrix value renames a status check, the one check branch
# protection requires is `check`, which fans these in, and a rename is a
# branch-protection edit in exchange for a word.
#
# **Where a new test file goes.** It used to be "here, unless it is slow enough
# to be worth naming", and that rule went with the property that justified it. It
# goes on whichever leg the newest table in docs/probes/ says is cheapest, and
# `test_every_test_file_is_in_exactly_one_ci_shard` in tests/test_harness.py is
# what stops it going on no leg at all.
tests/test_table.py
tests/test_mermaid.py
tests/test_search.py
tests/test_card.py
tests/test_cascade.py
tests/test_edges.py
tests/test_teaching.py
tests/test_index.py
tests/test_parse.py
tests/test_store.py
