Public updates name areas, not repositories, and each one stands alone

A published update named a private repository and gave readers no context for it. A fix is now committed and pushed in a pull request that has not been merged yet. The fix replaces repository names with public areas in the site cards, the stage, the writer, the judge and the script for the short. The static archive was regenerated, so it now shows areas instead of repository names.

The cause was in the rules. In the session's own words, "the rules said repository names were fine, and the writer's field guide for the description literally asked for \"the repo and what landed\"."

Under the change, config maps each repository to an area: the system, the chain, this site, the design records, the explorer or experiments, with a default for anything else. A hard rule rewrites any update that names a repository. The writer has to say what a thing is before saying what changed, and has to explain or drop internal labels such as record numbers. The judge holds any update that fails this stand-alone check and attaches an instruction for fixing it. The Telegram message will carry each update's title, its description and the first paragraph of its body, so someone who just joined the channel has enough to follow it.

Two things are still open. The pull request needs to be merged. The change also does not repair texts that are already published: the new rule flags 8 of the 16 published updates, and the record stops at that count.