docs: chain.py Event docstring shows gl.Event, which does not resolve at runtime #327

Problem

The docstring/examples on runners/genlayer-py-std/src/genlayer/chain.py (Event class, ~lines 103/107) show contracts subclassing gl.Event:

class TransferOccurredEvent(gl.Event):

But Event is exported only under genlayer.chain:

• top-level genlayer/__init__.py does from .types import *, and genlayer/types __all__ has no Event;
• the top-level __all__ lists submodules/aliases, not Event;
• the module-level __getattr__ is a lazy module loader only — __getattr__('Event') raises.

So a contract following the docstring crashes at module load:

File "/contract.py", line 8, in <module>
    class EmitterDeployed(gl.Event):
File "/py/libs/genlayer/__init__.py", line 186, in __getattr__
    raise AttributeError(f"module 'genlayer' has no attribute '{name}'")
AttributeError: module 'genlayer' has no attribute 'Event'

Verified against the py-lib-genlayer-std runner shipped in genvm-manager v0.6.0-rc1 (executor v0.3.0-rc7, runner map default py-genlayer:9b8kjyda…) by executing the same contract in both forms: gl.Event → VmError + empty emissions; gl.chain.Event → Return + the expected emission.

Why it bit hard downstream

The crashed deploy is still accepted by consensus (accepted-with-VmError), so an e2e that waits on transaction status sees a "successful" deploy that emitted nothing — the symptom ("zero events, everything green") implicated the executor/runner/manager/node pipeline before the docstring. Cost us a full cross-repo debugging cycle on the node side.

Fix options

1. Minimal: correct the docstring/examples to gl.chain.Event (and audit other docs for gl.Event, e.g. the website spec examples).
2. Nicer: additionally export Event at top level (add to the lazy map or re-export), making the current docstring true — the name is short and event definitions are common enough to warrant it.

Happy to PR option 1 if you prefer it.