fix(pr-pipeline): route a delivered report stop without reading work class #12766

Refs #9668

Outcome

The work-resolve-issue lane stops routing a report-delivered stop on work class. Today .github/scripts/work-resolve-issue/report-outcome.mjs (READ_ONLY_CLASS, about line 181, and the route about line 1335) closes only a work-class: read-only issue with no branch and retries any other; plugins/work-items/skills/work/SKILL.md (about line 167) states the same rule. After this change a delivered report with no branch is routed without a retry whatever the issue's class, the skill text says so, and a test covers a class-less and a structural issue on that route. Also reword the work-items docs that still say a merge partition reads the work-class: label (skills/triage/SKILL.md:38, reference/work-class-labels.md:3 and :22, reference/label-taxonomy.md:23, reference/item-content-trust.md:85, skills/triage/context/apply-outcome.md:44), since no merge step reads it (plugins/source-control/skills/babysit-prs/scripts/babysit_merge_policy.py, about line 4170). This is #9668's remainder: its other gates are removed and its eight sub-issues are closed.

Done when

The done-when lines below are copied from #9668 as written.

• git grep -n -i -E "work-class|workClass|work_class|lane_class" -- .github plugins/source-control/skills/babysit-prs/scripts plugins/work-items shows no read that refuses, holds, escalates or routes on a class (docs describing the removal are fine).
• The intake, admission, pr-merge and resolve-config test suites pass, with a case per former gate showing a class-less and a structural issue or PR passing it.

Notes

Drafted by the issue-triage session. Agent choice, not an owner answer. Owner decision Q85 on #9668: stop gating any step on work class. The untrusted-provenance hold is not a class read and stays.

Related

• feat(pr-pipeline): stop gating any step on work class (owner Q85) #9668 (parent), fix(pr-pipeline): route the issue lane's non-owner stops away from a person #10978.