# The admitted barrier-pull markers the integration-split lane ACTUALLY WRITES under
# MOBILEGL_IPC_STRICT_ERRORS=1, one `<field>@<verb>` per line.
#
# P5e (gl), ruling ID-119. THIS IS THE OTHER SIDE OF THE RATCHET, and it is the side that was
# missing. The generated allowlist (scripts/gen_pipe_field_ownership.py --print-admitted) says
# which pairs MAY be admitted - it is a statement about the tables. This file says which ones the
# lane DOES produce - a statement about the run. A lane checked only against the first kind
# ROTS GREEN: a debt retires, its marker stops being written, and nothing notices, so the day a
# regression re-introduces that read the lane calls it "expected".
#
# So Harness/split_log_paths.py's `markers` mode fails BOTH ways:
#   - a pair here that no longer appears  -> delete it, in the commit that retired it;
#   - a pair that appears and is not here -> add it with the phase that owes it, or retire it.
#
# HOW TO REFRESH (never by hand from a guess):
#   ctest -L integration-split --show-only=json-v1 > lane.json
#   MOBILEGL_IPC_STRICT_ERRORS=1 ctest -L integration-split -j 4
#   python3 MobileGL/MG_IntegrationTest/Harness/split_log_paths.py markers lane.json . \
#       <(python3 scripts/gen_pipe_field_ownership.py --print-admitted) this-file
# and put the census it prints here.
#
# P5f fe census: 179 integration-split entries pass, with zero Fatal, ordinary Admitted,
# or ESCALATED pairs. The expected set is therefore empty; either new marker kind is red.
# Eight live pairs retired through server framebuffer/texture/program records, reply scratch,
# and the Begin XFB snapshot. The two already-stale rows GetBoundVertexArray@DrawArrays and
# GetBufferBindingSlot@DrawArrays were independently identified at the f1 baseline (f1-report
# section 8.1). fe-report records every removed pair and its source. P8 client-array tests
# retain their separate lane; an empty census here does not assert that P8 is implemented.
