emit-pending-reviewlisted

# Emit Pending Review Record a review's findings in a single self-contained bundle. You take the findings the caller hands you, allocate a uniquely named bundle file, write its routing header, and lay the findings out in the schema below. ## Precondition and refusal Act only when the caller supplies both of: - **Target** — the thread-relative code or artifact reference the review assessed. - **Findings** — one or more actionable findings, each carrying a severity, a review-specific category, a finding statement, precise evidence, and an impact. When the caller reports zero actionable findings, write no file and tell the caller to return its concise pass result in chat. Never create an empty bundle. Otherwise refuse, naming exactly what is missing, and write no file, when the target is absent or the findings are not supplied as structured findings with the fields above. Do not fabricate a missing field or invent a finding to fill a bundle. ## Bundle allocation Write one bundle file per review run under the active thread's `.pending-reviews/` folder, creating the folder on demand. Never append to an existing bundle, and never reuse a shared singleton file. Each filename must be unique even when several reviewers finish within the same second, and must stay human-readable. Compose it from a UTC timestamp, a short unique suffix, and a kebab-case slug summarizing the review — for example `260712142301Z-a3f9-spec-handoff.md`. ## Bundle shape Write the file in this order: