PyPI - agentledger-runtime - Versions diffs - 1.3.1__tar.gz → 1.3.2__tar.gz - Mend

agentledger-runtime 1.3.1tar.gz → 1.3.2tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (377) hide show

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/CHANGELOG.md RENAMED Viewed

@@ -8,6 +8,18 @@ This project follows semantic versioning for the stable runtime-core contract. O
 No unreleased changes yet.
+## 1.3.2
+### Added
+- Added configurable Inspector redaction policies for JSON and static HTML reports.
+- Added `agentledger inspector run/evidence --redact-key ...` and `--redaction-policy policy.json` for local or internal debugging with sensitive fields masked.
+- Exported `InspectorRedactionPolicy` from both `agentledger-runtime` and the optional `agentledger-inspector` companion package for custom viewers.
+### Clarified
+- This is an Inspector-only patch release. It does not change the stable runtime-core contract or require Go, TypeScript, or Rust runtime-core changes.
 ## 1.3.1
 ### Fixed

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentledger-runtime
-Version: 1.3.1
+Version: 1.3.2
 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,7 +21,7 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: >=3.11
 Provides-Extra: all
-Requires-Dist: agentledger-inspector<2,>=1.3; extra == 'all'
+Requires-Dist: agentledger-inspector<2,>=1.3.2; 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'
@@ -33,7 +33,7 @@ Requires-Dist: agentledger-sandbox-docker<2,>=1.3; extra == 'all'
 Provides-Extra: docker
 Requires-Dist: agentledger-sandbox-docker<2,>=1.3; extra == 'docker'
 Provides-Extra: inspector
-Requires-Dist: agentledger-inspector<2,>=1.3; extra == 'inspector'
+Requires-Dist: agentledger-inspector<2,>=1.3.2; extra == 'inspector'
 Provides-Extra: langfuse
 Requires-Dist: agentledger-langfuse<2,>=1.3; extra == 'langfuse'
 Provides-Extra: langgraph
@@ -55,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.3.1 stable](https://img.shields.io/badge/Version-1.3.1--stable-111827)
+![Version 1.3.x stable](https://img.shields.io/badge/Version-1.3.x--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)
@@ -64,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.3.1` 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.x` 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.
@@ -333,7 +333,7 @@ AgentLedger is also not a new LLM SDK, not a workflow engine, not a general obse
 ## Current maturity
-AgentLedger 1.3.1 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.x is a stable runtime-core line with Python as the reference implementation and Go, TypeScript, and Rust covered by shared runtime-core parity gates. The current Python/Inspector patch is 1.3.2; Go, TypeScript, and Rust runtime-core package baselines remain 1.3.1 until their next runtime-core release. 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).

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/README.md RENAMED Viewed

@@ -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.3.1 stable](https://img.shields.io/badge/Version-1.3.1--stable-111827)
+![Version 1.3.x stable](https://img.shields.io/badge/Version-1.3.x--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.3.1` 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.x` 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.
@@ -281,7 +281,7 @@ AgentLedger is also not a new LLM SDK, not a workflow engine, not a general obse
 ## Current maturity
-AgentLedger 1.3.1 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.x is a stable runtime-core line with Python as the reference implementation and Go, TypeScript, and Rust covered by shared runtime-core parity gates. The current Python/Inspector patch is 1.3.2; Go, TypeScript, and Rust runtime-core package baselines remain 1.3.1 until their next runtime-core release. 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).

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/README.zh-CN.md RENAMED Viewed

@@ -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.3.1 stable](https://img.shields.io/badge/Version-1.3.1--stable-111827)
+![Version 1.3.x stable](https://img.shields.io/badge/Version-1.3.x--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.3.1` 是面向 Agent Harness stack 的 runtime reliability layer。它不负责让 Agent 更会“思考”，也不替代完整 Harness 生态；它负责让 Agent run 在 worker 崩溃、工具失败、prompt 变更和长任务恢复时，仍然具备持久化、可审计、可重放、可治理和可恢复能力。
+AgentLedger `1.3.x` 是面向 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。
@@ -282,7 +282,7 @@ AgentLedger 也不是新的 LLM SDK，不是 workflow engine，不是通用 obse
 ## 当前成熟度
-AgentLedger 1.3.1 是 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.x 是 stable runtime-core line，Python 是 reference implementation，Go、TypeScript、Rust 已由共享 runtime-core parity gate 覆盖。当前 Python/Inspector patch 是 1.3.2；Go、TypeScript、Rust runtime-core package baseline 仍是 1.3.1，直到它们进入下一次 runtime-core release。适合本地使用、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)。

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/ADAPTER_ROADMAP.md RENAMED Viewed

@@ -70,6 +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. |
+| Routing advisor / capability router | WisePick-style route decision services | Candidate direction only, not a committed adapter. It may be evaluated as a pre-execution suggestion and post-execution feedback loop, but should remain optional and must not turn AgentLedger core into a capability router or authorization layer. |
 | 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
@@ -113,3 +114,4 @@ Every official adapter must provide:
 7. Kubernetes sandbox/backend recipe, then optional execution adapter.
 8. Temporal/Ray/Kubernetes scheduler/backend bridges based on real user demand.
 9. Model provider/router adapters after the runtime `ModelGateway` contract is stable.
+10. Evaluate only, without implementation commitment, whether a Routing Advisor / Capability Router evidence boundary is useful for WisePick-style services. If later adopted, it should record externally supplied route suggestions, preserve replay by reusing stored routing evidence, and send feedback only after new real executions.

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/COMPLETE_CORE_PARITY_CHECKLIST.md RENAMED Viewed

@@ -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.3.1` | `go.mod` tag `go/v1.3.1` | npm package `1.3.1` | `Cargo.toml` `1.3.1` | `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.1` release smoke after publish | `go/v1.3.1` clean external `go get` smoke after tag | npm `agentledger-runtime@1.3.1` release smoke after publish | crates.io `agentledger-runtime==1.3.1` 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 1.3 release family | PyPI metadata `1.3.x` | `go.mod` tag `go/v1.3.1` for current baseline | npm package `1.3.1` for current baseline | `Cargo.toml` `1.3.1` for current baseline | `scripts/check_complete_core_parity.py` release-family check | done |
+| Package install smoke | Install/import/run from published or built package | PyPI `agentledger-runtime==1.3.2` release smoke after publish for current Inspector patch | `go/v1.3.1` clean external `go get` smoke after tag | npm `agentledger-runtime@1.3.1` release smoke after publish | crates.io `agentledger-runtime==1.3.1` 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.3.1`.
+4. Package release families are checked across Python, TypeScript, and Rust. The current core release family is `1.3`; Python may carry Inspector-only patch releases such as `1.3.2` without changing non-Python runtime-core baselines.
 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.3.1 → agentledger_runtime-1.3.2}/docs/IMPLEMENTATION_STATUS.md RENAMED Viewed

