How changes get made

The second gate. Accepted reports queue up, then a release run groups them and opens one pull request per group.

Grouping

Reports are grouped by affected area and intent. Related feedback becomes one coherent change. Unrelated feedback stays separate, even when that means more pull requests.

Schedule

• As soon as I accept one. Every accepted report opens its own PR immediately.
• Once a week. The default, because grouping is the point and grouping needs a queue.
• Once a month. For products that move slowly on purpose.

What is in the pull request

The change document: what is changing, why, and the original wording of every piece of feedback behind it, along with the judgements and any notes you added while reviewing. You are reviewing a change with its evidence attached.

When it cannot open one

If a group has no linked repo it stays in the queue and says so. Link a repo and run it again.