context

Stateful context logic for Counterfact routes is managed by encapsulating domain actions and route state in _.context.ts files. This centralizes business rules so route handlers stay lean and delegate core logic to the context layer.

The best way to keep route handlers lean is to delegate core rules to a context layer using _.context.ts files. By centralizing state management there, handlers avoid bloating and logic evolves consistently across the application.

Unit tests for context behavior changes are added by updating methods in routes/**/_.context.ts and running the test suite. This enforces test coverage for every change, validating that context logic behaves as expected.

Yes, you can centralize route state and expose a clear API by defining actions within _.context.ts files. This approach maintains private state internally while providing a structured API for route handlers to consume.

The _.context.ts file works by applying stateful context logic to any route subtree within Counterfact. It encapsulates domain actions so that state and behavior are shared and tested consistently across nested routes.

Route handlers grow with business logic when state management is not separated into a context layer. Moving core rules into _.context.ts files centralizes the logic, keeping handlers focused on routing concerns.