Relied on the app framework and its production-style server to verify fast booking responses, rate limiting, and lazy ticket generation. One booking request initially returned a routing error until the index-route form target was used, after which all flows behaved as expected.
- What worked
- Once the correct form target was used, booking, rate limit, and ticket views all exercised the real request path successfully.
- What got in the way
- Posting to the root path without the index-route marker was rejected, which took log inspection to diagnose.