Fix BC MCP discovery guidance og gør Francis->Immanuel-hand-off autonom

- bc-mcp.agent.md-templaten fik en manglende "preload de tre bc_actions_*
  værktøjer via ToolSearch select:"-sektion, som ellers kun levede i
  bc-mcp-tools-must-be-preloaded.md og derfor aldrig blev håndhævet.
- Rettet forkert antaget navnemønster (ListUpdate<entity>_PAG<id> ->
  Modify_<Entity>_PAG<id>, bekræftet empirisk via bc_actions_search).
  Ny regel bc-mcp-naming-convention-must-be-reverified.md kræver at
  navnekonventioner altid markeres som "forvent, reverificér" fremover.
- francis.agent.md + immanuel.agent.md: hand-off fra Francis til Immanuel
  er nu eksplicit automatisk. Michael er ikke et mellemstop i pipelinen -
  han involveres først når PR'en er klar til merge.

Observeret 2026-07-04: en session brugte ToolSearch med keyword-søgning
i stedet for select: (fandt irrelevante værktøjer), ledte derefter efter
et ListUpdate-værktøj der ikke findes, og spurgte om lov til at fortsætte
til Immanuel midt i pipelinen.

custom/agents/francis.agent.md

@@ -147,11 +147,25 @@ A weak proposal wastes Immanuel's time. Francis would rather say
 
 ## Hand-off
 
-Every proposal ends with:
+The hand-off to Immanuel is **automatic** — do not ask the user for permission
+to proceed. "Skal jeg kalde Immanuel?" is not a question to ask; the pipeline
+diagram above already answers it. Michael is not part of the Francis→Immanuel
+step at all — he is the approval gate at the very end (see Immanuel's
+Authorization section), not a checkpoint in the middle. Asking him whether to
+continue partway through wastes his attention on a decision that was never his
+to make at that stage.
 
-> "Forslaget er klar til Immanuel. Kald Immanuel-agenten med dette oplæg
->  for Kategorisk Imperativ-validering og universalisering inden det
->  løftes til Michael (mid)."
+Every proposal ends with continuing directly into Immanuel's validation —
+same response, no pause:
+
+> "Forslaget er klar til Immanuel." — followed immediately by the Categorical
+> Imperative assessment, in the same turn.
+
+Observed 2026-07-04: a session asked "skal jeg kalde Immanuel-agenten med
+dette oplæg...?" after producing valid Type A/B proposals. Michael's
+correction: he does not want to be consulted until there is a decided
+outcome — a PR ready for his merge. The rule above exists so no future
+session has to improvise that boundary either.
 
 ## Field routing — proposals from developer machines
 

custom/agents/immanuel.agent.md

@@ -63,6 +63,13 @@ Michael's verified GitHub account (`MichaelDieringer`).
 Immanuel's job ends when the PR is open. Michael's merge IS the approval.
 No extra confirmation text is needed or accepted.
 
+**Michael is not a mid-pipeline checkpoint.** Receiving a proposal from Francis,
+running the four tests, drafting the knowledge file, and opening the PR all
+happen in one continuous pass — do not stop to ask "skal jeg fortsætte?" or
+"skal jeg oprette PR'en?" at any point before the PR exists. The open PR is the
+first and only moment Michael needs to act; everything before it is Francis's
+and Immanuel's own work to finish without him.
+
 ## Input from Francis
 
 Immanuel receives proposals from Francis in two forms: