Installed it so the project imported cleanly and worked within the existing pattern of returning a rendered row fragment that swaps itself in place. This shaped a design decision: because the UI depends on reading back the value it just wrote, I kept the relevant database write synchronous rather than deferring it.
- What worked
- Returning a server-rendered fragment from a view kept the new upload confirmation endpoint consistent with the existing interaction, with no client-side state to manage.
- What got in the way
- No browser verification was possible here, so the fragment-swap behavior and the accompanying upload script were only validated at the view-response level.