partly or unimplemented features - now implemented

docs/features/unchecked/gateway/router-back-pressure-middleware.md

@@ -0,0 +1,37 @@
+# Router Back-Pressure Middleware (Dual-Window Rate Limiting + Circuit Breaker)
+
+## Module
+Gateway
+
+## Status
+IMPLEMENTED
+
+## Description
+Rate limiting is present in the Gateway and Graph API services. The advisory's highly detailed dual-window rate limiter with Redis/Valkey-backed environment limiter, ring counter, and custom circuit breaker pattern is not implemented as described. Standard ASP.NET rate limiting is used instead.
+
+## What's Implemented
+- Gateway middleware pipeline with request routing: `src/Gateway/StellaOps.Gateway.WebService/Middleware/RequestRoutingMiddleware.cs`
+- Sender constraint middleware: `src/Gateway/StellaOps.Gateway.WebService/Middleware/SenderConstraintMiddleware.cs`
+- Gateway options with configurable limits: `src/Gateway/StellaOps.Gateway.WebService/Configuration/GatewayOptions.cs`
+- Gateway metrics: `src/Gateway/StellaOps.Gateway.WebService/Services/GatewayMetrics.cs`
+- Standard ASP.NET rate limiting via middleware pipeline
+- **Router module has advanced rate limiting** (separate from Gateway):
+  - `src/Router/__Libraries/StellaOps.Router.Gateway/RateLimit/EnvironmentRateLimiter.cs` -- Valkey-backed environment rate limiter with circuit breaker
+  - `src/Router/__Libraries/StellaOps.Router.Gateway/RateLimit/InstanceRateLimiter.cs` -- per-instance rate limiting
+  - `src/Router/__Libraries/StellaOps.Router.Gateway/RateLimit/RateLimitService.cs` -- rate limit service orchestrator
+  - `src/Router/__Libraries/StellaOps.Messaging.Transport.Valkey/ValkeyRateLimiter.cs` -- Valkey-backed distributed rate limiter
+- Source: Feature matrix scan
+
+## What's Missing
+- **Gateway integration with Router rate limiting**: The Router module has Valkey-backed rate limiting and circuit breaker, but the Gateway module does not consume these services. The Gateway still uses standard ASP.NET rate limiting.
+- Dual-window rate limiter with sliding window algorithm in the Gateway
+- Ring counter implementation for rate tracking in the Gateway
+- Unified rate limit configuration across Gateway and Router modules
+
+## Implementation Plan
+- Evaluate whether standard ASP.NET rate limiting is sufficient for current scale
+- If needed, implement Redis/Valkey-backed rate limiting for distributed deployment
+- Add circuit breaker pattern for downstream service protection
+
+## Related Documentation
+- Source: See feature catalog

docs/features/unchecked/gateway/stellarouter-performance-testing-pipeline.md

@@ -0,0 +1,30 @@
+# StellaRouter Performance Testing Pipeline (k6 + Prometheus + Correlation IDs)
+
+## Module
+Gateway
+
+## Status
+IMPLEMENTED
+
+## Description
+The StellaRouter gateway service exists but the advisory's proposed k6 performance testing scenarios (A-G), correlation ID instrumentation, and Prometheus metric dashboards for performance curve modeling are not present as source code artifacts. These may exist as devops artifacts outside src/.
+
+## What's Implemented
+- Gateway service with full middleware pipeline: `src/Gateway/StellaOps.Gateway.WebService/`
+- Correlation ID middleware: `src/Gateway/StellaOps.Gateway.WebService/Middleware/CorrelationIdMiddleware.cs`
+- Gateway metrics: `src/Gateway/StellaOps.Gateway.WebService/Services/GatewayMetrics.cs` -- Prometheus-compatible metrics
+- Health monitoring: `src/Gateway/StellaOps.Gateway.WebService/Services/GatewayHealthMonitorService.cs`
+- Source: Feature matrix scan
+
+## What's Missing
+- k6 performance testing scripts (scenarios A-G)
+- Prometheus metric dashboards for performance curve modeling
+- These may exist under `devops/` rather than `src/` -- check `devops/` directory
+
+## Implementation Plan
+- Create k6 test scripts for Gateway performance scenarios
+- Add Grafana/Prometheus dashboards for Gateway metrics visualization
+- These are DevOps artifacts and may belong under `devops/perf/` or similar
+
+## Related Documentation
+- Source: See feature catalog