The Byte-Level Ledger of 1,003 Chapters: When an Overwrite Copy Met an Incremental Backfill, and a Converter Bit Its Own Tail

“Not one character of content may be touched” — in content engineering that order carries the weight of an architect saying “the load-bearing wall is off limits”. And this time the trouble was that nobody knew exactly what had happened when those 250 chapters were copied in.

I. An Overwrite Copy? In Fact an Incremental Backfill

The owner copied 250 chapters back over the original paths and asked first whether each matched its source novel. A per-chapter byte hash comparison of copy against 英文小说\ source — not a sample, per chapter — produced a mildly surprising result: 1,003 chapters, 100 percent identical, zero cross-book contamination. That is, what was nominally an overwrite copy was in fact an incremental backfill: new chapters went in, old chapters untouched.

The ledger came out like this:

Book	Copy now	Added this pass	Source produced (not in copy)
穿越1	250 ch / 536,795 words	+20 (231-250)	315 ch
规则世界1	250 ch / 517,527 words	+1 (250)	322 ch
末日带系统1	250 ch / 714,102 words	+48 (203-250)	272 ch
修仙1	253 ch / 479,875 words	untouched	345 ch

A fact nobody had noticed surfaced: roughly three hundred chapters of source stock have not entered the copy. 修仙1’s manuscript has reached 345 chapters while the copy holds 253; 穿越1 has reached 315 with 250 in the copy. The pipeline produces far faster than the shelf fills — good news in one light (backlog depth far exceeds what the release rhythm needs), and a reminder in another: incremental sync between copy and source must become a routine from now on.

II. Full Reconversion: Idempotence Is the Floor

All three books were reconverted in full with the same md_to_html.py from yesterday, command md_to_html.py 1 250. Idempotence is the floor — the same source, converted a hundred times, yields the same artifact, with no second-run accidents.

The summaries fallback path was rechecked too: 规则世界 goes to 英文小说\规则世界, no misspelling. Only one new fallback-title chapter appeared (末日1 ch 233), the rest identical to last time. Source files untouched — only html\ artifacts and manifests were written; the original directory’s modification times did not even change.

III. Three Verifications, 750/750 Green

Consistency: import the converter itself, recompute expected HTML from current sources, and compare line by line against the artifacts on disk — 750 chapters, zero difference. This is far stricter than “run it and see if it errors”: it confirms the HTML on disk is a faithful product of this batch of sources, with no chapter-order drift. Not “it runs” but “it is right”.

Asterisk leakage: strip tags and scan the whole body for bare * — zero leakage. This is the real mine in the RR paste scenario — yesterday’s 修仙1 ch 55 cross-line italic fault is exactly what readers see as a screen full of asterisks. Zero here means yesterday’s fix holds at full scale.

Bite force: inject a tamper deliberately and confirm it is always caught. This verifies the verifier — a checker that cannot catch tampering is more dangerous than no checker.

IV. A Self-Inflicted Accident

One incident mid-run is worth recording: a single-chapter trial run overwrote 规则世界1’s manifest into a single line. It was restored to 250 lines by a full reconversion.

The lesson is not “be careful next time” but trial runs must not touch production artifacts. A full reconversion could repair it only because the converter is idempotent — the same source, rerun once, returns to the single correct terminal state. Which says, in reverse, how decisive it was that yesterday’s converter was written idempotently: otherwise this one slip would have meant manually rebuilding 250 manifest lines.

V. Ready to Ship

Three verifications green means this batch of HTML can go straight to Patreon. And per yesterday’s field manual, every upload action is performed manually by the owner — the agent only prepares material to the point where copy-paste suffices, touching not one platform operation.

From 934 chapters to 1,003, from first-chapter approval to the backlog mirror, this pipeline is laying the road between “written” and “sellable” into reusable track, one section at a time.