{
  "parse_status": "pass",
  "overall_verdict": "supports_with_required_corrections",
  "confidence": "high",
  "findings": [
    {
      "severity": "medium",
      "issue": "cross_platform_prompt_alignment_matrix schema lacks explicit field definitions; the contract states all required artifacts have explicit field definitions, but this matrix is only described in prose without a bullet list of required fields.",
      "recommendation": "Add a dedicated bullet list of required fields (e.g., alignment_row_id, source_scene_id, source_shot_id, dramart_preview_packet_id, seedance_preview_packet_ids, ledger_mention_ids, unresolved_mention_count, unsupported_risky_field_count, source_trace_refs, review_status) under the 'Required Output Schemas' section to match the level of detail provided for other artifacts."
    },
    {
      "severity": "low",
      "issue": "adapter_entity_mention_ledger schema is not formalized as a distinct entry in the 'Required Output Schemas' section; its fields are described later but not listed with the same clarity as other artifacts.",
      "recommendation": "Either add a bullet list of required ledger fields (local_entity_key, entity_display_name, mention_token, source_scene_packet_id, etc.) to the 'Required Output Schemas' section or explicitly reference the 'Adapter Entity Mention Ledger' subsection as the normative schema definition."
    },
    {
      "severity": "low",
      "issue": "forbidden_side_effect_counters set is not explicitly defined within the contract; the validators and gate schema refer to these counters, but the exact list of counter names is only partially implied by the fresh run gate and the contract text.",
      "recommendation": "Include the complete set of forbidden counter names (e.g., from the fresh run gate's forbidden_side_effect_counters) as an explicit reference or enumerated list in the contract to ensure consistent validation across all outputs."
    },
    {
      "severity": "low",
      "issue": "public_review_page_contract required_markers (review_only=true, etc.) are described as boolean flags, but the method of embedding them in the generated HTML or page contract is ambiguous (JSON fields vs. HTML meta tags vs. visible text), risking inconsistent enforcement of the no-production markers.",
      "recommendation": "Specify the exact representation: whether these markers must appear as HTML meta tags with defined names, as JSON fields in the page contract, or as mandatory visible text blocks in the HTML body."
    },
    {
      "severity": "low",
      "issue": "advisory use of NOW-37 and NOW-38 artifacts is permitted but not bounded to specific file paths or schemas; this could allow inclusion of advisory data that exceeds the intended scope.",
      "recommendation": "List the allowable NOW-37 and NOW-38 artifact paths (or schema identifiers) explicitly, and reiterate that only advisory schema structure may be referenced, not execution data or writeback-authoritative fields."
    }
  ],
  "required_corrections": [
    "Add explicit required fields for cross_platform_prompt_alignment_matrix to the 'Required Output Schemas' section, with field names, descriptions, and types to match the other artifact definitions (e.g., alignment_row_id, source_scene_id, source_shot_id, dramart_preview_packet_id, seedance_preview_packet_ids, ledger_mention_ids, unresolved_mention_count, unsupported_risky_field_count, source_trace_refs, review_status).",
    "Formalize the adapter_entity_mention_ledger schema: either add its required fields to the 'Required Output Schemas' section as a bullet list, or add a clear reference stating that the 'Adapter Entity Mention Ledger' subsection defines the complete schema with fields such as local_entity_key, entity_display_name, mention_token, source_scene_packet_id, etc."
  ],
  "remaining_high_or_blocker_count": 0
}