Skip to content

feat: persist orchestration and payment events for audit history (Closes #26) - #107

Closed
laurentketterle-hub wants to merge 3 commits into
Flamki:masterfrom
laurentketterle-hub:feat/file-run-history-26
Closed

feat: persist orchestration and payment events for audit history (Closes #26)#107
laurentketterle-hub wants to merge 3 commits into
Flamki:masterfrom
laurentketterle-hub:feat/file-run-history-26

Conversation

@laurentketterle-hub

Copy link
Copy Markdown
Contributor

Summary

Implements durable run history with file-based persistence and API access.

What this solves

  • Survives restarts: runs persisted to data/run-history.json via atomic writes
  • Audit trail: each run records task, budget, spend, tx hash, status, explorer URL
  • Storage configurable: RUN_HISTORY_STORAGE=file, RUN_HISTORY_FILE, RUN_HISTORY_MAX_RUNS
  • API access: GET /api/runs (list recent) and GET /api/runs/:id (single run)
  • Backward compatible: existing in-memory mode unchanged

Files

  • New: src/storage/file-run-history.jsFileRunHistoryStore class
  • Updated: src/storage/run-history.js — re-exports the new class
  • Updated: src/server.js — adds /api/runs and /api/runs/:id endpoints

Closes #26

Signed-off-by: laurentketterle-hub <laurentketterle-hub@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@laurentketterle-hub, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 5513460a-17d9-4925-82e1-847a40d08e33

📥 Commits

Reviewing files that changed from the base of the PR and between 6eb1d2b and 0f9468b.

📒 Files selected for processing (2)
  • src/storage/file-run-history.js
  • src/storage/run-history.js

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Signed-off-by: laurentketterle-hub <laurentketterle-hub@users.noreply.github.com>
Signed-off-by: laurentketterle-hub <laurentketterle-hub@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Persist orchestration and payment events for audit history

1 participant