Skip to content

MoTeC MCP 0.6.0

Choose a tag to compare

View all tags
@Herbertmt978 Herbertmt978 released this 23 Jul 21:08
v0.6.0
fb5a4b6
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.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.

Assets 2
Loading