MoTeC MCP 0.7.0

MoTeC MCP 0.7.0

This additive release expands the MCP to a 136-tool public surface and adds the
reviewed internal foundations for template-backed C1212 project compilation.
The new path remains native-validation-required and does not promote private
target packs or proprietary project bytes into the repository.

Highlights

• Adds an exact six-page C1212 foundation compiler backed by admitted native
  page, group, rectangle, and static-text templates.
• Adds target-specific C1212 and C127 paint-order profiles so semantic
  back-to-front order is lowered only through the measured target contract.
• Adds descriptor-one power-on Animation closure that preserves the admitted
  embedded payload and composes one frontmost, autoplaying page video entirely
  in memory.
• Adds opaque C1212 target-pack admission. Exact foundation and media projects,
  manifests, and native-template handles stay private and are available only
  through genuine disposable authority.
• Adds deterministic state, menu, and channel readiness summaries with explicit
  deferrals for unproved native behavior, DBC evidence, and bindings.
• Adds an in-memory high-level C1212 compiler that joins the admitted target
  pack, exact foundation, and descriptor-one media stages while returning only
  disposable final project bytes and a privacy-minimal receipt.
• Retains the open-world catalogue covering 22 system groups and the declared
  Ultima integration workflow for PDM30, PDM15, C125, C1212, M150, MoTeC
  rotary, 8-button and 15-button controls, AiM RBI-WW-10 steering-wheel
  controls, AiM TPMS, Delta ABS, Holinger MXT, paddle-shift auxiliary kit, and
  reverse camera.

Validation and capability boundary

All template-backed C1212 compiler evidence in this release is synthetic,
in-memory, and fail-closed. Native vendor validation is still required:
reopen, readback, and Quick Check must pass before the foundation/media
target-pack path can be promoted.

This release does not provide a general arbitrary-media writer, gauge
writer, native menu writer, DBC writer, general .dcproj codec, or device
action. It does not authorize save, package, send, Device > Configure Device,
CAN transmission, or hardware configuration. Requested media replacement,
repeat control, native group membership, unproved object families, menu
behavior, and channel bindings remain explicitly deferred.

Private target packs, donor projects, manifests derived from private projects,
screenshots, native validation evidence, working copies, paths, hashes, and
embedded assets must stay outside Git and the release in authorized local
storage.

UAT dispositions

The machine-readable dispositions are:

• c125-native-display=native-unavailable
• c1212-native-display=native-unavailable
• c1212-rectangle-fill-colour-6-5-0-31=passed
• red-mini-c127-controlled-experiment=native-unavailable
• c1212-template-backed-foundation-media=not-run

The new c1212-template-backed-foundation-media disposition is not-run
because native-vendor-validation-required. Existing dispositions are retained
unchanged; the earlier narrow Rectangle fill-colour proof does not promote the
new whole-foundation/media path.

Installation and compatibility

Version 0.7.0 is additive. Existing MCP tool names and conservative
compatibility surfaces remain available. Upgrade by installing the locked
dependencies, building, and re-registering or restarting the MCP so the
136-tool inventory is loaded.

A reduced installation supports offline workflows. Full readiness additionally
asks for separately authorized installed application/help inputs required by a
selected live or evidence-capture route and, for the internal C1212 compiler,
the four private foundation/media target-pack candidates described below.
Private configurations, logs, manuals, target packs, generated indexes, working
copies, and UAT evidence remain outside the clone.

The product-knowledge snapshot remains 2026-07-17.1, checked on 2026-07-17.
Catalogue knowledge is not target fitment, and an empty search is not evidence
of absence.

Follow setup from GitHub, the
Display Creator fast-authoring guide,
the stateful icons and rotary menus guide,
and the private C1212 target-pack contract.
Exact release and UAT status is recorded in
data/release-metadata.json.

Licence and evidence boundaries

Copyright © 2026 Herbertmt978. All rights reserved. Use and modification are
permitted only by Herbertmt978 and people explicitly authorized in writing.
Redistribution is prohibited.

Previously published v0.3.0 and v0.4.0 copies retain their historical MIT terms.
Public visibility of later proprietary revisions does not grant use,
modification, or redistribution rights.

