Skip to content

DipTrace MCP 0.1.2

Pre-release
Pre-release

Choose a tag to compare

View all tags
@fireostendere fireostendere released this 01 Aug 17:16
v0.1.2
8ec5d26
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release Record: v0.1.2

Identity and scope

  • Version: 0.1.2; tag: v0.1.2.
  • Frozen commit: 8ec5d26d4e4f63a56cf42dd37d0b305f519f79cc (exact non-squash merge commit of PR #38);
    git rev-parse 'v0.1.2^{}' must equal this SHA.
  • Release manager: @fireostendere, the
    repository owner.
  • Independent reviewer: none.
  • Exception: solo-maintainer development-release exception, with the limits and
    evidence boundaries below.
  • This is an alpha/development-stage release. It is not production-ready and
    is not published to PyPI or another package index.
  • The predecessor v0.1.1 is withdrawn; its tag remains on the
    original commit for audit.

Required validation

The exact final PR head must pass the complete required CI matrix before merge:

  • Linux Python 3.10 and 3.13;
  • Linux Python 3.12 with Shapely/GEOS, coverage, and headless bridge tests;
  • Linux Python 3.12 no-Shapely fallback;
  • macOS and Windows Python 3.12;
  • native Windows bridge build and --help smoke test;
  • Ruff, strict Mypy, generated skills, MCP snapshot, artifact audit, format
    coverage, spec inventory, probe pack, trust-neutral ingest, and
    acceptance-seed audit.

The release procedure also requires a fresh exact coverage run, a clean-wheel
smoke test, a real MCP stdio initialize/tools/list handshake, a
get_capabilities response, and one read-only tool call. The direct wheel and
the wheel rebuilt from the sdist are compared by member set, member SHA-256,
entry points, packaged skills, METADATA, and RECORD hashes/sizes.

The fresh candidate run on 2026-08-01 completed with 991 passed and 4 skipped
on Python 3.12.3, Shapely 2.1.2, and GEOS 3.13.1. Total coverage was
85.941378% (16,922 statements, 2,379 missed); bridge.py was 264/83
(68.560606%), xml_document.py 808/86 (89.356436%),
semantic_compiler.py 1,349/159 (88.2135%), and routing_compiler.py 561/75
(86.631016%).

The candidate wheel/sdist audit passed with 79 wheel files and 280 sdist files.
The direct wheel and wheel rebuilt from the sdist had identical member sets and
per-member SHA-256 values. The clean wheel passed CLI --help and a real stdio
handshake: initialize, tools/list with 159 tools, get_capabilities, and
read-only summarize_design all succeeded. The local headless bridge smoke test
also passed. The exact final PR-head CI matrix, merge commit, CI run, Windows
bridge provenance, SHA256SUMS, and public-download smoke evidence remain
publication gates and are recorded only after those checks complete.

Live evidence boundary

The 2026-07-31 live acceptance record covers the tested Windows DipTrace
5.2.0.4 ↔ WSL topology for PCB and Schematic apply, cancel, wrong-SHA, GUI,
save/re-export, path-platform metadata, and connectivity/count checks. It does
not prove every registered tool, every DipTrace version, every XML object,
native library mutation, external solver path, or manufacturing sign-off.

The Windows bridge provenance must identify the successful exact-head CI run,
its artifact, source commit, non-empty executable, --help result, bundled
runtime dependencies, and SHA-256. The executable and plugin package are
unsigned; CI success is not a signature.

Release assets

The published asset set is:

  • diptrace_mcp-0.1.2.tar.gz;
  • diptrace_mcp-0.1.2-py3-none-any.whl;
  • diptrace_mcp_bridge.exe;
  • diptrace_mcp_windows_plugin-0.1.2.zip;
  • LIVE_ACCEPTANCE_2026-07-31.md;
  • CODE_REVIEW_2026-07-31.md;
  • INSTALL_FROM_RELEASE.md;
  • v0.1.2-forum-ru.md;
  • v0.1.2-forum-en.md; and
  • SHA256SUMS.txt covering every file above.

All assets are unsigned. The release does not publish to PyPI. Users must
download from GitHub, verify SHA-256, and retain the release URL and commit
metadata when reporting an issue.

Supported environments and limitations

  • Python 3.10–3.13 on Linux, macOS, Windows, and offline WSL server use;
  • live bridge integration on Windows 10/11 with a DipTrace build supporting
    executable XML plug-ins;
  • Component and Pattern Editor bridge profiles remain read-only;
  • broad DipTrace writer compatibility, native library mutation, manufacturing
    output, external-solver evidence, and complete trust invalidation remain
    explicitly incomplete;
  • the runtime get_capabilities response is authoritative for a particular
    document and installation; and
  • no production-ready, signed-binary, vendor-endorsement, independent-audit,
    or complete-manufacturing-sign-off claim is made.

Rollback and withdrawal

Release assets are immutable and are never replaced under an existing version.
If a material defect or documentation inconsistency is found, preserve the tag
and asset bytes, publish a replacement version, and mark this release withdrawn
with the reason and replacement link. Security reports use the private channel
in SECURITY.md. The v0.1.1 withdrawal record documents
the same procedure and the explicit Git revert that preserved history.

Publication evidence

  • PR #38 exact head: 759234f209927e3c033e44d63494d3ca3cfae150.
  • Required CI run: 30709466348; all 8 jobs completed successfully before merge.
  • Windows bridge artifact: diptrace-bridge-ci-unsigned, artifact ID 8821397342,
    from CI run 30709466348 and head 759234f209927e3c033e44d63494d3ca3cfae150; artifact archive SHA-256
    661a9aa6d9d13eb695a536101609d5ca10c705a9f92388393543a7f9e8909f3b.
  • Release commit: 8ec5d26d4e4f63a56cf42dd37d0b305f519f79cc.
  • Release asset hashes and sizes are in the attached SHA256SUMS.txt.
  • The Windows bridge is unsigned; no PyPI or package-index publication is performed.
  • No production-ready claim is made.
Assets 12
Loading