Name the clone in the parity block, which was reading this tree instead

docs/gate-parity.md

@@ -28,13 +28,26 @@ THE PAIR ABOVE CLONED `--depth 1` AND READ WHATEVER HEAD IT LANDED ON, WHICH IS
 THE ONE READING IN THIS FILE THAT COULD NOT BE LEFT TO MOVE. `--depth 1` takes
 the default branch head of a repository this board does not control, so the pair
 answered `fadecd85` on 2026-09-17 and the sha pasted under it had stopped
-reproducing. Everything below is measured inside that clone, so a reader
-following this section in order was reading one commit's workflow files against a
-table written against another, and the block below came back with two of its
+reproducing. The block of workflow files below was measured inside that clone, so
+a reader following this section in order was reading one commit's workflow files
+against a table written against another, and it came back with two of its
 twenty-four rows changed for them. The sha is an argument now rather than an
 output: it cannot drift, and a reader either gets the commit this table is about
 or an error saying that commit is gone.
 
+THAT SENTENCE SAID `EVERYTHING BELOW` UNTIL THIS EDIT, AND THE BLOCK IT NAMES IS
+THE ONLY READING HERE IT WAS TRUE OF. Three readings in this file are taken in
+THIS repository at pinned commits of it, and they find nothing inside a clone of
+the other one. The pair the paragraph above replaced was also the only command in
+this file that moved a reader's working directory, so after the replacement the
+block below was a bare relative glob with nothing left to stand it in front of
+the right tree. This repository carries `.github/workflows/` as well, so the
+block answered out of this tree and exited 0, and five of the twenty-six rows it
+returned there are byte-identical to rows in the paste, because the two gates
+share eight file names. It names the clone in its own argument now, the way the
+three commands above name it with `-C`, so no reading in this file depends on
+where a reader is standing. #395 is where that was found.
+
 THE DELETION THIS FILE APPLIES TO ITS OTHER MOVING READINGS IS NOT AVAILABLE
 HERE, and that is why this one is repaired rather than emptied. Those are
 readings the argument quotes, and the file keeps its point without them. This one
@@ -73,7 +86,7 @@ commit was head when it last ran, so it appears or does not depending on when th
 list is taken. The set that decides parity is therefore the workflow files and
 their triggers, which do not move between two readings of one commit:
 
-    awk 'FNR==1{if(NR>1)print f" | "t" | "nm; f=FILENAME; sub(/.*\//,"",f); t=""; nm=""; p=0} /^name:/&&nm==""{nm=substr($0,7)} /^on:/{p=1;next} /^[a-zA-Z]/{p=0} p&&/^  [a-z_]+:/{g=$0; sub(/:.*/,"",g); gsub(/ /,"",g); t=t g ","} END{print f" | "t" | "nm}' .github/workflows/*.yml
+    awk 'FNR==1{if(NR>1)print f" | "t" | "nm; f=FILENAME; sub(/.*\//,"",f); t=""; nm=""; p=0} /^name:/&&nm==""{nm=substr($0,7)} /^on:/{p=1;next} /^[a-zA-Z]/{p=0} p&&/^  [a-z_]+:/{g=$0; sub(/:.*/,"",g); gsub(/ /,"",g); t=t g ","} END{print f" | "t" | "nm}' ssoclone/.github/workflows/*.yml
     build.yml | workflow_call, | Build
     codeql.yml | push,pull_request,schedule, | CodeQL
     dco.yml | pull_request, | DCO