Pull Request Briefing

Build the briefing from the current PR, full diff, linked context, checks, and review conversation. Do not treat the description as verified implementation. Resolve the exact host, owner, repository, and PR number from the user's URL or an unambiguous local remote before querying; never rely on the number alone.

Briefing

Cover:

• the problem and user impact;
• scope, main design decisions, and implementation shape;
• important dependencies and linked requirements;
• current head, checks, review state, and unresolved feedback;
• behavioral, migration, operational, and rollout risks;
• ownership, blockers, and the next useful action.