feat(processes): composition contract — the process is the skeleton, the conversation supplies the parameters

Extends #2582's fix per the operator's direction: a stored Process must
incorporate the context it was triggered with, not displace it. No new
plumbing needed — the live context is already in the session; what was
missing is the stated contract. get_process now carries it: live
constraints/scope/focus fold into the procedure and override its
defaults where they disagree; a clarify step asks only what the
conversation has NOT already answered (confirm interpretations, don't
re-ask); stated concerns become lenses the procedure applies, not text
it discards. The sync-generated skill stubs state the short form.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

src/scribe/mcp/tools/processes.py

@@ -87,6 +87,16 @@ async def get_process(name_or_id: str) -> dict:
     fire mechanism. The operator says "run the <name> process"; call this and
     follow the returned body (including any 'clarify first' steps it contains).
 
+    COMPOSITION CONTRACT — a process is the PROCEDURE, not the whole prompt.
+    The conversation that invoked it supplies the PARAMETERS: fold the
+    operator's live constraints, scope, and focus areas into the procedure,
+    and wherever the two disagree, the live instructions override the
+    process's defaults. A 'clarify first' step asks only what the
+    conversation has NOT already answered — confirm your interpretation of
+    what was said rather than re-asking it, and turn stated concerns (a
+    posture, a hardware budget, a subsystem under suspicion) into lenses the
+    procedure applies, not text it discards.
+
     Resolution: numeric id → exact (case-insensitive) title → substring. On an
     ambiguous substring match, the best (most-recent) match is returned with an
     `other_matches` list so you can disambiguate with the operator.