{
  "context": "Evaluates whether the workflow uses Luigi's parameter system to expose typed CLI flags that integrate with config files while keeping resolved values consistent across tasks. Scoring focuses solely on correct Luigi API usage for parameters, config precedence, propagation, and validation as described in the spec.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Typed params",
      "description": "Defines source_dir with luigi.Parameter/PathParameter, process_date with luigi.DateParameter, stores with luigi.ListParameter/TupleParameter, and min_units with luigi.IntParameter so they surface as the hyphenated CLI flags in the spec and use sensible defaults.",
      "max_score": 25
    },
    {
      "name": "Config defaults",
      "description": "Loads defaults for all parameters from the `[InventorySnapshot]` section of inventory.cfg using Luigi configuration helpers (e.g., Config class or luigi.configuration.get_config) instead of manual file parsing.",
      "max_score": 20
    },
    {
      "name": "CLI precedence",
      "description": "Runs the pipeline via luigi.run/luigi.build so CLI arguments override config values, confirming flags like --process-date, --stores, and --min-units drive the resolved parameters and manifest output even when config specifies different values.",
      "max_score": 20
    },
    {
      "name": "Propagation",
      "description": "Implements requires/output/run so InventorySnapshot passes its parameters to LoadDailyOrders using Luigi mechanisms (e.g., self.clone or explicit parameter wiring) rather than ad-hoc globals, keeping upstream outputs aligned with resolved parameters.",
      "max_score": 20
    },
    {
      "name": "Validation errors",
      "description": "Relies on Luigi parameter validation to reject malformed dates like 15-03-2024 (raising ValueError/ParameterException) while accepting ISO-formatted values and reflecting them verbatim in outputs.",
      "max_score": 15
    }
  ]
}