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>

src/scribe/mcp/tools/tasks.py

@@ -31,6 +31,7 @@ from scribe.services.notes import minted_kind
 from scribe.services import placement as placement_svc
 from scribe.services import planning as planning_svc
 from scribe.services import record_batch as batch_svc
+from scribe.services import reply_preferences as reply_prefs_svc
 from scribe.services import rulebooks as rulebooks_svc
 from scribe.services import systems as systems_svc
 from scribe.services import task_logs as task_logs_svc
@@ -273,7 +274,13 @@ async def update_task(
     reads exactly like a real one when it is wrong.
 
     Closing a task (done or cancelled) also returns `report_back`: a one-line
-    reminder of what the reply to the operator should cover.
+    reminder of what the reply to the operator should cover. When the
+    operator has preferences for how a completion report is written, they
+    come back as `reply_preferences` ({id, title, statement, kind}) — found
+    by their `when_to_apply`, so a preference whose trigger is writing the
+    report after finishing a task is the one that arrives here. Where one
+    differs from the default shape, the preference is what the operator
+    asked for.
     """
     uid = current_user_id()
     fields: dict = {}
@@ -314,6 +321,14 @@ async def update_task(
     await placement_svc.attach_placement(uid, data, note)
     if status in _CLOSING_STATUSES:
         data["report_back"] = REPORT_BACK_CUE
+        # The operator's own adjustments to the completion report, retrieved
+        # at the one moment a server can see that report coming (milestone
+        # 409 step 4). Omitted rather than sent empty, like every decoration.
+        prefs = await reply_prefs_svc.completion_preferences(
+            uid, project_id=getattr(note, "project_id", None))
+        if prefs:
+            data["reply_preferences"] = prefs
+            data["report_back"] = REPORT_BACK_CUE + " " + REPLY_PREFERENCES_CUE
     return data
 
 
@@ -360,6 +375,12 @@ REPORT_BACK_CUE = (
     "Reporting this to the operator? Say where it sits (from `placement`), "
     "what now works, what needs them, and what comes next."
 )
+# Appended only when `reply_preferences` is present, so the key never arrives
+# unexplained and a session with no preferences reads exactly what it did.
+REPLY_PREFERENCES_CUE = (
+    "The operator has preferences for how this report is written — "
+    "follow `reply_preferences` over the default shape where they differ."
+)
 
 _ITEM_KEYS = {"title", "body", "type", "status", "priority", "kind", "tags", "system_ids"}