/* ============================================================
   pag-flow.css — ONE rule, and it has to load where it does.

   v4.7's markup is ordinary block flow. An Elementor container is a flex
   column, which does not collapse margins, ignores text-align on inline
   children and stretches every child to the full width. Measured against
   v4.7 that difference alone accounted for most of the height the built
   page had gained, and for the hero mark sitting left instead of centred.

   Every container the build creates carries `pag-flow`, so this puts them
   back into block flow. It is a separate file purely so it can be enqueued
   BETWEEN Elementor's frontend CSS and v4.7's own stylesheets: loaded here
   it beats `.e-con{display:var(--display)}`, and every rule in pag-base and
   pag-components — .s-hero__cta, .cap-grid, .grid, .s-who__col and the rest
   — still beats IT, so a container v4.7 really does flex or grid is
   untouched. Load it any later and it would flatten those too.

   To give one container Elementor's own flex behaviour back, delete
   `pag-flow` from its CSS Classes in the panel.
   ============================================================ */
.pag-flow{
  display:block;
  flex-direction:row;
  align-items:normal;
  justify-content:normal;
  gap:normal;
  /* Elementor pins every container to min-width:0, which stops a grid track
     ever growing to its content. v4.7 depends on the browser default: at 360px
     the About masthead's nowrap button widens its column, and the heading fits
     two lines instead of three because of it. Reset here rather than in the
     bridge so v4.7's own `min-width:0` — which it sets by hand on
     .s-execution__map, .cap-stage and .exec-step — still wins. */
  min-width:auto;
}