Say where a pending merge check is: queued since when, then building on which machine (hq issue 446)

The forge's holder set mesh/merge-gate pending as "the mesh is mapping this head onto its module graph" and nothing
changed it until the verdict, so a ten-minute controller check read as a stalled forge (issue 423). The holder now
says the head waits in the build queue since the local time it was announced; mesh-delivery follows the build
seat's started event and says the machine building it and since when, never over a verdict the forge holds.

modules/gitea/pulls.ts

@@ -18,6 +18,18 @@ export const CHECK_CONTEXT = "mesh/merge-gate";
 /** The status context of the repository's own merge-check.sh, the check's second layer (novox/hq ADR 0237). */
 export const REPO_CHECK_CONTEXT = "mesh/repo-check";
 
+/**
+ * The pending words a head's merge check is announced with (novox/hq issue 446): where the check is, and since when,
+ * in the time the operator reads. They stood as "the mesh is mapping this head onto its module graph" for the whole
+ * check — the few seconds the controller maps the head and then the queue wait and the build — and readers took the
+ * forge for lagging (issue 423). The controller maps and queues the check in seconds, so from the announcement it waits
+ * in the build queue; mesh-delivery says "building on <machine> since …" when a build machine takes it.
+ */
+export function pendingWords(announced: Date): string {
+  const two = (n: number) => String(n).padStart(2, "0");
+  return `waiting in the build queue since ${two(announced.getHours())}:${two(announced.getMinutes())}`;
+}
+
 /** One layer of a check, judged. */
 export interface Layer {
   verdict: string;