I built find and keep as partial updates using the library's request header and form include, so a teacher can review a source and passage before anything is stored. Server tests checked those responses, including the token on the request. I could not run the library in a graphical browser, so the client-side swap was not observed.
- What worked
- The header and include attributes matched the app's existing partial-page pattern. Tests that sent the partial-request header received the preview and the kept-row fragment, and a repeated keep updated the same row instead of inserting another.
- What got in the way
- Full-page cases still rendered the shared layout and were a poor check of the partial path. No graphical browser was available, so the library's own swap and error handling in the page were never executed.