agentledger-runtime 1.3.3__tar.gz → 1.3.5__tar.gz

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/CHANGELOG.md

@@ -8,6 +8,34 @@ This project follows semantic versioning for the stable runtime-core contract. O
 
 No unreleased changes yet.
 
+## 1.3.5 - 2026-06-07
+
+### Added
+
+- Added an Inspector chronological Event Stream view sorted by event timestamp, showing runtime run id, extracted agent run id, step id, event type, summary, and links back to detailed timeline records.
+- Added `agentledger inspector runs` and the `agentledger.inspector.runs.v1` read model for a read-only run index over SQLite/Postgres/MySQL runtime metadata.
+
+### Fixed
+
+- Improved Python static debug HTML layout so large JSON/details payloads and long ids do not expand tables or break the page width.
+- Reworked detailed Inspector, evidence, and time-travel tables so JSON opens in a full-width row below the record instead of a narrow right-side column.
+- Reworked the Inspector run-index HTML from a wide multi-column table into a compact paginated run list with status, timestamps, counters, Inspector links, and folded JSON details.
+
+### Clarified
+
+- This is a Python static debug HTML patch and is not published yet. It does not change the stable runtime-core contract or require Go, TypeScript, or Rust runtime-core changes.
+
+## 1.3.4
+
+### Fixed
+
+- Corrected the `agentledger-inspector` package module `__version__` so it matches published package metadata.
+- Added a release metadata regression check so the runtime package, Inspector companion package, and optional Inspector extra stay aligned in future patch releases.
+
+### Clarified
+
+- This is an Inspector/package metadata patch release. It does not change the stable runtime-core contract or require Go, TypeScript, or Rust runtime-core changes.
+
 ## 1.3.3
 
 ### Added

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentledger-runtime
-Version: 1.3.3
+Version: 1.3.5
 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.3; extra == 'all'
+Requires-Dist: agentledger-inspector<2,>=1.3.5; 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.3; extra == 'inspector'
+Requires-Dist: agentledger-inspector<2,>=1.3.5; extra == 'inspector'
 Provides-Extra: langfuse
 Requires-Dist: agentledger-langfuse<2,>=1.3; extra == 'langfuse'
 Provides-Extra: langgraph
@@ -90,6 +90,14 @@ Python remains the reference implementation, and Go, TypeScript, and Rust now ha
 | Use Go correctly | [go/README.md](go/README.md#install) |
 | Read the full documentation map | [docs/README.md](docs/README.md) |
 
+## Inspector Preview
+
+Inspector exports self-contained, read-only HTML for local or internal debugging. It can show a run index before opening a single run, then drill into chronological events, Tool Ledger rows, approvals, artifacts, and full-width JSON details.
+
+![AgentLedger Inspector run index](docs/assets/inspector/runs-index.png)
+
+![AgentLedger Inspector single run](docs/assets/inspector/single-run-timeline.png)
+
 ## At a glance
 
 | Question | Answer |
@@ -333,7 +341,7 @@ AgentLedger is also not a new LLM SDK, not a workflow engine, not a general obse
 
 ## Current maturity
 
-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.3; 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.
+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.5; 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.3 → agentledger_runtime-1.3.5}/README.md

@@ -38,6 +38,14 @@ Python remains the reference implementation, and Go, TypeScript, and Rust now ha
 | Use Go correctly | [go/README.md](go/README.md#install) |
 | Read the full documentation map | [docs/README.md](docs/README.md) |
 
+## Inspector Preview
+
+Inspector exports self-contained, read-only HTML for local or internal debugging. It can show a run index before opening a single run, then drill into chronological events, Tool Ledger rows, approvals, artifacts, and full-width JSON details.
+
+![AgentLedger Inspector run index](docs/assets/inspector/runs-index.png)
+
+![AgentLedger Inspector single run](docs/assets/inspector/single-run-timeline.png)
+
 ## At a glance
 
 | Question | Answer |
@@ -281,7 +289,7 @@ AgentLedger is also not a new LLM SDK, not a workflow engine, not a general obse
 
 ## Current maturity
 
-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.3; 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.
+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.5; 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.3 → agentledger_runtime-1.3.5}/README.zh-CN.md

