hackbot: run per-action-type hooks before recording an action

[suhaibmujahid]

Resolves #6424

ActionsRecorder now takes a mapping of action type to hooks (plus add_hook for wiring one after construction). Each hook receives the fully built action dict just before it is appended and may mutate it in place; raising aborts the recording, so a hook also serves as a validation gate.

Hooks live on the recorder so the runtime can attach behaviour that cuts across action domains without every handler knowing about it.

[Copilot]

Pull request overview

Adds per-action-type “pre-record” hooks to hackbot_runtime.actions.ActionsRecorder, allowing the runtime to enrich or reject actions centrally right before they’re appended to the recorder.

Changes:

• Introduces an ActionHook type and hook registration (hooks= in constructor + add_hook()).
• Executes registered hooks in order during record() and propagates hook exceptions to abort recording.
• Adds unit tests covering ordering, scoping, mutation visibility, abort behavior, and hook registration semantics.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
libs/hackbot-runtime/hackbot_runtime/actions/recorder.py	Adds hook storage/registration and runs hooks during record() before appending actions.
libs/hackbot-runtime/hackbot_runtime/actions/init.py	Exports ActionHook alongside ActionsRecorder.
libs/hackbot-runtime/tests/test_recorder.py	Adds test coverage for the new hook behavior and invariants.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.