CallTelemetry Elixir Test Harness

Portable policy-enforcing test harness and MCP server for CallTelemetry Elixir repositories.

The planned execution model delegates healthy local test runs to FMix and may route resource-constrained workloads to a governed Blacksmith Testbox. Headless Blacksmith execution remains disabled until Blacksmith provides a supported, scoped, expiring, independently revocable token lifecycle.

This repository is private. Runtime secrets must not be committed, logged, passed through process arguments, or persisted in fallback/cache files.

Distribution and release

The GitHub repository remains private while the npm package is public so a workload can install the CLI or MCP server with credential-free npx. Releases are created by Release Please and published only from its exact v<version> tag through npm trusted publishing (GitHub Actions OIDC); this repository does not use NPM_TOKEN. npm does not generate provenance for packages published from a private GitHub repository, so this release workflow intentionally does not claim or request it.

Before the first release, an npm organization administrator must configure the trusted publisher for @calltelemetry/elixir-test-harness to this repository's Release workflow and the protected GitHub npm environment. That external registry/environment setup is intentionally pending and is not represented by a secret in this repository. The enterprise currently also disables write permissions for GitHub Actions workflows, so Release Please cannot open its release PR until an enterprise administrator enables the narrowly scoped workflow permission or provides an approved repository-scoped app credential. Run npm run package:smoke to validate the packed, installed CLI and MCP binaries without publishing.

Status

Initial implementation. The first gate is a token-free, test-driven proof of the isolated Blacksmith authentication process contract and Doppler transport.