feat(500): reply shapes are delivered - the core every turn through the ledger, each slice at its moment, reply mounts before the reply (#5495)

- Every turn (/api/plugin/retrieve, UserPromptSubmit): the core reply shape
  leads the payload - in full the first time, as its one-line reminder
  after that - followed by whatever is mounted on reply.report, under the
  shared rule ledger. Fresh keys come back as shape_keys.
- The ledger is <sid>.shapes.ids in scribe-priorart (scribe_shapes_file /
  _seen / _append), so the compaction sweep that clears every .ids ledger
  is what brings the full core back after one.
- At a moment (/api/plugin/moment): the slice for that reply - completion
  on work.finish, asks on reply.ask, plan on work.plan - ahead of the
  mounted rules. reachable_tools now lists tools reaching a shaped moment
  even on an install with nothing mounted.
- Scribe's own tools (attach_moment_rules): reply_shape in the response,
  in full, since that door has no ledger. enter_project carries the core
  for clients with no prompt hook.
- Telemetry: one AppLog row per delivery (plugin / reply_shape), each
  shape with full or pointer and the door (turn, hook, mcp).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/scribe/mcp/tools/projects.py

@@ -28,6 +28,7 @@ from scribe.services import milestones as milestones_svc
 from scribe.services import notes as notes_svc
 from scribe.services import platforms as platforms_svc
 from scribe.services import projects as projects_svc
+from scribe.services import reply_shapes as reply_shapes_svc
 from scribe.services import rulebooks as rulebooks_svc
 from scribe.services import systems as systems_svc
 from scribe.services import trash as trash_svc
@@ -73,11 +74,16 @@ async def enter_project(project_id: int) -> dict:
         project_id: The project to enter.
 
     Returns a dict with keys: project, milestone_summary, open_tasks, systems,
-    design_system, project_rules, pattern_coverage —
+    design_system, project_rules, pattern_coverage, reply_shape —
     plus unplanned_milestones, milestone_summary_omitted,
     unplanned_milestones_omitted, family, inception and systems_bootstrap,
     each present only when it applies (see below).
 
+    `reply_shape` is the default shape of every reply you write to the
+    operator: conclusion first, the shortest reply that carries the answer,
+    where the work stands, and the one thing they need to do. Write to it;
+    an operator preference about replies that differs from it wins.
+
     `project` is id, title, status and the full goal. get_project has the
     whole record.
 
@@ -323,6 +329,11 @@ async def enter_project(project_id: int) -> dict:
         out["family"] = family
     if inception_ask:
         out["inception"] = inception_ask
+    # The core reply shape (milestone 500): for a client with no prompt hook,
+    # entering the project is the one point every session passes before it
+    # writes a reply. A plugin session gets it with its first turn as well;
+    # one repeat per session is the price of reaching every client.
+    out["reply_shape"] = reply_shapes_svc.render(reply_shapes_svc.core(), full=True)
     return out
 
 

src/scribe/mcp/tools/tasks.py

@@ -416,8 +416,9 @@ async def update_task(
     reconstructing them, because a remembered milestone title or "next step"
     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. When the
+    Closing a task (done or cancelled) also returns `reply_shape`, the
+    default shape of the completion report you are about to write, and
+    `report_back`: a one-line reminder of what that reply 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