Regenerate the doc pages — two of them had drifted (relay#46) #114

2026-09-04T22:39:14Z

paulhitt commented

2026-09-04 22:39:14 +00:00

(Migrated from gitlab.com)

spec.leaf carries the §6.15 correction now merged in flamenet-e2e:
Android records a mid for every line and applies inbound edits, so the
paragraph claiming it "cannot yet apply one" — and that replies and
reactions were blocked with it — is gone, replaced with what a run
proved.

And api.leaf was stale too, which I did not go looking for. The
range-request documentation from relay#37 landed in docs/API.md this
morning and was deployed without the generated page being rebuilt, so
/api has been missing Accept-Ranges, the three Range forms and the
206/416 answers all day. Exactly the drift relay#45 is about, found by
regenerating rather than by reading.

Both pages are generated and stamped with the sha256 of their source, so
the stamp is what makes drift detectable at all —
Scripts/check-doc-pages.py now reports all 9 pages matching.

Order matters here and is easy to get wrong: the spec page is stamped
against flamenet-e2e's DEFAULT branch, so the SPEC.md change had to be
merged there first or the regenerated page would stamp against something
CI cannot see.

659 tests pass.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

`spec.leaf` carries the §6.15 correction now merged in flamenet-e2e: Android records a `mid` for every line and applies inbound edits, so the paragraph claiming it "cannot yet apply one" — and that replies and reactions were blocked with it — is gone, replaced with what a run proved. **And `api.leaf` was stale too**, which I did not go looking for. The range-request documentation from relay#37 landed in `docs/API.md` this morning and was deployed without the generated page being rebuilt, so `/api` has been missing `Accept-Ranges`, the three `Range` forms and the 206/416 answers all day. Exactly the drift relay#45 is about, found by regenerating rather than by reading. Both pages are generated and stamped with the sha256 of their source, so the stamp is what makes drift detectable at all — `Scripts/check-doc-pages.py` now reports all 9 pages matching. Order matters here and is easy to get wrong: the spec page is stamped against flamenet-e2e's DEFAULT branch, so the SPEC.md change had to be merged there first or the regenerated page would stamp against something CI cannot see. 659 tests pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

paulhitt commented

2026-09-04 22:39:15 +00:00

(Migrated from gitlab.com)

assigned to @paulhitt

paulhitt commented

2026-09-04 22:39:20 +00:00

(Migrated from gitlab.com)

mentioned in commit 102df905f6

mentioned in commit 102df905f680a7ed899df823bb153987e805ea59

paulhitt (Migrated from gitlab.com) merged commit 102df905f6 into main

2026-09-04 22:39:20 +00:00

paulhitt commented

2026-09-09 18:58:59 +00:00

(Migrated from gitlab.com)

changed the description

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: extant2000/flamenet-relay#114