A green offline test, synthetic roundtrip, catalogue match, virtual display, or
installed application does not prove native vendor acceptance, vehicle wiring,
CAN traffic, sensor health, calibration correctness, activation,
connected-device state, or safe hardware operation.

MoTeC MCP 0.6.0

MoTeC MCP 0.6.0

This release expands the MCP to a 135-tool public surface and adds the design,
evidence, wiring, and internal validation foundations needed to make Display
Creator work faster without treating an unknown proprietary project format as
a general writable document.

Highlights

• Adds typed Display Creator authoring plans for pages, entities, styles,
  groups, paint order, channel-binding intent, layered tell-tales, flashing
  states, request-versus-actual menus, and simulation scenarios.
• Adds path-free reference-dashboard reconstruction. Operator-measured regions
  can be calibrated to C125, C127, or C1212 canvases and decomposed into native
  candidates, assets, layers, palette roles, typography evidence, scenarios,
  and explicit unresolved questions. The tool does not ingest image bytes,
  identify an exact font, invent a DBC channel, or execute the design.
• Adds a strict Display Creator example catalogue and 45 original C125/C1212
  concept assets for visual inspiration, plus a version-bound manual C1212
  blank-project authoring guide.
• Adds configured-root, exact-snapshot mutation-diff and repeatability evidence
  tools. Public caller-declared evidence remains non-promotable and cannot
  authorize a mapper, binding, project write, or vendor-software action.
• Adds pin-map catalogue, reconciliation, and wiring-path analysis tools that
  keep manufacturer capability, as-built loom evidence, and software assignment
  evidence separate.
• Pins audited transitive fixes for the SDK HTTP transport, request-body parser,
  and URI validator; the locked production dependency graph reports zero known
  vulnerabilities at release verification.
• Retains the open-world catalogue covering 22 system groups and the
  declared Ultima integration workflow for PDM30, PDM15, C125, C1212, M150,
  MoTeC rotary, 8-button and 15-button controls, AiM RBI-WW-10 steering-wheel
  controls, AiM TPMS, Delta ABS, Holinger MXT, paddle-shift auxiliary kit, and
  reverse camera.

Exact C1212 Display Creator proof

A bounded primary run and an independent fresh-root holdout both passed for one
exact internal route against the repository-owned synthetic blank-C1212
training fixture:

• Display Creator 6.5.0.31;
• C1212;
• one target-bound Rectangle fill-colour before-to-after transition;
• one normalization UI Save;
• one offline write to a verified disposable working copy;
• zero native-validation Saves; and
• close, reopen, typed readback, Quick Check, recovery, and cleanup gates.

The public result is deliberately non-promoting. This proof does not create
a general .dcproj writer or property codec. It does not authorize arbitrary
colours, other rectangles, border colour, geometry, text, images, video,
gradients, gauges, entity creation/deletion, layers, page structure, channel or
DBC binding, C125/C127 mutation, package/send, device configuration, or hardware
action. Those surfaces remain in Display Creator until each exact mapper and
its own independent disposable-copy UAT are implemented and passed.

The machine-readable dispositions are:

• c125-native-display=native-unavailable
• c1212-native-display=native-unavailable
• c1212-rectangle-fill-colour-6-5-0-31=passed
• red-mini-c127-controlled-experiment=native-unavailable

The broad C1212 disposition remains unavailable because one exact Rectangle
transition is not native display-authoring support.

Installation and compatibility

Version 0.6.0 is additive. Existing public MCP tool names and conservative v1
compatibility surfaces remain available. Upgrade by installing the locked
dependencies, building, and re-registering or restarting the MCP so the
135-tool inventory is loaded.

A reduced installation supports offline workflows. Full readiness additionally
asks for separately authorized installed application/help inputs required by a
selected live or evidence-capture route. Private configurations, logs, manuals,
screenshots, generated indexes, working copies, and UAT evidence stay outside
the clone in authorized local storage.

The product-knowledge snapshot remains 2026-07-17.1, checked on
2026-07-17. Catalogue knowledge is not target fitment, and an empty search is
not evidence of absence.

