Implement ActionLoggingMiddleware with timing metrics #109

New issue

Open

opened 2026-03-15 04:13:17 +00:00 by freemo · 0 comments

freemo commented

2026-03-15 04:13:17 +00:00

Owner

Metadata

Commit Message: feat(dispatch): add action logging middleware
Branch: feature/m1-middleware-pipeline

Background and Context

ActionLoggingMiddleware (after_action, priority 800) logs each executed action with
timing information for performance monitoring and debugging.

Expected Behavior

Records wall-clock time before and after action execution
Logs action class, player name, arguments, and elapsed time
Log level is configurable (default: Logger::Medium)

Acceptance Criteria

ActionLoggingMiddleware at after_action priority 800
Timing measurement with millisecond precision
Configurable log level
BDD scenarios

Subtasks

Implement ActionLoggingMiddleware
Add timing measurement
Write Cucumber scenarios

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the
Commit Message in Metadata exactly.
The commit is pushed to the remote on the branch matching the Branch in Metadata.
The commit is submitted as a pull request to master, reviewed, and merged.

## Metadata - **Commit Message**: `feat(dispatch): add action logging middleware` - **Branch**: `feature/m1-middleware-pipeline` ## Background and Context ActionLoggingMiddleware (after_action, priority 800) logs each executed action with timing information for performance monitoring and debugging. ## Expected Behavior - Records wall-clock time before and after action execution - Logs action class, player name, arguments, and elapsed time - Log level is configurable (default: Logger::Medium) ## Acceptance Criteria - ActionLoggingMiddleware at after_action priority 800 - Timing measurement with millisecond precision - Configurable log level - BDD scenarios ## Subtasks - [ ] Implement ActionLoggingMiddleware - [ ] Add timing measurement - [ ] Write Cucumber scenarios ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged**.