/* ============================================================
   Hifzhelper — Haidh calendar (V3.39)
   ============================================================ */

/* V3.44: the screen-level width cap that used to live here is REMOVED
   entirely, confirmed in chat -- #screen-haidhDetail is never
   independently capped now, it's just another --surface-track screen
   (css/base.css's universal .screen rule). This was also the screen
   whose calendar was confirmed via screenshot to render completely
   unrestricted at wide desktop widths -- root cause not fully
   explained, but this removes the mechanism entirely rather than
   patching it: the calendar content below is now wrapped in a new
   .screen-content div (index.html) with its own explicit 30/50 cap,
   independent of whatever was going wrong with this rule. */

.haidh-cal-nav {
  display: flex;
  align-items: center;
  justify-content: space-between;
  margin: var(--space-md) 0 var(--space-sm);
}
.haidh-cal-nav #haidhCalMonthLabel {
  font-weight: 700;
  color: var(--color-ink);
}
.haidh-cal-prev svg { transform: rotate(90deg); }
.haidh-cal-next svg { transform: rotate(-90deg); }

.haidh-cal-weekdays {
  display: grid;
  grid-template-columns: repeat(7, 1fr);
  text-align: center;
  font-size: 11px;
  color: var(--color-ink-faint);
  margin-bottom: var(--space-xs);
}

.haidh-cal-grid {
  display: grid;
  grid-template-columns: repeat(7, 1fr);
  gap: 4px;
}

.haidh-cal-day {
  aspect-ratio: 1;
  border: 1px solid var(--color-table-border);
  border-radius: var(--radius-sm);
  background: var(--color-surface);
  color: var(--color-ink);
  font: inherit;
  font-size: 13px;
  cursor: pointer;
}
.haidh-cal-day-muted { color: var(--color-ink-faint); background: var(--color-page-bg); }
.haidh-cal-day-today { border-color: var(--color-accent); border-width: 2px; }

/* Confirmed/actual haidh — full shade. Planned/predicted — lighter
   shade (confirmed in chat: visually distinct, using the existing
   predicted-haidh status). No difference once a planned day auto-
   resolves — that's a backend/attendance distinction, not a visual one
   here; a day only ever shows "planned" while it's still genuinely in
   the future. */
.haidh-cal-day-confirmed {
  background: var(--color-haidh);
  border-color: var(--color-haidh);
  color: #FFFFFF;
}
.haidh-cal-day-planned {
  background: var(--color-haidh-soft);
  border-color: var(--color-haidh-soft);
  color: var(--color-ink);
}

/* V3.40.2: a pending, not-yet-saved range being built via tap-first/
   tap-last -- deliberately a 3rd, distinct color (accent, not haidh's
   own mauve) so a still-editable selection never looks like it's
   already saved. Comes after -confirmed/-planned so it wins visually
   if a pending selection is ever built over an already-marked day
   (shouldn't normally happen -- see js/haidhDetailScreen.js -- but
   kept defensive rather than assuming it can't). */
.haidh-cal-day-selecting {
  background: var(--color-accent-soft);
  border-color: var(--color-accent);
  color: var(--color-ink);
}

.haidh-range-bar {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--space-sm);
  margin: var(--space-sm) 0;
  padding: var(--space-sm) var(--space-md);
  background: var(--color-accent-soft);
  border-radius: var(--radius-sm);
}
.haidh-range-bar-actions { display: flex; gap: var(--space-sm); flex: 0 0 auto; }
.haidh-range-confirm-btn, .haidh-range-cancel-btn {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  border-radius: 999px;
  font: inherit;
  font-size: 13px;
  padding: 8px 16px;
  cursor: pointer;
}
.haidh-range-confirm-btn svg, .haidh-range-cancel-btn svg {
  width: 14px;
  height: 14px;
  flex: 0 0 auto;
}
.haidh-range-confirm-btn {
  border: none;
  background: var(--palette-evergreen);
  color: white;
}
.haidh-range-cancel-btn {
  border: 1px solid var(--color-table-border);
  background: transparent;
  color: var(--color-ink-soft);
}