Follow setup from GitHub, the
Display Creator fast-authoring guide,
the reference-dashboard reconstruction guide,
and the wiring/pin-map workflow. Exact release and
UAT status is recorded in
data/release-metadata.json.

Licence and evidence boundaries

Copyright ? 2026 Herbertmt978. All rights reserved. Use and modification are
permitted only by Herbertmt978 and people explicitly authorized in writing.
Redistribution is prohibited.

Previously published v0.3.0 and v0.4.0 copies retain their historical MIT terms.
Public visibility of later proprietary revisions does not grant use,
modification, or redistribution rights.

A green offline test, catalogue match, virtual display, installed application,
or local resource observation does not prove vehicle wiring, CAN traffic,
sensor health, calibration correctness, activation, connected-device state, or
safe hardware operation.

MoTeC MCP 0.5.0

MoTeC MCP 0.5.0

This release adds an additive 125-tool public surface for local, evidence-led
motorsport workflow planning, resource handling, whole-vehicle analysis,
logging diagnostics, and virtual display design.

Highlights

• Adds logical-resource and manual-coverage workflows with six explicit
  coverage states, official-source metadata, permission-gated local
  acquisition and admission, installed-help indexing, and bounded read-only
  queries. Vendor manuals, private vehicle material, generated indexes, and
  application assets remain outside the repository.
• Adds an open-world whole-vehicle catalogue covering 22 system groups, plus
  evidence-bound Vehicle System Profile v2 and Signal Path v2 owners. Catalogue
  knowledge is not target fitment, and an empty search is not evidence of
  absence.
• Adds original simulation-only C125-primary/C1212-secondary display studies
  with shared semantic channels, request-versus-independent-actual feedback,
  menus, alarms, logging, diagnostics, deterministic previews, and bundle
  validation. They create no native project, generated DBC, device
  configuration, send route, or hardware authority.
• Adds public resource-admission, dual-display availability, and guarded C127
  controlled-experiment contracts. Reduced and full smoke coverage remains
  synthetic and offline-only; it does not inspect ambient applications or
  prove native hardware capability.
• Retains configured-root CSV telemetry support for summaries, channel
  discovery, selected numeric queries, and aggregate quality observations.
  Results are evidence for diagnosis, not a substitute for mechanical checks,
  calibration proof, or a native i2/Race Studio log.

Declared Ultima coverage

The portable expert workflow covers the declared PDM30, PDM15, C125, C1212,
M150, MoTeC rotary controller, MoTeC 8-button and 15-button boxes, AiM
RBI-WW-10 steering-wheel controls, AiM TPMS, Delta ABS, Holinger MXT,
paddle-shift auxiliary kit, and reverse camera. These are candidate devices
and integration requirements until the exact fitted revisions, firmware,
packages, wiring, CAN definitions, licences, configurations, and private target
files are supplied and admitted.

Compatibility and installation

The 0.5.0 public surface is additive: existing MCP tool names remain available,
and v1 profile/signal/capability surfaces remain conservative compatibility
paths. Upgrade by installing locked dependencies, building the server, and
re-registering or restarting the MCP so the 125-tool inventory is loaded.

A reduced installation supports offline workflows. Full readiness asks for the
separately authorized installed application/help inputs required by a selected
live or evidence-capture route. Logs, private configurations, manuals,
screenshots, and generated local indexes must stay in authorized local storage,
outside the clone.

Follow setup from GitHub, the
portable resource workflow, and
the Ultima dual-display builder. The exact
machine-readable release and UAT contract is
data/release-metadata.json.

Native-UAT status

The shipped virtual display work is not native display support. Current
machine-readable dispositions are:

• c125-native-display=native-unavailable
• c1212-native-display=native-unavailable
• red-mini-c127-controlled-experiment=native-unavailable

C125 and C1212 remain unavailable because their product-specific native
bindings are unproven. The Red Mini controlled experiment remains unavailable
because the production facade reports
controlled-experiment-native-driver-unavailable. No native C125/C1212 manager,
file suffix, project format, generated DBC, send route, or completed hardware
UAT is claimed. A later C127 experiment requires the exact version-bound driver,
private evidence, fresh single-use authorization, receipt, diff, save/reopen
proof, and clean recovery.

