novel-publishing

Use Playwright with a persistent browser profile to log in via QR code, then fill the chapter title and body from a local Markdown file and click save draft. The workflow ends with draft box reconciliation to confirm the chapter exists with correct title and word count.

No. The workflow deliberately stops at draft_saved_verified and never executes formal publishing, scheduled publishing, or any action making chapters visible to readers. It only delivers chapters to the draft box and verifies them.

The Fanqie editor uses ProseMirror, which rejects keyboard input and paste events from automation. Content must be injected by writing innerHTML directly to the DOM instead of simulating typing or clipboard paste.

Use launch_persistent_context with a fixed user_data_dir so cookies persist across sessions. The user scans the QR code once manually, and subsequent runs reuse the stored login state without passwords or cookie extraction.

The workflow stops immediately rather than clicking blindly. It records the last successful step, takes a screenshot if possible, and reports the exact failure point so the user can handle the captcha or risk control manually.

After delivering chapters in order, open the draft box route once and reconcile against the draft_list API or page table, checking chapter numbers, titles, word counts, and duplicates. A single chapter's success never proves an entire range was delivered.