{
  "context": "Evaluates how well the solution leverages the lunar_python Gregorian utilities to detect leap years, surface official festivals, and honor China-specific workday/holiday rules while navigating dates. Focus is entirely on calling the package APIs for data and movement rather than reimplementing calendar logic.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Leap year API",
      "description": "Uses the package’s leap-year logic (e.g., SolarUtil.isLeapYear or Solar.isLeapYear on a Solar instance) instead of custom arithmetic to implement is_leap_year and returns correct booleans for the test years.",
      "max_score": 15
    },
    {
      "name": "Festival lookup",
      "description": "festivals_on builds its results from the package’s official data (Solar.getFestivals plus getOtherFestivals or SolarUtil FESTIVAL tables), deduplicates and sorts the names, and returns the expected entries such as “国庆节” for 2024-10-01 and “春节” for 2024-02-12.",
      "max_score": 25
    },
    {
      "name": "Workday status",
      "description": "is_workday relies on the package’s workday/holiday data (HolidayUtil.getHoliday/getHolidays or equivalent) so that statutory make-up days like 2024-02-18 are treated as workdays and festival days like 2024-02-12 are treated as non-workdays.",
      "max_score": 20
    },
    {
      "name": "Workday navigation",
      "description": "next_workday advances via package-aware navigation (Solar.next with only_work_day=True or equivalent) to skip weekends and statutory holidays, producing correct destinations such as 2024-02-18 from 2024-02-12 for a single workday jump and honoring multi-day offsets.",
      "max_score": 25
    },
    {
      "name": "Solar date usage",
      "description": "Date parsing and formatting use Solar.fromYmd/fromDate plus package string helpers (toYmd/toYmdHms or Solar properties) so returned dates stay canonical YYYY-MM-DD values without manual string math.",
      "max_score": 15
    }
  ]
}