[havs-mc]

Description

IDS values are text, but IDSSpecifications.xmlParser parses numeric-looking values (parseAttributeValue: true, numberParseOptions: { leadingZeros: true, hex: true }). <simpleValue>01</simpleValue> becomes 1, an enumeration value 007 becomes 7, and 1e3 becomes 1000. The string fallback from #731 then compares "1" with the model's "01" and fails. Numbers are also compared exactly, so 0.1 + 0.2 doesn't match 0.3. That accounts for the tolerance disagreements listed in #831.

• The parser keeps tag and attribute values as text.
• evalRequirement compares simple and enumeration values by the type of the model value. Strings compare as text. Numbers compare within the IDS tolerance v ± (|v|·1e-6 + 1e-6) (tolerance.md). Values exactly on those bounds pass, as the test cases expect, and a tiny relative margin absorbs double rounding. xs: range restrictions stay exact, as that document requires. Booleans compare as xs:boolean (true/1, false/0).
• Bound and length limits are converted with Number() in importers/parameter.ts, since they are no longer parsed.
• The IDS wrong auto conversion #731 workaround in IDSProperty.evalValue is no longer needed and is removed.

Additional context

• buildingSMART implementer test cases (TestCases/tolerance): 36 of 36 agree (22 on main). Across all 307 non-invalid- cases, 14 more agree and none stops agreeing.
• New facets/value-comparison.test.ts: loading keeps 01, 007 and 1e3 as written; leading zeros; bound and xs:length limits; tolerance, including values on the bounds; booleans; enumerations.
• vitest --run (IDS folder) passes and tsc -p tsconfig-build.json --noEmit is clean.
• We've run the equivalent change as a local patch against two production models (≈30 600 and ≈55 400 checks), and the results match IfcTester.
• Overlap: fix(ids): apply optional and prohibited cardinality to the property facet as a whole #822 also edits Property.ts, around the IDS wrong auto conversion #731 workaround this PR removes. The textual conflict is small; I'm happy to rebase whichever lands second.
• Related: IDS can't check the numbers as string (IFCTEXT) #634, IDS wrong auto conversion #731, IDS conformance: status against buildingSMART's implementer test cases, and what is left #831 (tolerance).

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following:

• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Follow the Conventional Commits v1.0.0 standard for PR naming.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves.
• Ideally, include relevant tests that fail without this PR but pass with it.

🤖 Generated with Claude Code