docs: brief template run lists come from imports (mos-1612)

A builder's whole-file run list for a row comes from imports, not a text
grep, and goes in the builder's report before the run. Files on the
mos-1592 list stay off unless Mos approved the run. Row 329 round 2's
path grep matched fixture text and reran case1-accept.

docs/plans/BRIEF-TEMPLATE.md

@@ -96,6 +96,12 @@ suite by design and runs through a script puts that entry in the brief's
 Gate and in BUILD.md with the row, and the lead adds it to the landing
 gate's list. Any unlisted skip stays RED.
 
+A builder's list of whole test files to run for a row comes from imports,
+not from a text grep for a path, and goes in the builder's report before
+the run. A file on the mos-1592 list (`packages/cli/tests/case1-accept.test.mjs`
+for now) stays off the list unless Mos has approved that run (mos-1612,
+after row 329's round 2 grep matched fixture text and reran the F7 file).
+
 Any row that builds businessDoc() with a library project sets the chief's
 gitea ref in its fixture (mos-1584, after row 285 gave the chief of staff
 a read-scoped gitea credential that the validator requires when a business