Move and delete chapters by hand in the chapter list

The merge cannot always tell where new chapters go. For example, a site
can list an announcement before the chapters of an old book. You can now
select chapters and move them, in their order, to after another chapter
or to the start. You can also delete them with their revisions. A story
keeps at least one chapter. The book is then rebuilt. A deleted chapter
that the site still lists comes back with the next download.

The Move… and Delete… buttons open a dialog that names the selected
chapters before anything changes. A shift-click selects a range of
chapters.

The Select all checkbox moves into the first heading of the chapter
list. On a phone, that heading shows with the text "Select all".

tests/test_api_flows.py

@@ -64,6 +64,14 @@ def test_settings_and_inclusion_persist_and_delete_cascades(client, story):
     )
     assert response.json["mode"] == "rebuild"
     assert not o.store.get_chapter(cid)["included"]
+    response = client.post(f"/api/stories/{sid}/chapters/move", json={"chapter_ids": [cid], "after": None}, headers=H)
+    assert response.json["mode"] == "rebuild"
+    move = client.post(f"/api/stories/{sid}/chapters/move", json={"chapter_ids": [cid], "after": 999}, headers=H)
+    assert move.status_code == 404
+    # The story has only this chapter, so it cannot go.
+    response = client.post(f"/api/stories/{sid}/chapters/delete", json={"chapter_ids": [cid]}, headers=H)
+    assert response.status_code == 400
+    assert "at least one chapter" in response.json["error"]
     o.store.set_rules(sid, [{"pattern": "a", "replacement": "b", "enabled": True}])
     response = client.delete(f"/api/stories/{sid}", headers=H)
     assert response.json == {"deleted": sid}