Gate: mock-detect-covers-dialect

The project declares derived.mock_detect — the regex that recognises a test double in this ecosystem.

Property	Value
Judgment	an AI or a person answers the question below, through anchors judge
Confronts	test
Blocking by default — new project	yes
Blocking by default — existing project	no — informs
Presupposes	derived.mock_detect — until these are declared in anchors.yaml, the gate is pending and asks nothing

The question

The project declares derived.mock_detect — the regex that recognises a test double in this ecosystem. Read this test file and answer: does the declared pattern reach EVERY form of double it uses? Fail it if there is a double the regex does not match (another function, another dialect, a decorator instead of a call, a whole-module double vs a member double). A regex that matches nothing makes the mock-stamped gate report green without having checked anything. When failing it, PROPOSE the corrected pattern as a patch of anchors.yaml. BEFORE ANSWERING, check whether this unit declares @TBD for the piece this question asks about (@TBD: code, @TBD: code,test, …). If it does, the test does NOT exist yet by a recorded decision, and there is nothing to confront: answer waived, naming the absence (“the spec declares @TBD for this piece and it does not exist in the repository”). Do NOT answer pass — pass is a statement ABOUT the test, and without the test it states what nobody verified; the stamp stays in the map looking like real verification. Also check that the @TBD is TRUE: if the piece already exists in the repository, the marker is stale, the judgment is due as usual, and the stale declaration is a finding — while it stays there, every gate that reads it waives what it should demand.

Declaring it

gates:
  - name: mock-detect-covers-dialect
    on: [test]
    measures: judgment