Amy J. Ko

We need to automatically release the lease if it hasn't been renewed in a while to avoid stale locks.

We currently just say _that_ a chapter is locked, but not who has the lock or why input is ignored. This was a rush job and we need to finish...

All errors produced by Firebase interactions are swallowed by the book save status widget. Need to improve the clarity of the messages and make them available in the status UI.

There needs to be some way for site admins to see all books to support troubleshooting and feedback. This is currently locked down by firebase rules. Add an `admin` user...

I've only written a few lazy tests. Let's get 100% coverage.

For a reader bingeing the book, they'd have to use the navigation menu at the top left to go to the next chapter. It's quite far from the last word...

There's currently no testing infrastructure, which is a big risk.

Need a repeatable way to test across common browsers.

The code `\`applications_file\`` produces the error `Error: Unclosed \`Error: Unclosed _Error: Unclosed \`` I think the issue is that there are two unclosed formatting symbols, but it's not clear there...

Google's not likely to go down, but this may be more performant as it results in fewer requests.