@@ -6,7 +6,7 @@ This document tracks what is implemented in runtime-core, what remains planned f
 ## Current Baseline
-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:
+AgentLedger 1.3.x 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 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.3.0 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.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.
+Release-scope note: 1.3.0 added 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. 1.3.2 adds configurable redaction for Inspector JSON/HTML output. 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.
@@ -58,7 +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 |
+| 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, configurable redaction policy, 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 |

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/INSPECTOR.md RENAMED Viewed

@@ -90,6 +90,38 @@ The `--blob-root` argument currently points at a local blob directory containing
 `--html` writes a static HTML report for local or internal debugging. The file is self-contained and can be opened without a server.
+## Redaction
+Inspector output can include sensitive operational evidence, especially when `--include-payloads` is used. `1.3.2` adds explicit redaction for JSON and HTML reports. Redaction is applied to the Inspector read model before rendering, so custom viewers that consume `InspectorReport.to_dict()` receive the same masked data as the default HTML renderer.
+Redact one or more keys directly:
+```bash
+agentledger inspector evidence ./evidence/<run_id> \
+  --include-payloads \
+  --redact-key password \
+  --redact-key api_token \
+  --html ./inspector.html
+```
+Use a policy file when the same rule should be reused:
+```json
+{
+  "keys": ["password", "api_token", "authorization"],
+  "replacement": "[redacted]"
+}
+```
+```bash
+agentledger inspector run <run_id> \
+  --root .agentledger \
+  --redaction-policy ./inspector-redaction.json \
+  --out ./inspector.json
+```
+The built-in policy matches exact key names case-insensitively and also redacts JSON strings that can be parsed as objects or arrays. It is a local debug safeguard, not a substitute for upstream secret management, database permissions, or evidence retention policy.
 ## Extension API
 Inspector is intentionally split into three pieces so users can extend it:
@@ -103,12 +135,13 @@ Inspector is intentionally split into three pieces so users can extend it:
 Example:
 ```python
-from agentledger import InspectorDataSource, InspectorReportBuilder
+from agentledger import InspectorDataSource, InspectorRedactionPolicy, InspectorReportBuilder
-report = InspectorDataSource().from_evidence_path("./evidence/run-1")
+policy = InspectorRedactionPolicy(keys=("password", "api_token"))
+report = InspectorDataSource().from_evidence_path("./evidence/run-1", redaction_policy=policy)
 data = report.to_dict()
-custom_report = InspectorReportBuilder().from_evidence_path("./evidence/run-1")
+custom_report = InspectorReportBuilder().from_evidence_path("./evidence/run-1", redaction_policy=policy)
 html = custom_report.to_html()
 ```
@@ -135,6 +168,7 @@ For secondary development, keep these contracts stable:
 - accept `InspectorReport.to_dict()` as the UI/API input
 - preserve `schema_version == "agentledger.inspector.v1"`
+- apply `InspectorRedactionPolicy` before exposing reports to users when payloads may contain secrets
 - implement `EvidenceStateStoreProtocol` / `EvidenceBlobStoreProtocol` for custom stores
 - keep write/control actions out of Inspector surfaces
 - use runtime APIs, not Inspector data sources, when an operator needs to approve, deny, cancel, or recover a run
@@ -143,6 +177,7 @@ For secondary development, keep these contracts stable:
 - Treat Inspector JSON and HTML as sensitive operational evidence.
 - Reports can include tool names, tool status, external ids, approval reasons, model metadata, artifact refs, payload summaries, and failure details.
+- Use `--redact-key` or `--redaction-policy` before sharing reports outside the local debugging boundary.
 - Use read-only DB credentials for Postgres/MySQL.
 - Do not build custom write actions on top of Inspector reports. Use runtime APIs for runtime control and keep debug viewers read-only.
 - Prefer evidence-bundle input when the blob store is remote or managed by another service.
@@ -160,6 +195,10 @@ Implemented in `1.3.0`:
 - extension API for custom data sources and renderers
 - optional `agentledger-inspector` companion package
+Implemented in `1.3.2`:
+- configurable JSON/HTML report redaction through `--redact-key`, `--redaction-policy`, and `InspectorRedactionPolicy`
 Not in this version:
 - long-running web server

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/LANGUAGE_QUICKSTART.md RENAMED Viewed

@@ -2,7 +2,7 @@
 [English](LANGUAGE_QUICKSTART.md) | [中文](zh/LANGUAGE_QUICKSTART.md)
-AgentLedger 1.3.1 has one Python reference runtime and native preview runtime-core baselines for Go, TypeScript, and Rust. The shared promise is semantic parity for runtime-core: durable runs, leases, Tool Ledger, evidence, replay, policy/approval/sandbox boundaries, cost/failure attribution, conformance, and official optional adapter contracts.
+AgentLedger 1.3.x has one Python reference runtime and native preview runtime-core baselines for Go, TypeScript, and Rust. The shared promise is semantic parity for runtime-core: durable runs, leases, Tool Ledger, evidence, replay, policy/approval/sandbox boundaries, cost/failure attribution, conformance, and official optional adapter contracts. Python may carry Inspector-only patch releases such as 1.3.2 while the non-Python runtime-core package baselines remain on the latest shared runtime-core tag.
 The non-Python packages are native runtime packages, not thin clients: each runs a native local runtime loop and reports the shared conformance checks.
@@ -267,7 +267,7 @@ python3.11 scripts/audit_python_parity.py > /tmp/agentledger-python-parity-audit
 python3.11 scripts/check_language_parity.py --json-report /tmp/agentledger-language-parity.json
 ```
-Expected for 1.3.1:
+Expected for 1.3.x:
 ```text
 gap_count: 0
@@ -277,5 +277,5 @@ AgentLedger language parity checks passed
 ## What Not To Assume
 - Go/TypeScript/Rust are package surfaces, even though runtime-core semantics are conformance-aligned.
-- Official adapters in 1.3.1 use injected clients and dry-run manifests; real cloud SDKs and live service hardening are optional follow-up gates.
+- Official adapters in 1.3.x use injected clients and dry-run manifests; real cloud SDKs and live service hardening are optional follow-up gates.
 - AgentLedger does not replace LangGraph, LangChain, LangSmith, Langfuse, Temporal, Ray, Kubernetes, vector DBs, or eval platforms. It provides the runtime safety/evidence layer those systems can integrate with.

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/ROADMAP.md RENAMED Viewed

