[aryasaatvik]

Adds @executor-js/plugin-execution-history — an opt-in execution-history sink built on the observer foundation.

• Records every run (plus its tool calls and interactions) into three owner-scoped pluginStorage collections via a buffered-batch writer — no new tables, no migrations; works on D1/libSQL/sqlite/postgres.
• ./api: a scoped read API (list/get/listToolCalls) over HttpApi (executionHistoryHttpPlugin).
• ./client: a Runs page at /plugins/executionHistory/ (table, status filter, pagination, 4-tab detail drawer) — mounts via the existing plugins catch-all with zero router changes.

The base . entry never loads the API or React layers. Fully opt-in (not registered in any default config).

Stacked on the execution-observer foundation. Gates: format:check, lint, full-monorepo typecheck, unit + handler tests green. Runs-page live render still to verify.

Stack

1. feat: add the execution-observer foundation #12
2. feat: add the execution-history plugin #13 👈 current
3. feat: add the execution-metrics plugin #14

[greptile-apps]

Greptile Summary

Adds @executor-js/plugin-execution-history — an opt-in, observer-backed sink that records every execution run, tool call, and interaction into three owner-scoped pluginStorage collections with a buffered-batch write model, along with a scoped HTTP read API and a React Runs page.

• SDK (./src/sdk): makeExecutionHistoryStore buffers per-execution data in memory until ExecutionFinished flushes it to storage in one batch; two eager writes (running, waiting_for_interaction) provide restart durability. All previous review issues (buffer leak on StorageFailure, ExecutionFinished fallthrough, unsafe statusFilter cast, empty-page pagination label, compact prettyJson) are resolved.
• API (./src/api): Three read endpoints (list, get, listToolCalls) over HttpApiGroup; statusFilter is validated against RunStatus literals via Schema.is before reaching the storage facade.
• React (./src/react): Runs page with status filter, pagination, and a 4-tab detail drawer; mounts via the plugin catch-all route with no router changes needed.

Confidence Score: 5/5

Safe to merge — all blocking issues from the prior review round are addressed and no new defects were found in the changed code.

The buffer-cleanup guarantee, the ExecutionFinished fallthrough fix, the RunStatus validation, and the pagination display fix are all correctly implemented. The two remaining findings are both non-blocking suggestions (interaction kind defensive guard and a spurious "none" atom fetch on initial render).

No files require special attention — the core write path in store.ts and the HTTP handler wiring are solid.

Important Files Changed

Filename	Overview
packages/plugins/execution-history/src/sdk/store.ts	Buffered-batch writer + read surface; all previously flagged issues (buffer leak, ExecutionFinished fallthrough) are now resolved via Effect.ensuring and an explicit tag guard
packages/plugins/execution-history/src/sdk/collections.ts	Effect Schema definitions for RunRow/ToolCallRow/InteractionRow with indexed collections; looks correct
packages/plugins/execution-history/src/api/handlers.ts	HTTP handlers for list/get/listToolCalls; statusFilter now correctly filtered through Schema.is(RunStatus) guard, resolving the previous unsafe cast
packages/plugins/execution-history/src/react/RunsPage.tsx	Runs table with status filter, pagination, and detail drawer; prettyJson and empty-page pagination bugs from prior review are fixed; one minor sentinel atom call on initial render
packages/plugins/execution-history/src/api/handlers.test.ts	Handler integration tests covering CSV param mapping, no-filter case, get with null, and listToolCalls; well structured
packages/plugins/execution-history/src/sdk/store.test.ts	End-to-end store test through a real sqlite backend; covers started→tool call→finished lifecycle and verifies run/toolCall/interaction queries
packages/plugins/execution-history/src/react/atoms.ts	Atom family definitions for runs list, run detail, and tool calls; the "runDetailAtom" key of "none" passed from DetailDrawer may trigger a spurious network request on initial render
packages/plugins/execution-history/src/sdk/plugin.ts	Plugin definition wiring storage, extension, and observer together; straightforward and correct

Sequence Diagram

sequenceDiagram
    participant Engine as Execution Engine
    participant Observer as ExecutionObserver
    participant Store as ExecutionHistoryStore
    participant Buffer as RunBuffer (in-memory)
    participant Storage as PluginStorage (D1/sqlite)
    participant API as HTTP API
    participant UI as Runs Page (React)

    Engine->>Observer: ExecutionStarted
    Observer->>Store: handleEvent
    Store->>Buffer: buffers.set(executionId, ...)
    Store->>Storage: runsC.put(status: running)

    Engine->>Observer: ToolCallStarted / ToolCallFinished
    Observer->>Store: handleEvent
    Store->>Buffer: buffer.toolCalls.set(...)

    Engine->>Observer: InteractionStarted
    Observer->>Store: handleEvent
    Store->>Buffer: buffer.interactions.set(...)
    Store->>Storage: runsC.put(status: waiting_for_interaction)

    Engine->>Observer: InteractionResolved
    Observer->>Store: handleEvent
    Store->>Buffer: buffer.interactions.set(...updated)

    Engine->>Observer: ExecutionFinished
    Observer->>Store: handleEvent
    Store->>Storage: "runsC.put(terminal) + toolCallsC.put* + interactionsC.put*"
    Store->>Buffer: buffers.delete(executionId) via Effect.ensuring

    UI->>API: GET /execution-history/runs
    API->>Storage: runsC.query + runsC.count
    API-->>UI: runs + total

    UI->>API: GET /execution-history/runs/:id
    API->>Storage: runsC.get + toolCallsC.query + interactionsC.query
    API-->>UI: RunDetailResponse

Loading

_{Reviews (4): Last reviewed commit: "fix(plugin-execution-history): address G..." | Re-trigger Greptile}