> Rewrites are declared by the publisher, never inferred from overlap.

This style of writing is idiotic because it conveys no additional information. It's no different from stating

> Rewrites are declared by the publisher, never when moons collide.

The two sentences are actually logically identical. No idea why these models keep writing like this.

> Folds are monotone single statements. gen only goes up, extents only grow, processed periods only union, rw_start only moves earlier.

This is even more ridiculous.

Why leave such disparaging comments?

Fable is effectively worse than Opus 4.6 now. They severely messed with the model.

   // `HANDLE` is an opaque kernel handle (kernel32 validates and returns 0/FALSE
   // on a non-console handle); every out-param is `&mut T` to a `#[repr(C)]` POD,
   // ABI-identical to the Win32 `LP*` pointer (thin non-null). The reference type
   // encodes the only pointer-validity precondition, so `safe fn` discharges the
   // link-time proof. (`bun_windows_sys::kernel32` declares these with `*mut`;
   // redeclared locally so the legacy-conhost cursor path below is plain calls.)

   // Progress's terminal handle is the canonical `output::File` (vtable-backed
   // stderr/File from `OutputSinkVTable`). The duplicate `ProgressTerminalVTable`
   // from B-0 round 1 is removed; tty/ansi/winsize route through    the new
   // `OutputSinkVTable` slots so `bun_core` stays T0 (no `bun_sys` dep).