agentledger-runtime 1.2.4__tar.gz → 1.3.0__tar.gz

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/CHANGELOG.md

@@ -8,6 +8,21 @@ This project follows semantic versioning for the stable runtime-core contract. O
 
 No unreleased changes yet.
 
+## 1.3.0
+
+### Added
+
+- `agentledger inspector` CLI with read-only `run` and `evidence` subcommands.
+- Language-neutral Inspector read model `agentledger.inspector.v1` for run timeline, Tool Ledger, approvals, policy decisions, cost/failure records, artifacts, and risk flags.
+- Static HTML Inspector export for local or internal debugging without starting a server.
+- Read-only SQLite runtime data source and Postgres/MySQL read data sources through existing StateStore adapter boundaries.
+- Optional `agentledger-inspector` companion package for users who want to depend on the read model and extension API directly.
+
+### Clarified
+
+- Inspector is an evidence/runtime metadata consumer, not a permissions system or write/control plane.
+- Use read-only database credentials for Postgres/MySQL inspection; evidence-bundle input remains the most portable path across Python, Go, TypeScript, and Rust.
+
 ## 1.2.4
 
 ### Added
@@ -127,7 +142,7 @@ No unreleased changes yet.
 
 - Python reference runtime-core parity is now declared for Go, TypeScript, and Rust within the AgentLedger core scope.
 - Concrete production adapters such as Postgres, S3/MinIO, Docker, Kubernetes, MCP transport, LangGraph, Temporal, and OpenTelemetry remain optional packages unless explicitly shipped for a language.
-- AgentLedger remains a framework/library/runtime layer, not SaaS and not a general workflow, eval, RAG, or deployment platform.
+- AgentLedger remains a framework/library/runtime layer, not a managed service and not a general workflow, eval, RAG, or deployment product.
 
 ## 1.0.0
 

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentledger-runtime
-Version: 1.2.4
+Version: 1.3.0
 Summary: Runtime reliability layer for Agent Harness stacks
 Project-URL: Homepage, https://github.com/yaogdu/AgentLedger
 Project-URL: Repository, https://github.com/yaogdu/AgentLedger
@@ -21,30 +21,33 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: >=3.11
 Provides-Extra: all
-Requires-Dist: agentledger-langfuse<2,>=1.2; extra == 'all'
-Requires-Dist: agentledger-langgraph<2,>=1.2; extra == 'all'
-Requires-Dist: agentledger-mcp<2,>=1.2; extra == 'all'
-Requires-Dist: agentledger-mysql<2,>=1.2; extra == 'all'
-Requires-Dist: agentledger-otel<2,>=1.2; extra == 'all'
-Requires-Dist: agentledger-postgres<2,>=1.2; extra == 'all'
-Requires-Dist: agentledger-s3<2,>=1.2; extra == 'all'
-Requires-Dist: agentledger-sandbox-docker<2,>=1.2; extra == 'all'
+Requires-Dist: agentledger-inspector<2,>=1.3; extra == 'all'
+Requires-Dist: agentledger-langfuse<2,>=1.3; extra == 'all'
+Requires-Dist: agentledger-langgraph<2,>=1.3; extra == 'all'
+Requires-Dist: agentledger-mcp<2,>=1.3; extra == 'all'
+Requires-Dist: agentledger-mysql<2,>=1.3; extra == 'all'
+Requires-Dist: agentledger-otel<2,>=1.3; extra == 'all'
+Requires-Dist: agentledger-postgres<2,>=1.3; extra == 'all'
+Requires-Dist: agentledger-s3<2,>=1.3; extra == 'all'
+Requires-Dist: agentledger-sandbox-docker<2,>=1.3; extra == 'all'
 Provides-Extra: docker
-Requires-Dist: agentledger-sandbox-docker<2,>=1.2; extra == 'docker'
+Requires-Dist: agentledger-sandbox-docker<2,>=1.3; extra == 'docker'
+Provides-Extra: inspector
+Requires-Dist: agentledger-inspector<2,>=1.3; extra == 'inspector'
 Provides-Extra: langfuse
-Requires-Dist: agentledger-langfuse<2,>=1.2; extra == 'langfuse'
+Requires-Dist: agentledger-langfuse<2,>=1.3; extra == 'langfuse'
 Provides-Extra: langgraph
-Requires-Dist: agentledger-langgraph<2,>=1.2; extra == 'langgraph'
+Requires-Dist: agentledger-langgraph<2,>=1.3; extra == 'langgraph'
 Provides-Extra: mcp
-Requires-Dist: agentledger-mcp<2,>=1.2; extra == 'mcp'
+Requires-Dist: agentledger-mcp<2,>=1.3; extra == 'mcp'
 Provides-Extra: mysql
-Requires-Dist: agentledger-mysql<2,>=1.2; extra == 'mysql'
+Requires-Dist: agentledger-mysql<2,>=1.3; extra == 'mysql'
 Provides-Extra: otel
-Requires-Dist: agentledger-otel<2,>=1.2; extra == 'otel'
+Requires-Dist: agentledger-otel<2,>=1.3; extra == 'otel'
 Provides-Extra: postgres
-Requires-Dist: agentledger-postgres<2,>=1.2; extra == 'postgres'
+Requires-Dist: agentledger-postgres<2,>=1.3; extra == 'postgres'
 Provides-Extra: s3
-Requires-Dist: agentledger-s3<2,>=1.2; extra == 's3'
+Requires-Dist: agentledger-s3<2,>=1.3; extra == 's3'
 Description-Content-Type: text/markdown
 
 # AgentLedger
