feat(409): an operator's own reply shapes reach the reply they are about (#4013)

The reporting-back skill ships default shapes; an operator's adjustments to
them are preference records. Prompt-time retrieval matches the operator's
message, and a shape preference is about the reply, so those preferences were
on file and never arrived. Operator's decision (logged on #4013): the server
delivers them for a completion report, and the skill asks for every other kind.

- Completion reports (option C): closing a task with update_task runs a
  kind-filtered preference search for the moment "writing the completion
  report after finishing a task" and returns matches as `reply_preferences`
  ({id, title, statement, kind}), with a sentence added to `report_back`
  naming the key. A preference says it is about completion reports through
  its own when_to_apply; no tag or column. Omitted when nothing matches, and
  the lookup fails open.
- Telemetry: every call logs to retrieval_logs under `report_preference`
  (empty calls included; a search that never ran writes no row) and hits are
  recorded surfaced. The source is ranked, so it counts toward pull-through.
  The bar is the prompt arm's setting until step 6 reads this source's near
  misses.
- Every other reply (option A): reporting-back gains "The operator's own
  shapes come first". Before a finding, decision, handoff or "where are we",
  search(content_type="rule") in the words of that moment and follow what
  comes back. Registered in the ownership guard with reporting-back as owner.
- Loading reply shapes at session start (option B) was rejected: it would be
  a small copy of the preloading milestone 394 retired.

Domain-neutral query (pinned); works on an install with no preferences.
Plugin version minted.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

plugin/skills/reporting-back/SKILL.md

@@ -41,6 +41,24 @@ it is wrong. So take placement from Scribe:
 - Work with no task behind it: say so plainly — "this wasn't tracked as a
   task" — and offer to record it. An honest "untracked" is a placement too.
 
+## The operator's own shapes come first
+
+The shapes below are defaults. An operator may have changed some of them — a
+section they always want, an order they read faster, a kind of reply they want
+shorter — and those changes are `preference` records. Where a preference and a
+default differ, the preference is what they asked for.
+
+- **A completion report brings its preferences with it.** Closing a task with
+  `update_task` returns them as **`reply_preferences`** when the operator has
+  any; the `report_back` line says so. Nothing to search for.
+- **Every other reply, ask before writing it.** A finding, a decision, a
+  handoff, a "where are we" — no tool call comes before these, so nothing
+  hands their preferences over. Once you know which kind of reply you are
+  writing, `search(content_type="rule")` for it in the words of that moment —
+  "writing a decision for the operator", "handing off to the operator" — and
+  follow any preference that comes back. Nothing coming back means the default
+  shape stands.
+
 ## Reports — work happened
 
 | Kind | Sections |