@@ -38,6 +38,13 @@ Python 仍然是 reference implementation；Go、TypeScript、Rust 已有 native
 | 正确使用 Go | [go/README.md](go/README.md#install) |
 | 查看完整文档地图 | [docs/zh/README.md](docs/zh/README.md) |
 
+## Inspector 预览
+
+Inspector 会导出自包含、只读的 HTML，适合本地或内网排查问题。它可以先展示 run index，再进入单个 run 查看按时间排序的事件、Tool Ledger、approval、artifact 和全宽 JSON 详情。
+
+![AgentLedger Inspector run index](docs/assets/inspector/runs-index.png)
+
+![AgentLedger Inspector single run](docs/assets/inspector/single-run-timeline.png)
 
 ## 快速判断
 
@@ -282,7 +289,7 @@ AgentLedger 也不是新的 LLM SDK，不是 workflow engine，不是通用 obse
 
 ## 当前成熟度
 
-AgentLedger 1.3.x 是 stable runtime-core line，Python 是 reference implementation，Go、TypeScript、Rust 已由共享 runtime-core parity gate 覆盖。当前 Python/Inspector patch 是 1.3.3；Go、TypeScript、Rust runtime-core package baseline 仍是 1.3.1，直到它们进入下一次 runtime-core release。适合本地使用、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.5；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.3 → agentledger_runtime-1.3.5}/docs/COMPLETE_CORE_PARITY_CHECKLIST.md

@@ -56,7 +56,7 @@ Excluded or not applicable:
 | 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 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.3` 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 |
+| Package install smoke | Install/import/run from published or built package | PyPI `agentledger-runtime==1.3.5` 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 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.3` without changing non-Python runtime-core baselines.
+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.5` 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.3 → agentledger_runtime-1.3.5}/docs/IMPLEMENTATION_STATUS.md

@@ -15,7 +15,7 @@ AgentLedger 1.3.x 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 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. 1.3.3 adds static report navigation and read-model cross-links for timeline, tool, approval, policy, and artifact records. 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. 1.3.3 adds static report navigation and read-model cross-links for timeline, tool, approval, policy, and artifact records. 1.3.4 fixes Inspector package release metadata alignment. 1.3.5 improves Python static debug HTML layout, adds a chronological event stream, adds a read-only run index, paginates the run list, and moves table JSON/details payloads into full-width rows 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.
 
 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, section navigation, row anchors, cross-links between related records, evidence-bundle input, read-only SQLite input, Postgres/MySQL read paths through existing adapter boundaries, configurable redaction policy, optional `agentledger-inspector` companion package |
+| Inspector | `agentledger.inspector.v1` single-run read model, `agentledger.inspector.runs.v1` run-index read model, `agentledger inspector run/runs/evidence`, static HTML reports, section navigation, row anchors, cross-links between related records, 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.3 → agentledger_runtime-1.3.5}/docs/INSPECTOR.md

@@ -4,6 +4,14 @@ AgentLedger Inspector is a language-neutral, read-only debug and audit view for
 
 It is not a long-running service and not a runtime control plane. It does not approve requests, cancel runs, mutate Tool Ledger rows, call tools, or contact model providers.
 
+## Preview
+
+The default renderer is a static reference UI: a paginated run index plus a single-run view with chronological events and full-width JSON details.
+
+![AgentLedger Inspector run index](assets/inspector/runs-index.png)
+
+![AgentLedger Inspector single run](assets/inspector/single-run-timeline.png)
+
 ## Install
 
 Inspector is available through the core CLI and as an optional companion package:
@@ -22,7 +30,7 @@ Inspector is implemented once as a companion evidence consumer. Go, TypeScript,
 The boundary is:
 
 - language runtimes write AgentLedger metadata, Tool Ledger rows, events, artifacts, and evidence
-- Inspector reads that data through the stable read model `agentledger.inspector.v1`
+- Inspector reads that data through stable read models such as `agentledger.inspector.v1` and `agentledger.inspector.runs.v1`
 - users can build their own viewer, API endpoint, or internal debug tool on top of the read model
 
 This keeps Inspector outside runtime-core execution semantics while still making all language implementations debuggable through one tool.
@@ -35,6 +43,7 @@ Inspector supports two read paths.
 |---|---|---|
 | Exported evidence | `agentledger inspector evidence <path>` | Portable artifact from any language implementation or CI job. |
 | Local SQLite runtime | `agentledger inspector run <run_id> --root .agentledger` | Local development and small deployments. |
+| Run index | `agentledger inspector runs --root .agentledger` | Read-only list of recent runs before opening one run. |
 | Direct SQLite path | `agentledger inspector run <run_id> --backend sqlite --db state.db --blob-root blobs` | Custom runtime directory layouts. |
 | Postgres metadata | `agentledger inspector run <run_id> --backend postgres --dsn ... --schema ... --blob-root ...` | Server-side StateStore deployments. |
 | MySQL metadata | `agentledger inspector run <run_id> --backend mysql --dsn ... --database ... --blob-root ...` | MySQL-backed StateStore deployments. |
@@ -56,6 +65,8 @@ This path reads AgentLedger runtime metadata directly. SQLite is opened in read-
 ```bash
 agentledger inspector run <run_id> --root .agentledger --html ./inspector.html
 agentledger inspector run <run_id> --backend sqlite --db .agentledger/state.db --blob-root .agentledger/blobs --out ./inspector.json
