DipTrace MCP v0.2.1

DipTrace MCP 0.2.1 is an unsigned development prerelease focused on distribution and installation.

Highlights:

• installable Python package with pip install diptrace-mcp==0.2.1 after PyPI publication;
• validated wheel and source distribution;
• Windows one-click installer and portable archive;
• Windows MCPB candidate;
• deterministic SHA-256 identities for every attached release asset;
• manual, annotated-tag-bound PyPI Trusted Publishing through GitHub OIDC.

Important boundaries:

• Windows executables are unsigned;
• the Python package installs the MCP server but does not automatically install the DipTrace bridge plug-in;
• production readiness and universal DipTrace 5.x compatibility are not claimed;
• Novarm/DipTrace endorsement or affiliation is not claimed.

Validated source commit: 1d2b7bef256cd43262b566dc2cd4050248d0145d.

Successful release workflows:

• Windows one-click installer: run 30990831129;
• MCPB and registry preparation: run 30990857901;
• PyPI distribution validation: run 30990871942.

Verify downloaded files with the attached SHA256SUMS.txt before use.

DipTrace MCP v0.2.0

DipTrace MCP 0.2.0

Unsigned alpha/development prerelease of the DipTrace Model Context Protocol server and Windows live XML bridge.

Highlights

• Windows one-click installer, standalone server, portable bundle, and Codex/Claude configurator.
• Service-Facade decomposition with the public contract preserved at 159 MCP tools.
• Guarded transactions, SHA-bound previews and commits, backups, rollback, live apply/cancel, and explicit policy limits.
• Expanded review, routing, placement, synchronization, evidence, provenance, and release auditing.
• Exact release assets include wheel, source distribution, installer, portable bundle, checksums, SBOM, dependency inventory, notices, and provenance records.

Important limitations

• Windows executables are unsigned. SHA-256 checks establish byte identity, not publisher trust.
• This is not production-ready manufacturing sign-off software and is not endorsed by Novarm/DipTrace.
• Runtime get_capabilities is authoritative for each installation and document.
• Universal DipTrace 5.x compatibility is not claimed.
• Q1 Component Angle GUI/re-export evidence remains NOT_RUN.
• Some real Windows 11, current DipTrace 5, Codex, Claude Desktop, elevated-install, and custom-state acceptance items remain uncompleted and are disclosed in the bundled release record.

DipTrace MCP 0.1.2

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.

DipTrace MCP 0.1.1 — Withdrawn

WITHDRAWN: superseded by v0.1.2 because release documentation contained stale generated metrics and incomplete release-asset installation guidance. No critical runtime vulnerability was identified. Replacement: https://github.com/fireostendere/mcp_diptrace/releases/tag/v0.1.2 # Release Record: v0.1.1 ## Identity and frozen commit - Version: 0.1.1, tag: v0.1.1. - Frozen commit: the tip of main produced by the 0.1.1 release pull request and recorded in the annotated tag object v0.1.1. Verify with git rev-parse v0.1.1^{}. - Artifact hashes are published as the immutable release asset SHA256SUMS.txt; verify them with sha256sum -c SHA256SUMS.txt. ## Scope This patch release contains the Windows/WSL live-exchange-path fix, the Windows inherited-stdout cleanup fix, focused cross-platform path regressions, and the English/Russian documentation reconciliation for the completed live acceptance campaign. It does not expand the advertised native DipTrace writer surface. ## Approvals and exception - Release manager: @fireostendere (repository owner), 2026-08-01. - Independent reviewer: none exists. The owner approves this unsigned alpha release under the documented solo-maintainer development-release exception. - Private vulnerability reporting remains the security channel published in SECURITY.md. - No verified confidential conduct channel, signing identity, or independent release approver exists. The release must not be described as signed, independently reviewed, or production-ready. ## Verification - The complete GitHub Actions matrix passes on the release pull-request tree: Linux 3.10/3.13, Linux geometry plus coverage, Linux no-Shapely fallback, macOS, Windows, native Windows bridge build/smoke, and static/release audit. - Ruff, strict Mypy, generated skill contracts, the exact 159-tool snapshot, release allowlist, specification inventory, format coverage, probe pack, trust-neutral ingest, and acceptance-seed audit pass. - The direct wheel and the wheel rebuilt from the source distribution have the same member set and per-member SHA-256 values. - The frozen wheel installs into a clean environment, starts the CLI, completes a real MCP stdio handshake, exposes 159 tools, and answers a real tool call. - The unsigned Windows bridge is taken from the same successful CI run that built and smoke-ran it with --help. ## Real DipTrace acceptance evidence The 2026-07-31 DipTrace 5.2.0.4 Windows bridge тЖФ WSL MCP campaign completed with ACCEPTANCE: PASS and RELEASE BLOCKER: NO for its explicit matrix: - PCB apply, cancel, and wrong-SHA; - Schematic apply, cancel, and wrong-SHA; - GUI confirmation for applied changes; - PCB Save As plus independent XML re-export and semantic comparison; - stable connectivity/counts; - Windows-native exchange-path metadata; and - no phantom C:\mnt\c\... target. See LIVE_ACCEPTANCE_2026-07-31.md. This is operator-assisted evidence for the tested topology, not proof for every MCP tool, DipTrace version, XML object, native library writer, or optional external solver. ## Release assets - diptrace_mcp-0.1.1.tar.gz тАФ audited Python source distribution. - diptrace_mcp-0.1.1-py3-none-any.whl тАФ MCP server and eight packaged skills. - diptrace_mcp_bridge.exe тАФ unsigned Windows bridge built and smoke-run by CI. - diptrace_mcp_windows_plugin-0.1.1.zip тАФ bridge, installer, four settings profiles, license, and live-path documentation. - LIVE_ACCEPTANCE_2026-07-31.md and CODE_REVIEW_2026-07-31.md тАФ scoped evidence records. - SHA256SUMS.txt тАФ SHA-256 manifest for every attached asset above. ## Supported environments - Python 3.10тАУ3.13 on Linux, macOS, and Windows for the MCP server. - Offline XML analysis under WSL. - Live integration on Windows 10/11 with a DipTrace build that supports executable XML plug-ins; the accepted host matrix includes DipTrace 5.2.0.4, while separate schematic evidence exists for DipTrace 5.3.0.2. ## Known limitations - Not a replacement for the DipTrace GUI or native EDA engine. - get_capabilities remains authoritative for each document and installation. - Component and Pattern Editor bridge profiles remain read-only. - Native Component/Pattern Library mutation and native manufacturing output are not claimed. - Broad redistributable DipTrace 5.3 writer fixtures, native library writer acceptance, complete trust invalidation across every write path, and real external-solver matrices remain incomplete. - Artifacts are unsigned and no package-index publication is performed. ## Retention and rollback Release assets are immutable and are never replaced under the same version. A defect requires a new version or withdrawal under RELEASE_PROCESS.md. Security-sensitive incidents use the private channel in SECURITY.md.

