Build RoadRunner Scenario from OpenSCENARIO

Interpret an OpenSCENARIO 1.x (.xosc) file and recreate the scenario in RoadRunner using the roadrunner-scenario-authoring skill. Translates positions, maps constructs, preserves relative references, and builds correct phase logic.

When to Use

• User has a .xosc file and wants to recreate it in RoadRunner
• User wants to programmatically build a scenario from OpenSCENARIO
• User says "build this .xosc in RoadRunner" or "recreate this scenario"
• User has an OpenSCENARIO file from a partner or standards body (e.g., Euro NCAP, ALKS)
• User wants to generate a MATLAB script from a .xosc file
• User says "convert this xosc to matlab" or "recreate with a matlab script"

When NOT to Use

• User says "import" a .xosc file, they want importScenario(rrApp, xoscPath), not this skill. Simply call the API directly.
• User wants to use RoadRunner's built-in importScenario (let them, it works for simple cases)
• User wants to create a scenario from scratch without a .xosc file (use roadrunner-scenario-authoring)
• User wants to export a scenario TO OpenSCENARIO (use roadrunner-export-scenario)

Critical Rules

1. Never fabricate actions or conditions not present in the source XOSC. If a construct cannot be mapped, skip it and warn the user.

2. Never propose workarounds. Do not replace DistanceToPointCondition with DurationCondition, do not substitute SimulationTimeCondition for unsupported triggers, do not add any construct not in the source.

3. Never simplify or duplicate trajectory vertices. Extract exactly the polyline vertices present in the source XOSC, no fewer, no more. Do not reduce 90 vertices to 5. Do not duplicate start/end points during extraction.

4. Never guess scenes. Only report the .xodr filename from <LogicFile>. Import it, do not search for a scene with a similar name.