/* ============ SHARED CHROME-MOUNT TIER (chromemount.css) ============
   Every page mounts the shared Nav chrome with <dc-import name="Nav">. Until that child
   component's own markup has loaded, the runtime paints a streaming SKELETON in the mount's
   place: a .sc-placeholder box carrying a 1px 50%-ink border. At the Nav mount's hint size
   that box collapses to a full-width, 2px-tall strip pinned near the top of the page -- i.e.
   a stray dark hairline that hangs across the ARRIVING page for as long as the child DC
   takes to load (a second or two on a cold navigation), then vanishes when Nav renders.
   That is what the "random line after Work -> Expertise" was: not a leftover from the page
   you left (a navigation tears the whole document down, nothing survives it) but the
   arriving page's own loading skeleton for its chrome mount.

   This is a FINISHED site loaded from files, not an authoring session: every value a hole or
   a list needs resolves in the same tick the markup arrives, so a loading skeleton has nothing
   to communicate and can only flash. So the rule is unconditional and unscoped -- no skeleton
   box paints anywhere, at any viewport, whatever the runtime nests it in. .sc-placeholder-error
   is deliberately NOT hidden, so a genuine load failure still reports itself.

   The rule also exists as a paint-time literal inside every page's inline <style> (same
   pattern as Nav's paint-time button fallbacks): the skeleton is in the DOM from the first
   frame, which is earlier than an external sheet can land. This file stays the source of
   truth; the inline copies are fallbacks and must stay identical to it.

   Linked from every page's helmet. */
.sc-placeholder{display:none!important}