Function propose_depth 

pub fn propose_depth(
    table: &CostTable,
    cal: &AcceptanceCalibration,
    n: usize,
    slack: f64,
    mtp_max_seqs: usize,
) -> usize

2026-10-04: The propose depth for a batch of n sequences: see the module doc. slack is --spec-cost-slack, in 0..1. A table without depth 1 has no reference rate, so its constraint is against depth 0. mtp_max_seqs is the serve’s own dispatch cap (sched.levers.mtp_max_seqs, SSOT — never a restated default here); n > mtp_max_seqs returns 0 without consulting the table (see the module doc). Within the cap the search can also return 0 on its own terms (a draft row that costs a whole step — see the no_drafting_when_it_is_neither_faster_nor_cheaper test) — the two 0s mean different things to a caller that is not wired to suspend MTP from the table’s energy preference alone: it must re-check the cap itself to tell them apart (mtp_step.rs does).