justerm_core/

term.rs

//! The terminal state model: a `vte::Perform` that maps parsed VT actions onto
//! the grid, cursor, and pen. This is where the "hidden VT state" lives —
//! pending-wrap, the wide-char spacer, and the pen (BCE seam).

use std::collections::VecDeque;

use unicode_width::{UnicodeWidthChar, UnicodeWidthStr};
use vte::{Params, Perform};

use crate::cell::{Cell, CellFlags, UnderlineStyle};
use crate::color::Color;
use crate::cursor::{Cursor, CursorShape, Pen};
use crate::damage::{LineBounds, LineDamage, ScrollOp, TermDamage};
use crate::event::{ClipboardTarget, TermEvent, Terminator};
use crate::grid::{ExtAttrs, Grid, Row};
use crate::input::{
    KeyEvent, MouseEncoding, MouseEvent, MouseProtocol, encode_focus, encode_key, encode_mouse,
    encode_paste,
};
use crate::search::Match;
use crate::selection::{BufferPoint, Selection};
use crate::serialize::{Frame, FrameKind, MAX_SCROLL_COUNT, MarkerId, MarkerKind, Overlay, Span};

/// Buffer-walk primitives shared by every read surface (#585). A child module, so
/// it reaches `Term`'s private fields directly — no field is widened for it.
mod walk;

/// The search query surface (#586) — finding matches, and the highlight set the
/// consumer pushes back. Stands on `walk`, whose `pub(super)` reaches a sibling
/// module because both are descendants of `term`.
mod search;

/// The selection surface (#587) — gestures, the anchor fixups the write path drives,
/// and text extraction. Stands on `walk` like its siblings.
mod selection;

/// The decoration-marker surface (#588) — marks anchored to absolute buffer lines, the
/// OSC 133 command queries over them, and the anchor fixups the write path drives.
mod markers;

/// Viewport logical lines (#601) — the soft-wrap-joined text a consumer needs for URL
/// detection and the a11y mirror. The last read surface to leave this file under #584.
mod logical;

/// Tracked points (#691) — absolute positions the engine keeps on their content for a
/// holder that lives outside it, and the anchor fixups the write path drives.
mod tracked;

/// Owns the authoritative screen state and applies VT actions to it.
///
/// **No `#[non_exhaustive]` ([#844](https://github.com/kihyun1998/justerm/issues/844)): nothing outside this crate has a reason to build one.** No
/// public function accepts it — the engine hands it out — and there are zero out-of-crate literal
/// sites, so the attribute would bind nothing it does not already bind.
pub struct Term {
    grid: Grid,
    /// The inactive screen. Swapped with `grid` on alt-screen enter/leave; holds
    /// whichever of primary/alternate is not currently shown. The alt screen has
    /// no scrollback (#3 only rings the primary).
    alt_grid: Grid,
    cursor: Cursor,
    /// Cursor saved on alt-screen enter (DEC 1049), restored on leave.
    saved_cursor: Cursor,
    /// Whether the alternate screen is currently active. Guards enter/leave so a
    /// double-enter or double-leave is a no-op.
    on_alt: bool,
    /// One flag per column: is there a tab stop here? Explicit per-column state
    /// (HTS sets, TBC clears), not a fixed modulo. Default = every 8th column.
    tabs: Vec<bool>,
    /// Which characters end a word for Word (semantic) selection — **consumer policy**,
    /// not engine state (ADR-0017). Defaults to [`DEFAULT_WORD_SEPARATORS`]; replaced
    /// through `set_word_separators`, which is also where the `' '` floor is enforced.
    ///
    /// Being *policy* is what puts it on the short list `full_reset` carries across RIS,
    /// beside `replies` and `events`: `ESC c` resets the terminal's state, and a
    /// consumer's configuration is not that. All three references survive RIS here by
    /// construction rather than by remembering to — alacritty's `reset_state` never
    /// touches `self.config`, xterm.js holds it in `OptionsService`, and ghostty passes
    /// the set in per call.
    word_separators: String,
    /// The window title the application last set (OSC 0/2), retained so that a
    /// title *pop* has something to restore (#823). Until XTWINOPS 22/23 landed
    /// the engine forwarded the string and forgot it, which is exactly why a pop
    /// could not be answered: a party that does not know what it is stacking
    /// cannot maintain a stack, and the consumer cannot do it either — it holds
    /// a frame and an event queue and never sees that a pop was requested.
    ///
    /// This is **terminal state the application owns**, so it dies on RIS. It
    /// needs no entry in `full_reset`'s copy-back list — the wholesale rebuild
    /// drops it, which is the behaviour alacritty spells out (`title_stack =
    /// Vec::new()` in its `reset_state`). Note it is a *fifth* kind for the RIS
    /// invariant note's table, which sorts fields into configuration / buffer
    /// coordinate / pending obligation / id counter: a retained title is none of
    /// those, and it dies because the application wrote it, not the embedder.
    window_title: String,
    /// The icon name, the second axis XTWINOPS addresses (#823). Narrower than
    /// it looks: **OSC 1 is not parsed**, so the only thing that ever writes
    /// this is OSC 0, which sets both axes at once. It is retained and stacked
    /// anyway so that mixed push/pop sequences keep the two axes aligned — the
    /// engine has no icon-name event, so restoring one has no observable output
    /// today. That asymmetry is deliberate and stated rather than an oversight;
    /// xterm.js takes the same route (`setIconName` fires nothing).
    ///
    /// **The obligation that outlives this comment: no test can observe this
    /// field, so a fourth writer would disagree with the other three in
    /// silence.** There are exactly three today, all in this file — `OSC 0` in
    /// `osc_dispatch`, and the push and pop in [`Term::window_ops`] — and the
    /// window axis funnels through [`Term::set_window_title`] precisely so its
    /// retained string and its event cannot drift apart. This axis has no such
    /// funnel because it has no event to keep in step with. **Adding `OSC 1` is
    /// the foreseeable fourth writer** (it is the natural neighbour of the OSC
    /// work in #47's tail), and whoever adds it should route every write through
    /// one owner the way the window axis does — not because a test will fail,
    /// but because none can.
    icon_name: String,
    /// The window-title stack (XTWINOPS `CSI 22 t` / `CSI 23 t`), bounded at
    /// [`TITLE_STACK_DEPTH`]. Separate from `icon_name_stack` because the
    /// sequence's second parameter selects an axis and real applications use it:
    /// `vim` emits a fully nested `22;0;0t · 22;2t · 22;1t … 23;2t · 23;1t ·
    /// 23;0;0t`.
    ///
    /// **This is a choice among three models, not two, and the spec does not
    /// make it** — `ctlseqs.txt:1688-1693` names the two axes and never says how
    /// many stacks there are. (a) One stack with the axis ignored: alacritty,
    /// and it restores the wrong string on the sequence above. (b) Two
    /// independent stacks: xterm.js, and this. (c) One stack of `{icon, window}`
    /// **pairs**, where an axis-limited push leaves the other member empty and a
    /// pop that finds an empty member walks *back* through older slots for one:
    /// xterm (`ptyx.h:2361`, `misc.c:8011`). (c) handles the axis correctly by a
    /// different mechanism, so the argument against (a) is not an argument
    /// against it; what separates (b) from (c) is that they do not share a depth
    /// budget — ten each here, ten *total* there — and that a repeated same-axis
    /// pop goes silent under (b) while (c) re-emits from an older slot. Neither
    /// shape is reachable by anything measured, and (b) is the one whose depth
    /// accounting a reader can predict without simulating a ring.
    window_title_stack: Vec<String>,
    /// The icon-name stack — the other half of the pair above.
    icon_name_stack: Vec<String>,
    /// Origin mode (DECOM ?6): when set, cursor addressing is relative to the
    /// scroll region's top margin (and clamped to it).
    origin_mode: bool,
    /// Autowrap (DECAWM ?7): default on. When off, a glyph past the right margin
    /// pins the cursor to the last column and overwrites in place instead of
    /// wrapping to the next line (matches xterm.js) (#63).
    autowrap: bool,
    /// Insert mode (IRM, the non-private SM/RM mode 4): default off (replace).
    /// When on, a printed glyph shifts the row's tail right first (#64).
    insert_mode: bool,
    /// New-line mode (LNM, the non-private SM/RM mode 20): default off. When on,
    /// a line feed also carriage-returns (`convertEol`). Output-only — the Enter
    /// key still encodes CR, matching xterm.js (#71).
    newline_mode: bool,
    /// Reverse wraparound (DEC ?45): default off. When on, a step back at column 0
    /// of a soft-wrapped row moves to the end of the previous row, and a step back
    /// from a parked cursor spends the deferred wrap instead of moving. Both verbs
    /// take that step — `BS` and `CSI D` alike, through `Term::step_back` (#80, #873).
    /// Soft wraps only, and **both halves need `?7h` as well as this flag**: xterm reaches
    /// them through one `rev`, which is `?45 AND ?7h` (`cursor.c:123-127`). The walk leaves
    /// the wrap link alone — see the per-verb table on [`Term::end_wrap`].
    reverse_wraparound: bool,
    /// Bracketed-paste mode (DEC ?2004). The engine owns the flag; the input
    /// encoder (#11) reads it to decide whether to wrap pasted text in markers.
    bracketed_paste: bool,
    /// Synchronized output (DEC ?2026): the app brackets a frame of output so the
    /// renderer can paint it atomically. The engine only *tracks* the flag — the
    /// consumer owns the paint-hold and the spec-mandated timeout.
    synchronized_output: bool,
    /// Color-scheme-update notifications (DEC ?2031): the app asked to be told
    /// when the light/dark scheme changes. The engine is theme-agnostic — it only
    /// tracks the flag; the consumer (which knows the scheme) drives the ?997
    /// notification via `report_color_scheme` (#85).
    color_scheme_updates: bool,
    /// Grapheme-cluster mode (DEC ?2027, default OFF): the app opted into UAX #29 grapheme-cluster
    /// width — a ZWJ / skin-tone / flag / emoji+VS16 sequence is clustered into ONE cell instead of
    /// one cell per scalar (#295). OFF keeps the per-char (wcwidth-compatible) behaviour so the
    /// cursor stays in sync with wcwidth apps — clustering is opt-in for exactly that reason (#301).
    grapheme_clustering: bool,
    /// Where the last content-producing print landed — `(row, col)` of that cluster's
    /// lead cell — or `None` when nothing has been printed since the last thing that
    /// cleared it.
    ///
    /// **One reader again — but the constraint the second one imposed is still binding.**
    /// `REP` (CSI b) reads the grapheme back off this cell, and for a while
    /// `Term::cursor_cluster_col` also asked *is the cursor standing on the cell the
    /// print wrote*, because the deferred-wrap flag could not express a pin under `?7l`
    /// (#865). #869 fixed the flag and that reader went back to it.
    ///
    /// **The anchor must still name a cell that holds the cluster, and the reason is
    /// `REP`'s own, not the departed reader's.** A promotion at the last column
    /// relocates the cluster to the next row (#303), so the join anchors on where it
    /// landed rather than where it was joined; anchored on the vacated column, `REP`
    /// repeats the blanks `vacate_for_wrap` left. Pinned by
    /// `rep_after_a_promotion_relocated_the_cluster_repeats_the_cluster`. Stated here
    /// because the rationale that arrived with it named the other reader, and removing
    /// that reader must not read as permission to undo this.
    ///
    /// The grapheme itself is not stored: it is read back from this cell, which is what
    /// keeps the repeated unit in step with what the cell model actually holds. The
    /// **position** is recorded rather than re-derived, because re-deriving it from the
    /// cursor cannot be done: with autowrap off the cursor reaches the last column both
    /// by *filling* it (pinned, the cluster is under the cursor) and by *advancing onto*
    /// it (the cluster is one to the left), and no cursor state distinguishes them. An
    /// earlier version of this guessed with `pending_wrap || (!autowrap && col + 1 ==
    /// cols)` and repeated whatever happened to sit in the last column — including, on
    /// `?7l` + `ZZZZZ` + `CUP` + `abcd` + `CSI 1 b`, a `Z` from an unrelated earlier part
    /// of the stream. Recording the site cannot be wrong about it.
    ///
    /// **Set** by the three sites that give a cell content, all reached through
    /// `place_grapheme`, each returning where it wrote; **cleared** by every other
    /// `Perform` callback and by [`Term::resize`], whose reflow moves the cell out from
    /// under the anchor.
    ///
    /// That enumeration is xterm's rule (`charproc.c:6478` — assign the retained char
    /// only when the parser is back in the ground state, and it is unset unless a
    /// graphic character was printed) expressed the only way this crate can express it.
    /// `vte`'s `Parser` publishes `new` / `new_with_size` / `advance` /
    /// `advance_until_terminated` and **nothing about its state**, so the structural
    /// formulation is unavailable and an enumeration is what is left.
    ///
    /// **The enumeration is incomplete, and cannot be completed against `vte` 0.15.**
    /// Two parser states return to ground with no callback at all, so nothing here can
    /// observe the sequence ending (measured by feeding `-`, the sequence, then
    /// `CSI 3 b`; xterm gives one dash for every row):
    ///
    /// | input | reaches | dashes |
    /// |---|---|---|
    /// | `CSI 1 ? b`, `CSI SP 1 p`, `CSI ? ? m` | `State::CsiIgnore`, exiting at `vte-0.15.0/src/lib.rs:222` (`0x40..=0x7E => self.state = Ground`) | 4 |
    /// | `DCS 1 ? q … ST` | `State::DcsIgnore`, which routes to `anywhere` and never calls `hook`/`unhook` | 4 |
    ///
    /// All of these are malformed sequences. The divergence is bounded by the anchor's
    /// shape: with a *position* rather than a heuristic, a missed clear repeats the
    /// genuinely last-printed grapheme where xterm repeats nothing — which is ghostty's
    /// behaviour (`Terminal.zig:4467` clears only on full reset), not a wrong glyph.
    ///
    /// `Perform` methods that clear: `execute`, `esc_dispatch`, `osc_dispatch`, `unhook`,
    /// and `csi_dispatch` (which takes it up-front and lets `REP` disarm itself —
    /// xterm's behaviour, and not ghostty's, whose `printRepeat` re-arms through
    /// `print`). `print` clears only on its zero-cell path; `hook` and `put` do not,
    /// because nothing that could read this can arrive before `unhook` does.
    repeat_anchor: Option<(usize, usize)>,
    /// win32-input-mode (DEC ?9001): the app asked for keys as raw Windows
    /// key-records. The engine only *tracks* the flag — the raw record encoding
    /// (`CSI Vk;Sc;Uc;Kd;Cs;Rc _`) is a non-goal (raw passthrough, no semantic
    /// conversion), left to the ConPTY consumer; `encode_key` is unchanged (#86).
    win32_input_mode: bool,
    /// Application cursor keys (DECCKM ?1): when set, cursor keys / Home / End
    /// encode as SS3 rather than CSI (see `input.rs`).
    app_cursor_keys: bool,
    /// Application keypad mode (DECNKM ?66 / DECKPAM `ESC =` / DECKPNM `ESC >`):
    /// tracked for protocol completeness + DECRQM, but NOT yet acted on in key
    /// encoding — xterm.js tracks it the same way and never reads it (#74).
    application_keypad: bool,
    /// VT52 compatibility mode (DECANM ?2 *reset*): when set, `esc_dispatch` is
    /// re-routed into the pre-ANSI VT52 dialect (`ESC A`-style sequences) instead
    /// of the ANSI meaning. `ESC <` clears it. Default off (ANSI). (#84)
    vt52_mode: bool,
    /// VT52 `ESC Y row col` direct-addressing state (#84). vte tokenizes `ESC Y`
    /// as a final and returns to ground, so the two coordinate bytes arrive as
    /// `print()` calls — not part of the escape sequence. This counts them down
    /// (2 → 1 → 0; 0 = not addressing) and `vt52_y_row` parks the first (row)
    /// until the second (col) lands. Each byte decodes as `value - 0x20`.
    vt52_y_pending: u8,
    vt52_y_row: usize,
    /// Mouse tracking mode — what events the app asked to be reported
    /// (?1000/?1002/?1003). `Off` by default.
    mouse_protocol: MouseProtocol,
    /// Mouse coordinate encoding (default X10 vs ?1006 SGR).
    mouse_encoding: MouseEncoding,
    /// Focus in/out reporting (?1004): emit `CSI I`/`CSI O` on focus change.
    focus_events: bool,
    /// Kitty keyboard-protocol progressive-enhancement flags currently in effect
    /// (bit0 disambiguate, bit1 report-events, bit2 alt-keys, bit3 all-as-escape,
    /// bit4 associated-text). 0 = legacy. `encode_key` consults these (#23).
    kitty_flags: u8,
    /// Saved `kitty_flags` for the protocol's push/pop stack (`CSI > u` pushes,
    /// `CSI < u` pops). Capped depth — overflow drops the oldest entry.
    kitty_stack: Vec<u8>,
    /// The other screen's `kitty_flags` and `kitty_stack`: each screen keeps its own, and
    /// [`Self::swap_kitty_keyboard`] exchanges them when the screen changes.
    kitty_flags_inactive: u8,
    kitty_stack_inactive: Vec<u8>,
    /// xterm's `modifyOtherKeys` at level 2 or above, asked for with
    /// `CSI > 4 ; Pv m` (XTMODKEYS) and what `vim` turns on at startup (#890).
    /// `encode_key` consults it *after* `kitty_flags`, because it belongs to the
    /// legacy encoding rather than competing with the newer protocol.
    ///
    /// **Both resets clear it**, RIS by the wholesale rebuild in [`Self::full_reset`] and
    /// DECSTR by a line of its own in [`Self::soft_reset`]. Which it is, and why the answer
    /// is the reference's rather than a convenience, is in
    /// `docs/map/invariant/ris-keeps-configuration-drops-coordinates.md`, whose table this
    /// field is the fifth row of.
    modify_other_keys_2: bool,
    /// Consumer events (title / bell / cwd) accumulated since the last
    /// `drain_events` (#12). Pull, not push — see `event.rs`.
    events: Vec<TermEvent>,
    /// Outbound reply bytes (DA/DSR/DECRQM query answers, #27) accumulated
    /// during `feed` for the consumer to write back to the PTY. Raw bytes →
    /// PTY, kept separate from typed `events` → UI.
    replies: Vec<u8>,
    /// The hyperlink currently open (OSC 8 with a URI), stamped onto every glyph
    /// written until closed (OSC 8 with empty URI). Ambient pen-like state — not
    /// part of the pen/SGR, and *not* cleared by an SGR reset.
    ///
    /// The URI itself, not a pool index — there is no pool (#628). The lead paragraph
    /// here used to describe one (*"Hyperlink side-table … referenced by `Cell.link`
    /// (1-based). Append-only (#26)"*), left behind when its field was deleted.
    current_link: Option<std::sync::Arc<str>>,
    /// Live OSC 8 `id=` groups: `"id;;uri"` → the allocation that key already named,
    /// held **weakly**.
    ///
    /// `Weak`, not `Arc`, is the whole lifetime story. A strong entry here would make
    /// every id'd link immortal for the life of the `Term` — precisely the leak #628
    /// deleted, re-entering through the door grouping opens. A dangling key is the
    /// correct answer rather than a hole: the link it named has left the buffer, so a
    /// later open of the same id is genuinely a new link. xterm.js expresses the same
    /// lifetime by *deleting* its `_entriesWithId` entry when the last line marker
    /// referencing it is disposed (`OscLinkService.ts:98-100`); justerm has no disposal
    /// hook by design, and `Weak` is that lifetime without one.
    link_ids: std::collections::HashMap<String, std::sync::Weak<str>>,
    /// Map length at which [`Self::link_ids`] is swept for dangling keys, doubling each
    /// time so the sweep is amortised O(1) per open and dead keys stay O(live).
    ///
    /// A sweep is affordable here for the reason #628's rejected option (c) was not:
    /// staleness is observable in O(1) (`Weak::strong_count`), where (c) had to decide
    /// "is the pool oversized" by counting live references — the O(buffer) walk it was
    /// trying to avoid.
    link_ids_sweep_at: usize,
    /// Scroll region top/bottom margins (DECSTBM), 0-based inclusive. A
    /// line-feed at `scroll_bottom` scrolls only rows `[scroll_top..=scroll_bottom]`.
    /// Default = the full screen.
    scroll_top: usize,
    scroll_bottom: usize,
    /// Lines that have scrolled off the top of the primary screen, oldest at the
    /// front. Accrues only on a top-anchored, primary-screen scroll.
    scrollback: VecDeque<Row>,
    /// How many lines the viewport is scrolled up from the bottom. 0 = following
    /// the live screen; clamped to `[0, scrollback.len()]`.
    display_offset: usize,
    /// Maximum scrollback lines retained; the oldest are evicted past this.
    scrollback_limit: usize,
    /// A spare row buffer recycled across full-screen scrolls: the cap-evicted
    /// oldest line is parked here and reused as the next scroll's blank bottom,
    /// so a steady-state flood allocates nothing (ADR-0009).
    recycled_row: Option<Row>,
    /// Per-line damage bounds since the last `reset_damage` (ack), one per row.
    line_damage: Vec<LineBounds>,
    /// A first-class scroll recorded since the last `reset_damage`.
    scroll: Option<ScrollOp>,
    /// The whole screen changed (alt switch / clear / later resize+flood) — the
    /// renderer must redraw everything.
    full_damage: bool,
    /// The cursor `(row, col)` at the last `reset_damage` (ack) — where the
    /// consumer last saw the caret. A pure cursor move records no content
    /// damage, so `damage()` folds this *old* cell plus the current one into the
    /// frame; without it a cell-invert caret ghosts at the old spot (mirrors
    /// Alacritty's `last_cursor`). #38.
    prev_cursor: (usize, usize),
    /// The live selection, in absolute buffer coordinates. `None` when nothing
    /// is selected. See `selection.rs`.
    selection: Option<Selection>,
    /// The search highlights the consumer asked to paint (#108). Search
    /// matches are consumer-owned (it drives next/prev), so the engine holds only
    /// the set handed back via `set_search_highlights`, and `frame()` projects it
    /// onto the viewport — the same anchoring path as the selection.
    search_highlights: Vec<Match>,
    /// The *active* (current) search match (#428), stored as its absolute span
    /// (#436) — designated by the consumer (next/prev is its policy) either as
    /// an index into `search_highlights` (resolved to the span at call time) or
    /// directly by span, which a capping backend uses for a past-cap match
    /// (xterm creates its active decoration from the found result, OUTSIDE the
    /// capped highlight list). A span is NOT structurally tied to the set, so
    /// every path that voids the set must void this too: `set_search_highlights`
    /// (hand-over reset, #428) and `invalidate_search_highlights` (the single
    /// funnel for eviction / every region scroll incl. the accrual sub-region
    /// branch (#449) / reflow / both alt swaps) — a stale span would otherwise
    /// keep painting coordinates that now hold other text.
    ///
    /// **That list is the *motion* funnel, and it is complete only for motion.** An
    /// in-place erase or overwrite stales this set too, and deliberately does not
    /// funnel — read `invalidate_search_highlights`, which owns that decision and its
    /// grounds. Stated here because this comment enumerating the callers reads as the
    /// whole rule, and a reader who stops at it concludes the erase verbs were
    /// forgotten.
    active_search_highlight: Option<Match>,
    /// Engine-owned decoration markers (#118), split per buffer like xterm's
    /// `BufferSet` (#177 S0): each a stable id bound to an absolute buffer line
    /// that re-anchors through eviction/scroll/reflow like a selection anchor. The
    /// active buffer's list is selected by `on_alt` — `markers`/`markers_mut`.
    /// `alt_markers` holds the plain anchors `add_marker` makes on the alt screen
    /// (#187); OSC 133 command marks never land there, because `add_command_mark`
    /// returns on the alt screen (#192). It is disposed on alt-leave (xterm
    /// `clearAllMarkers`). `next_marker_id` hands
    /// out monotonic ids across both buffers so ids never alias.
    normal_markers: VecDeque<Marker>,
    alt_markers: VecDeque<Marker>,
    next_marker_id: u32,
    /// The basis that keeps a *pulled* marker index valid without re-pulling
    /// (#490). Both are reported by [`Term::marker_index`] and — from the wire
    /// slice on — by the frame header, so a consumer can compare what it holds
    /// against what is current.
    ///
    /// `evicted_total` counts lines popped off the front of scrollback since
    /// startup or RIS — one at a time by the scrollback cap, all of history at once
    /// by `ED 3` and [`Term::clear`] (#936). Eviction shifts **every** live marker
    /// by the same amount, so
    /// that whole class of movement is one number rather than M facts, and a
    /// consumer rebases a held line by the delta.
    ///
    /// `marker_epoch` covers everything the delta cannot express: a mutation
    /// after which a held line is wrong for a reason no single offset repairs.
    /// It says *"what you pulled no longer describes this buffer"* — not *"a verb
    /// ran"*, which is why the movers bump it only when a surviving marker's line
    /// actually moved. Disposal is deliberately **not** a bump: a consumer learns
    /// of that through `TermEvent::MarkerDisposed` and can drop the entry without
    /// asking for the rest again.
    evicted_total: u64,
    marker_epoch: u32,
    /// Positions the engine keeps on their content for a holder that lives
    /// *outside* it (#691). Split per buffer and re-anchored by the same fixups as
    /// the markers beside them; the difference is that nothing here reaches a
    /// frame — a tracked point is answered on request, never projected.
    normal_tracked: Vec<TrackedPoint>,
    alt_tracked: Vec<TrackedPoint>,
    next_tracked_id: u32,
    /// Cursor state saved by DECSC (ESC 7), restored by DECRC (ESC 8). A slot
    /// separate from `saved_cursor` (which is the alt-screen save). Defaults to
    /// home/default so a DECRC with no prior DECSC restores a sane state.
    decsc: SavedCursor,
    /// SCS-designated character sets G0..G3 (#62). `gl` indexes the active (GL)
    /// set, switched by SI (→G0) / SO (→G1). First cut uses G0/G1.
    charsets: [Charset; 4],
    gl: usize,
}

/// A character set designated by SCS (#62). First cut: ASCII (default), DEC
/// Special Graphics (line-drawing), and UK. G2/G3 and the GR half are later.
#[derive(Clone, Copy, PartialEq, Eq, Default)]
enum Charset {
    #[default]
    Ascii,
    DecSpecialGraphics,
    Uk,
}

impl Charset {
    /// Map one GL byte (a `char` in the 7-bit range) through this set. ASCII and
    /// any out-of-range char pass through; UK swaps `#`→£; DEC Special Graphics
    /// translates `_`..`~` to the line-drawing / symbol glyphs.
    fn map(self, c: char) -> char {
        match self {
            Charset::Ascii => c,
            Charset::Uk if c == '#' => '£',
            Charset::Uk => c,
            Charset::DecSpecialGraphics => dec_special_graphics(c),
        }
    }
}

/// The VT100 DEC Special Graphics set: bytes `_`..`~` (0x5F..0x7E) map to the
/// box-drawing and symbol glyphs. Matches xterm/alacritty; anything outside the
/// range passes through unchanged.
fn dec_special_graphics(c: char) -> char {
    // Keys ``..`~` only — `_` (0x5F) is deliberately absent, matching xterm.js /
    // alacritty (it passes through as a literal underscore), not the strict-DEC
    // "0x5F = blank" reading.
    match c {
        '`' => '◆',
        'a' => '▒',
        'b' => '␉',
        'c' => '␌',
        'd' => '␍',
        'e' => '␊',
        'f' => '°',
        'g' => '±',
        'h' => '␤',
        'i' => '␋',
        'j' => '┘',
        'k' => '┐',
        'l' => '┌',
        'm' => '└',
        'n' => '┼',
        'o' => '⎺',
        'p' => '⎻',
        'q' => '─',
        'r' => '⎼',
        's' => '⎽',
        't' => '├',
        'u' => '┤',
        'v' => '┴',
        'w' => '┬',
        'x' => '│',
        'y' => '≤',
        'z' => '≥',
        '{' => 'π',
        '|' => '≠',
        '}' => '£',
        '~' => '·',
        other => other,
    }
}

/// Default scrollback retention when not specified.
const DEFAULT_SCROLLBACK: usize = 10_000;

/// The narrowest screen the engine represents: **two columns**.
///
/// A width-2 glyph occupies a `WIDE_CHAR` lead *and* the `WIDE_CHAR_SPACER` that
/// stands for its second half, so one column cannot hold one — and a pair with only
/// one half written is the malformed state every repair path in this crate keys off
/// ([ADR-0025](https://github.com/kihyun1998/justerm/blob/master/docs/adr/0025-row-and-wide-pair-cell-state-ownership.md) D4). `Term::with_scrollback` and [`Term::resize`] clamp `cols` up to
/// this, which is what makes D4 (*both halves of a pair move together*)
/// unconditionally satisfiable rather than true only above some unstated width.
///
/// Both references that a terminal *engine* can be compared to forbid one column for
/// exactly this reason — alacritty's `MIN_COLUMNS = 2` and xterm.js's
/// `MINIMUM_COLS = 2` — and the third (ghostty) permits it only by destroying the
/// glyph.
///
/// The clamp is **silent and pull-only**: a `resize(1, rows)` during a pane drag is
/// widened rather than rejected, and no event reports it. Both references instead
/// make the clamped size the one that travels outward — alacritty derives its
/// `WindowSize` from the clamped `SizeInfo`, xterm.js fires `onResize` with the
/// clamped pair — so a justerm consumer must do that correlation itself: read the
/// width back from [`Term::grid`] / the frame header and size the PTY from *that*,
/// never from the value it requested. Sizing a PTY to one column leaves the
/// application rendering for a width the buffer does not have.
pub const MIN_COLUMNS: usize = 2;

/// The built-in word-boundary set for Word (semantic) selection — the default value of
/// [`Term::set_word_separators`], and **policy the consumer may replace** ([ADR-0017](https://github.com/kihyun1998/justerm/blob/master/docs/adr/0017-core-consumer-boundary-mechanism-vs-policy.md):
/// mechanism in core, policy injected).
///
/// It is alacritty's `SEMANTIC_ESCAPE_CHARS` (`alacritty_terminal/src/term/mod.rs:45`
/// @ `852e971`) verbatim — space, tab and a punctuation set that deliberately omits
/// `.`, `/` and `-` so a path or URL stays one word — **plus U+3000 IDEOGRAPHIC
/// SPACE**, which is justerm's one divergence from every reference default.
///
/// Two properties of this list are load-bearing and neither is obvious:
///
/// - **It is a literal set, not the Unicode `White_Space` property.** A
///   `char::is_whitespace()` predicate would end a word at every space-like codepoint —
///   including the four `Line_Break=GL` (glue) ones U+00A0, U+2007, U+202F and U+205F,
///   whose whole purpose is "do not break here". A locale-formatted `1<NNBSP>234`
///   double-clicked as `1`. All three references are literal sets for the same reason.
/// - **U+3000 is in it, and no reference's default has it.** It is the only
///   East-Asian-Wide codepoint `White_Space` accepts (measured over U+0000–U+10FFFF),
///   so on alacritty and xterm.js `　abc` is one word while justerm gives the useful
///   answer. Keeping it was once argued *on the grounds that core had no injection
///   point*; that ground is gone, so it survives here as a **default**, and a consumer
///   who wants reference-exact behaviour removes it.
///
/// [`Term::set_word_separators`] additionally forces `' '` into whatever it is given —
/// see there for why that floor is not optional.
pub const DEFAULT_WORD_SEPARATORS: &str = ",│`|:\"' ()[]{}<>\t\u{3000}";

/// A declared OSC 8 hyperlink, as handed to a consumer.
///
/// **Owned, not borrowed**, and that is the point: the URI lives in a row's side map, so
/// a `&str` into it would be tied to `&Engine` and a caller could not hold the link
/// across the next `feed()` — which is precisely what a hover handler does. Measured on
/// the alternative: reading a borrow costs 0.75 ns, but keeping it *does not compile*, so
/// the caller copies the string instead at 62.6 ns. Handing back this handle is 17.9 ns
/// — cheaper than the workaround it removes, on a call made once per hover.
///
/// Cloning is a refcount bump; the allocation is shared with every cell of the same OSC 8
/// open and released when the last row holding it dies.
///
/// **A struct rather than a bare `Arc<str>`** for two reasons: it keeps `Arc` out of the
/// published signature, and OSC 8's `id=` parameter lands here as a field without
/// changing the return type again. Same shape as alacritty's `Hyperlink`, for the same
/// reasons (`alacritty_terminal/src/term/cell.rs`).
///
/// **Link *identity* is deliberately not exposed yet.** Two OSC 8 opens of an identical
/// URI are two links here, so `uri() == uri()` cannot answer "is this cell part of the
/// same link as that one?" — an `Arc::ptr_eq` accessor would. It is left out because no
/// consumer asks it today (nothing outside this crate's tests calls `link_at` at all),
/// and unlike this type's *shape*, adding a method later is not a breaking change. The
/// asymmetry decides it: shipping an accessor nobody uses is hard to undo, adding one
/// when a caller appears is free.
///
/// **No `#[non_exhaustive]` ([#844](https://github.com/kihyun1998/justerm/issues/844)): nothing outside this crate has a reason to build one.** No
/// public function accepts it — the engine hands it out — and there are zero out-of-crate literal
/// sites, so the attribute would bind nothing it does not already bind.
#[derive(Clone, PartialEq, Eq, Debug)]
pub struct Hyperlink {
    uri: std::sync::Arc<str>,
}

impl Hyperlink {
    pub(crate) fn new(uri: std::sync::Arc<str>) -> Self {
        Hyperlink { uri }
    }

    /// The link target, exactly as the application declared it — never validated,
    /// never resolved. Whether it is a URL a consumer is willing to open is that
    /// consumer's policy ([ADR-0017](https://github.com/kihyun1998/justerm/blob/master/docs/adr/0017-core-consumer-boundary-mechanism-vs-policy.md)), the same way colour resolution is.
    ///
    /// **One exception to "exactly":** a URI containing 14 or more unencoded `;` arrives
    /// cut short, because the parser this engine builds on passes at most 16 OSC fields.
    /// The shorter URI is not marked as cut. A percent-encoded `%3B` is unaffected.
    pub fn uri(&self) -> &str {
        &self.uri
    }
}

/// Length at which the `id=` group map is first swept for dangling keys, doubling from
/// there. Small enough that a session declaring a handful of ids never pays a sweep,
/// large enough that the sweep is not the common path.
const LINK_IDS_FIRST_SWEEP: usize = 16;

/// How deep an XTWINOPS title stack goes before a push starts dropping the
/// oldest entry.
///
/// Ten is **two implementations plus a spec inference**, not a clean sweep, and
/// the difference is worth stating so nobody reads it as more than it is:
/// xterm's `MAX_SAVED_TITLES` (`ptyx.h:2357`) and xterm.js's
/// `Constants.STACK_LIMIT` both say ten, and the spec describes the
/// direct-access parameter as taking a value *"in the range 1 through 10"*
/// (`ctlseqs.txt:1698`), which only makes sense against a ten-slot stack.
/// **alacritty is 4096** (`TITLE_STACK_MAX_DEPTH`), so the corpus is 2–1 on the
/// number. Nothing observed nests deeper than three, so the bound is a
/// robustness cap rather than a compatibility one, and ten is the value two
/// references chose for exactly that job.
///
/// The **overflow rule**, unlike the number, is 4-for-4: drop the oldest and let
/// the push succeed. xterm.js `shift()`s, alacritty `remove(0)`s, and xterm gets
/// there by arithmetic rather than by saying so — `which = used++ %
/// MAX_SAVED_TITLES` writes an eleventh push over slot 0, which is the oldest.
/// Refusing the push instead would break the pairing for the *innermost*
/// nesting levels — the ones a user unwinds first — and nobody does it.
const TITLE_STACK_DEPTH: usize = 10;

/// The `id=` value out of an OSC 8 `params` field, or `None` when it is absent or empty.
///
/// Three rules, each taken from xterm.js's `_createHyperlink` verbatim rather than from
/// the spec prose, because each is a place a reasonable reading goes wrong
/// (`src/common/InputHandler.ts:3128-3131` at the pinned SHA `699f5537b023`):
///
/// - **`:`-separated**, not `;` — `params` is one OSC argument holding a key=value list
///   (`id=xyz123:foo=bar:baz=quux`), so the split is on colons (`params.split(':')`).
/// - **`id` may sit anywhere in it** (`findIndex(e => e.startsWith('id='))`), so matching
///   only a leading `id=` is the wrong parse and passes a single-parameter test.
/// - **an empty value is not an id** (`slice(3) || undefined`). This is the one with teeth:
///   an empty key would group every `id=`-with-no-value link in a session into one link
///   across unrelated URIs, and it is a wrong answer that grows with uptime.
///
/// Only the first `id=` is consulted, matching `findIndex` — an empty first one yields
/// `None` rather than searching on for a non-empty sibling.
fn osc8_link_id(params: &[u8]) -> Option<&[u8]> {
    params
        .split(|b| *b == b':')
        .find_map(|kv| kv.strip_prefix(b"id="))
        .filter(|value| !value.is_empty())
}

/// The widest grid the engine will hold, and the mirror of [`MIN_COLUMNS`] — but derived
/// from a different kind of constraint, which is why the two are not symmetric.
///
/// The floor is **semantic**: a width-2 glyph needs two cells, so one column is a screen
/// no correct grid can be. The ceiling is **representational**: the frame header stores
/// `cols` and `rows` as `u16` each, so a grid wider than `u16::MAX` cannot be *described*
/// to a consumer even though the engine could hold it. Without the clamp that mismatch was
/// silent — measured, `Engine::new(70_000, 2)` built a 70 000-column grid whose frame
/// declared `cols = 4464` and decoded `Ok`, so a consumer laid out 4464 columns of a
/// 70 000-column screen with nothing reporting the difference.
///
/// No reference bounds a grid this way, and that is expected rather than a divergence:
/// none of them serializes a grid, so none has a header field to overflow. This is the
/// one axis where justerm's own wire is the only authority.
///
/// **A backstop, not a policy.** A 4K display at a very small font is roughly 550 columns;
/// this is two orders of magnitude past any real terminal, so it should never be reached
/// by a consumer that is not already doing something wrong. The clamp is silent and
/// pull-only on the same terms as [`MIN_COLUMNS`] — read the size back from
/// [`Term::grid`] rather than trusting the value you passed in.
pub const MAX_COLUMNS: usize = u16::MAX as usize;

/// The tallest grid the engine will hold. The row half of [`MAX_COLUMNS`] — same
/// `u16` header field, same reasoning, same silent-clamp contract.
pub const MAX_ROWS: usize = u16::MAX as usize;

/// The most live markers one buffer will hold.
///
/// Derived from the wire the same way [`MAX_COLUMNS`] is: the marker group's count
/// are `u16`, so a population past `u16::MAX` encodes a wrapped count while writing
/// every record, and `decode` then reads the next group's count out of the middle of
/// a marker record and returns `Ok`. The field bounds the value; this constant only
/// writes that bound down where the value is produced, because `encode` returns
/// `Vec<u8>` and has no channel to refuse.
///
/// **Why a bound is needed at all**, rather than a wider field: markers are allocated
/// by the *stream*. `add_command_mark` appends per OSC 133 sequence, several marks can
/// share one line, and scrollback eviction only drops a marker when its line reaches
/// absolute 0 — so a stream that never emits a newline accumulates marks in a 24-row
/// buffer without bound (measured: 70 000). [`crate::Engine::feed`] is an untrusted
/// entry point ([ADR-0007](https://github.com/kihyun1998/justerm/blob/master/docs/adr/0007-robustness-testing-property-and-fuzz.md)), and unbounded allocation behind it is a defect class that
/// record exists to catch.
///
/// **A backstop, not a policy**, on the same terms as [`MAX_COLUMNS`]. Ordinary shell
/// integration emits at most four marks per command and a command occupies at least one
/// line, so a default-scrollback session tops out near 40 000 — this is not reached by a
/// consumer that is not already being fed something hostile. Overflow disposes the
/// *oldest* marker and announces it through `TermEvent::MarkerDisposed`, which is the
/// channel scrollback eviction already uses for the same event.
pub const MAX_MARKERS: usize = u16::MAX as usize;

/// The longest command text an OSC-133 `OutputStart` mark will freeze, in `char`s.
/// A longer command is captured truncated to this many characters.
///
/// **Why a bound at all** is [`MAX_MARKERS`]'s argument one field over: the *stream*
/// decides the size. The text spans `[B, C)`, and nothing bounds how far apart those
/// two sequences are — a stream that emits `B`, dumps a full screen and then `C` names
/// a command as long as the buffer. Re-extracting on demand made that a transient
/// allocation; freezing it at `C` makes it resident, for as long as the mark lives, and
/// [`crate::Engine::feed`] is an untrusted entry point ([ADR-0007](https://github.com/kihyun1998/justerm/blob/master/docs/adr/0007-robustness-testing-property-and-fuzz.md)).
///
/// **A display bound, not a semantic one.** [`CommandLine::command`]'s consumer
/// announces it and lists it; a prefix is a usable answer and an absent one is not, so
/// overflow truncates rather than declining to capture. The truncation is at a `char`
/// boundary, so the answer is always valid text. No ordinary command reaches it — this
/// is not a limit a shell user can type into.
pub const MAX_COMMAND_TEXT: usize = 4096;

/// The longest `OSC 52` base64 payload the engine will decode, in bytes (#828).
/// A longer one is **dropped whole**, never truncated.
///
/// **What this bounds is ours, not the parser's, and the difference was
/// measured.** `vte` is built with its default features, so its OSC accumulator
/// is a `Vec<u8>` rather than the `ArrayVec<_, 1024>` of its `no_std` path: a
/// 4 MB payload arrives at `osc_dispatch` complete, 4 000 003 bytes across three
/// fields. Anyone reading this bound as "the engine cannot be made to allocate"
/// has the wrong model; `vte` already did, before the handler ran.
///
/// What it does refuse is the **second** allocation — the rejoin, which copies
/// every field again — and everything downstream of it. That is why the check
/// sums the field lengths rather than measuring the joined payload: a bound
/// applied *after* the join would let a hostile stream buy the copy it was
/// meant to prevent, which is what the first draft did. The decoded `Vec` is a
/// third; the `String` is not a fourth, since `String::from_utf8` reuses the
/// buffer it is given. The property all of it buys is the one worth naming: no
/// unbounded string crosses the boundary into a consumer that then has to hold
/// it.
///
/// **It does not bound the queue, and the queue is unbounded.** `drain_events`
/// is pull-style with no back-pressure, so a consumer that does not drain
/// accumulates stores at up to this size each — the pre-existing hole
/// `docs/map/territory/events-and-replies.md` records, which this sequence
/// enlarges by roughly three orders of magnitude over the next-largest payload
/// (`MAX_COMMAND_TEXT`, 4096). Bounding a queue nobody drains is a different
/// decision from bounding a payload, and it is not taken here.
///
/// **Dropped rather than truncated**, which is the opposite of
/// [`MAX_COMMAND_TEXT`] one field up, and the asymmetry is the point: a prefix of
/// a command is a usable answer, while a prefix of a clipboard is text the user
/// pastes somewhere believing it is what they copied. An ignored copy is visible
/// the moment they paste; a truncated one is not.
///
/// **A backstop, not a policy**, and sized so that no real copy reaches it: 16
/// MiB of base64 is ~12 MiB of text, well past a whole scrollback buffer's worth
/// of `tmux set-buffer`. Neither reference has a hard cap to import — alacritty
/// has none at all and ghostty's `MAX_BUF = 2048` is an inline-buffer threshold
/// with an allocator path past it (`src/terminal/osc.zig:298`) — so this number
/// is justerm's own and is chosen by what it must not break rather than by what
/// it permits.
pub const MAX_CLIPBOARD_BASE64: usize = 16 * 1024 * 1024;

/// The state DECSC (ESC 7) saves and DECRC (ESC 8) restores: position, pen/SGR,
/// pending-wrap, and origin mode (per ADR-0004 — DECRC restores origin mode,
/// which Alacritty omits). Cursor *visibility* is deliberately not part of this
/// (DECTCEM is separate from DECSC).
#[derive(Clone, Copy, Default)]
struct SavedCursor {
    row: usize,
    col: usize,
    pen: Pen,
    pending_wrap: bool,
    origin_mode: bool,
    /// SCS charset state at save time — DECSC/DECRC round-trip the designated
    /// sets and the active GL shift (#62).
    charsets: [Charset; 4],
    gl: usize,
}

/// An engine-owned decoration marker (#118): a stable id bound to an absolute
/// buffer line. The line shifts in lockstep with eviction/region scroll/reflow
/// (the same coordinate moves the selection anchor tracks); the marker is
/// dropped when its line leaves the buffer — **or when `ED` blanks the whole row
/// it stands on** (#750), which is the one death that is not the buffer moving.
struct Marker {
    id: MarkerId,
    line: usize,
    /// The cursor column at emit time (#166). Meaningful for OSC-133 command
    /// marks — CommandStart(B)/OutputStart(C) columns bound the *typed command*
    /// (excluding the prompt), like VSCode's `commandStartX`/`commandExecutedX`.
    /// Plain `add_marker` decorations are row-granular and carry `col = 0`.
    ///
    /// **Domain is `[0, cols]`, not `[0, cols - 1]` (#562)** — a bound, not a cell.
    /// A command that exactly fills its row ends *one past* the last column, and
    /// that value is what `extract_lines` wants: it clips `[b_col, c_col)`, so the
    /// exclusive end absorbs it through `.min(cells.len())`. Storing `cursor.col`
    /// alone (the cursor is held at `cols - 1` with `pending_wrap`) cost such a
    /// command its last character with no resize involved. The **inclusive** side
    /// cannot absorb it, so `extract_lines` steps a `from` of `cells.len()` to the
    /// next line rather than selecting an empty run and flushing a `\n`.
    col: usize,
    /// Plain for a `add_marker` decoration; a command-boundary role for an
    /// OSC 133 mark (#158). All kinds share the anchor/eviction machinery.
    kind: MarkerKind,
    /// What an `OutputStart` mark froze about the command it closes (#750) —
    /// `None` on every other kind, and the reason this is one boxed pointer rather
    /// than two inline fields: three marks in four never carry it, and the
    /// population is bounded at [`MAX_MARKERS`].
    ///
    /// It dies with the marker, which is the point: a side table keyed by
    /// [`MarkerId`] would need its own purge at every disposal site, i.e. exactly
    /// the missing-destruction-funnel defect this issue is about (ADR-0025 D1 —
    /// a fact lives with its owner).
    command: Option<Box<CommandRecord>>,
}

/// The part of a command that is **not** in the buffer, frozen on its `OutputStart`
/// mark.
///
/// Both fields are recorded at the instant they are first true, and neither can be
/// recovered afterwards:
///
/// - `text` is complete and on screen exactly when `C` arrives. Re-reading it later
///   through the recorded `[b_col, c_col)` clip names whatever now occupies those
///   cells — measured for a plain overwrite, ICH, DCH and an erase, and only the last
///   of those is a verb any mark-lifetime rule could reach.
/// - `exit` arrives with `D`, one mark later, and lives in no cell at all. Resolving it
///   at query time meant pairing over *survivors* (`out.last_mut()`), which re-parented
///   a code onto the previous command as soon as a disposal broke the run. Written here
///   when `D` is parsed, a disposal can only drop an answer, never move one.
struct CommandRecord {
    text: Box<str>,
    exit: Option<i32>,
}

/// A stable handle to a tracked buffer position, handed out by
/// [`Term::track_point`].
///
/// It is deliberately **not** a [`MarkerId`]: a marker is a decoration anchor and
/// rides two frame groups, so every marker a consumer registers is something the
/// renderer paints. A tracked point is private to whoever asked for it.
///
/// **No `#[non_exhaustive]` ([#844](https://github.com/kihyun1998/justerm/issues/844)): the attribute is already implied.** The field is `pub(crate)`,
/// so no literal is possible outside this crate however many fields it grows.
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)]
pub struct TrackedId(pub(crate) u32);

/// One tracked position: an absolute buffer `(line, col)` the write path keeps on
/// its content (#691). The element type of `normal_tracked` / `alt_tracked`.
struct TrackedPoint {
    id: TrackedId,
    line: usize,
    col: usize,
}

/// One live marker, as the pull query reports it: its stable id, its
/// **absolute** `[scrollback ++ screen]` line, and the static facts a consumer
/// would otherwise have to re-learn from every frame.
///
/// `kind` and `exit` ride here rather than on the frame because they never change
/// after `push_marker` — re-sending them per frame is the same class of waste as
/// re-sending the line.
///
/// **No `#[non_exhaustive]` ([#844](https://github.com/kihyun1998/justerm/issues/844)): nothing outside this crate has a reason to build one.** No
/// public function accepts it — the engine hands it out — and there are zero out-of-crate literal
/// sites, so the attribute would bind nothing it does not already bind.
#[derive(Debug, Clone, PartialEq, Eq)]
pub struct MarkerEntry {
    pub id: MarkerId,
    pub line: u32,
    pub kind: MarkerKind,
}

/// The answer to [`Term::marker_index`] — every live marker of the *active*
/// buffer, plus the basis that says how long the answer stays usable.
///
/// The consumer keeps this and rebases per frame:
/// `current = line - (evicted_total_now - evicted_total)`, valid for exactly as long
/// as `epoch` is unchanged. When the epoch moves, the held lines are wrong in a way
/// no offset repairs and the consumer asks again.
///
/// It reports the active buffer because an absolute index means a different thing on
/// each screen — the same reason `markers`/`markers_mut` route by `on_alt`. An
/// alt-screen switch therefore bumps the epoch even though no line moved: what the
/// answer *describes* changed.
///
/// **No `#[non_exhaustive]` ([#844](https://github.com/kihyun1998/justerm/issues/844)): nothing outside this crate has a reason to build one.** No
/// public function accepts it — the engine hands it out — and there are zero out-of-crate literal
/// sites, so the attribute would bind nothing it does not already bind.
#[derive(Debug, Clone, PartialEq, Eq)]
pub struct MarkerIndex {
    pub markers: Vec<MarkerEntry>,
    pub evicted_total: u64,
    pub epoch: u32,
}

/// One executed shell command recovered from OSC-133 marks, for
/// screen-reader command navigation. The consumer jumps prompt-to-prompt over
/// these and announces `command` + a success/fail signal from `exit`.
///
/// **No `#[non_exhaustive]` ([#844](https://github.com/kihyun1998/justerm/issues/844)): nothing outside this crate has a reason to build one.** No
/// public function accepts it — the engine hands it out — and there are zero out-of-crate literal
/// sites, so the attribute would bind nothing it does not already bind.
#[derive(Debug, Clone, PartialEq, Eq)]
pub struct CommandLine {
    /// The command's jump anchor as a *document* line — the logical-line index of
    /// the CommandStart(B) mark within [`Term::accessible_text`], so the consumer
    /// reveals the right row of the accessible view (soft-wrapped rows collapse to
    /// one logical line). This is core's analog of VSCode's
    /// `bufferToEditorLineMapping`; the frame-mode web side has no wrap info to
    /// map it itself.
    ///
    /// **It is an index into a document, so it is only meaningful together with the
    /// document it indexes** — the one [`Term::accessible_text`] returns *at the same
    /// instant, on the primary screen*. Neither half is expressible as a number on this
    /// struct, and they are the two that recur; they are not a proof of
    /// sufficiency. The hedge was earned: a mark whose row is erased in place also
    /// answers about content that is gone — on the primary screen, at one instant, and
    /// a re-ask reproduces it, so neither half below reaches it. That was a
    /// defect in mark *lifetime* rather than in dating, and it is fixed at the
    /// lifetime: `ED` now retires the marks on each whole row it blanks, and the
    /// command's text and exit are frozen when the stream reveals them rather than
    /// re-read from cells (see [`Term::command_lines`]). One residue is deliberate and
    /// belongs to this field — `EL`/`ECH` retire nothing, so a mark can still name a
    /// row they blanked, and this line then resolves onto it:
    ///
    /// - **the instant.** No scalar this engine publishes dates a document line, and
    ///   the reason is not one axis but two. Eviction moves it by the number of evicted
    ///   *line-ends*, which equals the row count except when an evicted row soft-wraps
    ///   into the next — measured, one eviction took the absolute lines
    ///   `[12, 12, 12, 13]` → `[11, 11, 11, 12]` while this line stayed at `11`, and the
    ///   very next eviction moved both. And flipping a row's wrap bit, which ordinary
    ///   output does, moves this line while the absolute lines, `evicted_total` and
    ///   `marker_epoch` all stay put — a motion the absolute space does not have.
    ///   Carrying the instant is therefore *buildable but expensive*: a line-end counter
    ///   **and** a generation of its own. [ADR-0029](https://github.com/kihyun1998/justerm/blob/master/docs/adr/0029-a-published-coordinate-carries-its-instant-or-is-re-asked.md) defers it (alternative D) and takes
    ///   the re-ask discharge, which D3 grants this surface on its own merits;
    /// - **the screen.** The document is `[scrollback ++ primary]`, always. While the
    ///   alt screen is up [`Term::accessible_text`] returns the *alt* document, and this
    ///   line indexes the other one. When the alt screen is the taller of the two the
    ///   index still **resolves**, onto unrelated content — so this is not a bounds
    ///   problem a caller can check its way out of.
    ///
    /// So: ask for both together, keep them together, and re-ask rather than rebase.
    pub line: usize,
    /// The typed command text, prompt- and output-excluded (B→C columns).
    ///
    /// **Frozen at the `133;C` that closed the command**, not re-read from the
    /// cells when you ask. Those cells are not reserved for it: a plain overwrite,
    /// `ICH`, `DCH` and an erase were each measured making the recorded column range
    /// name somebody else's content, and only the last of the four is a verb any
    /// mark-lifetime rule could reach. Bounded at [`MAX_COMMAND_TEXT`] `char`s.
    pub command: String,
    /// The CommandFinished(D) exit code, if the shell reported one and the
    /// command has finished.
    ///
    /// **Recorded when `133;D` is parsed**, onto the mark that closed the
    /// command — not paired here at query time. It lives in no cell, so nothing on
    /// screen can reconstruct it, and pairing over *survivors* re-parented a code onto
    /// the previous command as soon as a disposal broke the run.
    pub exit: Option<i32>,
}

/// Collect per-line damage bounds into damaged `LineDamage` spans (undamaged
/// lines dropped). Shared by `damage` (content-only) and `frame_damage`
/// (content + cursor cells).
fn bounds_to_lines(bounds: &[LineBounds]) -> Vec<LineDamage> {
    bounds
        .iter()
        .enumerate()
        .filter(|(_, b)| b.is_damaged())
        .map(|(line, b)| {
            let (left, right) = b.span();
            LineDamage { line, left, right }
        })
        .collect()
}

impl Term {
    pub fn new(cols: usize, rows: usize) -> Self {
        Self::with_scrollback(cols, rows, DEFAULT_SCROLLBACK)
    }

    pub fn with_scrollback(cols: usize, rows: usize, scrollback_limit: usize) -> Self {
        // Both clamps mirror `resize` exactly, so a screen cannot be born at a size a
        // resize would refuse. They are not the same *kind* of rule, though: the width
        // floor is a published contract (#547 — one column was supported and no longer
        // is), while the row floor is `resize`'s own long-standing "a terminal is never
        // 0-tall" that this constructor merely failed to enforce while carrying the
        // same `scroll_bottom: rows - 1` below. That gap was a subtract-overflow panic
        // on `rows == 0`, not a degenerate screen.
        // …and the ceiling is the header's, not the glyph's: `frame.cols`/`rows` are u16,
        // so a wider grid would be built and then misdescribed on the wire (#621).
        let cols = cols.clamp(MIN_COLUMNS, MAX_COLUMNS);
        let rows = rows.clamp(1, MAX_ROWS);
        Term {
            grid: Grid::new(cols, rows),
            alt_grid: Grid::new(cols, rows),
            cursor: Cursor::default(),
            saved_cursor: Cursor::default(),
            on_alt: false,
            origin_mode: false,
            autowrap: true,
            insert_mode: false,
            newline_mode: false,
            reverse_wraparound: false,
            bracketed_paste: false,
            synchronized_output: false,
            color_scheme_updates: false,
            grapheme_clustering: false,
            repeat_anchor: None,
            win32_input_mode: false,
            app_cursor_keys: false,
            application_keypad: false,
            vt52_mode: false,
            vt52_y_pending: 0,
            vt52_y_row: 0,
            mouse_protocol: MouseProtocol::Off,
            mouse_encoding: MouseEncoding::Default,
            focus_events: false,
            kitty_flags: 0,
            kitty_stack: Vec::new(),
            kitty_flags_inactive: 0,
            kitty_stack_inactive: Vec::new(),
            modify_other_keys_2: false,
            events: Vec::new(),
            replies: Vec::new(),
            current_link: None,
            link_ids: std::collections::HashMap::new(),
            link_ids_sweep_at: LINK_IDS_FIRST_SWEEP,
            tabs: default_tabs(cols),
            word_separators: DEFAULT_WORD_SEPARATORS.to_owned(),
            window_title: String::new(),
            icon_name: String::new(),
            window_title_stack: Vec::new(),
            icon_name_stack: Vec::new(),
            scroll_top: 0,
            scroll_bottom: rows - 1,
            scrollback: VecDeque::new(),
            display_offset: 0,
            scrollback_limit,
            recycled_row: None,
            line_damage: vec![LineBounds::undamaged(cols); rows],
            scroll: None,
            full_damage: false,
            prev_cursor: (0, 0), // matches the default cursor's home position
            selection: None,
            search_highlights: Vec::new(),
            active_search_highlight: None,
            normal_markers: VecDeque::new(),
            alt_markers: VecDeque::new(),
            next_marker_id: 0,
            evicted_total: 0,
            marker_epoch: 0,
            normal_tracked: Vec::new(),
            alt_tracked: Vec::new(),
            next_tracked_id: 0,
            decsc: SavedCursor::default(),
            charsets: [Charset::Ascii; 4],
            gl: 0,
        }
    }

    /// What changed since the last `reset_damage()` — line ranges, each with a
    /// changed column span. See [ADR-0003](https://github.com/kihyun1998/justerm/blob/master/docs/adr/0003-damage-model-incremental-bounds.md).
    pub fn damage(&self) -> TermDamage {
        if self.full_damage {
            return TermDamage::Full;
        }
        // Scrolled up under follow-bottom "stay": the viewport is frozen, so
        // screen changes below it are not visible — report nothing. (A user
        // scroll that moves the viewport sets full_damage above.)
        if self.display_offset > 0 {
            return TermDamage::Partial(Vec::new());
        }
        TermDamage::Partial(bounds_to_lines(&self.line_damage))
    }

    /// Render damage: content damage plus the cursor cells, for [`Term::frame`].
    ///
    /// A pure cursor move changes no cell *content*, so [`Term::damage`] (which
    /// stays content-only, the cadence/flow-control primitive) would miss it —
    /// yet a cell-invert caret must clear its old spot and ink the new one. So
    /// the frame producer folds the old (last-acked) + current cursor cells in,
    /// but only when the cursor actually moved: a still cursor needs no redraw,
    /// keeping an idle frame empty. Mirrors Alacritty's `last_cursor`. #38.
    fn frame_damage(&self) -> TermDamage {
        if self.full_damage {
            return TermDamage::Full;
        }
        if self.display_offset > 0 {
            return TermDamage::Partial(Vec::new());
        }
        let cur = self.cursor.point();
        if cur == self.prev_cursor {
            return TermDamage::Partial(bounds_to_lines(&self.line_damage));
        }
        let mut bounds = self.line_damage.clone();
        bounds[cur.0].expand(cur.1, cur.1);
        let pr = self.prev_cursor.0.min(self.grid.rows() - 1);
        let pc = self.prev_cursor.1.min(self.grid.cols() - 1);
        bounds[pr].expand(pc, pc);
        TermDamage::Partial(bounds_to_lines(&bounds))
    }

    /// Clear accumulated damage. The consumer calls this after applying a frame
    /// (the ack); the next `damage()` reflects only changes since.
    pub fn reset_damage(&mut self) {
        for b in &mut self.line_damage {
            b.reset();
        }
        self.scroll = None;
        self.full_damage = false;
        // The consumer has now seen the caret at the current position; the next
        // frame's cursor-move damage is measured from here (#38).
        self.prev_cursor = self.cursor.point();
    }

    /// Mark the whole screen damaged (alt switch / clear / flood, and a consumer
    /// reattach that needs a full re-sync — see [`crate::Engine::mark_fully_damaged`]).
    pub fn mark_fully_damaged(&mut self) {
        self.full_damage = true;
    }

    /// Record that columns `[left, right]` of `row` changed.
    ///
    /// Both columns are **clamped to the last column, and asserted in debug** (#536).
    ///
    /// Ten of the fourteen call sites derive their bound from a cursor column or from `cols`.
    /// **Four derive it from a wide pair's width**, and that is the shape worth centralising:
    /// `write_glyph`'s `col + width - 1` (which had no guard — this issue), `promote_cluster_to_wide`'s
    /// `col + 1` (guarded by its own `col + 1 >= cols` early return), `demote_cluster_to_narrow`'s
    /// `(col + 1).min(cols - 1)` (self-clamped), and `relocate_cluster_wide`'s literal `(0, 1)`
    /// (valid only because `MIN_COLUMNS = 2`, #547). Three carried a private guard and one did not.
    ///
    /// No reference has this shape to port a clamp from: alacritty computes damage ranges too
    /// (`term/mod.rs:1406`, `:1649` @ `852e971`) but always from a column or `columns()` — its print
    /// path records no damage at all, relying on the previous and current cursor *points* to bracket
    /// the line — while xterm.js tracks whole rows (`markDirty(y)`) and ghostty a per-row
    /// `dirty: bool`. alacritty's `LineDamageBounds::expand`, which this one is a copy of, is equally
    /// unguarded.
    ///
    /// The two halves do different jobs:
    ///
    /// - the **`debug_assert` is the detector**. An out-of-range bound is stored silently and
    ///   detonates later, when `frame()` slices the row, so the stack trace accuses the reader
    ///   rather than the writer. That delay is what #536 was filed about, and the assert collapses
    ///   it — a bad caller dies here, at the site that recorded it (measured: an injected off-by-one
    ///   moved the panic from `frame()`'s slice to this line).
    /// - the **clamp is the release backstop**, and it clamps *toward a false positive*. justerm is
    ///   a library, so a panic crosses into the consumer's process; over-damaging repaints a cell
    ///   that did not change, which costs nothing a consumer can see. ghostty states the asymmetry
    ///   as a rule: *"Dirty tracking may have false positives but should never have false negatives.
    ///   A false negative would result in a visual artifact on the screen."* (`page.zig:1993-1995`).
    ///
    /// **`left` is guarded for that reason, and it is the axis that can actually lose a cell.**
    /// Clamping `right` cannot under-report — columns past the last do not exist. But `LineBounds`
    /// marks a line undamaged with `left = cols, right = 0` and `is_damaged()` is `left <= right`,
    /// so a single `expand` with `left > right` on an otherwise-clean line leaves the line reading
    /// as undamaged and **drops its whole span silently**. Unreachable from the ten column-derived
    /// sites today; guarded because that is precisely the failure ghostty's rule forbids.
    ///
    /// `row` is deliberately left to panic on the index, and that is **not** in tension with
    /// `frame_damage` clamping a row fifty lines below (`prev_cursor.0.min(rows - 1)`). The two
    /// rows are different kinds of thing under the same rule: `prev_cursor` is a *stale remembered*
    /// coordinate that a shrinking resize may have put out of range, so clamping it repaints the
    /// nearest surviving cell — a false positive. `row` here is a *live computed* index for the
    /// mutation just made, so clamping it would damage a different line than the one that changed:
    /// a false negative on the real line, which is the outcome the rule forbids.
    fn damage_span(&mut self, row: usize, left: usize, right: usize) {
        let last = self.grid.cols().saturating_sub(1);
        debug_assert!(
            left <= right && right <= last,
            "damage_span({row}, {left}, {right}) is not a span inside [0, {last}]"
        );
        self.line_damage[row].expand(left.min(last), right.min(last));
    }

    /// The first-class scroll recorded since the last `reset_damage`, if any.
    /// Suppressed while scrolled up — a content scroll must not shift the frozen
    /// viewport.
    ///
    /// **The count is capped at the region's own height.** Shifting a region
    /// by more than its height moves every source row outside it, so the surplus
    /// names nothing a consumer can act on — while it does overflow the wire's
    /// `i16` and turn an up-scroll into a down-scroll: measured, a single
    /// 32 770-byte `feed()` of newlines, no slow consumer required. Both references
    /// that state a quantity at their own scroll sites clamp it to the same bound
    /// (alacritty `term/mod.rs:773`, ghostty `Terminal.zig:2703`).
    ///
    /// The cap is here, on the **read**, and not on the accumulator in
    /// `record_scroll`: a region that scrolls far and comes back then still reports
    /// its true small net, instead of one walked down from a saturated value.
    ///
    /// A second, crate-internal bound backs it up, and it is representational rather
    /// than semantic: [`MAX_ROWS`] is `u16::MAX` while the wire field is `i16`, so a
    /// region can legally be taller than any count that field can hold. In that
    /// corner the magnitude truncates. What it never does is wrap — a wrapped count
    /// arrives with the opposite sign and the consumer shifts the wrong way, which is
    /// the whole reason the saturation is here.
    pub fn scroll_delta(&self) -> Option<ScrollOp> {
        if self.display_offset > 0 {
            return None;
        }
        self.scroll.map(cap_scroll)
    }

    /// Build a serializable [`Frame`] from the current damage + grid + grapheme
    /// pool. `Full` ships every row; `Partial` ships the damaged spans. The
    /// global side-table is remapped to **frame-local** indices — the engine pool
    /// is append-only and leaky, so a frame carries only the clusters its cells
    /// reference, renumbered, with each cell's `extra` rewritten to the local id.
    pub fn frame(&self) -> Frame {
        let cols = self.grid.cols();
        let rows = self.grid.rows();
        let (kind, line_spans): (FrameKind, Vec<(usize, usize, usize)>) = match self.frame_damage()
        {
            TermDamage::Full => (
                FrameKind::Full,
                (0..rows).map(|l| (l, 0, cols - 1)).collect(),
            ),
            TermDamage::Partial(lines) => (
                FrameKind::Partial,
                lines
                    .into_iter()
                    .map(|d| (d.line, d.left, d.right))
                    .collect(),
            ),
        };

        // Frame-local numbering for the hyperlink table (#26). Keyed by the URI's
        // *identity* — the `Arc` pointer — so two cells sharing one open share one entry
        // and a distinct open gets its own, which is exactly the semantics the pool
        // index used to carry.
        //
        // Sized by this frame, not by session history (#628). It was
        // `vec![0u32; hyperlink_pool.len() + 1]`, allocated and zeroed on **every**
        // frame against every OSC 8 the session had ever seen — measured at 10 µs per
        // frame with 100 000 opens retained. With the pool gone there is nothing left to
        // size it by, and the cost disappears rather than being reduced.
        let mut link_table: Vec<String> = Vec::new();
        let mut link_remap: std::collections::HashMap<*const u8, u32> =
            std::collections::HashMap::new();
        // Cells come from the viewport at `display_offset`, not the live grid:
        // viewport row `line` is absolute buffer line `top + line` (scrollback
        // when scrolled up, the live grid when `display_offset == 0`, where
        // `top == scrollback.len()` and this is identical to reading the grid).
        // Without this, a wire consumer — cells reach it only through `frame()` —
        // could never display scrollback (#48).
        let top = self.scrollback.len() - self.display_offset;
        let mut spans = Vec::with_capacity(line_spans.len());
        for (line, left, right) in line_spans {
            let mut cells = Vec::with_capacity(right - left + 1);
            let mut combining = std::collections::BTreeMap::new();
            let mut links = std::collections::BTreeMap::new();
            let mut ucolors = std::collections::BTreeMap::new();
            let row = self.abs_row(top + line);
            let last_col = row.len().saturating_sub(1);
            for col in left..=right {
                let mut cell = row[col];
                // Soft-wrap is a row property (#538), but the wire has no per-row slot — so it is
                // *derived* back onto the last cell's WRAPLINE bit here, which keeps the format
                // byte-identical and is why moving the storage needed no VERSION bump. The bit is
                // therefore wire-only: on a live grid it is never set, and `Row::is_wrapped` is
                // the question to ask.
                if col == last_col && row.is_wrapped() {
                    cell.insert_flags(CellFlags::WRAPLINE);
                }
                // Combining clusters and hyperlinks live in the row's maps; each
                // tagged cell contributes its reference to the frame, recorded on
                // the span by span-relative column (the cell holds only the bit).
                if let Some(marks) = row.combining_at(col) {
                    // The cluster itself, at its column — no side table and no index
                    // since v14 (#621). Nothing interned these (this push was
                    // unconditional), so the index only ever bought indirection.
                    combining.insert(col - left, marks.to_vec());
                }
                if let Some(uri) = row.link_at(col) {
                    // Number each distinct open once per frame (only referenced URIs
                    // ship). The wire keeps its interning — #621 measured inlining a URI
                    // per linked cell at +171…403% — so this stays an index into
                    // `link_table`; only the *engine* side stopped being a table.
                    let key = std::sync::Arc::as_ptr(uri) as *const u8;
                    let next = link_table.len() as u32 + 1;
                    let fidx = *link_remap.entry(key).or_insert_with(|| {
                        link_table.push(uri.to_string());
                        next
                    });
                    let fidx = core::num::NonZeroU32::new(fidx)
                        .expect("frame-local link indices are 1-based");
                    links.insert(col - left, fidx);
                }
                // Underline colour (SGR 58, #520): a colour reference, not a
                // side-table index, so it rides the span inline. `ucolor_at` is
                // flag-gated + already Default-filtered (the stamp only fires on an
                // underlined cell), so a present entry is a real non-default colour.
                if let Some(color) = row.ucolor_at(col) {
                    ucolors.insert(col - left, color);
                }
                cells.push(cell);
            }
            spans.push(Span {
                line: line as u16,
                left: left as u16,
                right: right as u16,
                cells,
                combining,
                links,
                ucolors,
            });
        }

        Frame {
            cols: cols as u16,
            rows: rows as u16,
            kind,
            // The live cursor: position in screen coords + DECTCEM visibility.
            // Reported, not drawn — the consumer renders the caret (#38).
            cursor_row: self.cursor.row as u16,
            cursor_col: self.cursor.col as u16,
            // Hidden while scrolled up: the live cursor is off the frozen
            // viewport, and a cell-invert caret would otherwise ink over
            // scrollback. Consistent with the frozen-damage policy (no cursor
            // damage is emitted while scrolled) and with xterm.js / alacritty,
            // which hide the caret when it falls outside the visible rows (#48).
            cursor_visible: self.cursor.visible && self.display_offset == 0,
            cursor_shape: self.cursor.shape,
            cursor_blink: self.cursor.blink,
            // Viewport scroll position for the consumer's scrollbar (ADR-0013).
            display_offset: self.display_offset as u32,
            scrollback_len: self.scrollback.len() as u32,
            evicted_total: self.evicted_total,
            marker_epoch: self.marker_epoch,
            // The active buffer's population, which is what `marker_index` reports and
            // therefore what a consumer's held index is compared against (#490).
            marker_count: self.markers().len() as u32,
            // The mouse tracking mode as a routing mask (#129): which mouse events
            // the app wants, derived from the protocol by the single source
            // `encode_mouse` shares. The consumer routes app-vs-local on it.
            mouse_events: self.mouse_protocol.wanted_events(),
            // Alt-screen flag (#149): buffer-global state the consumer can't
            // derive from viewport damage; the a11y announce policy gates on it.
            alt_screen: self.on_alt,
            // Which modified C0 keys reach the application under the current keyboard
            // modes (#941), derived from the encoder `encode_key` runs.
            modified_keys: crate::input::modified_keys(
                self.app_cursor_keys,
                self.application_keypad,
                self.kitty_flags,
                self.modify_other_keys_2,
            ),
            scroll: self.scroll_delta(),
            spans,
            link_table,
            // Interaction overlays projected onto this viewport (#108): the
            // engine-owned selection and the consumer-supplied search highlights,
            // each re-projected here so the scroll offset is applied once, by the
            // same authority that projects the cells.
            overlay: Overlay {
                selection: self.selection_range(),
                matches: self
                    .search_highlights
                    .iter()
                    .flat_map(|m| self.match_spans(m))
                    .collect(),
                // The consumer-designated active match (#428), projected through
                // the same `match_spans` math — usually also present in `matches`
                // above (the renderer's ranking resolves the overlap, #424), but
                // a span designation may sit OUTSIDE a capped hand-over (#436).
                active_match: self
                    .active_search_highlight
                    .as_ref()
                    .map(|m| self.match_spans(m))
                    .unwrap_or_default(),
                markers: self.marker_positions(),
            },
        }
    }

    /// Record a scroll of rows `[top, bottom]` by `count` (positive = up).
    ///
    /// Damage is indexed by row position, so it must follow the content the
    /// scroll just moved: rotate the bounds the same way and mark the newly
    /// exposed line fully damaged (it is new blank content for the consumer).
    fn record_scroll(&mut self, top: usize, bottom: usize, count: isize) {
        let cols = self.grid.cols();
        match count {
            1 => {
                self.line_damage[top..=bottom].rotate_left(1);
                self.line_damage[bottom] = LineBounds::fully_damaged(cols);
            }
            -1 => {
                self.line_damage[top..=bottom].rotate_right(1);
                self.line_damage[top] = LineBounds::fully_damaged(cols);
            }
            _ => {}
        }
        // Accumulate repeated scrolls of the same region into one op (flow
        // control). A *different* region cannot be expressed as one op, so
        // degrade to full rather than silently dropping the earlier scroll.
        match self.scroll {
            Some(op) if op.top == top && op.bottom == bottom => {
                self.scroll = Some(ScrollOp {
                    top,
                    bottom,
                    count: op.count + count,
                });
            }
            None => self.scroll = Some(ScrollOp { top, bottom, count }),
            Some(_) => {
                self.scroll = None;
                self.mark_fully_damaged();
            }
        }
    }

    /// Number of lines currently held in scrollback history.
    /// Replace the word-boundary set used by Word (semantic) selection — the policy half
    /// of `selection_begin(.., SelectionType::Word)`, injected per [ADR-0017](https://github.com/kihyun1998/justerm/blob/master/docs/adr/0017-core-consumer-boundary-mechanism-vs-policy.md) (core owns
    /// the buffer walk, the consumer owns which characters separate words). The default
    /// is [`DEFAULT_WORD_SEPARATORS`].
    ///
    /// **`' '` is forced into whatever you pass**, and that is not a convenience. A
    /// blank cell packs `' '`, so the space terminates the walk at the end of a row's
    /// written text *and* backstops the wide-pair rule: without it, double-clicking next
    /// to a wide separator starts the highlight on that separator's trailing spacer,
    /// bisecting the glyph, and the walk then runs to the row's end through the padding.
    /// Enforcing it here rather than in the walk is ghostty's shape — it prepends its own
    /// blank codepoint to every parsed set at the config intake (`config/Config.zig`,
    /// *"Always include null as first boundary"*), so `selectWord` never has to.
    ///
    /// A consequence worth knowing before you narrow the set: this predicate is the only
    /// thing bounding the walk, so a set that omits the separators actually present in
    /// the buffer makes one double-click walk the whole soft-wrap run — measured at 11.7 ms
    /// (release) selecting 801,920 chars.
    ///
    /// If a length bound is ever wanted, **it is a field beside this one, not an argument**:
    /// `word_start` / `word_end` are `pub(super)`, reached through
    /// [`Term::selection_begin`], so there is no call site for a consumer to inject into.
    /// This setter is the shape it would take (injected policy over a core
    /// mechanism, [ADR-0017](https://github.com/kihyun1998/justerm/blob/master/docs/adr/0017-core-consumer-boundary-mechanism-vs-policy.md)).
    pub fn set_word_separators(&mut self, separators: &str) {
        let mut set: String = separators.to_owned();
        if !set.contains(' ') {
            set.push(' ');
        }
        self.word_separators = set;
    }

    /// The word-boundary set currently in force — what was passed to
    /// [`Term::set_word_separators`] plus the forced `' '`, or
    /// [`DEFAULT_WORD_SEPARATORS`] if it was never called.
    pub fn word_separators(&self) -> &str {
        &self.word_separators
    }

    pub fn scrollback_len(&self) -> usize {
        self.scrollback.len()
    }

    /// Whether the app has an open synchronized-output block (DEC ?2026).
    pub fn synchronized_output(&self) -> bool {
        self.synchronized_output
    }

    /// Whether the app enabled color-scheme-update notifications (DEC ?2031).
    pub fn color_scheme_updates(&self) -> bool {
        self.color_scheme_updates
    }

    /// Whether the app enabled grapheme-cluster mode (DEC ?2027): emoji ZWJ / skin-tone /
    /// flag / VS16 sequences are clustered into one cell. OFF (default) is per-char, wcwidth-compat.
    pub fn grapheme_clustering(&self) -> bool {
        self.grapheme_clustering
    }

    /// Whether the app enabled win32-input-mode (DEC ?9001). The engine does
    /// not encode the raw key-records itself (a non-goal); a ConPTY consumer reads
    /// this to decide whether to emit them.
    pub fn win32_input_mode(&self) -> bool {
        self.win32_input_mode
    }

    /// Queue a color-scheme report (`CSI ? 997 ; 1 n` dark / `; 2 n` light) on the
    /// reply channel. The consumer calls this to answer a `ColorSchemeQuery` event
    /// or, when its scheme changes and `color_scheme_updates()` is set, to send the
    /// unsolicited notification. The engine never stores or interprets the scheme.
    pub fn report_color_scheme(&mut self, dark: bool) {
        let ps = if dark { 1 } else { 2 };
        self.replies
            .extend_from_slice(format!("\x1b[?997;{ps}n").as_bytes());
    }

    /// OSC 10/11/12 set/query the default fg/bg/cursor colour, stacking the
    /// `;`-separated specs across the `[foreground, background, cursor]` slots —
    /// xterm's `ChangeColorsRequest` offset loop (`misc.c:3679`, walking
    /// `OSC_TEXT_FG` → `OSC_TEXT_BG` → `OSC_TEXT_CURSOR`, `ptyx.h:1018-1020`).
    /// OSC 10 starts at slot 0, OSC 11 at slot 1, OSC 12 at slot 2 (#137, #832).
    /// A `?` spec is a query.
    ///
    /// **An empty spec addresses its slot and leaves it alone** — neither a set
    /// nor a reset — and the stack still advances past it, so `OSC 10 ; ; <bg>`
    /// is how xterm reaches the background alone. That skip-and-advance is xterm's
    /// *implementation*, not documented behaviour: `ctlseqs.txt:2082` documents only
    /// the stack (*"each successive parameter changes the next color in the list"*)
    /// and expects at least one parameter. The two empty
    /// cases are the same rule from both ends: nothing left in the string yields
    /// no name (`misc.c:3684-3685`), and a separator where a name should be yields no
    /// name either (`misc.c:3687`) before the parse steps past it.
    ///
    /// That rule is not a hardening detail here, it is a precondition: the empty
    /// form is the *only* one real applications emit for OSC 12 (`nvim` sends
    /// `ESC ] 12 ; BEL` four to five times per session), so a cursor slot without
    /// it would relay a burst of empty-string colour changes every time a user
    /// opens an editor (#832).
    ///
    /// The stack ends after the cursor. xterm's next slots are the pointer
    /// colours (`OSC_MOUSE_FG` = 13, `OSC_MOUSE_BG` = 14), which justerm does not
    /// model — dropping a fourth spec is better than mis-addressing it.
    fn special_color(&mut self, params: &[&[u8]], start: usize, terminator: Terminator) {
        for (i, &spec) in params[1..].iter().enumerate() {
            if spec.is_empty() {
                continue; // skip this slot, but still advance to the next
            }
            let event = match start + i {
                0 if spec == b"?" => TermEvent::QueryForeground { terminator },
                0 => TermEvent::SetForeground(String::from_utf8_lossy(spec).into_owned()),
                1 if spec == b"?" => TermEvent::QueryBackground { terminator },
                1 => TermEvent::SetBackground(String::from_utf8_lossy(spec).into_owned()),
                2 if spec == b"?" => TermEvent::QueryCursorColor { terminator },
                2 => TermEvent::SetCursorColor(String::from_utf8_lossy(spec).into_owned()),
                _ => break, // past [fg, bg, cursor] — the pointer colours are unmodelled
            };
            self.events.push(event);
        }
    }

    /// OSC 52 (`OSC 52 ; Pc ; Pd`) — an application asking to put text on a
    /// selection, or to read one back (#828).
    ///
    /// The engine's half is *mechanism* and nothing else: recognise the
    /// sequence, resolve `Pc` to a [`ClipboardTarget`], decode `Pd`, and relay.
    /// It never touches a clipboard, never holds one, and carries no allow/deny
    /// knob — under ADR-0017 that gate is the consumer's, and a consumer that
    /// drops the event has refused the request. alacritty puts a gate at the
    /// equivalent site (`alacritty_terminal/src/term/mod.rs:1706`) — **not because
    /// it is the whole terminal, which is what this comment used to say and is
    /// not the distinction (#841)**: that gate is in alacritty's *engine* crate
    /// too, reading a policy the application injects through `Config`
    /// (`:353`, written at `alacritty/src/config/ui_config.rs:125`). The reason
    /// this crate has none is that it holds no clipboard at all, so a gate in
    /// front of a relay refuses nothing a dropped event does not already refuse.
    ///
    /// **An absent target field means the clipboard, and that is a divergence
    /// from the spec taken deliberately.** `ctlseqs.txt:2161` says *"If the
    /// parameter is empty, xterm uses s 0, to specify the configurable
    /// primary/clipboard selection and cut-buffer 0"*, and `misc.c:3359` is that
    /// sentence in code. Neither half is representable here: `s` is whichever
    /// selection a *user resource* has configured — policy, which ADR-0017 puts
    /// in the consumer — and cut buffers are not modelled at all. So "follow the
    /// spec" is not a well-defined instruction, exactly as it was not for #834's
    /// empty colour spec, where xterm's trigger (*a colour that failed to parse*)
    /// is a condition this engine structurally cannot observe.
    ///
    /// Two qualifications, because the short version of this argument overclaims
    /// in both directions. **The cut buffer is what is unrepresentable; `s` is
    /// merely unmodelled** — xterm resolves it through the `selectToClipboard`
    /// resource (`button.c:2081`), and DECSET 1041 sets that same resource *from
    /// the stream* (`ctlseqs.txt:1008`), so an engine tracking 1041 could
    /// resolve it. justerm declines to model 1041; that is a choice, not an
    /// impossibility. And **xterm-as-shipped reads the empty field as PRIMARY**,
    /// since the resource defaults to false — so this diverges from what the
    /// reference does by default, not merely from a sentence in its manual.
    ///
    /// What decides it is the other two lines of evidence. **Independent
    /// lineages, and there are fewer than a naive count gives**: alacritty never
    /// sees an empty field at all, because `vte` substitutes `b'c'` first
    /// (`vte-0.15.0/src/ansi.rs:1488`) — those two are *one* lineage, not two.
    /// The genuinely separate ones are ghostty, by an explicit byte-scan branch
    /// pinned under a test (`clipboard_operation.zig:24`, `:64`), and xterm.js's
    /// clipboard addon, whose browser provider ignores the selector entirely and
    /// always writes `navigator.clipboard`
    /// (`addons/addon-clipboard/src/ClipboardAddon.ts:77`). Three lineages, one
    /// answer. **And the emitter's own documentation agrees**: `tmux`'s
    /// `set-clipboard` is documented as setting *the terminal clipboard* — never
    /// the primary selection — and `tmux` 3.2a is measured sending exactly this
    /// empty form.
    ///
    /// **A missing payload *field* is not an empty payload.** `OSC 52 ; c`
    /// arrives as two fields and does nothing; `OSC 52 ; c ;` arrives as three,
    /// the third empty, and is a store of the empty string — which is how the
    /// sequence clears a selection. xterm makes the same split by construction,
    /// its whole handler sitting inside `if (*buf == ';')` (`misc.c:3353`), and
    /// ghostty rejects the payload-less form for the same reason
    /// (`clipboard_operation.zig:20`).
    ///
    /// **The payload is `params[2..]` rejoined**, the rule #650 established for
    /// OSC 8: `vte` splits the whole OSC body on `;`, so reading `params[2]`
    /// alone would take a payload containing a `;` and decode its first piece —
    /// which for a well-formed prefix is a *successful* decode of a truncated
    /// clipboard, the one failure mode this handler must not have. Rejoined, the
    /// stray `;` reaches the decoder and is refused there.
    ///
    /// **Malformed in, nothing out**, which is the second deliberate divergence
    /// — and it is narrower than the spec sentence makes it look. The spec ends
    /// a payload that is *"neither a base64 string nor ?"* by clearing the
    /// selection (`ctlseqs.txt:2174`); this drops it silently. Clearing is
    /// destructive, and inferring one from bytes the engine could not parse
    /// means corruption on the wire wipes what the user copied by hand.
    ///
    /// The family, counted rather than asserted: **three drop** — alacritty
    /// (`alacritty_terminal/src/term/mod.rs:1717`), ghostty, which returns on a
    /// decode failure (`src/Surface.zig:2186`) and states the rule beside its
    /// test as *"Read requests and malformed base64 must never reach the
    /// callback"* (`src/terminal/c/terminal.zig:2961`), and this. **One clears**
    /// — xterm.js's addon, deliberately: *"Clear clipboard if text is not a
    /// base64 encoded string"* (`addons/addon-clipboard/src/ClipboardAddon.ts:55`).
    /// **And one neither** — xterm, below.
    ///
    /// What the divergence actually is, stated precisely because reading the
    /// spec alone gets it wrong: **xterm has no validator to disagree with.**
    /// `AppendToSelectionBuffer` (`button.c:4679`) decodes one character at a
    /// time and `return`s on any byte outside the alphabet (`:4698`), so xterm
    /// *filters* rather than rejects — `Zm9v-Zm9v` yields `foofoo` there — and
    /// since the store path clears the buffer first (`misc.c:3410`), the spec's
    /// "cleared" is what falls out when the filter finds nothing to keep. So the
    /// disagreement is about what to **accept**, not about what to do on
    /// refusal, and this engine is the stricter of the two on purpose: a filter
    /// hands the consumer text assembled from bytes the application did not
    /// send.
    ///
    /// Non-UTF-8 is refused on the same principle one level up: every text
    /// surface this crate publishes is UTF-8, and a lossy conversion would hand
    /// the consumer characters the application never sent.
    fn clipboard(&mut self, params: &[&[u8]], terminator: Terminator) {
        let Some(&field) = params.get(1) else {
            return;
        };
        let target = match field {
            // Empty and `c` are the same answer; see the divergence note above.
            b"" | b"c" => ClipboardTarget::Clipboard,
            // `p` and `s` are NOT the same answer, and the first draft made them
            // one. See `ClipboardTarget`: a collapse here would put a selector
            // the application never wrote into the reply.
            b"p" => ClipboardTarget::Primary,
            b"s" => ClipboardTarget::Selection,
            // Anything else — an unmodelled target like `q` or a cut buffer, and
            // also a *multi*-target list like `pc`, which the spec permits
            // (`ctlseqs.txt:2156`) and this engine cannot express. Both are
            // dropped rather than approximated: honouring one target of two is
            // the same defect as truncating a payload, one axis over, and
            // `vte`/alacritty's first-byte-wins would do exactly that. ghostty
            // rejects a multi-byte field too (`clipboard_operation.zig:36`).
            _ => return,
        };
        // Two fields is `OSC 52 ; c` — no payload field at all, not an empty one.
        if params.len() < 3 {
            return;
        }
        // The bound is checked on the fields, BEFORE the join — `join` is itself
        // an unconditional full copy, so checking after it would let a hostile
        // payload buy a second allocation the size of the first. `+ len - 3` is
        // the separators the join puts back.
        let fields = &params[2..];
        if fields.iter().map(|f| f.len()).sum::<usize>() + fields.len() - 1 > MAX_CLIPBOARD_BASE64 {
            return;
        }
        let payload: Vec<u8> = fields.join(&b';');
        if payload == b"?" {
            self.events
                .push(TermEvent::QueryClipboard { target, terminator });
            return;
        }
        if let Some(bytes) = crate::base64::decode(&payload)
            && let Ok(text) = String::from_utf8(bytes)
        {
            self.events.push(TermEvent::ClipboardStore { target, text });
        }
    }

    /// Answer an OSC 52 [`TermEvent::QueryClipboard`]: base64-encode the
    /// consumer's text into the OSC 52 reply envelope, ST-terminated.
    ///
    /// The consumer hands the target back rather than the engine remembering
    /// which one was asked about — the same shape as
    /// [`Term::report_palette_color`], which takes its `index` back for the same
    /// reason. alacritty is the alternative: its query captures the target and
    /// the terminator in a closure the consumer later calls
    /// (`alacritty_terminal/src/term/mod.rs:1740`), which is one more piece of
    /// hidden state and one more question ("what if replies interleave?") bought
    /// for nothing the consumer does not already hold.
    ///
    /// **Answering is optional, and that is the security property.** The engine
    /// holds no clipboard, so a query it is never asked to answer reveals
    /// nothing; a consumer refuses a *read* simply by not calling this, whatever
    /// it does about *writes*.
    ///
    /// **The selector round-trips.** `c` / `p` / `s` in, the same one out, which
    /// is why [`ClipboardTarget`] keeps `p` and `s` apart: every reference echoes
    /// the field the application wrote — xterm the recognised list
    /// (`misc.c:3384`), alacritty the raw byte (`…/term/mod.rs:1744`), ghostty
    /// its three locations (`src/Surface.zig:5954`) — and it is the one field a
    /// client can pair a reply on. The single exception is an **empty** field,
    /// answered naming `c`, which is what alacritty also sends once `vte` has
    /// defaulted it: the reply says what the engine understood, and there is no
    /// selector to echo.
    ///
    /// The reply echoes the terminator the query arrived with, like every other
    /// reply this crate queues — settled for the whole channel rather than for
    /// this sequence alone.
    pub fn report_clipboard(
        &mut self,
        target: ClipboardTarget,
        text: &str,
        terminator: Terminator,
    ) {
        let field = match target {
            ClipboardTarget::Clipboard => 'c',
            ClipboardTarget::Primary => 'p',
            ClipboardTarget::Selection => 's',
        };
        let data = crate::base64::encode(text.as_bytes());
        self.replies
            .extend_from_slice(format!("\x1b]52;{field};{data}").as_bytes());
        self.replies.extend_from_slice(terminator.bytes());
    }

    /// Answer an OSC 4 palette query: wrap the consumer-supplied spec for
    /// `index` in the OSC 4 reply envelope.
    ///
    /// The reply echoes the terminator the query arrived with, which the
    /// consumer takes off the `Query…` event and hands back here: the
    /// spec says a terminal *"uses the same terminator used in a query"*
    /// (`ctlseqs.txt:2020`), and the engine cannot choose on the consumer's
    /// behalf because only the parser ever saw which byte arrived.
    pub fn report_palette_color(&mut self, index: u8, spec: &str, terminator: Terminator) {
        self.replies
            .extend_from_slice(format!("\x1b]4;{index};{spec}").as_bytes());
        self.replies.extend_from_slice(terminator.bytes());
    }

    /// Answer an OSC 10 foreground query: wrap the consumer-supplied spec
    /// in the OSC 10 reply envelope.
    ///
    /// The reply echoes the terminator the query arrived with, which the
    /// consumer takes off the `Query…` event and hands back here: the
    /// spec says a terminal *"uses the same terminator used in a query"*
    /// (`ctlseqs.txt:2020`), and the engine cannot choose on the consumer's
    /// behalf because only the parser ever saw which byte arrived.
    pub fn report_foreground(&mut self, spec: &str, terminator: Terminator) {
        self.replies
            .extend_from_slice(format!("\x1b]10;{spec}").as_bytes());
        self.replies.extend_from_slice(terminator.bytes());
    }

    /// Answer an OSC 11 background query: wrap the consumer-supplied spec
    /// (it knows its palette) in the OSC 11 reply envelope. The engine formats
    /// the envelope only — it never knows the colour.
    ///
    /// The reply echoes the terminator the query arrived with, which the
    /// consumer takes off the `Query…` event and hands back here: the
    /// spec says a terminal *"uses the same terminator used in a query"*
    /// (`ctlseqs.txt:2020`), and the engine cannot choose on the consumer's
    /// behalf because only the parser ever saw which byte arrived.
    pub fn report_background(&mut self, spec: &str, terminator: Terminator) {
        self.replies
            .extend_from_slice(format!("\x1b]11;{spec}").as_bytes());
        self.replies.extend_from_slice(terminator.bytes());
    }

    /// Answer an OSC 12 cursor-colour query: the same envelope one slot
    /// over, terminated like its siblings. The consumer supplies the spec — it
    /// owns the palette, and the engine never learns the colour.
    ///
    /// The reply echoes the terminator the query arrived with, which the
    /// consumer takes off the `Query…` event and hands back here: the
    /// spec says a terminal *"uses the same terminator used in a query"*
    /// (`ctlseqs.txt:2020`), and the engine cannot choose on the consumer's
    /// behalf because only the parser ever saw which byte arrived.
    pub fn report_cursor_color(&mut self, spec: &str, terminator: Terminator) {
        self.replies
            .extend_from_slice(format!("\x1b]12;{spec}").as_bytes());
        self.replies.extend_from_slice(terminator.bytes());
    }

    /// The cells of visible row `i` (0..rows) at the current scroll position.
    /// The viewport windows into `[history.. ; screen..]`: rows above
    /// `scrollback.len()` come from history, the rest from the live screen.
    pub fn viewport_line(&self, i: usize) -> &[Cell] {
        let top = self.scrollback.len() - self.display_offset;
        let idx = top + i;
        if idx < self.scrollback.len() {
            &self.scrollback[idx]
        } else {
            self.grid.row(idx - self.scrollback.len())
        }
    }

    /// Scroll the viewport up by `n` lines into history (clamped to the oldest).
    pub fn scroll_up(&mut self, n: usize) {
        let target = (self.display_offset + n).min(self.scrollback.len());
        self.set_display_offset(target);
    }

    /// Scroll the viewport down by `n` lines toward the live screen.
    pub fn scroll_down(&mut self, n: usize) {
        let target = self.display_offset.saturating_sub(n);
        self.set_display_offset(target);
    }

    /// Jump the viewport back to the live screen (follow the bottom).
    pub fn scroll_to_bottom(&mut self) {
        self.set_display_offset(0);
    }

    /// Move the viewport. A user scroll changes which lines are visible, so the
    /// whole viewport is repainted (full damage) when the offset actually moves.
    fn set_display_offset(&mut self, offset: usize) {
        // The alt screen has no scrollback to view; scroll intents are no-ops.
        if self.on_alt {
            return;
        }
        if offset != self.display_offset {
            self.display_offset = offset;
            self.mark_fully_damaged();
        }
    }

    // ---- selection -----------------------------------------------------------

    /// Map a viewport cell `(row, col)` to an absolute buffer point. The top
    /// visible row is `scrollback.len() - display_offset`, so viewport row `i`
    /// is that plus `i`.
    ///
    /// **`row` is clamped to the last visible row, and that is the anchor's whole defence
    /// against a caller that hands it one past the end (#660).** The row arrives from a
    /// pointer position, so it is off the end whenever a drag leaves the grid — including
    /// the ordinary case where the container is a sub-cell remainder taller than
    /// `rows × cell_height` and a click lands in that strip. Stored unclamped it does not
    /// fail here: it detonates later, in whichever read walks the selection
    /// (`selection_range`, `selection_text`, the word extents), so the stack trace accuses
    /// the reader rather than the caller — the delay `damage_span`'s doc describes and
    /// #536 was filed about.
    ///
    /// **Clamped, and deliberately *not* `debug_assert`ed** — which is where this differs
    /// from `damage_span`, whose split it otherwise mirrors. That function is engine-
    /// internal, so an out-of-range span there is a justerm bug and the assert names its
    /// producer. This one is reached from `Engine::selection_begin` / `selection_extend`,
    /// whose documented input is *"what a mouse event carries"* — and a pointer leaves the
    /// grid whenever a drag does, so a row past the end is **ordinary input, not a defect**.
    /// Asserting on it would panic a consumer's debug build for a legal gesture.
    ///
    /// Clamping is also what every producer already wants: a drag past the bottom edge
    /// selects to the edge. alacritty clamps at the same boundary (`Point::grid_clamp`);
    /// ghostty's pins cannot express an out-of-range row at all.
    ///
    /// **This is a backstop, and since #667 nothing in the family relies on it.** The
    /// sentence here used to read that justerm-web's selection converter did *not* clamp,
    /// which was what made an unclamped row reachable in the shipped stack rather than
    /// only in theory; that converter now bounds both axes at its own seam, as all three
    /// references do at theirs. The claim is retracted rather than deleted because it was
    /// the record of why this clamp was worth adding.
    ///
    /// **`col` is bounded the same way, and against the grid rather than the line
    /// (#671).** #660 reasoned about the row alone and this function passed the column
    /// through, which was not a smaller version of the same gap — it was a *different*
    /// one, because the two axes are consumed differently downstream. A column reaches
    /// `resolve`, where the `Side` decides whether it gets a `+ 1`, and the two readers
    /// then bound only one end each: `selection_range`'s Linear arm clips `right_excl`
    /// and not `left`, `selection_text`'s Block arm clips `hi` and not `from`. So
    /// `Side::Right` was already safe by accident (its `+ 1` lands past the end and the
    /// clip catches it) while **`Side::Left` had no `+ 1` to clip**, and the raw column
    /// survived into `left` — silently deleting the anchor's own row from both the
    /// projection and the copy. `usize::MAX` was the one value that panicked instead,
    /// on the `+ 1`.
    ///
    /// Bounding here rather than in `resolve` keeps one site answering "what does a
    /// viewport coordinate mean", and makes both axes total for the same reason; the
    /// alternative — clamping at each `+ 1` — is five sites for one rule. alacritty
    /// bounds both endpoints' columns in `Selection::to_range` *before* its own side
    /// arithmetic and pairs the `+ 1` with an explicit *"column == columns → wrap to the
    /// next line"*; justerm reaches that same outcome through the reader's
    /// `right_excl > left`, which is why an **in-range** `Side::Right` on the last column
    /// still starts the selection on the following row and is pinned as unchanged.
    ///
    /// The grid, not `abs_line(..).len()`, is the bound: `SelectionType::Line` already
    /// resolves `to` as `grid.cols()`, so the whole type works in grid coordinates and a
    /// short line must not shrink a selection that reaches past it.
    ///
    /// **`resolve`'s five `+ 1`s stay unguarded, and that is sound only while every stored
    /// anchor arrives through here.** The completeness pass enumerated the writers: the
    /// three coordinate fixups move `.line` or write columns that are in range by
    /// construction, `resize`'s primary branch re-clamps the reflowed points (#562) and its
    /// alt branch drops the selection outright (#660), and `Term::resize` is the only writer
    /// of `grid.cols()`. So no path strands a column that was clamped here. The condition is
    /// **a fourth writer of `self.selection`** — one that builds an `Anchor` without this
    /// function would put `resolve` back in reach of its own arithmetic.
    fn viewport_to_abs(&self, row: usize, col: usize) -> BufferPoint {
        let top = self.scrollback.len() - self.display_offset;
        let last = self.grid.rows().saturating_sub(1);
        BufferPoint {
            line: top + row.min(last),
            col: col.min(self.grid.cols().saturating_sub(1)),
        }
    }

    /// The hyperlink **URI** at **screen** `(row, col)` (the live grid), or `None` —
    /// flag-gated through the row's link map. Since #628 the map holds the URI itself,
    /// so there is no index and no second call to resolve one.
    /// Mirrors `grid().cell(row, col)`.
    pub(crate) fn screen_link_at(&self, row: usize, col: usize) -> Option<Hyperlink> {
        self.grid
            .row_ref(row)
            .link_at(col)
            .cloned()
            .map(Hyperlink::new)
    }

    /// The underline colour (SGR 58, #520) at screen `(row, col)`, as a theme-agnostic
    /// reference. `Color::Default` means "follow the fg" — the common case, and what an
    /// unset cell returns. Mirror of [`Term::screen_link_at`].
    pub(crate) fn screen_underline_color_at(&self, row: usize, col: usize) -> Color {
        self.grid.row_ref(row).ucolor_at(col).unwrap_or_default()
    }

    /// The hyperlink URI at **viewport** `(row, col)` (visible window, history
    /// included at the current scroll), or `None`. Mirrors `viewport_line(row)`.
    pub(crate) fn viewport_link_at(&self, row: usize, col: usize) -> Option<Hyperlink> {
        let idx = self.scrollback.len() - self.display_offset + row;
        self.abs_row(idx).link_at(col).cloned().map(Hyperlink::new)
    }

    /// Resize the screen to `cols` x `rows`. Rows dropped off the top (on shrink)
    /// enter scrollback. Column reflow of soft-wrapped lines is layered on top
    /// separately. The whole screen is damaged.
    ///
    /// `cols` is widened to [`MIN_COLUMNS`] — a narrower screen cannot hold a
    /// width-2 glyph, so it is clamped rather than represented.
    pub fn resize(&mut self, cols: usize, rows: usize) {
        // Not a print — and not a parser callback either, which is the whole reason
        // [`Term::repeat_anchor`] is stated as a rule rather than as a list of
        // `Perform` methods. A reflow rewrites cells and moves the cursor, so the cell
        // `REP` would read back is no longer the one the arming print wrote (#825).
        self.repeat_anchor = None;
        // A terminal is never 0-tall; clamp so the math below (rows - 1) can't
        // underflow. Columns clamp to MIN_COLUMNS, not 1: chunking by cols needs a
        // non-zero width, but a *wide glyph* needs two (#547). The ceiling is the frame
        // header's u16, clamped here as well as in the constructor — a ceiling that held
        // only until the first resize is the gap `new` had against this function's own row
        // floor before #547 (#621).
        let cols = cols.clamp(MIN_COLUMNS, MAX_COLUMNS);
        let rows = rows.clamp(1, MAX_ROWS);
        let old_cols = self.grid.cols();
        let old_rows = self.grid.rows();
        let limit = self.scrollback_limit;

        // A reflow rewrites marker lines outright, at three separate sites below and in
        // two different frames of reference — so a held index goes stale in a way no
        // offset repairs (#490). Bumped **here**, once, rather than beside each rewrite:
        // this function is the only way any of them runs, and a per-site obligation is
        // the shape `docs/map/territory/marker.md` already records as a known hole for
        // the alt guard. Gated on a *dimension change* as well as on there being a marker:
        // `resize` has no early return for unchanged geometry and `ResizePort` states no
        // idempotency guarantee, so a consumer may call this with the size it already has —
        // `justerm-web`'s fit does exactly that when the *cell* moves and the proposed grid
        // does not, since it dedupes on cell and grid together. An ungated bump would then be
        // a full re-pull for a resize that changed nothing — measured at 100 bumps for 100
        // no-op resizes.
        //
        // This comment said the fit loop *"re-asserts the size every frame"*, which stopped being true
        // when #632 gave `FitController` its four-field dedupe. The gate is unaffected: what it
        // rests on is the missing early return, and that is still measured.
        if (cols != old_cols || rows != old_rows)
            && (!self.normal_markers.is_empty() || !self.alt_markers.is_empty())
        {
            self.bump_marker_epoch();
        }

        // A reflow moves match coordinates (and can change the match set), so the
        // query-derived highlights are invalidated; the consumer re-searches at
        // the new width. The selection re-anchors below — it is user-authored.
        self.invalidate_search_highlights();

        // ...except on the alt screen, where a *shrink* drops the selection (#660). The
        // primary pane carries user-authored points through `reflow_pane` and gets them back
        // mapped to the new geometry; on alt the selection is dropped instead.
        //
        // **This is a policy choice, not a capability limit, and the difference matters
        // because the first version of this comment got it wrong.** It claimed the alt pane
        // has "nothing to re-anchor through" — measurably false: the alt branch below makes
        // its own `reflow_pane` call with tracked points and already uses the returned
        // `extras` / `evicted` to rotate and dispose alt *markers*. `reflow: false` disables
        // the column re-split, not the point tracking. Installing a false "cannot" as the
        // justification for fixing a false "cannot" is precisely the failure #660 is.
        //
        // What actually makes rotation the wrong trade here is that a marker and a selection
        // are different shapes. A marker is one point with a binary fate — survive, or be
        // disposed with an event. A selection is two *ordered* endpoints, so when a shrink
        // destroys the row under one of them and not the other, "dispose" has no meaning and
        // the correct behaviour is the clamp-and-overtake policy `selection_rotate_region`
        // implements for scrolls. Reusing the marker path would give a selection whose ends
        // moved by different rules; writing the second policy is a feature, not this fix.
        // And on a column shrink an alt anchor would additionally need the `.min(cols - 1)`
        // the primary branch applies, which alt markers deliberately do *not* take.
        //
        // Both references drop rather than rotate on the axis they consider unsafe —
        // alacritty on a width change (`term/mod.rs:680-682`), xterm.js on a height change,
        // its comment naming this bug class outright (`SelectionService.ts:156-160`).
        //
        // **Any geometry change, not just a shrink — and the `!=` is load-bearing in the
        // direction that looks wasteful.** The obvious refinement is to keep the selection on
        // a *grow*, since the alt pane pads rather than moving content, so no anchor looks
        // invalidated. That was tried and a randomised sweep refuted it in one run: an alt
        // resize also reflows the **primary** pane below, and on the alt screen `scrollback`
        // *is* that primary history — so `scrollback.len()` moves under an anchor whose
        // absolute line was measured from the old base, even when the alt grid itself does not
        // move at all. `selection_text` then walks off the end. The branch below already knows
        // this and converts alt *markers* through `old_base` → new base for exactly that
        // reason ("the primary scrollback below may rewrap and change length even when the alt
        // grid does not move"); the selection has no such conversion, so the geometry change
        // is the honest trigger.
        //
        // Rebasing instead of dropping is the better answer and is not done here: a grow has
        // no destroyed row, so both endpoints could shift by the base delta unambiguously —
        // but a *shrink* still needs the two-endpoint policy below, and shipping half of it
        // would leave the two axes behaving differently for no stated reason.
        //
        // The exact no-op is still not a resize: nothing reflows when neither axis moves, so
        // the base cannot shift, and a consumer that re-asserts its size every frame (a
        // `fit()` loop) must not make selecting on the alt screen impossible.
        if self.on_alt && (cols != old_cols || rows != old_rows) {
            self.selection = None;
        }

        // Both screens are resized. Scrollback pairs with the PRIMARY screen
        // (whichever is active) — the alt screen has no history of its own.
        // `reflow: true` is the *primary* pane's setting and is deliberately a constant, **not**
        // `self.autowrap`. ghostty gates its equivalent on DECAWM — `.reflow =
        // self.modes.get(.wraparound)` (`terminal/Terminal.zig` `resize`) — and the reading that
        // makes that coherent is the one this file just accepted for the alt screen: an application
        // that turns autowrap off is placing lines itself, so its content is a layout rather than a
        // flow, and re-wrapping it changes what it drew.
        //
        // Not followed here, for three reasons, and they are recorded rather than filed because
        // nothing observable is known to break either way (measured: with DECAWM off, a full
        // 6-column row still re-splits into two rows at width 3 exactly as it does with DECAWM on;
        // the difference against ghostty is that ghostty truncates that row instead).
        //
        // - **The wrap flag is not a lie.** `Row::is_wrapped` means "this row continues into the
        //   next", which after a re-split is simply true. DECAWM governs the **write** path — where
        //   a glyph goes when the cursor is at the last column — not how stored content is laid out
        //   again later. Dropping the flag would make `"abcdef"` extract as `"abc\ndef"`.
        // - **The mode is global and momentary; the buffer is neither.** DECAWM is read at resize
        //   time and would decide the fate of history written under the opposite setting. A TUI that
        //   turns it off while drawing would, on a resize landing in that window, leave every
        //   properly wrapped line in scrollback un-reflowed.
        // - **It costs content.** Not reflowing truncates each row to the new width, so the tail of
        //   a long line leaves the grid. justerm keeps it.
        //
        // There is no per-row signal to be finer with: a row written under DECAWM off and a row that
        // merely ended early are both simply unwrapped. "Do not re-split an unwrapped logical line"
        // would break ordinary reflow, since a line that exactly fills its width carries no wrap
        // flag either.
        let dims = ReflowDims {
            old_cols,
            cols,
            rows,
            limit,
            reflow: true,
        };
        let scrollback = std::mem::take(&mut self.scrollback);
        if self.on_alt {
            // Active = alt (cursor, no scrollback); inactive = primary. No selection anchors
            // to track here — but *because the geometry change above dropped them* (#660),
            // not because there cannot be any. This comment used to read "selection is
            // primary-only and cleared on alt enter": the clearing is real
            // (`enter_alt_screen` / `leave_alt_screen`, "a selection cannot survive a screen
            // swap") and says nothing about a selection made *while* the alt screen is up,
            // which is the ordinary act of copying out of vim. A premise that held at one
            // instant was read as an invariant holding for the screen's lifetime.
            // Alt markers still ride this pane, but **not because it reflows** — since #567 it does
            // not, so a marker's content no longer moves under it and the old reason here ("justerm
            // column-reflows the alt grid, so a marker must follow its content") is retracted. What
            // they ride it for is the row *fit*: a shrink still drops rows off the top, and a marker
            // on one of those has left a screen with no history to hold it. Their stored line is
            // `base + alt_row` (base = primary scrollback len), so convert to alt-local rows here
            // and re-anchor on the new base afterward — the primary scrollback below may rewrap and
            // change length even when the alt grid does not move at all.
            let old_base = scrollback.len();
            let mut alt_pts: Vec<(usize, usize)> = self
                .alt_markers
                .iter()
                .map(|m| (m.line - old_base, m.col))
                .collect();
            // Alt-scoped tracked points are stored on the same `base + alt_row`
            // frame as the alt markers, so they convert and come back the same way
            // (#691).
            let alt_tracked_off = alt_pts.len();
            alt_pts.extend(
                self.alt_tracked
                    .iter()
                    .map(|p| (p.line.saturating_sub(old_base), p.col)),
            );
            let alt = self.grid.take_lines();
            let r_alt = reflow_pane(
                alt,
                VecDeque::new(),
                self.cursor.point(),
                &alt_pts,
                ReflowDims {
                    limit: 0,
                    reflow: false,
                    ..dims
                },
            );
            self.grid.set_screen(r_alt.screen, cols, rows);
            self.cursor.set_point(r_alt.cursor, rows, cols);

            // Primary is inactive here, but markers anchor *primary* content, so
            // they reflow with it. There is no *primary* selection to carry alongside them —
            // `switch_to_alt` nulls it before the alt screen exists, so one cannot coexist
            // with `on_alt` — which is a different statement from the "cleared on alt enter"
            // this comment used to make, and the difference is #660: that clearing says
            // nothing about the *alt* selection the branch above now drops.
            // `(line, col)`, not `(line, 0)`: the column is what bounds OSC-133 command-text
            // extraction (#166), and discarding it here truncated the recorded command for any
            // resize taken while a full-screen app was up. The primary branch below has always
            // passed and restored both; this one is the sibling that did not.
            let mut marker_pts: Vec<(usize, usize)> = self
                .normal_markers
                .iter()
                .map(|m| (m.line, m.col))
                .collect();
            // Primary-scoped tracked points anchor primary content too, so they
            // reflow with this pane even though the alt screen is the active one
            // (#691) — the same reason the markers above do.
            let tracked_off = marker_pts.len();
            marker_pts.extend(self.normal_tracked.iter().map(|p| (p.line, p.col)));
            let primary = self.alt_grid.take_lines();
            let r = reflow_pane(
                primary,
                scrollback,
                self.saved_cursor.point(),
                &marker_pts,
                dims,
            );
            self.alt_grid.set_screen(r.screen, cols, rows);
            self.scrollback = r.scrollback;
            self.saved_cursor.set_point(r.cursor, rows, cols);
            for (i, m) in self.normal_markers.iter_mut().enumerate() {
                m.line = r.extras[i].0.saturating_sub(r.evicted);
                m.col = r.extras[i].1;
            }
            // Released rather than clamped when the reflow evicted its line — see
            // the primary-active branch for why the two loops differ (#691).
            let mut ti = 0;
            let evicted = r.evicted;
            let extras = &r.extras;
            self.normal_tracked.retain_mut(|p| {
                let (line, col) = extras[tracked_off + ti];
                ti += 1;
                match line.checked_sub(evicted) {
                    Some(line) => {
                        p.line = line;
                        p.col = col;
                        true
                    }
                    None => false,
                }
            });
            // The alt half lives in a different frame from the primary one above, and adding the
            // two was the defect: `extras` count from the top of the alt pane's own history, and
            // the alt screen **has** no history — every row the shrink pushed off the top is gone,
            // not archived. Passing the primary's scrollback limit made `reflow_pane` keep them,
            // so a rows-only resize (no reflow at all) reported a marker four lines past the end of
            // the buffer. The limit is `0` here because that is what an alt screen's history is.
            //
            // A marker whose row went with it is **disposed**, matching what the alt screen already
            // does when a row leaves by scrolling (`markers_rotate_region` fires `MarkerDisposed`
            // for the marker on the departing edge). Silently relocating it to row 0 would put a
            // decoration on content it was never attached to.
            let new_base = self.scrollback.len();
            let mut alt_disposed = Vec::new();
            let mut i = 0;
            self.alt_markers.retain_mut(|m| {
                let (line, col) = r_alt.extras[i];
                i += 1;
                match line.checked_sub(r_alt.evicted) {
                    Some(row) if row < rows => {
                        m.line = new_base + row;
                        // The column rides along for the same reason as the primary half, but
                        // **unpinned**: `add_marker` always passes column 0, and I could not get an
                        // OSC-133 mark (the only column-bearing kind) to appear in `alt_markers` at
                        // all. That is a gap in my knowledge, not evidence the column is
                        // structurally zero — `push_marker` takes a column and `markers_mut` routes
                        // by active buffer, so the field is reachable in principle. Carrying it
                        // keeps the two halves stating one invariant; if the alt path really is
                        // marker-column-free, this line is a no-op.
                        m.col = col;
                        true
                    }
                    _ => {
                        alt_disposed.push(m.id);
                        false
                    }
                }
            });
            for id in alt_disposed {
                self.events.push(TermEvent::MarkerDisposed(id));
            }
            // The alt half's tracked points, on the alt marker's rule: a row the
            // shrink pushed off an unarchived screen is gone, so the point is
            // released rather than relocated (#691).
            //
            // The `row < rows` half of that guard is **unproven, deliberately kept**.
            // A mutation dropping it stays green, and a sweep of 324 alt resizes
            // (rows 1..6 x cols {4,10,30}, both directions, a point on every alt row
            // at columns 0 / 1 / cols-1 / cols plus one past the pane) never reached
            // it — the alt fit runs with `reflow: false`, so a surviving row always
            // maps below the new row count. That is a measured *validity condition*,
            // not a proof of unreachability, and the marker loop above carries the
            // same bound: parity is the reason it stays.
            let mut ai = 0;
            let alt_extras = &r_alt.extras;
            let alt_evicted = r_alt.evicted;
            self.alt_tracked.retain_mut(|p| {
                let (line, col) = alt_extras[alt_tracked_off + ai];
                ai += 1;
                match line.checked_sub(alt_evicted) {
                    Some(row) if row < rows => {
                        p.line = new_base + row;
                        p.col = col;
                        true
                    }
                    _ => false,
                }
            });
        } else {
            // Active = primary (cursor, scrollback); inactive = alt. The selection
            // anchors (absolute) reflow alongside the cursor so they keep their
            // content across a column change.
            let sel_pts: Vec<(usize, usize)> = self
                .selection
                .as_ref()
                .map(|s| {
                    vec![
                        (s.anchor.point.line, s.anchor.point.col),
                        (s.focus.point.line, s.focus.point.col),
                    ]
                })
                .unwrap_or_default();
            // Markers reflow on the same pane by (line, col) — the column matters
            // for OSC-133 command marks, whose B/C columns bound the extracted
            // command text (#166). They ride after the selection points so each
            // reads its own reflowed slot back from `extras` (#118).
            let mut pts = sel_pts.clone();
            pts.extend(self.normal_markers.iter().map(|m| (m.line, m.col)));
            // Tracked points ride after the markers, reading their own slots back
            // by the same offset idiom (#691).
            let tracked_off = pts.len();
            pts.extend(self.normal_tracked.iter().map(|p| (p.line, p.col)));

            let primary = self.grid.take_lines();
            let r = reflow_pane(primary, scrollback, self.cursor.point(), &pts, dims);
            self.grid.set_screen(r.screen, cols, rows);
            self.scrollback = r.scrollback;
            self.cursor.set_point(r.cursor, rows, cols);
            if let Some(sel) = &mut self.selection {
                // A selection endpoint is **UI** state, so its reading of `col == cols` (#562) is
                // neither the cursor's nor a mark's: it is clamped into the grid. UI state may not
                // move the application's content to make room for itself — the criterion that
                // decided this, and the one ghostty encodes by clamping every non-cursor pin before
                // it can widen a row (`terminal/PageList.zig:1576-1585` @ `e6e26e1`) while leaving
                // the cursor pin unclamped (`:1602-1606`).
                sel.anchor.point = BufferPoint {
                    line: r.extras[0].0.saturating_sub(r.evicted),
                    col: r.extras[0].1.min(cols - 1),
                };
                sel.focus.point = BufferPoint {
                    line: r.extras[1].0.saturating_sub(r.evicted),
                    col: r.extras[1].1.min(cols - 1),
                };
            }
            let marker_off = sel_pts.len();
            for (i, m) in self.normal_markers.iter_mut().enumerate() {
                m.line = r.extras[marker_off + i].0.saturating_sub(r.evicted);
                m.col = r.extras[marker_off + i].1;
            }
            // A point whose reflowed line fell inside the evicted prefix has left
            // the buffer, so it is released rather than clamped to line 0 (#691) —
            // deliberately unlike the marker loop above, which saturates. A marker
            // that lands on the wrong line still paints something the consumer can
            // see and correct; a tracked point is *asked* for a position, and
            // answering with content the caller never anchored to is the exact
            // failure this whole module exists to remove.
            let mut i = 0;
            let evicted = r.evicted;
            let extras = &r.extras;
            self.normal_tracked.retain_mut(|p| {
                let (line, col) = extras[tracked_off + i];
                i += 1;
                match line.checked_sub(evicted) {
                    Some(line) => {
                        p.line = line;
                        p.col = col;
                        true
                    }
                    None => false,
                }
            });

            let alt = self.alt_grid.take_lines();
            let r = reflow_pane(
                alt,
                VecDeque::new(),
                (0, 0),
                &[],
                ReflowDims {
                    limit: 0,
                    reflow: false,
                    ..dims
                },
            );
            self.alt_grid.set_screen(r.screen, cols, rows);
        }

        // Carry the deferred wrap across the resize — it is *cursor* state, and it used to be
        // reset here alongside the scroll margins. Losing it meant the next byte overwrote the
        // last glyph instead of wrapping past it, on a column resize *and* on a rows-only one
        // where no reflow runs at all.
        //
        // This comment also named the tab stops beside the margins, as state that "does
        // legitimately reset". That was wrong, and #849 measured it: the table is indexed by
        // *columns* and written by the *application*, so rebuilding it on a rows-only resize
        // destroyed it on an axis it does not name. The margins still reset; the table does not,
        // and the extension below is why.
        //
        // The flag means "the cursor is logically one past the column it sits on". Where the
        // reflow leaves it somewhere other than the last column that logical position **is**
        // representable, so the flag is cleared and the cursor takes it instead — ghostty's rule,
        // stated in its own words for the saved cursor: *"If we had pending wrap set and we're no
        // longer at the end of the line, we unset the pending wrap and move the cursor to reflect
        // the correct next position"* (`terminal/Screen.zig:2092-2098` @ `e6e26e1`). alacritty
        // reaches the same place from the other side, lifting the cursor outside the grid before
        // reflowing and clamping it back afterwards (`grid/resize.rs:113-116`, `:248-251`,
        // `:173-177` @ `852e971`); xterm.js needs no rule because `x === cols` is representable.
        //
        // `col + 1` cannot overflow the row: the branch requires `col != cols - 1`, and `col` is
        // already clamped below `cols` by `Cursor::set_point`.
        if self.cursor.pending_wrap && self.cursor.col != cols - 1 {
            self.cursor.pending_wrap = false;
            self.cursor.col += 1;
        }
        // The scroll region is a *range over the current screen*, so a geometry change discards
        // it: at a new row count the range names rows that are not the ones it was set for. Every
        // reference does the same, and the spec's own width change says so in an enumeration —
        // xterm's DECCOLM handler calls `resetMargins` under a `DEC 070, pp 5-71 to 5-72`
        // citation (`charproc.c:7446`, `:7463` @ `6380a3e`).
        //
        // What is **not** a geometry change is a resize to the size the terminal already has, and
        // until this gate the two were the same call. `resize` has no early return, so a consumer
        // re-asserting its size destroyed a region only the *application* could restore — and the
        // application is never told, so nothing restores it. Every reference is guarded against
        // that by an early return this function does not have (`alacritty_terminal/src/term/
        // mod.rs:662` @ `852e971`, `src/terminal/Terminal.zig:3753` @ `e6e26e1`,
        // `src/browser/CoreBrowserTerminal.ts:1055` @ `699f553`); the gate is the narrow form of
        // the same guard, and it is the predicate this function already uses twice above.
        if cols != old_cols || rows != old_rows {
            self.scroll_top = 0;
            self.scroll_bottom = rows - 1;
        }
        // Extend, never rebuild and never trim (#849). A resize changes the *grid*; the
        // tab-stop table is state the application wrote through the stream. The line this
        // replaces rebuilt it from defaults on every call, so a window dragged one row
        // taller — or a consumer merely re-asserting its size, which reaches here because
        // this function has no early return for unchanged geometry — silently replaced an
        // application's stops with multiples of eight, on an axis the table is not even
        // indexed by.
        //
        // New columns take the default ladder at their **absolute** index, which is why the
        // closure carries `index` instead of counting from zero: filling them with `false`
        // keeps the length right and loses every default stop past the old width.
        //
        // Nothing is trimmed, so `tabs.len()` is the widest this terminal has ever been and
        // the invariant the two walks need is `len() >= cols` rather than equality — every
        // index site is bounded by `cols` or by `cursor.col`. A stop pushed outside the grid
        // by a narrowing is unreachable while narrow and returns when the grid widens again.
        // The corpus splits 2-2 on that half: xterm keeps it structurally (MAX_TABS is 1024,
        // independent of the screen, `ptyx.h:3611` @ `6380a3e`) and xterm.js keeps it in a
        // sparse map, while alacritty truncates through `Vec::resize_with`
        // (`alacritty_terminal/src/term/mod.rs:2341` @ `852e971`) and ghostty rebuilds the
        // table outright when the column count moves (`src/terminal/Terminal.zig:3759` @
        // `e6e26e1`). No tie-breaker row covers the axis, so the call is the maintainer's,
        // recorded on #849.
        //
        // Only the *rebuild* is wrong here, not every reset: RIS still restores the default
        // ladder, because `full_reset` replaces the whole struct and takes the table from
        // the constructor — the right answer for state the application wrote and `ESC c`
        // resets.
        if cols > self.tabs.len() {
            let mut index = self.tabs.len();
            self.tabs.resize_with(cols, || {
                let is_stop = is_default_tab_stop(index);
                index += 1;
                is_stop
            });
        }
        self.display_offset = self.display_offset.min(self.scrollback.len());

        // Damage tracking is sized to the screen; a resize repaints everything,
        // so drop any pending scroll op (it points at the old rows).
        self.line_damage = vec![LineBounds::undamaged(cols); rows];
        self.scroll = None;
        self.mark_fully_damaged();
    }

    pub fn grid(&self) -> &Grid {
        &self.grid
    }

    pub fn cursor(&self) -> &Cursor {
        &self.cursor
    }

    /// Whether bracketed-paste mode (DEC ?2004) is enabled. The input encoder
    /// reads this to decide whether to wrap pasted text in markers.
    pub fn bracketed_paste(&self) -> bool {
        self.bracketed_paste
    }

    // ---- input encoding (#11) ------------------------------------------------

    /// Encode a key event to bytes using every mode that decides one: the active
    /// cursor-key mode (DECCKM), application keypad, the kitty keyboard-protocol
    /// flags and `modifyOtherKeys` level 2. `encode_key` consults all four,
    /// and asks kitty first.
    pub fn encode_key(&self, ev: KeyEvent) -> Option<Vec<u8>> {
        encode_key(
            &ev,
            self.app_cursor_keys,
            self.application_keypad,
            self.kitty_flags,
            self.modify_other_keys_2,
        )
    }

    /// Encode a mouse event using the active tracking mode + encoding. `None`
    /// when reporting is off or the event is filtered by the mode.
    pub fn encode_mouse(&self, ev: MouseEvent) -> Option<Vec<u8>> {
        encode_mouse(&ev, self.mouse_protocol, self.mouse_encoding)
    }

    /// Encode pasted text, wrapping it in bracketed-paste markers when ?2004 is
    /// on.
    pub fn encode_paste(&self, text: &str) -> Vec<u8> {
        encode_paste(text, self.bracketed_paste)
    }

    /// Encode a focus change (`CSI I`/`CSI O`), or `None` when focus reporting
    /// (?1004) is off.
    pub fn encode_focus(&self, focused: bool) -> Option<Vec<u8>> {
        encode_focus(focused, self.focus_events)
    }

    /// Take the consumer events queued since the last drain, emptying the queue.
    pub fn drain_events(&mut self) -> Vec<TermEvent> {
        std::mem::take(&mut self.events)
    }

    /// Take the reply bytes queued since the last drain (DA/DSR/DECRQM answers),
    /// emptying the buffer. The consumer writes them back to the PTY.
    pub fn drain_replies(&mut self) -> Vec<u8> {
        std::mem::take(&mut self.replies)
    }

    /// Device Status Report (CSI Ps n): 6 = cursor position, 5 = operating
    /// status. Queues the reply for `drain_replies` (#27).
    fn device_status_report(&mut self, param: u16) {
        match param {
            6 => {
                // CSI row;col R, 1-based — region-relative under origin mode
                // (the coordinate system the app is addressing in).
                let row = if self.origin_mode {
                    self.cursor.row.saturating_sub(self.scroll_top)
                } else {
                    self.cursor.row
                } + 1;
                let col = self.cursor.col + 1;
                self.replies
                    .extend_from_slice(format!("\x1b[{row};{col}R").as_bytes());
            }
            5 => self.replies.extend_from_slice(b"\x1b[0n"), // status: OK
            _ => {}
        }
    }

    /// Kitty keyboard-protocol negotiation (#23). `lead` is the leading CSI
    /// intermediate: `?` query, `>` push, `=` set, `<` pop.
    fn kitty_dispatch(&mut self, lead: u8, params: &Params) {
        match lead {
            // Query → report the current flags as `CSI ? flags u` (#27 channel).
            b'?' => self
                .replies
                .extend_from_slice(format!("\x1b[?{}u", self.kitty_flags).as_bytes()),
            // Push: save the current flags, then set the new ones (default 0).
            b'>' => {
                const KITTY_STACK_CAP: usize = 16;
                if self.kitty_stack.len() >= KITTY_STACK_CAP {
                    self.kitty_stack.remove(0); // drop the oldest on overflow
                }
                self.kitty_stack.push(self.kitty_flags);
                self.kitty_flags = param_or(params, 0, 0) as u8;
            }
            // Pop `n` (default 1): restore from the stack, 0 once empty.
            b'<' => {
                for _ in 0..param_or(params, 0, 1) {
                    self.kitty_flags = self.kitty_stack.pop().unwrap_or(0);
                }
            }
            // Set in place (no push): mode 1 replace, 2 or-in, 3 and-not.
            b'=' => {
                let flags = param_or(params, 0, 0) as u8;
                self.kitty_flags = match param_or(params, 1, 1) {
                    1 => flags,
                    2 => self.kitty_flags | flags,
                    3 => self.kitty_flags & !flags,
                    _ => self.kitty_flags,
                };
            }
            _ => {}
        }
    }

    /// DECRQM (CSI ? Ps $ p): report whether DEC private mode `Ps` is set —
    /// `CSI ? Ps ; val $ y` with val 1=set, 2=reset, 0=not recognized (#27).
    fn decrqm(&mut self, mode: u16) {
        let state = match mode {
            1 => Some(self.app_cursor_keys),
            // DECANM (#84): set = ANSI mode (the normal state), reset = VT52.
            2 => Some(!self.vt52_mode),
            6 => Some(self.origin_mode),
            // DECCOLM: derived from the actual width, never a tracked flag — a
            // flag would lie if the consumer ignored the resize request (#82).
            3 => Some(self.grid.cols() == 132),
            7 => Some(self.autowrap),
            45 => Some(self.reverse_wraparound),
            9 => Some(self.mouse_protocol == MouseProtocol::X10),
            66 => Some(self.application_keypad),
            12 => Some(self.cursor.blink),
            25 => Some(self.cursor.visible),
            // Mouse tracking is a single-state enum (the levels are mutually
            // exclusive — an app enables one), so querying ?1000 while ?1002 is
            // active reports "reset". Faithful to that model.
            1000 => Some(self.mouse_protocol == MouseProtocol::Normal),
            1002 => Some(self.mouse_protocol == MouseProtocol::ButtonEvent),
            1003 => Some(self.mouse_protocol == MouseProtocol::AnyEvent),
            1004 => Some(self.focus_events),
            1006 => Some(self.mouse_encoding == MouseEncoding::Sgr),
            1015 => Some(self.mouse_encoding == MouseEncoding::Urxvt),
            1005 => Some(self.mouse_encoding == MouseEncoding::Utf8),
            1016 => Some(self.mouse_encoding == MouseEncoding::SgrPixels),
            47 | 1047 | 1049 => Some(self.on_alt),
            2004 => Some(self.bracketed_paste),
            2026 => Some(self.synchronized_output),
            2027 => Some(self.grapheme_clustering),
            2031 => Some(self.color_scheme_updates),
            9001 => Some(self.win32_input_mode),
            _ => None,
        };
        let val = match state {
            Some(true) => 1,
            Some(false) => 2,
            None => 0,
        };
        self.replies
            .extend_from_slice(format!("\x1b[?{mode};{val}$y").as_bytes());
    }

    // ---- cursor / scroll primitives ------------------------------------------

    /// Move down one line. At the bottom margin, scroll the region instead;
    /// below the region, just descend (no scroll). Column is unchanged (raw LF;
    /// CR is what returns to column 0).
    /// An ordinary line feed — `LF`/`VT`/`FF`, `IND` and `NEL`. None of them serves a wrap.
    ///
    /// It clears the deferred wrap, as every acting positioner does — see
    /// [`Cursor::pending_wrap`]. The clear sits here rather than in
    /// [`Term::linefeed_inner`] because the wrap machinery drives that same
    /// primitive and *consumes* the flag rather than clearing it; folding the two
    /// together would put one property's arm and its clear in one statement.
    /// Leaving it armed made the print after an `LF` wrap a second time, landing a
    /// row further down and leaving the row the feed had reached blank (#848).
    fn linefeed(&mut self) {
        self.linefeed_inner(false);
        self.cursor.pending_wrap = false;
    }

    /// A line feed, carrying the one fact the shift itself cannot see: whether the auto-wrap asked
    /// for it.
    ///
    /// `serves_wrap` is the **bottom** seam's exemption in `shift_region`, the mirror of
    /// `evicts_to_scrollback` for the top one. When `wrapline` drives this, the blank that lands at
    /// the region's bottom *is* where the wrapped text is about to go — so the row that #540 would
    /// call "the one that lost its continuation to the blank" is in fact the row whose continuation
    /// that blank **is**.
    ///
    /// xterm.js threads the identical fact through the identical seam, in the opposite direction:
    /// `BufferService.scroll(eraseAttr, isWrapped)` stamps the *destination* row
    /// (`common/services/BufferService.ts:68`/`:77` @ `699f553`), and exactly one of its four
    /// non-test callers passes `true` — the auto-wrap branch of `_print` (`InputHandler.ts:588`),
    /// not `lineFeed`, `index` or the ED-2 loop.
    fn linefeed_inner(&mut self, serves_wrap: bool) {
        // New-line mode (LNM ?20): a line feed also returns to column 0 (#71).
        if self.newline_mode {
            self.carriage_return();
        }
        if self.cursor.row == self.scroll_bottom {
            // A top-anchored primary-screen scroll pushes the evicted top line
            // into scrollback history.
            if self.scroll_top == 0 && !self.on_alt {
                // Scrollback accrues whenever the scroll is top-anchored on the
                // primary screen (`scroll_top == 0`) — but the O(1) ring handshake
                // only applies to a *full-screen* scroll (`scroll_bottom` at the
                // last row). A top-anchored *sub-region* (`[0..k]`, k < rows-1)
                // still accrues, yet must scroll only its region, so it keeps the
                // copy + region scroll. These are distinct predicates (ADR-0009).
                let evicted = if self.scroll_bottom == self.grid.rows() - 1 {
                    // Full-screen hot path: move the evicted top row out, install
                    // a recycled blank as the new bottom (zero-alloc steady state).
                    let blank = self
                        .recycled_row
                        .take()
                        .unwrap_or_else(|| Row::from_cells(Vec::with_capacity(self.grid.cols())));
                    let evicted = self.grid.scroll_up_recycle(blank);
                    // The one row-shifting path that does not route through `shift_region` (it
                    // needs the primitive that *returns* the evicted row), so it records its own
                    // scroll op — and owes no seam clear, which is now an argument rather than a
                    // coincidence: the top seam is exempt because this evicts into scrollback
                    // (adjacency is preserved one row back), and the bottom seam is exempt because
                    // this branch only runs at `scroll_bottom == rows - 1`, where a wrap on the
                    // last row is the state the scroll exists to serve.
                    self.record_scroll(self.scroll_top, self.scroll_bottom, 1);
                    evicted
                } else {
                    // Top-anchored sub-region: copy row 0, then region-scroll
                    // `[0..=scroll_bottom]` (rows below stay fixed).
                    //
                    // #449: the fixed rows keep their GRID position while
                    // scrollback grows, so their content's concatenated absolute
                    // index shifts +1 — re-anchor the content-tracking anchors
                    // (selection, markers; alacritty's swap-back of the fixed
                    // bottom lines is the screen-relative equivalent of this)
                    // and invalidate the query-derived highlights
                    // (drop-not-re-anchor policy, #108). In-region and
                    // scrollback content keeps stable indices — untouched.
                    let below = self.scrollback.len() + self.scroll_bottom + 1;
                    self.selection_shift_below_margin(below);
                    self.markers_shift_below_margin(below);
                    self.tracked_shift_below_margin(below);
                    self.invalidate_search_highlights();
                    let evicted = self.grid.row_owned(0);
                    self.shift_region(
                        self.scroll_top,
                        self.scroll_bottom,
                        false,
                        true,
                        serves_wrap,
                    );
                    evicted
                };
                self.scrollback.push_back(evicted);
                // Follow-bottom = stay: if the user is scrolled up, bump the
                // offset so the same lines stay in view instead of being yanked
                // to the bottom.
                if self.display_offset > 0 {
                    self.display_offset = (self.display_offset + 1).min(self.scrollback.len());
                }
                // Cap: evict the oldest line past the limit. The view is anchored
                // to history, so dropping the front shifts the offset down too
                // (xterm.js trims ybase and ydisp together) — also keeps the
                // offset within `[0, len]`. The evicted row is parked for reuse.
                if self.scrollback.len() > self.scrollback_limit {
                    self.recycled_row = self.scrollback.pop_front();
                    self.lines_left_the_front(1);
                    if self.display_offset > 0 {
                        // Scrolled up: evicting the oldest line advanced the
                        // viewport, so it must be repainted (the "frozen while
                        // scrolled" rule does not apply when the view itself moved).
                        self.display_offset -= 1;
                        self.mark_fully_damaged();
                    }
                }
            } else {
                // Region (top margin > 0) or alt-screen scroll: the evicted line
                // does NOT enter scrollback, so content moves *within* the screen
                // and absolute indices in the region shift. Rotate the selection
                // up so it follows; an endpoint on the dropped line clears it.
                let base = self.scrollback.len();
                self.selection_rotate_region(
                    base + self.scroll_top,
                    base + self.scroll_bottom,
                    true,
                );
                // Rotate the active buffer's markers with the content (#187):
                // per-buffer storage (#186) scopes them, so an alt scroll rotates
                // *alt* marks and leaves the frozen primary list untouched — no
                // guard needed. `markers_rotate_region` routes via `markers_mut`.
                self.markers_rotate_region(base + self.scroll_top, base + self.scroll_bottom, true);
                self.tracked_rotate_region(base + self.scroll_top, base + self.scroll_bottom, true);
                self.invalidate_search_highlights();
                self.shift_region(
                    self.scroll_top,
                    self.scroll_bottom,
                    false,
                    false,
                    serves_wrap,
                );
            }
        } else if self.cursor.row + 1 < self.grid.rows() {
            self.cursor.row += 1;
        }
    }

    /// DECSTBM (CSI r): set the top/bottom scroll margins (1-based inclusive).
    /// An invalid region (top ≥ bottom) is ignored.
    fn set_scroll_region(&mut self, top: usize, bottom: usize) {
        let bottom = bottom.min(self.grid.rows());
        if top >= bottom {
            return;
        }
        self.scroll_top = top - 1;
        self.scroll_bottom = bottom - 1;
        self.goto(0, 0); // DECSTBM homes the cursor (absolute)
    }

    // ---- alt screen (DEC 1049) -----------------------------------------------

    /// Enter the alternate screen: save the cursor, swap in the other grid, and
    /// clear it.
    /// Save the cursor into the alt-screen slot — `?1048` set, and the first
    /// half of `?1049` enter (#72).
    fn save_alt_cursor(&mut self) {
        self.saved_cursor = self.cursor;
    }

    /// Restore the cursor from the alt-screen slot — `?1048` reset, and the
    /// second half of `?1049` leave. DECTCEM visibility is a standalone mode, not
    /// part of the save, so preserve it across the restore (#38/#72).
    fn restore_alt_cursor(&mut self) {
        let visible = self.cursor.visible;
        self.cursor = self.saved_cursor;
        self.cursor.visible = visible;
        self.settle_restored_wrap();
    }

    /// Switch to the (cleared) alternate buffer without touching the cursor —
    /// `?47`/`?1047` set, and the second half of `?1049` enter (#72).
    fn switch_to_alt(&mut self) {
        if self.on_alt {
            return;
        }
        // The pulled index reports the ACTIVE buffer, so a swap changes what the
        // consumer's held answer even describes — with no line having moved (#490).
        // Gated on a marker existing on either side, since an empty index is already
        // correct for both buffers.
        if !self.normal_markers.is_empty() || !self.alt_markers.is_empty() {
            self.bump_marker_epoch();
        }
        std::mem::swap(&mut self.grid, &mut self.alt_grid);
        self.grid.clear();
        self.swap_kitty_keyboard();
        self.on_alt = true;
        self.display_offset = 0; // the alt screen has no scrollback to view
        self.selection = None; // a selection cannot survive a screen swap
        self.invalidate_search_highlights(); // matches index the primary buffer
        self.mark_fully_damaged();
    }

    /// Switch back to the primary buffer without touching the cursor —
    /// `?47`/`?1047` reset, and the first half of `?1049` leave (#72).
    fn switch_to_primary(&mut self) {
        if !self.on_alt {
            return;
        }
        // Dispose the alt buffer's markers on leave — xterm `activateNormalBuffer`
        // → `clearAllMarkers` (#177 S0). Empty while the alt guards stand, so this
        // fires nothing today; it's the seam the alt-marker slices (#187) build on.
        for m in self.alt_markers.drain(..) {
            self.events.push(TermEvent::MarkerDisposed(m.id));
        }
        // Same fate for alt-scoped tracked points, and for the same reason: the alt
        // buffer is not archived, so leaving it destroys what they named (#691).
        // No announcement — `tracked_point` answers `None` on the next ask.
        // The pulled index reports the ACTIVE buffer, so a swap changes what the
        // consumer's held answer even describes — with no line having moved (#490).
        // Only `normal_markers` is asked: the drain above just emptied `alt_markers`, so
        // an `|| !alt_markers.is_empty()` disjunct would be dead code carrying a comment
        // that claims it reads "either side". What was alt-scoped left through
        // `MarkerDisposed`; what can still be stale is the primary population.
        if !self.normal_markers.is_empty() {
            self.bump_marker_epoch();
        }
        self.alt_tracked.clear();
        std::mem::swap(&mut self.grid, &mut self.alt_grid);
        self.swap_kitty_keyboard();
        self.on_alt = false;
        self.display_offset = 0; // return to the primary at its bottom
        self.selection = None; // a selection cannot survive a screen swap
        self.invalidate_search_highlights(); // matches index the swapped-out buffer
        self.mark_fully_damaged();
    }

    /// Exchange the active screen's kitty keyboard flags and stack with the other screen's.
    fn swap_kitty_keyboard(&mut self) {
        std::mem::swap(&mut self.kitty_flags, &mut self.kitty_flags_inactive);
        std::mem::swap(&mut self.kitty_stack, &mut self.kitty_stack_inactive);
    }

    fn enter_alt_screen(&mut self) {
        if self.on_alt {
            return;
        }
        self.save_alt_cursor();
        self.switch_to_alt();
    }

    /// Leave the alternate screen: swap the primary grid back in and restore the
    /// saved cursor.
    fn leave_alt_screen(&mut self) {
        if !self.on_alt {
            return;
        }
        self.switch_to_primary();
        self.restore_alt_cursor();
    }

    /// RI (ESC M): move up one line. At the top margin, scroll the region down
    /// instead.
    fn reverse_index(&mut self) {
        if self.cursor.row == self.scroll_top {
            // RI never enters scrollback; the region scrolls down within the
            // screen, so absolute indices in it shift down. Rotate the selection.
            let base = self.scrollback.len();
            self.selection_rotate_region(base + self.scroll_top, base + self.scroll_bottom, false);
            // Rotate the active buffer's markers (#187) — alt-scoped on the alt
            // screen, so no guard (see `linefeed`).
            self.markers_rotate_region(base + self.scroll_top, base + self.scroll_bottom, false);
            self.tracked_rotate_region(base + self.scroll_top, base + self.scroll_bottom, false);
            self.invalidate_search_highlights();
            self.shift_region(self.scroll_top, self.scroll_bottom, true, false, false);
        } else if self.cursor.row > 0 {
            self.cursor.row -= 1;
        }
        // Cleared in both branches, because both are the verb acting: one moves the
        // cursor, the other scrolls the content under it. Branching on which would
        // reintroduce the per-verb special-casing [`Cursor::pending_wrap`] exists to
        // remove, and xterm and ghostty both clear unconditionally here (`cursor.c:284`
        // via `CursorUp`; `Terminal.zig:2174` in `index`, under a comment saying so).
        self.cursor.pending_wrap = false;
    }

    // ---- cursor save/restore (DECSC / DECRC) ---------------------------------

    /// DECSC (ESC 7): save the cursor position, pen, pending-wrap, and origin
    /// mode. Visibility is not saved (DECTCEM is separate).
    fn save_cursor(&mut self) {
        self.decsc = SavedCursor {
            row: self.cursor.row,
            col: self.cursor.col,
            pen: self.cursor.pen,
            pending_wrap: self.cursor.pending_wrap,
            origin_mode: self.origin_mode,
            charsets: self.charsets,
            gl: self.gl,
        };
    }

    /// DECRC (ESC 8): restore what DECSC saved. Origin mode is restored (per
    /// ADR-0004); visibility is left as-is. The position is clamped to the
    /// current screen in case it shrank since the save.
    fn restore_cursor(&mut self) {
        let s = self.decsc;
        self.cursor.row = s.row.min(self.grid.rows() - 1);
        self.cursor.col = s.col.min(self.grid.cols() - 1);
        self.cursor.pen = s.pen;
        self.cursor.pending_wrap = s.pending_wrap;
        self.origin_mode = s.origin_mode;
        self.charsets = s.charsets;
        self.gl = s.gl;
        self.settle_restored_wrap();
    }

    /// A restored deferred wrap is only meaningful at the last column; anywhere
    /// else the logical position is representable and the cursor takes it.
    ///
    /// The same translation `Term::resize` applies to the **live** cursor, applied
    /// to the two saved slots — which is where ghostty puts it, on the saved cursor
    /// it has just reflowed (`terminal/Screen.zig:2094`: *"If we had pending wrap
    /// set and we're no longer at the end of the line, we unset the pending wrap and
    /// move the cursor to reflect the correct next position"*).
    ///
    /// justerm's slots are not reflowed, so the repair belongs at the restore rather
    /// than at the resize: `decsc` is untouched by `Term::resize` and clamped here,
    /// and the alt slot is copied whole. Measured before the fix: 4 columns, `abcd`,
    /// `DECSC`, `resize(8, 3)`, `DECRC` left the flag armed at column 3 of an
    /// 8-column grid — five columns from the edge — and the next print wrapped
    /// instead of landing at column 4 (#848).
    fn settle_restored_wrap(&mut self) {
        if self.cursor.pending_wrap && self.cursor.col + 1 < self.grid.cols() {
            self.cursor.pending_wrap = false;
            self.cursor.col += 1;
        }
    }

    /// Set the window title and tell the consumer, in one place.
    ///
    /// Both writers come through here — the OSC 0/2 path and the XTWINOPS pop
    /// path — so the retained string and the event a consumer sees cannot
    /// disagree. A pop deliberately fires the **same** `TermEvent::Title` an
    /// ordinary title change does: both implementations that carry the stack do
    /// exactly this (xterm.js's `setTitle` fires `_onTitleChange`, alacritty's
    /// `pop_title` routes through `set_title`), and a second event would ask
    /// every consumer to learn a distinction it has no use for. The consequence
    /// worth stating: `Title` now means *"the title is this"*, not *"the
    /// application just set this"*.
    fn set_window_title(&mut self, title: String) {
        self.window_title.clone_from(&title);
        self.events.push(TermEvent::Title(title));
    }

    /// XTWINOPS (`CSI Ps ; Ps ; Ps t`) — window manipulation, of which this
    /// engine implements exactly two operations (#823).
    ///
    /// It owns no window, so most of the family is meaningless here: 14/16 ask
    /// about pixels the engine has no concept of, and the resize/move/iconify
    /// operations are requests about a window the consumer owns. 22 (push
    /// title) and 23 (pop title) are different — they are pure VT state, and
    /// they were the single most-emitted unimplemented sequence in the capture
    /// sweep that produced #823. **This does not make `CSI t` a handled final**;
    /// every other first parameter still falls through and is ignored.
    ///
    /// The second parameter selects the axis: absent or `0` both, `1` the icon
    /// name, `2` the window title, anything else no axis at all. It is honoured
    /// rather than assumed away because real applications use it — `vim` emits
    /// a fully nested `22;0;0t · 22;2t · 22;1t … 23;2t · 23;1t · 23;0;0t`,
    /// which a single shared stack gets wrong.
    ///
    /// **The optional third parameter is deliberately ignored**, and that is a
    /// divergence from the spec rather than a simplification of it:
    /// `ctlseqs.txt:1698` gives a value in 1..10 *direct access to the stack*,
    /// storing or retrieving without pushing or popping, and xterm implements
    /// it (`charproc.c:9272`). Measured reach of that form is zero on every
    /// axis checked — no occurrence across seven programs recorded under real
    /// ptys, no file under `/usr/bin` or `/usr/lib64` containing it, no
    /// terminfo capability that emits `CSI 22/23 t` at all under any candidate
    /// `TERM`, and no other implementation honouring it (xterm.js ignores it,
    /// alacritty's dispatch never reads past the first parameter, ghostty
    /// carries the index and then drops the command). It entered xterm in patch
    /// #385 (2023-10-01) for symmetry with XTPUSHCOLORS, not because an
    /// application asked. So `CSI 22;2;3t` is an ordinary push here.
    fn window_ops(&mut self, params: &Params) {
        // `param_or` folds an explicit 0 to the default, which is what both
        // axis and operation want: absent and `0` mean the same thing in each.
        let axis = param_or(params, 1, 0);
        let (window, icon) = (axis == 0 || axis == 2, axis == 0 || axis == 1);
        match param_or(params, 0, 0) {
            22 => {
                if window {
                    let title = self.window_title.clone();
                    push_title(&mut self.window_title_stack, title);
                }
                if icon {
                    let name = self.icon_name.clone();
                    push_title(&mut self.icon_name_stack, name);
                }
            }
            23 => {
                if window && let Some(title) = self.window_title_stack.pop() {
                    self.set_window_title(title);
                }
                // Restoring the icon name has no observable output: the engine
                // has no icon-name event. The stack is still popped so the two
                // axes stay aligned across mixed push/pop sequences.
                if icon && let Some(name) = self.icon_name_stack.pop() {
                    self.icon_name = name;
                }
            }
            _ => {}
        }
    }

    /// RIS (ESC c) — full reset to the power-on state (#53). Reconstruct every
    /// screen/mode field to its construction default (preserving only the
    /// dimensions and the scrollback cap), but keep the consumer-bound output
    /// queues (`replies`/`events`) that accrued earlier in this `feed`, and
    /// signal a full repaint. The vte parser lives outside `Term`, so replacing
    /// `self` does not disturb in-progress parsing. Mirrors xterm.js fullReset.
    ///
    /// The XTWINOPS title stacks and the retained title/icon strings (#823) are
    /// **not** on the copy-back list and must not be: they are terminal state the
    /// application wrote, so *justerm's own* RIS invariant drops them, and the
    /// wholesale rebuild does that for free.
    ///
    /// Read "justerm's own" literally — this is a **minority position, 1–2**, and
    /// no spec text settles it. Only alacritty agrees (`title_stack =
    /// Vec::new()` in `reset_state`); xterm.js's `reset()` touches nothing but
    /// attribute data, and xterm's only bulk free of `saved_titles` is inside
    /// `VTDestroy`, i.e. widget teardown rather than `ESC c`. So the two
    /// references whose *model* this slice copied — two stacks, the bound, the
    /// drop-oldest rule — are the two that keep the stack across a reset. The
    /// grounds are the invariant note next door, which already records that no
    /// reference can be cited here because none of them holds the embedder's
    /// configuration in the object its reset replaces.
    ///
    /// **That "1–2" is right for the stacks and wrong for the retained strings**, and
    /// the sentence above ran the two together (corrected 2026-09-08, #835). Ghostty
    /// drops the title on a reset exactly as this does — `self.title` and `self.pwd`
    /// are both `clearRetainingCapacity()`d in `fullReset` (`Terminal.zig:4468-4469`)
    /// — so on the **retained string** the tally is 2–2, not 1–2, and justerm is not
    /// in a minority. It cannot be counted on the *stack* half at all, because it
    /// holds no title stack in `Terminal` to have an opinion about; there the 1–2
    /// stands. The correction matters because "minority position" is a standing
    /// invitation to revisit, and half of what it was pointing at is a tie.
    ///
    /// **Dropping the title is also not announced, and that too matches both
    /// references that drop it.** A consumer keeps the exited application's window
    /// title after `ESC c` — the same shape as the palette below, and *worse* on its
    /// face, since here the engine does hold the string and does discard it, so the
    /// two sides actually diverge. It is nonetheless not a defect by any available
    /// standard: alacritty clears `title`/`title_stack` in `reset_state` with no
    /// event on its proxy, and ghostty's `StreamHandler.fullReset` sends a mouse
    /// shape, a mode-2031 report and a progress clear — and nothing about the title.
    /// 2–0 among the references that face the question. Measured on #835 rather than
    /// assumed; if it is ever revisited, the first thing to re-measure is whether
    /// dropping at all is right, since xterm and xterm.js simply keep the title.
    ///
    /// **The palette is deliberately *not* announced here, and the silence is a
    /// decision rather than an omission (#835).** An application that redefined
    /// entries with `OSC 4`, or the foreground/background/cursor with
    /// `OSC 10`/`11`/`12`, keeps them across `ESC c`: the engine is theme-agnostic
    /// and holds no palette, so the consumer's copy is the only one, and this path
    /// pushes no `ResetPaletteColor` / `ResetForeground` / `ResetBackground` /
    /// `ResetCursorColor` onto the queue above. xterm is the one reference that
    /// resets its own palette on **both** strengths (`charproc.c:14366`, in the
    /// `if_OPT_ISO_COLORS` block *above* the `if (full)` split); three things
    /// decided against following it, none of them the head-count:
    ///
    /// * **The tie-breaker does not reach it.** ADR-0004 defers to xterm where
    ///   *the spec* mandates something alacritty merely omits. `OSC 4`/`104` are
    ///   xterm's own invention and DEC never defined a palette, so no spec text
    ///   says what `RIS` does to one — a genuine ambiguity, which ADR-0004 routes
    ///   to alacritty. ("The inventor owns the semantics", which settled
    ///   `XTREVWRAP` on [`Self::step_back`], does not transfer: that was the
    ///   invented sequence's *own* meaning, and this is what a **DEC** sequence
    ///   does to state the invented one left behind.)
    /// * **terminfo says the palette reset is not part of `RIS`.**
    ///   `xterm-256color` spells its reset string `rs1=\Ec\E]104\007` and `linux`
    ///   spells it `rs1=\Ec\E]R`: both append an explicit palette reset *after*
    ///   `RIS`, which xterm's own entry would not need if `\Ec` implied one. So
    ///   `tput reset` already emits `OSC 104` — measured, not read — and the
    ///   engine already relays it. The reachable case is covered without adding
    ///   anything, which is what `ris_then_osc104_is_the_reset_string_that_ships`
    ///   pins.
    /// * **The reference that shares this shape declines.** ghostty holds the
    ///   palette *and* announces every change across a consumer boundary, and its
    ///   override mask tells it exactly which entries are dirty — so a selective
    ///   announcement would be free there, and its `fullReset` still sends none.
    ///   justerm cannot even be selective: holding no palette, it would have to
    ///   fire unconditionally on every `ESC c`.
    ///
    /// What xterm resets on both strengths is **two** things, and the engine
    /// already does one: the pen is covered by this rebuild and by
    /// [`Self::soft_reset`]. The *dynamic* colours are restored by nobody, xterm
    /// included — `ReallyReset` never touches them. Rows in
    /// `docs/agents/reference-facts.md`; reversal criterion on #835.
    fn full_reset(&mut self) {
        let replies = std::mem::take(&mut self.replies);
        let mut events = std::mem::take(&mut self.events);
        // RIS wipes the buffer, so every marker's line is gone — announce each
        // disposal so the consumer drops its decorations (and isn't confused when
        // the reset id counter reissues the same ids). The events survive the
        // reset below (#118).
        events.extend(
            self.normal_markers
                .iter()
                .chain(&self.alt_markers)
                .map(|m| TermEvent::MarkerDisposed(m.id)),
        );
        let (cols, rows) = (self.grid.cols(), self.grid.rows());
        // The word-boundary set is consumer *policy* (ADR-0017), not terminal state, so
        // RIS does not own it — an application printing `reset` must not silently revert
        // a setting the embedder chose. It rides across with `replies`/`events` because
        // this reset rebuilds `Term` wholesale; the references never face the question,
        // holding the equivalent outside the object RIS clears (#545).
        let word_separators = std::mem::take(&mut self.word_separators);
        // Tracked points die here with everything else, but their *id counter*
        // rides across (#691). They have no disposal event — a holder learns its
        // point is gone by being told `None` — so a reissued id would answer a
        // stale ask with a *different* point's position, silently. The markers
        // above take the other route and announce; the counter is what a pull-only
        // handle has instead.
        let next_tracked_id = self.next_tracked_id;
        // The marker epoch rides across too, and then moves — for the reason one
        // paragraph up, now that a marker index is *pulled* as well as announced (#490).
        // A consumer re-pulls when the epoch differs; resetting it to 0 leaves it equal
        // to the value a quiet session already holds, so the one signal it watches would
        // not fire for the mutation that invalidates everything. `evicted_total`
        // legitimately restarts — the buffer it counted is gone — and the epoch change is
        // what stops the consumer rebasing against the old basis.
        let marker_epoch = self.marker_epoch;
        // Marker ids ride across for the *same* reason as `next_tracked_id`, which this
        // slice makes true of markers: a pulled handle outlives the announcement that
        // killed it, so a reissued id lets a stale `MarkerDisposed(7)` drop the live
        // post-RIS marker 7.
        let next_marker_id = self.next_marker_id;
        *self = Term::with_scrollback(cols, rows, self.scrollback_limit);
        self.replies = replies;
        self.events = events;
        self.word_separators = word_separators;
        self.next_tracked_id = next_tracked_id;
        self.next_marker_id = next_marker_id;
        self.marker_epoch = marker_epoch;
        self.bump_marker_epoch();
        self.mark_fully_damaged();
    }

    /// DECSTR (CSI ! p) — soft reset (#53). Resets a defined subset of modes to
    /// their defaults *without* destroying screen content or scrollback, moving
    /// the active cursor, or touching the mouse/focus reporting subsystem. Per
    /// xterm.js softReset, autowrap returns to ON (the xterm default), not off.
    ///
    /// The pen returning to [`Pen::default`] is this path's half of xterm's
    /// `reset_SGR_Colors`, which runs on **both** reset strengths. The other half
    /// of that block — resetting the indexed palette — is deliberately not
    /// mirrored, here or in [`Self::full_reset`], where the grounds are written
    /// out.
    fn soft_reset(&mut self) {
        self.cursor.visible = true;
        self.cursor.pen = Pen::default();
        self.cursor.shape = None; // the application's caret shape and blink mode (#927)
        self.cursor.blink = false;
        self.scroll_top = 0;
        self.scroll_bottom = self.grid.rows() - 1;
        self.origin_mode = false;
        self.app_cursor_keys = false;
        self.bracketed_paste = false;
        self.modify_other_keys_2 = false; // xterm clears the modify resources on DECSTR too (#890)
        self.grapheme_clustering = false; // ?2027 back to the wcwidth-compat default (#295)
        self.autowrap = true; // xterm default is ON (not the VT100 "off")
        self.insert_mode = false;
        self.charsets = [Charset::Ascii; 4];
        self.gl = 0;
        self.decsc = SavedCursor::default();
    }

    fn carriage_return(&mut self) {
        self.cursor.col = 0;
        self.cursor.pending_wrap = false;
    }

    /// DECSCUSR (CSI Ps SP q): set the caret shape + blink (#89). 1/2 =
    /// blinking/steady block; 3/4 = blinking/steady underline; 5/6 =
    /// blinking/steady bar (odd = blink). 0 clears the shape to `None` — the
    /// consumer's default shape (#927) — and turns the blink mode off. An unknown
    /// param leaves the style unchanged.
    fn set_cursor_style(&mut self, param: u16) {
        let (shape, blink) = match param {
            0 => (None, false),
            1 => (Some(CursorShape::Block), true),
            2 => (Some(CursorShape::Block), false),
            3 => (Some(CursorShape::Underline), true),
            4 => (Some(CursorShape::Underline), false),
            5 => (Some(CursorShape::Bar), true),
            6 => (Some(CursorShape::Bar), false),
            _ => return,
        };
        self.cursor.shape = shape;
        self.cursor.blink = blink;
    }

    /// Backspace (BS, 0x08): one step back.
    fn backspace(&mut self) {
        self.step_back();
    }

    /// One step back, shared by `BS` and by `CSI D` (#873).
    ///
    /// **Both verbs take this step, and that is the decision rather than a convenience.**
    /// xterm reaches one `CursorBack` from `CASE_BS` (`charproc.c:3703`) and `CASE_CUB`
    /// (`:3933`) alike; ghostty's `backspace` is `cursorLeft(1)` (`Terminal.zig:1696`).
    /// xterm.js is the one reference that separates them, and does so **on purpose** —
    /// *"Our implementation deviates from xterm on purpose"*, one of whose four bullets is
    /// *"any cursor movement sequence keeps working as expected"* (`InputHandler.ts:810-818`).
    /// The tie was broken for xterm by ADR-0004 and by `XTREVWRAP` being xterm's own
    /// invention (`ctlseqs.txt:952`), with no DEC text above it to appeal to. Maintainer's
    /// call, 2026-09-08, and theirs to reverse; the tally and the reach measurement behind
    /// it are on `tests/reverse_wrap.rs::cursor_left_spends_a_park`.
    ///
    /// With reverse wraparound (?45) a step at column 0 of a *soft-wrapped* row moves back
    /// to the last column of the previous row — undoing one autowrap. Only soft wraps
    /// reverse (the previous row carries `WRAPLINE`), and that is xterm's rule too rather
    /// than an xterm.js import: its walk gives up on `!LineTstWrapped(ld)` (`cursor.c:178`).
    /// A hard CR/LF line does not reverse.
    fn step_back(&mut self) {
        // A parked cursor is logically one past the column it sits on, so under `?45`
        // the first step back lands *on* that column — which is where it already is.
        // The park is therefore **spent** as the first unit of the move rather than
        // cleared alongside it: clearing and decrementing discards the logical `+1` and
        // collapses the parked and unparked states onto the same landing (#80).
        //
        // **The gate needs autowrap as well as the mode**, and reading only the
        // conditional at xterm's spend site says otherwise — which is how a first
        // version of this got it backwards. `cursor.c:153` reads
        // `if ((rev || rev2) && screen->do_wrap) { --count; } else { --col; }`, but
        // `rev` is not the mode flag: `:123-127` define
        // `WRAP_MASK (REVERSEWRAP | WRAPAROUND)` and `rev = ((flags & WRAP_MASK) ==
        // WRAP_MASK)`, so `rev` means *`?45` **and** `?7h`* and the whole branch is dead
        // under `?7l`. ghostty gates the same way and earlier —
        // `if (!self.modes.get(.wraparound)) break :wrap_mode .none;`
        // (`Terminal.zig:1756`), returning through the plain decrement at `:1766-1769`
        // before it can reach the spend at `:1774`. xterm.js never reaches the state at
        // all, since its `?7l` print pins `x = cols - 1` (`InputHandler.ts:612`). So a
        // park taken under `?7l` is **spent by moving**, 3-0, and the park #869 arms
        // there is not this rule's to consume.
        if self.reverse_wraparound && self.autowrap && self.cursor.pending_wrap {
            self.cursor.pending_wrap = false;
            return;
        }
        self.cursor.pending_wrap = false;
        if self.cursor.col > 0 {
            self.cursor.col -= 1;
            return;
        }
        // **The walk needs autowrap too, and for the same reason the spend does.** xterm
        // reaches both arms through one `rev`, so `:165` is as dead under `?7l` as `:153`
        // is, and ghostty returns through the plain decrement at `:1766-1769` before it
        // can reach either. This engine gated only the spend, so `?45h` + `?7l` walked a
        // row where both references clamp — found while sharing this step with `CSI D`.
        if self.reverse_wraparound
            && self.autowrap
            && self.cursor.row > self.scroll_top
            && self.cursor.row <= self.scroll_bottom
        {
            let prev = self.cursor.row - 1;
            let last = self.grid.cols() - 1;
            if self.grid.row_ref(prev).is_wrapped() {
                // **The wrap link survives the walk.** Undoing the *cursor's* trip across
                // the boundary does not undo the boundary: the rows still hold one logical
                // line, and every public reader of that — logical lines, link detection,
                // command extraction, reflow — asks this flag. Clearing it (xterm.js's
                // `line.isWrapped = false`) made two buffers with identical visible content
                // answer differently depending on how the cursor got there, and a resize
                // kept them apart. xterm writes no wrap flag anywhere in `CursorBack`;
                // ghostty only *reads* `prev_row.wrap` (`Terminal.zig:1842-1843`).
                self.cursor.row = prev;
                self.cursor.col = last;
            }
        }
    }

    /// Auto-wrap at end of line: line-feed then return to column 0.
    fn wrapline(&mut self) {
        self.linefeed_inner(true);
        self.cursor.col = 0;
        self.cursor.pending_wrap = false;
    }

    // ---- tab stops (HT / HTS / TBC) ------------------------------------------

    /// HT: advance to the next set tab stop, or the last column if none remain
    /// (no wrap).
    ///
    /// **The deferred wrap is cleared only when the walk actually moves** — see
    /// [`Cursor::pending_wrap`], which owns the rule. At the last column there is
    /// no stop to the right, so this verb changes nothing and must leave the flag
    /// armed; clearing it there discarded the parked position and let the next
    /// print overwrite the character already in that column (#848).
    ///
    /// Three of the four references keep it here, by three different mechanisms:
    /// xterm's `TabToNextStop` clamps to `LineMaxCol` and never touches `do_wrap`
    /// (`tabs.c:142-158`; the one `ResetWrap` on this path is in `TabNext`, gated
    /// on the `curses` resource at `tabs.c:113`, off by default), ghostty's loop
    /// condition `cursor.x < scrolling_region.right` is already false
    /// (`Terminal.zig:2111`), and xterm.js returns early on `x >= cols` because
    /// that *is* its parked state (`InputHandler.ts:850`). alacritty is the
    /// outlier and consumes the wrap instead (`term/mod.rs:1366`); it preserves
    /// the character too, and differs only on which row the next one lands in.
    fn put_tab(&mut self) {
        let cols = self.grid.cols();
        let mut col = self.cursor.col;
        while col + 1 < cols {
            col += 1;
            if self.tabs[col] {
                break;
            }
        }
        if col != self.cursor.col {
            self.cursor.col = col;
            self.cursor.pending_wrap = false;
        }
    }

    /// CHT (CSI Ps I): [`Term::put_tab`] repeated `n` times, stopping at the first
    /// one that does not move — so the deferred-wrap rule is `put_tab`'s, and the
    /// work is bounded by the row rather than by the parameter (#898). The break
    /// is defensive only: a `put_tab` that did not move will not move on a repeat,
    /// so removing it changes no outcome and no test can redden it.
    fn put_forward_tabs(&mut self, n: usize) {
        for _ in 0..n {
            let col = self.cursor.col;
            self.put_tab();
            if self.cursor.col == col {
                break;
            }
        }
    }

    /// CBT (CSI Ps Z): step back `n` tab stops, or to column one if fewer
    /// remain.
    ///
    /// The mirror of [`Term::put_tab`] over the *same* table, walked in the
    /// other direction. Writing it as a mirror rather than as arithmetic is
    /// what keeps the two from drifting: an application that moved a stop with
    /// HTS has moved it for both directions, and a modulo here would disagree
    /// with the forward walk the moment it did.
    ///
    /// The count repeats the walk — `n` stops, not one stop `n` columns away —
    /// which is what makes a multi-field jump land correctly when the stops are
    /// unevenly spaced.
    ///
    /// Backward tabulation is defined *within the line*: it clamps at column
    /// one and never wraps to the row above, which would make it a
    /// cursor-relocating operation across rows and give it interactions with
    /// the wrap state it should not have. The outer loop breaks at column zero
    /// for that reason and for a second one — it bounds the work by the grid
    /// rather than by the parameter, so a hostile `CSI 65535 Z` costs one walk
    /// of the row. That second reason is **defensive only**: `vte` saturates a
    /// parameter at `u16::MAX`, so the unbounded form would cost 65535 no-op
    /// iterations, and no test can redden the guard.
    ///
    /// The **count** converges 4/4 — every reference repeats the *walk* rather
    /// than computing a column: alacritty `term/mod.rs:1571-1585` @ `852e971`,
    /// ghostty `stream_terminal.zig:593-599` + `Terminal.zig:2124-2136` @
    /// `e6e26e1`, xterm `charproc.c:3745-3752` + `tabs.c:131-180` @ `6380a3e`,
    /// xterm.js `InputHandler.ts:1141-1151` + `Buffer.ts:599-603` @ `699f553`.
    ///
    /// The **clamp is 3/4**, and the outlier is alacritty — the one whose loop
    /// shape this most resembles, which is why the resemblance is worth
    /// distrusting. It seeds `col` with the cursor's current column and
    /// overwrites it only inside `if self.tabs[i]` (`term/mod.rs:1578-1583`),
    /// so with **no stop to the left it writes the cursor back unchanged** — a
    /// no-op where the walk below runs to column zero. Reachable after
    /// `CSI 3 g`, since clearing all stops clears column zero too in both
    /// engines. xterm (`TabPrev` returns 0), ghostty (returns at
    /// `x <= left_limit`) and xterm.js (`x < 0 ? 0 : x`) all clamp, and
    /// `back_tab_with_no_stops_lands_at_column_one` is the test that pins which
    /// side justerm is on.
    ///
    /// **Clearing the deferred wrap diverges from all four, deliberately.**
    /// None of them clears it here: alacritty's `move_backward_tabs` writes no
    /// `input_needs_wrap` though its own CUB does (`term/mod.rs:1253`);
    /// ghostty's `horizontalTabBack` calls the *screen*-level `cursorLeft`,
    /// which does not touch `pending_wrap`, where its terminal-level one does
    /// (`Terminal.zig:1768`); xterm's `TabToPrevStop` has no `ResetWrap` at all
    /// — the only one in `tabs.c` is in the *forward* walk and is gated on the
    /// `curses` resource (`tabs.c:113`), off by default; and xterm.js has no
    /// flag, representing the state as `x == cols` and returning early on it,
    /// so its CBT from the right margin moves *nothing*.
    ///
    /// ADR-0004's spec-first rule has nothing to award here, and the reason is
    /// stronger than "the spec is quiet". `ctlseqs.txt:755` is one line, but
    /// that file is xterm's documentation *of xterm* rather than the normative
    /// text; CBT's normative home is ECMA-48, which no pinned tree carries. The
    /// argument that does not depend on a document nobody here can open: the
    /// deferred wrap is an **implementation device** for "the cursor is parked
    /// at the last column", not an ECMA-48 concept, so no version of that spec
    /// can rule on it in principle.
    ///
    /// So the grounds are this engine's own coherence: **every horizontal-positioning
    /// verb here clears the flag** — `move_forward`, `move_back`, `set_col`,
    /// `set_row`, `goto`, `move_up`, `move_down`, `backspace`,
    /// `carriage_return`, `put_tab` — so a back-tab that did not would be the
    /// sole exception. Leaving it armed also reproduces the very bug #826
    /// exists to fix, from the other side: the next character would land on the
    /// *following row* rather than in the column the back-tab chose.
    ///
    /// The unanimity is over that population and not over every writer of
    /// `cursor.col`. `linefeed_inner` and `reverse_index` do **not** clear it,
    /// which is a separate and unsettled question — justerm is the outlier 3-1
    /// there — and deliberately outside this change. `put_tab` is in that
    /// population only where it moves: at the right edge of a full row it finds
    /// no stop and leaves the flag armed (#848), which is the same rule — clear
    /// where the verb moves the cursor — and CBT always moves. See
    /// [`docs/agents/reference-facts.md`](https://github.com/kihyun1998/justerm/blob/master/docs/agents/reference-facts.md).
    ///
    /// **What the divergence actually costs, stated as behaviour rather than as
    /// a flag.** On a full row, `CSI Z` then a print puts the character where
    /// the back-tab landed; every reference puts it on the *following row*,
    /// having in effect discarded the back-tab. Pinned by
    /// `back_tab_on_a_full_row_prints_where_it_landed_not_on_the_next_row`.
    ///
    /// **Cleared concern, with its validity condition.** xterm and ghostty
    /// clamp a back-tab to the **left margin** under origin mode
    /// (`tabs.c:171-175`; `Terminal.zig:2126`), not to column zero. That is
    /// inert here only because this engine implements no DECSLRM, so both
    /// reduce to zero. **If DECSLRM ever lands, this function is a site**, and
    /// nothing else in the tree points at it.
    fn put_back_tab(&mut self, n: usize) {
        let mut col = self.cursor.col;
        for _ in 0..n {
            if col == 0 {
                break;
            }
            while col > 0 {
                col -= 1;
                if self.tabs[col] {
                    break;
                }
            }
        }
        self.cursor.col = col;
        self.cursor.pending_wrap = false;
    }

    /// HTS (ESC H): set a tab stop at the cursor column.
    fn set_tab_stop(&mut self) {
        let col = self.cursor.col;
        self.tabs[col] = true;
    }

    /// TBC (CSI g): clear the tab stop at the cursor (mode 0) or all stops
    /// (mode 3).
    fn clear_tab_stop(&mut self, mode: u16) {
        match mode {
            0 => {
                let col = self.cursor.col;
                self.tabs[col] = false;
            }
            3 => self.tabs.iter_mut().for_each(|t| *t = false),
            _ => {}
        }
    }

    // ---- printing ------------------------------------------------------------

    /// The extended attributes the pen currently stamps onto a cell it writes: the open OSC 8
    /// hyperlink (#26/#46) and a non-default underline colour (SGR 58, #520).
    ///
    /// The colour is gated on the UNDERLINE attribute — an underline colour is meaningless on a
    /// cell that draws no underline, and xterm likewise does not persist it there
    /// (`AttributeData isEmpty()` ignores the colour; `InputHandler.test.ts:2084`). That keeps
    /// it off the wire for cells that never draw it (ADR-0020: no inert per-cell payload). SGR 58
    /// is the *underline* colour, so STRIKETHROUGH alone does not arm it.
    ///
    /// One place, because three sites take their extended attrs from the PEN — the glyph, its wide
    /// spacer, and the vacated wrap column — mirroring the pen half of `Row::ext_attrs_at`, so a
    /// later rider is added here rather than at each of them (#521/#528).
    ///
    /// **Five sites build a cell from the pen, not three, and the other two deliberately do not
    /// come here**: `promote_cluster_to_wide` and `relocate_cluster_wide` synthesise a pair's
    /// spacer, whose attrs are the LEAD's rather than the pen's (ADR-0025 D4), so they read
    /// `Row::ext_attrs_at` and the lead's underline style directly. Counting them in is how a
    /// rider gets added here and silently misses them — which is exactly what #829's underline
    /// style did until a refuting pass measured it.
    fn pen_ext_attrs(&self) -> ExtAttrs {
        let ucolor = self.cursor.pen.underline_color;
        let armed =
            ucolor != Color::Default && self.cursor.pen.flags.contains(CellFlags::UNDERLINE);
        ExtAttrs::from_pen(self.current_link.clone(), armed.then_some(ucolor))
    }

    /// Free a cell that has stopped being part of a glyph — the *structural repair* every
    /// overwrite, erase and row-shift owes the no-orphan invariant when it destroys one half of
    /// a width-2 glyph, plus the spacer a mode-2027 demotion no longer needs.
    ///
    /// This is **not** an erase. The app asked for something at a *different* column; freeing
    /// this one is the engine keeping its own invariant. But it is still a mutation, so it
    /// **damages** — and that is the half every site used to forget, because each function
    /// damaged its own range and the repaired cell lies outside it by construction (that is what
    /// makes it a repair). A frame-mode consumer therefore kept painting the destroyed glyph.
    /// Bundling the reset with its damage is the point of this helper: a repair site added later
    /// cannot forget the half that has no compiler behind it (#530).
    ///
    /// The cell it leaves is a **blank carrying the current background** — the same rule
    /// `clear_cells` already applies to a BCE erase, extended to the repair, so one sentence
    /// covers both: *a blank cell carries the current background.* A bare `Cell::default()`
    /// would punch an uncoloured notch into a coloured run, which no reference implementation
    /// does.
    ///
    /// Deliberately the pen's **background only** — not its full attributes, and this is not a
    /// compromise between references: it is byte-for-byte xterm.js's `_eraseAttrData()`
    /// (`DEFAULT_ATTR_DATA` + `curAttr.bg & ~0xFC000000`, i.e. default everything plus the pen's
    /// background colour), which is what its `replaceCells` / `insertCells` / `deleteCells`
    /// repairs are handed — eight of the twelve sites here. Only xterm's *print* path uses the
    /// whole pen. Taking the whole pen
    /// (xterm.js `setCellFromCodepoint(x, 0, 1, curAttr)`) would plant the pen's hyperlink and,
    /// worse, its DECSCA protection onto a cell the app never wrote — a cell no later erase could
    /// clear. Taking the *cell's own* attributes (alacritty `clear_wide`, which keeps `extra`)
    /// would leave the destroyed glyph's hyperlink alive and clickable, the defect #529 is filed
    /// against. Both were considered and rejected; the maintainer chose this on 2026-07-24 and it
    /// is theirs to reverse (see #530 for what they were shown).
    ///
    /// What used to be recorded here as a known limitation is **resolved** (#538, ADR-0025 D1):
    /// `reset()` still clears the whole content word, but the soft-wrap link is no longer part of
    /// it. The live flag is on the `Row`, so freeing the last column — here or on the erase path —
    /// cannot break a wrap; `CellFlags::WRAPLINE` is wire-only, derived onto the last cell at
    /// encode time and never read back (`cell.rs`). Ending a wrap is now an explicit per-verb call
    /// (`end_wrap`), which is the shape both references already had and the reason the move was
    /// made: ghostty and xterm.js hold the flag on the row/line, and xterm.js takes `clearWrap` as
    /// an explicit argument on its erase helper (`_eraseInBufferLine`, `InputHandler.ts:1175`)
    /// rather than letting a cell clear decide it.
    ///
    /// Known cost, accepted rather than overlooked: with DECSCA the freed cell loses its
    /// protection. ghostty has the same hole and flags it in its own source; justerm does not
    /// implement DECSCA today, so revisit if it lands.
    fn free_cell(&mut self, row: usize, col: usize) {
        let bg = self.cursor.pen.bg;
        let cell = self.grid.cell_mut(row, col);
        cell.reset();
        cell.set_bg(bg);
        // As in `clear_cells`: the bits are gone, so release what they gated (#628).
        self.grid.row_mut(row).purge_side_maps(col..col + 1);
        self.damage_span(row, col, col);
    }

    /// Will the next `wrapline()` actually reach another row?
    ///
    /// `wrapline` → `linefeed` advances in exactly two cases: the cursor sits at the scroll
    /// region's bottom (so the region scrolls under it), or it has a row below it on screen.
    /// Parked *below* a DECSTBM region on the last row it does neither — it silently stays put.
    ///
    /// Both wide-at-boundary paths must ask before they commit anything, because both destroy
    /// content on the assumption that the row is about to change: `write_glyph` blanks the column
    /// it is leaving, and `relocate_cluster_wide` writes its cluster to `(cursor.row, 0..=1)`
    /// *after* the wrap — which is the same row when nothing advanced, so it lands on live cells.
    /// Reasoning only about the vacated source column misses that second case entirely.
    ///
    /// This mirrors `linefeed`'s own condition; the two must be read together.
    fn wrapline_advances(&self) -> bool {
        self.cursor.row == self.scroll_bottom || self.cursor.row + 1 < self.grid.rows()
    }

    /// Blank the last column as the soft-wrap artefact it is, when a width-2 glyph could not fit
    /// there (#528). Shared by the two paths that reach this state: `write_glyph`'s wide-at-boundary
    /// wrap and `relocate_cluster_wide`'s promoted cluster.
    ///
    /// The column is **written**, not merely flagged: a blank built from the current pen, exactly
    /// as every reference does it — xterm.js `setCellFromCodepoint(col, 0, 1, curAttr)`
    /// (`InputHandler.ts:609-611`; `BufferLine.ts:244-251` takes the pen's fg/bg *and* its
    /// `extended` link/colour), ghostty `printCell(0, .spacer_head)` (`Terminal.zig:1410-1412`,
    /// whose `printCell` stamps the cursor's hyperlink), alacritty `write_at_cursor(' ')` under a
    /// `LEADING_WIDE_CHAR_SPACER` template (`mod.rs:1108-1113`, assigning `extra` from it).
    ///
    /// Flagging in place instead left the previous occupant's glyph, hyperlink and underline colour
    /// alive in a cell every text reader skips — so a renderer drew a character that could not be
    /// copied, searched or announced (#528). Building from `Pen::cell` also clears the presence
    /// bits, so no stale side-map entry can be read back through the new cell.
    ///
    /// WRAPLINE marks the row a continuation rather than a hard line-end (search, logical lines
    /// #113 and reflow #7 all read it); the leading-spacer marker makes the text extractors skip
    /// the blank instead of joining `"ab한"` → `"ab 한"`.
    ///
    /// The marker is **alacritty's** `LEADING_WIDE_CHAR_SPACER` (`term/cell.rs`) — ghostty calls
    /// the same thing `.spacer_head`. It is *not* xterm's: xterm.js has no marker at all, writing
    /// a bare null cell and re-inferring the artefact at reflow time from "ends in null and the
    /// following line starts with a wide char". That difference has a consequence here — in
    /// xterm.js a lost marker degrades to an empty cell that trimming drops anyway, whereas
    /// justerm writes `' '`, so the marker is the *only* thing keeping this column out of the
    /// extracted text.
    fn vacate_for_wrap(&mut self, row: usize, col: usize) {
        // Writing this column makes the vacate an overwrite like any other, so it inherits the
        // no-orphan obligation every other overwrite site carries (`write_glyph`,
        // `promote_cluster_to_wide`, `insert_chars`, `delete_chars`, the erase path): if the
        // column was the *spacer* of a wide glyph, blanking it destroys the spacer marker and
        // strands the lead. That is unrecoverable rather than merely untidy — every repair path
        // keys off `is_wide_spacer()`, so once the marker is gone no later write, ECH, EL, ICH
        // or DCH can ever clear the orphan.
        if col > 0 && self.grid.cell(row, col).is_wide_spacer() {
            self.free_cell(row, col - 1);
        }
        let mut vacated = self.cursor.pen.cell(' ');
        vacated.set_leading_spacer();
        *self.grid.cell_mut(row, col) = vacated;
        self.begin_wrap(row);
        let ext = self.pen_ext_attrs();
        self.grid.row_mut(row).set_ext_attrs(col, ext);
        // The cell's contents changed, so a frame-mode consumer must be told or it keeps painting
        // the old glyph (ADR-0003: every mutation site records damage). The *repaired* lead above
        // is damaged by `free_cell`, which owns that pairing for all twelve repair sites — this
        // site used to hand-roll it, and keeping both left neither able to discriminate.
        self.damage_span(row, col, col);
    }

    /// Place one already-charset-translated scalar: join it to the previous cluster
    /// under mode 2027, attach it as a combining mark, or write it as a new glyph.
    ///
    /// Split out of `print` so `REP` can re-enter the print path *below* two things it
    /// must not repeat (#825): the VT52 `ESC Y` coordinate intercept, and the GL
    /// character-set translation — `REP` reads its grapheme back off a cell, which
    /// holds the *translated* glyph, so passing it through `print` would map it twice.
    /// Neither is observable today (the intercept is unreachable because `ESC Y`
    /// disarms the repeat, and no glyph either implemented set produces is a key in
    /// its own table), so this is insurance, and its condition is worth stating: it
    /// stops being insurance the moment a set is added whose output overlaps its
    /// input.
    ///
    /// The three arms that place content are exactly the sites that arm
    /// [`Term::repeat_anchor`]. xterm reaches the same set from the other end — it arms
    /// on every printed scalar and then rejects the zero-width ones with a guard at
    /// `REP` (`charproc.c:6154`) — and the two are equivalent because the only scalars
    /// that reach here with no width are unreachable in the first place.
    fn place_grapheme(&mut self, c: char) {
        // Grapheme-cluster mode (DEC ?2027, #295): if `c` extends the previous cell's cluster,
        // join it there instead of placing a new cell. OFF → the per-char (wcwidth) path below.
        if self.grapheme_clustering
            && let Some(at) = self.try_grapheme_join(c)
        {
            self.repeat_anchor = Some(at);
            return;
        }
        match c.width() {
            // Zero-width (combining marks): a zero-width code point is a combining
            // mark — attach it to the previous base glyph rather than dropping it.
            Some(0) => self.repeat_anchor = Some(self.push_combining(c)),
            // Reachable, and the only scalar that reaches it: `vte` sends C0 and the
            // 8-bit C1 range to `execute`, but `ground_dispatch` matches only
            // `'\x00'..='\x1f' | '\u{80}'..='\u{9f}'` there (`vte-0.15.0/src/lib.rs:722`),
            // so `DEL` (0x7F) arrives here and `'\u{7f}'.width()` is `None`. It writes no
            // cell, so it clears the anchor — which is xterm's answer too, reached by its
            // own route (`lastchar` is set only by CASE_PRINT, and REP guards on positive
            // width, `charproc.c:6154`). An earlier version of this claimed the arm was
            // unreachable, citing a `0x7F => ()` line that belongs to `CsiIgnore`.
            None => self.repeat_anchor = None,
            // Coerced to a pair, because a pair is the only multi-column shape the cell model
            // has (`WIDE_CHAR` + exactly one `WIDE_CHAR_SPACER`) — see ADR-0025, which states
            // every clause over "a pair" and never over a wider run. `unicode-width` genuinely
            // returns 3 for at least one codepoint (U+17D8 KHMER SIGN BEYYAL, a ligature drawn
            // as three characters), and that value is not wrong — it is unrepresentable here.
            //
            // Left uncoerced, the width fell through *every* wide branch in `write_glyph`
            // (each gated on `width == 2`) while still driving the cursor advance, so the glyph
            // landed as a lone narrow cell followed by columns that no flag distinguished from
            // real blanks: search could not find the text on screen and word selection split
            // the run, handing the clipboard a space the buffer never held (#595).
            //
            // All three references bound it, and ghostty says why in the same words —
            // `unicode/props.zig:11-13`, *"We clamp to [0, 2] … i.e. 3-em dash becomes a 2-em
            // dash"*. Clamping *here* rather than inside `write_glyph` keeps the two jobs apart:
            // this is the policy for an out-of-range external value, and the invariant it
            // establishes is asserted at the site that depends on it.
            Some(width) => self.repeat_anchor = self.write_glyph(c, width.min(2)),
        }
    }

    /// Write one glyph at the cursor, handling deferred wrap and the wide-char
    /// spacer, then advance the cursor (deferring the wrap if it hits the edge).
    /// Returns where the glyph landed — `(row, col)` of its lead cell — or `None` on
    /// the one path that writes nothing: a width-2 glyph that cannot fit the last column
    /// with autowrap off is dropped. [`Term::repeat_anchor`] is set from this, so a
    /// print that placed no cell must not arm the repeat.
    fn write_glyph(&mut self, c: char, width: usize) -> Option<(usize, usize)> {
        // Every wide branch below is gated on `width == 2`, and the four unguarded uses
        // (`insert_chars`, `col + width - 1` twice, the cursor advance) assume the same bound.
        // The caller coerces (#595); this states the assumption at the site that holds it, so a
        // future second caller fails a test rather than writing an unmarked run of blanks.
        // Ghostty pairs its own source-side clamp with the same assertion for the same reason
        // (`Terminal.zig`, *"it is possible to have a width of 3 … assert(width <= 2)"*).
        debug_assert!(
            width <= 2,
            "write_glyph({c:?}, {width}) — the cell model represents at most a pair"
        );
        let cols = self.grid.cols();

        // Resolve a deferred last-column wrap before placing the next glyph.
        // The row being left soft-wrapped: mark its last cell so reflow (#7) can
        // tell it from a hard CR/LF line-end.
        if self.cursor.pending_wrap && !self.autowrap {
            // **This is where DECAWM is tested, and since #869 it is the only place.**
            // The arm is unconditional, so under `?7l` every row-filling print leaves a
            // park and this guard is what spends it in place instead of wrapping — not
            // the narrow "the mode was turned off after the flag was armed" repair it
            // began as. Deleting it does not merely regress an edge case; it wraps with
            // autowrap disabled. `decawm.rs::autowrap_off_overwrites_the_last_column` is
            // the guard on the guard.
            //
            // **All four references print in place here**: xterm clears `do_wrap` and
            // only then asks `WRAPAROUND` (`charproc.c:7059-7061`), xterm.js un-parks
            // with `x = cols - 1` in the else arm of its `wraparoundMode` branch
            // (`InputHandler.ts:612`), ghostty gates the whole consume
            // (`Terminal.zig:1368`) and alacritty's `wrapline` early-returns on
            // `!LINE_WRAP` (`term/mod.rs:962`). What they differ on is whether the flag
            // is left standing afterwards, and that is a separate axis — see
            // `docs/agents/reference-facts.md`, where #848's "2-2" is corrected as a
            // sampling artefact rather than a real split.
            //
            // Pre-existing, and #848 widened it: until that change `put_tab` cleared
            // the flag, so `abc` + `?7l` + `HT` + `X` printed in place by accident.
            self.cursor.pending_wrap = false;
        }
        if self.cursor.pending_wrap {
            let row = self.cursor.row;
            // Claim the wrap only if there will *be* a next row to continue into. Parked below a
            // DECSTBM region on the last row, `wrapline` → `linefeed` advances nothing and the
            // glyph overwrites this same row from column 0 — so the wrap never happened, and a
            // flag set here is permanently false: the cursor never leaves, nothing clears it, and
            // it survives into `backspace`'s reverse-wraparound, reflow, and every text reader.
            //
            // The predicate is not new and neither is its rationale: `wrapline_advances` was
            // written for exactly this state and is already asked by both wide-at-boundary paths.
            // This narrow path was the one caller that committed without asking. (Surfaced by the
            // #540 completeness pass, which found a row-shift verb inheriting the bogus flag and
            // merging two unrelated logical lines.)
            if self.wrapline_advances() {
                self.begin_wrap(row);
            }
            self.wrapline();
        }

        // A width-2 glyph that cannot fit in the last column wraps first — unless
        // autowrap is off, in which case it is dropped (xterm.js `continue`), not
        // squeezed or wrapped.
        if width == 2 && self.cursor.col + 1 >= cols {
            if !self.autowrap {
                return None; // dropped: nothing written, so nothing to repeat
            }
            // …but only if the wrap actually happens: vacating for a wrap that never occurs
            // blanks a column holding a live glyph.
            if self.wrapline_advances() {
                self.vacate_for_wrap(self.cursor.row, cols - 1);
            }
            self.wrapline();
        }

        // Insert mode (IRM): open a `width`-wide gap at the cursor first, shifting
        // the row's tail right (off-edge cells discarded, wide halves repaired),
        // then write into the gap — mirrors xterm.js's insertCells (#64).
        if self.insert_mode {
            self.insert_chars(width);
        }

        let (row, col) = (self.cursor.row, self.cursor.col);

        // Overwriting either half of a pair that wrapped from the row above ends that pair, so the
        // row above's artefact record is void (#534). The one exception is the in-place same-width
        // overwrite — a wide lead replaced by another wide lead at the same column — which is
        // ghostty's `if (cell.wide != wide)` escape and the reason this is asked *before* the
        // write rather than after it. Note IRM has already run its own check inside `insert_chars`
        // by the time this would fire, on the pre-shift state, which is the correct one.
        if col <= 1 && self.wrapped_pair_at_row_start(row) && !(col == 0 && width == 2) {
            self.void_wrap_artefact_above(row);
        }

        // Overwriting one half of an existing wide glyph orphans the other —
        // clear it so no stray lead/spacer is left behind.
        let last = col + width - 1;
        if col > 0 && self.grid.cell(row, col).is_wide_spacer() {
            self.free_cell(row, col - 1);
        }
        if last + 1 < cols && self.grid.cell(row, last).is_wide() {
            self.free_cell(row, last + 1);
        }

        let mut cell = self.cursor.pen.cell(c);
        if width == 2 {
            cell.insert_flags(CellFlags::WIDE_CHAR);
        }
        *self.grid.cell_mut(row, col) = cell;
        // Stamp the pen's extended attrs — the open hyperlink (#26/#46) and a non-default
        // underline colour (#520) — into the row's side maps.
        let ext = self.pen_ext_attrs();
        // `.clone()`: `ExtAttrs` stopped being `Copy` at #628 (the link rider is a shared
        // `Arc<str>`), and the spacer below stamps the same value — a refcount bump, not
        // a second string.
        self.grid.row_mut(row).set_ext_attrs(col, ext.clone());

        // The trailing column of a wide glyph carries a distinct spacer marker —
        // and the same link + underline colour, so a hover/selection/underline over
        // either half agrees.
        if width == 2 && col + 1 < cols {
            let mut spacer = self.cursor.pen.cell(' ');
            spacer.insert_flags(CellFlags::WIDE_CHAR_SPACER);
            *self.grid.cell_mut(row, col + 1) = spacer;
            self.grid.row_mut(row).set_ext_attrs(col + 1, ext);
        }

        // Record damage for the cell(s) just written.
        self.damage_span(row, col, col + width - 1);

        // Advance. Reaching/passing the last column sets pending-wrap instead of
        // wrapping eagerly — the cursor parks on the last column.
        let new_col = col + width;
        if new_col >= cols {
            self.cursor.col = cols - 1;
            // The park is taken whatever the mode says (#869): the cursor is logically
            // one past this column either way, and that is the whole of what this flag
            // means. With `?7l` the *consume* site above spends the park in place, so
            // the next glyph still overwrites the last column (#63) — but if the mode
            // is re-enabled before that print, the park is still there and it wraps,
            // which is what all four references do.
            self.cursor.pending_wrap = true;
        } else {
            self.cursor.col = new_col;
        }
        Some((row, col))
    }

    /// The column, on the cursor's row, of the cluster the cursor last printed into —
    /// or `None` when nothing precedes it on this row. Shared by the combining-mark
    /// attach point and the mode-2027 join point, which each used to carry their own
    /// copy of it.
    ///
    /// # Two cases, and why the first one is trustworthy again (#865, #869)
    ///
    /// **Parked.** [`Cursor::pending_wrap`] says the cursor is logically one past the
    /// column it sits on, so the cluster is *at* the cursor — and once left over a
    /// `WIDE_CHAR_SPACER` to reach its lead.
    ///
    /// **This reading was wrong for a whole mode until #869, and the repair is not
    /// here.** The flag used to be armed as `pending_wrap = self.autowrap`, so with
    /// `?7l` a print that filled the last column pinned the cursor and armed nothing:
    /// a pin and a bare *advance onto* that column shared every cursor field, and a
    /// mark landed one column too far left. #865 worked around it here by consulting
    /// [`Term::repeat_anchor`]; #869 removed the cause instead — the arm is now
    /// unconditional and the mode is tested where it is consumed, which is what
    /// alacritty (`term/mod.rs:1136`), ghostty (`Terminal.zig:1434`) and xterm
    /// (`charproc.c:7152`) all do — that line is the *exact-fill* arm and is
    /// unconditional; xterm's *overflow* arm two branches up (`:7145`) is gated on
    /// `WRAPAROUND`, and the arm site here is only ever reached by the former. The
    /// workaround was then measured dead across the
    /// whole core suite, against a positive control that reproduced it under the old
    /// arming, and removed.
    ///
    /// **Not parked.** The cursor is merely *at* a cell, so the cluster is one column
    /// left, and once more left over a spacer. This is also the answer after a bare
    /// cursor move to the last column, which the four references answer four different
    /// ways: xterm attaches under the cursor (`char_was_written` is false after
    /// `ResetWrap`, so it falls back to `cur_col`), alacritty and ghostty attach one
    /// column left, and xterm.js attaches nowhere — its `precedingJoinState` is zeroed
    /// on every escape transition (`EscapeSequenceParser.ts:676`), so `shouldJoin` is
    /// false (`UnicodeV6.ts:134`) and the mark becomes its own zero-width cell. This
    /// engine keeps the answer it had, which is the plurality's; #865 deliberately did
    /// not reopen it, since nothing measured reaches the case.
    ///
    /// **`REP` still does not use this**, and the reason is on [`Term::repeat_anchor`]:
    /// it needs the position a print wrote even where the cursor has since moved, which
    /// is a different question from the one asked here.
    fn cursor_cluster_col(&self) -> Option<usize> {
        let row = self.cursor.row;
        // The pinned case. The wide arm is the same cell reached from its spacer: a
        // pair that fills the row leaves the cursor on the trailing spacer, one past
        // the anchored lead.
        let col = if self.cursor.pending_wrap {
            self.cursor.col
        } else if self.cursor.col == 0 {
            return None;
        } else {
            self.cursor.col - 1
        };
        Some(if self.grid.cell(row, col).is_wide_spacer() {
            col.saturating_sub(1)
        } else {
            col
        })
    }

    /// The text the cell at `(row, col)` holds, in print order: its base glyph followed
    /// by any combining marks the row's side table carries for it. One grapheme cluster
    /// by construction — it is what a single print produced.
    ///
    /// A `String` and not a `Vec<char>`, because both callers want text: returning scalars
    /// and collecting cost a second allocation and measured 2.06x on the join path
    /// (11.66 ms -> 24.06 ms over 20k joins, release, best of 7). `REP` iterates
    /// `.chars()` instead, which costs it nothing.
    ///
    /// **It is no longer on the per-scalar path.** Until #867 the mode-2027 join called this for
    /// every printed scalar, which is what made a growing cluster quadratic; the join now consults
    /// it only when a width can actually change, so this is O(L) once per cluster rather than once
    /// per join.
    fn cluster_text(&self, row: usize, col: usize) -> String {
        let mut out = String::new();
        out.push(self.grid.cell(row, col).c());
        if let Some(marks) = self.grid.row_ref(row).combining_at(col) {
            out.extend(marks.iter().copied());
        }
        out
    }

    /// REP (CSI Ps b): repeat the preceding grapheme `count` times (#825). The caller
    /// owns the armed check — see the `'b'` arm of `csi_dispatch`, which holds both
    /// halves of the ordering this sequence needs.
    ///
    /// **The repeat re-enters the print path**, which is the load-bearing decision:
    /// printing already owns pending-wrap, autowrap, wide-character pairing, cluster
    /// promotion under mode 2027, the pen, insert mode and the scroll region, so a
    /// cell-fill would have to re-derive every one of them and would drift from typed
    /// text the first time any of them changed. ghostty does the same
    /// (`src/terminal/Terminal.zig:452-456`), and so does xterm.js.
    ///
    /// **What is repeated is the cluster at [`Term::repeat_anchor`], read off the cell.**
    /// A retained copy would have to be kept in step with the cell by hand at three
    /// arming sites and nothing would catch it drifting; the anchor keeps the *position*
    /// exact, which is the half a read-back can get wrong.
    ///
    /// **That the unit is the cluster is a product judgement, not a derivation**, and
    /// the three references give three answers. xterm repeats *nothing* after a
    /// combining mark — its retained value is a single `IChar`, so the mark replaces
    /// the base and the positive-width guard (`charproc.c:6154`) then rejects it.
    /// ghostty repeats the base *without* its marks: its cluster-append branch returns
    /// before `previous_char = c` (`Terminal.zig:1355-1365`). xterm.js repeats the
    /// whole cluster, reading it off the cell (`InputHandler.ts:1649-1671`). ADR-0004
    /// makes xterm the tie-breaker for *the spec*, and xterm's answer here follows from
    /// a scalar `lastchar` rather than from a reading of it — while a cell in this
    /// engine holds a cluster. Decided by the maintainer on 2026-09-07 and theirs to
    /// reverse; a better derivation does not settle it.
    ///
    /// # Two bounds, and only one of them is the load-bearing one
    ///
    /// The count is untrusted and the repeat is the only place in this engine where one
    /// wire parameter buys unbounded work, so it is bounded twice — for different
    /// reasons, and the *order of importance is the reverse of the order they read in*.
    ///
    /// **The progress guard is what actually bounds the pathological case.** An
    /// iteration that places no new cell has not repeated anything: under mode 2027 a
    /// cluster ending in `ZWJ` re-joins the cluster it was read from, so each replay
    /// grows one cell's cluster instead of writing a second one, and `try_grapheme_join`
    /// **was** O(L) in that cluster's length. Measured before the guard: `?2027h`,
    /// `U+1F468`, `U+200D`, then the eight bytes `CSI 65535 b` cost **593 seconds** —
    /// nine minutes and fifty-three seconds of one consumer thread, for eight bytes of
    /// PTY output. The guard ends the loop the first time an iteration leaves the anchor
    /// where it found it, which is exactly the condition "nothing was repeated".
    ///
    /// **#867 removed that O(L), and it did not retire this guard.** The join is now
    /// constant in the cluster's length, so the amplification that produced 593 seconds
    /// no longer exists — but a no-progress iteration is still a no-progress iteration,
    /// and without the guard `CSI 65535 b` would still run 65 535 of them to place
    /// nothing. The guard bounds pointless work; it never bounded the cost of a join.
    ///
    /// **The count cap is defence in depth and would not have caught that case**, which
    /// is why it is stated second. The cap is a whole buffer's worth of
    /// cells, and at the default 10 000-line scrollback that is 801 920 on an 80x24
    /// grid — larger than the 65535 a `u16` parameter can carry, so it never binds
    /// there. It binds on a small buffer, where a count far past what the buffer can
    /// hold only rewrites what the repeat already wrote. Shipping the cap alone would
    /// have looked like a fix for the measurement above and been none.
    ///
    /// Both are divergences from every reference: xterm (`charproc.c:6156`), xterm.js
    /// (`InputHandler.ts:1655`) and ghostty (`Terminal.zig:452-456`) all loop uncapped,
    /// and alacritty does not implement the sequence. The asymmetry that justifies them
    /// is that all three *are* the terminal and own the thread they burn, while this is
    /// a library running on a consumer's.
    fn repeat_last(&mut self, count: usize) {
        let Some((row, col)) = self.repeat_anchor else {
            return;
        };
        // Snapshot once: the repeats move the anchor, so re-reading it per iteration
        // would repeat the growing run rather than the grapheme.
        let cluster = self.cluster_text(row, col);
        let cap = (self.scrollback_limit + self.grid.rows()).saturating_mul(self.grid.cols());
        for _ in 0..count.min(cap.max(1)) {
            let before = self.repeat_anchor;
            for c in cluster.chars() {
                self.place_grapheme(c);
            }
            if self.repeat_anchor == before {
                break; // placed no new cell — see "the progress guard" above
            }
        }
    }

    /// Attach a combining mark (width-0 code point) to the grapheme it modifies —
    /// the cell the cursor just left. With pending-wrap the cursor still sits on
    /// the just-written last-column glyph, so attach in place (no back-up, no
    /// deferred wrap); otherwise step back one column, and once more over a
    /// wide-char spacer to reach its lead. Stored in the grapheme side-table.
    fn push_combining(&mut self, c: char) -> (usize, usize) {
        let row = self.cursor.row;
        // `unwrap_or(0)`: a mark that opens the stream has no base and attaches to
        // column 0, which is what the `saturating_sub` here did before #825. The join
        // path declines that case instead; the two differ deliberately.
        let col = self.cursor_cluster_col().unwrap_or(0);
        // Append the mark to the row's combining map at this column (setting the
        // cell's combining bit). No global pool — the cluster rides the row.
        self.grid.row_mut(row).push_combining(col, c);
        self.damage_span(row, col, col);
        (row, col)
    }

    /// Mode 2027 (#295): if `c` **extends** the previous cell's grapheme cluster (UAX #29), append
    /// it to that cell's side-table — no new cell, no cursor advance — and return where it joined.
    /// Otherwise `None`, so `place_grapheme` takes the per-scalar path (a break starts a cell).
    ///
    /// The break state lives in the cell rather than being carried across calls, so cursor moves
    /// and CR/LF cannot corrupt it — but the cluster is **not** reconstructed to ask the question
    /// (#867): [`crate::grapheme::joins_cluster`] reads a bounded tail of the side table, and the
    /// width oracle is consulted only when [`crate::grapheme::width_may_change`] says the answer
    /// can have moved. Together those make the join O(1) in the cluster's length, where it used to
    /// be O(L) three times over.
    fn try_grapheme_join(&mut self, c: char) -> Option<(usize, usize)> {
        let row = self.cursor.row;
        // Locate the previous cluster's base cell; `None` means nothing precedes it on
        // this row, so there is nothing to extend.
        let Some(col) = self.cursor_cluster_col() else {
            return None; // nothing precedes on this row
        };
        // The cell is read, never rebuilt into a string (#867): both the break question and the
        // width question are answered from the base scalar, the side table's length, and — only
        // when the width can actually move — the cluster text itself.
        let base = self.grid.cell(row, col).c();
        let base_is_wide = self.grid.cell(row, col).is_wide();
        let (joins, first_join) = {
            let marks = self.grid.row_ref(row).combining_at(col).unwrap_or(&[]);
            (
                crate::grapheme::joins_cluster(base, marks, c),
                marks.is_empty(),
            )
        };
        if !joins {
            return None;
        }
        // Width promotion: a flag's second regional indicator, or a text-base + VS16, grows the
        // cluster to width 2. `UnicodeWidthStr` over the whole cluster remains the authority for
        // that; `width_may_change` only decides whether it has to be asked, so a cluster that
        // keeps growing stops paying for an answer that cannot have moved. Read BEFORE the push,
        // because `cluster_text` reads the side table this join is about to extend.
        let cluster_w = if crate::grapheme::width_may_change(c, first_join, base_is_wide) {
            let mut prev = self.cluster_text(row, col);
            prev.push(c);
            UnicodeWidthStr::width(prev.as_str())
        } else if base_is_wide {
            2
        } else {
            1
        };
        // Join: ride the side-table (no new cell).
        self.grid.row_mut(row).push_combining(col, c);
        // Where the cluster ends up, which is not always where it was joined: a promotion at
        // the last column relocates it to the next row (#303), and the anchor has to follow or
        // it names a column `vacate_for_wrap` just blanked.
        let mut at = (row, col);
        if cluster_w == 2 && !self.grid.cell(row, col).is_wide() {
            at = self.promote_cluster_to_wide(row, col);
        } else if cluster_w == 1 && self.grid.cell(row, col).is_wide() {
            // The mirror case: a default-wide emoji + VS15 (text selector) shrinks to width 1.
            self.demote_cluster_to_narrow(row, col);
        }
        self.damage_span(row, col, col);
        Some(at)
    }

    /// Shrink a wide cluster cell back to a single-width cell (#295): a default-wide emoji joined by
    /// VS15 (U+FE0E, the text selector) requests text presentation → width 1. Remove `WIDE_CHAR`,
    /// free the spacer, and back the cursor up over it (the inverse of `promote_cluster_to_wide`).
    fn demote_cluster_to_narrow(&mut self, row: usize, col: usize) {
        let cols = self.grid.cols();
        self.grid
            .cell_mut(row, col)
            .remove_flags(CellFlags::WIDE_CHAR);
        if col + 1 < cols {
            self.free_cell(row, col + 1); // free the now-unused spacer
        }
        // The cluster shrank 2→1: the cursor sat just past the wide cell (col+2, or pending-wrap on
        // the last column); it now sits just past the single-width cell at col+1.
        self.cursor.pending_wrap = false;
        self.cursor.col = (col + 1).min(cols - 1);
        self.damage_span(row, col, (col + 1).min(cols - 1));
    }

    /// Widen a narrow base cell to a double-width cluster in place (#295): set `WIDE_CHAR`, write
    /// its spacer, and step the cursor over it. Only reached when a joining scalar (flag's 2nd RI,
    /// VS16) promotes the cluster to width 2. A base pinned at the last column has no room for a
    /// spacer — relocation is a later step; until then it stays narrow (rare, renders single-width).
    fn promote_cluster_to_wide(&mut self, row: usize, col: usize) -> (usize, usize) {
        let cols = self.grid.cols();
        if col + 1 >= cols {
            // No spacer room at the last column: relocate the whole cluster to the next line as a
            // wide cell (the row soft-wraps), mirroring write_glyph's wide-at-boundary wrap (#303).
            return self.relocate_cluster_wide(row, col);
        }
        // Overwriting col+1 with the spacer can orphan the far half of a WIDE glyph standing there
        // (the cursor may have been repositioned before the joining scalar arrived). Reset that
        // orphan, exactly as write_glyph does (2462-2470), so no dangling spacer survives.
        if self.grid.cell(row, col + 1).is_wide() && col + 2 < cols {
            self.free_cell(row, col + 2);
        }
        self.grid
            .cell_mut(row, col)
            .insert_flags(CellFlags::WIDE_CHAR);
        // The spacer is the lead's second half, so it takes the LEAD's extended attrs — the
        // hyperlink and underline colour riding the row's side maps — exactly as write_glyph
        // stamps both halves of a wide write. `pen.cell(' ')` carries neither (and the pen may
        // have moved on since the base was printed), so they are re-attached here; a base with
        // none clears whatever the overwritten column held (#521).
        let ext = self.grid.row_ref(row).ext_attrs_at(col);
        // The underline STYLE needs the same treatment as those extended attrs and for the same
        // reason this comment already gives (#829): it is the LEAD's, and the pen may have moved
        // on. It rides the packed cell rather than a side map, so it is carried across directly
        // instead of through `set_ext_attrs`. ADR-0025 D4 — a path that *synthesises* one half of
        // a pair carries the whole pair; taking this from the pen curls the left half and leaves
        // the right half bare.
        let lead_style = self.grid.cell(row, col).underline_style();
        let mut spacer = self.cursor.pen.cell(' ');
        spacer.insert_flags(CellFlags::WIDE_CHAR_SPACER);
        spacer.set_underline_style(lead_style);
        *self.grid.cell_mut(row, col + 1) = spacer;
        self.grid.row_mut(row).set_ext_attrs(col + 1, ext);
        // The cursor sat at col+1 (just past the narrow base); move it over the new spacer, applying
        // the same last-column pending-wrap rule as a wide write.
        let new_col = col + 2;
        if new_col >= cols {
            self.cursor.col = cols - 1;
            self.cursor.pending_wrap = true;
        } else {
            self.cursor.col = new_col;
        }
        self.damage_span(row, col, col + 1);
        // Promoted in place: the lead did not move.
        (row, col)
    }

    /// Relocate a last-column narrow cluster to the next line as a wide cell (#303): its base +
    /// side-table marks move to `(next_row, 0..=1)` and the vacated last column becomes a soft-wrap
    /// (WRAPLINE + leading spacer), exactly as `write_glyph` wraps a wide glyph that can't fit. With
    /// autowrap off it stays narrow.
    ///
    /// The destination is an **overwrite**, so it owes the no-orphan repair every other overwrite
    /// site owes (#529, ADR-0025 D4) — see the comment at that site for why justerm restates it
    /// once per wide-writing path where the references get it structurally.
    ///
    /// The `cols < 2` arm is **unreachable since #547** —
    /// `MIN_COLUMNS = 2` is the floor on every path that sets a width — and is kept only as a
    /// bounds guard for the `col + 1` writes below, not as a described behaviour.
    fn relocate_cluster_wide(&mut self, row: usize, col: usize) -> (usize, usize) {
        let cols = self.grid.cols();
        if cols < 2 || !self.autowrap || !self.wrapline_advances() {
            // Nowhere to place a wide cell — leave it narrow. `!wrapline_advances()` joins the
            // other two for the same reason: with no next row, the relocation would write the
            // cluster over columns 0-1 of the *current* row and destroy whatever is there.
            return (row, col);
        }
        // Capture the base cell (glyph + attrs), its marks, and its extended attrs before
        // vacating. The extended attrs (hyperlink, underline colour) must be read HERE and not
        // after the move: they live in the *source row's* side maps, and `wrapline()` below may
        // scroll — after which that row is a different (or recycled) `Row` (#521).
        let base = *self.grid.cell(row, col);
        let marks: Vec<char> = self
            .combining_at(row, col)
            .map(<[char]>::to_vec)
            .unwrap_or_default();
        let ext = self.grid.row_ref(row).ext_attrs_at(col);
        // Vacate the last column as a soft-wrap artefact — the same step `write_glyph` takes for a
        // wide glyph that cannot fit, and now literally the same code, so the two cannot drift
        // apart again (#528; they held opposite behaviours until then).
        self.vacate_for_wrap(row, col);
        // Advance to the next line (scrolls if at the bottom); cursor lands at col 0.
        self.wrapline();
        let nr = self.cursor.row;
        // The destination is an overwrite like any other, so it owes the same no-orphan repair
        // `write_glyph` performs for its own trailing column (#529, D4): the spacer about to land
        // on `(nr, 1)` half-destroys a wide glyph standing there, stranding its far half at
        // `(nr, 2)` — a `WIDE_CHAR_SPACER` with no lead to its left, still carrying the destroyed
        // glyph's hyperlink and underline colour. Asked *before* the writes, on the pre-write
        // state, exactly as `write_glyph`'s `last + 1` check is.
        //
        // Two of the three references have this exact site, and both repair it without a rule of
        // their own, because they write a pair as two *separate* cell writes and the repair lives
        // in the write:
        //   - xterm.js names the case outright — *"Combining character widens 1 column to 2. Move
        //     old character to next line."* (`InputHandler.ts:583-611` @ 699f553,
        //     `copyCellsFrom(oldRow, oldCol, 0, oldWidth, false)` at `:605-607`). The relocation
        //     leaves `x == 2`, so its once-per-run right-edge repair (`:668-669`) lands on exactly
        //     the orphaned column.
        //   - ghostty relocates in `Terminal.zig:1188-1252` @ e6e26e1 and reaches the repair
        //     through `cursorRight(1); printCell(0, .spacer_tail)` (`:1251-1252`) — that second
        //     `printCell` runs the `cell.wide != wide` switch (`:1484`) whose `.wide` arm clears
        //     the neighbouring lead's tail (`:1489-1499`).
        //   - alacritty has **no** counterpart: a width-0 codepoint returns early through
        //     `push_zerowidth` (`term/mod.rs:1069-1085` @ 852e971), so a cluster never changes
        //     width and nothing is ever relocated. Its orphan repair (`:994-1008`) is still the
        //     mechanism reference, reached the same way — one repair per `write_at_cursor`.
        // justerm writes both halves in one step, so the repair is not structural here and each
        // wide-writing path restates it — this is the third (`write_glyph`,
        // `promote_cluster_to_wide`, and now the relocation).
        //
        // What justerm does **not** copy is ghostty's reach-back at this site: its `.wide` arm
        // also clears the previous row's `.spacer_head` (`:1504-1506`, gated `cursor.y > 0 and
        // cursor.x <= 1`) — the very marker this relocation set seven statements earlier
        // (`:1200`). Derived from source, not executed. Suppressing it here is #534's rule
        // verbatim: a repair keyed on a state predicate must not fire while that state is
        // mid-construction.
        //
        // The other two obligations `write_glyph` carries are N/A here, recorded because an
        // unexplained omission is what gets re-litigated:
        //   - the *left*-orphan repair asks `col > 0`, and the lead lands at column 0.
        //   - `void_wrap_artefact_above(nr)` would clear a record that `vacate_for_wrap` **just
        //     set**, in both the advance case (`nr == row + 1`, so its target `nr - 1` is `row`)
        //     and the scroll case (`nr == row`, the source rotated up to `row - 1`). Firing it
        //     would be self-clobbering, not merely redundant — the same shape as #534's
        //     mid-construction rule. Measured after a repairing relocation: `is_row_wrapped(0)`
        //     and `(0, cols-1).is_leading_spacer()` both hold.
        //
        // `2 < cols` is a live bound, not defence in depth. The print paths cannot leave a
        // `WIDE_CHAR` lead in the last column — `write_glyph` wraps rather than write one there
        // and `promote_cluster_to_wide` relocates rather than promote in place — but `Row::resize`
        // can: the alt screen resizes without reflowing (#567), so truncating a row through a pair
        // strands its lead in the final column. The relocation then meets `is_wide() == true` at
        // `cols == 2`, and without the bound reads `(nr, 2)` on a two-column grid — an
        // out-of-bounds panic in a library, inside a consumer's process, reachable by shrinking a
        // window over a CJK glyph. Pinned by `min_columns.rs::
        // a_relocation_beside_a_truncated_wide_lead_does_not_index_past_the_row`.
        if 2 < cols && self.grid.cell(nr, 1).is_wide() {
            self.free_cell(nr, 2);
        }
        // Re-place the base as a wide lead + spacer, re-attaching the marks fresh (drop the combining
        // bit so push_combining starts a clean cluster at the new column).
        let mut lead = base;
        lead.set_combined(false);
        lead.insert_flags(CellFlags::WIDE_CHAR);
        *self.grid.cell_mut(nr, 0) = lead;
        for m in marks {
            self.grid.row_mut(nr).push_combining(0, m);
        }
        // Re-attach the extended attrs to BOTH halves at the new row. `lead` copied the base's
        // presence bits but not its map entries, so without this the bit is set with nothing
        // behind it — the read is gated and silently returns the default, and the frame stops
        // round-tripping (the cell encodes as linked with no index).
        self.grid.row_mut(nr).set_ext_attrs(0, ext.clone());
        // …and the underline style from the relocated LEAD, for the reason the sibling site above
        // states (#829, ADR-0025 D4).
        let lead_style = self.grid.cell(nr, 0).underline_style();
        let mut spacer = self.cursor.pen.cell(' ');
        spacer.insert_flags(CellFlags::WIDE_CHAR_SPACER);
        spacer.set_underline_style(lead_style);
        *self.grid.cell_mut(nr, 1) = spacer;
        self.grid.row_mut(nr).set_ext_attrs(1, ext);
        // Cursor just past the wide cell (pending-wrap if it fills a 2-column row).
        if cols <= 2 {
            self.cursor.col = cols - 1;
            self.cursor.pending_wrap = true;
        } else {
            self.cursor.col = 2;
            self.cursor.pending_wrap = false;
        }
        self.damage_span(nr, 0, 1);
        // The cluster's new home. Callers anchor on this, not on the vacated column.
        (nr, 0)
    }

    // ---- cursor movement (CSI A/B/C/D/E/F/G/d/e/H/f) -------------------------

    /// Up `n` rows — CUU, and through it VT52 `ESC A` and CPL — stopping at the top
    /// margin when the cursor is at or below it and at the screen top otherwise.
    fn move_up(&mut self, n: usize) {
        let floor = if self.cursor.row >= self.scroll_top {
            self.scroll_top
        } else {
            0
        };
        self.cursor.row = self.cursor.row.saturating_sub(n).max(floor);
        self.cursor.pending_wrap = false;
    }

    /// Down `n` rows — CUD, and through it VT52 `ESC B` and CNL — stopping at the
    /// bottom margin when the cursor is at or above it and at the screen bottom otherwise.
    fn move_down(&mut self, n: usize) {
        let ceiling = if self.cursor.row <= self.scroll_bottom {
            self.scroll_bottom
        } else {
            self.grid.rows() - 1
        };
        self.cursor.row = (self.cursor.row + n).min(ceiling);
        self.cursor.pending_wrap = false;
    }

    fn move_forward(&mut self, n: usize) {
        self.cursor.col = (self.cursor.col + n).min(self.grid.cols() - 1);
        self.cursor.pending_wrap = false;
    }

    fn move_back(&mut self, n: usize) {
        // Under `?45` this is n applications of the step `BS` takes — xterm's shape
        // literally, where one `CursorBack` serves both verbs and its loop spends one unit
        // of the count per step (`cursor.c:160-190`), so `CSI 3 D` from a park moves two
        // and a walk at column 0 costs one of the three (#873). Off the mode there is
        // neither a walk nor a spend to distribute, so the whole move is one saturating
        // subtraction — the same landing without the loop.
        if self.reverse_wraparound {
            for _ in 0..n {
                self.step_back();
            }
        } else {
            self.cursor.col = self.cursor.col.saturating_sub(n);
        }
        // Both call sites pass at least 1 — `param_or` maps an explicit `CSI 0 D` to the
        // default — so the loop always runs and always puts the flag down. Cleared here
        // anyway rather than relied upon: a zero count must still clear, as every other
        // positioning verb does, and the loop is the only shape in this file where that
        // obligation can be skipped by arithmetic.
        self.cursor.pending_wrap = false;
    }

    fn set_col(&mut self, col: usize) {
        self.cursor.col = col.min(self.grid.cols() - 1);
        self.cursor.pending_wrap = false;
    }

    fn set_row(&mut self, row: usize) {
        self.cursor.row = row.min(self.grid.rows() - 1);
        self.cursor.pending_wrap = false;
    }

    fn goto(&mut self, row: usize, col: usize) {
        let (offset, max_row) = self.addressable_rows();
        self.cursor.row = (row + offset).min(max_row);
        self.cursor.col = col.min(self.grid.cols() - 1);
        self.cursor.pending_wrap = false;
    }

    /// The row addressing origin and the last addressable row. Origin mode
    /// addresses rows relative to the scroll region's top margin and clamps to its
    /// bottom; otherwise rows are absolute to the screen.
    fn addressable_rows(&self) -> (usize, usize) {
        if self.origin_mode {
            (self.scroll_top, self.scroll_bottom)
        } else {
            (0, self.grid.rows() - 1)
        }
    }

    /// VPR (CSI Ps e): the current row plus `n`, positioned as CUP positions a row
    /// — bounded by the last addressable row, not by the scroll margin CUD stops at.
    fn vertical_position_relative(&mut self, n: usize) {
        let (_, max_row) = self.addressable_rows();
        self.cursor.row = (self.cursor.row + n).min(max_row);
        self.cursor.pending_wrap = false;
    }

    // ---- erase (CSI J / K) ---------------------------------------------------

    /// Clear cells `from..to` on `row`.
    ///
    /// Background Color Erase (BCE): erased cells carry the current SGR
    /// background only — fg and text attributes reset to default (matches
    /// xterm/alacritty, where the fill is `cursor.template.bg.into()`).
    ///
    /// **Cleared concern, with its validity condition — an empty range would break the pair
    /// invariant.** With `from == to` the first guard below still frees the lead at `from - 1`
    /// while the second is skipped (`to > from` is false) and the fill loop does nothing, so the
    /// spacer at `from` would survive its lead — an ADR-0025 D4 break, and the exact lead-less
    /// orphan the word walk must then treat as opaque. This is unreachable **as long as every
    /// caller passes a non-empty range**, which holds today: `ECH` clamps to
    /// `(col + n).min(cols)` with `n >= 1` (both `CSI X` and `CSI 0 X` erase one cell), and every
    /// `EL`/`ED` site passes `0..cols` or `0..=cursor`. A future caller that can pass an empty
    /// range must guard here first.
    fn clear_cells(&mut self, row: usize, from: usize, to: usize) {
        let cols = self.grid.cols();
        // Erasing either half of a pair that wrapped from the row above ends it, so that row's
        // artefact record is void (#534). `from <= 1` rather than `from == 0` because erasing from
        // column 1 destroys the spacer and the no-orphan repair below then frees the lead. ghostty
        // reaches the same row from its erase path — `Screen.splitCellBoundary`'s `x == 0 or x ==
        // 1` branch (`Screen.zig:1873` @ `e6e26e1`), called from `eraseChars` (`Terminal.zig:3159`).
        if from <= 1 && to > from && self.wrapped_pair_at_row_start(row) {
            self.void_wrap_artefact_above(row);
        }
        // Don't orphan a wide char straddling the erase boundary.
        if from > 0 && self.grid.cell(row, from).is_wide_spacer() {
            self.free_cell(row, from - 1);
        }
        if to > from && to < cols && self.grid.cell(row, to - 1).is_wide() {
            self.free_cell(row, to);
        }

        let bg = self.cursor.pen.bg;
        for col in from..to {
            let cell = self.grid.cell_mut(row, col);
            cell.reset();
            cell.set_bg(bg);
        }
        // `reset` cleared the presence bits; this releases what they gated (#628).
        self.grid.row_mut(row).purge_side_maps(from..to);
        if to > from {
            self.damage_span(row, from, to - 1);
        }
    }

    /// End `row`'s soft wrap, because something just destroyed the content that was continuing
    /// onto the next row.
    ///
    /// Which verbs owe this is **not** derivable from the erased range — it is a per-verb rule,
    /// and both references spell it out call site by call site rather than inferring it:
    ///
    /// | verb | ends the wrap? | xterm | ghostty |
    /// |---|---|---|---|
    /// | `EL 0` (erase right) | **yes**, at any column | `ClearRight` → `LineClrWrapped` unconditionally (`util.c:1871`) | `cursorResetWrap()` in `eraseLine(.right)` |
    /// | `ECH` | **yes**, at any column | same `ClearRight` (`util.c:1961`) | `cursorResetWrap()` in `eraseChars` |
    /// | `DCH` | **yes** | `screen.c` | `cursorResetWrap()` — *"Our row's soft-wrap is always reset"* |
    /// | `EL 1` (erase left) | no | `ClearLeft`, no clear | no |
    /// | `ICH` | no | no | no |
    /// | a reverse-wrap walk (`BS` / `CSI D` under `?45`) | **no** (#873) | `CursorBack` writes no wrap flag | only *reads* `prev_row.wrap` (`Terminal.zig:1842-1843`) |
    ///
    /// The last row is the one that was wrong. The walk **did** clear the flag — copied from
    /// xterm.js's `line.isWrapped = false` (`InputHandler.ts:823`), which neither other
    /// reference does — and it did so by writing the row directly, so it never appeared in
    /// this table and never took the damage obligation below. Three consequences, all
    /// measured: two buffers with identical cells read as different logical lines depending
    /// on how the cursor arrived, a reflow kept them apart instead of healing it, and the
    /// clear's whole damage was `Partial([])` where `EL 0` through this function reports
    /// `Partial([LineDamage { line: 0, left: 0, right: 2 }])`, so a frame-mode consumer was
    /// left joined where the engine had split.
    /// Undoing the *cursor's* trip across the boundary does not undo the boundary.
    ///
    /// The shape behind the three that do: each destroys content **from the cursor rightward**, so
    /// "this row continues past its last column" can no longer be asserted. Erasing leftward or
    /// inserting blanks leaves the tail — and whatever it flowed into — intact.
    ///
    /// **`EL 2` is a deliberate divergence.** justerm ends the wrap; xterm does not (`ClearLine`,
    /// `util.c:1905`, has no `LineClrWrapped`) and ghostty copies that with a comment naming it —
    /// *"it seems like complete should reset the soft-wrap state of the line but in xterm it does
    /// not."* justerm differs because it *joins* logical lines for `accessible_text` / `search` /
    /// selection text, so a blanked-but-still-wrapped row visibly merges two lines in copy — a
    /// consequence xterm does not carry. Recorded rather than silently matched or silently
    /// Mark `row` as soft-wrapping into the next one — and damage the cell the bit rides on.
    ///
    /// The exact mirror of [`Term::end_wrap`], and it exists for the mirror of that function's
    /// reason. The flag lives on the `Row` (#538) and reaches a consumer only as the last cell's
    /// `WRAPLINE`, derived at encode time. Every other cell-carried fact changes when that cell is
    /// written, so damage covers it for free; this one does not, and a `Partial` frame would never
    /// ship the bit — a frame-mode consumer rebuilding logical lines from cells then keeps the two
    /// rows *split* forever, the exact dual of the "joined forever" that `end_wrap` guards.
    ///
    /// `end_wrap` took that obligation in #540; the set side never did. It stayed invisible because
    /// a wrap normally moves the cursor to the next row, and `frame_damage` tops the frame up with
    /// the old cursor cell. When a **scroll serves the wrap** the cursor keeps its row index, so
    /// nothing tops it up — which is how #557 surfaced it.
    ///
    /// Damaging here rather than at each caller is what keeps this true for set sites added later,
    /// the same argument `end_wrap`'s comment makes.
    fn begin_wrap(&mut self, row: usize) {
        self.grid.row_mut(row).set_wrapped(true);
        let last = self.grid.cols() - 1;
        self.damage_span(row, last, last);
    }

    /// diverged; see #538.
    fn end_wrap(&mut self, row: usize) {
        self.grid.row_mut(row).set_wrapped(false);
        // The flag is stored on the `Row` but rides the wire on the row's **last cell**, derived
        // at encode time. Every other cell-carried fact changes only when that cell is written,
        // so damage covers it for free; this one does not, and a `Partial` frame would never
        // re-ship the bit — leaving a frame-mode consumer with two rows joined forever. Damaging
        // here rather than at each caller is what keeps that true for call sites added later.
        let last = self.grid.cols() - 1;
        self.damage_span(row, last, last);
        // The wrap artefact goes with the wrap. The marker's claim is "the last column is the
        // blank a width-2 glyph vacated **because this row continues onto the next**", so a row
        // that stops continuing cannot hold one (ADR-0025 D3 — position is part of the test, and
        // so is the wrap it is positioned in). Coupling the two here is what makes the row-shift
        // seams and every wrap-ending erase a single rule instead of a clear per verb: ghostty
        // couples them in one function the same way — `Screen.cursorResetWrap`
        // (`terminal/Screen.zig:1524` @ `e6e26e1`, spacer-head clear at `:1539-1545`), reached from
        // `deleteChars` / `eraseChars` / `eraseLine`. It early-returns on `if (!page_row.wrap)`;
        // this one clears unconditionally, which is strictly safer.
        //
        // Most callers erase through this column anyway, so the clear is redundant for them; the
        // ones it is *not* redundant for are the row-shift seams (#540's `shift_region`, which
        // ends a wrap without touching a cell) and `delete_chars`, whose marker rides the shift.
        // The leftward erases are the mirror case — they blank this column while the wrap
        // legitimately survives — and go through `drop_artefact_if_erased` instead.
        //
        // One wrap-ending path deliberately does *not* reach here: `shift_region`'s `top == 0`
        // seam, whose row is in scrollback rather than the grid. It couples the same two clears
        // inline; see the comment there.
        self.grid.cell_mut(row, last).clear_leading_spacer();
    }

    /// The pair that wrapped into `row` is about to be destroyed or moved, so the artefact record
    /// on the row **above** it is void — drop it. **Call before the mutation.**
    ///
    /// The marker makes a claim with two clauses: this row soft-wraps (owned by `end_wrap`), and
    /// its last column is the blank *that specific pair* vacated. This is the second clause, and
    /// the rule behind every call site is one sentence: **the record survives only an in-place
    /// same-width overwrite.** Anything else that reaches columns 0/1 of the continuation — a
    /// narrow write, an erase, a shift in either direction — ends the pair the record was about,
    /// and a wide lead that arrives afterwards by some other route did not *wrap* from anywhere.
    ///
    /// Both references gate on that, and both gate on the state **before** the write rather than
    /// after it:
    ///
    /// - ghostty `Terminal.zig:1484` @ `e6e26e1` — the whole wide-repair `switch` sits under
    ///   `if (cell.wide != wide)`, so a wide glyph overwritten by another wide glyph skips it; the
    ///   reach-back stanza then appears in the `.wide` (`:1501-1506`) and `.spacer_tail`
    ///   (`:1529-1532`) arms only.
    /// - alacritty `term/mod.rs:994` @ `852e971` — the reach-back at `:1004-1008` is inside
    ///   `if cursor_cell.flags.intersects(WIDE_CHAR | WIDE_CHAR_SPACER)`, but with no
    ///   width-unchanged escape, so it drops a record that is still true. Alacritty is the outlier
    ///   of the two and justerm follows ghostty.
    ///
    /// Asking *after* the mutation instead looks equivalent and is not: it answers "is some wide
    /// lead standing at column 0", which a `DCH` that pulls the *next* wide glyph left also
    /// satisfies, and which a two-step placement (a narrow base promoted to wide by VS16 under
    /// mode 2027, or IRM's insert-then-write) satisfies only at the end. Both were measured
    /// disagreeing with the rule above before this took its current form.
    ///
    /// The erase and intra-row-shift call sites are **ported, not derived**: ghostty's
    /// `Screen.splitCellBoundary` (`Screen.zig:1831`, the `x == 0 or x == 1` branch at `:1873`)
    /// reaches up one row and clears the previous row's spacer head, and it is called from
    /// `deleteChars` (`Terminal.zig:3107-3109`) and `eraseChars` (`:3159-3160`). Only justerm's
    /// `ICH` site has no counterpart — ghostty's `insertBlanks` (`:2988`) calls it nowhere.
    ///
    /// `row == 0` does not mean "no row above": on the primary screen the text readers walk
    /// `[scrollback ++ grid]` as one buffer (`abs_floor() == 0`), so the row above grid row 0 is
    /// the last **scrollback** row and it can carry the marker. Alacritty reaches the same row for
    /// the same reason — its `topmost_line()` is `Line(-history_size)` (`grid/mod.rs:504`), so
    /// `point.line - 1` indexes into history; ghostty is the one that stops at the viewport
    /// (`cursor.y > 0`). On the alt screen `abs_floor()` is the screen top, so no join crosses the
    /// boundary and there is nothing to repair.
    ///
    /// No damage is owed by either branch, and for a stronger reason than #540's: the marker is a
    /// `content` bit outside `CONTENT_MARKER_MASK`, so `Cell::flags()` never sees it and it does
    /// not cross the wire at all. The `damage_span` below is defensive, not load-bearing.
    fn void_wrap_artefact_above(&mut self, row: usize) {
        if row > 0 {
            let last = self.grid.cols() - 1;
            if self.grid.cell(row - 1, last).is_leading_spacer() {
                self.grid.cell_mut(row - 1, last).clear_leading_spacer();
                self.damage_span(row - 1, last, last);
            }
        } else if !self.on_alt
            && let Some(cell) = self.scrollback.back_mut().and_then(|r| r.last_mut())
        {
            cell.clear_leading_spacer();
        }
    }

    /// Is a wide pair standing at columns 0..=1 of `row` — i.e. is there a record for
    /// `void_wrap_artefact_above` to void? A cheap pre-mutation test the four call sites share, so
    /// the rule lives in one place rather than being re-derived per verb (ADR-0025 D2).
    fn wrapped_pair_at_row_start(&self, row: usize) -> bool {
        self.grid.cell(row, 0).is_wide()
    }

    /// Drop a wide-wrap artefact marker that has outlived the wrap it belonged to, without
    /// touching the wrap itself.
    ///
    /// The mirror of the marker clean-up inside `end_wrap`, for the verbs that erase *leftward*:
    /// `EL 1` and `ED 1` correctly leave the wrap alone (the row's tail still flows onward), but
    /// they can still clear the last column, and then the artefact's blank turns into visible
    /// text that a reflow bakes in permanently. Only the marker goes; the wrap is the caller's
    /// business.
    fn drop_artefact_if_erased(&mut self, row: usize, from: usize, to: usize) {
        let last = self.grid.cols() - 1;
        if from <= last && to > last {
            self.grid.cell_mut(row, last).clear_leading_spacer();
        }
    }

    /// Shift `[top..=bottom]` by one line — up unless `down` — and end the wraps the shift
    /// falsified. Every row-shifting verb (IL/DL/SU/SD and the region paths in LF/RI) goes
    /// through here so the repair cannot be forgotten at a call site (ADR-0025 D2).
    ///
    /// The wrap flag claims "this row continues into the **next** row", so it is a statement about
    /// *adjacency*, and rotating whole `Row`s keeps it true for free: both halves of a pair inside
    /// the region move by the same line, so the claim still describes the same neighbour. Only the
    /// two seams falsify it, where a row's next neighbour changed underneath it:
    ///
    /// - **`top - 1`**, just outside the region. Its continuation rotated away (up-shift) or was
    ///   pushed down (down-shift), so whatever now sits at `top` is a stranger. This is the seam
    ///   that merges two unrelated logical lines in copy/search/accessible text (#540's repro).
    /// - **the row that lost its continuation to the blank** — `bottom - 1` after an up-shift (the
    ///   blank lands at `bottom`), `bottom` after a down-shift (its continuation rotated up to
    ///   `top` and was blanked there). The down-shift form is the one that reaches *outside* the
    ///   region: the stale claim points at `bottom + 1`, a row the verb never touched.
    ///
    /// Damaging matters as much as clearing, and `end_wrap` does both: `top - 1` is outside the
    /// region, so the scroll op the caller records does not cover it and a `Partial` frame would
    /// never re-ship the derived `WRAPLINE` bit.
    ///
    /// **Each seam has exactly one exemption, and both are facts about the caller that this
    /// function cannot see** — which is why they are parameters rather than tests:
    ///
    /// - `evicts_to_scrollback` exempts the **top** seam: a linefeed pushes row 0 into scrollback,
    ///   so the readers' `[scrollback ++ grid]` walk finds the continuation one row further back
    ///   and adjacency survives.
    /// - `serves_wrap` exempts the **bottom** seam: the shift was asked for by `wrapline`, so the
    ///   blank it exposes at `bottom` is not a stranger that displaced a continuation — it *is*
    ///   the continuation, about to be written into (#557).
    ///
    /// Both are one-sided on purpose. A wrap-serving scroll still falsifies the top seam, and a
    /// scrollback-evicting linefeed still falsifies the bottom one when no wrap asked for it.
    ///
    /// **No reference implements this rule**, so it is derived rather than ported — ADR-0004, the
    /// spec is the authority for VT semantics, above any implementation:
    ///
    /// - **ghostty** clears the wrap on *every* row a full-width IL/DL touches
    ///   (`terminal/Terminal.zig:2746-2752`, `:2906-2912` @ `e6e26e1`). The clear runs *before* the
    ///   row swap at `:2936-2939`, so both ends stay false: an interior pair is split, not
    ///   preserved. It still never reaches the row above the shifted range.
    /// - **alacritty** has no `WRAPLINE` clear on any scroll path (@ `852e971`).
    /// - **xterm.js** splices whole line objects and never touches `isWrapped`
    ///   (`common/InputHandler.ts:1345-1402` @ `699f553`). Its opposite polarity — "I continue the
    ///   *previous* row" (`common/buffer/Buffer.ts:566-570`) — moves the exposure to the mirrored
    ///   seam rather than removing it: a spliced-in line keeps a continuation claim about a
    ///   predecessor it never met.
    ///
    /// The seam row's wide-wrap *marker* is the same shift's other half, and it now rides along:
    /// `end_wrap` clears both (#534), and the `top == 0` branch below — the one seam whose row is
    /// not a grid row — couples them inline for the same reason.
    ///
    /// **Validity condition for clearing at the seams rather than everywhere.** ghostty clears the
    /// wrap and the spacer head on *every* row a full-width IL/DL touches, and its own comment
    /// gives two reasons: it splits interior pairs, **and** it supports left/right margins
    /// (DECSLRM), where a partial-row shift can break an interior pair without moving its
    /// neighbour. justerm rotates whole `Row`s and implements no DECSLRM, so an interior pair and
    /// its continuation always move together and seam-only is sound. If left/right margins ever
    /// land, this rule and #534's marker rule break at the same time — neither is safe under a
    /// shift that moves part of a row.
    fn shift_region(
        &mut self,
        top: usize,
        bottom: usize,
        down: bool,
        evicts_to_scrollback: bool,
        serves_wrap: bool,
    ) {
        if down {
            self.grid.scroll_down_region(top, bottom);
        } else {
            self.grid.scroll_up_region(top, bottom);
        }
        // Recording the scroll op is part of shifting, not a step a caller adds after: damage is
        // indexed by row position, so `record_scroll` rotates `line_damage` with the content. A
        // seam clear damaged *before* that rotation is carried to the wrong row — and on a
        // down-shift it lands on `top`, which `record_scroll` immediately overwrites with
        // `fully_damaged`. The clear then never reaches the wire at all: the model splits the
        // rows, a `Partial` frame does not say so, and the consumer keeps them joined forever.
        // Ordering it here is what makes that unrepeatable at a sixth call site.
        self.record_scroll(top, bottom, if down { -1 } else { 1 });
        if top > 0 {
            self.end_wrap(top - 1);
        } else if !evicts_to_scrollback && !self.on_alt {
            // `top == 0` does not mean "no row above": on the primary the text readers walk
            // `[scrollback ++ grid]` as one buffer (`abs_floor() == 0`), so the row above grid row
            // 0 is the last *scrollback* row and it can wrap into the screen. A full-screen SU /
            // DL / RI therefore leaves this issue's defect one row higher, outside the grid.
            //
            // `evicts_to_scrollback` is what keeps `linefeed` out: it pushes grid row 0 into
            // scrollback, so the continuation is re-attached one row further back and the claim
            // stays true — clearing there would split a line the scroll preserved. On the alt
            // screen `abs_floor()` is the screen top, so no join crosses the boundary at all.
            //
            // No damage is owed with the clear, unlike `end_wrap`'s grid form: a scrollback row
            // only reaches the wire while `display_offset > 0`, and there `damage()` returns an
            // empty `Partial` (`term.rs`, the frozen-viewport short-circuit) while any scroll that
            // *moves* the viewport marks full damage. Valid as long as that short-circuit holds.
            //
            // The artefact marker goes with the wrap here exactly as it does in `end_wrap`, and
            // this branch is the reason that coupling cannot simply live in `end_wrap`: it is the
            // one wrap-ending path whose row is not a grid row, so it does not call it. Leaving it
            // out left #534's defect alive one row above the grid — reachable from every
            // `scroll_region_lines` verb, since all of them pass `evicts_to_scrollback: false`,
            // and visible as a word selection one cell too wide plus a reflow that bakes the
            // stranded marker mid-row.
            if let Some(row) = self.scrollback.back_mut() {
                row.set_wrapped(false);
                if let Some(cell) = row.last_mut() {
                    cell.clear_leading_spacer();
                }
            }
        }
        // The blank lands at `bottom` going up and at `top` going down, so the row that lost its
        // continuation is the one just above it. Going down that is `top - 1`, already cleared
        // above; going up it is `bottom - 1`, which for a one-row region is that same row.
        //
        // The up-shift form needs the `bottom + 1` guard, and it is not defensive — without it the
        // clear destroys a **live** wrap. A row at the screen's bottom edge that wraps is the
        // ordinary soft-wrap-at-the-last-row state: `wrapline` sets the flag and the linefeed
        // scrolls precisely so the continuation has somewhere to land, which is the *next* row
        // after this shift. Its claim is about a row that does not exist yet, so the shift makes it
        // true rather than false.
        //
        // **The rest of that guard's original rationale was too narrow, and #557 is what it cost.**
        // It read: *"the link is only broken when there is a stationary row below the region
        // (`bottom + 1 < rows`): then the continuation stayed put while its lead moved up."* A
        // stationary row below is **necessary but not sufficient**. At a *region's* bottom the same
        // wrapline-asked-for scroll happens with `bottom + 1 < rows` perfectly true, and the clear
        // then split the logical line the scroll existed to continue. The geometry was never the
        // discriminator; **why the shift is happening** is — which is what `serves_wrap` carries.
        //
        // The guard stays anyway: it is the screen-bottom case of the same fact, and it also holds
        // for a *non*-wrap-serving linefeed at the screen edge.
        //
        // One invariant is still worth naming, because it was not true when this guard was first
        // written: **a row only claims a wrap if a next row will exist for it**. A row parked below
        // a DECSTBM region kept a permanent false claim, and this guard preserved it — the #540
        // completeness pass merged two unrelated logical lines through exactly that hole. The claim
        // is now gated at its set site (`write_glyph` asks `wrapline_advances`), so the guard's
        // premise holds. Valid as long as that gate stays.
        let orphaned = if serves_wrap {
            // The blank this shift just exposed is the continuation the wrap is waiting for, so
            // there is nothing to falsify — see the `serves_wrap` note on `linefeed_inner` (#557).
            None
        } else if down {
            Some(bottom)
        } else if bottom + 1 < self.grid.rows() {
            bottom.checked_sub(1)
        } else {
            None
        };
        if let Some(row) = orphaned {
            self.end_wrap(row);
        }
    }

    fn erase_display(&mut self, mode: u16) {
        let (cols, rows) = (self.grid.cols(), self.grid.rows());
        let (cr, cc) = (self.cursor.row, self.cursor.col);
        match mode {
            0 => {
                // Erases this row's tail and every row below, so nothing can continue from here
                // — and the rows below cannot continue either.
                self.clear_cells(cr, cc, cols);
                self.end_wrap(cr);
                for row in (cr + 1)..rows {
                    self.clear_cells(row, 0, cols);
                    self.end_wrap(row);
                    self.dispose_markers_on_row(row);
                }
            }
            1 => {
                // Leftward: this row's tail survives, so its own wrap does. The rows *above* are
                // gone entirely.
                for row in 0..cr {
                    self.clear_cells(row, 0, cols);
                    self.end_wrap(row);
                    self.dispose_markers_on_row(row);
                }
                self.clear_cells(cr, 0, cc + 1);
                self.drop_artefact_if_erased(cr, 0, cc + 1);
                // Covering the whole row means nothing continues from it. xterm.js has a
                // dedicated arm for exactly this case, in its own words: *"Deleted entire
                // previous line. This next line can no longer be wrapped."*
                // (`InputHandler.ts:1248-1252` — under its continuation polarity that assignment
                // is this engine's `end_wrap(cr)`.) `EL 1` has no such arm there, and none here.
                if cc + 1 == cols {
                    self.end_wrap(cr);
                }
            }
            2 => {
                for row in 0..rows {
                    self.clear_cells(row, 0, cols);
                    self.end_wrap(row);
                    self.dispose_markers_on_row(row);
                }
            }
            // xterm's addition: erase saved lines. The screen and the cursor are untouched.
            3 => self.erase_history(),
            _ => {}
        }
    }

    /// Drop every scrollback line — `ED 3`, and the first step of [`Term::clear`]
    /// (#936). The lines leave the *front* of the buffer, so every holder of an
    /// absolute line is repaired exactly as the scrollback cap repairs it, `n` lines
    /// at once: the selection clamps, markers and tracked points on the dropped lines
    /// go, search highlights are dropped, and `evicted_total` advances by `n`. The
    /// view returns to the bottom, since the history it was showing is gone.
    ///
    /// On the alt screen it drops the primary's history underneath, as xterm does;
    /// every alt line sits above the dropped ones, so its holders only shift.
    fn erase_history(&mut self) {
        let n = self.scrollback.len();
        if n == 0 {
            return;
        }
        self.scrollback.clear();
        self.lines_left_the_front(n);
        self.display_offset = 0;
        self.mark_fully_damaged();
    }

    /// Repair every holder of an absolute line after `n` lines left the front of the
    /// buffer — the one funnel for the scrollback cap (one line per linefeed), `ED 3` and
    /// [`Term::clear`]. Every absolute index shifted by exactly `n`, which is what makes
    /// this class of movement expressible as a scalar (#490): `evicted_total` counts it
    /// here, because the fact is about the *buffer*, not about any one holder.
    ///
    /// **Scope, because the name `evicted_total` over-promises.** Reflow also drops lines
    /// off the front (`PaneReflow::evicted`, installed by replacing the deque) and does
    /// not come through here: it moves the survivors non-uniformly, so no delta repairs
    /// them and `marker_epoch` signals it instead. A holder rebasing off this number
    /// *without* also watching the epoch gets a wrong answer across every resize.
    ///
    /// The holders, each with its own answer: the selection re-anchors (its ends keep
    /// their content); query-derived search highlights cannot survive the shift and are
    /// dropped; markers shift and those on a dropped line are disposed and announced
    /// (#118); tracked points shift and those on a dropped line go (#691). The view is
    /// the caller's, because the cap keeps it on the same content and `ED 3` returns it.
    fn lines_left_the_front(&mut self, n: usize) {
        self.evicted_total += n as u64;
        self.selection_evict_oldest(n);
        self.invalidate_search_highlights();
        self.markers_evict_oldest(n);
        self.tracked_evict_oldest(n);
    }

    /// Clear the primary screen and its scrollback, keeping the cursor's line
    /// — a terminal's Clear command, out of band: the parser and whatever it
    /// holds mid-sequence are untouched. The cursor's logical line, from its first
    /// row on screen down to the cursor's row, moves to the top with the cursor on it
    /// at the same column; the rows above it and all of history are dropped, and the
    /// rows below the cursor are blanked. The view returns to the bottom and the next
    /// frame is `Full`.
    ///
    /// The selection and the search highlights are cleared. A marker on a kept row
    /// stays on it; every other marker is disposed and announced. Tracked points on
    /// dropped lines go; the rest shift with the kept rows.
    ///
    /// Returns `false` and changes nothing on the alt screen.
    pub fn clear(&mut self) -> bool {
        if self.on_alt {
            return false;
        }
        let (cols, cursor) = (self.grid.cols(), self.cursor.row);
        // The kept line is the cursor's whole logical line up to the cursor, so a prompt
        // and a command that wrapped keep their start — as far up as the screen reaches.
        let mut top = cursor;
        while top > 0 && self.grid.is_row_wrapped(top - 1) {
            top -= 1;
        }
        // Move the rows above it into history, so dropping history takes them too: their
        // absolute lines are unchanged by the move, so no holder moves.
        for _ in 0..top {
            let row = self.grid.scroll_up_recycle(Row::blank(cols));
            self.scrollback.push_back(row);
        }
        let last = cursor - top;
        self.cursor.row = last;
        self.erase_history();
        self.selection = None;
        self.invalidate_search_highlights();
        for row in last + 1..self.grid.rows() {
            let blanked = self.grid.row_mut(row);
            blanked.blank_in_place();
            blanked.purge_side_maps(0..cols);
            self.dispose_markers_on_row(row);
        }
        // Nothing follows the cursor's row now, so it cannot continue onto the next row.
        self.end_wrap(last);
        // `REP` reads back the cell the last print wrote. That cell is on the cursor's row
        // whenever the anchor is armed, so it moves up with it; anywhere else it is gone.
        self.repeat_anchor = self
            .repeat_anchor
            .filter(|&(row, _)| row == cursor)
            .map(|(_, col)| (last, col));
        self.scroll = None;
        self.mark_fully_damaged();
        true
    }

    /// Erase in line (EL): 0 = cursor→end, 1 = start→cursor, 2 = whole line.
    fn erase_line(&mut self, mode: u16) {
        let cols = self.grid.cols();
        let (cr, cc) = (self.cursor.row, self.cursor.col);
        match mode {
            // Erase right — ends the wrap at any column (xterm's `ClearRight`).
            0 => {
                self.clear_cells(cr, cc, cols);
                self.end_wrap(cr);
            }
            // Erase left — the tail survives, so the wrap does. The artefact marker does not:
            // if the erase reached the last column it just blanked the cell the marker described.
            1 => {
                self.clear_cells(cr, 0, cc + 1);
                self.drop_artefact_if_erased(cr, 0, cc + 1);
            }
            // Erase the whole line — see `end_wrap`: a deliberate divergence from xterm.
            2 => {
                self.clear_cells(cr, 0, cols);
                self.end_wrap(cr);
            }
            _ => {}
        }
    }

    // ---- intra-line editing (ICH / DCH / ECH) --------------------------------

    /// ECH (CSI Pn X): erase `n` cells in place from the cursor — no shift.
    /// BCE-filled (via `clear_cells`); pending-wrap is left untouched.
    fn erase_chars(&mut self, n: usize) {
        let cols = self.grid.cols();
        let (row, col) = (self.cursor.row, self.cursor.col);
        let to = (col + n).min(cols);
        self.clear_cells(row, col, to);
        // Destroys content from the cursor rightward, so the row can no longer be continuing —
        // unconditionally, at any column and for any `n`. Both references do exactly this (see
        // `end_wrap`): xterm routes ECH through the same `ClearRight` as `EL 0`, ghostty calls
        // `cursorResetWrap()` in `eraseChars`.
        self.end_wrap(row);
    }

    /// ICH (CSI Pn @): insert `n` blanks at the cursor, shifting the rest of the
    /// line right; cells pushed past the right edge are lost. The opened gap is
    /// BCE-filled; pending-wrap is left untouched.
    fn insert_chars(&mut self, n: usize) {
        let cols = self.grid.cols();
        let (r, col) = (self.cursor.row, self.cursor.col);
        let n = n.min(cols - col);
        if n == 0 {
            return;
        }
        // Shifting a wrapped pair out of columns 0/1 ends it, so the row above's artefact record
        // is void (#534). Asked **before** the shift, which is what keeps IRM correct: `write_glyph`
        // routes its wide-at-boundary insert through here *after* `vacate_for_wrap` has just set
        // the marker on the row above, and a post-shift test would see the freshly blanked gap and
        // clear the marker inside its own SET site's critical section. Pre-shift the question is
        // about the pair that was actually there, which is the one the record is about.
        if col <= 1 && self.wrapped_pair_at_row_start(r) {
            self.void_wrap_artefact_above(r);
        }
        let bg = self.cursor.pen.bg;
        let row = self.grid.row_mut(r);
        // Shift [col .. cols-n) right by n; the tail falls off the edge. The
        // combining map follows the moved cells (the bit travels with the raw
        // copy, the cluster data must too).
        row.copy_within(col..cols - n, col + n);
        row.move_maps(col..cols - n, col + n);
        for cell in &mut row[col..col + n] {
            cell.reset();
            cell.set_bg(bg);
        }
        // Repair wide-char halves split at the seams (no-orphan invariant):
        // a lead just before the gap lost its spacer; the first shifted cell may
        // be a spacer whose lead did not move.
        if col > 0 && self.grid.cell(r, col - 1).is_wide() {
            self.free_cell(r, col - 1);
        }
        if col + n < cols && self.grid.cell(r, col + n).is_wide_spacer() {
            self.free_cell(r, col + n);
        }
        // A lead shifted to the last column lost its spacer off the edge.
        if self.grid.cell(r, cols - 1).is_wide() {
            self.free_cell(r, cols - 1);
        }
        // Note ICH needs no repair to *this* row's marker: a right shift always pushes the last
        // column off the edge, so it discards a marker rather than carrying one inward —
        // measured, and pinned by `ich_discards_the_marker_off_the_edge`.
        self.damage_span(r, col, cols - 1);
    }

    /// DCH (CSI Pn P): delete `n` cells at the cursor, shifting the tail left; the
    /// vacated cells at the right are BCE-blanked. Pending-wrap is left untouched.
    fn delete_chars(&mut self, n: usize) {
        let cols = self.grid.cols();
        let (r, col) = (self.cursor.row, self.cursor.col);
        let n = n.min(cols - col);
        if n == 0 {
            return;
        }
        // The shift pulls the tail left and blanks the far end, so the row stops continuing —
        // ghostty says it outright (*"Our row's soft-wrap is always reset"* in `deleteChars`,
        // `Terminal.zig:3133` @ `e6e26e1`).
        //
        // **Before the shift, not after** (#534): `end_wrap` clears the artefact marker at the
        // *last* column, and the marker is a cell bit that the shift carries inward with every
        // other cell. Ending the wrap afterwards would clear a column the marker has already left,
        // stranding it mid-row where it describes nothing (ADR-0025 D3) and silently swallows the
        // blank between two runs in copy, search and accessible text. Same shape as #540's
        // `record_scroll` ordering: the clear has to happen where the state still is.
        self.end_wrap(r);
        // Deleting a wrapped pair out of columns 0/1 ends it, so the row above's artefact record
        // is void — and this is where the "ask before, not after" rule earns its keep twice over:
        // a `DCH` can pull the *next* wide glyph left into column 0, which a post-shift "is a wide
        // lead standing here?" test happily accepts even though the pair the record was about has
        // been deleted. ghostty asks the same question at the same point:
        // `Screen.splitCellBoundary(cursor.x)` from `deleteChars` (`Terminal.zig:3107` @ `e6e26e1`),
        // whose `x == 0 or x == 1` branch reaches up a row and clears the spacer head.
        if col <= 1 && self.wrapped_pair_at_row_start(r) {
            self.void_wrap_artefact_above(r);
        }
        let bg = self.cursor.pen.bg;
        let row = self.grid.row_mut(r);
        // Shift [col+n .. cols) left to [col ..); BCE-fill the vacated tail. The
        // combining map follows the moved cells.
        row.copy_within(col + n..cols, col);
        row.move_maps(col + n..cols, col);
        for cell in &mut row[cols - n..cols] {
            cell.reset();
            cell.set_bg(bg);
        }
        // Repair wide-char halves split by the deletion (no-orphan invariant):
        // a lead just before the cut lost its spacer; the cell now at the cursor
        // may be a spacer whose lead was deleted.
        if col > 0 && self.grid.cell(r, col - 1).is_wide() {
            self.free_cell(r, col - 1);
        }
        if self.grid.cell(r, col).is_wide_spacer() {
            self.free_cell(r, col);
        }
        self.damage_span(r, col, cols - 1);
    }

    // ---- line/region editing (IL / DL / SU / SD) -----------------------------

    /// Scroll rows `[top..=bottom]` by `n` lines, BCE-filling the exposed lines.
    /// `down` inserts blanks at the top (content moves down); otherwise content
    /// moves up and blanks appear at the bottom. Reuses the one-line region scroll
    /// primitives (so damage + scroll-op accumulation come for free), then fills
    /// the exposed lines with the current SGR background.
    fn scroll_region_lines(&mut self, top: usize, bottom: usize, n: usize, down: bool) {
        let height = bottom - top + 1;
        let n = n.min(height);
        if n == 0 {
            return;
        }
        // Anchors (selection #3, markers #118/#158) live at absolute buffer lines;
        // SU/SD/IL/DL don't accrue scrollback, so `base` is stable across the loop.
        let base = self.scrollback.len();
        for _ in 0..n {
            self.shift_region(top, bottom, down, false, false);
            // Rotate anchors with the content, like `linefeed`/`reverse_index`
            // (#162). `up` = content moved up = the non-`down` case. Markers rotate
            // with the active buffer (#187) — alt-scoped on the alt screen, so no
            // guard. **The selection is unguarded here for the same reason, not because
            // "it is cleared on alt enter"** — that was this comment's claim until #660 and
            // it is false: a selection made while the alt screen is up is ordinary, it does
            // reach this line, and rotating it is correct, because the content really did
            // move under it. The code was right; only its stated reason was wrong.
            self.selection_rotate_region(base + top, base + bottom, !down);
            self.markers_rotate_region(base + top, base + bottom, !down);
            self.tracked_rotate_region(base + top, base + bottom, !down);
        }
        self.invalidate_search_highlights();
        // BCE-fill the n exposed lines (the primitives blank to default).
        let bg = self.cursor.pen.bg;
        let (fill_top, fill_end) = if down {
            (top, top + n)
        } else {
            (bottom + 1 - n, bottom + 1)
        };
        let cols = self.grid.cols();
        for r in fill_top..fill_end {
            for c in 0..cols {
                let cell = self.grid.cell_mut(r, c);
                cell.reset();
                cell.set_bg(bg);
            }
        }
    }

    /// SU (CSI Pn S): scroll the scroll region up by `n`.
    fn scroll_up_lines(&mut self, n: usize) {
        self.scroll_region_lines(self.scroll_top, self.scroll_bottom, n, false);
    }

    /// SD (CSI Pn T): scroll the scroll region down by `n`.
    fn scroll_down_lines(&mut self, n: usize) {
        self.scroll_region_lines(self.scroll_top, self.scroll_bottom, n, true);
    }

    /// IL (CSI Pn L): insert `n` blank lines at the cursor, scrolling
    /// `[cursor..=scroll_bottom]` down. A no-op when the cursor is outside the
    /// scroll region.
    fn insert_lines(&mut self, n: usize) {
        let cur = self.cursor.row;
        if cur < self.scroll_top || cur > self.scroll_bottom {
            return;
        }
        // 3-1 for clearing, and the odd one out is the row-shift family's usual
        // outlier: xterm `util.c:1295`, ghostty `Terminal.zig:2691` (*"Always unset
        // pending wrap"*), and xterm.js structurally — `insertLines` opens with
        // `_restrictCursor()`, whose `Math.min(cols - 1, …)` un-parks the column
        // (`InputHandler.ts:1346`, `:890`). Only alacritty leaves it.
        //
        // `SU`/`SD` deliberately do **not** join them: ghostty saves and restores the
        // flag around those two on purpose (`Terminal.zig:2390`), so this is a
        // per-verb answer and not "row-shift verbs clear" (#848).
        self.cursor.pending_wrap = false;
        self.scroll_region_lines(cur, self.scroll_bottom, n, true);
    }

    /// DL (CSI Pn M): delete `n` lines at the cursor, scrolling
    /// `[cursor..=scroll_bottom]` up. A no-op when the cursor is outside the
    /// scroll region.
    fn delete_lines(&mut self, n: usize) {
        let cur = self.cursor.row;
        if cur < self.scroll_top || cur > self.scroll_bottom {
            return;
        }
        // Same 3-1 as `Term::insert_lines`; xterm `util.c:1388`, ghostty
        // `Terminal.zig:2856`, xterm.js `InputHandler.ts:1380` via `_restrictCursor`.
        self.cursor.pending_wrap = false;
        self.scroll_region_lines(cur, self.scroll_bottom, n, false);
    }

    // ---- SGR (CSI m) ---------------------------------------------------------

    fn sgr(&mut self, params: &Params) {
        let pen = &mut self.cursor.pen;
        let mut iter = params.iter();
        while let Some(param) = iter.next() {
            let code = param.first().copied().unwrap_or(0);
            match code {
                0 => pen.reset(),
                1 => pen.flags.insert(CellFlags::BOLD),
                2 => pen.flags.insert(CellFlags::DIM),
                3 => pen.flags.insert(CellFlags::ITALIC),
                // SGR 4 and its colon sub-parameter form (#829). The sub-parameter is already
                // here — `params.iter()` yields the whole `&[u16]` and every other arm reads only
                // `first()` — so `4:3` has been arriving as `[4, 3]` and being truncated to a
                // plain underline. `4:0` is an explicit off in every reference that implements
                // the form. An unrecognised sub-style stays a single underline: three of the four
                // references degrade that way (xterm is the outlier and swallows the whole
                // parameter), and losing an underline entirely is a worse failure than drawing the
                // wrong kind — the application asked for emphasis and would get nothing, with no way
                // to tell. #830 confirmed that rule against the corpus rather than changing it.
                //
                // Every value is stored **and every value is now drawn** (#830). #829 stored all six
                // while the shader branched on `Curly` alone, because storing and drawing are not
                // symmetric in cost: storing 2/4/5 was three arms and no pixel, while NOT storing
                // them was a loss #830 could not have repaired — a cell written `4:5m` and scrolled
                // into history would have recorded `Single` forever.
                4 => {
                    let style = match param.get(1) {
                        None | Some(1) => UnderlineStyle::Single,
                        Some(0) => UnderlineStyle::None,
                        Some(2) => UnderlineStyle::Double,
                        Some(3) => UnderlineStyle::Curly,
                        Some(4) => UnderlineStyle::Dotted,
                        Some(5) => UnderlineStyle::Dashed,
                        Some(_) => UnderlineStyle::Single,
                    };
                    pen.flags.set_underline_style(style);
                }
                5 => pen.flags.insert(CellFlags::BLINK),
                7 => pen.flags.insert(CellFlags::INVERSE),
                8 => pen.flags.insert(CellFlags::HIDDEN),
                9 => pen.flags.insert(CellFlags::STRIKETHROUGH),
                // The legacy double underline (#830), which predates the sub-parameter form above.
                // It lands on the same field, so `24` clears both spellings — ghostty gets that by
                // construction (4, 4:x, 21 and 24 all reduce to one variant on one arm,
                // `Screen.zig:2269-2271`) where xterm leaves two independent bits set and lets each
                // consumer resolve them (`html.c:208-216` against `svg.c:271`).
                //
                // **Decided by the spec, not by a head count**, because the corpus is not
                // unanimous: `vte` — the crate this engine's own parser is built on — reads `[21]`
                // as `CancelBold` (`vte-0.15.0/src/ansi.rs:1849`), so alacritty produces no double
                // underline from it at all. `ctlseqs.txt:1200` reads *"Doubly-underlined, ECMA-48
                // 3rd"*, and the VT tie-breaker puts the spec above any implementation including
                // ours; xterm (`charproc.c:4407-4409`), ghostty (`sgr.zig:301`) and xterm.js
                // (`InputHandler.ts:2653-2655`) all agree. A reference that *contradicts* rather
                // than omits is the third case ADR-0004's text does not classify — #824 settled
                // that routing for DA2 and it applies unchanged here.
                //
                // The consequence, pinned rather than left to a bug report: an application sending
                // `CSI 1m` then `CSI 21m` **meaning "stop bold"** gets a double underline and keeps
                // its bold. That is what `22` is for, and this arm deliberately does not touch it.
                21 => pen.flags.set_underline_style(UnderlineStyle::Double),
                22 => pen.flags.remove(CellFlags::BOLD | CellFlags::DIM),
                23 => pen.flags.remove(CellFlags::ITALIC),
                // Clears the style, not just the derived flag (#829) — removing `UNDERLINE` alone
                // would leave a styled-but-not-underlined pen, the disagreement this model exists
                // to make unrepresentable.
                24 => pen.flags.set_underline_style(UnderlineStyle::None),
                25 => pen.flags.remove(CellFlags::BLINK),
                27 => pen.flags.remove(CellFlags::INVERSE),
                28 => pen.flags.remove(CellFlags::HIDDEN),
                29 => pen.flags.remove(CellFlags::STRIKETHROUGH),
                30..=37 => pen.fg = Color::Indexed((code - 30) as u8),
                38 => {
                    if let Some(c) = parse_extended_color(param, &mut iter) {
                        pen.fg = c;
                    }
                }
                39 => pen.fg = Color::Default,
                40..=47 => pen.bg = Color::Indexed((code - 40) as u8),
                48 => {
                    if let Some(c) = parse_extended_color(param, &mut iter) {
                        pen.bg = c;
                    }
                }
                49 => pen.bg = Color::Default,
                // Underline colour (SGR 58 / 59, #520) — same extended-colour grammar
                // as 38/48 (colon `58:2:r:g:b` / `58:5:n`, or legacy semicolon), so it
                // reuses `parse_extended_color` verbatim. 59 returns to "follow the fg".
                58 => {
                    if let Some(c) = parse_extended_color(param, &mut iter) {
                        pen.underline_color = c;
                    }
                }
                59 => pen.underline_color = Color::Default,
                // bright foreground/background (aixterm) → palette 8..=15.
                90..=97 => pen.fg = Color::Indexed((code - 90 + 8) as u8),
                100..=107 => pen.bg = Color::Indexed((code - 100 + 8) as u8),
                _ => {}
            }
        }
    }
}

/// Cap a recorded scroll to what a consumer can act on **and** what the wire can
/// carry (#661) — two bounds for two different reasons, see [`Term::scroll_delta`].
///
/// A free function so the second bound is provable without building the grid that
/// reaches it: a region taller than `i16::MAX` means a screen taller than 32 767
/// rows, and every scroll of it rotates a `line_damage` of that length, so driving
/// the engine to that corner costs ~10⁹ element moves (measured: 16 s in a debug
/// build, for one assertion). The engine-level tests in `tests/damage.rs` prove
/// `scroll_delta` applies this at ordinary sizes; the wire-level one in
/// `tests/serialize.rs` proves a count at the bound survives `encode`.
fn cap_scroll(op: ScrollOp) -> ScrollOp {
    let height = op.bottom.saturating_sub(op.top).saturating_add(1) as isize;
    let bound = height.min(MAX_SCROLL_COUNT);
    ScrollOp {
        count: op.count.clamp(-bound, bound),
        ..op
    }
}

/// Parse `38`/`48`/`58` extended colour (foreground / background / underline colour, #520), in
/// either form:
/// - sub-parameter (colon) form inline in `param`: `38:5:n`, `38:2:r:g:b`
///   (optionally `38:2:cs:r:g:b` with a colorspace id), or
/// - legacy (semicolon) form: pull the following top-level params from `iter`.
///
/// The colon RGB form is **count-based** (`off = if param.len() >= 6 { 3 } else { 2 }`): a 5-param
/// `38:2:r:g:b` (no colorspace slot) reads RGB(r,g,b) directly, while a 6-param `38:2:cs:r:g:b` — or
/// `38:2::r:g:b` with an *empty* cs, the form kitty/nvim actually emit — skips the colorspace slot.
/// The short 5-param form is **non-conformant to T.416 / ISO-8613-6** (the de-jure standard always
/// carries a colorspace field), but tolerating it is the **ecosystem-dominant** behaviour, verified
/// against real source (2026-07, #520): VTE (`src/sgr.hh`, branches on `n > 4`), foot (`csi.c`,
/// `sub.idx >= 5`) and alacritty (`ansi.rs`, `params.len() > 4`) all count the sub-parameters and
/// decode the short form as RGB(r,g,b), exactly as here. VTE's own comment calls it a "common
/// misinterpretation of the standard" (foot: "bastard version") that it supports anyway; **only
/// xterm.js is strict** (always consumes a colorspace slot, so it misreads the short form). So a
/// difference from xterm here is deliberate leniency shared with the non-xterm ecosystem, not a
/// defect — the ADR-0004 spec-faithfulness is about not *omitting* behaviour, not about rejecting a
/// widely-emitted non-standard input.
fn parse_extended_color<'a, I>(param: &[u16], iter: &mut I) -> Option<Color>
where
    I: Iterator<Item = &'a [u16]>,
{
    if param.len() > 1 {
        // Colon sub-parameter form: kind is param[1].
        match param[1] {
            2 => {
                // 38:2:r:g:b (len 5) or 38:2:cs:r:g:b (len 6, colorspace skipped).
                let off = if param.len() >= 6 { 3 } else { 2 };
                let r = *param.get(off)? as u8;
                let g = *param.get(off + 1)? as u8;
                let b = *param.get(off + 2)? as u8;
                Some(Color::Rgb(r, g, b))
            }
            5 => Some(Color::Indexed(*param.get(2)? as u8)),
            _ => None,
        }
    } else {
        // Legacy semicolon form: kind, then its operands, are separate params.
        match iter.next()?.first().copied()? {
            2 => {
                let r = iter.next()?.first().copied()? as u8;
                let g = iter.next()?.first().copied()? as u8;
                let b = iter.next()?.first().copied()? as u8;
                Some(Color::Rgb(r, g, b))
            }
            5 => Some(Color::Indexed(iter.next()?.first().copied()? as u8)),
            _ => None,
        }
    }
}

/// Reflow one screen (joined with its `scrollback`) to `cols` x `rows`, tracking
/// `point` (a cursor in screen coordinates). Returns the new screen rows, the new
/// scrollback (capped to `limit`), and the new point. The alt screen passes an
/// empty scrollback and discards the returned one.
/// The fixed dimensions a resize reflows toward.
#[derive(Clone, Copy)]
struct ReflowDims {
    old_cols: usize,
    cols: usize,
    rows: usize,
    limit: usize,
    /// Whether a column change may **re-split** this pane's content, or only re-fit its rows.
    ///
    /// False for the alt screen (#567). Reflow re-splits a long line so history stays readable at
    /// the new width — it assumes the content is text that *flows*. The alt screen has no history,
    /// its content is a **layout** rather than a paragraph (re-wrapping htop's columns means
    /// nothing), and the application already knows the new size and repaints. All three references
    /// take the same position with the same shape — one flag on the same resize function:
    /// ghostty `alt.resize(.{ .reflow = false })`, alacritty `grid.resize(!is_alt, …)`, xterm.js
    /// gating on `_hasScrollback` with the alt buffer built as `new Buffer(false, …)`.
    ///
    /// It is not merely wasted work: measured on a real `htop` recording taken across a live
    /// `SIGWINCH`, re-splitting leaves debris in the cells htop does not overwrite, because htop
    /// repaints **without** clearing. `vim` hides it by erasing first.
    reflow: bool,
}

/// The result of reflowing one pane.
struct PaneReflow {
    screen: Vec<Row>,
    scrollback: VecDeque<Row>,
    /// The cursor's new screen-relative position.
    cursor: (usize, usize),
    /// Each tracked extra point's new position **in this pane's own `[history ++ screen]` frame**,
    /// index-aligned with the `extra_abs` argument — *before* any history the caller discards.
    ///
    /// Reported raw, with `evicted` beside it, because the two callers translate differently and
    /// doing it here silently picked the primary's answer for both: the primary keeps its history,
    /// so an extra's absolute line only moves by what the cap threw away, while the alt pane has no
    /// history at all and everything above the screen is *gone*. Adding the alt result to the
    /// primary's scrollback length then produced a line the buffer does not have — reachable
    /// without any reflow, on a rows-only resize.
    extras: Vec<(usize, usize)>,
    /// Rows that left the buffer entirely off the front of this pane's history. For the primary
    /// that is the scrollback cap's eviction; for the alt pane, whose limit is `0` because it has
    /// no history, it is every row the shrink pushed off the top. An extra whose raw line is below
    /// this **is not in the buffer any more** — the caller decides what that means for its kind.
    evicted: usize,
}

/// Reflow one pane (its `scrollback` joined with `screen`) to `dims`, tracking
/// the screen-relative cursor `point` plus any `extra_abs` points given in
/// **absolute** `[scrollback ++ screen]` coordinates (selection anchors).
fn reflow_pane(
    screen: Vec<Row>,
    scrollback: VecDeque<Row>,
    point: (usize, usize),
    extra_abs: &[(usize, usize)],
    dims: ReflowDims,
) -> PaneReflow {
    let scroll_len = scrollback.len();
    let mut all: Vec<Row> = scrollback.into();
    all.extend(screen);

    // The cursor is screen-relative; lift it to absolute, then track it together
    // with the already-absolute extras.
    let mut pts: Vec<(usize, usize)> = Vec::with_capacity(1 + extra_abs.len());
    pts.push((scroll_len + point.0, point.1));
    pts.extend_from_slice(extra_abs);

    let pts = if dims.reflow && dims.cols != dims.old_cols {
        let (reflowed, np) = crate::grid::reflow(all, dims.cols, &pts);
        all = reflowed;
        np
    } else {
        pts
    };

    // The cursor can land one row past everything the reflow emitted — "just after the content"
    // when the content ends on a full row (#562). That row is real, and while the pane is shorter
    // than the screen the caller's fit supplies it for free. When the content already fills the
    // pane it has to be bought, and the price is one row of history: the pane **scrolls**, which is
    // what a terminal does when content grows past the bottom. Without it the cursor was pulled
    // back onto the last glyph and the next byte destroyed a character — the ordinary shell shape,
    // a prompt at the bottom of a full screen.
    //
    // Five earlier designs made `reflow` itself materialise the row and were rejected on
    // measurements (a cursor at column 59 resized to width 4 emptied the buffer; a blank-line
    // exemption turned 22 alt lines into 21). `reflow` cannot see this pane's budget, so it spent
    // what it did not have. Here the budget is in scope, and it is the gate: a pane with no history
    // cannot pay — the displaced row would be destroyed rather than archived — so it keeps clamping.
    //
    // `limit > 0`, deliberately, and not "is this the alt screen": since #567 the alt panes pass
    // `limit: 0` because that is what an alt screen's history is, so they are excluded by the budget
    // rather than by a branch. That branch is what the design carrying this rule was rejected for
    // needing.
    //
    // This **amends** ADR-0025 rather than reading it narrowly: `reflow` does not create rows; the
    // seam may, when the pane can pay. What that record measured is that materialising
    // *unconditionally* destroys content.
    let cursor_abs = pts[0].0 + usize::from(pts[0].1 == dims.cols);
    if dims.limit > 0 {
        while all.len() <= cursor_abs {
            all.push(Row::blank(dims.cols));
        }
    }

    let split = all.len().saturating_sub(dims.rows);
    let history: Vec<Row> = all.drain(0..split).collect();
    let mut sb: VecDeque<Row> = history.into();
    let mut dropped = 0usize;
    while sb.len() > dims.limit {
        sb.pop_front();
        dropped += 1;
    }

    // `reflow` may answer `col == cols` — "just after the last cell", which is a real place in the
    // logical line and no place in the grid (#562). The **cursor's** reading of it is the next
    // *write* position, so a full row means the start of the row after; the caller's row fit
    // provides that row (`Grid::set_screen` pads at the bottom). A mark reads the same value the
    // opposite way and keeps it verbatim — see `Term::resize`.
    let cursor_row = pts[0].0.saturating_sub(split);
    let cursor = if pts[0].1 == dims.cols {
        (cursor_row + 1, 0)
    } else {
        (cursor_row, pts[0].1)
    };

    // The bound on a tracked line belongs **here**, not inside `reflow`: this is where the final
    // geometry is known. The screen is padded to `dims.rows` whatever `reflow` emitted, so this
    // pane's last addressable line is `split + dims.rows - 1`. Bounding against `reflow`'s own row
    // count instead clamped away rows the fit was about to create (#562), while still being the
    // only thing standing between an out-of-range anchor and a panic in the consumer's process —
    // selection anchors and marks are written back raw, unlike the cursor (`Cursor::set_point`).
    // Expressed in this pane's own frame, so it is the same frame `extras` and `evicted` are in.
    let max_line = split + dims.rows - 1;

    // The cursor returns to screen-relative (its absolute index minus the history split). The
    // extras stay in this pane's frame — see the field docs for why they are not shifted here.
    PaneReflow {
        cursor,
        extras: pts[1..]
            .iter()
            .map(|&(l, c)| (l.min(max_line), c))
            .collect(),
        evicted: dropped,
        screen: all,
        scrollback: sb,
    }
}

/// Default tab stops: one every 8 columns (incl. column 0), matching xterm.
fn default_tabs(cols: usize) -> Vec<bool> {
    (0..cols).map(is_default_tab_stop).collect()
}

/// Whether `col` carries a stop in the default ladder.
///
/// Shared by the table the constructor builds and the extension [`Term::resize`]
/// performs, which fills at the *absolute* column index. The two must not drift,
/// and a second literal `8` is exactly how they would.
fn is_default_tab_stop(col: usize) -> bool {
    col.is_multiple_of(8)
}

/// First sub-parameter of CSI param `idx`, or `default` when absent or zero
/// (a zero/omitted numeric param means "1" for cursor movement and "0" for
/// erase — callers pass the right default).
/// Push onto an XTWINOPS title stack, bounded at [`TITLE_STACK_DEPTH`] (#823).
///
/// At the bound the **oldest** entry goes and the push still succeeds, which is
/// what both implementations carrying this feature do — xterm.js `shift()`s its
/// array, alacritty `remove(0)`s its `Vec`, and xterm wraps a fixed-size one.
/// The alternative (refuse the push) is worse in the case that actually occurs:
/// it breaks the pairing for the innermost nesting levels, and those are the
/// ones a user unwinds first.
fn push_title(stack: &mut Vec<String>, value: String) {
    if stack.len() >= TITLE_STACK_DEPTH {
        stack.remove(0);
    }
    stack.push(value);
}

fn param_or(params: &Params, idx: usize, default: u16) -> u16 {
    match params.iter().nth(idx).and_then(|p| p.first().copied()) {
        Some(v) if v != 0 => v,
        _ => default,
    }
}

/// The `Pv` field of the secondary device-attributes report (#824), derived
/// from the crate version so a release cannot ship a report that disagrees
/// with what was published.
///
/// Semver components are padded base-100, so a higher version always reports a
/// higher number. That is alacritty's scheme, and it is a *reinterpretation* of
/// the spec rather than a divergence from it: `ctlseqs.txt` calls `Pv` "the
/// firmware version" and fixes no encoding for it.
///
/// **The encoding has a functional floor, and it is not cosmetic.** Measured on
/// a real pty by sweeping this field alone (RHEL 9.2, vim 8.2), vim picks its
/// mouse protocol off `Pv`:
///
/// ```text
/// Pv < 95     ->  ttymouse=xterm    (no upgrade at all)
/// Pv = 95     ->  ttymouse=sgr      (vim special-cases the exact >1;95;0c
///                                    signature that macOS Terminal sends)
/// 95..276     ->  ttymouse=xterm2
/// Pv >= 277   ->  ttymouse=sgr
/// ```
///
/// The mouse rows above reproduced across two independent runs, 11 arms each,
/// with no-reply controls bracketing both.
///
/// A further gate sits on the same field: vim's XTGETTCAP key-code
/// interrogation, which its `term.txt` (*xterm-codes*) documents as needing a
/// response indicating "patchlevel 141 or higher". Measured here only to the
/// extent of bracketing — present at 276 and 1500, absent at 1, 94 and 95 — so
/// the doc's 141 is consistent but not independently pinned. The number
/// therefore gates upgrades at three separate thresholds rather than one, and
/// 1500 clears all three.
///
/// justerm at 0.15.0 maps to 1500 and clears it comfortably. A `0.2.x` would map
/// to 200 and silently cost every consumer the SGR mouse encoding — so the
/// base-100 scheme is load-bearing for a reason that has nothing to do with
/// monotonicity, and lowering the base would be a behavioural change.
///
/// Three edges, all deliberate. A component of 100 or more carries into the
/// next place — justerm is far from that, and widening the base would change
/// every number already reported for no measured gain. The pre-release suffix
/// is cut at the **first** hyphen, which is where semver says it begins;
/// alacritty cuts at the last, which mis-parses a two-part suffix like
/// `-rc.1-dev`. And the monotonicity above holds only below `u16::MAX`: a CSI
/// parameter is a `u16` in `vte` (saturating), and ghostty types the field
/// `firmware_version: u16`, so a `Pv` past 65535 — major version 7 — reaches a
/// receiver saturated. alacritty carries the same latent property; the corpus
/// prescribes no wider encoding, so this is recorded rather than designed
/// around.
const fn version_number(version: &str) -> u32 {
    let bytes = version.as_bytes();
    let mut parts = [0u32; 3];
    let mut part = 0usize;
    let mut i = 0usize;
    while i < bytes.len() {
        let b = bytes[i];
        if b == b'-' || b == b'+' {
            break;
        } else if b == b'.' {
            part += 1;
            if part >= 3 {
                break;
            }
        } else if b.is_ascii_digit() {
            parts[part] = parts[part] * 10 + (b - b'0') as u32;
        }
        i += 1;
    }
    parts[0] * 10_000 + parts[1] * 100 + parts[2]
}

/// `Pp` of the secondary DA report: 1 = VT220, from the spec's closed table
/// (`ctlseqs.txt:825`). It names the same terminal DA1 already advertises —
/// `CSI ? 62 ; 22 c`, where 62 *is* VT220 (`ctlseqs.txt:778`).
///
/// The two are not forced to agree in general: DA1's first parameter is an
/// operating **level** and `Pp` a device **type**, and xterm can decouple them
/// through DECTID. justerm implements neither DECTID nor DECSCL, so nothing
/// here can decouple them — which is why one terminal identity is the only
/// coherent answer, not because disagreeing would be malformed.
///
/// ghostty is the convergence check: it derives both from one device type
/// (`src/terminal/device_attributes.zig:82`, `:161` @ `e6e26e1`) and pairs a
/// level-62 DA1 with `Pp = 1` (`src/termio/stream_handler.zig:843`). Its DA1 is
/// *not* byte-identical to justerm's at its default — `clipboard-write` is
/// `.allow` (`src/config/Config.zig:2380`), which appends `;52`; the identical
/// string is its deny branch. alacritty pairs `?6c` (VT102) with `Pp = 0` and
/// xterm.js `?1;2c` (VT100) with `Pp = 0`, both of which are what this same
/// rule produces at those levels — so neither is a counterexample, and no
/// reference in the corpus pairs a level-62 DA1 with a `Pp` other than 1.
const DA2_TERMINAL_TYPE: u32 = 1;

/// `Pc` of the secondary DA report: 0.
///
/// The ground is first-principles and needs no reference: `Pc` is a **ROM
/// cartridge registration number**, justerm has no cartridge, and 0 is the
/// absence value. That is how both implementations that comment the field read
/// it — xterm writes it as `/* options (none) */` (`charproc.c:4267`) and
/// ghostty as *"Always 0 for emulators"* (`src/terminal/device_attributes.zig:88`
/// @ `e6e26e1`). xterm.js sends 0 in all three of its branches; alacritty alone
/// sends 1 (`alacritty_terminal/src/term/mod.rs:1267` @ `852e971`).
///
/// **What does *not* carry this choice, stated because it looks like it should.**
/// `ctlseqs.txt:839` says `Pc` *"is always zero"* only of a **DEC terminal** —
/// a description of hardware in xterm's own documentation, not a requirement on
/// emulators. And ADR-0004 tie-breaks the spec against alacritty where alacritty
/// *"merely omits or under-implements"*; here alacritty **contradicts**, which
/// is neither of its branches, and its other branch (genuine ambiguity → follow
/// alacritty) would give 1. So the value rests on the argument above and on the
/// 3-1 head count, not on a spec mandate that does not exist.
const DA2_ROM_CARTRIDGE: u32 = 0;

/// The `Pv` this build reports, folded at compile time so the doc-comment above
/// is literally true and the query path does no arithmetic.
const DA2_VERSION: u32 = version_number(env!("CARGO_PKG_VERSION"));

impl Term {
    /// Apply one DEC private mode set (`'h'`) or reset (`'l'`). DECSET/DECRST
    /// carry a list of modes, so `csi_dispatch` folds this over every parameter
    /// (#56); each mode is an independent toggle, not a stack.
    fn set_dec_private_mode(&mut self, action: char, mode: u16) {
        match (action, mode) {
            ('h', 1049) => self.enter_alt_screen(),
            ('l', 1049) => self.leave_alt_screen(),
            // Legacy alt-screen variants (#72): ?47/?1047 switch the buffer
            // without saving the cursor; ?1048 saves/restores the cursor without
            // switching. ?1049 is the two combined.
            ('h', 47) | ('h', 1047) => self.switch_to_alt(),
            ('l', 47) | ('l', 1047) => self.switch_to_primary(),
            ('h', 1048) => self.save_alt_cursor(),
            ('l', 1048) => self.restore_alt_cursor(),
            ('h', 6) => {
                // DECOM: set homes the cursor to the region top.
                self.origin_mode = true;
                self.goto(0, 0);
            }
            ('l', 6) => self.origin_mode = false, // unset leaves the cursor put
            ('h', 7) => self.autowrap = true,     // DECAWM
            ('l', 7) => self.autowrap = false,
            ('h', 45) => self.reverse_wraparound = true, // reverse wraparound (#80)
            ('l', 45) => self.reverse_wraparound = false,
            // DECCOLM (#82): the engine is dimension-free, so emit a request the
            // consumer may honor by resizing — no screen/cursor/margin change here.
            ('h', 3) => self.events.push(TermEvent::ColumnMode { cols: 132 }),
            ('l', 3) => self.events.push(TermEvent::ColumnMode { cols: 80 }),
            ('h', 25) => self.cursor.visible = true, // DECTCEM show
            ('l', 25) => self.cursor.visible = false, // DECTCEM hide
            ('h', 12) => self.cursor.blink = true,   // att610 cursor blink (#81)
            ('l', 12) => self.cursor.blink = false,
            ('h', 2004) => self.bracketed_paste = true,
            ('l', 2004) => self.bracketed_paste = false,
            ('h', 2026) => self.synchronized_output = true, // synchronized output (#73)
            ('l', 2026) => self.synchronized_output = false,
            ('h', 2027) => self.grapheme_clustering = true, // grapheme-cluster mode (#295)
            ('l', 2027) => self.grapheme_clustering = false,
            ('h', 2031) => self.color_scheme_updates = true, // color-scheme notifications (#85)
            ('l', 2031) => self.color_scheme_updates = false,
            ('h', 9001) => self.win32_input_mode = true, // win32-input-mode (#86)
            ('l', 9001) => self.win32_input_mode = false,

            // Input-encoding modes (#11): DECCKM, mouse tracking + encoding,
            // focus reporting. Each set assigns the level; each reset clears
            // it (apps enable/disable the same mode, not a stack).
            ('h', 1) => self.app_cursor_keys = true, // DECCKM
            ('l', 1) => self.app_cursor_keys = false,
            ('h', 66) => self.application_keypad = true, // DECNKM (#74)
            ('l', 66) => self.application_keypad = false,
            // DECANM (#84): set = ANSI (the normal state); reset enters VT52. Only
            // the reset is meaningful — `?2h` is a no-op (already ANSI).
            ('l', 2) => self.vt52_mode = true,
            ('h', 9) => self.mouse_protocol = MouseProtocol::X10, // X10 mouse (#70)
            ('h', 1000) => self.mouse_protocol = MouseProtocol::Normal,
            ('h', 1002) => self.mouse_protocol = MouseProtocol::ButtonEvent,
            ('h', 1003) => self.mouse_protocol = MouseProtocol::AnyEvent,
            ('l', 9) | ('l', 1000) | ('l', 1002) | ('l', 1003) => {
                self.mouse_protocol = MouseProtocol::Off
            }
            ('h', 1006) => self.mouse_encoding = MouseEncoding::Sgr,
            ('l', 1006) => self.mouse_encoding = MouseEncoding::Default,
            ('h', 1015) => self.mouse_encoding = MouseEncoding::Urxvt,
            ('l', 1015) => self.mouse_encoding = MouseEncoding::Default,
            ('h', 1005) => self.mouse_encoding = MouseEncoding::Utf8,
            ('l', 1005) => self.mouse_encoding = MouseEncoding::Default,
            ('h', 1016) => self.mouse_encoding = MouseEncoding::SgrPixels,
            ('l', 1016) => self.mouse_encoding = MouseEncoding::Default,
            ('h', 1004) => self.focus_events = true,
            ('l', 1004) => self.focus_events = false,

            _ => {} // other DEC modes are later slices
        }
    }

    /// Dispatch one VT52 escape sequence (`ESC <final>`), reached only while
    /// `vt52_mode` is set (#84). VT52 is a pre-ANSI dialect: the cursor/erase
    /// finals map to the same `Term` primitives the ANSI path uses. `ESC <`
    /// returns to ANSI. Unknown finals are ignored.
    fn vt52_dispatch(&mut self, byte: u8) {
        match byte {
            b'A' => self.move_up(1),         // cursor up
            b'B' => self.move_down(1),       // cursor down
            b'C' => self.move_forward(1),    // cursor right
            b'D' => self.move_back(1),       // cursor left
            b'H' => self.goto(0, 0),         // cursor home
            b'I' => self.reverse_index(),    // reverse line feed
            b'J' => self.erase_display(0),   // erase cursor → end of screen
            b'K' => self.erase_line(0),      // erase cursor → end of line
            b'Y' => self.vt52_y_pending = 2, // direct address: two coord bytes follow
            // Identify (DECID): reply `ESC / Z` — "I am a VT52".
            b'Z' => self.replies.extend_from_slice(b"\x1b/Z"),
            b'=' => self.application_keypad = true, // enter alternate keypad
            b'>' => self.application_keypad = false, // exit alternate keypad
            b'<' => self.vt52_mode = false,         // exit VT52, return to ANSI
            // RIS (`ESC c`) is honored even here: it is a hard "recover from any
            // state" reset, and `full_reset` rebuilds `Term` with `vt52_mode`
            // cleared, so RIS always escapes VT52 back to ANSI. VT52 defines no
            // other meaning for `ESC c`.
            b'c' => self.full_reset(),
            // Graphics mode (`ESC F`/`ESC G`) is a documented non-goal: the VT52
            // graphics glyph set differs from DEC Special Graphics, so reusing that
            // charset would render the wrong glyphs. No-op rather than approximate.
            b'F' | b'G' => {}
            _ => {} // unknown VT52 finals are ignored
        }
    }

    /// Consume one `ESC Y` coordinate byte (#84). The first byte is the row, the
    /// second the column; each decodes as `value - 0x20`. On the second byte the
    /// cursor is addressed (`goto` clamps out-of-range coordinates). Reached only
    /// from `print` while `vt52_y_pending > 0`.
    fn vt52_take_coord(&mut self, c: char) {
        let coord = (c as usize).saturating_sub(0x20);
        if self.vt52_y_pending == 2 {
            self.vt52_y_row = coord;
            self.vt52_y_pending = 1;
        } else {
            self.vt52_y_pending = 0;
            self.goto(self.vt52_y_row, coord);
        }
    }

    /// The allocation an OSC 8 `id=` names: the live one if that id already named a link
    /// with this same URI, else a fresh one recorded under the key (#635).
    ///
    /// Keyed on **id and URI together**, mirroring xterm.js's `_getEntryIdKey`
    /// (`` `${id};;${uri}` ``, `OscLinkService.ts:87`). Keying on the id alone would follow
    /// a reused id to a stale target — an application saying "same link" about two
    /// different destinations has not said anything the engine should honour.
    fn link_for_id(&mut self, id: &str, uri: &str) -> std::sync::Arc<str> {
        let key = format!("{id};;{uri}");
        // A key whose link has left the buffer is *absent*, not stale — the group it named
        // is gone, so this open starts a new one. That is xterm.js's behaviour too, reached
        // by deleting the entry rather than by letting a reference die.
        if let Some(live) = self.link_ids.get(&key).and_then(std::sync::Weak::upgrade) {
            return live;
        }
        // Amortised sweep before inserting, so dangling keys stay O(live) rather than
        // O(ids ever declared). Doubling the threshold keeps it O(1) per open.
        if self.link_ids.len() >= self.link_ids_sweep_at {
            self.link_ids.retain(|_, weak| weak.strong_count() > 0);
            self.link_ids_sweep_at = (self.link_ids.len() * 2).max(LINK_IDS_FIRST_SWEEP);
        }
        let fresh: std::sync::Arc<str> = std::sync::Arc::from(uri);
        self.link_ids.insert(key, std::sync::Arc::downgrade(&fresh));
        fresh
    }
}

impl Perform for Term {
    fn print(&mut self, c: char) {
        // VT52 `ESC Y` direct addressing (#84): vte delivers the two coordinate
        // bytes here (it returned to ground after the `Y` final), so intercept
        // them before they would be written as glyphs.
        if self.vt52_y_pending > 0 {
            self.vt52_take_coord(c);
            return;
        }
        // Translate through the active (GL) character set first (#62): under DEC
        // Special Graphics a printable byte becomes a line-drawing glyph.
        let c = self.charsets[self.gl].map(c);
        self.place_grapheme(c);
    }

    /// A DCS is terminated: not a print, so the repeat is disarmed. This method
    /// exists for that alone — the payload is otherwise unhandled — and it is reachable
    /// in ordinary use: with DA2 answered, `vim` follows up with XTGETTCAP
    /// (`DCS + q <hex> ST`) queries this engine does not answer. Both halves of that
    /// are pinned on recorded bytes rather than asserted — `tests/closed_loop_capture.rs`.
    ///
    /// The end of the DCS and not its start, which is both xterm's rule (its gate fires
    /// when the parser returns to the ground state) and the only half that can be shown
    /// to matter: no CSI can arrive between `hook` and here, so a disarm in `hook` is a
    /// guard no mutation can redden.
    ///
    /// Which DCS terminator is fed decides whether this line is load-bearing at all,
    /// measured by deleting it (`-`, a DCS, then `CSI 3 b`, counting dashes):
    ///
    /// | terminator | dashes without this line |
    /// |---|---|
    /// | `ESC \` (7-bit ST) | 1 — `esc_dispatch` disarms on the `\` |
    /// | `0x9C` (8-bit ST, which DCS accepts where OSC refuses it) | 4 |
    /// | none; aborted by the `ESC` of the next sequence | 4 |
    ///
    /// So a test that feeds only `ESC \` proves nothing here, which is what the first
    /// version of `rep_after_a_dcs_repeats_nothing` did.
    ///
    /// The last row is a **deliberate divergence from xterm**, in the safe direction:
    /// an unterminated DCS never returns xterm's parser to the ground state, so xterm
    /// would still repeat, while `vte` calls this on the abort and this engine does
    /// not. Disarming too eagerly can only turn `REP` into a no-op.
    fn unhook(&mut self) {
        self.repeat_anchor = None;
    }

    fn execute(&mut self, byte: u8) {
        // Not a print, so the repeat is disarmed (#825, [`Term::repeat_anchor`]). This
        // is also where `CAN` and `SUB` land, which abort a sequence in every state.
        self.repeat_anchor = None;
        match byte {
            // LF, VT, FF all line-feed.
            b'\n' | 0x0b | 0x0c => self.linefeed(),
            b'\r' => self.carriage_return(),
            0x08 => self.backspace(),
            b'\t' => self.put_tab(),
            0x07 => self.events.push(TermEvent::Bell), // BEL (#12)
            0x0e => self.gl = 1,                       // SO (LS1): GL = G1 (#62)
            0x0f => self.gl = 0,                       // SI (LS0): GL = G0
            _ => {}
        }
    }

    fn csi_dispatch(&mut self, params: &Params, intermediates: &[u8], _ignore: bool, action: char) {
        // Every completed CSI disarms `REP` (#825, [`Term::repeat_anchor`]). It is
        // *taken* here rather than cleared on the way out because this function has
        // six early returns and a clear at the end would miss all of them; `REP` is
        // the one arm that needs the value, and it puts it back.
        let repeat_anchor = self.repeat_anchor.take();
        // Kitty keyboard-protocol negotiation: CSI > / = / < / ? ... u. The
        // leading intermediate distinguishes it from plain `CSI u` (SCORC) (#23).
        if action == 'u'
            && let Some(&lead) = intermediates.first()
            && matches!(lead, b'>' | b'<' | b'=' | b'?')
        {
            self.kitty_dispatch(lead, params);
            return;
        }
        // DEC private modes arrive with a '?' intermediate.
        if intermediates.first() == Some(&b'?') {
            // DECRQM (CSI ? Ps $ p) — report whether mode Ps is set. The '$'
            // intermediate distinguishes it from a plain `?...p`. It queries a
            // single mode, so it keys off the first parameter only.
            if action == 'p' && intermediates.contains(&b'$') {
                self.decrqm(param_or(params, 0, 0));
                return;
            }
            // Private DSR (CSI ? Ps n): ?996 = color-scheme query (#85). The
            // theme-agnostic engine relays it as an event for the consumer.
            if action == 'n' {
                if param_or(params, 0, 0) == 996 {
                    self.events.push(TermEvent::ColorSchemeQuery);
                }
                return;
            }
            // DECSET/DECRST carry a *list* of modes; apply set/reset to EVERY
            // parameter, not just the first — htop batches `?1006;1000h` into one
            // CSI, so folding only params[0] dropped the 1000 (#56).
            for mode in params.iter().filter_map(|p| p.first().copied()) {
                self.set_dec_private_mode(action, mode);
            }
            return;
        }
        // DECSTR soft reset: CSI ! p (#53).
        if intermediates.first() == Some(&b'!') && action == 'p' {
            self.soft_reset();
            return;
        }
        // DECSCUSR set cursor style: CSI Ps SP q (space intermediate) (#89). The raw
        // value is read, since `param_or` folds 0 to its default and 0 is the reset.
        // `CSI SP q` arrives from vte as an explicit 0; `unwrap_or(1)` covers a
        // params list with no entry at all.
        if intermediates.first() == Some(&b' ') && action == 'q' {
            let param = params.iter().next().and_then(|p| p.first().copied());
            self.set_cursor_style(param.unwrap_or(1));
            return;
        }
        // DA2 (secondary device attributes, CSI > c) — the query vim uses to
        // fill `v:termresponse` and identify what it is talking to (#824).
        //
        // What answering it actually buys, measured as a control pair on a real
        // pty (RHEL 9.2, vim 8.2, TERM=xterm-256color, 24x80; every other query
        // answered identically in both arms, controls run before and after):
        //
        //     no reply           ->  ttymouse=xterm
        //     ESC[>1;1500;0c     ->  ttymouse=sgr
        //
        // The mouse protocol is what the version number buys *directly*: legacy
        // `xterm` encoding cannot report a column past 223 and cannot report a
        // release, `sgr` has neither limit.
        //
        // It is not the only effect, and the second one is the larger. Answering
        // also makes vim **ask ten more questions** — `DCS + q <hex> ST`
        // (XTGETTCAP) for `Co`, `ku`, `kd`, `kl`, `kr`, `k1`, `#2`, `#4`, `%i`
        // and `*7`: the colour count and the arrow / function / shifted key
        // codes. vim's own `term.txt` gates that on the reply indicating
        // "patchlevel 141 or higher", and its point is that a terminal produces
        // different key codes in different modes, so it asks instead of
        // guessing. Measured rather than taken from the doc: the requests appear
        // at `Pv` 276 and 1500 and are absent at 1, 94 and 95, which brackets the
        // gate to (95, 276] and is consistent with 141 without pinning it. What
        // is stable across runs is whether they appear at all; *how many* arrive
        // is not — one arm sent each capability once where every other sent it
        // twice. **justerm answers none of those today** — they fall to the
        // same intermediate catch-all this block sits above — so the capability
        // is unlocked and then unanswered. That is the honest state, and it is
        // #47 tail rather than this slice.
        //
        // modifyOtherKeys is *not* gated on any of it: vim emits `CSI > 4 ; 2 m`
        // about 180 bytes before it asks.
        //
        // `>` reaches us as an *intermediate*, so DA2 was not "unhandled" but
        // unreachable: the catch-all below returns before the final is ever
        // examined. This opened exactly one route through it — the `>` prefix
        // alone, with the `c` final. **A second one is open now**: the `m`
        // final, for XTMODKEYS (#890), in the block immediately below this one.
        //
        // It is one route out of ten `>` finals xterm routes, and the choice is
        // reach, not completeness: across this repo's capture corpus `CSI > c`
        // occurs 5 times and XTMODKEYS `CSI > m` 10 (re-measured 2026-09-11 after
        // #891 added a twentieth fixture; they read 4 and 7 when #890 chose on
        // them, and the order the choice turned on is unchanged) — the latter is
        // the highest-reach `>` sequence justerm did not route, which is why it
        // was the next one taken (#890) rather than a later one — it no longer falls
        // through here. XTVERSION `CSI > q` occurs **once**, in `tmux_clipboard.raw`.
        //
        // Both numbers moved after this paragraph was written, and the second one
        // changed sign: it said `> q` occurred *zero* times, which was true on
        // 2026-09-01 and false on 2026-09-02, when #842 checked in a tmux capture
        // that contains one (re-measured 2026-09-11, and a fresh tmux attach
        // recorded the same day emits it too — tmux asks unconditionally). A count
        // taken from a corpus is only ever true of one revision of it.
        //
        // And it is a floor rather than a measurement of reach, because all but one
        // capture is **open-loop** — recorded under `script(1)` or a bare `expect`,
        // both of which answer nothing, so no sequence an application only sends *after* a reply can
        // appear in it. The signature is in the corpus: answering DA2 makes vim ask
        // ten `DCS + q` XTGETTCAP questions, and `DCS + q` occurs **zero** times
        // across every open-loop fixture, four of which ask DA2. The exception is
        // `vim_closed_loop.raw`, which holds all ten (#891) — what it cost to record
        // one, and why its bytes are a function of a consumer policy as well as of
        // vim, is in `docs/map/territory/vt-interpretation.md`.
        //
        // The match is on the whole slice rather than `.first()`, so
        // `CSI > $ c` is not DA2. That is 3-1: xterm drops it
        // (`VTPrsTbl.c:4747`, `$` is CASE_CSI_IGNORE inside `dec2_table`),
        // ghostty drops it (`src/terminal/stream.zig:1612`, `else => null`) and
        // xterm.js drops it (its handler key packs prefix *and* intermediates,
        // `InputHandler.ts:233`), while alacritty **would answer** it
        // (`vte-0.15.0/src/ansi.rs:1572` passes `intermediates.first()`). No
        // producer of that form exists in any pinned corpus, so this is a
        // divergence with no measured reach — pinned by a test regardless,
        // because the predicate is otherwise unfalsifiable.
        if intermediates == [b'>'] && action == 'c' {
            // Only `Ps = 0` or omitted is a request; a qualifier we do not
            // recognise is answered with silence rather than with a report that
            // does not address it. xterm (`charproc.c:4220`), xterm.js
            // (`InputHandler.ts:1738`) and alacritty (`ansi.rs:1572`) all gate
            // this way; ghostty reads no parameter at all and has no test that
            // would notice.
            if param_or(params, 0, 0) == 0 {
                self.replies.extend_from_slice(
                    format!("\x1b[>{DA2_TERMINAL_TYPE};{DA2_VERSION};{DA2_ROM_CARTRIDGE}c")
                        .as_bytes(),
                );
            }
            return;
        }
        // XTMODKEYS (`CSI > Pp ; Pv m`) — the second route through the `>` guard, and
        // the highest-reach one: 10 occurrences across this repo's captures against
        // DA2's 5, all of them `Pp = 4` (modifyOtherKeys). `vim` sets it at startup
        // and clears it on exit, and the clear is the more frequent of the two.
        //
        // **Only `Pp = 4` is routed**, of the eight resources xterm keys off this one final;
        // `CSI > m` is deliberately not honoured, because an omitted `Pp` is measurably
        // indistinguishable from one aimed at another resource. **`Pv >= 2`, not `== 2`**:
        // level 2 is what separates `Ctrl+I` from `Tab`, and 3 asks for more than 2 rather
        // than for nothing. Both, with the reference sites, are in
        // `docs/agents/reference-facts.md` (#890).
        if intermediates == [b'>'] && action == 'm' {
            if param_or(params, 0, 0) == 4 {
                self.modify_other_keys_2 = param_or(params, 1, 0) >= 2;
            }
            return;
        }
        // Other private/intermediate sequences are later slices; ignore them
        // rather than misinterpret.
        if !intermediates.is_empty() {
            return;
        }
        match action {
            'A' => self.move_up(param_or(params, 0, 1) as usize),
            'B' => self.move_down(param_or(params, 0, 1) as usize),
            'e' => self.vertical_position_relative(param_or(params, 0, 1) as usize),
            // CNL / CPL (CSI Ps E / F): CUD / CUU, then CR (#898).
            'E' => {
                self.move_down(param_or(params, 0, 1) as usize);
                self.carriage_return();
            }
            'F' => {
                self.move_up(param_or(params, 0, 1) as usize);
                self.carriage_return();
            }
            'C' | 'a' => self.move_forward(param_or(params, 0, 1) as usize),
            'D' => self.move_back(param_or(params, 0, 1) as usize),
            // CBT (CSI Ps Z): back-tab, the mirror of HT over the tab-stop
            // table. Cursor motion only — it writes no cell (#826).
            'Z' => self.put_back_tab(param_or(params, 0, 1) as usize),
            // CHT (CSI Ps I): forward tab, the counted HT (#898).
            'I' => self.put_forward_tabs(param_or(params, 0, 1) as usize),
            // REP (CSI Ps b): repeat the preceding grapheme. `param_or` folds an
            // absent parameter and an explicit zero to one, as everywhere else here.
            'b' => {
                // The three lines are one rule and their order is the rule: put back
                // what this dispatch took, repeat, then clear what the repeats re-armed
                // through the print path. That is xterm's lifecycle — the byte
                // completing `CSI b` returns the parser to the ground state with nothing
                // printed, so a second `CSI b` repeats nothing. ghostty is the outlier
                // and re-arms (`printRepeat` calls `print`); pinned by
                // `rep_does_not_rearm_itself` (#825).
                self.repeat_anchor = repeat_anchor;
                self.repeat_last(param_or(params, 0, 1) as usize);
                self.repeat_anchor = None;
            }
            'G' | '`' => self.set_col(param_or(params, 0, 1) as usize - 1),
            'd' => self.set_row(param_or(params, 0, 1) as usize - 1),
            'H' | 'f' => {
                let row = param_or(params, 0, 1) as usize - 1;
                let col = param_or(params, 1, 1) as usize - 1;
                self.goto(row, col);
            }
            'J' => self.erase_display(param_or(params, 0, 0)),
            'K' => self.erase_line(param_or(params, 0, 0)),
            'X' => self.erase_chars(param_or(params, 0, 1) as usize),
            '@' => self.insert_chars(param_or(params, 0, 1) as usize),
            'P' => self.delete_chars(param_or(params, 0, 1) as usize),
            'S' => self.scroll_up_lines(param_or(params, 0, 1) as usize),
            'T' => self.scroll_down_lines(param_or(params, 0, 1) as usize),
            'L' => self.insert_lines(param_or(params, 0, 1) as usize),
            'M' => self.delete_lines(param_or(params, 0, 1) as usize),
            'g' => self.clear_tab_stop(param_or(params, 0, 0)),
            'r' => {
                let rows = self.grid.rows() as u16;
                let top = param_or(params, 0, 1) as usize;
                let bottom = param_or(params, 1, rows) as usize;
                self.set_scroll_region(top, bottom);
            }
            'm' => self.sgr(params),
            's' => self.save_cursor(), // SCOSC (CSI s) — alias of DECSC
            't' => self.window_ops(params), // XTWINOPS — only 22/23 (#823)
            'u' => self.restore_cursor(), // SCORC (CSI u) — alias of DECRC
            // DA1 (primary device attributes, CSI c): advertise VT220 + ANSI
            // colour — the levels justerm actually implements (#27).
            'c' => self.replies.extend_from_slice(b"\x1b[?62;22c"),
            'n' => self.device_status_report(param_or(params, 0, 0)),
            // Non-private SM/RM. Folded over every parameter (modes can batch,
            // like the private path #56). IRM (4) and LNM (20) so far.
            'h' => {
                for m in params.iter().filter_map(|p| p.first().copied()) {
                    match m {
                        4 => self.insert_mode = true,
                        20 => self.newline_mode = true,
                        _ => {}
                    }
                }
            }
            'l' => {
                for m in params.iter().filter_map(|p| p.first().copied()) {
                    match m {
                        4 => self.insert_mode = false,
                        20 => self.newline_mode = false,
                        _ => {}
                    }
                }
            }
            _ => {}
        }
    }

    fn esc_dispatch(&mut self, intermediates: &[u8], _ignore: bool, byte: u8) {
        // Not a print: the repeat is disarmed (#825, [`Term::repeat_anchor`]).
        self.repeat_anchor = None;
        // VT52 mode (#84): the pre-ANSI dialect reuses the same `ESC <final>`
        // tokens vte already produces, but with different meanings, so it is a
        // mode-gated branch here rather than a separate parser. All VT52 sequences
        // are intermediate-free; anything with an intermediate is not VT52.
        if self.vt52_mode && intermediates.is_empty() {
            self.vt52_dispatch(byte);
            return;
        }
        if let Some(&i) = intermediates.first() {
            // SCS: designate a charset to G0 (`ESC ( F`) or G1 (`ESC ) F`) (#62).
            if matches!(i, b'(' | b')') {
                let set = match byte {
                    b'0' => Charset::DecSpecialGraphics,
                    b'A' => Charset::Uk,
                    b'B' => Charset::Ascii,
                    _ => return, // other sets are later slices
                };
                self.charsets[if i == b'(' { 0 } else { 1 }] = set;
            }
            // Other intermediates (G2/G3 designators, etc.) are later slices.
            return;
        }
        match byte {
            b'D' => self.linefeed(), // IND (line-feed without CR)
            b'E' => {
                // NEL (next line): carriage return + line-feed.
                self.carriage_return();
                self.linefeed();
            }
            b'H' => self.set_tab_stop(),             // HTS
            b'M' => self.reverse_index(),            // RI
            b'7' => self.save_cursor(),              // DECSC
            b'8' => self.restore_cursor(),           // DECRC
            b'c' => self.full_reset(),               // RIS (#53)
            b'=' => self.application_keypad = true,  // DECKPAM (#74)
            b'>' => self.application_keypad = false, // DECKPNM
            _ => {}
        }
    }

    /// OSC dispatch (the event surface): title (0/2), cwd (7). OSC 8 hyperlink
    /// is per-cell state, handled in its own slice, not here.
    fn osc_dispatch(&mut self, params: &[&[u8]], bell_terminated: bool) {
        // Not a print: the repeat is disarmed (#825, [`Term::repeat_anchor`]).
        self.repeat_anchor = None;
        // Which byte ended the sequence decides which byte ends its reply, and
        // this is the only place it is observable — vte hands it over per
        // dispatch and keeps nothing (#836). It rides outward on the query
        // events rather than being remembered: `drain_events` is a batch, so
        // two queries can be outstanding at once and one stored scalar could
        // not say which exchange it belonged to.
        let terminator = if bell_terminated {
            Terminator::Bel
        } else {
            Terminator::St
        };
        // params[0] is the OSC number; params[1..] the payload fields.
        let Some(&number) = params.first() else {
            return;
        };
        match number {
            // OSC 0 = icon + window title, OSC 2 = window title. Both set title.
            // Since #823 the string is also *retained*, because a title pop has
            // nothing to restore otherwise. OSC 0 writes both axes and OSC 2
            // only the window one — the distinction was invisible while the
            // engine merely forwarded, and becomes observable the moment an
            // axis-limited push/pop pair (which `vim` emits) is answered.
            //
            // The payload is `params[1..]` **rejoined**, not `params[1]`: `vte` splits on
            // every `;` and a title may legally contain one, so reading a single field cut
            // `make -j8; ./run` down to `make -j8` and announced the short string as the
            // real one (#880). Same read-site rule #650 established for `OSC 8`. The guard
            // is the *slice* being non-empty, not the string: a fieldless `OSC 2` must stay
            // ignored where `OSC 2 ;` clears the title, and `params.get(1..)` answers
            // `Some(&[])` for the first, whose join is indistinguishable from the second.
            //
            // The rejoin recovers only what `vte` hands over, which is at most 16 fields: a
            // title with 15 or more `;` still arrives cut, and cannot be told from a complete
            // one here (#840, closed not planned; see the VT interpretation map note).
            b"0" | b"2" => {
                if let Some(fields) = params.get(1..).filter(|f| !f.is_empty()) {
                    let title = String::from_utf8_lossy(&fields.join(&b';')).into_owned();
                    if number == b"0" {
                        self.icon_name.clone_from(&title);
                    }
                    self.set_window_title(title);
                }
            }
            // OSC 7 = current working directory (a file:// URI). Rejoined for the reason
            // on the title arm above — `;` is a legal byte in a path and in a URI, and the
            // engine hands the value over as declared (#880, ADR-0017), up to the same
            // 16-field bound as the title.
            b"7" => {
                if let Some(fields) = params.get(1..).filter(|f| !f.is_empty()) {
                    let cwd = String::from_utf8_lossy(&fields.join(&b';')).into_owned();
                    self.events.push(TermEvent::Cwd(cwd));
                }
            }
            // OSC 133 = FinalTerm/iTerm2 shell-integration command marks (#158):
            // `A` prompt start, `B` command start, `C` output start, `D[;exit]`
            // command finished. Each anchors a kinded marker at the cursor line;
            // pairing + navigation is consumer policy (#160). Unknown subcommands
            // (or none) are ignored. `D`'s exit field parses to `i32`, else None.
            b"133" => match params.get(1).copied() {
                Some(b"A") => self.add_command_mark(MarkerKind::PromptStart),
                Some(b"B") => self.add_command_mark(MarkerKind::CommandStart),
                Some(b"C") => self.add_command_mark(MarkerKind::OutputStart),
                Some(b"D") => {
                    let exit = params
                        .get(2)
                        .and_then(|p| core::str::from_utf8(p).ok())
                        .and_then(|s| s.parse::<i32>().ok());
                    self.add_command_mark(MarkerKind::CommandFinished(exit));
                }
                _ => {}
            },
            // OSC 8 = hyperlink: `OSC 8 ; params ; URI`. A non-empty URI opens a
            // link (made current); an empty URI closes it. `params` carries the
            // optional `id=` that groups runs into one link (#635).
            b"8" => {
                // One allocation per *open*, shared by that open's cells and dropped
                // with the last row holding it (#628 — there is no pool). Two opens of
                // an identical URI stay two links, deliberately: merging them would
                // override a distinction the application controls through `id=`. That
                // parameter is the *only* dedup performed, which is one rule and not
                // two — xterm.js states it as "links with no id will only ever be
                // registered a single time" beside a lookup keyed on id-plus-uri
                // (`OscLinkService.ts:34`, `:49-54`).
                // The URI is `params[2..]` **rejoined**, not `params[2]` (#650). vte splits the
                // OSC payload on `;`, so a URI carrying an unencoded `;` arrives in pieces and
                // reading only the first dropped the rest — silently, with no error. Measured,
                // `]8;;https://x/a;b=c` arrives as `["8", "", "https://x/a", "b=c"]`. xterm.js
                // special-cases the same thing from the other side, splitting on the *first* `;`
                // only and taking all the rest as the URI, *"to support unencoded semi-colons in
                // the URIs"* (`InputHandler.ts:3106-3112`). `?a=1;b=2` is a legal query string.
                //
                // Nothing is lost at the parser **up to 16 fields**, and past that the tail is
                // gone before this arm runs: `vte` records at most 16 field boundaries, so a URI
                // with 14 or more `;` resolves to a shorter one that is indistinguishable from a
                // complete link (#840, closed not planned; see the VT interpretation map note).
                //
                // The close survives this: `]8;;` arrives as `["8", "", ""]`, whose rejoin is
                // empty, and an empty URI still closes. Never decoded — a `%3B` stays `%3B`,
                // because the engine hands the target over exactly as declared (ADR-0017).
                let uri: Vec<u8> = params.get(2..).unwrap_or_default().join(&b';');
                self.current_link = if uri.is_empty() {
                    None
                } else {
                    let uri = String::from_utf8_lossy(&uri);
                    Some(match osc8_link_id(params.get(1).copied().unwrap_or(b"")) {
                        // No id declared: fresh per open, the reference-correct default.
                        None => std::sync::Arc::from(&*uri),
                        Some(id) => self.link_for_id(&String::from_utf8_lossy(id), &uri),
                    })
                };
            }
            // OSC 4 = set/query an ANSI palette entry: `OSC 4 ; index ; spec`
            // (#122). The engine forwards index + raw spec; the consumer applies
            // it to its palette (theme-agnostic — the cell keeps `Indexed`).
            //
            // **An empty spec relays nothing, and drops only its own pair** (#834).
            // The engine cannot tell a *malformed* colour from a good one — it
            // never parses one, which is its identity and not a gap — but "this
            // field is empty" needs no parser, and forwarding `""` hands the
            // consumer a value it must invent a policy for.
            //
            // Dropping *the rest of the sequence* was the alternative, and it is
            // what xterm does: `ChangeOneAnsiColor` returns negative and that hits
            // `/* stop on any error */ break` (`misc.c:3013-3016`, pair loop at
            // `:2993`; chain `AllocateAnsiColor` → `xtermAllocColor` → `-1` at
            // `:2918`).
            //
            // **This is a deliberate divergence from the ADR-0004 tie-breaker, not
            // a case the tie-breaker fails to reach.** An earlier draft of this
            // comment claimed the latter and was wrong, which is worth stating
            // because the wrong version is the intuitive one: xterm makes the
            // *same* observation this engine makes — `strlen(spec) == 0`, no
            // parser, `misc.c:3105-3107` — and `XParseColor` at `:3111` is in the
            // `else if`, so it is never reached for an empty spec. The trigger IS
            // available here and "follow xterm" IS well defined. It is declined
            // because reading a blank field as evidence that structurally
            // well-formed pairs are corrupt is an inference about *application
            // intent*, which ADR-0017 puts on the consumer's side, and because it
            // would discard a value the application explicitly sent. That call is
            // the maintainer's, recorded on #834 with its grounds, and theirs to
            // reverse.
            //
            // **The references are 2–2 on this input, not 1–1**, and the two that
            // answer as this engine does are the two that keep walking: xterm.js
            // (`InputHandler.ts:3073`, loop `:3064`) and alacritty via `vte`
            // (`vte-0.15.0/src/ansi.rs:1372-1389` — a failed `xparse_color` falls
            // to `unhandled` with no `break`). ghostty relays nothing here, by a
            // *third* mechanism rather than by agreeing: `tokenizeScalar` drops
            // the empty token (`color.zig:130`) so the pairing re-aligns, and then
            // `RGB.parse("2")` fails into `catch return result` (`:210`), yielding
            // the accumulated — empty — list. Its re-alignment only becomes
            // *visible* where the re-aligned pair parses: `OSC 4 ; 1 ; ; #fff`
            // sets index 1 there and nothing anywhere else.
            //
            // The guard tests **emptiness only**, deliberately (#834 Out of
            // Scope). A space-only spec is relayed verbatim; TAB and NUL are C0
            // bytes `vte` drops inside an OSC string, so those fields arrive
            // genuinely empty and *are* dropped. Both are pinned by tests, so a
            // later "align with the reference" widening to whitespace reddens.
            b"4" => {
                // One event per `index ; spec` pair (xterm's `while slots > 1`).
                // The walk advances two fields whether or not a pair produces an
                // event, so dropping one cannot misalign the pairs after it.
                let mut rest = &params[1..];
                while let [idx, spec, tail @ ..] = rest {
                    rest = tail;
                    if let Ok(index) = String::from_utf8_lossy(idx).parse::<u8>() {
                        if *spec == b"?" {
                            self.events
                                .push(TermEvent::QueryPaletteColor { index, terminator });
                        } else if !spec.is_empty() {
                            self.events.push(TermEvent::SetPaletteColor {
                                index,
                                spec: String::from_utf8_lossy(spec).into_owned(),
                            });
                        }
                    }
                }
            }
            // OSC 104 = reset palette entries (#122): an **empty payload** resets
            // the whole table, else one event per named index.
            //
            // Empty means both `OSC 104` and `OSC 104 ;` (#832). vte hands those
            // over as `["104"]` and `["104", ""]`, and testing only the first left
            // the second falling into the index loop, where `"".parse::<u8>()`
            // fails and the reset evaporated silently. xterm tests the payload
            // string rather than the field count — `if (*buf != '\0')`
            // (`misc.c:3057`), whose else-branch is *"resetting all colors"*
            // (`misc.c:3077`) — and xterm.js gates on the same emptiness
            // (`InputHandler.ts:3223-3224`, a slot-less RESTORE).
            //
            // The test is `params[1]` being the *whole* payload, not "every field
            // is empty": for `OSC 104 ; ;` xterm's buf is `";"`, which is not
            // empty, so that form takes the index path. (ghostty differs here —
            // `tokenizeScalar` drops both separators and it resets everything —
            // but it agrees on the form that matters, `misc.c` and xterm.js do
            // not, and ADR-0004 puts the spec proxy on top.)
            b"104" => {
                if params.len() <= 1 || (params.len() == 2 && params[1].is_empty()) {
                    self.events.push(TermEvent::ResetPaletteColor(None));
                } else {
                    for &idx in &params[1..] {
                        if let Ok(index) = String::from_utf8_lossy(idx).parse::<u8>() {
                            self.events.push(TermEvent::ResetPaletteColor(Some(index)));
                        }
                    }
                }
            }
            // OSC 10/11/12 = set/query the default foreground/background/cursor
            // colour, stacking specs across the [fg, bg, cursor] slots (#122,
            // #137, #832). Each code names the slot the stack starts at. The
            // engine forwards raw specs (theme-agnostic).
            b"10" => self.special_color(params, 0, terminator),
            b"11" => self.special_color(params, 1, terminator),
            b"12" => self.special_color(params, 2, terminator),
            // OSC 52 = manipulate selection data (#828): `OSC 52 ; Pc ; Pd`.
            // The engine decodes `Pd` and relays the request; the *clipboard* is
            // the consumer's, and so is every policy about it.
            b"52" => self.clipboard(params, terminator),
            // OSC 110 / 111 / 112 = reset the default foreground / background /
            // cursor colour (#122, #832). One slot each, never a stack — xterm's
            // reset path resolves a single index from the code itself and walks
            // nothing (`misc.c:3729`).
            b"110" => self.events.push(TermEvent::ResetForeground),
            b"111" => self.events.push(TermEvent::ResetBackground),
            b"112" => self.events.push(TermEvent::ResetCursorColor),
            _ => {} // other OSCs are later slices
        }
    }
}

#[cfg(test)]
mod tests {
    use super::cap_scroll;
    use super::version_number;
    use crate::Engine;
    use crate::damage::ScrollOp;
    use crate::serialize::MAX_SCROLL_COUNT;

    /// #824 — the `Pv` mapping, in-crate because the seam cannot reach it.
    ///
    /// `tests/reply.rs` asserts the reply carries the number *this* crate
    /// version maps to, which is the assertion that fires the moment a release
    /// drifts from its report. What it cannot observe is the mapping itself:
    /// there is only ever one crate version at run time, so a hand-written
    /// literal equal to today's number is byte-identical to the derivation at
    /// that seam. Measured, by replacing the call site with `1500`:
    /// `cargo test --workspace` stayed green, and `cargo clippy --workspace
    /// --all-targets -- -D warnings` **failed** — `version_number` loses its
    /// only non-test caller and `dead_code` is an error under the gate. So the
    /// test suite alone cannot see it and the gate can; these cases are what
    /// make the mapping itself falsifiable rather than assumed.
    #[test]
    fn version_number_pads_semver_base_100() {
        // Each place is two decimal digits wide, so a higher version always
        // reports a higher number — which is the only property `Pv` promises.
        assert_eq!(version_number("0.0.1"), 1);
        assert_eq!(version_number("0.15.0"), 15_00);
        assert_eq!(version_number("1.2.3"), 1_02_03);
        assert_eq!(version_number("999.99.99"), 9_99_99_99);
        assert!(version_number("0.16.0") > version_number("0.15.9"));
        assert!(version_number("1.0.0") > version_number("0.99.99"));
    }

    #[test]
    fn version_number_strips_a_pre_release_suffix() {
        // Semver starts the pre-release at the FIRST hyphen, so a two-part
        // suffix strips whole. alacritty cuts at the last and mis-parses this.
        assert_eq!(version_number("0.15.0-dev"), 15_00);
        assert_eq!(version_number("1.2.3-rc.1-dev"), 1_02_03);
        assert_eq!(version_number("1.2.3+build.5"), 1_02_03);
        // The cases above cannot observe the strip at all: their suffixes carry
        // no digits, so removing the `-` break leaves the number unchanged —
        // measured, by doing exactly that and watching them stay green. A digit
        // *inside* the suffix is what the strip is for.
        assert_eq!(version_number("0.15.0-rc2"), 15_00);
        assert_eq!(version_number("1.2.3-4"), 1_02_03);
    }

    #[test]
    fn version_number_tolerates_a_short_or_odd_version() {
        // A missing component reads as zero rather than panicking, and a fourth
        // component is ignored — the report must not be able to fail.
        assert_eq!(version_number("2"), 2_00_00);
        assert_eq!(version_number("2.7"), 2_07_00);
        assert_eq!(version_number("1.2.3.4"), 1_02_03);
        assert_eq!(version_number(""), 0);
    }

    /// #661 — the wire's `i16` bound, not the region-height one.
    ///
    /// In-crate on purpose, and the reason is cost rather than visibility: reaching
    /// this through `Engine` needs a screen taller than 32 767 rows *and* 32 768
    /// scrolls of it, each rotating a `line_damage` of that length. Measured at
    /// 15.8 s in a debug build for a single assertion — the whole `serialize` suite
    /// is 0.2 s without it. See `cap_scroll`'s note for how the coverage is split.
    #[test]
    fn a_region_taller_than_the_wire_field_truncates_rather_than_wraps() {
        // 40 000 rows: over i16::MAX, under MAX_ROWS (u16::MAX), so the region
        // height alone would let 35 000 through — and 35 000 as i16 is -30 536.
        let up = cap_scroll(ScrollOp {
            top: 0,
            bottom: 40_000,
            count: 35_000,
        });
        assert_eq!(up.count, MAX_SCROLL_COUNT, "capped, and still an up-scroll");

        let down = cap_scroll(ScrollOp {
            top: 0,
            bottom: 40_000,
            count: -35_000,
        });
        assert_eq!(down.count, -MAX_SCROLL_COUNT, "sign survives the cap");
    }

    /// The cap is a ceiling, not a rewrite: a count inside both bounds is reported
    /// exactly, and the region it names is untouched.
    #[test]
    fn a_scroll_inside_both_bounds_passes_through_unchanged() {
        let op = ScrollOp {
            top: 4,
            bottom: 9,
            count: -2,
        };
        assert_eq!(cap_scroll(op), op);
    }

    /// #628 — a hyperlink's storage is released once no live row references it.
    ///
    /// In-crate on purpose: this defect has **no public observable**, which is why it
    /// survived from #46 until #621's completeness pass went looking. Pool indices never
    /// cross the wire (`Term::frame` remaps them to frame-local `link_table` positions),
    /// and the one public reader takes an index the caller already holds — so from
    /// outside the crate a pool of 5 entries and a pool of 50 000 are indistinguishable.
    /// The assertion has to stand where the storage does.
    ///
    /// The fixture is a buffer that cannot hold what it is fed: 2 rows plus 2 lines of
    /// scrollback is four lines total, so by the end all but the last four opens have
    /// been evicted and nothing on screen or in history refers to them.
    #[test]
    fn a_link_evicted_from_the_buffer_stops_being_stored() {
        let mut e = Engine::with_scrollback(20, 2, 2);
        for i in 0..50 {
            e.feed(format!("\x1b]8;;https://example.com/{i}\x07L{i}\x1b]8;;\x07\r\n").as_bytes());
        }

        // The observable had to move with the storage — there is no pool left to count.
        // A `Weak` is the stronger form of the same claim anyway: a bounded count can be
        // bounded and still wrong, while a dead `Weak` says *this exact allocation* was
        // released.
        //
        // **`e2` must outlive the assertion, and that is the whole test.** The first
        // version of this scoped the engine to the block that built the `Weak`, so the
        // engine was dropped before the check and the `Weak` died for that reason
        // instead. Measured: with a deliberate leak reintroduced (a `Vec<Arc<str>>` on
        // `Term`, retaining every open), that version stayed **green** — a tautological
        // proof, confirming only that dropping an `Engine` frees its own memory. Keeping
        // the engine alive is what makes the assertion about reclamation.
        let mut e2 = Engine::with_scrollback(20, 2, 2);
        e2.feed(b"\x1b]8;;https://example.com/first\x07L\x1b]8;;\x07\r\n");
        let weak = {
            let arc = e2
                .term
                .grid
                .row_ref(0)
                .link_at(0)
                .expect("on screen")
                .clone();
            std::sync::Arc::downgrade(&arc)
        };
        // The live half first: a fix that simply never stored the URI would satisfy the
        // dead-`Weak` assertion below for the wrong reason.
        assert!(
            weak.upgrade().is_some(),
            "the URI must be alive while its cell is on screen",
        );
        for i in 0..50 {
            e2.feed(format!("filler {i}\r\n").as_bytes());
        }
        assert!(
            weak.upgrade().is_none(),
            "the first link scrolled out of a 4-line buffer and nothing should still \
             hold its URI — before #628 every OSC 8 open lived for the life of the Term",
        );

        // The whole-buffer form of the same claim: 50 distinct opens through a buffer
        // that holds four lines leaves at most four entries *owned*.
        //
        // `owned_link_count` and not `link_at`, and that distinction is the test. The
        // first version summed the gated reader, which counts **linked cells** — measured
        // on an erased screen it read 0 while every URI was still allocated, so it could
        // not fail for the property this test exists to assert.
        // Deduped by allocation: one open covering three cells is three map entries and
        // one URI, so counting entries would fail at 9 for a buffer holding four links.
        let owned: std::collections::HashSet<*const u8> = e
            .term
            .scrollback
            .iter()
            .chain((0..2).map(|r| e.term.grid.row_ref(r)))
            .flat_map(|r| r.owned_links())
            .map(|u| std::sync::Arc::as_ptr(u) as *const u8)
            .collect();
        assert!(
            owned.len() <= 4,
            "a 4-line buffer cannot own more than 4 distinct URIs, found {}",
            owned.len(),
        );
    }

    /// #628 — erasing a cell in place releases its URI, not just its presence bit.
    ///
    /// The sibling of the eviction test above, and the case that one structurally cannot
    /// see: `clear_cells` / `free_cell` blank a cell **without dropping its row**, so no
    /// row-lifetime event fires. Under `row-keyed-side-maps` rule 3 leaving the map entry
    /// is sanctioned — *"a write that clears the cell owes the bit, not the map"* — and
    /// that was exactly right while the value was a 4-byte index: a stale entry is
    /// unreadable through the gate and costs nothing.
    ///
    /// #628 changed what the entry *is*. The map now owns a heap string, so the same
    /// sanctioned line retains one. Rule 3 still holds as stated — purging is not the
    /// correctness step, and missing a site costs bounded retention rather than a wrong
    /// answer — but the optimisation it calls optional became worth taking here.
    /// All three references release at this point: alacritty's `Cell::reset` drops the
    /// `Option<Arc<CellExtra>>` outright, ghostty's ref-counted set frees at zero, and
    /// xterm.js's `_resetBufferLine` clears `_extendedAttrs` and disposes the line's
    /// markers so `OscLinkService` deletes the entry.
    #[test]
    fn an_erased_cell_releases_its_uri_not_only_its_bit() {
        let mut e = Engine::new(80, 24);
        e.feed(b"]8;;https://example.com/erasedL]8;;");
        let weak = {
            let a = e
                .term
                .grid
                .row_ref(0)
                .link_at(0)
                .expect("on screen")
                .clone();
            std::sync::Arc::downgrade(&a)
        };
        assert!(weak.upgrade().is_some(), "alive while on screen");

        e.feed(b""); // ED 2 — erases in place; no row is dropped or reused

        // The gated reader already says "no link", and so does the frame. Neither can
        // see the retention, which is why this assertion holds the `Weak` instead:
        // measured before the purge, both public views read 0 while the URI lived.
        assert!(e.link_at(0, 0).is_none(), "the presence bit is cleared");
        assert!(
            weak.upgrade().is_none(),
            "and the URI itself is released — before the purge the map kept owning it,              so an erased screen retained every link it had shown",
        );
    }

    /// `Arc`, not `Rc`, and this is what makes that a fact rather than a comment.
    ///
    /// #628 chose `Arc<str>` for the row's link map on the stated ground that `Engine` is
    /// `Send + Sync`; `Rc` would have removed both **silently** — no signature changes
    /// here, and a downstream `Mutex<Engine>` failing to compile instead. The claim was
    /// load-bearing and unpinned: a repo-wide grep for it found only prose.
    #[test]
    fn the_engine_stays_send_and_sync() {
        fn assert_send_sync<T: Send + Sync>() {}
        assert_send_sync::<Engine>();
    }

    /// Two OSC 8 opens of an identical URI are **two links**, not one.
    ///
    /// Deliberate, and the reason is #635: merging them would override the grouping the
    /// application controls through `id=`, which is the one dedup xterm.js performs.
    /// Asserted by allocation identity through the in-crate observer rather than through
    /// a public accessor — the behaviour is real now, a consumer asking about it is not.
    #[test]
    fn two_opens_of_one_uri_are_two_links() {
        let mut e = Engine::new(40, 2);
        // One open covering two cells, then a *separate* open of the very same URI.
        e.feed(b"]8;;https://example.com/xAB]8;;");
        e.feed(b"]8;;https://example.com/xC]8;;");

        let row = e.term.grid.row_ref(0);
        let ptr = |c: usize| std::sync::Arc::as_ptr(row.link_at(c).expect("linked")) as *const u8;
        assert_eq!(
            e.link_at(0, 0).map(|h| h.uri().to_owned()),
            e.link_at(0, 2).map(|h| h.uri().to_owned()),
            "the text is the same",
        );
        assert_eq!(ptr(0), ptr(1), "A and B are one open, so one allocation");
        assert_ne!(
            ptr(0),
            ptr(2),
            "…but C is a second open — merging the two would override the distinction              `id=` exists to express (#635)",
        );
    }

    /// The other half of the rule above: an `id=` the application declared **does** group
    /// (#635). One rule, not two — "never merge on URI alone, always merge on a declared
    /// id" is how xterm.js states it (`OscLinkService.ts:34`, `:51` at the pinned SHA), and
    /// justerm shipped the first half only because #26 ported `registerLink`'s id-minting
    /// and not its lookup.
    ///
    /// Grouping is asserted as **allocation identity**, which is not an implementation
    /// detail leaking into a test: since #628 the `Arc`'s address *is* link identity —
    /// `Term::frame` interns `link_table` by `Arc::as_ptr`, so one allocation is what makes
    /// two runs one link index on the wire, and that index is what a consumer groups by.
    #[test]
    fn the_same_id_and_uri_group_into_one_link() {
        let mut e = Engine::new(40, 2);
        // Two separate opens, same `id=` and same URI, on two different lines — the case
        // the parameter exists for (a link that cannot be one contiguous run).
        e.feed(b"\x1b]8;id=xyz;https://example.com/a\x07A\x1b]8;;\x07\r\n");
        e.feed(b"\x1b]8;id=xyz;https://example.com/a\x07B\x1b]8;;\x07");

        let ptr = |r: usize, c: usize| {
            std::sync::Arc::as_ptr(e.term.grid.row_ref(r).link_at(c).expect("linked")) as *const u8
        };
        assert_eq!(
            ptr(0, 0),
            ptr(1, 0),
            "the application said these two runs are one link, so they share one allocation",
        );

        // And the wire agrees, which is the half a consumer can actually see: one entry in
        // `link_table`, referenced by both spans. Two entries is the defect.
        let f = e.frame();
        assert_eq!(f.link_table.len(), 1, "one link ships once");
    }

    /// Keyed on `id` **and** URI, not on `id` alone — xterm.js's `_getEntryIdKey` is
    /// `` `${id};;${uri}` `` (`OscLinkService.ts:87`). An application reusing an id for a
    /// different target has not said "same link"; treating it as one would follow a stale
    /// declaration to the wrong URI.
    #[test]
    fn the_same_id_with_a_different_uri_stays_two_links() {
        let mut e = Engine::new(40, 2);
        e.feed(b"\x1b]8;id=xyz;https://example.com/a\x07A\x1b]8;;\x07\r\n");
        e.feed(b"\x1b]8;id=xyz;https://example.com/b\x07B\x1b]8;;\x07");

        let ptr = |r: usize, c: usize| {
            std::sync::Arc::as_ptr(e.term.grid.row_ref(r).link_at(c).expect("linked")) as *const u8
        };
        assert_ne!(
            ptr(0, 0),
            ptr(1, 0),
            "same id, different target — two links"
        );
        assert_eq!(e.frame().link_table.len(), 2, "and both ship");
    }

    /// `id=` with an **empty value** is no id at all, so the no-id rule applies and each
    /// open is its own link. xterm.js reaches this by `parsedParams[i].slice(3) || undefined`
    /// (`InputHandler.ts:3130`) — the `||` is the whole behaviour, and reading `slice(3)`
    /// alone gives the opposite answer.
    ///
    /// Worth a test rather than a comment because the empty-string key is the one that
    /// would group *every* `id=`-with-no-value link in a session into one, across unrelated
    /// URIs — a wrong answer that grows with uptime.
    #[test]
    fn an_empty_id_value_is_no_id_at_all() {
        let mut e = Engine::new(40, 2);
        e.feed(b"\x1b]8;id=;https://example.com/a\x07A\x1b]8;;\x07\r\n");
        e.feed(b"\x1b]8;id=;https://example.com/a\x07B\x1b]8;;\x07");

        let ptr = |r: usize, c: usize| {
            std::sync::Arc::as_ptr(e.term.grid.row_ref(r).link_at(c).expect("linked")) as *const u8
        };
        assert_ne!(
            ptr(0, 0),
            ptr(1, 0),
            "no id declared, so the reference-correct fresh-per-open rule still holds",
        );
    }

    /// `params` is a **`:`-separated** key=value list (`id=xyz123:foo=bar:baz=quux`), and
    /// `id` may sit anywhere in it — xterm.js scans with `findIndex(e =>
    /// e.startsWith('id='))` (`InputHandler.ts:3129`). Testing only a leading `id=` would
    /// pass with a `starts_with` on the whole field, which is the wrong parse.
    #[test]
    fn the_id_param_is_found_among_other_params() {
        let mut e = Engine::new(40, 2);
        e.feed(b"\x1b]8;foo=bar:id=xyz:baz=quux;https://example.com/a\x07A\x1b]8;;\x07\r\n");
        e.feed(b"\x1b]8;id=xyz;https://example.com/a\x07B\x1b]8;;\x07");

        let ptr = |r: usize, c: usize| {
            std::sync::Arc::as_ptr(e.term.grid.row_ref(r).link_at(c).expect("linked")) as *const u8
        };
        assert_eq!(
            ptr(0, 0),
            ptr(1, 0),
            "the id is the same whatever else rides beside it",
        );
    }

    /// The grouping registry must not become the pool #628 deleted.
    ///
    /// Whatever maps an `id=` to its link has to hold it **weakly**: a strong reference
    /// would make every id'd link immortal for the life of the `Term` — the exact defect
    /// #628 removed, re-entering through the door #635 opens. xterm.js's equivalent map is
    /// reclaimed rather than weak (`_entriesWithId.delete` when the entry's last line
    /// marker is disposed, `OscLinkService.ts:98-100`); justerm has no disposal hook by
    /// design, so `Weak` is how the same lifetime is expressed here.
    ///
    /// This is the test that discriminates the two, and nothing public can: both spellings
    /// group correctly, and they differ only in what stays alive afterwards.
    #[test]
    fn the_id_registry_does_not_keep_a_link_alive() {
        let mut e = Engine::new(80, 24);
        e.feed(b"\x1b]8;id=xyz;https://example.com/grouped\x07L\x1b]8;;\x07");
        let weak = {
            let a = e
                .term
                .grid
                .row_ref(0)
                .link_at(0)
                .expect("on screen")
                .clone();
            std::sync::Arc::downgrade(&a)
        };
        assert!(weak.upgrade().is_some(), "alive while on screen");

        e.feed(b"\x1b[2J"); // ED 2 — the in-place erase that releases the row's side maps

        assert!(
            weak.upgrade().is_none(),
            "the id registry must hold a Weak — a strong entry would outlive the screen and              rebuild #628's leak one id at a time",
        );
    }
}