Skip to content

Persist self-healing process traces#53

Draft
giaphutran12 wants to merge 1 commit into
codex/collection-official-website-sourcesfrom
codex/self-healing-process-trace
Draft

Persist self-healing process traces#53
giaphutran12 wants to merge 1 commit into
codex/collection-official-website-sourcesfrom
codex/self-healing-process-trace

Conversation

@giaphutran12
Copy link
Copy Markdown
Collaborator

Summary

Stacked on #52 (codex/collection-official-website-sources).

This makes the self-healing layer persist a real process trace artifact from both runtime paths:

  • Mastra/injected runtime records search, fetch, insert-row, and recovery steps.
  • Collection runtime maps vendored pipeline reports into the same trace shape.
  • Self-healing run records persist a process-trace artifact, including search queries, fetched URLs, source artifacts, selected row source, notes, and ordered steps.
  • playwright-candidate-script is reserved as an artifact kind but intentionally not emitted yet.

Reviewer fixes included:

  • Search-result URLs are no longer labeled as successful fetch artifacts. Captured sources now track search, fetch, or synthetic provenance.
  • Large process-trace artifacts are truncated before JSON serialization, so the stored artifact remains valid parseable JSON and stays within the artifact size cap.

What this does not claim

  • No Playwright script compiler yet.
  • No cron rerun/promotion of generated Playwright scripts yet.
  • No automatic benchmark migration into Meteor's next app branch yet.

Verification

  • node --import ./backend/node_modules/tsx/dist/esm/index.mjs --test backend/test/populate-self-healing.test.ts backend/test/collection-agent-runner.test.ts
  • npm --prefix backend run build
  • npm --prefix backend test
  • git diff --check
  • node --check benchmarks/dataset-agent/run-benchmark.mjs
  • make verify-self-healing

@giaphutran12 giaphutran12 self-assigned this May 22, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 22, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e2cef09c-5cc7-44d5-aa1a-5d3182a7a4ff

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/self-healing-process-trace

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 and usage tips.

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.

1 participant