A test marker is not always a visibility rule

A synthetic or smoke marker should not automatically exclude records if the product also uses marked records as visible operator test cases. Define one population predicate shared by counts, lists, and detail reads: admit visible marked records, exclude deliberately hidden marked records, and retain real hidden history according to its separate policy. Capacity or execution eligibility may still need a narrower predicate. This prevents cards from undercounting and links from returning not-found while preserving intentionally hidden fixtures. If every marked row is forbidden, marker-only exclusion remains correct.

Applies when: Test-marked records can be intentionally visible in an operational workspace. Keywords: smoke test marker visibility counts detail routes hidden fixtures