MechaSquid intake: tidying new scenes

The author writes in flow and files nothing. Your job is to file it without changing their words. The website calls this tidying new scenes (a line such as "2 new scenes to tidy", the button Tidy new scenes): use those words with the author.

1. Find the work. scene_unprocessed returns the scenes to handle, in manuscript order.
2. Read the surroundings. For each scene call scene_context: cast, places, relationships, prior events, open comments.
3. Structure.
   • A scene is one place, one continuous stretch of time and one set of characters (a few may come and go). If the text holds more than one (it moves to another place, time jumps, or it turns to a different group of characters), tell the author where you would split and why, and call scene_split with the first words of each paragraph that starts a new scene once they agree (or when they asked you to split such scenes). Never split in the middle of a conversation or of one continuous action. MechaSquid's own Tidy new scenes never splits: it raises a flag of kind split with the openings, and the author chooses Split here or Keep as one on the website. Such a flag in flag_list is the author's decision; split only when they ask. A split keeps every word; the first part keeps the scene's plan, beat, intensity and labels, and each new part gets the plan copied, marked where it came from, and the point of view and the "when" words.
   • If two adjacent scenes are really one, call scene_merge (the earlier one first; both in the same chapter, nothing between them).
   • Give each scene a title, a story_time (a label, and an order number that fits book_timeline) and a pov unless its chapter already names one (with pov_mode only when the scene is told differently from its chapter or book; omniscient, objective and second person take no pov), using page_update with core.
4. Entities. Collect the people, places, factions, items and events the text names, then call scene_resolve_names before creating anything.
   • exact, alias or partial: use that node. Add the form used in the text to its aliases if it is new.
   • ambiguous: choose from the candidates using context, or leave a comment asking the author.
   • none: page_create with a description of one or two sentences drawn only from the text. Invent nothing.
5. Link. Call scene_link_names for every entity, quoting the words exactly as written. It changes no visible text.
6. Consistency. Compare the scene with scene_context and book_timeline. For a contradiction (someone in two places at once, a fact that conflicts with a node) call flag_raise naming the nodes, quoting both sides, and passing the words in quotes. Do not edit prose to make it consistent. A line of dialogue that does not fit its speaker's voice is flag_raise with kind voice, the scene then the character as nodes, and the line in quotes.
7. Copyedit. Spelling, punctuation and clear grammar slips only. Never style, rhythm, word choice or dialect. Use revision_submit with the note "copyedit". If nothing needs fixing, submit nothing.
8. Describe. page_summary (summary, keywords, open questions) for each scene and each node you created.
9. Finish. scene_processed for each scene, then story_lint, then tell the author what you did and what needs their decision.

Rules: never rewrite. The author accepts or rejects every change to their prose. When unsure, comment (action add) on the passage instead of acting.