+agentledger inspector runs --root .agentledger --html ./runs.html
+agentledger inspector runs --root .agentledger --out ./runs.json
 ```
 
 Postgres and MySQL are also supported through the existing StateStore adapter boundaries. Inspector uses read-only store wrappers for these paths and does not run migrations or create tables:
@@ -63,12 +74,16 @@ Postgres and MySQL are also supported through the existing StateStore adapter bo
 ```bash
 agentledger inspector run <run_id> --backend postgres --dsn "$AGENTLEDGER_POSTGRES_DSN" --schema agentledger --blob-root .agentledger/blobs --html ./inspector.html
 agentledger inspector run <run_id> --backend mysql --dsn "$AGENTLEDGER_MYSQL_DSN" --database agentledger --blob-root .agentledger/blobs --html ./inspector.html
+agentledger inspector runs --backend postgres --dsn "$AGENTLEDGER_POSTGRES_DSN" --schema agentledger --html ./runs.html
+agentledger inspector runs --backend mysql --dsn "$AGENTLEDGER_MYSQL_DSN" --database agentledger --html ./runs.html
 ```
 
 Use database credentials with read-only permissions. AgentLedger does not add an Inspector-specific permission system; database grants, filesystem ACLs, and deployment policy remain the enforcement layer. The Inspector code path exposes no runtime write/control actions, but Postgres/MySQL client libraries cannot replace database-side read-only grants.
 
 The `--blob-root` argument currently points at a local blob directory containing the payload blobs referenced by the runtime metadata. If payload blobs live in S3/MinIO or another managed object store, export an evidence bundle first or provide a custom `EvidenceBlobStoreProtocol` implementation through the extension API.
 
+For `agentledger inspector runs`, `--blob-root` is optional. When present, Inspector may use it to extract an application-level `agent_run_id` from event payloads. When absent, the run index still works but may show `agent_run_id` as `-`.
+
 ## Output
 
 `--out` writes the stable JSON read model:
@@ -78,6 +93,8 @@ The `--blob-root` argument currently points at a local blob directory containing
   "schema_version": "agentledger.inspector.v1",
   "run": {},
   "summary": {},
+  "agent_run_id": null,
+  "event_stream": [],
   "timeline": [],
   "tool_ledger": [],
   "approvals": [],
@@ -90,6 +107,32 @@ 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.
 
+`agentledger inspector runs --out` writes a run-index read model:
+
+```json
+{
+  "schema_version": "agentledger.inspector.runs.v1",
+  "summary": {},
+  "runs": []
+}
+```
+
+`agentledger inspector runs --html` writes a static read-only run list. The default renderer uses a compact paginated vertical list with status, timestamps, counters, optional Inspector links, and folded JSON details instead of a wide table. Use `--run-link-template "/runs/{run_id}/inspector.html"` when an application or internal tool already exposes single-run Inspector pages and should link from the index to those pages.
+
+## Event Stream
+
+`1.3.5` adds an Event Stream section to the Inspector read model and static HTML report. It is a chronological view of the same run events, sorted by event time and tied together by:
+
+- `runtime_run_id`: the AgentLedger runtime run id
+- `agent_run_id`: an agent/application run id when one is present in event metadata or payloads
+- `seq`: the original AgentLedger event sequence
+- `type`, `step_id`, and `summary`: compact event context
+- `related_links`: local links back to detailed timeline, step, tool, approval, policy, or artifact records
+
+This view is intended for debugging a single run from top to bottom. It does not replace the detailed section views; it gives operators a time-ordered path through them.
+
+Detailed tables keep compact record columns on the first row and render the folded JSON payload in a full-width row below each record. This keeps long payloads readable without forcing a narrow right-side details column.
+
 ## Navigation And Cross-links
 
 `1.3.3` adds stable row anchors and related links to the Inspector read model. Timeline events, steps, Tool Ledger rows, approval requests, policy decisions, and artifacts may include:
@@ -220,11 +263,19 @@ Implemented in `1.3.3`:
 - stable read-model anchors for timeline, step, Tool Ledger, approval, policy, and artifact rows
 - static HTML section navigation and internal cross-links between related runtime records
 
+Implemented in `1.3.5`:
+
+- chronological Event Stream in JSON and static HTML reports
+- read-only run index through `agentledger inspector runs`
+- `agentledger.inspector.runs.v1` run-index read model for custom viewers
+- runtime run id and extracted agent run id in event/timeline read-model rows
+- safer static HTML layout for long ids, full-width JSON details, and paginated run lists
+
 Not in this version:
 
 - long-running web server
+- login, permission, user, or organization management for Inspector surfaces
 - write/control-plane actions
-- user/organization management
 - permission, identity, billing, or administration backend
 - full LangSmith/Langfuse replacement
 - live remote blob adapters inside the Inspector package

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/docs/LANGUAGE_QUICKSTART.md

@@ -2,7 +2,7 @@
 
 [English](LANGUAGE_QUICKSTART.md) | [中文](zh/LANGUAGE_QUICKSTART.md)
 
-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.3 while the non-Python runtime-core package baselines remain on the latest shared runtime-core tag.
+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.5 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.
 

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/docs/ROADMAP.md

@@ -564,9 +564,16 @@ Implemented in `1.3.3`:
 - stable read-model anchors for timeline, step, Tool Ledger, approval, policy, and artifact rows
 - static HTML section navigation and internal cross-links between related runtime records
 
+Implemented in `1.3.5`:
+
+- chronological Event Stream in JSON and static HTML reports
+- read-only run index with status, timestamps, cost summary, failure summary, and optional single-run links
+- runtime run id and extracted agent run id in event/timeline rows
+- paginated run-list static HTML and full-width JSON/details rows for Inspector, evidence, and time-travel tables
+
 Follow-up work:
 
-- run/session list with status, timestamps, cost summary, and failure summary
+- richer filtering, search, pagination, and saved views for the read-only run index
 - run timeline for steps, events, model calls, tool calls, approvals, artifacts, and checkpoints
 - state diff and state-version view
 - Tool Ledger view with idempotency key, causal token, side-effect status, request/response refs, and unknown-state handling

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/docs/zh/COMPLETE_CORE_PARITY_CHECKLIST.md

@@ -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 release family 已自动检查；当前 core release family 是 `1.3`。Python 可以有 Inspector-only patch release，例如 `1.3.3`，不代表非 Python runtime-core baseline 必须同时变化。
+4. Python、TypeScript、Rust 的 package release family 已自动检查；当前 core release family 是 `1.3`。Python 可以有 Inspector-only patch release，例如 `1.3.5`，不代表非 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.3 → agentledger_runtime-1.3.5}/docs/zh/IMPLEMENTATION_STATUS.md

@@ -15,7 +15,7 @@ AgentLedger 1.3.x 是 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。1.3.2 增加 Inspector JSON/HTML 输出的可配置脱敏。1.3.3 增加 static report navigation，以及 timeline、tool、approval、policy、artifact record 的 read-model cross-links。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 输出的可配置脱敏。1.3.3 增加 static report navigation，以及 timeline、tool、approval、policy、artifact record 的 read-model cross-links。1.3.4 修复 Inspector package release metadata 对齐。1.3.5 改善 Python static debug HTML 布局，增加 chronological event stream 和只读 run index，为 run list 增加分页，并把表格中的 JSON/details payload 移到全宽行中，不改变 runtime-core 语义。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、section navigation、row anchor、相关 record 之间的 cross-link、evidence-bundle input、read-only SQLite input、通过已有 adapter boundary 的 Postgres/MySQL read path、可配置 redaction policy、optional `agentledger-inspector` companion package |
+| Inspector | `agentledger.inspector.v1` 单 run read model、`agentledger.inspector.runs.v1` run-index read model、`agentledger inspector run/runs/evidence`、静态 HTML report、section navigation、row anchor、相关 record 之间的 cross-link、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.3 → agentledger_runtime-1.3.5}/docs/zh/INSPECTOR.md

@@ -4,6 +4,14 @@ AgentLedger Inspector 是语言无关、只读的 run 调试和审计视图。
 
 它不是长运行服务，也不是 runtime 控制平面。它不会 approve request、cancel run、修改 Tool Ledger、调用工具或访问 model provider。
 
+## 预览
+
+默认 renderer 是静态参考 UI：分页 run index，以及带 chronological event 和全宽 JSON details 的单 run 视图。
+
+![AgentLedger Inspector run index](../assets/inspector/runs-index.png)
+
+![AgentLedger Inspector single run](../assets/inspector/single-run-timeline.png)
+
 ## 安装
 
 Inspector 可以通过 core CLI 使用，也提供 optional companion package：
@@ -22,7 +30,7 @@ Inspector 只实现一套，作为 companion evidence consumer 存在。Go、Typ
 边界是：
 
 - 各语言 runtime 写入 AgentLedger metadata、Tool Ledger、event、artifact 和 evidence
-- Inspector 通过稳定 read model `agentledger.inspector.v1` 读取这些数据
+- Inspector 通过 `agentledger.inspector.v1`、`agentledger.inspector.runs.v1` 等稳定 read model 读取这些数据
 - 用户可以基于 read model 二开自己的 viewer、API endpoint 或内部 debug 工具
 
 这样 Inspector 不进入 runtime-core 执行语义，但四种语言实现都能通过同一个工具排查问题。
@@ -35,6 +43,7 @@ Inspector 支持两条只读路径。
 |---|---|---|
 | 导出的 evidence | `agentledger inspector evidence <path>` | 任意语言实现或 CI job 导出的可移植证据包。 |
 | 本地 SQLite runtime | `agentledger inspector run <run_id> --root .agentledger` | 本地开发和小规模部署。 |
+| Run index | `agentledger inspector runs --root .agentledger` | 打开单个 run 前，先只读查看最近 run 列表。 |
 | 直接 SQLite 路径 | `agentledger inspector run <run_id> --backend sqlite --db state.db --blob-root blobs` | 自定义 runtime 目录结构。 |
 | Postgres metadata | `agentledger inspector run <run_id> --backend postgres --dsn ... --schema ... --blob-root ...` | 使用 server-side StateStore 的部署。 |
 | MySQL metadata | `agentledger inspector run <run_id> --backend mysql --dsn ... --database ... --blob-root ...` | 使用 MySQL StateStore 的部署。 |
@@ -56,6 +65,8 @@ agentledger inspector evidence ./bundle.json --out ./inspector.json
 ```bash
 agentledger inspector run <run_id> --root .agentledger --html ./inspector.html
 agentledger inspector run <run_id> --backend sqlite --db .agentledger/state.db --blob-root .agentledger/blobs --out ./inspector.json
