Publishing the wiki

The loop (3 passages, no note) that keeps this wiki alive: a change in the glossary (28 passages, no note) or in the specifications (15 passages, no note) is linted where it is written, then the configuration repository (note: Configuration repository) rebuilds the site (3 passages, no note) of the three repositories (note: Knowledge repository) and publishes (16 passages, no note) it. Nothing is copied from one repository to another and nothing is written into a content repository. Until the first release (note: Release) of the tool, every workflow (9 passages, no note) builds (note: Build) the command (21 passages, no note) line from a checkout (3 passages, no note) of the tool's repository, the interim form (52 passages, no note) of the pipelines the guide gives with the published package (23 passages, no note).

1. An author (note: Author) pushes a note (note: Note) to the main branch (6 passages, no note) of the glossary or of the specifications, after the lint of the merge (27 passages, no note) request (31 passages, no note).
2. The lint workflow of that repository runs the linter again on the main branch and stops there on an error finding (4 passages, no note).
3. When the lint is green and the repository holds the dispatch (6 passages, no note) token, the workflow sends a content-updated dispatch to the configuration repository; without the token it stops, and the nightly schedule or a manual dispatch takes over.
4. The wiki workflow of the configuration repository starts, on that dispatch, on a push to its own main branch, on its schedule or by hand: it checks (note: Check) out the configuration (note: Configuration), builds the command line, validates the configuration (3 passages, no note) and runs the build, which clones the two content repositories at their main ref (4 passages, no note) at depth 1 (3 passages, no note).
5. The build writes the site (note: Site), the model and the build log; an error finding fails the workflow as build.fail_on says and nothing is published.
6. The site is uploaded as the Pages artifact and deployed; the published site names the commit (29 passages, no note) of every source (note: Source) in the build block of its model (note: Model).
7. The repository of the tool verifies (6 passages, no note) on every change that the wiki still covers it: every check has a rule note (note: Rule), every page slot (note: Slot) a screen note (note: Screen), every active (4 passages, no note) type (note: Type) a note, every configuration key (46 passages, no note) and check family (note: Check family) a glossary term (note: Term).