Changelog

Fleet management + MDM providers

• Added tenant-scoped MDM provider configuration and sync workflows for Jamf and Intune.
• Fleet management now supports on-demand provider inventory synchronization to upsert endpoint records.
• Provider sync now supports default fleet and environment mapping for imported endpoints.

Headless control plane

• thothctl is now documented as the default admin path for no-dashboard bootstrap and updates.
• New GitOps headless section covers Terraform, Pulumi, Argo CD, and GovAPI orchestration patterns.
• GitOps docs now use public-provider/public-runbook distribution patterns instead of internal module paths.
• SIEM/PAM integration guidance is now aligned to API-first and CI-driven operations.

Event pipeline deployment

• ECS deployment workflows now enforce eventingestor as a Rust service target.
• Deployment matrix validation now fails if eventingestor drifts out of the Rust service group.

Manual endpoint enrollment

• Fleet management now provides generated re-enrollment scripts for endpoints not associated with a fleet.
• Direct endpoint enrollment supports optional fleet assignment through THOTH_FLEET_ID.
• Endpoint health state remains current through periodic proxy check-ins.

Documentation

• Added external-facing docs for MDM provider sync and manual endpoint enrollment flow.
• Proxy install docs now default to thoth/v0.2.8.
• Added public-platform delivery workflows: Terraform-based public repo bootstrap and CI mirroring for provider/runbook content.

MCP Proxy (thoth binary)

• Endpoint identity resolution now defaults to immutable machine identity (Intune/Jamf managed ID override, then OS machine ID), with hostname only as last-resort fallback.
• THOTH_USER_ID remains required and must be a valid email address.
• enforcer_url and govapi_url are inferred from tenant_id + apex_domain.
• --enforcer-url / THOTH_ENFORCER_URL are now deprecated and ignored.

Enforcer

• Requests with valid keys now proceed even when endpoint/fleet scope context does not match exactly; enforcer emits warnings for follow-up.
• Tenant user-domain mismatches are now warn-only when key validation succeeds.

Documentation

• Customer docs now reflect thoth/v0.2.7 defaults for identity, URL inference, and runtime env expectations.

MCP Proxy (thoth binary)

• thoth wrap-config now supports repeatable --env KEY=VALUE to inject runtime environment values directly into selected MCP server entries.
• Wrap output remains idempotent and now reports environment changes when values are updated.
• Fleet registration URL handling is simplified:
  • govapi_url is derived automatically from tenant_id + apex_domain as https://grid.<tenant>.<apex-domain>.
  • enforcer_url is derived automatically as https://enforce.<tenant>.<apex-domain> when not explicitly set.
  • legacy gov_api_url compatibility paths are removed.
• Runtime identity hardening:
  • THOTH_USER_ID must be a valid email address.
  • customer domain policy is enforced centrally by enforcer tenant metadata (admin-managed), with automatic request blocking for non-matching user domains.

Documentation

• Customer-facing docs are updated for v0.2.3.
• Proxy setup examples now use supported wrap-config flags and document inline environment injection via --env.

Proxy + SDK enforcement behavior

• Go and proxy paths now enforce fail-closed posture on enforcer/runtime failures.
• Enforcement payload contract is normalized to canonical fields:
  • tool_args
  • enforcement_trace_id
  • user_id, approved_scope, session_intent, session_tool_calls
• Session tool-call history is bounded to the latest 128 calls for parity across Go and proxy paths.

Documentation

• Docs now reflect fail-closed behavior in SDK guidance and security posture sections.
• Version banners and docs-site changelog are updated for the latest SDK/proxy releases.

Python SDK (aten-thoth)

• BehavioralEvent now includes endpoint context fields:
  • endpoint_id
  • hostname
• BehavioralEvent now includes WORM chain evidence fields:
  • chain_index
  • hash
  • previous_hash
  • signature
• Dependency lock/metadata refreshed as part of the SDK patch line.

TypeScript SDK (@atensec/thoth)

• Enforcer payload now propagates:
  • tool_args
  • user_id
  • metadata.policy_context
  • enforcement_trace_id
• ThothConfig adds:
  • policyContext
  • enforcementTraceId
• Instrumentation now serializes tool call arguments safely before enforcement checks.

MCP Proxy (thoth binary)

• Emitted events now include normalized top-level endpoint metadata:
  • endpoint_id
  • hostname
• Event metadata includes hostname consistently for downstream pipelines.
• MCP proxy distribution now uses the cross-platform thoth binary release line.
• Docs + install path standardized to:
  • curl -fsSL https://install.atensecurity.com/thoth | sh
  • GitHub release assets from atensecurity/thoth

Unified SDK API URL contract

• Go, Python, and TypeScript SDKs now use a single tenant API URL for both:
  • policy enforcement (POST /v1/enforce)
  • behavioral event ingestion (POST /v1/events/batch)
• SDK startup now requires tenant API URL configuration via:
  • explicit config (APIURL / api_url / apiUrl)
  • or THOTH_API_URL
• Removed SDK fallbacks to hosted global defaults and split endpoint semantics.

Go SDK

• NewClient now fails fast when APIURL is missing.
• Examples and tests updated to pass THOTH_API_URL explicitly.
• SDK docs now include required env setup and quickstart examples.

Python SDK

• ThothConfig now requires tenant API URL resolution (api_url or THOTH_API_URL) and enforces a single URL contract.
• resolved_enforcer_url now follows the single-URL contract and mirrors resolved_api_url.
• session_intent is now accepted in config and passed to enforcement payloads.
• Step-up polling now sends auth headers when api_key is present.

TypeScript SDK

• Removed HOSTED_API_URL fallback and split enforcer semantics.
• instrument() now throws at startup when apiUrl/THOTH_API_URL is missing.
• Enforcement and event emission now route through the same tenant API URL.
• sessionIntent is now supported in config and forwarded to enforcement payloads.
• Runtime/test baseline updated and validated for Node.js 18+ compatibility.