/* Teams-specific UI overrides.
   Applied only when the <html> element carries the .in-teams class,
   which teams.js stamps as soon as microsoftTeams.app.initialize() confirms
   we are running inside a Teams frame.

   Rules are intentionally kept minimal — hide chrome that is either
   redundant (logout is handled by Teams itself) or disruptive (cross-tab
   navigation from within a pinned Teams tab). */

/* ── All pages ─────────────────────────────────────────────────────────── */

/* Logout is managed by Teams; the link is useless and confusing inside a tab. */
.in-teams .logout-btn {
  display: none;
}

/* ── Module pages (pipeline-tracker, poker, admin) ─────────────────────── */

/* The breadcrumb back-link navigates to the hub homepage — fine in a browser,
   wrong inside Teams where each module is a separate pinned tab. Hide both
   the link and the "/" separator that follows it. */
.in-teams .back-link,
.in-teams .header-sep {
  display: none;
}

/* ── Homepage ───────────────────────────────────────────────────────────── */

/* The modules widget is a launcher for other pages. Inside Teams each module
   has its own tab, so this widget serves no purpose and wastes screen space. */
.in-teams #widget-modules {
  display: none;
}

/* With modules gone the sidebar has nothing to show. Collapse it so the
   calendar and Redmine widgets expand to fill the full page width.
   Announcements are still surfaced by hub-alert-ribbon at the top of the page. */
.in-teams .hub-sidebar {
  display: none;
}

.in-teams .hub-grid {
  grid-template-columns: 1fr;
}