@@ -22,6 +22,7 @@ Most capabilities should be evaluated in three layers: core contract, built-in m
 | FinOps / Cost Control | token/call/cost records, budget enforcement hooks, cost attribution reports | provider price catalogs, finance exports, alerts | invoice or payment system |
 | Inspector / Debug Viewer | stable read models, evidence export, static HTML debug export, redaction hooks, schema/version metadata | separate read-only local or internal inspector package | deployment management service, write/control plane in runtime-core |
 | Model Gateway / Router | model-call boundary, request/response archival, replay skipping, token/cost attribution, budget/fallback semantics | provider adapters, LiteLLM-style router adapters, policy packs, price catalogs | bundling every model SDK, becoming a full model gateway product, replacing provider SDKs |
+| Routing Advisor / Capability Router | candidate boundary only; no committed core feature. If future evaluation proves the boundary useful, runtime may record externally supplied route decisions as evidence and keep replay deterministic | possible WisePick-style capability router adapters or feedback clients, only if real usage justifies them | becoming a capability router, optimizing provider selection in core, or treating external routing decisions as authorization or idempotency keys |
 Execution backend positioning is documented in `EXECUTION_BACKENDS.md`: Temporal, Ray, and Kubernetes are backend adapters for generic distributed execution, while AgentLedger keeps agent-specific runtime invariants.
@@ -54,6 +55,7 @@ Recommended stack positioning:
 | Observability / eval UI | Langfuse, LangSmith, OpenTelemetry, custom dashboards | structured events, evidence bundles, trace/cost/failure export, correlation IDs |
 | Tool and context protocols | MCP, internal tool servers, provider SDK tools | ToolGateway, Tool Ledger, schema validation, approvals, sandbox, audit records |
 | Model providers / routers | OpenAI, Anthropic, Gemini, Bedrock, Ollama, LiteLLM | ModelGateway contract, archived model responses, budget/fallback/replay semantics |
+| Routing advisors / capability routers | WisePick-style decision services, custom capability routers | candidate integration boundary only; no planned implementation until real usage proves the need |
 | Storage / artifacts | SQLite, Postgres, MySQL, S3/MinIO, internal stores | StateStore/BlobStore contracts, migrations, conformance, evidence refs |
 ### Must Stay In Runtime-Core
@@ -101,6 +103,7 @@ LiteLLM and enterprise model gateways
 vector databases, RAG systems, long-term memory systems
 eval platforms and benchmark runners
 MCP tool servers and enterprise tool catalogs