DipTrace MCP 0.1.0

DipTrace MCP 0.1.0

First tagged release of DipTrace MCP: a local Model Context Protocol server
and guarded XML bridge for reading, analyzing, reviewing, and safely editing
DipTrace designs. Licensed under Apache-2.0.

Artifacts and verification

Artifact	Contents
diptrace_mcp-0.1.0.tar.gz	source distribution built from an exact versioned allowlist
diptrace_mcp-0.1.0-py3-none-any.whl	MCP server plus eight packaged skills
diptrace_mcp_bridge.exe	unsigned Windows bridge, built and smoke-run (--help) by CI on the tagged commit
SHA256SUMS.txt	SHA-256 manifest covering every artifact

All 0.1.0 artifacts are unsigned. Verify after download:

sha256sum -c SHA256SUMS.txt

Known hashes:

795a884ad5c6bd9e4afff4c504db8869638a05135c4de2e2562b0864e77e51f3  diptrace_mcp-0.1.0.tar.gz
0e1b459b7dbfdb28d5b179e6efb1371a57107fec83edf3c7dfc083ee9fd90eb4  diptrace_mcp-0.1.0-py3-none-any.whl
46c37b845ba8fd1ab05047047a2cd6800ec68aeff0204f0e04b6b905cd290171  diptrace_mcp_bridge.exe

Install

python3.12 -m venv .venv
./.venv/bin/pip install diptrace_mcp-0.1.0-py3-none-any.whl
./.venv/bin/diptrace-mcp --help

Requirements: Python 3.10–3.13. Live integration additionally requires
Windows 10/11 and a DipTrace build with executable XML plug-in support; see
README.md (Windows Quick Start) and docs/USAGE.md in the repository.

Implemented in this release

• normalized reads for PCB, Schematic, Component Library, and Pattern Library
  XML, with stable object references, connectivity graphs, and spatial queries;
• guarded XML and semantic edits with preview, transactions, expected-SHA,
  backup, and rollback;
• schematic authoring and schematic-to-PCB synchronization;
• bounded placement/routing, differential-pair analysis, and review workflows;
• a live PCB/Schematic bridge with explicit apply or cancel;
• 159 public MCP tools with a committed, CI-gated tools/list snapshot;
• CI-gated release artifacts built from an exact allowlist, with an audited
  wheel RECORD, entry points, and Apache-2.0 license metadata.

Runtime-available vs DipTrace-verified

• Runtime availability of every tool is reported by get_capabilities and is
  authoritative for a specific document and installation.
• DipTrace-verified compatibility is published separately: a live DipTrace
  5.3.0.2 schematic acceptance round trip (41 scoped edits, independent
  re-export, unchanged normalized counts, no new offline ERC errors).
• Broad real-DipTrace open/save/re-export evidence remains incomplete.

Known limitations

• Not a replacement for the DipTrace GUI or native EDA engine.
• Component and Pattern Editor bridge profiles are read-only.
• No native Gerber, NC Drill, ODB++, IPC-2581, or vendor production packages.
• No signed artifacts yet; see the unsigned-binary disclosure above.

Provenance

Release record: docs/releases/v0.1.0.md at tag v0.1.0
(frozen commit 97e18b53dc7cdd9709ac72d2df997aad6f684468). Local gates on the
frozen commit: 981 passed / 4 skipped (Windows-only), Ruff and strict Mypy
clean; wheel rebuilt from the frozen sdist matches the direct wheel member by
member; clean-environment smoke test passes with 159 tools; CI is green on the
tagged commit, including a smoke-run of the built Windows bridge executable.

This is an independent integration. No DipTrace, Novarm, OpenAI, Anthropic, or
other vendor endorsement, sponsorship, affiliation, or support-program
acceptance is claimed.