usecase-extractorlisted

# Use Case Extractor Transform requirements documents and functional specifications into structured, role-based use case documentation following established business-analysis practice. ## Languages Source and output languages are independent: a source may be in any language, and several sources may each be in a different one. - **Output language**: whatever the request states. When the request states none, ask in Step 2 and apply this default to a reply that still does not choose: the language of the request if that is Italian or English, Italian otherwise. User-facing messages always follow the language of the request, including Step 2's question. - **Written in the output language**: section headings, sheet names, field labels, priority values, the Coverage Assessment value, the five relationship-type words, and the flagged-item categories — one fixed term per relationship type across the whole document, listed in a legend: the Appendix in the document formats, under the dependencies matrix in the Excel workbook. - **Kept in the source language**: the `Source` citation, which quotes the document's own section wording and identifier. The `(inferred)` marker beside it is the analysis's own annotation rather than part of the quotation, so it follows the output language. - **Translated with the source term kept**: the document's own vocabulary — entity, status, screen, and field names — written as the output-language term with the source's term in pare