Template: Pull Request Description

Use this template when creating pull requests in any repository.

---

Summary

[1-3 bullet points describing what this PR does and why]

Implementation Plan Reference

• Plan: [Link to implementation plan]
• Task(s): [Task number(s) from the plan that this PR implements]

Changes

[Component / Area 1]

• [Description of change]
• [Description of change]

[Component / Area 2]

• [Description of change]

Database Migrations

• No migrations in this PR
• Migration V0XX__description.sql — [brief description of schema change]

Testing

Unit Tests

• New tests added for: [list of new test classes or scenarios]
• Existing tests updated for: [list of modified tests]
• All tests pass locally

Acceptance Tests

• Not applicable for this PR
• Bruno API tests added/updated in: api-test/[collection]/[suite]/
• Playwright e2e tests added/updated in: arda-frontend-app/e2e/specs/

Screenshots (for UI changes)

Before	After
[screenshot or N/A]	[screenshot]

CHANGELOG

• CHANGELOG entry added under the correct category (Added / Fixed / Changed / Removed)
• Version bump is appropriate (major / minor / bugfix)

Checklist

• Code follows project coding standards and patterns
• No secrets, credentials or hardcoded environment-specific values
• PR title is concise (under 70 characters)
• Related GitHub issue linked

Deviations from Plan

List any deviations from the implementation plan and the rationale for each. If none, write “None.”

Integration Details

Complete this section when this PR is part of a multi-worktree project using the integration branch pattern. Leave blank or omit for single-branch PRs.

• Base branch: [The branch this PR targets — typically main, but could be dev, stage, or a pre-existing feature branch. Never hardcode main; confirm the actual target before creating the PR.]
• Integration branch: [The <username>/<project-name>-integration branch that consolidates all worktree changes before this PR.]
• Worktree branches merged: [List the worktree branches merged into the integration branch, e.g., jmpicnic/my-project/task-a, jmpicnic/my-project/task-b]
• Coordinator: [The team-lead agent or person responsible for the integration branch and this PR]

If this is a single-branch PR with no parallel worktrees, replace this section with “N/A — single-branch PR.”

Open Questions

List any questions for the reviewer. If none, write “None.”