style: restore two doc-comment bindings the new code displaced

Simplifier pass over the branch. Both are comment/import placement, zero behavior
change, no test touched:

  - verified-by-scan.ts: findOutsideCorpus's JSDoc had landed above the TESTISH_*
    constants, with an unrelated doc-comment sandwiched between it and the function
    it describes.
  - render/verify.py: the new payload_accessors import was inserted between
    ERR_VAR_NOT_ON_PAYLOAD's `#:` doc-comment and the constant, breaking the
    binding Sphinx reads.

The rest of the branch was reviewed and deliberately left alone: the four ports
already express the same presence rules, and the two-pass recurse-then-derive
structure is duplicated on purpose rather than being cruft -- collapsing it in TS
alone would make one port diverge for no gain in clarity.

One genuine cross-port asymmetry was found and NOT changed: Python's first
recursion pass copies non-string dict keys where C#/Java filter them in both
passes. Changing it would alter output for a shape the conformance corpus does not
cover, which is a corpus-fixture decision rather than a cleanup-pass one.

cli 559 tests pass; python render 257 passed.

Author: dmealing

server/python/src/metaobjects/render/verify.py

@@ -23,9 +23,9 @@
 from dataclasses import dataclass
 from typing import Protocol
 
-#: A ``{{var}}`` references a field the (contextual) payload does not declare.
 from .payload_accessors import is_boolean_accessor
 
+#: A ``{{var}}`` references a field the (contextual) payload does not declare.
 ERR_VAR_NOT_ON_PAYLOAD = "ERR_VAR_NOT_ON_PAYLOAD"
 #: A ``{{> ref}}`` partial does not resolve in the provider.
 ERR_PARTIAL_UNRESOLVED = "ERR_PARTIAL_UNRESOLVED"

server/typescript/packages/cli/src/lib/verified-by-scan.ts

@@ -176,13 +176,6 @@ function walk(
   }
 }
 
-/**
- * Where does this name live, if not in the test corpus?
- *
- * Only ever called on the miss path, so the cost is paid per BROKEN claim rather than
- * per run. Returns the first unclassified source file containing the name, which is
- * enough to tell the author which pattern they are missing.
- */
 /** Does this path or body look like a test the corpus definition simply did not match?
  *  Deliberately narrow: living under a test directory, or containing an assertion/test
  *  declaration. Without this, a name occurring anywhere in PRODUCTION source downgrades a
@@ -197,6 +190,13 @@ function looksLikeTest(rel: string, lines: string[]): boolean {
   return TESTISH_PATH.test(rel) || lines.some((l) => TESTISH_BODY.test(l));
 }
 
+/**
+ * Where does this name live, if not in the test corpus?
+ *
+ * Only ever called on the miss path, so the cost is paid per BROKEN claim rather than
+ * per run. Returns the first unclassified source file containing the name, which is
+ * enough to tell the author which pattern they are missing.
+ */
 function findOutsideCorpus(name: string, root: string, files: string[]): string | undefined {
   const rx = wordRx(name);
   for (const rel of files) {