Epic: Action Middleware Pipeline #104

New issue

Open

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

freemo commented

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

Owner

Metadata

Commit Message: feat(dispatch): implement action middleware pipeline
Branch: feature/middleware-pipeline

Background and Context

The specification describes a composable middleware pipeline that wraps action execution
with before_action and after_action filters. Each middleware has a numeric priority that
determines execution order. This replaces the current pattern of duplicating guard checks
(permission, balance, position) inside each command handler.

Expected Behavior

Middleware classes register for before_action or after_action phases with a priority.
The pipeline executes before_action middleware in priority order, then the action, then
after_action middleware. Any middleware can halt the chain.

Acceptance Criteria

Middleware base class with call(action, context) interface
MiddlewarePipeline executor with priority ordering
Built-in middleware: Permission, Alive, Balance, Position, Cooldown, Logging, EventSourcing
CommandAction metadata DSL for declaring requirements
BDD test coverage

Subtasks

Implement Middleware base and MiddlewarePipeline
Implement PermissionCheck and AliveCheck middleware
Implement BalanceCheck and PositionCheck middleware
Implement CooldownMiddleware
Implement ActionLoggingMiddleware
Implement EventSourcingMiddleware
Add CommandAction metadata DSL

Definition of Done

This Epic is complete when all child issues are closed and all acceptance criteria
are satisfied.

## Metadata - **Commit Message**: `feat(dispatch): implement action middleware pipeline` - **Branch**: `feature/middleware-pipeline` ## Background and Context The specification describes a composable middleware pipeline that wraps action execution with before_action and after_action filters. Each middleware has a numeric priority that determines execution order. This replaces the current pattern of duplicating guard checks (permission, balance, position) inside each command handler. ## Expected Behavior Middleware classes register for before_action or after_action phases with a priority. The pipeline executes before_action middleware in priority order, then the action, then after_action middleware. Any middleware can halt the chain. ## Acceptance Criteria - `Middleware` base class with `call(action, context)` interface - `MiddlewarePipeline` executor with priority ordering - Built-in middleware: Permission, Alive, Balance, Position, Cooldown, Logging, EventSourcing - `CommandAction` metadata DSL for declaring requirements - BDD test coverage ## Subtasks - [ ] Implement Middleware base and MiddlewarePipeline - [ ] Implement PermissionCheck and AliveCheck middleware - [ ] Implement BalanceCheck and PositionCheck middleware - [ ] Implement CooldownMiddleware - [ ] Implement ActionLoggingMiddleware - [ ] Implement EventSourcingMiddleware - [ ] Add CommandAction metadata DSL ## Definition of Done This Epic is complete when all child issues are closed and all acceptance criteria are satisfied.