Nice fix, @shoummu1! Great root cause analysis — the existing htmx:afterRequest handler was already the right mechanism, and the old code was just bypassing it by swapping inline HTML directly. Removing the duplicated server-side HTML generation (-40 lines) in favor of the full refresh via initializeTeamManagement() is the right call. Clean and minimal. LGTM!

Code Review

Verdict: Correct and well-designed

Flow analysis:

1. Form submits POST to /admin/teams
2. Backend creates team, returns HTMLResponse(content="", status_code=201)
3. HTMX swaps empty content into #create-team-error (clears any prior errors)
4. Global htmx:afterRequest handler (admin.html:14756) catches status === 201 + elt.id === 'create-team-form'
5. Calls closeCreateTeamModal() (hides modal + resets form)
6. Calls initializeTeamManagement() (fetches /teams/partial and re-renders entire list)

Consistency: This pattern is consistent with how delete, leave, and cancel-join work (lines 14662-14680) — they all call initializeTeamManagement() after completion. The other team operations (edit, add/remove members) use the adminTeamAction HX-Trigger event system, but those are more complex operations with success HTML feedback. Using the afterRequest listener for create is simpler and appropriate.

Error handling: Error paths (validation, integrity, generic) all properly use HX-Retarget="#create-team-error" + HX-Reswap="innerHTML", which is now redundant (form already targets that div), but harmless and defensive.

No issues found

• Security: No issues. Removes 30+ lines of server-side HTML generation (which had html.escape but was still a risk surface). The new approach delegates rendering entirely to Jinja templates via teams_partial.html.
• Performance: Slightly better — one fewer response payload (empty vs. HTML blob). The full list refresh is the same cost as before (since the old code never triggered it properly).
• Logic: Correct. The afterRequest check for status === 201 is precise enough since only successful creation returns 201.
• Test: Updated correctly — asserts empty body and 201 status.

Minor observation (not a blocker)

The removed code previously triggered resetTeamCreateForm via the adminTeamAction HX-Trigger header. The resetTeamCreateForm() function still exists in admin.js (line 21294) and is still referenced in handleAdminTeamAction (line 21852). It's not dead code — other parts of the system could still trigger adminTeamAction with resetTeamCreateForm: true — but since team creation no longer sends that trigger, you may want to clean it up in a follow-up if nothing else uses it.

Net change: +5 / -40 lines — a good simplification.