Repository navigation
Preserve XMILE namespace boundaries and update engine comparison - #11
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
XMILE import previously discarded namespace URIs, allowing a foreign equation to shadow core mathematics and a foreign auxiliary to become executable. The scalar parser now selects one supported root vocabulary and rejects unsupported foreign or mixed material with bounded, actionable errors before saving.
OASIS, legacy and namespace-free scalar profiles, prefix aliases, known editor annotations, standard non-executing XML/schema hints, Stock & Flow provenance, retained MDL source, seeds, tables and geometry keep their supported behavior. The ordinary Model response is preserved. The public validation receipt binds the reviewed parser; all 996 model definitions and other engine modules are unchanged.
The existing engine comparison document is updated with current matched Euler/RK4 receipts, bounded feature comparisons and rejected optimization measurements. It distinguishes our historical own-baseline improvements from Simlin's faster measured scalar execution, and makes no overall speed, completeness or general XML losslessness claim.
Validation: 3,146 tests passed, with three expected failures and 18 passing subtests (369.57s). Real local HTTP/SSE/stdio MCP checks passed with 996-model inventory. Four XML profiles passed actual HTTP import/export/reload in a temporary file-backed store with exact seeded outputs and provenance; four unsupported uploads returned 400 without saving. No production deployment performed.