Skip to content

MoTeC MCP 0.4.0

Choose a tag to compare

View all tags
@Herbertmt978 Herbertmt978 released this 16 Jul 15:13
v0.4.0
a0824f8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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.

Assets 2
Loading