mirror of
https://github.com/hanzoai/gateway.git
synced 2026-11-02 08:45:10 +00:00
zeekayandHanzo Dev
9d9c15f32f
The rejecter chain was built on every boot and handed to a handler factory that discarded it. It existed to feed the endpoint JWT validator this gateway no longer runs, no config declares `auth/revoker` or `krakend-bf`, and a thing whose product is discarded should not be built. The alias table drops `auth/revoker` with it, so the list of namespaces the gateway honours stays a list of namespaces the gateway honours. The CEL rejecter went with it. `validation/cel` is untouched — it is wired through the proxy and backend factories, and the shipped lux config's expression still loads. LLM.md states completeness rather than presence, the two shipped configs and how they map to canon's validators, and the polarity to watch while classifying: `true` both makes the check pass and preserves what a route did before, which is why it is the answer that needs justifying. Co-authored-by: Hanzo Dev <[email protected]>