Skip to content

Releases

Trajectory Fidelity Bridge v0.4.2

Choose a tag to compare

@atomicdjt atomicdjt released this 21 Oct 04:36
d6a7027

Fixes #45. Removes the obsolete Ruff DTZ001 suppression without changing runtime behavior. Release metadata updated for 0.4.2. The full Python/platform CI matrix and package checks passed on PR #46.

Trajectory Fidelity Bridge v0.4.1

Choose a tag to compare

@atomicdjt atomicdjt released this 28 Sep 18:26
136d1a1

Changed

  • Published this release as atomicdjt-trajectory-fidelity-bridge. The existing atomicdjt-agent-session-bridge PyPI project and its 0.4.0 release remain available for users who have not migrated.
  • Added the tfb command as a shorter alias while retaining agent-session for existing scripts and documentation.
  • Updated repository links and citation metadata to the renamed GitHub repository.

Migration

  • Existing installations of atomicdjt-agent-session-bridge==0.4.0 continue to work. New environments should install atomicdjt-trajectory-fidelity-bridge.
  • See the PyPI migration guide before switching an existing environment.

Agent Session Bridge v0.4.0

Choose a tag to compare

@atomicdjt atomicdjt released this 25 Sep 03:26

Agent Session Bridge v0.4.0

This backward-compatible release makes the merged Claude Code evidence work available on PyPI.

Highlights

  • agent-session explain renders imported ATIF trajectories as a deterministic Markdown account of steps, tool calls, results, provenance, and conversion limits.
  • Claude Code imports provide finer fidelity evidence for unsupported bookkeeping, potentially content-bearing and unrecognized records, ignored fields, and duplicate usage records.
  • The project adds a controlled real Claude Code fixture with synthetic data, pseudonymized identifiers, explicit provenance, and regression coverage.
  • A private local-only sanitizer and review procedure supports preparing controlled real-session candidates without publishing raw logs.

Correctness and boundaries

  • Observed model names and token usage are carried to compatible ATIF step fields. Cost is unavailable and is not inferred.
  • The fixture preserves its source SHA-256 on Windows checkouts and verifies tool-result correlation.
  • It covers one controlled Windows session from Claude Code 2.1.266 using Read, Bash, Edit, and Write. It does not establish general compatibility across versions, operating systems, session shapes, or tools.

Verification

  • Built both wheel and source distribution; both passed twine check.
  • Installed the wheel in a fresh environment and confirmed version 0.4.0 and agent-session explain --help.
  • Ruff, Mypy, all 213 pytest tests, and the semantic interoperability corpus passed locally.
  • Protected pull request checks and post-merge CI and CodeQL passed on the tagged release commit.

Full details are in CHANGELOG.md.

Agent Session Bridge v0.3.0

Choose a tag to compare

@atomicdjt atomicdjt released this 21 Sep 09:43

Agent Session Bridge v0.3.0

Interoperability and fidelity hardening for the Claude Code → ATIF v1.7 path, a stronger heuristic redactor, and the ATIF differential-conformance corpus and verifier added since v0.2.1. No breaking change to the ATIF output contract; the ASB fidelity report gains two additive counters.

Interoperability and fidelity

  • Timestamp loss is now reported, never fabricated. ATIF v1.7 has no timestamp on an observation result, so a tool result's own timestamp cannot be carried. It is counted as fidelity.omitted_tool_result_timestamps instead of being dropped silently or copied onto another step.
  • Invalid source timestamps no longer abort an import. A non-string or non-ISO-8601 timestamp is omitted and counted as fidelity.invalid_source_timestamps; the record is otherwise converted.
  • Unknown structure no longer becomes known semantics. text blocks with null/non-string text and tool_use blocks with no string name are counted as unsupported instead of emitting the literal "None". is_error is preserved as the source value instead of coerced with bool() ("false" was recorded as an error).
  • Includes the differential conformance corpus, interoperability.reproduce/verifier modules, structured tool-result arrays, multimodal omission reporting, span-status correction, and provider-attribution precedence merged since v0.2.1.

Conformance verifier

  • Reads source lines exactly as the parser does; U+2028/U+0085 inside a JSON string no longer create phantom records or shift source positions.
  • tool_result_timestamps is derived from the source (NOT_APPLICABLE when nothing is timestamped) and cross-checked against ASB's fidelity counter.