+agentledger inspector runs --root .agentledger --html ./runs.html
+agentledger inspector runs --root .agentledger --out ./runs.json
 ```
 
 Postgres 和 MySQL 通过已有 StateStore adapter boundary 读取。Inspector 在这些路径上使用 read-only store wrapper，不会运行 migration，也不会创建表：
@@ -63,12 +74,16 @@ Postgres 和 MySQL 通过已有 StateStore adapter boundary 读取。Inspector
 ```bash
 agentledger inspector run <run_id> --backend postgres --dsn "$AGENTLEDGER_POSTGRES_DSN" --schema agentledger --blob-root .agentledger/blobs --html ./inspector.html
 agentledger inspector run <run_id> --backend mysql --dsn "$AGENTLEDGER_MYSQL_DSN" --database agentledger --blob-root .agentledger/blobs --html ./inspector.html
+agentledger inspector runs --backend postgres --dsn "$AGENTLEDGER_POSTGRES_DSN" --schema agentledger --html ./runs.html
+agentledger inspector runs --backend mysql --dsn "$AGENTLEDGER_MYSQL_DSN" --database agentledger --html ./runs.html
 ```
 
 Postgres/MySQL 建议使用只读数据库账号。AgentLedger 不为 Inspector 单独做一套权限系统；数据库 grant、文件系统 ACL 和部署策略才是权限执行层。Inspector 代码路径不暴露 runtime 写入/控制动作，但 Postgres/MySQL 客户端无法替代数据库侧的只读授权。
 
 `--blob-root` 当前指向本地 blob 目录，用于读取 runtime metadata 中引用的 payload blob。如果 payload blob 在 S3/MinIO 或其它托管对象存储中，优先先导出 evidence bundle，或者通过 extension API 提供自定义 `EvidenceBlobStoreProtocol` 实现。
 
+对 `agentledger inspector runs` 来说，`--blob-root` 是可选项。提供后，Inspector 会尽量从 event payload 中提取业务侧 `agent_run_id`；不提供时，run index 仍可用，只是 `agent_run_id` 可能显示为 `-`。
+
 ## 输出
 
 `--out` 写出稳定 JSON read model：
@@ -78,6 +93,8 @@ Postgres/MySQL 建议使用只读数据库账号。AgentLedger 不为 Inspector
   "schema_version": "agentledger.inspector.v1",
   "run": {},
   "summary": {},
+  "agent_run_id": null,
+  "event_stream": [],
   "timeline": [],
   "tool_ledger": [],
   "approvals": [],
@@ -90,6 +107,32 @@ Postgres/MySQL 建议使用只读数据库账号。AgentLedger 不为 Inspector
 
 `--html` 写出静态 HTML 报告，适合本地或内网排查问题；打开 HTML 不需要启动服务。
 
+`agentledger inspector runs --out` 会写出 run-index read model：
+
+```json
+{
+  "schema_version": "agentledger.inspector.runs.v1",
+  "summary": {},
+  "runs": []
+}
+```
+
+`agentledger inspector runs --html` 会写出静态只读 run list。默认 renderer 使用紧凑的分页纵向列表展示 status、时间、计数、可选 Inspector 链接和折叠 JSON 详情，不再用很宽的多列表格。如果你的应用或内部工具已经暴露单 run Inspector 页面，可以用 `--run-link-template "/runs/{run_id}/inspector.html"` 把列表页链接到单 run 页面。
+
+## Event Stream
+
+`1.3.5` 在 Inspector read model 和静态 HTML report 中增加 Event Stream。它复用同一批 run event，但按事件时间排序，并用下面这些字段把执行过程串起来：
+
+- `runtime_run_id`：AgentLedger runtime run id
+- `agent_run_id`：如果 event metadata 或 payload 中存在 agent/application run id，则提取出来
+- `seq`：原始 AgentLedger event sequence
+- `type`、`step_id`、`summary`：压缩后的事件上下文
+- `related_links`：跳回 timeline、step、tool、approval、policy、artifact 等详细记录的本地链接
+
+这个视图用于从头到尾排查单个 run。它不替代分块详情页，而是给 operator 一条按时间查看详情的路径。
+
+详细表格会把紧凑记录列放在第一行，折叠 JSON payload 放到当前记录下面的全宽行中。这样长 payload 可读性更好，也不会被挤在右侧很窄的 details 列里。
+
 ## 导航和交叉链接
 
 `1.3.3` 在 Inspector read model 中增加了稳定的行级 anchor 和 related links。Timeline event、step、Tool Ledger row、approval request、policy decision 和 artifact 可能包含：
@@ -220,11 +263,19 @@ data = report.to_dict()
 - timeline、step、Tool Ledger、approval、policy 和 artifact row 的稳定 read-model anchor
 - static HTML section navigation，以及相关 runtime record 之间的内部交叉链接
 
+`1.3.5` 已实现：
+
+- JSON 和 static HTML report 中的 chronological Event Stream
+- 通过 `agentledger inspector runs` 提供只读 run index
+- 面向自定义 viewer 的 `agentledger.inspector.runs.v1` run-index read model
+- event/timeline read-model row 中的 runtime run id 和提取出的 agent run id
+- 对长 id、全宽 JSON details 和分页 run list 更稳的 static HTML 布局
+
 本版本不包含：
 
 - 长运行 Web server
+- Inspector surface 的登录、权限、用户或组织管理
 - 写入/控制平面动作
-- 用户/组织管理
 - permission、identity、billing 或 administration backend
 - 完整 LangSmith/Langfuse 替代品
 - Inspector package 内置 live remote blob adapter

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/docs/zh/LANGUAGE_QUICKSTART.md

@@ -2,7 +2,7 @@
 
 [English](../LANGUAGE_QUICKSTART.md) | [中文](LANGUAGE_QUICKSTART.md)
 
-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.3；非 Python runtime-core package baseline 仍保持在最近一次共享 runtime-core tag。
+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.5；非 Python runtime-core package baseline 仍保持在最近一次共享 runtime-core tag。
 
 非 Python package 是 native runtime package，不是 thin client：它们都能运行本地 native runtime loop，并报告共享 conformance checks。
 

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/docs/zh/ROADMAP.md

@@ -603,10 +603,19 @@ timeline、step、Tool Ledger、approval、policy、artifact row 的稳定 read-
 相关 runtime record 之间的 static HTML section navigation 和内部 cross-link
 ```
 
