Skip to content

TraceWeave 2.0.2

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Aug 15:11
· 155 commits to main since this release
v2.0.2
0847f43

TraceWeave v2.0.2

TraceWeave 2.0.2 clarifies and hardens installation for two distinct deployment profiles: portable PyPI usage and repository-local full EDA integration.

The goal of this release is to make the installation boundary explicit:

  • Use the portable PyPI profile for log/VCD analysis, MCP integration, the unlicensed Python fallback stack, and optional open-source Source Graph support.
  • Use the repository-local full EDA profile when FSDB, Verdi/NPI, VCS/Xcelium, LSF, or site-specific EDA integration is required.

This avoids unsupported combinations between portable PyPI installations and repository-local FSDB/runtime setup.

Highlights

  • Added scripts/install.sh as the recommended entry point for repository-local full EDA installation.

  • The full installer orchestrates Source Graph setup, FSDB wrapper construction, FSDB verification, and a repository MCP runtime smoke test.

  • Added read-only installation checks with:

    bash scripts/install.sh --check

    and machine-readable output with:

    bash scripts/install.sh --check --json

  • Added MCP client configuration templates for Codex, Claude Code, and GitHub Copilot through --print-config.

  • The installer prints configuration templates only and never edits user MCP client configuration files.

  • Added:

    traceweave-mcp --doctor

    and:

    traceweave-mcp --doctor --json

    for portable installation diagnostics.

  • Clearly separated the portable PyPI profile from the repository-local EDA profile, avoiding unsupported PyPI/repository FSDB mixing.

  • Hardened FSDB verification so the repository Python runtime must load the exact repository-built wrapper. Mismatched or incomplete installations now fail loudly.

  • Strengthened wheel and sdist audits to ensure portable artifacts expose only the traceweave_mcp namespace and contain no FSDB wrapper sources, native binaries, setup scripts, proprietary runtime, or test artifacts.

  • Preserved the existing python server.py, component setup scripts, and repository-local EDA workflow.

  • The MCP server continues to expose the same 38 MCP tools.

Installation

Repository-local full EDA profile

Recommended for simulation hosts using Source Graph, FSDB, Verdi/NPI, VCS/Xcelium, or LSF.

Clone the repository and run the unified installer:

git clone https://github.com/gokeshenzhen/TraceWeave.git
cd TraceWeave

export VERDI_HOME=/path/to/verdi

bash scripts/install.sh

The installer coordinates the repository-local EDA setup, including Source Graph, FSDB wrapper construction, verification, and MCP runtime validation.

Inspect an existing installation without making changes:

bash scripts/install.sh --check
bash scripts/install.sh --check --json

Print an MCP client configuration template without modifying user files:

bash scripts/install.sh --print-config codex
bash scripts/install.sh --print-config claude
bash scripts/install.sh --print-config copilot

The existing component-level commands remain supported:

bash scripts/setup_source_graph.sh
bash scripts/setup_fsdb.sh
bash scripts/verify_fsdb.sh

The existing repository-local server entry point also remains supported:

python server.py

Verdi NPI support remains conditional on the site's KDB, pynpi, licensed runtime, and local or LSF environment.

TraceWeave does not install or distribute proprietary EDA software, proprietary libraries, Verdi runtime components, or license data.

Portable PyPI profile

Recommended for portable MCP usage, log analysis, VCD analysis, and the unlicensed Python fallback stack.

Install the standard package:

python -m pip install traceweave-mcp

Run installation diagnostics:

traceweave-mcp --doctor

For machine-readable diagnostic output:

traceweave-mcp --doctor --json

To include the pinned open-source Source Graph frontend:

python -m pip install "traceweave-mcp[source-graph]"

The portable PyPI package intentionally does not contain:

  • TraceWeave FSDB wrapper source
  • FSDB build scripts
  • Native FSDB wrapper binaries
  • Proprietary Verdi/NPI runtime components
  • Proprietary EDA software
  • License data
  • Repository-local EDA setup payloads

When FSDB or Verdi/NPI support is required, use the repository-local full EDA profile instead of combining a PyPI installation with repository setup scripts.

Installation Profiles at a Glance

Portable

python -m pip install traceweave-mcp

