server.max_concurrent_requests and request_timeout are not enforced #78

Summary

The configured global request concurrency limit and request timeout are not applied to the server router.

Current behavior

server.max_concurrent_requests and server.request_timeout are exposed as configuration, but router construction does not install middleware that enforces either value. The middleware module documentation describes global concurrency and timeout behavior that the running server does not provide.

Expected behavior

Requests should be bounded by the configured global concurrency limit and timeout, with behavior and error responses covered by tests.

Suggested implementation

Install the appropriate concurrency and timeout layers during router construction using the validated configuration values. Add tests that saturate the global limit and exercise a timed-out handler. If these controls are not part of the intended server design, remove the inert fields and misleading documentation.

Relevant code

• crates/walgit-config/src/lib.rs:43
• crates/walgit-server/src/lib.rs:139
• crates/walgit-server/src/middleware.rs:1