+`1.3.5` 已实现：
+
+```text
+JSON 和 static HTML report 中的 chronological Event Stream
+只读 run index：status、timestamp、cost summary、failure summary、可选单 run 链接
+event/timeline row 中的 runtime run id 和提取出的 agent run id
+run list static HTML 分页，以及 Inspector、evidence、time-travel 表格中的全宽 JSON/details 行
+```
+
 后续工作：
 
 ```text
-run/session list：status、timestamp、cost summary、failure summary
+只读 run index 的 filtering、search、pagination、saved views
 单个 run timeline：step、event、model call、tool call、approval、artifact、checkpoint
 state diff 和 state-version view
 Tool Ledger view：idempotency key、causal token、side-effect status、request/response refs、unknown-state handling

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/packages/agentledger-inspector/README.md

@@ -15,6 +15,13 @@ Inspect a local runtime database:
 agentledger inspector run <run_id> --root .agentledger --html ./inspector.html
 ```
 
+Inspect recent runs from a local runtime database:
+
+```bash
+agentledger inspector runs --root .agentledger --html ./runs.html
+agentledger inspector runs --root .agentledger --out ./runs.json
+```
+
 Inspect an exported evidence bundle:
 
 ```bash
@@ -53,7 +60,7 @@ agentledger inspector run <run_id> --backend mysql --dsn "$AGENTLEDGER_MYSQL_DSN
 
 The Inspector does not start a server, mutate runtime state, call tools, approve requests, or contact model providers. It builds a language-neutral read model from AgentLedger runtime metadata or exported evidence bundles. AgentLedger does not add a separate permission layer for Inspector; use database grants, filesystem ACLs, and deployment policy.
 
-Static HTML reports include local section navigation and internal cross-links between related timeline events, steps, Tool Ledger rows, approvals, policy decisions, and artifacts. Custom viewers can reuse the same `anchor`, `related_refs`, and `related_links` fields from `InspectorReport.to_dict()`.
+Static HTML reports include local section navigation, a chronological Event Stream, a read-only run index, and internal cross-links between related timeline events, steps, Tool Ledger rows, approvals, policy decisions, and artifacts. Custom viewers can reuse the same `event_stream`, `anchor`, `related_refs`, `related_links`, and run-index fields from `InspectorReport.to_dict()` / `InspectorRunIndex.to_dict()`.
 
 Extension API:
 
@@ -73,9 +80,15 @@ custom_source_report = InspectorDataSource().from_runtime_store(
     blobs=my_read_only_blob_store,
     run_id="run_123",
 )
+
+run_index = InspectorDataSource().runs_from_runtime_store(
+    store=my_read_only_state_store,
+    blobs=my_read_only_blob_store,
+    run_link_template="/runs/{run_id}/inspector.html",
+)
 ```
 