Provides:

  • MCP server
  • Log analysis
  • VCD analysis
  • Python fallback stack
  • Portable diagnostics
  • 38 MCP tool definitions

Optional Source Graph support:

python -m pip install "traceweave-mcp[source-graph]"

Full EDA

git clone https://github.com/gokeshenzhen/TraceWeave.git
cd TraceWeave
export VERDI_HOME=/path/to/verdi
bash scripts/install.sh

Adds repository-local support for environments that may include:

  • Source Graph
  • FSDB
  • Verdi NPI
  • VCS
  • Xcelium
  • Local simulation environments
  • LSF-based simulation environments

Availability of proprietary EDA backends depends on the software, licenses, environment, and configuration provided by the user's site.

MCP Registry

Official MCP Registry name:

io.github.gokeshenzhen/traceweave

TraceWeave continues to expose the same 38 MCP tools.

Runtime receipts and backend status distinguish portable capabilities from optional EDA backends, including:

  • Log
  • VCD
  • Python fallback
  • Source Graph
  • FSDB
  • Verdi NPI

This allows MCP clients and AI agents to understand which capabilities are available in the current runtime environment.

MCP Client Configuration

Repository-local installations can print configuration templates for supported MCP clients without modifying existing user configuration.

Codex:

bash scripts/install.sh --print-config codex

Claude Code:

bash scripts/install.sh --print-config claude

GitHub Copilot:

bash scripts/install.sh --print-config copilot

These commands are intentionally read-only with respect to user client configuration.

They print the recommended configuration so users or automation can review and apply it explicitly.

Diagnostics

Repository-local installation

Human-readable check:

bash scripts/install.sh --check

Machine-readable check:

bash scripts/install.sh --check --json

Portable PyPI installation

Human-readable diagnostics:

traceweave-mcp --doctor

Machine-readable diagnostics:

traceweave-mcp --doctor --json

These diagnostics are intended to make installation state, optional backend availability, and configuration problems easier to identify.

FSDB Packaging Boundary

TraceWeave 2.0.2 strengthens the separation between the portable distribution and repository-local FSDB integration.

The PyPI wheel and source distribution do not ship TraceWeave's repository FSDB wrapper implementation or FSDB build/runtime payload.

FSDB support is instead built and verified from the repository-local installation flow.

Repository FSDB verification now requires the active repository Python runtime to load the exact repository-built wrapper. Incorrect, stale, mismatched, or incomplete wrapper installations fail explicitly rather than silently falling back to another installation.

This makes the runtime boundary easier to reason about for users, CI systems, and AI coding agents.

Validation

The v2.0.2 release was validated across the supported portable release flow.

  • Python 3.11 CI suite: 1,840 passed, 37 skipped
  • Python 3.12 CI suite: 1,840 passed, 37 skipped
  • Clean wheel installations on Python 3.11 and Python 3.12 successfully initialized the MCP stdio server.
  • Clean wheel installations listed all 38 MCP tools outside the repository checkout.
  • The installed Source Graph extra passed its isolated worker smoke test.
  • Wheel content audits confirmed that portable artifacts contain no FSDB build/runtime payload.
  • Source distribution audits confirmed that portable artifacts contain no proprietary EDA content.
  • PyPI Trusted Publishing passed.
  • Public-package installation verification passed.
  • Official MCP Registry OIDC publishing passed.
  • Exact MCP Registry API lookup verification passed.
  • MCP Registry search verification passed.
  • The GitHub Actions release workflow completed successfully.

Backward Compatibility

Existing repository-local workflows remain supported.

The following entry point is still available:

python server.py

Existing component setup commands also remain available:

bash scripts/setup_source_graph.sh
bash scripts/setup_fsdb.sh
bash scripts/verify_fsdb.sh

The main change in v2.0.2 is not removal of the existing workflow, but the introduction of a clearer recommended installation entry point and a stricter separation between portable and full EDA environments.

Links

  • PyPI: traceweave-mcp
  • GitHub: gokeshenzhen/TraceWeave
  • MCP Registry: io.github.gokeshenzhen/traceweave

Release commit:

0847f43d960055e48877c0ef1e182d1252a2ef64

Full Changelog:

v2.0.1...v2.0.2
Assets 4
Loading