Catalogue and repository-file identities

All three SHA-256 values use the machine-readable
catalogueHashBasis=canonical-utf8-lf: decode as UTF-8 and normalize CRLF to
LF before hashing. Windows and LF checkouts therefore verify the same content.

• Product knowledge snapshot: motorsport-product-knowledge
2026-07-17.1, checked 2026-07-17 (schema 1.0.0), repository-file
  SHA-256 8c9d2d37e727a1f9291b1529ac9405928f5c7cc3550cfd68a2d9b4dc431eca64.
• Whole-vehicle catalogue:
  whole-vehicle-instrumentation-and-control-catalog 1.0.0 (schema
  1.0.0), repository-file SHA-256
  fd6e183e3e1b4d9969b177455f3fee1c61ec974d3aa38c1ae534de075db9bd81.
• Logical-resource catalogue: motorsport-logical-resource-catalog (schema
  1.0.0; no separate catalogue-version field), repository-file SHA-256
  44ce407be8ad01a05508023c40dea3a434f46bf3e84b142d1c22a1a3019146da.

These are canonical repository-file identities, not target fitment,
manual-content, software-installation, configuration, or hardware evidence.

Licence and evidence boundaries

Copyright © 2026 Herbertmt978. All rights reserved. Use and modification are permitted only by Herbertmt978 and people explicitly authorized in writing. Redistribution is prohibited.

Previously published v0.3.0 and v0.4.0 copies retain their historical MIT
terms. Public visibility of later proprietary revisions does not grant use,
modification, or redistribution rights.

A green offline test, catalogue match, virtual bundle, installed application,
or local resource observation does not prove vehicle wiring, CAN traffic,
sensor health, calibration correctness, activation, connected-device state, or
safe hardware operation.

MoTeC MCP 0.4.0

MoTeC MCP 0.4.0

This release adds exact, path-redacted single-file analysis for authorised MoTeC
and AiM configuration files, and establishes the first conservative offline
structure maps for C127 Dash Manager and Display Creator projects.

Highlights

• Adds motec_configuration_file_analysis, a strict read-only tool that captures
  one exact configured-root snapshot and returns bounded pages of compact entities
  or relations. Cursors bind to the exact source digest, analyzer version, format,
  resource and query budgets.
• Recognises the verified wrapped Display Creator .dcproj container, reports
  bounded ISO-BMFF media-box framing, and returns schema-only XML-like element
  names/counts without text values, attribute values, raw project bytes, or
  arbitrary binary strings. Retained schema names are individually pageable with
  bounded occurrence counts and first-offset evidence.
• Extends exact .c127v65 inspection with embedded CHANLST framing, known
  section-tag locations, unknown-region accounting, and mechanically verified
  channel names for the supported channel-record version. Unknown record versions
  expose framing only.
• Uses installed Display Creator and C127 Manager resources as clean-room
  interoperability evidence. The installed applications are native compiled PE
  programs, not source distributions; this release does not reproduce vendor code
  or claim undocumented field semantics.
• Strengthens Display Creator DBC planning with a separate exact source identity,
  configured-root admission, bounded snapshot capture, stale-source checks, and a
  graph fingerprint that changes with the selected DBC bytes.
• Adds an offline-only workspace-report mode so configuration analysis can avoid
  process and application discovery entirely.
• Documents the supported offline structure, XML-export evidence bridge, exact
  file-routing workflow, and the boundary between structural evidence and
  vendor-owned editing.
• Adds contract coverage for bounded Display Creator live-UAT evidence recovery
  and runner behaviour while retaining the existing fail-closed authorization and
  cleanup boundaries.
• Keeps Promise-owned deadline timers live until their bounded operations settle
  under Node 22, and binds Windows ACL commands to the security module belonging
  to the actual PowerShell host even when setup inherits a mixed-version module
  path.

Safety and evidence boundaries

• Proprietary project analysis remains partial. Unknown bytes are identified but
  not assigned guessed meanings, and proprietary binary projects are never edited
  directly.
• The single-file tool may return mechanically verified semantic names, including
  DBC/channel names. It does not return physical/requested paths, source bytes,
  heuristic printable strings, XML text, or XML attribute values.
