Clarify ABIDES hook signatures

Author: Muhtasham

codeclash/arenas/abides/runtime/README.md

@@ -13,4 +13,7 @@ across identical seeded market worlds.
 Scores are computed from exchange execution messages, so editing `self.holdings` directly does not
 create scored profit.
 Some upstream ABIDES agents keep default behavior behind exact-class checks. If you subclass one of
-those agents, override the relevant hooks instead of relying on an empty subclass.
+those agents, override the relevant hooks instead of relying on an empty subclass. Inspect method
+signatures before overriding them; common signatures are `wakeup(self, currentTime)`,
+`receiveMessage(self, currentTime, msg)`, `kernelStarting(self, startTime)`, and
+`kernelStopping(self)`.

configs/examples/ABIDES__dummy__r1__s2.yaml

@@ -28,5 +28,9 @@ prompts:
 
     from agent.ValueAgent import ValueAgent as MyAgent
 
+    If you subclass an upstream ABIDES agent, inspect and match ABIDES method signatures exactly.
+    Common hooks are `wakeup(self, currentTime)`, `receiveMessage(self, currentTime, msg)`,
+    `kernelStarting(self, startTime)`, and `kernelStopping(self)`.
+
     The arena runs compact ABIDES market simulations. Your objective is to maximize average
     mark-to-market profit across identical seeded market worlds.

docs/reference/arenas/abides.md

@@ -41,7 +41,9 @@ is installed in the ABIDES arena Docker image, not in CodeClash's core Python en
 
 Some upstream ABIDES agents, including `ValueAgent`, keep default behavior behind exact-class
 checks. If you subclass one of those agents, override the relevant `wakeup` and `receiveMessage`
-hooks instead of relying on `pass`.
+hooks instead of relying on `pass`. Inspect method signatures before overriding hooks; common
+signatures are `wakeup(self, currentTime)`, `receiveMessage(self, currentTime, msg)`,
+`kernelStarting(self, startTime)`, and `kernelStopping(self)`.
 
 ## Configuration Example