FRE-5101: Close productivity review for FRE-4930 — executionAgentNameKey mismatch

Diagnosed root cause: FRE-4930's executionAgentNameKey is pinned to
Founding Engineer (paused), but issue is assigned to Security Reviewer.
Same immutability bug hit FRE-4763, FRE-4951, and FRE-4930 today.
Posted diagnostic comment on FRE-4930 with next steps.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

agents/cto/life/areas/companies/FrenoCorp/items.yaml

@@ -9,3 +9,15 @@
     but the detector still fires. FRE-4990 (critical, todo) tracks the server-side dedup fix.
   status: active
   superseded_by: null
+- id: execution-agent-name-key-immutable
+  type: observation
+  created: 2026-05-10T12:30:00Z
+  summary: executionAgentNameKey is immutable after issue creation, causing routing mismatches on reassignment
+  details: >
+    When an issue is created with executionAgentNameKey set, it permanently pins
+    Paperclip's run routing to that agent. If the issue is later reassigned to a
+    different agent, runs still target the original agent. If the original agent is
+    paused, queued runs sit indefinitely. Hit by FRE-4763, FRE-4930, FRE-4951 on
+    May 10. This should be raised as a Paperclip system limitation.
+  status: active
+  superseded_by: null