Fix stale goal references reintroduced by the CL-5664 merge

Rebasing onto main picked up #407's rewrite of gate-wire.ts (display-
gated timers, onOperator safety net, attachApprovalBudget). Two of
its new comments and one test fixture still said "goal-mode timeout"
/ "goal mode" — composed correctly with this branch's removal in
substance (the timeout is generic plumbing either way) but stale in
wording now that there's no goal subsystem to name. Reworded only;
no logic changed.

Author: TheGreatAxios

src/tui-opentui/gate-wire.test.ts

@@ -985,7 +985,7 @@ describe("operator.gate auto-cancel", () => {
             resolved = result
           },
           timeoutMs: 5,
-          timeoutMessage: "goal mode: no answer in time",
+          timeoutMessage: "auto-cancel: no answer in time",
         })
         expect(shell.overlayKind).toBe("operator")
 

src/tui-opentui/gate-wire.ts

@@ -493,7 +493,7 @@ export function wireGates(
     // entry, which is itself the single-resolve guard, so the other side is
     // simply a no-op once it runs.
     //
-    // The goal-mode timeout is display-dependent and arms inside `open`
+    // The auto-deny timeout is display-dependent and arms inside `open`
     // (below), not here: a request sitting behind others in `pending` must
     // not burn its timeout while the operator has never seen it. Abort is not
     // display-dependent — it reflects the tool having already finished or
@@ -540,7 +540,7 @@ export function wireGates(
     // whether the host has since moved on to a newer one.
     let openedGeneration: number | undefined
 
-    // Mirrors the permission gate: watchdog abort and the goal-mode timeout
+    // Mirrors the permission gate: watchdog abort and the auto-deny timeout
     // both race an operator who may never answer, and unlike the permission
     // path this gate previously had no safety net at all — a queued question
     // behind a stuck overlay hung the run forever. The timeout is