exegetical-noteslisted

# Exegetical Notes ## Purpose Produce structured, context-neutral exegetical analysis of a biblical passage. Data-grounded. Always English. Output to file (default) or inline (`--output print`). **Key constraint:** Every data claim must come from bundled data or web-verified scholarly sources. Training knowledge supplements but never substitutes for data. --- ## Iron Rules ### Rule 1: Run Pericope Check First — Warning BEFORE Notes Before generating notes, run a lightweight boundary check: 1. Identify passage boundaries 2. Check Levinsohn (NT) or Masoretic (OT) for boundary confirmation 3. **If boundaries are problematic:** Print the warning BEFORE the notes header. The warning is a standalone block that appears BEFORE `# Exegetical Notes:`. Do not embed it inside Section 1. Do not skip it. 4. **If user confirms problematic passage:** Proceed with note in Pericope Status **Warning format (print this BEFORE the notes):** ``` ⚠️ Boundary check: [Book] [Range] may be a partial unit. [Specific issue with discourse evidence] Recommended passage: [better range] Proceeding with [original range] — boundary issue noted in Pericope Status. ``` **Correct output order for problematic boundaries:** 1. First: ⚠️ Boundary check warning (standalone) 2. Then: `# Exegetical Notes: [Book] [Range]` header and all 10 sections **Wrong:** Embedding the boundary warning inside Section 1 without a standalone warning first. ### Rule 2: Lexical Analysis Uses query_morphology MCP Tool Sect