Follow-up from PR #297 clawpatch review.

The settings route is an optional catch-all, while static export only emits the finite paths from generateStaticParams. This may be intentional now that settings supports a constrained set of URL shapes, but we should either constrain the route or make generated/deep-link behavior explicit.

Scope:

• Audit supported /settings URL shapes.
• Either generate every supported path or reject unsupported catch-all paths intentionally.
• Add a production-build/deep-link smoke check if useful.