Skip to content

MoTeC MCP 0.2.1

Choose a tag to compare

View all tags
@Herbertmt978 Herbertmt978 released this 13 Jul 15:07
v0.2.1
c624e42
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.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.

Assets 2
Loading