-The default HTML renderer is a reference renderer. Users can build their own UI by consuming `InspectorReport.to_dict()` and preserving `schema_version == agentledger.inspector.v1`.
+The default HTML renderer is a reference renderer. Users can build their own UI by consuming `InspectorReport.to_dict()` / `InspectorRunIndex.to_dict()` and preserving `schema_version == agentledger.inspector.v1` or `agentledger.inspector.runs.v1`. The package does not include a long-running web server, login system, permission system, or runtime control plane.
 
 `EvidenceStateStoreProtocol` and `EvidenceBlobStoreProtocol` describe the minimal read API for custom database/blob backends.
 

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/packages/agentledger-inspector/pyproject.toml

@@ -4,14 +4,14 @@ build-backend = "hatchling.build"
 
 [project]
 name = "agentledger-inspector"
-version = "1.3.3"
+version = "1.3.5"
 description = "Read-only Inspector and evidence viewer package for AgentLedger"
 readme = "README.md"
 requires-python = ">=3.11"
 license = {text = "Apache-2.0"}
 authors = [{name = "AgentLedger Contributors"}]
 keywords = ["agents", "runtime", "inspector", "debug", "evidence"]
-dependencies = ["agentledger-runtime>=1.3.3,<2"]
+dependencies = ["agentledger-runtime>=1.3.5,<2"]
 
 [project.urls]
 Homepage = "https://github.com/yaogdu/AgentLedger"

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/packages/agentledger-inspector/src/agentledger_inspector/__init__.py

