Probe why a cover title typed on a new book can fail to reach the collection

[andrew-polk]

Problem

Three nightlies have now lost a cover title. A title typed on the cover of a brand-new book is missing from the saved book, so the collection never learns it and Bloom never renames the folder to match — import-recording hit it on 5 September, and bulk-upload-quick-test has died on it on 10 and 11 September, which is why that test is red every night. On the runner it is close to deterministic; on a developer machine it has never once reproduced (twelve attempts, including with the WebView renderer throttled), so nobody can say whether Bloom is dropping an edit or our own typing is not enough like a person's.

What this PR does

It adds no fix. It adds the two instruments that should settle the question from a single nightly run, and writes down what is known so far.

• cover-title-save.spec.ts makes the same book three times, typing the title a different way each time — today's insertText, real key presses, and insertText followed by an explicit blur — and reports for each what the box held just before the save and whether the collection learned the title.
• typeInGroup gains an optional typing-method argument for that. It defaults to today's behavior, so no existing test changes.
• EditingModel logs the bookTitle it finds in the page content the browser sends back for a save, and only for pages that have one. That splits the timeline again: it says whether the text was already gone before Bloom saw it, or was lost after.
• AUTOMATION-DEBT.md records what this investigation established — only the cover title is lost while everything typed after it saves; the log signature is a missing Renaming folder line after InsertTemplatePage — and what each probe outcome would mean. A separate entry notes that a dropped page-thumbnail click is the same already-listed gap.

Read the probe from a nightly; locally all three variants pass. Both instruments are meant to be deleted once the question is settled.

🤖 Generated with Claude Code

Devin review

---

This change is 

[andrew-polk]

[Claude Opus 5 (1M context)] Consulted Devin on 2026-09-11 21:40 UTC up to commit 5eb4b2a63d8f73375f1366f3eb12a25bf8fdb961.

No Bugs and no Informational items. One Investigate flag, mirrored as a review thread and left open for the developer: the probe exercises only the Test branding, so a branding-specific difference could survive the experiment. That is a design question about the experiment rather than a defect, so it is not being decided here.

The local review (a read-only sub-agent over the diff) found two real problems in the probe, both fixed in 5eb4b2a63d: the pre-save read was clicking the title box back into focus, which silently undid the blur variant, and a bare catch was recording a dead Bloom as a lost title. The full C# suite is green (3442 passed) and the probe passes locally, all three variants.