/*
 * A boundary is a plain box that happens to be measured, so it states the layout
 * every caller wrote against and nothing else: the `View` column it replaced.
 * The height, the width and the flex behaviour stay the caller's — a boundary
 * that sized itself would decide the very thing it exists to report.
 */
@layer theme, base, lotics, components, utilities;
@layer lotics.tokens, lotics.reset, lotics.components;

@layer lotics.components {
  .lotics-size-boundary {
    /* The CSS half of the same fact (`constitution.md` §10): a rule inside asks
       `@container lotics-boundary (…)` and gets this box, the way a component
       inside asks `useContainerSize()`. Which is why a boundary may only wrap a
       box that OWNS its width — inline-size containment zeroes what the contents
       contribute, and a shrink-wrapped parent collapses around it. */
    container: lotics-boundary / inline-size;
    display: flex;
    flex-direction: column;
    align-items: stretch;
    position: relative;
    min-width: 0;
    min-height: 0;
    flex-shrink: 0;
  }
}