MoTeC MCP 0.2.0

MoTeC MCP 0.2.0

Release date: 2026-07-13

Highlights

• Adds bounded offline workspace intelligence, exact snapshot identities, semantic comparison/query support, safer path handling, and deterministic output limits.
• Adds portable reduced/full install readiness, shared setup/verification contracts, exact missing-input questions, CI, and release gates.
• Adds whole-vehicle product/workflow registries, vehicle-system profiling, end-to-end signal-path analysis, CAN/system fault isolation, staged commissioning and I/O test planning, and evidence-led dyno/rolling-road planning.
• Adds installed local-help indexing and version/authority boundaries without copying proprietary manuals into the repository.
• Adds PDM Manager action classification and live read-only workflow correlation, with Monitor, Get Configuration and Test Outputs represented as authorizable operations after their exact connected-safety gates.
• Adds Display Creator DBC-backed build planning, strict full-dashboard design validation, operation classification, alarms/navigation/simulation/acceptance planning, and improved live tab/page-tree evidence capture.
• Adds AiM official-source metadata, Race Studio operation classification, an M800-to-MXG integration planner, exact bounded ECU-protocol XML analysis, and path-free read-only Race Studio database schema/count analysis.
• Records a disposable MXG 1.3 Strada Race Studio learning sweep while explicitly preventing generic M8XX or Evo X-labelled protocol choices and editor defaults from becoming Evo target recommendations.
• Adds configured-root file routing and a guarded preview/execute launch pair for
  ECU Manager .e30-.e35, Display Creator .dcproj, exact C127 .c127v65, and
  PDM Manager .pdm files, with exact recovery-copy, executable-version,
  stopped-process, expiry, single-use authorization, and immediate revalidation
  gates. Race Studio containers, DBC/DBM, and unverified C12x suffixes fail closed.

Authorization boundary

No known valid MoTeC or AiM software action is permanently prohibited. Known actions are eligible only after an action-specific driver binds the exact target, source, effect, prerequisites, abort conditions, evidence, recovery and immediate state, followed by exact single-use user authorization. Unknown actions require classification first. Authorization never waives missing safety or compatibility evidence.

Planning, catalog, offline-analysis and generic UI-evidence tools do not execute actions, grant authorization, rewrite proprietary binary configurations, or contact devices.

Installation and private data

The GitHub release contains code, schemas, synthetic tests, authored guidance and official-source metadata. It does not contain private vehicle configurations, copied vendor manuals, generated indexes or credentials. Setup asks for the main MoTeC data root, authorized additional vehicle/AiM roots, missing configuration classes, applications and installed help needed for full readiness.

Known boundaries

• Proprietary configuration semantics remain evidence-led and format/version-specific; unsupported binary regions are never invented.
• Race Studio and Display Creator state-changing actions still require reviewed operation-specific live drivers before execution.
• A successful guarded application spawn does not prove the vendor UI loaded the
  exact project; live title/session correlation remains required before changes.
• An AiM protocol XML proves only its own explicit structure. Vehicle compatibility requires the exact M800 output/configuration, official connection document, fitted harness, device/firmware, physical link and live end-to-end evidence.
• The superseded PDM-only repository must remain available until the merged release passes the documented live parity gate.