@@ -1,18 +1,20 @@
 """Read-only Inspector package for AgentLedger."""
 
-__version__ = "1.3.2"
+__version__ = "1.3.5"
 
-from agentledger.inspector import INSPECTOR_SCHEMA_VERSION, InspectorDataSource, InspectorRedactionPolicy, InspectorReport, InspectorReportBuilder, ReadOnlyLocalBlobStore, ReadOnlyMySQLStore, ReadOnlyPostgresStore, ReadOnlySQLiteStore
+from agentledger.inspector import INSPECTOR_RUN_INDEX_SCHEMA_VERSION, INSPECTOR_SCHEMA_VERSION, InspectorDataSource, InspectorRedactionPolicy, InspectorReport, InspectorReportBuilder, InspectorRunIndex, ReadOnlyLocalBlobStore, ReadOnlyMySQLStore, ReadOnlyPostgresStore, ReadOnlySQLiteStore
 from agentledger.protocol import EvidenceBlobStoreProtocol, EvidenceStateStoreProtocol
 
 __all__ = [
     "INSPECTOR_SCHEMA_VERSION",
+    "INSPECTOR_RUN_INDEX_SCHEMA_VERSION",
     "EvidenceBlobStoreProtocol",
     "EvidenceStateStoreProtocol",
     "InspectorDataSource",
     "InspectorRedactionPolicy",
     "InspectorReport",
     "InspectorReportBuilder",
+    "InspectorRunIndex",
     "ReadOnlyLocalBlobStore",
     "ReadOnlyMySQLStore",
     "ReadOnlyPostgresStore",

{agentledger_runtime-1.3.3 → agentledger_runtime-1.3.5}/packages/agentledger-inspector/tests/test_import.py

@@ -3,13 +3,15 @@ import unittest
 
 class InspectorPackageImportTests(unittest.TestCase):
     def test_imports(self) -> None:
-        from agentledger_inspector import INSPECTOR_SCHEMA_VERSION, EvidenceStateStoreProtocol, InspectorDataSource, InspectorRedactionPolicy, InspectorReportBuilder, ReadOnlyPostgresStore
+        from agentledger_inspector import INSPECTOR_RUN_INDEX_SCHEMA_VERSION, INSPECTOR_SCHEMA_VERSION, EvidenceStateStoreProtocol, InspectorDataSource, InspectorRedactionPolicy, InspectorReportBuilder, InspectorRunIndex, ReadOnlyPostgresStore
 
         self.assertEqual(INSPECTOR_SCHEMA_VERSION, "agentledger.inspector.v1")
+        self.assertEqual(INSPECTOR_RUN_INDEX_SCHEMA_VERSION, "agentledger.inspector.runs.v1")
         self.assertEqual(EvidenceStateStoreProtocol.__name__, "EvidenceStateStoreProtocol")
         self.assertEqual(InspectorDataSource.__name__, "InspectorDataSource")
         self.assertEqual(InspectorRedactionPolicy(keys=("password",)).to_dict()["keys"], ["password"])
         self.assertEqual(InspectorReportBuilder.__name__, "InspectorReportBuilder")
+        self.assertEqual(InspectorRunIndex({"schema_version": INSPECTOR_RUN_INDEX_SCHEMA_VERSION}).to_dict()["schema_version"], INSPECTOR_RUN_INDEX_SCHEMA_VERSION)
         self.assertEqual(ReadOnlyPostgresStore.__name__, "ReadOnlyPostgresStore")