test(cli): lift the never-read-reader quarantine now that the shim hang is fixed

Reverses 392f410 exactly: the `'never-read'` spawn in `beforeAll` and the
case it feeds are live again, and the definite-assignment assertion the
quarantine needed is gone with it. The file is byte-for-byte its pre-quarantine
shape (blob 131331e) — nothing else has touched it since.

Per the maintainer's ruling A (2026-09-03): the quarantine is not a resting
state, and the PR that fixes the hang re-enables the case in the same change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016yfqQh2dBgPAymYd7xipza

Author: claude

packages/cli/test/run-dev-unbuilt-workspace.e2e.test.ts

@@ -291,13 +291,7 @@ let unbuilt: Run;
 let built: Run;
 let genuinelyMissing: Run;
 let stalled: Run;
-// Definite-assignment assertion for the duration of the QUARANTINE below: the
-// `'never-read'` spawn in `beforeAll` is commented out, so nothing assigns this
-// and `strict` reports TS2454 at each of the three reads inside the skipped
-// case. Restoring that spawn makes the `!` redundant again, so it goes when the
-// quarantine is lifted. (Measured: the package's own `typecheck` is
-// `include: ["src"]`, so it never compiles this file and would not have said.)
-let unread!: Lifetime;
+let unread: Lifetime;
 let closedEnd: Lifetime;
 
 beforeAll(async () => {
@@ -306,18 +300,10 @@ beforeAll(async () => {
   built = await runCli(REAL_COMMAND, dir, undefined);
   genuinelyMissing = await runCli(['definitely-not-a-command'], dir, undefined);
   stalled = await runCliWhileParentStalls(REAL_COMMAND, dir, `--import ${UNBUILT_HOOK}`);
-  // ⛔ QUARANTINED — the `'never-read'` child is NOT spawned while the case it
-  // feeds is skipped. See the quarantine note on
-  // `it.skip('gives up and exits instead of waiting forever')` further down:
-  // this spawn is where the 180 s `UNREAD_HARD_CAP_MS` is paid under CI load,
-  // and that one case is its ONLY consumer — `unread` is read nowhere else in
-  // this file. The PR that fixes the hang in `bin/run-dev.js` un-skips that case
-  // and restores these four lines verbatim, in the same change:
-  //
-  //   // ⛔ Nothing measured above is consulted here. Case 1's wall clock is read by
-  //   // the failure message below, as evidence; the ceiling is a constant, so a
-  //   // slow sample can no longer size the instrument that judges the next run.
-  //   unread = await runCliAgainstDeadReader(REAL_COMMAND, dir, `--import ${UNBUILT_HOOK}`, 'never-read', UNREAD_HARD_CAP_MS);
+  // ⛔ Nothing measured above is consulted here. Case 1's wall clock is read by
+  // the failure message below, as evidence; the ceiling is a constant, so a
+  // slow sample can no longer size the instrument that judges the next run.
+  unread = await runCliAgainstDeadReader(REAL_COMMAND, dir, `--import ${UNBUILT_HOOK}`, 'never-read', UNREAD_HARD_CAP_MS);
   closedEnd = await runCliAgainstDeadReader(REAL_COMMAND, dir, `--import ${UNBUILT_HOOK}`, 'destroy-read-end', UNREAD_HARD_CAP_MS);
 }, RUN_TIMEOUT_MS * 6);
 
@@ -406,23 +392,7 @@ describe('the mirror direction: a reader that is never coming back', () => {
    * this replaces armed no bound at all (`write()` returned true, so an early
    * return skipped it) and read as correct in every stalled-reader test.
    */
-  // ⛔ QUARANTINED under the maintainer's ruling A of 2026-09-03 on
-  // objectstack#14832 — do not un-skip it on its own.
-  //
-  // WHY. The `'never-read'` child this case reads HANGS under CI load. The
-  // defect is in the product — `bin/run-dev.js`, the other half of #14832 —
-  // and NOT a cap that is set too low, so raising `UNREAD_HARD_CAP_MS` would buy
-  // nothing and would only make each failure slower. On `Test Core (1/6)` the
-  // harness SIGKILLed the child at the 180 s cap and this assertion red, and
-  // every occurrence EJECTED A WHOLE MERGE-QUEUE BATCH: `main` could not advance
-  // for hours behind this one case, which is what the ruling weighed.
-  //
-  // RE-ENABLE CONDITION. The PR that fixes the hang in `bin/run-dev.js` un-skips
-  // this case in the SAME change, and restores the `'never-read'` spawn in
-  // `beforeAll` (kept there verbatim, commented). The body below and all of its
-  // comments are untouched, so lifting the quarantine is `it.skip` -> `it` plus
-  // that one spawn line — nothing here has to be reconstructed.
-  it.skip('gives up and exits instead of waiting forever', () => {
+  it('gives up and exits instead of waiting forever', () => {
     // A child still alive at the cap was SIGKILLed: signal set, code null.
     // That is the hang, and it is the whole point of this case.
     //