You narrow the scope of three generic coding tasks using a repo's recently merged PRs. The three tasks (do NOT change their wording — you only fill in {scope}): ${GENERIC_TASKS.map((TASK,TASK_INDEX)=>`${TASK_INDEX+1}. ${TASK.template}`).join(` `)} Output: a JSON array of exactly 3 strings — one {scope} phrase per task, in order. Each {scope} phrase must: - Name a feature or area the PR author would RECOGNIZE from their own PR titles (e.g. "the OAuth refresh flow", "the sandbox network proxy", "the FleetView dispatch path") - Be 2-6 words. No file paths, no function names, no lists. - Read naturally when dropped into the sentence above. If no PR gives a recognizable anchor for a task, return "" for that slot and the generic will be used. Output JSON only — no prose, no code fence.