{
  "context": "Checklist focuses on using lunar_python's solar/lunar construction and conversion APIs, including Julian day handling and leap-month awareness. It rewards direct use of the library instead of reimplementing calendar math.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Solar creation",
      "description": "Gregorian inputs are built via `Solar.fromYmdHms` (or `Solar.fromYmd` when seconds are zero) so that year/month/day and HH:MM:SS come from the library, not manual arithmetic.",
      "max_score": 20
    },
    {
      "name": "Solar to lunar",
      "description": "Solar instances convert to lunar through `Solar.getLunar()` with lunar year/month/day and time read from that result rather than recomputed, satisfying the 2023-01-22 expectation.",
      "max_score": 20
    },
    {
      "name": "Leap lunar to solar",
      "description": "Leap-month scenario uses `Lunar.fromYmdHms(..., isLeapMonth=True)` (or equivalent leap flag) to create the date, verifies `Lunar.isLeapMonth()` on the lunar side, and converts to Gregorian via `Lunar.getSolar()`.",
      "max_score": 25
    },
    {
      "name": "Julian day",
      "description": "Julian day flow relies on `Solar.fromJulianDay` to instantiate and `Solar.getJulianDay()` (or equivalent getter) for the reverse check, matching the 2459215.5 round-trip.",
      "max_score": 20
    },
    {
      "name": "Round-trip check",
      "description": "Solar ↔ lunar round-trip correctness is asserted using `getLunar()` and `getSolar()` outputs (no manual date math) to prove 2017-09-30 23:59:59 survives conversion unchanged.",
      "max_score": 15
    }
  ]
}