+routing advisors and capability routers such as WisePick-style services; candidate only, if future evaluation proves the boundary useful
 ```
 AgentLedger should provide adapters, export formats, evidence bundles, trace correlation, and conformance checks for these layers.
@@ -552,6 +555,12 @@ Implemented in `1.3.0`:
 - static HTML export for shareable offline debugging
 - Tool Ledger, approval, policy decision, cost/failure, artifact, and timeline read model
+Implemented in `1.3.2`:
+- configurable Inspector redaction policy for JSON and static HTML output
+- CLI support for `--redact-key`, `--redaction-policy`, and `--redaction-replacement`
+- `InspectorRedactionPolicy` API for custom read-model consumers
 Follow-up work:
 - run/session list with status, timestamps, cost summary, and failure summary
@@ -560,7 +569,7 @@ Follow-up work:
 - Tool Ledger view with idempotency key, causal token, side-effect status, request/response refs, and unknown-state handling
 - artifact/evidence browser with payload refs, blob hashes, media refs, and stream checkpoint refs
 - cost and failure attribution panels
-- configurable redaction for secrets, credentials, prompts, payload fields, and large blobs
+- richer redaction presets for prompts, large blobs, and project-specific evidence fields
 - schema/version compatibility checks before reading a database
 Explicit non-goals:

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/zh/ADAPTER_ROADMAP.md RENAMED Viewed

@@ -70,6 +70,7 @@ Docker 优先官方化，是因为它适合作为 reference sandbox adapter，
 | Workflow | Airflow / Prefect / Argo | 它们是 batch/workflow 系统；可以桥接，但 AgentLedger 不应变成通用 workflow engine。 |
 | Eval | LangSmith / Braintrust / custom eval platforms | Eval 是 evidence/replay contract 的消费者，不属于 runtime-core。 |
 | Vector DB / RAG | Pinecone、Weaviate、Milvus、pgvector 等 | Long-term memory/retrieval infra 应外置；runtime 存 ref/evidence，不拥有知识检索逻辑。 |
+| Routing advisor / capability router | WisePick-style route decision service | 仅作为候选方向，不是已承诺 adapter。可以评估其作为执行前 suggestion 和执行后 feedback loop 的价值，但应保持 optional，不能把 AgentLedger core 变成 capability router 或授权层。 |
 | 应用管理后台 | 用户、组织、计费、身份或控制面 adapter | 当前项目范围外。AgentLedger 是 framework/library/runtime reliability layer。 |
 ## 跨语言策略
@@ -113,3 +114,4 @@ Python 是 reference implementation，但官方 adapter 在生态存在时应尽
 7. Kubernetes sandbox/backend recipe，然后再做 optional execution adapter。
 8. 根据真实用户需求做 Temporal/Ray/Kubernetes scheduler/backend bridge。
 9. `ModelGateway` contract 稳定后，再做 model provider/router adapters。
+10. 仅评估，不承诺实现：Routing Advisor / Capability Router evidence boundary 是否对 WisePick-style services 有价值。如果后续采纳，应记录外部传入的 route suggestion，replay 时复用已存 routing evidence，并且只在新的真实执行完成后发送 feedback。

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/zh/COMPLETE_CORE_PARITY_CHECKLIST.md RENAMED Viewed

@@ -26,7 +26,7 @@
 1. 四语言 CLI baseline 已有自动化检查，不再只依赖 conformance。
 2. Go、TypeScript、Rust 已有 runnable quickstart example files。
 3. TypeScript/Rust package surface 已有 `npm pack --dry-run` / `cargo package --allow-dirty --no-verify` 发布 dry-run；发布后仍需重复 clean install smoke。
-4. Python、TypeScript、Rust 的 package version 已自动检查；当前 release train 对齐到 `1.3.1`。
+4. Python、TypeScript、Rust 的 package release family 已自动检查；当前 core release family 是 `1.3`。Python 可以有 Inspector-only patch release，例如 `1.3.2`，不代表非 Python runtime-core baseline 必须同时变化。
 5. Go module 外部消费依赖 Git tag/release；每次 release 推送 `go/vX.Y.Z` tag 后都需要重复 clean external `go get` smoke。
 6. 真实服务 hardening 仍不属于 core parity，继续作为 optional follow-up 记录。

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/zh/IMPLEMENTATION_STATUS.md RENAMED Viewed

@@ -6,7 +6,7 @@
 ## 当前基线
-AgentLedger 1.3.0 是 stable runtime-core line，Python 是 reference implementation，Go/TypeScript/Rust 已通过共享 runtime-core parity gate 覆盖。1.3.0 保持 stable runtime-core contract，同时增加 language-neutral、read-only Inspector companion path，用于查看 evidence 和 runtime metadata。它适合：
+AgentLedger 1.3.x 是 stable runtime-core line，Python 是 reference implementation，Go/TypeScript/Rust 已通过共享 runtime-core parity gate 覆盖。1.3 line 保持 stable runtime-core contract，同时增加 language-neutral、read-only Inspector companion path，用于查看 evidence 和 runtime metadata。它适合：
 - 本地使用
 - runtime 设计评审
@@ -15,7 +15,7 @@ AgentLedger 1.3.0 是 stable runtime-core line，Python 是 reference implementa
 - reliability semantics 验证
 - 在明确 adapter 边界下做 production pilot 准备
-版本范围说明：1.3.0 增加 Inspector，定位是只读 evidence/runtime metadata consumer。它可以读取导出的 evidence bundle，也可以用只读凭证连接 SQLite/Postgres/MySQL AgentLedger metadata，并导出静态 HTML debug report。MySQL 仍是 1.2.2 的 storage adapter boundary，Langfuse 仍是 1.2.3 的 observability adapter boundary；真实服务生产级声明仍需要外部验证。
+版本范围说明：1.3.0 增加 Inspector，定位是只读 evidence/runtime metadata consumer。它可以读取导出的 evidence bundle，也可以用只读凭证连接 SQLite/Postgres/MySQL AgentLedger metadata，并导出静态 HTML debug report。1.3.2 增加 Inspector JSON/HTML 输出的可配置脱敏。MySQL 仍是 1.2.2 的 storage adapter boundary，Langfuse 仍是 1.2.3 的 observability adapter boundary；真实服务生产级声明仍需要外部验证。
 runtime-core contract 已稳定。optional production adapter、外部基础设施加固和完整 eval 系统都不属于 stable core 边界；非 Python runtime-core baseline 由共享 parity gate 验证。
@@ -58,7 +58,7 @@ runtime-core contract 已稳定。optional production adapter、外部基础设
 | Adapter contract | framework adapter base、LangGraph facade、MCP tool/context mapping、dependency-free method facades、第一方 adapter package boundaries |
 | Sandbox boundary | fail-closed `none`、local executor、router、external executor contract、Docker/bubblewrap command path、Kubernetes dry-run/gated path |
 | Observability | trace JSONL export、dependency-free OTLP JSON export、optional OTLP/JSON collector POST、evidence-linked audit record |
-| Inspector | `agentledger.inspector.v1` read model、`agentledger inspector run/evidence`、静态 HTML report、evidence-bundle input、read-only SQLite input、通过已有 adapter boundary 的 Postgres/MySQL read path、optional `agentledger-inspector` companion package |
+| Inspector | `agentledger.inspector.v1` read model、`agentledger inspector run/evidence`、静态 HTML report、evidence-bundle input、read-only SQLite input、通过已有 adapter boundary 的 Postgres/MySQL read path、可配置 redaction policy、optional `agentledger-inspector` companion package |
 | Reliability checks | failure injection suite、failure attribution report、conformance runner、runtime-boundary lint, scheduler facade, adversarial review, evidence regression、JSON rule-pack extension |
 | Media/stream contracts | `MediaArtifact`、`MediaMetadata`、`ArtifactLineage`、`StreamChunkRef`、`EventStreamCheckpoint`、AgentContext helpers、tool schema conventions、evidence/replay validation |
 | 开源发布骨架 | CI workflow、changelog、security policy、versioning policy、release checklist、contributor checks、中英文文档入口、SVG 架构图、adapter certification checklist、adapter packaging docs/checks |

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/zh/INSPECTOR.md RENAMED Viewed

@@ -90,6 +90,38 @@ Postgres/MySQL 建议使用只读数据库账号。AgentLedger 不为 Inspector
 `--html` 写出静态 HTML 报告，适合本地或内网排查问题；打开 HTML 不需要启动服务。
+## 脱敏
+Inspector 输出可能包含敏感运行证据，尤其是在使用 `--include-payloads` 时。`1.3.2` 增加了显式 redaction policy，作用于 JSON read model 和 HTML report。脱敏会在渲染前作用到 Inspector read model，所以二开的 viewer 如果消费 `InspectorReport.to_dict()`，拿到的也是同一份脱敏后的数据。
+直接指定一个或多个敏感 key：
+```bash
+agentledger inspector evidence ./evidence/<run_id> \
+  --include-payloads \
+  --redact-key password \
+  --redact-key api_token \
+  --html ./inspector.html
+```
+如果需要复用规则，可以使用 policy 文件：
+```json
+{
+  "keys": ["password", "api_token", "authorization"],
+  "replacement": "[redacted]"
+}
+```
+```bash
+agentledger inspector run <run_id> \
+  --root .agentledger \
+  --redaction-policy ./inspector-redaction.json \
+  --out ./inspector.json
+```
+内置 policy 按 key 精确匹配，不区分大小写；如果字段值是可以解析的 JSON 字符串，也会继续对其中的对象或数组做脱敏。它是本地 debug 的防护手段，不替代上游 secret 管理、数据库权限或 evidence retention policy。
 ## 二开接口
 Inspector 分成三层，方便用户二开：
@@ -103,12 +135,13 @@ Inspector 分成三层，方便用户二开：
 示例：
 ```python
