The in-process chat.agent e2e harness runs every leg against the single
globalThis API registry. When a leg closed while its run was still
parked on a session waitpoint, that run stayed alive into the next leg
and its later teardown unregistered the globals out from under the
active run. In CI this surfaced as Noop run-metadata and "can only be
used from inside task.run()" errors across most legs.
close() now aborts the run and awaits full teardown instead of racing a
10s timeout; the abort disables the session-waitpoint backend so any
in-flight or later wait() returns at once; and the backend keeps its
pending entry until the wait resolves so disable() can abort it. Runs
no longer overlap, so the shared globals stay consistent.
Eric Allam
de4c3c734f