//! Admitted candidates for the layout seams, committed byte for byte as the model
//! returned them (`roadmap.md` -> "Decisions", "Admitted candidates are committed into the
//! engine's source tree"). Each file's header names the provenance record beside it
//! (`docs/provenance.md`). `stacking` is the one seam whose output is an ordering rather
//! than geometry; `crate::paint_order` runs it over the fragment tree the others produce.
//!
//! `height` is the one file here that did not come from a model batch: it holds the
//! hand-written rule `crate::fragment` ran inline before `specs/block-height-equation.md`
//! extracted it, committed as this seam's starting candidate because it is already correct
//! by construction. A model candidate replaces it only by scoring strictly higher
//! (`generation::admit::beats_committed`), which is the same gate every other file here is
//! held to -- only the incumbent differs.
//!
//! `inline_atomic` starts from its own function's deliberately wrong baseline too -- one
//! atomic inline per line, stacked down the container's left content edge, which is what
//! the engine did for a `display: inline-block` box before `crate::inline_atomic`
//! existed. Its header says `hand-written` and its verification counts are zero for that
//! reason; the first model candidate to score above it replaces it through the same gate
//! every other file here is held to.
//!
//! `table` starts from its own function's two deliberately wrong baselines, for the same
//! reason `inline_atomic` did: every column as wide as the whole table and every cell
//! stacked under the one before it, which is what the engine did with a `display:
//! table-cell` box before `crate::table` existed. Its header says `hand-written` and its
//! verification counts are zero for that reason; the first model candidate to score above
//! it replaces it through the same gate. It is the one file here holding two exported
//! functions whose answers are independent -- `columns` and `rows`, split on the axis CSS
//! 2.1 17.5.2.1 splits the algorithm on -- the way `margin` holds `classify` and
//! `combine`.
//!
//! `overflow` starts from its seam's deliberately wrong baseline -- no box ever scrolls,
//! what the engine did before the seam existed -- rather than from a model batch or a
//! correct-by-construction rule. Its header says `hand-written` and its verification
//! counts are zero for exactly that reason; the first model candidate to score above it
//! replaces it through the same gate.

pub mod absolute;
pub mod containing_block;
pub mod float;
pub mod height;
pub mod inline_atomic;
pub mod margin;
pub mod overflow;
pub mod percentage;
pub mod relpos;
pub mod stacking;
pub mod table;
pub mod transform;
pub mod width;