• A structure tag or installed-resource string is not proof of a setting. Deeper
  advice must be correlated with the exact application version, supported
  XML/DBC export, installed help, or a separately authorised UI observation.
• Display Creator XML export/import semantics have not yet been proven against a
  version-matched synthetic regression fixture. Direct page/object/property edits
  remain application-owned.
• Shared Dash Manager, Display Creator, M1 Tune and PDM live-driver hardening is
  contract-tested but still pending direct native live UAT. This release does not
  promote those paths to verified live capability.
• No green test or offline result proves vehicle wiring, CAN traffic, sensor
  health, calibration correctness, software activation, connected-device state,
  or safe hardware operation.

Compatibility and installation

The new analysis tool and offline-only report option are additive. Existing MCP
tool names remain available. Installations upgrading from 0.3.0 should pull the
release, run npm ci and npm run build, then re-register or restart the MCP so
the 0.4.0 tool inventory is loaded.

Private vehicle files, vendor manuals/help extractions, screenshots and generated
indexes remain outside the repository. A fresh Codex installation must be given
the main MoTeC data root and each additional car/AiM root it is allowed to read;
setup asks for missing private roots and application/help paths rather than
assuming this machine's locations.

Follow setup from GitHub, then complete the
release checklist. Live vendor-UI and hardware UAT remain
separate, operator-authorised evidence gates.

MoTeC MCP 0.3.0

MoTeC MCP 0.3.0

This minor release adds a public, bounded telemetry-analysis foundation and the
portable guidance another Codex installation needs to use it safely.

Highlights

• Adds four strict, read-only MCP tools for configured-root CSV logs:
  motec_log_summary, motec_log_channels, motec_log_query, and
  motec_log_quality_report.
• Captures one exact source snapshot, hashes and revalidates the opened file, and
  processes selected numeric/empty/invalid states in the same bounded streaming
  pass. Default summaries retain no sample projection.
• Supports exact channel/unit discovery, bounded cursor paging, inclusive row/time
  filters, deterministic uniform downsampling, exact numeric aggregates, and
  aggregate-only quality observations for missing/invalid values, configured-time
  behaviour, clipping candidates, and constant/stale runs.
• Binds cursors to a process-local HMAC plus the exact source and normalized CSV
  interpretation. Changing the digest, parser/query version, delimiter, layout,
  channel identities, time column, filters, order, or budgets invalidates a cursor.
• Separates source completeness from response-page completeness and reports every
  threshold as explicit, default, or fixed provenance rather than presenting an
  unexplained diagnosis.
• Adds portable i2/RaceStudio logging guidance, official-source metadata, local
  installed-help discovery, fresh-Codex routing, synthetic examples, and exact
  questions for missing source/session/export evidence.
• Adds the MIT licence with copyright © 2026 Herbertmt978 and refreshes the
  professional README, plugin metadata, tags, and installation hand-off.
• Makes Windows prerequisite probing tolerant of ordinary cold npm startup and
  runs long PowerShell automation from short-lived script files instead of an
  oversized command line.

Safety and evidence boundaries

• CSV analysis is vendor-neutral. No MoTeC .ld or AiM
  .xrk/.xrz/.drk/.gpk decoder, dialect, export, lap, beacon, resampling, or
  native-parity claim is made.
• A vendor-specific claim still requires a private native original, a paired
  same-session CSV, exact installed application/build and activation/licence
  evidence, and at least three human- or UI-confirmed facts.
• Query output contains only selected numeric, empty, or invalid states. It never
  returns raw CSV rows, raw text cells, source bytes, requested paths, or physical
  paths. Private logs and generated evidence stay in authorised local roots and
  must not be committed to Git or included in the release.
• Quality findings are observations with evidence counts and threshold
  provenance, not proof of a sensor, wiring, CAN, mechanical, calibration, or
  vehicle fault. The workflow explicitly stops tuning around unresolved faults.
• The new tools do not launch i2/RaceStudio, retrieve or erase device data, change
  a workspace, write cache state, communicate with hardware, or authorize a live
  action.
