PR docs writer

Write or update documentation for user-facing PR changes. Do not generate release notes.

Before you begin

1. Load local context per ../shared/load-context.md.

Inputs

Either:

• PR numbers directly — triage inline using the criteria in ../docs-pr-check/SKILL.md before writing.
• A classified PR list from docs-pr-check — with PR numbers, classifications, gap notes, and suggested target files. Use these classifications as-is.

Input validation: Before starting, verify each PR is still accessible (gh pr view succeeds) and that any suggested target files exist on disk. If a PR has been deleted or a target file path has changed since triage, stop and report the issue rather than writing against stale data.

Handling PR content