Goal: Produce a Conventional Commit PR title and a concise, factual PR summary for this branch, into the staging branch. STAGING. Assume MVP quality unless evidence exists otherwise.

Hard rules:

•Title MUST follow Conventional Commits: type(scope): subject (≤72 chars, imperative). Types: feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert. Scope = primary affected area (e.g., app, features, core, ports, adapters, infra, docs).
•If changes are disjoint or span multiple unrelated scopes, STOP and output: SPLIT_REQUIRED: <brief reason>.
•No hype or claims you cannot verify directly in diffs/tests.
•If you lack evidence for "Risk/Impact" or "Rollout," leave HTML comments with TODOs.

Process:

•
Enumerate diffs:
- •Get changed files and hunks (git diff --name-status origin/staging...HEAD and git diff).
- •Read touched code and docs to understand what actually changed (imports, exports, behavior, configs, tests).
•
Cohesion check:
- •Confirm a single coherent purpose and a single dominant scope. If not coherent → SPLIT_REQUIRED.
•
Title:
- •Derive a single Conventional Commit title reflecting the dominant change.
- •If breaking change is clear, add a BREAKING CHANGE: footer in the summary.
•
Summary:
- •Use the template below. Describe only what you can point to in the diff. No speculation.
•
Pull Request:
- •Create the PR to staging with the content you determined in 4.

Template to output:

Title: <type(scope): subject>

Context

Why this change exists, based only on code/comments/issue links in the diff. If unclear, write:

Change

Bullet the observable modifications (APIs, functions, files, configs). No promises.

Risk & Impact

User-facing or operational impact. List modules touched. If unknown:

Rollout / Backout

Minimal, concrete steps. If unknown:  /

Evidence

•CI:
•Screenshots/Logs:
•Manual validation:

Footers (if any)

•BREAKING CHANGE: <impact and required migration>
•Refs: <#issue>