-from agentledger import InspectorDataSource, InspectorReportBuilder
+from agentledger import InspectorDataSource, InspectorRedactionPolicy, InspectorReportBuilder
-report = InspectorDataSource().from_evidence_path("./evidence/run-1")
+policy = InspectorRedactionPolicy(keys=("password", "api_token"))
+report = InspectorDataSource().from_evidence_path("./evidence/run-1", redaction_policy=policy)
 data = report.to_dict()
-custom_report = InspectorReportBuilder().from_evidence_path("./evidence/run-1")
+custom_report = InspectorReportBuilder().from_evidence_path("./evidence/run-1", redaction_policy=policy)
 html = custom_report.to_html()
 ```
@@ -135,6 +168,7 @@ data = report.to_dict()
 - 将 `InspectorReport.to_dict()` 作为 UI/API 输入
 - 保留 `schema_version == "agentledger.inspector.v1"`
+- payload 可能包含 secret 时，先应用 `InspectorRedactionPolicy` 再对用户暴露 report
 - 为自定义 store 实现 `EvidenceStateStoreProtocol` / `EvidenceBlobStoreProtocol`
 - Inspector surface 保持只读，不加入写入/控制动作
 - 需要 approve、deny、cancel、recover run 时走 runtime API，不要走 Inspector data source
@@ -143,6 +177,7 @@ data = report.to_dict()
 - Inspector JSON 和 HTML 可能包含敏感运行证据，应按敏感运维数据处理。
 - 报告可能包含 tool name、tool status、external id、approval reason、model metadata、artifact ref、payload summary 和 failure detail。
+- 把 report 分享出本地 debug 边界前，建议使用 `--redact-key` 或 `--redaction-policy`。
 - Postgres/MySQL 使用只读数据库账号。
 - 不要基于 Inspector report 自行增加写入动作。runtime 控制应走 runtime API，debug viewer 保持只读。
 - 如果 blob store 是远程服务或由其它系统管理，优先使用 evidence bundle 输入。
@@ -160,6 +195,10 @@ data = report.to_dict()
 - 用于自定义 data source 和 renderer 的 extension API
 - optional `agentledger-inspector` companion package
+`1.3.2` 已实现：
+- 通过 `--redact-key`、`--redaction-policy` 和 `InspectorRedactionPolicy` 对 JSON/HTML report 做可配置脱敏
 本版本不包含：
 - 长运行 Web server

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/zh/LANGUAGE_QUICKSTART.md RENAMED Viewed

@@ -2,7 +2,7 @@
 [English](../LANGUAGE_QUICKSTART.md) | [中文](LANGUAGE_QUICKSTART.md)
-AgentLedger 1.3.1 包含 Python reference runtime，以及 Go、TypeScript、Rust 的 native preview runtime-core baseline。共享承诺是 runtime-core 语义对齐：durable run、lease、Tool Ledger、evidence、replay、policy/approval/sandbox boundary、cost/failure attribution、conformance 和 official optional adapter contract。
+AgentLedger 1.3.x 包含 Python reference runtime，以及 Go、TypeScript、Rust 的 native preview runtime-core baseline。共享承诺是 runtime-core 语义对齐：durable run、lease、Tool Ledger、evidence、replay、policy/approval/sandbox boundary、cost/failure attribution、conformance 和 official optional adapter contract。Python 可以有 Inspector-only patch release，例如 1.3.2；非 Python runtime-core package baseline 仍保持在最近一次共享 runtime-core tag。
 非 Python package 是 native runtime package，不是 thin client：它们都能运行本地 native runtime loop，并报告共享 conformance checks。
@@ -213,7 +213,7 @@ python3.11 scripts/audit_python_parity.py > /tmp/agentledger-python-parity-audit
 python3.11 scripts/check_language_parity.py --json-report /tmp/agentledger-language-parity.json
 ```
