Resource template boolean query parameters silently coerced any unrecognized string value to False — ?flag=banana would quietly become False instead of raising an error. The CLI's boolean parsing (client.py) already handled this correctly with explicit true/false sets; this applies the same pattern to template.py.

# Before: ?enabled=banana → False (silent)
# After:  ?enabled=banana → ValueError

@mcp.resource("config://settings{?enabled}")
def get_settings(enabled: bool = True) -> str:
    ...

Closes #3424