docs(pm-dispatch): triage closes a report-only instrument's fix card not_planned at first grade, citing ruling 208

instrument-discipline.md says a report-only instrument gets no card, no
dev and no PR, and that its only in-flight work is deletion (ruling 208).
Nothing on the triage path read that line, so the grade never asked it.
One sentence in the grading block of references/triage-duties.md now
does: a card whose fix lands in a report-only instrument (the widening
tell, the half-state patrols) closes not_planned at first touch, citing
ruling 208, and the instrument's only in-flight work is deletion. No new
gate, label or script.

Enumeration pin (the two instances where the line was not read; a third
is a red reading of this sentence, not a new card):
  - #20969 / PR #21016 (landed)
  - #21465 / PR #21679 (held)

Paid in place, net 0 lines (120 -> 120, ceiling unchanged, no re-wrap):
the deleted line is the triage-side restatement of the filing door's four
classes; its owning copy stays in references/filing-gate.md (the class
list and the refusal of everything else, one line, with the four class
heads on the lines below it), reached from the pointer line kept right
under the deleted one.

Claude-Session: https://claude.ai/code/session_01CB6W87z22K2yjUCDyVrJRk
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.claude/skills/pm-dispatch/references/triage-duties.md

@@ -37,7 +37,6 @@
 - 碰迁移形状或删已发布能力也进决策箱;说明书脱节不进:有裁定出处才是 (b),否则改文档。
 - 决策卡落卡必带四棱卡面块与其上的「维护者速读」,⛔ 不留待有人接手再补。
 - 决策卡的速读同题,用业务语言先讲事情与选项,末句只问一字:A/B/C 或是否。
-- 立卡门四类:① 缺陷 / ② 维护者决定 / ③ 直派任务 / ④ 协调节点,⛔ 其余一律不立卡。
 - 首行写立卡门类别 ①–④;四类定义、⛔ 清单、三答与配额见 `references/filing-gate.md`。
 - `finding` = 三类内待定级:(a) 可复现缺陷(复现或失败探针);(b) 违背已声明契约(引契约文);
 - (c) AI 写元数据会被运行时拒收或静默丢弃的陷阱;其余进 PR `## Acceptance notes`,⛔ 不立卡。
@@ -62,6 +61,7 @@
 - 清单项三态定级(会 fail / 步骤够不到 / 无项断言)与定级判据见 `references/filing-gate.md`。
 - 「无则关」= 首触即关 not_planned,带理由与入队两条件,⛔ 不定 p3、不 hold;下行同此。
 - 所入车道队列 P0/P1 开着(= 未派发,在飞不算)时,无解锁对象的 p2/p3 `tooling` 卡同样关。
+- 只报告仪器(放宽 tell、半状态巡查)的修复卡首触即关 not_planned,引裁决 208;在途只有删除。
 - 路由是分诊的技术判断,⛔ 永不升级哪个仓的问题;父单是协调节点,永不派发。
 - 父单已有子结构的:父单队列标签即可,分诊逐个展开路由、补 `Blocked-by:` 排序。
 - 跨层功能点(≥2 层)立父单带 `area:*`+`pm:epic`+清单项级,逐层子单按 `Blocked-by:` 排。