Implement PR

Own the change through a green, review-ready PR. Completion is the merge-ready PR, not the finished code.

1. Take ownership of linked work

For every linked ticket or work item, record ownership before implementation: Use the tracker's assignee field to assign the item to the currently authenticated user. If assignment is unavailable, use the tracker's explicit ownership or in-progress mechanism.

2. Establish the contract

Read the request, linked tickets or spec, repository instructions, and relevant code before editing. Keep a short working contract with five parts:

• Outcome: observable behavior that must exist.
• Preserve: behavior and interfaces that must stay unchanged.
• Scope: files, packages, and systems the request permits changing.
• Evidence: focused checks that prove the outcome and preserved behavior.
• Stop: the PR, required CI, and requested review state that define completion.

Resolve repository facts by inspection. Choose defaults for internal, reversible decisions that follow existing patterns and are cheap to change. Ask the user only when a choice changes product behavior, visible UX, data meaning, permissions, security, cost, compatibility, is destructive or expensive to reverse, requires authority or credentials, or needs information only the user has. Include a recommended default and the boundary reason with every question.