2026-10-03 (9): the public site rebuilt and checked
What this cycle did
This was the first cycle of the run that started at 08:43 UTC on 3 October 2026. A run is one scheduled session of work; it is split into up to four cycles, each of which does one job, records it, and merges its own pull request (a proposed change to the main copy of the repository) before the next begins.
A small program called the selector (tools/next_mode.py) chooses each cycle's job by weighing how long it has been since each kind of work was last done. This time it chose site: rebuild the public website from the dictionary's entries and test it. The site had last been built and checked on 30 September, and in the three days since then about a hundred new entries have been written and many more revised, so the check was due. The selector's other signals: 1,099 entries, all reviewed and none waiting in draft; 414 entries that have had only one round of review by the outside reviewer models; 4,955 words waiting in the queue; US$2.91 spent today out of the US$15 daily cap. A site cycle makes no paid calls.
What was built
The site builder (tools/build_site.py) turned the 1,099 entry files into 1,018 headword pages. There are fewer pages than entries because words spelled the same but with different parts of speech share one page: dream the noun and dream the verb appear together. No entries were held back as drafts and there are no redirects (pages for renamed words). In all 2,276 files were written to the docs/ folder. That folder is never saved to the repository; the published copy is built separately by GitHub's automation each time a change is merged.
What was checked
The site checker (tools/site_check.py) opens the built pages in a real browser at phone width (360 pixels) and at desktop width, and tests what a reader would do. All 54 checks passed. In plain terms:
- the home page and three entry pages load without script errors and without any sideways scrolling on a phone;
- typing ran into the search box finds run first, and pressing Enter opens it;
- tapping a linked word in a definition (on a phone) or hovering over it (on a desktop) shows a short preview of that word's meaning, and a second tap follows the link;
- the "translator's view", a switch that shows notes written for translators and teachers, opens and closes, and remembers its setting after the page is reloaded;
- dark mode shows light text on a dark background.
The checker always looks at the same few pages near the start of the alphabet. As an extra check by hand, I looked at five pages written or revised in the last day (economy, dream, disease, bubble, shock) for formatting marks that should have been turned into bold or italic type but were left showing as raw asterisks. There were none, and no page on the site has them.
What did not work
Nothing failed. No tool was changed, and no entry was changed.
What is next
The next cycle starts straight after this one merges, if the run's clock allows, and the selector will choose its job afresh. Building new entries is the most likely; the queue's next band 1 nouns follow economy. A routine lint pass (the periodic consistency check across the whole dictionary) is due within one or two cycles.
What needs the owner
Nothing new from this cycle. The standing questions remain as listed in NEXT.md: whether to switch off three reviewer issue families whose precision has fallen below the 30 percent line (the automatic switch-off was refused by a safety check, so they wait for a ruling), and the open questions in wiki/open-questions.md, chiefly 4 to 7 (splitting be/have/do/one by part of speech, the look of the inline marks, an entry for infinitive to, and proper names in definitions).