@@ -52,7 +55,7 @@ Description-Content-Type: text/markdown
 [English](README.md) | [中文](README.zh-CN.md)
 
 ![Python 3.11+](https://img.shields.io/badge/Python-3.11%2B-3776AB?logo=python&logoColor=white)
-![Version 1.2.4 stable](https://img.shields.io/badge/Version-1.2.4--stable-111827)
+![Version 1.3.0 stable](https://img.shields.io/badge/Version-1.3.0--stable-111827)
 ![License Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-0f766e)
 ![Runtime Durable](https://img.shields.io/badge/Runtime-durable%20execution-1f6feb)
 ![Storage SQLite/Postgres/MySQL](https://img.shields.io/badge/Storage-SQLite%20%7C%20Postgres%20%7C%20MySQL-b45309)
@@ -61,7 +64,7 @@ Description-Content-Type: text/markdown
 
 Your agent called a tool. Did it happen? Can you retry safely? Can you prove it later?
 
-AgentLedger `1.2.4` is a runtime reliability layer for Agent Harness stacks. It does not try to teach agents how to reason or replace the surrounding harness ecosystem; it makes agent runs durable, auditable, replayable, policy-governed, and recoverable when workers crash, tools fail, or prompts change.
+AgentLedger `1.3.0` is a runtime reliability layer for Agent Harness stacks. It does not try to teach agents how to reason or replace the surrounding harness ecosystem; it makes agent runs durable, auditable, replayable, policy-governed, and recoverable when workers crash, tools fail, or prompts change.
 
 Most agent frameworks focus on planning, reasoning, and workflow logic. AgentLedger sits underneath or beside LangChain, LangGraph, CrewAI, AutoGen, OpenAI Agents SDK, LlamaIndex, Semantic Kernel, or custom agents to provide runtime guarantees around state, tools, evidence, replay, and recovery.
 
@@ -77,6 +80,7 @@ Python remains the reference implementation, and Go, TypeScript, and Rust now ha
 | Choose Python / Go / TypeScript / Rust | [docs/LANGUAGE_QUICKSTART.md](docs/LANGUAGE_QUICKSTART.md) |
 | Find runnable examples | [examples/README.md](examples/README.md), [go/examples/README.md](go/examples/README.md), [typescript/examples/README.md](typescript/examples/README.md), [rust/examples/README.md](rust/examples/README.md) |
 | Query runtime tables | [docs/QUERY_EXAMPLES.md](docs/QUERY_EXAMPLES.md) |
+| Inspect a run visually | [docs/INSPECTOR.md](docs/INSPECTOR.md) |
 | Understand Harness stack composition | [docs/HARNESS_STACK.md](docs/HARNESS_STACK.md) |
 | Understand open-source impact | [docs/OPEN_SOURCE_IMPACT.md](docs/OPEN_SOURCE_IMPACT.md) |
 | Understand maintainer responsibilities | [docs/MAINTAINER_NOTES.md](docs/MAINTAINER_NOTES.md) |
@@ -93,7 +97,7 @@ Python remains the reference implementation, and Go, TypeScript, and Rust now ha
 | What is stable? | The v1.x runtime-core contract: durable execution, Tool Ledger, evidence/replay, policy/approval/sandbox boundaries, cost/failure reports, worker/conformance, and Python reference implementation with Go/TypeScript/Rust runtime-core parity gates. |
 | What is optional? | Postgres, MySQL, S3/MinIO, framework-native packages, OTLP collector transport, sandbox infrastructure, distributed deployment recipes, and real-service hardening. |
 | What is experimental? | Some concrete provider adapters, media/stream processing adapters, and real-service hardening paths. Go/TypeScript/Rust runtime-core baselines are native implementations covered by shared conformance. |
-| What is not in core? | Planning engines, full eval systems, RAG/vector memory, trace stores, hosted application products, and hosted sandbox infrastructure. |
+| What is not in core? | Planning engines, full eval systems, RAG/vector memory, trace stores, application administration backends, and sandbox infrastructure providers. |
 | How should other languages work? | This repo is contract-first. Python is the reference runtime; Go, Node/TypeScript, and Rust now have native runtime baselines under `go/`, `typescript/`, and `rust/`. Runtime-ready requires `contracts/agentledger.runtime.v1.json`, the shared semantic manifest `contracts/conformance/runtime_semantics.v1.json`, shared conformance fixtures, and per-language conformance commands. |
 
 ## Scope principle
@@ -329,7 +333,7 @@ AgentLedger is also not a new LLM SDK, not a workflow engine, not a general obse
 
 ## Current maturity
 
-AgentLedger 1.2.4 is a stable runtime-core release with Python as the reference implementation and Go, TypeScript, and Rust covered by shared runtime-core parity gates. It is suitable for local use, framework adapter integration, reliability semantics validation, and production pilot preparation with explicit adapter boundaries.
+AgentLedger 1.3.0 is a stable runtime-core release with Python as the reference implementation and Go, TypeScript, and Rust covered by shared runtime-core parity gates. It is suitable for local use, framework adapter integration, reliability semantics validation, and production pilot preparation with explicit adapter boundaries.
 
 The runtime-core contract is stable; optional production adapters and external infrastructure hardening remain separately tracked. See [docs/MATURITY_MODEL.md](docs/MATURITY_MODEL.md), [docs/IMPLEMENTATION_STATUS.md](docs/IMPLEMENTATION_STATUS.md), and [docs/ROADMAP.md](docs/ROADMAP.md).
 
@@ -338,6 +342,7 @@ The runtime-core contract is stable; optional production adapters and external i
 | Goal | Document |
 | --- | --- |
 | Use the runtime | [docs/USAGE.md](docs/USAGE.md) |
+| Inspect runtime evidence | [docs/INSPECTOR.md](docs/INSPECTOR.md) |
 | Understand architecture | [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) |
 | Compare with adjacent tools | [docs/COMPARISONS.md](docs/COMPARISONS.md) |
 | Read implementation details | [docs/DESIGN_AND_IMPLEMENTATION.md](docs/DESIGN_AND_IMPLEMENTATION.md) |

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/README.md

@@ -3,7 +3,7 @@
 [English](README.md) | [中文](README.zh-CN.md)
 
 ![Python 3.11+](https://img.shields.io/badge/Python-3.11%2B-3776AB?logo=python&logoColor=white)
-![Version 1.2.4 stable](https://img.shields.io/badge/Version-1.2.4--stable-111827)
+![Version 1.3.0 stable](https://img.shields.io/badge/Version-1.3.0--stable-111827)
 ![License Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-0f766e)
 ![Runtime Durable](https://img.shields.io/badge/Runtime-durable%20execution-1f6feb)
 ![Storage SQLite/Postgres/MySQL](https://img.shields.io/badge/Storage-SQLite%20%7C%20Postgres%20%7C%20MySQL-b45309)
@@ -12,7 +12,7 @@
 
 Your agent called a tool. Did it happen? Can you retry safely? Can you prove it later?
 
-AgentLedger `1.2.4` is a runtime reliability layer for Agent Harness stacks. It does not try to teach agents how to reason or replace the surrounding harness ecosystem; it makes agent runs durable, auditable, replayable, policy-governed, and recoverable when workers crash, tools fail, or prompts change.
+AgentLedger `1.3.0` is a runtime reliability layer for Agent Harness stacks. It does not try to teach agents how to reason or replace the surrounding harness ecosystem; it makes agent runs durable, auditable, replayable, policy-governed, and recoverable when workers crash, tools fail, or prompts change.
 
 Most agent frameworks focus on planning, reasoning, and workflow logic. AgentLedger sits underneath or beside LangChain, LangGraph, CrewAI, AutoGen, OpenAI Agents SDK, LlamaIndex, Semantic Kernel, or custom agents to provide runtime guarantees around state, tools, evidence, replay, and recovery.
 
@@ -28,6 +28,7 @@ Python remains the reference implementation, and Go, TypeScript, and Rust now ha
 | Choose Python / Go / TypeScript / Rust | [docs/LANGUAGE_QUICKSTART.md](docs/LANGUAGE_QUICKSTART.md) |
 | Find runnable examples | [examples/README.md](examples/README.md), [go/examples/README.md](go/examples/README.md), [typescript/examples/README.md](typescript/examples/README.md), [rust/examples/README.md](rust/examples/README.md) |
 | Query runtime tables | [docs/QUERY_EXAMPLES.md](docs/QUERY_EXAMPLES.md) |
+| Inspect a run visually | [docs/INSPECTOR.md](docs/INSPECTOR.md) |
 | Understand Harness stack composition | [docs/HARNESS_STACK.md](docs/HARNESS_STACK.md) |
 | Understand open-source impact | [docs/OPEN_SOURCE_IMPACT.md](docs/OPEN_SOURCE_IMPACT.md) |
 | Understand maintainer responsibilities | [docs/MAINTAINER_NOTES.md](docs/MAINTAINER_NOTES.md) |
@@ -44,7 +45,7 @@ Python remains the reference implementation, and Go, TypeScript, and Rust now ha
 | What is stable? | The v1.x runtime-core contract: durable execution, Tool Ledger, evidence/replay, policy/approval/sandbox boundaries, cost/failure reports, worker/conformance, and Python reference implementation with Go/TypeScript/Rust runtime-core parity gates. |
 | What is optional? | Postgres, MySQL, S3/MinIO, framework-native packages, OTLP collector transport, sandbox infrastructure, distributed deployment recipes, and real-service hardening. |
 | What is experimental? | Some concrete provider adapters, media/stream processing adapters, and real-service hardening paths. Go/TypeScript/Rust runtime-core baselines are native implementations covered by shared conformance. |
-| What is not in core? | Planning engines, full eval systems, RAG/vector memory, trace stores, hosted application products, and hosted sandbox infrastructure. |
+| What is not in core? | Planning engines, full eval systems, RAG/vector memory, trace stores, application administration backends, and sandbox infrastructure providers. |
 | How should other languages work? | This repo is contract-first. Python is the reference runtime; Go, Node/TypeScript, and Rust now have native runtime baselines under `go/`, `typescript/`, and `rust/`. Runtime-ready requires `contracts/agentledger.runtime.v1.json`, the shared semantic manifest `contracts/conformance/runtime_semantics.v1.json`, shared conformance fixtures, and per-language conformance commands. |
 
 ## Scope principle
@@ -280,7 +281,7 @@ AgentLedger is also not a new LLM SDK, not a workflow engine, not a general obse
 
 ## Current maturity
 
-AgentLedger 1.2.4 is a stable runtime-core release with Python as the reference implementation and Go, TypeScript, and Rust covered by shared runtime-core parity gates. It is suitable for local use, framework adapter integration, reliability semantics validation, and production pilot preparation with explicit adapter boundaries.
+AgentLedger 1.3.0 is a stable runtime-core release with Python as the reference implementation and Go, TypeScript, and Rust covered by shared runtime-core parity gates. It is suitable for local use, framework adapter integration, reliability semantics validation, and production pilot preparation with explicit adapter boundaries.
 
 The runtime-core contract is stable; optional production adapters and external infrastructure hardening remain separately tracked. See [docs/MATURITY_MODEL.md](docs/MATURITY_MODEL.md), [docs/IMPLEMENTATION_STATUS.md](docs/IMPLEMENTATION_STATUS.md), and [docs/ROADMAP.md](docs/ROADMAP.md).
 
@@ -289,6 +290,7 @@ The runtime-core contract is stable; optional production adapters and external i
 | Goal | Document |
 | --- | --- |
 | Use the runtime | [docs/USAGE.md](docs/USAGE.md) |
+| Inspect runtime evidence | [docs/INSPECTOR.md](docs/INSPECTOR.md) |
 | Understand architecture | [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) |
 | Compare with adjacent tools | [docs/COMPARISONS.md](docs/COMPARISONS.md) |
 | Read implementation details | [docs/DESIGN_AND_IMPLEMENTATION.md](docs/DESIGN_AND_IMPLEMENTATION.md) |

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/README.zh-CN.md

@@ -3,7 +3,7 @@
 [English](README.md) | [中文](README.zh-CN.md)
 
 ![Python 3.11+](https://img.shields.io/badge/Python-3.11%2B-3776AB?logo=python&logoColor=white)
-![Version 1.2.4 stable](https://img.shields.io/badge/Version-1.2.4--stable-111827)
+![Version 1.3.0 stable](https://img.shields.io/badge/Version-1.3.0--stable-111827)
 ![License Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-0f766e)
 ![Runtime Durable](https://img.shields.io/badge/Runtime-durable%20execution-1f6feb)
 ![Storage SQLite/Postgres/MySQL](https://img.shields.io/badge/Storage-SQLite%20%7C%20Postgres%20%7C%20MySQL-b45309)
@@ -12,7 +12,7 @@
 
 你的 Agent 调用了一个工具。它真的执行了吗？可以安全重试吗？之后能证明发生过什么吗？
 
-AgentLedger `1.2.4` 是面向 Agent Harness stack 的 runtime reliability layer。它不负责让 Agent 更会“思考”，也不替代完整 Harness 生态；它负责让 Agent run 在 worker 崩溃、工具失败、prompt 变更和长任务恢复时，仍然具备持久化、可审计、可重放、可治理和可恢复能力。
+AgentLedger `1.3.0` 是面向 Agent Harness stack 的 runtime reliability layer。它不负责让 Agent 更会“思考”，也不替代完整 Harness 生态；它负责让 Agent run 在 worker 崩溃、工具失败、prompt 变更和长任务恢复时，仍然具备持久化、可审计、可重放、可治理和可恢复能力。
 
 大多数 Agent 框架关注 planning、reasoning 和 workflow logic。AgentLedger 放在 LangChain、LangGraph、CrewAI、AutoGen、OpenAI Agents SDK、LlamaIndex、Semantic Kernel 或自定义 Agent 的下方或旁边，提供 state、tool、evidence、replay、recovery 相关的 runtime guarantees。
 
@@ -28,6 +28,7 @@ Python 仍然是 reference implementation；Go、TypeScript、Rust 已有 native
 | 选择 Python / Go / TypeScript / Rust | [docs/zh/LANGUAGE_QUICKSTART.md](docs/zh/LANGUAGE_QUICKSTART.md) |
 | 找可运行示例 | [examples/README.md](examples/README.md)、[go/examples/README.md](go/examples/README.md)、[typescript/examples/README.md](typescript/examples/README.md)、[rust/examples/README.md](rust/examples/README.md) |
 | 查询 runtime 表 | [docs/zh/QUERY_EXAMPLES.md](docs/zh/QUERY_EXAMPLES.md) |
+| 可视化排查 run | [docs/zh/INSPECTOR.md](docs/zh/INSPECTOR.md) |
 | 理解 Harness stack 组合方式 | [docs/zh/HARNESS_STACK.md](docs/zh/HARNESS_STACK.md) |
 | 理解开源生态价值 | [docs/zh/OPEN_SOURCE_IMPACT.md](docs/zh/OPEN_SOURCE_IMPACT.md) |
 | 理解维护者职责 | [docs/zh/MAINTAINER_NOTES.md](docs/zh/MAINTAINER_NOTES.md) |
@@ -281,7 +282,7 @@ AgentLedger 也不是新的 LLM SDK，不是 workflow engine，不是通用 obse
 
 ## 当前成熟度
 
-AgentLedger 1.2.4 是 stable runtime-core release，Python 是 reference implementation，Go、TypeScript、Rust 已由共享 runtime-core parity gate 覆盖；适合本地使用、framework adapter integration、reliability semantics 验证，以及在明确 adapter 边界下做 production pilot 准备。
+AgentLedger 1.3.0 是 stable runtime-core release，Python 是 reference implementation，Go、TypeScript、Rust 已由共享 runtime-core parity gate 覆盖；适合本地使用、framework adapter integration、reliability semantics 验证，以及在明确 adapter 边界下做 production pilot 准备。
 
 runtime-core contract 已稳定；optional production adapter 和外部基础设施加固仍按独立阶段推进。详见 [docs/MATURITY_MODEL.md](docs/MATURITY_MODEL.md)、[docs/zh/IMPLEMENTATION_STATUS.md](docs/zh/IMPLEMENTATION_STATUS.md) 和 [docs/zh/ROADMAP.md](docs/zh/ROADMAP.md)。
 
@@ -290,6 +291,7 @@ runtime-core contract 已稳定；optional production adapter 和外部基础设
 | 目标 | 文档 |
 | --- | --- |
 | 学会使用 runtime | [docs/zh/USAGE.md](docs/zh/USAGE.md) |
+| 查看 runtime evidence | [docs/zh/INSPECTOR.md](docs/zh/INSPECTOR.md) |
 | 理解整体架构 | [docs/zh/ARCHITECTURE.md](docs/zh/ARCHITECTURE.md) |
 | 对比相邻工具 | [docs/zh/COMPARISONS.md](docs/zh/COMPARISONS.md) |
 | 阅读实现细节 | [docs/zh/DESIGN_AND_IMPLEMENTATION.md](docs/zh/DESIGN_AND_IMPLEMENTATION.md) |

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/docs/ADAPTER_CERTIFICATION.md

@@ -212,10 +212,10 @@ This does not make an adapter production-ready by itself. It gives users a concr
 AgentLedger can generate a machine-readable starting bundle for official adapter profiles:
 
 ```bash
-PYTHONPATH=src python3 -m agentledger adapter certify --kind postgres --adapter-version 1.2.4
-PYTHONPATH=src python3 -m agentledger adapter certify --kind mysql --adapter-version 1.2.4 --out ./mysql-certification.json
-PYTHONPATH=src python3 -m agentledger adapter certify --kind s3 --adapter-version 1.2.4 --out ./s3-certification.json
-PYTHONPATH=src python3 -m agentledger adapter certify --kind langgraph --adapter-version 1.2.4 --package-name agentledger-langgraph
+PYTHONPATH=src python3 -m agentledger adapter certify --kind postgres --adapter-version 1.3.0
+PYTHONPATH=src python3 -m agentledger adapter certify --kind mysql --adapter-version 1.3.0 --out ./mysql-certification.json
+PYTHONPATH=src python3 -m agentledger adapter certify --kind s3 --adapter-version 1.3.0 --out ./s3-certification.json
+PYTHONPATH=src python3 -m agentledger adapter certify --kind langgraph --adapter-version 1.3.0 --package-name agentledger-langgraph
 ```
 
 Supported built-in profiles:

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/docs/ADAPTER_PACKAGING.md

@@ -1,6 +1,6 @@
 # Adapter Packaging
 
-AgentLedger `1.2.1` introduced the adapter packaging model, `1.2.2` extended it with the official MySQL storage adapter boundary, and `1.2.3` adds a dependency-free Langfuse evidence/trace export boundary. Runtime-core stays small and dependency-light; concrete integrations move into optional adapter packages that can be installed through extras or directly.
+AgentLedger `1.2.1` introduced the adapter packaging model, `1.2.2` extended it with the official MySQL storage adapter boundary, `1.2.3` added a dependency-free Langfuse evidence/trace export boundary, and `1.3.0` adds the read-only Inspector companion package. Runtime-core stays small and dependency-light; concrete integrations and external evidence consumers move into optional packages that can be installed through extras or directly.
 
 ## Why Split Adapters
 
@@ -24,7 +24,7 @@ extras preserve easy installation
 
 Adapter packaging is language-specific. The goal is the same across languages, but the package mechanism follows each ecosystem:
 
-| Language | Mechanism in `1.2.x` | Reason |
+| Language | Mechanism | Reason |
 | --- | --- | --- |
 | Python | separate PyPI packages under `packages/` plus `agentledger-runtime[...]` extras | Python extras are the cleanest way to keep optional SDK dependencies out of core |
 | TypeScript/Node | `agentledger-runtime` subpath exports plus separate npm adapter packages under `typescript/packages/` | subpath exports are ergonomic for local use; adapter packages preserve future independent npm releases |
@@ -50,6 +50,7 @@ pip install "agentledger-runtime[mcp]"
 pip install "agentledger-runtime[otel]"
 pip install "agentledger-runtime[langfuse]"
 pip install "agentledger-runtime[docker]"
+pip install "agentledger-runtime[inspector]"
 pip install "agentledger-runtime[all]"
 ```
 
@@ -64,6 +65,7 @@ pip install agentledger-mcp
 pip install agentledger-otel
 pip install agentledger-langfuse
 pip install agentledger-sandbox-docker
+pip install agentledger-inspector
 ```
 
 Use extras for normal projects. Use direct adapter packages when an organization wants explicit dependency locks, separate package mirrors, or independent adapter release governance.
@@ -89,6 +91,7 @@ agentledger-runtime/
     agentledger-otel/
     agentledger-langfuse/
     agentledger-sandbox-docker/
+    agentledger-inspector/                 # companion package, not an adapter
   typescript/
     src/adapters/                        # runtime subpath exports
     packages/                            # npm adapter packages
@@ -132,7 +135,7 @@ Each adapter package should provide:
 
 ## First Adapter Packages
 
-| Package | Owns in `1.2.x` | Dependency status |
+| Package | Owns in current `1.3.x` release train | Dependency status |
 | --- | --- | --- |
 | `agentledger-postgres` | `PostgresStore`, `PostgresStoreConfig`, migration/conformance helpers | Requires `psycopg[binary]`; production rollout still needs real-service drills. |
 | `agentledger-mysql` | `MySQLStore`, `MySQLStoreConfig`, migration/conformance helpers | Requires `pymysql`; production rollout still needs real-service drills. |
@@ -143,6 +146,18 @@ Each adapter package should provide:
 | `agentledger-langfuse` | Langfuse-style evidence/trace payload export | Current package is dependency-light; Langfuse SDK/server ingestion behavior remains application/deployment validation. |
 | `agentledger-sandbox-docker` | Docker sandbox executor package and local/team recipes | Current boundary can use Docker CLI/manifest semantics; daemon hardening, network policy, and resource validation are external. |
 
+## Companion Packages
+
+Not every optional package is an adapter. `agentledger-inspector` is a read-only evidence/runtime metadata consumer. It uses the same package and extra mechanism for installation convenience, but it does not provide a storage, framework, sandbox, model, or observability adapter.
+
+```bash
+pip install "agentledger-runtime[inspector]"
+agentledger inspector evidence ./evidence/<run_id> --html ./inspector.html
+agentledger inspector run <run_id> --root .agentledger --html ./inspector.html
+```
+
+The Inspector package should remain read-only and dependency-light. Web servers, authentication, deployment management, and write/control-plane actions are outside this package boundary.
+
 Language fit matters. `agentledger-langgraph` is first-class for Python and TypeScript/Node because those ecosystems have LangGraph packages. Go and Rust expose a generic `framework` adapter boundary instead of pretending a native LangGraph ecosystem exists there.
 
 ## Sandbox Adapter Scope
@@ -195,23 +210,25 @@ Do not remove these shim paths in `1.2.1`. A future `2.0` may remove compatibili
 
 ```toml
 [project.optional-dependencies]
-postgres = ["agentledger-postgres>=1.2,<2"]
-mysql = ["agentledger-mysql>=1.2,<2"]
-s3 = ["agentledger-s3>=1.2,<2"]
-langgraph = ["agentledger-langgraph>=1.2,<2"]
-mcp = ["agentledger-mcp>=1.2,<2"]
-otel = ["agentledger-otel>=1.2,<2"]
-langfuse = ["agentledger-langfuse>=1.2,<2"]
-docker = ["agentledger-sandbox-docker>=1.2,<2"]
+postgres = ["agentledger-postgres>=1.3,<2"]
+mysql = ["agentledger-mysql>=1.3,<2"]
+s3 = ["agentledger-s3>=1.3,<2"]
+langgraph = ["agentledger-langgraph>=1.3,<2"]
+mcp = ["agentledger-mcp>=1.3,<2"]
+otel = ["agentledger-otel>=1.3,<2"]
+langfuse = ["agentledger-langfuse>=1.3,<2"]
+docker = ["agentledger-sandbox-docker>=1.3,<2"]
+inspector = ["agentledger-inspector>=1.3,<2"]
 all = [
-  "agentledger-postgres>=1.2,<2",
-  "agentledger-mysql>=1.2,<2",
-  "agentledger-s3>=1.2,<2",
-  "agentledger-langgraph>=1.2,<2",
-  "agentledger-mcp>=1.2,<2",
-  "agentledger-otel>=1.2,<2",
-  "agentledger-langfuse>=1.2,<2",
-  "agentledger-sandbox-docker>=1.2,<2",
+  "agentledger-postgres>=1.3,<2",
+  "agentledger-mysql>=1.3,<2",
+  "agentledger-s3>=1.3,<2",
+  "agentledger-langgraph>=1.3,<2",
+  "agentledger-mcp>=1.3,<2",
+  "agentledger-otel>=1.3,<2",
+  "agentledger-langfuse>=1.3,<2",
+  "agentledger-sandbox-docker>=1.3,<2",
+  "agentledger-inspector>=1.3,<2",
 ]
 ```
 
@@ -219,18 +236,20 @@ During local monorepo development, tests may install packages from `packages/*`
 
 ## Release Gates
 
-The `1.2.x` packaging release is expected to pass:
+The packaging release is expected to pass:
 
 ```bash
 PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src python3 -m unittest discover -s tests -q
-PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src python3 -m agentledger adapter certify --kind postgres --adapter-version 1.2.4
-PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src python3 -m agentledger adapter certify --kind mysql --adapter-version 1.2.4
+PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src python3 -m agentledger adapter certify --kind postgres --adapter-version 1.3.0
+PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src python3 -m agentledger adapter certify --kind mysql --adapter-version 1.3.0
 PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src python3 scripts/check_adapter_packages.py
 go test ./...
 cd typescript && npm test
 cd rust && cargo test --features adapters-all
 ```
 
+`scripts/check_adapter_packages.py` covers official adapter packages and read-only companion packages. `agentledger-inspector` is checked for metadata, dependency declaration, README, and import smoke coverage, but it remains a companion package rather than an adapter.
+
 Each adapter package should also pass:
 
 ```bash
@@ -239,9 +258,11 @@ python3 -m pip install dist/<adapter>.whl
 python3 -c "import <adapter_import_name>"
 ```
 
-## Non-Goals For 1.2.1
+Rust adapter crates depend on the published `agentledger-runtime` crate version as well as the local monorepo `path` dependency. For a new release train, publish `agentledger-runtime` first; then run `cargo package` or `cargo publish` for `rust/crates/agentledger-*`. Before the runtime crate version exists on crates.io, adapter crate packaging may fail registry dependency resolution even though local tests pass.
+
+## Non-Goals For The Adapter Package Boundary
 
-`1.2.1` should not claim production hardening just because packages exist. The following stay as later work:
+The adapter package boundary should not claim production hardening just because packages exist. The following stay as later work:
 
 - real Postgres/S3 restore drills and load/concurrency reports
 - full framework-native version matrix
@@ -249,4 +270,4 @@ python3 -c "import <adapter_import_name>"
 - Temporal/Ray/Kubernetes backend adapters
 - media processing adapters
 - sub-agent or multi-agent runtime semantics
-- hosted platform, SaaS, long-running UI, or full eval platform
+- long-running UI, deployment management, or full eval system

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/docs/ADAPTER_ROADMAP.md

@@ -21,7 +21,7 @@ An adapter should stay community/experimental when:
 - The upstream SDK is unstable or mostly private/internal.
 - The integration requires opinionated infrastructure that users should own.
 - The runtime can only expose a safe boundary, not guarantee real behavior.
-- The adapter would force core to become a workflow engine, eval platform, SaaS platform, or deployment product.
+- The adapter would force core to become a workflow engine, eval system, application administration backend, or deployment product.
 
 ## Priority 1: Official Adapters
 
@@ -55,7 +55,7 @@ These are valuable but should follow the Priority 1 adapters or remain thinner f
 | Sandbox | Kubernetes Job sandbox | Good production boundary for cluster users. | Should support dry-run manifests, namespace/service account policy, and optional runtimeClass. |
 | Sandbox | E2B | Good managed remote sandbox for code/tool execution. | Keep as optional remote executor adapter. |
 | Distributed execution | Ray bridge | Useful for Python distributed worker pools. | Ray should own cluster scheduling; AgentLedger owns run semantics. |
-| Deployment | Kubernetes worker recipe | Useful for pilots. | Recipe/Helm/examples first; full platform later only if needed. |
+| Deployment | Kubernetes worker recipe | Useful for pilots. | Recipe/Helm/examples first; keep deployment management outside runtime-core. |
 | Model providers/router | OpenAI, Anthropic, Gemini, Bedrock, Azure OpenAI, Ollama, LiteLLM-style bridge | Model calls affect evidence, cost, replay, fallback, and budget enforcement, but provider SDKs should not be runtime-core dependencies. | Wait for `ModelGateway`/`ModelRouter` contract before stabilizing provider packages. |
 
 ## Priority 3: Experimental Or Community Adapters
@@ -70,7 +70,7 @@ These should not block core parity or official release claims.
 | Workflow | Airflow / Prefect / Argo | They are batch/workflow systems; useful bridges, but AgentLedger should not become a general workflow engine. |
 | Eval | LangSmith / Braintrust / custom eval platforms | Eval remains a consumer of evidence/replay contracts, not runtime-core. |
 | Vector DB / RAG | Pinecone, Weaviate, Milvus, pgvector, etc. | Long-term memory/retrieval infra should be external; runtime stores refs/evidence, not knowledge retrieval logic. |
-| SaaS/multi-tenant platform | Any hosted platform adapter | Out of current project scope. AgentLedger is a framework/library/runtime, not SaaS. |
+| Application administration backend | User, organization, billing, identity, or control-plane adapters | Out of current project scope. AgentLedger is a framework/library/runtime reliability layer. |
 
 ## Cross-Language Policy
 

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/docs/ADOPTION.md

@@ -31,7 +31,7 @@ These can be opened as GitHub issues when the project is ready for public tracki
 | Build a cross-language 3-minute Tool Ledger demo | example | Shows the core value in a few minutes across Python, Go, TypeScript, and Rust. |
 | Add OpenAI Agents SDK approval/replay example | example | Connects AgentLedger to a major agent SDK boundary without claiming official endorsement. |
 | Add MCP tool governance example | example | Shows how MCP-style tools should pass through policy, approval, sandbox, idempotency, and evidence. |
-| Prototype AgentLedger Inspector | product | Makes run timelines, Tool Ledger, approvals, replay, and failures visible. |
+| Prototype AgentLedger Inspector | debug tool | Makes run timelines, Tool Ledger, approvals, replay, and failures visible. |
 | Add Temporal bridge example | integration | Clarifies Temporal owns workflow lifecycle while AgentLedger owns node-internal reliability. |
 | Add tool-injection risk scanner | security | Detects risky tool schemas, missing approval/sandbox, and runtime-boundary bypass patterns. |
 | Publish legal-agent case study | case study | Shows a realistic audit/evidence use case without private data. |

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/docs/COMPLETE_CORE_PARITY_CHECKLIST.md

@@ -17,7 +17,7 @@ Excluded or not applicable:
 
 - ecosystem-specific adapters whose upstream ecosystem does not exist or is not mature in a language, such as LangGraph outside Python
 - real cloud/service hardening that requires external infrastructure, unless a release explicitly claims it
-- SaaS, hosted multi-tenant platform, full eval platform, workflow engine, RAG system, or sandbox provider behavior
+- application administration backend, full eval system, workflow engine, RAG system, or sandbox provider behavior
 
 ## Status Legend
 
@@ -55,8 +55,8 @@ Excluded or not applicable:
 | CLI baseline | `--help`, `doctor`, `version`, `quickstart`, `conformance`, `contract validate`, `contract export` | `agentledger` CLI | `agentledger-go` | `agentledger-ts` | `agentledger-rust` | `scripts/check_complete_core_parity.py` | done |
 | Quickstart docs | Language quickstart and adapter quickstart | README + docs | `go/README.md` | `typescript/README.md` | `rust/README.md` | docs link check | done |
 | Examples | Runnable examples for core runtime and adapter API | Python examples | `go/examples/quickstart/main.go` | `typescript/examples/quickstart/quickstart.js` | `rust/examples/quickstart.rs` | `scripts/check_complete_core_parity.py` | done |
-| Package metadata | Installable package metadata in the current release train | PyPI metadata `1.2.4` | `go.mod` tag `go/v1.2.4` | npm package `1.2.4` | `Cargo.toml` `1.2.4` | `scripts/check_complete_core_parity.py` version check | done |
-| Package install smoke | Install/import/run from published or built package | PyPI `agentledger-runtime==1.2.4` release smoke after publish | `go/v1.2.4` clean external `go get` smoke after tag | npm `agentledger-runtime@1.2.4` release smoke after publish | crates.io `agentledger-runtime==1.2.4` release smoke after publish | publish logs + `scripts/check_complete_core_parity.py` dry-run gates | release-gated |
+| Package metadata | Installable package metadata in the current release train | PyPI metadata `1.3.0` | `go.mod` tag `go/v1.3.0` | npm package `1.3.0` | `Cargo.toml` `1.3.0` | `scripts/check_complete_core_parity.py` version check | done |
+| Package install smoke | Install/import/run from published or built package | PyPI `agentledger-runtime==1.3.0` release smoke after publish | `go/v1.3.0` clean external `go get` smoke after tag | npm `agentledger-runtime@1.3.0` release smoke after publish | crates.io `agentledger-runtime==1.3.0` release smoke after publish | publish logs + `scripts/check_complete_core_parity.py` dry-run gates | release-gated |
 | Release docs | Changelog, release checklist, status docs reflect exact parity boundary | docs | docs | docs | docs | docs link check | done |
 | Comparison docs | Honest overlap with LangChain/LangGraph/LangSmith/Langfuse/etc. | docs | docs | docs | docs | docs link check | done |
 
@@ -67,7 +67,7 @@ The strict core parity gate now covers the previously weak areas:
 1. CLI baseline is automatically checked for all four language CLIs.
 2. Go, TypeScript, and Rust have runnable quickstart example files.
 3. TypeScript and Rust package surfaces have package dry-run checks (`npm pack --dry-run`, `cargo package --allow-dirty --no-verify`) and post-publish install smokes are required for release.
-4. Package versions are checked across Python, TypeScript, and Rust; the current release train is aligned at `1.2.4`.
+4. Package versions are checked across Python, TypeScript, and Rust; the current release train is aligned at `1.3.0`.
 5. Go external module consumption is tag/release dependent; each release should repeat the clean external `go get` smoke after pushing the `go/vX.Y.Z` tag.
 6. Real service-backed hardening remains out of scope for core parity and stays documented as optional follow-up work.
 

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/docs/GETTING_STARTED.md

@@ -9,7 +9,7 @@ This is the shortest path from install to a working AgentLedger run. If you are
 | Language | Install / use | Quickstart | Examples | Package / command |
 |---|---|---|---|---|
 | Python | `pipx install agentledger-runtime` or `pip install agentledger-runtime` | `agentledger quickstart` | `../examples/README.md` | PyPI package `agentledger-runtime`, CLI `agentledger` |
-| Go | `go get github.com/yaogdu/AgentLedger/go@v1.2.4` inside a Go module | `cd go && go run ./examples/quickstart` from this repo | `../go/examples/README.md` | Go module `github.com/yaogdu/AgentLedger/go`, CLI package `.../go/cmd/agentledger-go` |
+| Go | `go get github.com/yaogdu/AgentLedger/go@v1.3.0` inside a Go module | `cd go && go run ./examples/quickstart` from this repo | `../go/examples/README.md` | Go module `github.com/yaogdu/AgentLedger/go`, CLI package `.../go/cmd/agentledger-go` |
 | TypeScript | `npm install agentledger-runtime` | `node typescript/examples/quickstart/quickstart.js` | `../typescript/examples/README.md` | npm package `agentledger-runtime`, CLI `agentledger-ts` |
 | Rust | crates.io package: `agentledger-runtime` | `cargo add agentledger-runtime` 或 `cd rust && cargo run --example quickstart` | `../rust/examples/README.md` | crate `agentledger-runtime`, binary `agentledger-rust` |
 
@@ -36,17 +36,17 @@ Use the library inside a Go module:
 
 ```bash
 go mod init your-module-name  # only if your project does not already have go.mod
-go get github.com/yaogdu/AgentLedger/go@v1.2.4
+go get github.com/yaogdu/AgentLedger/go@v1.3.0
 ```
 
 Install the optional CLI:
 
 ```bash
-go install github.com/yaogdu/AgentLedger/go/cmd/agentledger-go@v1.2.4
+go install github.com/yaogdu/AgentLedger/go/cmd/agentledger-go@v1.3.0
 agentledger-go --help
 ```
 
-Important: `go get` must run inside a Go module. `go install github.com/yaogdu/AgentLedger/go@v1.2.4` is not valid because that path is a library, not `package main`. Use `/cmd/agentledger-go` for the CLI.
+Important: `go get` must run inside a Go module. `go install github.com/yaogdu/AgentLedger/go@v1.3.0` is not valid because that path is a library, not `package main`. Use `/cmd/agentledger-go` for the CLI.
 
 ### TypeScript
 
@@ -98,6 +98,7 @@ The crate is published as `agentledger-runtime`; the library crate is imported a
 | MCP governance | `../examples/mcp_governance/README.md`; Go `../go/examples/mcp_governance`; TypeScript `../typescript/examples/mcp_governance`; Rust `../rust/examples/mcp_governance.rs` |
 | Sandbox command tool | `../examples/sandbox/command_tool.py` |
 | Media/stream refs | `../examples/media_stream/basic_media_stream.py` |
+| Read-only Inspector/custom viewer | `../examples/inspector/README.md` |
 | Go quickstart | `../go/examples/quickstart/main.go` |
 | TypeScript quickstart | `../typescript/examples/quickstart/quickstart.js` |
 | Rust quickstart | `../rust/examples/quickstart.rs` |

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/docs/HARNESS_STACK.md

@@ -232,7 +232,7 @@ AgentLedger should not become:
 - a full eval platform;
 - a RAG or vector memory platform;
 - a model marketplace or billing system;
-- a hosted sandbox platform;
-- a SaaS or multi-tenant app platform.
+- a sandbox infrastructure provider;
+- an application administration, identity, billing, or control-plane backend.
 
 The long-term direction is to make AgentLedger the reliability substrate that allows a harness stack to be assembled from mature components without losing durable execution, governance, evidence, replay, and side-effect safety.

{agentledger_runtime-1.2.4 → agentledger_runtime-1.3.0}/docs/IMPLEMENTATION_STATUS.md

@@ -6,7 +6,7 @@ This document tracks what is implemented in runtime-core, what remains planned f
 
 ## Current Baseline
 
-AgentLedger 1.2.4 is a stable runtime-core line with Python as the reference implementation and Go/TypeScript/Rust covered by shared runtime-core parity gates. The 1.2.x line adds adapter packaging boundaries across the supported language ecosystems and now includes the official MySQL storage adapter boundary plus a dependency-free Langfuse export adapter boundary while keeping selected preview/experimental concrete adapter paths explicit. It is suitable for:
+AgentLedger 1.3.0 is a stable runtime-core line with Python as the reference implementation and Go/TypeScript/Rust covered by shared runtime-core parity gates. The 1.3.0 line keeps the stable runtime-core contract and adds a language-neutral, read-only Inspector companion path for evidence and runtime metadata inspection. It is suitable for:
 
 - local use
 - runtime design review
@@ -15,7 +15,7 @@ AgentLedger 1.2.4 is a stable runtime-core line with Python as the reference imp
 - reliability semantics validation
 - production pilot preparation with explicit adapter boundaries
 
-Release-scope note: 1.2.4 is an adoption and example-focused release. It adds cross-language 3-minute side-effect safety demos, cross-language MCP governance examples, adoption documentation, public issue/discussion candidates, and legal-agent case-study templates without changing runtime-core semantics. MySQL remains the 1.2.2 storage adapter boundary and Langfuse remains the 1.2.3 observability adapter boundary; real-service production claims still require external validation.
+Release-scope note: 1.3.0 adds Inspector as a read-only evidence/runtime metadata consumer. It can read exported evidence bundles or connect to SQLite/Postgres/MySQL AgentLedger metadata with read-only credentials and can export a static HTML debug report. MySQL remains the 1.2.2 storage adapter boundary and Langfuse remains the 1.2.3 observability adapter boundary; real-service production claims still require external validation.
 
 The runtime-core contract is stable. Optional production adapters, external infrastructure hardening, and full eval systems remain outside the stable core boundary; non-Python runtime-core baselines are verified by the shared parity gates.
 
@@ -23,7 +23,7 @@ Scope rule: runtime-core should stay thin but indispensable. It should own only
 
 ## Current Completion Boundary
 
-For the current 1.2.x goal, "stable runtime-core" means the Python reference runtime is usable, documented, tested, release-gated, and contract-frozen, with Go/TypeScript/Rust covered by runtime-core parity gates. It also means first-party adapter boundaries are packaged or importable in each ecosystem where they fit. It does not mean every optional production adapter or external eval integration is production-hardened in every language.
+For the current 1.3.x goal, "stable runtime-core plus read-only evidence consumers" means the Python reference runtime is usable, documented, tested, release-gated, and contract-frozen, with Go/TypeScript/Rust covered by runtime-core parity gates. It also means first-party adapter boundaries are packaged or importable in each ecosystem where they fit, and the Inspector can consume exported evidence across languages. It does not mean every optional production adapter or external eval integration is production-hardened in every language.
 
 Included in this boundary:
 
@@ -58,6 +58,7 @@ Excluded from this boundary:
 | Adapter contracts | framework adapter base, LangGraph facade, MCP tool/context mapping, dependency-free method facades, first-party adapter package boundaries |
 | Sandbox boundary | fail-closed `none`, local executor, router, external executor contracts, Docker/bubblewrap command paths, Kubernetes dry-run/gated path |
 | Observability | trace JSONL export with media/stream spans, dependency-free OTLP JSON export, optional OTLP/JSON collector POST, evidence-linked audit records |
+| Inspector | `agentledger.inspector.v1` read model, `agentledger inspector run/evidence`, static HTML report, evidence-bundle input, read-only SQLite input, Postgres/MySQL read paths through existing adapter boundaries, optional `agentledger-inspector` companion package |
 | Reliability checks | failure injection suite, failure attribution report, conformance runners including media runtime conformance, runtime-boundary lint, scheduler facade, adversarial review, evidence regression for shell, HTTP, cloud, GitHub, and common model SDK bypasses with JSON rule-pack extension |
 | Media and stream contracts | `MediaArtifact`, `MediaMetadata`, `ArtifactLineage`, `StreamChunkRef`, `EventStreamCheckpoint`, `AgentContext.create_media_artifact(...)`, `AgentContext.create_stream_checkpoint(...)`, media/stream tool schema conventions, ToolGateway/Tool Ledger media tool example, evidence indexes, replay artifact validation/counts |
 | Release scaffolding | CI workflow, changelog, security policy, versioning policy, release checklist, contributor checks, bilingual documentation entrypoints, SVG architecture diagram, ResourceWarning-sensitive test gate, adapter certification checklist, adapter packaging docs/checks |
@@ -76,7 +77,7 @@ Excluded from this boundary:
 | MCP support | descriptor-to-ToolSpec mapping, dependency-free tool/context server fixtures, context read tool adapter, examples, `agentledger-mcp` package boundary | exact MCP SDK client/server integration |
 | Sandbox | contract, local/fail-closed modes, command-style Docker/bubblewrap, Kubernetes dry-run/gated execution, E2B/Firecracker slots, Docker sandbox package boundary | hardened isolation packages, secret injection policy, network policy recipes, resource limit validation |
 | Retention and backup checks | non-destructive retention plan with media/stream protected refs, compaction marker, and backup readiness check including media/stream nested refs | actual compaction/snapshot job that preserves replay guarantees |
-| Time travel and debug | JSON CLI timeline, state reconstruction, state diff view, `debug --json`, `--include-diffs`, `--include-states`, optional static HTML report export | richer report layout and artifact cross-links; no long-running web app in core |
+| Time travel and debug | JSON CLI timeline, state reconstruction, state diff view, `debug --json`, `--include-diffs`, `--include-states`, optional static HTML report export, Inspector static report | richer report layout and artifact cross-links; no long-running web app in core |
 
 ## Remaining Gaps And Preview Areas