-1.3.1 期望：
+1.3.x 期望：
 ```text
 gap_count: 0
@@ -223,5 +223,5 @@ AgentLedger language parity checks passed
 ## 不要误解
 - Go/TypeScript/Rust 仍是 package surface，但 runtime-core 语义已 conformance-aligned。
-- 1.3.1 的 official adapter 使用 injected client 和 dry-run manifest；真实云 SDK 和 live service hardening 是后续 optional gate。
+- 1.3.x 的 official adapter 使用 injected client 和 dry-run manifest；真实云 SDK 和 live service hardening 是后续 optional gate。
 - AgentLedger 不替代 LangGraph、LangChain、LangSmith、Langfuse、Temporal、Ray、Kubernetes、vector DB 或 eval platform；它提供的是这些系统可以接入的 runtime safety/evidence layer。

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/docs/zh/ROADMAP.md RENAMED Viewed

@@ -22,6 +22,7 @@
 | FinOps / Cost Control | token/call/cost records、budget enforcement hooks、cost attribution reports | provider price catalogs、finance exports、alerts | 发票或支付系统 |
 | Inspector / Debug Viewer | stable read models、evidence export、static HTML debug export、redaction hooks、schema/version metadata | 独立 read-only 本地/内网 inspector package | deployment management service、runtime-core 中的写入/控制平面 |
 | Model Gateway / Router | model-call boundary、request/response archival、replay skipping、token/cost attribution、budget/fallback semantics | provider adapter、LiteLLM-style router adapter、policy packs、price catalogs | 打包所有 model SDK、变成完整 model gateway 产品、替代 provider SDK |
+| Routing Advisor / Capability Router | 仅作为候选边界评估；目前不承诺成为 core feature。如果未来验证这个边界有价值，runtime 可以把外部传入的 route decision 作为 evidence 记录，并保持 replay 确定性 | 可能的 WisePick-style capability router adapter 或 feedback client；只有真实需求证明有价值时才考虑 | 在 core 里做 capability router、provider selection optimization，或把外部 routing decision 当成授权/幂等键 |
 Execution backend 定位见 `EXECUTION_BACKENDS.md`：Temporal、Ray、Kubernetes 是通用分布式执行 backend adapters，AgentLedger 保留 agent-specific runtime invariants。
@@ -54,6 +55,7 @@ storage backends, and sandbox systems instead of replacing them.
 | Observability / eval UI | Langfuse、LangSmith、OpenTelemetry、custom dashboards | structured events、evidence bundles、trace/cost/failure export、correlation IDs |
 | Tool and context protocols | MCP、internal tool servers、provider SDK tools | ToolGateway、Tool Ledger、schema validation、approval、sandbox、audit records |
 | Model providers / routers | OpenAI、Anthropic、Gemini、Bedrock、Ollama、LiteLLM | ModelGateway contract、archived model responses、budget/fallback/replay semantics |
+| Routing advisors / capability routers | WisePick-style decision service、自定义 capability router | 仅作为候选集成边界；没有已规划实现，除非后续真实使用证明需要 |
 | Storage / artifacts | SQLite、Postgres、MySQL、S3/MinIO、internal stores | StateStore/BlobStore contracts、migration、conformance、evidence refs |
 ### 必须留在 runtime-core 的能力
@@ -101,6 +103,7 @@ LiteLLM and enterprise model gateways
 vector databases, RAG systems, long-term memory systems
 eval platforms and benchmark runners
 MCP tool servers and enterprise tool catalogs
+WisePick-style routing advisor / capability router；仅作为候选方向，前提是后续评估证明这个边界有价值
 ```
 AgentLedger 应该为这些层提供 adapter、export format、evidence bundle、trace correlation 和 conformance checks。
