SledTrace v0.7.0 — External Developer Readiness

SledTrace v0.7.0 — External Developer Readiness

SledTrace v0.7.0 makes the existing local-first RAG debugging stack easier for an external developer to evaluate, install, validate, and contribute to. It is a readiness and distribution release, not a new diagnostic-feature release and not a claim of external adoption.

Highlights

• independent GitHub Actions jobs for Python 3.9, Python 3.13, the Go Collector, and the Dashboard
• protected main branch with those four required checks
• OIDC Trusted Publishing workflow for TestPyPI and production PyPI
• TestPyPI 0.7.0rc1 publication and clean-index validation
• first production PyPI release for ordinary pip install sledtrace
• clean-clone startup instructions with Docker and explicit non-Docker prerequisites
• deterministic reference-trace and Dashboard validation evidence
• current SledTrace-branded README screenshots
• focused contribution templates and a repeatable release checklist

Install the Python SDK

python -m pip install sledtrace==0.7.0

Preferred usage remains:

from sledtrace import trace

The legacy raglens import remains temporarily available for migration compatibility.

Serving boundary

The wheel contains the Python SDK and sledtrace CLI. It does not bundle the Go Collector, Dashboard, Docker files, or a standalone serving runtime.

• sledtrace --help, sledtrace serve --help, and sledtrace version work after package installation.
• sledtrace serve starts local services only from inside a SledTrace source checkout.
• Outside a checkout, sledtrace serve exits non-zero with guidance to clone the repository and use the documented local stack.

Clean-clone evidence

The v0.7 release candidate was cloned into a new directory and validated with the non-Docker fallback on Windows:

• Collector health returned {"service":"sledtrace-collector","status":"ok"}.
• all nine deterministic reference_rag_app traces flushed successfully
• the Dashboard displayed current SledTrace branding and all nine traces
• the conflict case displayed 30-day versus 14-day retrieved-chunk evidence
• the weak case displayed low-score, weak-match, and unsupported-claim diagnostics

Docker Desktop was installed on the validation host but could not start because WSL2 virtualization was disabled. The Docker path therefore remains covered by the existing Docker configuration and prior v0.4 smoke evidence; the v0.7 clean-clone run used the documented non-Docker path and added explicit Docker prerequisites.

Scope preserved

v0.7.0 does not add:

• span types beyond retrieval and llm
• LangChain or LlamaIndex adapters
• cloud hosting, authentication, or hosted services
• agent/tool/memory tracing
• LLM-as-judge evaluation
• new warning rules or storage/API schema changes

Production publication validation

• immutable annotated tag v0.7.0 targets release commit 58887907973aff3948d2cf3667681832f4305ec6
• protected Trusted Publishing workflow passed: https://github.com/Schromeo/SledTrace/actions/runs/34410674101
• production package: https://pypi.org/project/sledtrace/0.7.0/
• a no-cache install of sledtrace==0.7.0 from production PyPI succeeded in a new virtual environment outside the repository
• preferred sledtrace and temporary legacy raglens imports passed and reported 0.7.0
• installed CLI help, serve help, and version passed
• wheel-installed sledtrace serve outside a checkout exited non-zero with the documented source-checkout guidance

Release-preparation validation

• Python SDK: 17 tests passed
• wheel and source distribution: built successfully for 0.7.0
• package metadata and long description: twine check passed
• clean-wheel preferred and legacy imports: passed
• installed CLI help, serve help, and version: passed with version 0.7.0
• wheel-installed serve outside a checkout: expected non-zero exit and guidance passed
• Go Collector API, storage, and warning tests: passed
• Dashboard 0.7.0 TypeScript and Vite production build: passed
• repository whitespace check: passed