Security

  • Redaction closes realistic leaks reproduced with synthetic values: prefixed env vars (OPENAI_API_KEY=…, GITHUB_TOKEN=…, DB_PASSWORD=…), Authorization schemes beyond Bearer, Cookie/Set-Cookie, --token VALUE, curl -u, URL user-info, client_secret/refresh_token/id_token, JSON-escaped pairs, PEM private keys, JWTs, AWS access-key IDs.
  • Names are matched by their ending, so credential_type, max_tokens, tokenizer, password_file stay visible. Matching is linear on adversarial input.
  • Redaction remains heuristic. docs/SECURITY.md now states what is matched and what is not claimed.

Tests and metadata

  • 158 tests (up from 77), including regression tests that fail against v0.2.1 behavior; a test keeps pyproject.toml, CITATION.cff and the README pin in sync.

Known limitations

  • ATIF v1.7 cannot represent tool-result timestamps (reported, not recoverable). atif 1.7.0 is still the only released version; ASB stays on atif>=1.7,<1.8.
  • Thinking, image, document, server-tool and unknown Claude blocks remain unsupported (counted, not converted).
  • Not detected by redaction: short secrets, unlisted names, mysql -pSECRET, npm/cloud tokens without a listed shape, encoded values.
  • ASB is transcript/session interchange; it does not resume sessions natively in any harness.
  • The wheel installs generic top-level packages (adapters, bridge, cli, security, …); namespacing them is future work.

Full PR: #36

Agent Session Bridge v0.2.1

Choose a tag to compare

@atomicdjt atomicdjt released this 25 Aug 13:29
fc559bb

Agent Session Bridge v0.2.1

This release prepares Agent Session Bridge for its first PyPI Trusted Publishing release.

Changes

  • Bumps the package version to 0.2.1.
  • Aligns citation metadata with the package version.
  • Adds release tag/version consistency verification.
  • Publishes through GitHub Actions using PyPI Trusted Publishing.

Agent Session Bridge v0.2.0 — Historical ATIF Observability

Choose a tag to compare

@atomicdjt atomicdjt released this 23 Aug 13:32
1a6a2e6

Agent Session Bridge v0.2.0 — Historical ATIF Observability

v0.2.0 adds an optional historical observability projection for portable ATIF trajectories.

Agent Session Bridge can now take previously captured Claude Code or ATIF trajectories and reconstruct them as OpenTelemetry/OpenInference-compatible traces for export over OTLP to Phoenix or another compatible backend.

Highlights

  • New agent-session observe command.
  • Projects canonical ATIF v1.7 trajectories into a CHAIN → AGENT → TOOL trace hierarchy.
  • Supports local Phoenix visualization through OTLP/HTTP.
  • Three explicit privacy modes:
    • metadata-only — default; sensitive content is not exported.
    • redacted-content — content is projected after ASB redaction.
    • full-content — content is exported only when explicitly requested.
  • Preserves source-observed timestamp provenance rather than presenting reconstructed traces as original runtime instrumentation.
  • Requires timezone-aware source timestamps and rejects ambiguous timestamps.
  • Uses exact integer timestamp conversion without floating-point precision loss.
  • Handles timezone offsets safely across Python's supported datetime range.
  • Rejects empty trajectories rather than reporting false export success.
  • Reports OTLP collector/export failure instead of silently succeeding.
  • Observability dependencies remain isolated behind the optional observability extra.

Design boundary

ATIF remains the portable source of truth.

The observability layer is a downstream historical projection: it reconstructs telemetry after execution from a preserved trajectory. It does not claim to reproduce original runtime instrumentation or measured execution durations that were not present in the source data.

Example

python -m pip install -e ".[observability]"
python -m pip install arize-phoenix

agent-session observe trajectory.atif.json \
  --from atif \
  --backend phoenix \
  --endpoint http://127.0.0.1:6006/v1/traces

See docs/OBSERVABILITY.md for the semantic mapping, privacy model, timestamp provenance rules, and known limitations.

Verification

The merged implementation passed the full repository test suite, Ruff, mypy, canonical CLI regression checks, CodeRabbit review, and the GitHub Actions matrix across:

  • Windows / Python 3.11 and 3.12
  • Ubuntu / Python 3.11 and 3.12
  • macOS / Python 3.11 and 3.12

PR: #10

v0.1.0

Choose a tag to compare

@atomicdjt atomicdjt released this 21 Aug 15:57

Initial public release: ASEF canonical schema, Claude Code JSONL import, validation, explicit fidelity/loss accounting, secret redaction, CLI tooling, reference mapping to observed Antigravity derived-log structures, Antigravity integration RFC, and adversarial verification evidence. Does not provide supported native Antigravity session ingestion (no upstream import API exists).