[epistrephein]

Numeric datatype ranges lose their base datatype and earlier bounds during extraction, so generated documentation shows only the final constraint. For example, an integer range from 1 to 3 appears as "≤ restricted by 3".

The failing OWL statement (from monomyth ontology) that triggered this bugfix is

monomyth:actOrder a owl:DatatypeProperty,
        owl:FunctionalProperty ;
    rdfs:label "act order"@en ;
    rdfs:comment """The sequential position of an act in the three-act structure (1-3)."""@en ;
    rdfs:domain monomyth:Act ;
    rdfs:range [
        a rdfs:Datatype ;
        owl:onDatatype xsd:integer ;
        owl:withRestrictions (
            [ xsd:minInclusive 1 ]
            [ xsd:maxInclusive 3 ]
        )
    ] .

The bugfix crosses three layers:

• Model: stored only one facet value while a range needs the datatype plus multiple paired constraints, such as >= 1 and <= 3. It now stores the base datatype separately from all facet/value pairs.
• Reader: overwrote the datatype with each operator and overwrote the previous bound. It now preserves every constraint without overwriting the datatype or previous bounds.
• Viewer: now renders the complete range, such as integer[>= 1, <= 3].

---

Screenshots: 🖼️ main | 🖼️ this PR