elizaos--eliza/.github/pull_request_template.md

Relates to

Definition of Done: full standard in CONTRIBUTING.md.

• This PR targets develop and is rebased onto the latest origin/develop with zero conflicts (git fetch origin && git rebase origin/develop).
• bun install and bun run verify were run after sync, or any failure is recorded below with the exact unrelated blocker.
• A reviewer can confirm the change works without reading the code, from the evidence attached below.

Sync with develop

• Rebased/merged onto the latest origin/develop; zero conflicts.
• bun run verify passes post-sync, or the exact unrelated blocker is documented in Known gaps / failures below.

Risks

Background

What does this PR do?

What kind of change is this?

Documentation changes needed?

Testing

Where should a reviewer start?

Detailed testing steps

Evidence Gate

Any change testable on the frontend is not mergeable without a video walkthrough, before/after screenshots, and logs. If you did not attach them, say why.

Attach each applicable artifact inline in this PR (drag-and-drop into the description or a comment), or write N/A - <reason> on the row. Do not leave evidence rows blank. Videos must be MP4 (GitHub renders them inline); prefer JPG over PNG for screenshots. Do not commit evidence files to the repo.

• Before full-page screenshots are attached for every affected UI surface (desktop and mobile), or marked N/A - <reason>.

• After full-page screenshots are attached for every affected UI surface (desktop and mobile), or marked N/A - <reason>.

• A video walkthrough of the complete user flow is attached, or marked N/A - <reason>.

• Backend logs show the real code path firing end to end, or are marked N/A - <reason>.

• Frontend console and network logs show the request/response and state change, or are marked N/A - <reason>.

• Real-LLM trajectory is attached for agent/action/provider/prompt/model changes, or marked N/A - <reason>.

• Domain artifacts are attached where applicable (DB rows, memories, scheduled tasks, wallet/on-chain output, generated files, audio, etc.), or marked N/A - <reason>.

Evidence Details

Real LLM-call trajectory

For agent/action/provider/prompt/model changes, use a real live-model run, not the deterministic proxy. Produce with:

  packages/scenario-runner/bin/eliza-scenarios run <scenario> --report <out.json>

Link the JSON report, run viewer, native jsonl, or write N/A - <reason>.

Backend + frontend logs

Backend: structured logger lines ([ClassName] …) showing the code path firing end to end. Frontend: console + network trace showing the request/response and state change. Paste here inline (wrap long output in a <details> block), or write N/A - <reason>.

Screenshots (before / after) + video walkthrough

Full-page before AND after screenshots are required for any UI change. Include a video click-through of the flow.

  bun run evidence:doctor                 (check capture tools; prints fixes for any missing)
  bun run test:e2e:record                 (general E2E recordings)
  bun run --cwd packages/app audit:app    (app + cloud UI — REQUIRED for UI changes)

A UI-touching diff (rendered .tsx/.css/.svg under packages/app, packages/ui, apps/app, …) MUST attach real screenshot/video/OCR artifacts — the CI evidence gate rejects N/A on those rows for such diffs, label or not. If a capture tool is missing, evidence:doctor prints the install command; install it rather than marking evidence N/A.

Before

After

Walkthrough video

Or write N/A - <reason>.

Audio / voice walkthrough

For voice / transcript / TTS / STT / omnivoice changes, attach captured audio of the real round-trip plus a narrated walkthrough. Or write N/A - <reason>.

Known gaps / failures

List any command failure, missing artifact, unavailable device, unavailable live service, or evidence row marked N/A. Include the exact reason and why it is not a blocker for this PR.