@@ -587,6 +590,14 @@ static HTML export，用于离线 debug 分享
 Tool Ledger、approval、policy decision、cost/failure、artifact、timeline read model
 ```
+`1.3.2` 已实现：
+```text
+JSON 和 static HTML 输出的可配置 Inspector redaction policy
+CLI 支持 --redact-key、--redaction-policy 和 --redaction-replacement
+给自定义 read-model consumer 使用的 InspectorRedactionPolicy API
+```
 后续工作：
 ```text
@@ -596,7 +607,7 @@ state diff 和 state-version view
 Tool Ledger view：idempotency key、causal token、side-effect status、request/response refs、unknown-state handling
 artifact/evidence browser：payload refs、blob hashes、media refs、stream checkpoint refs
 cost / failure attribution panels
-secret、credential、prompt、payload field、大 blob 的 redaction 配置
+prompt、大 blob 和项目自定义 evidence field 的更丰富 redaction preset
 读取数据库前做 schema/version compatibility check
 ```

{agentledger_runtime-1.3.1 → agentledger_runtime-1.3.2}/packages/agentledger-inspector/README.md RENAMED Viewed

@@ -21,6 +21,29 @@ Inspect an exported evidence bundle:
 agentledger inspector evidence ./evidence/<run_id> --html ./inspector.html
 ```
+Redact sensitive keys before writing JSON or HTML:
+```bash
+agentledger inspector evidence ./evidence/<run_id> \
+  --include-payloads \
+  --redact-key password \
+  --redact-key api_token \
+  --html ./inspector.html
+```
+Reusable redaction policy:
+```json
+{
+  "keys": ["password", "api_token", "authorization"],
+  "replacement": "[redacted]"
+}
+```
+```bash
+agentledger inspector run <run_id> --root .agentledger --redaction-policy ./inspector-redaction.json --out ./inspector.json
+```
 For Postgres or MySQL, use a read-only database credential and pass the local blob root that contains the referenced payload blobs. Inspector uses read-only store wrappers and does not run migrations or create tables:
 ```bash
@@ -33,14 +56,15 @@ The Inspector does not start a server, mutate runtime state, call tools, approve
 Extension API:
 ```python
-from agentledger_inspector import EvidenceBlobStoreProtocol, EvidenceStateStoreProtocol, InspectorDataSource, InspectorReportBuilder
+from agentledger_inspector import EvidenceBlobStoreProtocol, EvidenceStateStoreProtocol, InspectorDataSource, InspectorRedactionPolicy, InspectorReportBuilder
-report = InspectorDataSource().from_evidence_path("./evidence/run-1")
+policy = InspectorRedactionPolicy(keys=("password", "api_token"))
+report = InspectorDataSource().from_evidence_path("./evidence/run-1", redaction_policy=policy)
 data = report.to_dict()
 html = report.to_html()
 builder = InspectorReportBuilder()
-custom_report = builder.from_evidence_path("./evidence/run-1")
+custom_report = builder.from_evidence_path("./evidence/run-1", redaction_policy=policy)
 custom_source_report = InspectorDataSource().from_runtime_store(
     store=my_read_only_state_store,

agentledger-runtime 1.3.1__tar.gz → 1.3.2__tar.gz

agentledger-runtime 1.3.1tar.gz → 1.3.2tar.gz