Measure each fix from the move to fixing to delivered, and say one over its budget (issue 403)

hq ADR 0313: the operator's five minutes start when an agent moves the issue
to fixing, not at the merge. mesh-delivery says on each transition, and in
checks, when the pull request opened, when it merged and the class of what it
moves. mesh-issues keeps the first move to fixing, the fix time with its four
phases once the last fix is delivered, serves fix-times, and says
issue-tracker.fix.<class>.over-budget on the operator's channel, cleared by the
next fix of that class within budget.

modules/mesh-issues/module.json

@@ -17,7 +17,8 @@
         "groom",
         "set",
         "tracking",
-        "reserve"
+        "reserve",
+        "fix-times"
       ]
     }
   ],
@@ -36,7 +37,8 @@
         "groom",
         "set",
         "tracking",
-        "reserve"
+        "reserve",
+        "fix-times"
       ]
     }
   ],
@@ -61,6 +63,7 @@
     "claude-code.claude_code_judge",
     "seat:mesh-delivery.checks",
     "seat:operator-channel.notify",
+    "gitea.gitea_pull_reviews",
     "records.records_status",
     "records.records_list",
     "records.records_read",