• PDM section capture now skips full-smoke only through a structured, path-free
  initial-preflight result. A live selection verifies caret/viewport ownership and
  an unchanged Windows input epoch, but Win32 TreeView messages are not atomic
  with human input; do not use mouse or keyboard while that capture runs.

Compatibility and installation

The four tools and documentation are additive; existing MCP tool contracts remain
available. A fresh Windows install requires PowerShell 5.1 or 7, Node.js 20+ with
npm, Git (with GitHub CLI optional), Codex CLI/Desktop for registration and use,
the repository, a main MoTeC data root, and any additional roots the user chooses
to authorize.
MoTeC/AiM applications and installed help are optional for reduced offline use and
required only for their corresponding full/live capabilities. Logs and CSV exports
are not installation prerequisites. Installed i2 readiness proves declared files
are present only; it does not prove edition, activation, API entitlement,
workspace load, or native export capability.

Follow setup from GitHub, then run the checks in the
release checklist. Native-log parity remains a future
evidence gate and is not implied by a green build, smoke test, or release.

MoTeC MCP 0.2.1

MoTeC MCP 0.2.1

This patch release strengthens PDM understanding, bounded live-software evidence,
and the installation handoff for a fresh Codex environment.

Highlights

• Adds motec_pdm_query, a strict, exact-snapshot PDM query surface with eight
  version-bound PDM Manager sections, fifteen closed result kinds, deterministic
  cursor paging, response/time budgets, source-hash preconditions, and path-free
  output.
• Keeps authoritative pre-materialization PDM counts available when detailed
  semantic output is compacted or truncated. Returned counts and count authority
  are reported separately so unavailable data is never presented as zero.
• Makes file-based PDM semantic provenance path-free before parsing, so deep
  Windows workspace or temporary paths cannot consume the analyzer's response
  budget or change the reported configuration semantics. Physical paths remain
  confined to file access, authorization, revalidation, and input errors.
• Distinguishes missing, empty, non-empty, verified, dangling, and
  name-derived-unverified channel-reference states without inventing optionality
  or target semantics. Known structural identifiers are retained separately from
  unknown attributes.
• Reworks PDM graph compaction around deterministic section correlation,
  high-cardinality linear channel aggregation, opaque channel identities, derived
  relationship evidence, and bounded deadline-aware filtering and serialization.
• Adds motec_pdm_manager_section_capture, constrained to the eight known PDM
  Manager 1.9 tree sections. The driver uses native TreeView messages, rejects
  process/window/dialog/topology ambiguity, invokes no command, and proves prior
  tree and foreground restoration.
• Hardens shared PDM Manager, Dash Manager, Display Creator, and M1 Tune visual
  menu evidence with exact-session revalidation, bounded target/menu captures,
  exclusive evidence ownership, and verified menu/cursor/foreground cleanup.
• Refreshes the README, package metadata, installation handoff, capability
  matrix, and PDM workflow documentation for a more discoverable and professional
  repository.

Safety and evidence boundaries

• No generic key, click, coordinate, menu-command, save, send, firmware,
  credential, option, output-test, or device executor is introduced.
• No known MoTeC action is permanently policy-blocked. State-changing and
  high-impact actions still require a reviewed action-specific driver, current
  prerequisites, and exact single-use user authorization.
• A 2026-07-13 manual read-only UAT confirmed the visible eight-section PDM
  Manager 1.9 tree and restored its original selection. The new native section
  driver and shared menu hardening remain explicitly pending direct live-driver
  UAT; a window title alone does not prove exact loaded-file identity.
• Offline section correlation is version-bound and partial. It does not prove
  physical wiring, live CAN state, fitted hardware, firmware compatibility, or a
  safe output test.

Distribution and privacy

The release contains source code, schemas, synthetic fixtures, authored guidance,
and official-source metadata. It does not contain private vehicle configurations,
screenshots, local paths, generated indexes, credentials, or copied proprietary
manuals. Setup asks the installer for the authorized MoTeC data root, any
additional vehicle/AiM roots, installed software/help locations, and missing
hardware/package/version evidence required for full readiness.

The superseded PDM-only repository must remain available until this release is
merged, CI is green, a clean installation is proven, and the documented live PDM
parity gate is complete.

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.