http worker 0.21.4 registers parameterized routes but never matches them

Repro notes: https://github.com/lgs/iii-fasthtml-frontend/blob/main/docs/ARCHITECTURE.md#11-platform-quirks-discovered-all-worked-around-in-code. Register an http trigger such as /tasks/{tid}; registration succeeds and appears in registered triggers, but requests to /tasks/123 return <no route> in the http worker log. Equivalent literal /tasks/toggle route matches. Expected: path parameters match and are delivered according to the trigger contract. Workaround: literal paths plus hidden task_id form field; revert to {tid} routes after fix.