fix(core): make me_hotsite url non-capturing so the view does not take a dummy arg

[SAY-5]

What

core/urls.py routes /me/ and /ME/ to me_hotsite via a re_path with a capturing group:

re_path(
    r"^(me|ME)\/?$",
    me_hotsite,
    name="mitologia-extendida",
),

Because the group is capturing, Django passes the matched string ("me" or "ME") as a positional arg to the view. The view swallows it with an underscore:

def me_hotsite(request, _):
    return render(request, "core/ME/hotsite.html", {})

The captured value is never used. The fragility is the signature: anyone cleaning up the URL (dropping the capture, converting to (?:me|ME), switching to path(...), or reusing me_hotsite from a pattern without capture) immediately breaks the view with TypeError: me_hotsite() missing 1 required positional argument: '_'. The two sides are coupled for no functional reason.

Fix

• urls.py: capture → non-capturing group (?:me|ME).
• static_views.py: drop the unused second arg from the view signature.

# urls.py
re_path(r"^(?:me|ME)\/?$", me_hotsite, name="mitologia-extendida"),

# static_views.py
def me_hotsite(request):
    return render(request, "core/ME/hotsite.html", {})

Both /me/ and /ME/ continue to match and render the same page. The captured string was never consulted, so no behaviour changes.

Fixes #851

[vjpixel]

Review

Verdict: ✅ Correct fix.

(?:me|ME) is a non-capturing group, so Django no longer passes the matched casing as a positional arg, and the view signature drops the unused _. Verified via Django shell that resolve('/me'), resolve('/me/'), resolve('/ME/') all land on me_hotsite with empty args/kwargs.

Duplicate: Same fix in #928.

---

Generated by Claude Code