Yezur Wiki:Daily routine/Report
Working report of the Alompan daily routine (how it works). Every finding lives as one row below until it is resolved: set a row's Status to give a verdict, and the next run carries it out and clears the row. Nothing on the wiki is changed except what is explicitly approved or amended.
The possible statuses:
pending— awaiting review; no action is taken (the default)approvedoraccepted— carry out the Suggested fix, as writtenamended— carry out the fix described in Notes insteaddeferred— real, but not now; moves to Dismissed flags and is not re-flaggedrejected— not an issue; moves to Dismissed flags and is not re-flaggedto to-do— real issue that should be marked on User talk:Yezur's to-do list instead for human interventionfixed— real issue, but was a simple fix for Yezur, or has by other means already been taken care of; confirm and clear
To revive a dismissed flag, move it back into the table as pending.
Flagged items
| # | Flagged | Type | Severity | Page(s) | Issue | Suggested fix | Status | Notes |
|---|---|---|---|---|---|---|---|---|
| 47 | 2026-07-26 | structural | medium | MediaWiki:Sidebar, Yezur Wiki:Main Page, Yezur Wiki:Conventions | Two namespaces are documented as part of the wiki's structure and have never held a single page. Meta: — namespace 4, this wiki's project namespace — is named as live out-of-frame space in six places across three pages. Yezur Wiki:Conventions gives it a row of its own in the §Namespaces table ("Meta: — Out-of-frame — Design notes and rationale"), names it in §Where out-of-frame content goes ("It belongs on Talk pages, in the Meta: namespace, or in this Yezur Wiki: namespace"), and names it again in the same section's rule of thumb ("except the Meta:, Talk:, and Yezur Wiki: namespaces"). Yezur Wiki:Main Page lists it first under §Behind the scenes as "about the Yezur project itself; the place for Earth comparisons and design notes" and repeats it under §Conventions. And MediaWiki:Sidebar gives it a permanent navigation slot on every page of the wiki, as Project docs → Special:PrefixIndex/Meta:. But Meta: and Meta talk: hold 0 pages, and list=allrevisions returns nothing for either — no page has ever existed in them, so the sidebar link every reader sees leads to an empty index. The same is true of Help:, which Yezur Wiki:Main Page lists as the third out-of-frame namespace ("how-to guidance for editors") and which Yezur Wiki:Conventions's table omits entirely: also 0 pages, also no revision ever. Everything the two are described as holding is in fact on Talk pages and in the six-page Yezur Wiki: namespace. |
A decision, then mechanical edits. Say whether Meta: is still wanted as a namespace distinct from Yezur Wiki:. (a) If it is retired — the reading that fits what has actually been built, since every out-of-frame page written so far has gone to Yezur Wiki: or to a Talk page — then drop its row from the §Namespaces table, drop it from the two sentences in §Where out-of-frame content goes and the rule of thumb, drop the §Behind the scenes bullet and the §Conventions mention, and repoint the sidebar's Project docs link at Special:PrefixIndex/Yezur Wiki:, where the six project pages actually are. (b) If it is still wanted, it needs at least one page so the sidebar link is not a dead end, and the two project pages should be made to agree on what belongs there rather than in Yezur Wiki:. Either way the Help: mismatch wants settling in the same pass, since the two project pages disagree about whether it is part of the scheme at all. One caveat on scope: the sidebar sits in the MediaWiki: namespace, which needs the editinterface right — queried directly this run, Alompan does not hold it — so that one line needs an administrator even once approved. The two project pages the routine can do itself. |
pending | New 2026-07-26, from the first full read of the Module, Talk, User, MediaWiki and project namespaces. Same species as #45 — documentation that was never followed through — but load-bearing in a way #45 is not: this is the only navigation link on the wiki that leads somewhere empty, and it is on every page. Recorded as not a finding beside it: Yezur Wiki talk:, Dictionary talk: and Map talk: are empty too, but no page claims otherwise, and a talk namespace fills itself when there is something to discuss.
Re-confirmed 2026-07-28: |
| 50 | 2026-07-26 | structural | low | Module:Auphen | An unreachable branch in the affix path, and an else-clause form that is silently dropped along with it. In Engine:handle_affix, the change slot is handled by two branches — one for a change containing #, and one for an empty change carrying only an @-index or span, which is what a pure indexed operation parses to, since the index-stripping helper removes the @n and leaves the change empty. The else slot copies that same two-branch shape, but wraps it in if ELS ~= then — so its second branch tests ELS == inside a block that has already required ELS ~= , and can never run. The same guard also skips the else clause's affix_prep call a few lines earlier. The consequence is not only dead code: an affix rule whose else clause is an @-index alone falls through both guards, the else never applies, and the rule returns the word unchanged with no warning — where the identical form in the change slot works. It is the same class of defect the talk page records as already fixed: D1 reads "the ELS @-index is parsed and used as a fallback instance filter (the JS assigned it to the CHG index, so ELS indices were dead)" — and in the affix path they are still dead. |
flag-only. This is a change to a live rule engine with an off-wiki test suite behind it, and the routine will not edit module code on the strength of its own reading. The shape of the fix is plain — hoist the ELS ~= guard so the index-only case reaches affix_prep and apply_affix_logic, mirroring the change slot exactly — but it wants a proving test case in that suite first, and the module is Khurouan's. Raised so it is recorded rather than found again later. Worth settling one question before any code moves: whether an index-only else clause on an affix rule is a form the rule notation actually admits. If it is not, the right fix is the opposite one — delete the dead branch and say in a comment why the else slot needs only the # case. |
pending | New 2026-07-26, from the first full read of Module:Auphen — at 38 KB the largest page on the wiki outside this report. The only code defect the sweep found: the UTF-8 codepoint layer, the case tables, the escape layer, the category-explosion guard (opts.explodeCap, default 5,000,000, exactly as the talk page states) and the IPA transposition all check out against their documented behaviour, as do the two data pages' category sets.
Re-checked 2026-07-28, unchanged. Re-checked 2026-07-30, unchanged — Module:Auphen's last revision is still that of 2026-07-18. Re-checked 2026-07-31, unchanged — Module:Auphen's last revision is still that of 2026-07-18. |
| 51 | 2026-07-26 | naming | low | Yezur Wiki:Conventions, Category:Countries | The worked example for place-qualified category names matches neither the wiki's categories nor the same page's own next paragraph. Yezur Wiki:Conventions gives the form twice as "Polities of Andusia" — in §Categories ("a country in Andusia sits in a 'Polities of Andusia' category that is a child of both 'Andusia' and 'Polities'") and again in §Naming ("Keep narrower place qualifiers, such as 'Polities of Andusia'"). Two paragraphs after the first, the same section writes "Former countries in Andusia". Every place-qualified category that exists uses in, and none uses polities: Category:Cities in Hertia and Category:Ancient cities in Hertia, beside Category:Countries and Category:Former countries. The split runs deeper than the connector. The category side of the wiki says country — Category:Countries, one member, Engil — while the template and Cargo side says polity: Template:Infobox polity declaring and storing into the Polities table. Only Template:Infobox former country and Category:Former countries agree with each other across the divide. | Two parts, one mechanical and one a decision. (a) The connector is settled both by practice and by this page's own later sentence: make both worked examples read "in". Mechanical. (b) Whether the house word is country or polity is yours to say — and it is cheap now: Category:Countries holds one page and the Polities table holds none, so nothing has to be moved either way. If country wins, the examples become "Countries in Andusia" and Template:Infobox polity is the odd name out; if polity wins, Category:Countries wants renaming to match, and the routine holds the move right so it could do that on approval. Leaving both words in use is defensible too — but then the examples on the convention page should at least use a form that exists somewhere. |
pending | New 2026-07-26, from re-reading Yezur Wiki:Conventions in full beside all 24 category pages. Third row touching §Naming, with #28 and #45(a) — if more than one is approved, make them in one edit. Recorded as not a finding: neither Category:Andusia nor Category:Polities exists, though the worked example implies both — those are categories not built yet rather than an inconsistency, and the same page asks that new categories be cleared with the operator first. (Named in italics rather than linked, so this report does not itself create two more wanted categories.)
Re-checked 2026-07-28. Now the only open row touching §Naming — #28 and #45(a) were carried out this run, so part (a) here is a standalone one-line edit whenever you want it. The section is otherwise unchanged by those edits: #45(a) removed the retired Family A bullet and touched nothing else, and both "Polities of Andusia" wordings are still live, in §Categories and §Naming. Part (b) is cheaper than when filed: Category:Countries still holds one page and Polities still holds 0 rows. Re-checked 2026-07-30, unchanged: both "Polities of Andusia" wordings are still live, in §Categories and §Naming, and Category:Countries still holds one page. Part (b) is cheaper again than when last checked: the Polities Cargo table no longer exists at all, so nothing on the wiki stores the word polity except Template:Infobox polity's own name and documentation — and that template is now transcluded by no page, so whichever word wins, nothing has to be migrated. Re-checked 2026-07-31, unchanged: Yezur Wiki:Conventions was not edited this window, both "Polities of Andusia" wordings are still live, Category:Countries still holds one page, and Template:Infobox polity is still transcluded by no page at all. |
| 52 | 2026-07-26 | factual | low | Yezur Wiki:Conventions, Template:On the map | The convention set's list of map templates omits the one that articles actually use, and lists four that none do. Yezur Wiki:Conventions §Maps reads, in full: "Link to the Yezur map with {{Node}}, {{Way}}, and {{Relation}} (by object id), or {{Coords}} / {{Coordslink}} (by coordinates)." All five exist, and the transclusion counts show how they are used: {{Node}} by seven articles, and {{Way}}, {{Relation}}, {{Coords}} and {{Coordslink}} by no page at all. Meanwhile Template:On the map is not mentioned, though it is in use on Alompe and is the only one of the six that behaves structurally differently: it renders through MediaWiki's page-status-indicator mechanism, placing a 🌐 On the map link beside the page title rather than inline. Its own documentation carries two rules that are recorded nowhere else — "by convention, put it on the first line of the article", and "If the template appears more than once on a page, the last use wins" — and it states its own scope: points on the map, "not continents or countries, which cannot be reduced to a single point". |
Add one bullet to §Maps, restating only what Template:On the map's own usage note already says: that a subject resolving to a single point on the map takes {{On the map|lat|lon}} on its first line, which places a title-side indicator rather than an inline link and takes effect once per page; and that continents and countries, which cannot be reduced to a point, do not take it. Nothing new is asserted. Mechanical. The four unused templates are not proposed for removal — a documented template awaiting its first use is not a defect. |
pending | New 2026-07-26, from reading all 25 templates against the convention set. If #28, #45 or #51 are approved this can go into the same edit to Yezur Wiki:Conventions, though it falls in §Maps rather than §Naming. Related but deliberately not flagged: Talk:Alompe records that article's map node id (60111) as an open thread "until a settlement infobox exists to hold it" — a new infobox is a decision the convention set reserves to the operator, so the note is left where it is.
Re-checked 2026-07-28, unchanged; §Maps still lists the five and omits Template:On the map, whose transclusion count rose from one page to one page (Alompe only). Both edits to Yezur Wiki:Conventions this run fell in other sections, so this remains a single clean bullet insertion. Re-checked 2026-07-30, unchanged; §Maps still lists the same five templates and still omits Template:On the map, whose transclusion count is still one article (Alompe). The 2026-07-30 edit to Yezur Wiki:Conventions fell in other sections, so this remains a single clean bullet insertion. Re-checked 2026-07-31, unchanged; §Maps still lists the same five templates and still omits Template:On the map, whose transclusion count is still one article (Alompe). |
| 53 | 2026-07-27 | structural | medium |  , Tacchoan |
The wiki's first image carries an out-of-frame attribution strip, and its colour key cannot distinguish two of the four branches it exists to distinguish. The file was uploaded on 2026-07-27 and placed in Tacchoan §Members; it is a 1283×785 map export, and both defects were read out of the pixels rather than inferred. (a) The attribution strip. A pale bar carrying the mapping software's "© OpenStreetMap contributors" credit is baked into the saved image at its bottom-right corner — rows 778–784 across columns 1159–1283, so the frame's own bottom edge cuts the line of text in half. It renders at full size in the article, where Yezur Wiki:Conventions §Namespaces holds that "everything a reader or editor sees is in-character". It is the most reader-visible break of frame currently on the wiki, and the only one that is not text. (b) The colour key. The caption assigns yellow twice — "yellow for the Kipoa languages, and a small yellow area to denote the Usy language" — and the image bears this out: two separate yellow fields, an eastern strip and a southern island, in the same hue. A reader cannot tell which is which, on a map whose whole purpose is to separate the four branches. Purple (north), green (centre) and the two yellows do match the four bullets' stated geography, and red does sit off to the southwest, away from Taccho. | Three parts, and only the third is mechanical. (a) is flag-only: a corrected export is the map's business, not the routine's, and a straight crop of the bottom seven pixels is not a safe substitute — mapped land reaches the bottom edge across the left of the frame (77–108 non-sea pixels in every one of rows 778–784), so cropping would clip the southwestern island chain. There is also a question the routine cannot answer: whether any of the framed data is OpenStreetMap-sourced, in which case the credit is a licence condition and must be re-placed rather than removed. (b) is likewise flag-only — giving Usy its own colour needs a new export. (c) is mechanical and can be done without touching the file: the caption opens on "Red is referring to the Herta-Olaic family" without saying that Herta-Olaic is not a Tacchoan branch at all but the neighbouring family, shown for contrast; one clause fixes that, asserting nothing that Herta-Olaic and Taccho do not already say. | pending | New 2026-07-27. Verified against the file itself, not the caption: the strip's extent was measured, and the two yellow fields confirmed as the same hue. #54 covers the description page rather than the image. If (c) is approved it can go into the same edit as #55, #56 and the mechanical half of #57, which all touch the same six lines of Tacchoan.
Re-checked 2026-07-28, unchanged.
Re-checked 2026-07-30, unchanged.
Re-checked 2026-07-31, unchanged — |
| 54 | 2026-07-27 | structural | medium | Yezur Wiki:Conventions, |
The wiki now holds files, and has no conventions for them. Until 2026-07-27 the site statistics read images 0, and the last report recorded the unused-images check as clean on the grounds that "the wiki holds no files at all". That is no longer true: there is one file, and nothing governs it. Yezur Wiki:Conventions has no §Files — its eleven sections cover voice, namespaces, naming, formatting, categories, infoboxes, open threads, maintenance, maps and sourcing, and say nothing about what a file description page carries, whether files are categorised, or how a source or licence is recorded. The consequences are already visible on the one file that exists: it is the sole entry in Special:UncategorizedImages; no File: namespace category exists for it to join; and its description page is the article caption copied verbatim — the same colour key, word for word, in two places that nothing keeps in step, so approving any caption change (see #53) silently puts them out of sync. |
flag-only on the substance. What a file description page should carry is a convention decision, and the convention set reserves those to the operator. Three questions settle it: whether files are categorised at all (and if so, whether the category is in-character like every other, per §Naming); whether a source line is recorded, given that these are exports of the map and the question of licence raised in #53; and whether a description page may restate an article caption or should point at it. Once decided the mechanical work is small — one category, one short description — and the routine can carry it out. | pending | New 2026-07-27, from the first upload in the wiki's history. Deliberately not proposed here: any particular category name, or a licence template. #14 (deferred) is the neighbouring case for pages — uncategorised front pages, where the operator accepted the finding but had no decided approach yet; this is the same shape one namespace over, and may want the same answer.
Re-checked 2026-07-28, unchanged.
Re-checked 2026-07-30, unchanged: still one file on the wiki, still the sole entry in Special:UncategorizedImages, still no |
| 55 | 2026-07-27 | voice | low | Tacchoan | Four wordings in the new §Members text sit below the encyclopedic register. Yezur Wiki:Conventions §Editorial voice asks for "neutral and third-person, definition-first, like any good reference work". (a) The caption describes the key rather than the subject: "Red is referring to the Herta-Olaic family, while green is the Esselis branch, purple the Rumesselis branch..." — a reference work captions what the map shows, not the act of matching colours to names. (b) "Esselis, the one spoken by the highest amount of population" — amount takes a mass noun, and "the one spoken by" is a conversational stand-in for a plain superlative. (c) "a subfamily that is spoken in the south-east of the continent, as well as spoken on small areas of Lovvocia" — spoken twice in one sentence, and on where the sense is in. (d) "subdivisible into four categories" — category has a working meaning on this wiki, and the same six lines call these things branch or subfamily three times over. | Mechanical, and asserts nothing new — every fact stays exactly as written, including which colour marks which branch and which branch sits where. (a) recast as a description: the four Tacchoan branches, named with their colours, and Herta-Olaic identified as the neighbour (see #53(c)). (b) → "the most widely spoken of the four, in the centre of the continent". (c) → "spoken in the south-east of the continent, and in small areas of Lovvocia through colonial ties". (d) → "divided into four branches". | pending | New 2026-07-27, from reviewing the day's one article edit against the convention set in full. Not flagged in the same passage, and recorded as passing: the lead's "one of the five major Yezuri language families" is the reflexive planet-qualifier already carried by #38, which lists Tacchoan among its pages; the new Kipoa bullet's colonial claim is confirmed by Lovvocia, which independently records Tacchoan languages "in smaller areas — particularly the central region adjoining Vetsia"; and "the continent", used three times unnamed, resolves correctly to Taccho from the first sentence.
Re-checked 2026-07-28, unchanged. Re-checked 2026-07-30, unchanged. Tacchoan was edited this window (2026-07-30, rev 1618), but only to replace the empty Cargo member query in §Members with the plain sentence "No member languages are currently listed."; all four wordings are untouched. Re-checked 2026-07-31, unchanged — Tacchoan was not edited this window. |
| 56 | 2026-07-27 | factual | low | Tacchoan | Tacchoan calls one of its own branches an isolate, against the wiki's own definition of the word. The fourth bullet reads "Usy, an isolate subfamily spoken on the island of Usings". Category:Language isolates defines the term on this wiki, in full: "Languages with no demonstrated kinship to any language family." Its one member, English language, uses it in exactly that sense — "It is a language isolate: it has no demonstrated kinship with any of the major language families". A branch of Tacchoan has demonstrated kinship by definition: that is what makes it a branch. As written the sentence claims both at once. | Mechanical, a two-word swap. "an isolate subfamily" → "the family's only single-language branch", which is what the passage means and what the caption already implies by naming "the Usy language" in the singular. Nothing else in the bullet changes. | pending | New 2026-07-27. The distinction matters beyond the wording: Category:Language isolates is a live category with a member, so leaving isolate in place invites Usy into it when the article is written, which would put it in two mutually exclusive places at once.
Re-checked 2026-07-28, unchanged. Re-checked 2026-07-30, unchanged — the bullet still reads "an isolate subfamily", and Category:Language isolates still has exactly one member, English language. Re-checked 2026-07-31, unchanged — the bullet still reads "an isolate subfamily", and Category:Language isolates still has exactly one member, English language. |
| 57 | 2026-07-27 | structural | medium | Tacchoan, Esselis, Rumesselis, Kipoa, Usy, Usings | Five subjects were named into existence and none has an article; and the four branches are linked in the caption but left as plain text in the bullets that define them. The 2026-07-27 edit to Tacchoan introduces four branch names — Esselis, Rumesselis, Kipoa, Usy — and one place, the island of Usings. All five are red. They account for the entire rise in wanted pages this run, 31 → 36: four at two incoming links each (the article and the file description page, which repeats the caption) and Usings at one. Separately, the linking is inconsistent within the same six lines: all four branches are linked from the image caption, and all four are plain text in the bullet list immediately below — the bullets being the passage that actually defines each one. | Two halves. The mechanical half is the linking: link the four branch names at their bullets, where they are defined. The flag-only half is the articles. Four branch stubs could be written from what Tacchoan already asserts — each branch's position on Taccho, its relation to the others, and Kipoa's colonial reach into Lovvocia — restating wiki-asserted facts only and inventing nothing; Usings cannot, since the article gives it no property beyond being an island where Usy is spoken. Whether those stubs are wanted is the operator's call. | pending | New 2026-07-27. #11 (deferred) is not this: it covers the empty Cargo member query on this and two sibling articles, which is a language-level gap and stays empty either way, because these five are branches and places rather than languages. Which raises a structural question the routine is not filing as its own row: the branch layer has nowhere to live in the structured data — LanguageFamilies holds the family, Languages holds languages, and neither carries a field for the layer between, so once branch articles exist nothing will relate them to Tacchoan but prose. Adding a field is a schema change and needs the administrative rebuild noted in §Infoboxes and structured data. Talk:Tacchoan does not exist; if the stubs are declined, §Open threads there is where the four names belong. The five names are written unlinked throughout this report, as Template:He-decl and Dictionary:dog were last run: linking them here would add a third incoming link to each and make this page a cause of the very counts it reports.
Re-checked 2026-07-28, unchanged. Re-checked 2026-07-30, unchanged: the five names are still red, still account for five of the 36 wanted pages, and the four branches are still linked in the caption and plain text in the bullets that define them. The 2026-07-30 edit to Tacchoan replaced the empty Cargo member query and touched nothing else. One part of this note is now moot: the structural question it raised — that the branch layer had nowhere to live in the structured data — has been settled by the retirement of Cargo from the encyclopedia. Member lists are hand-maintained now, so branch articles would be tied to Tacchoan by prose and category whether or not they are written, and no schema change is in the way. Re-checked 2026-07-31, unchanged: the five names are still red, they still account for five of the 31 wanted pages, and the four branches are still linked in the caption and plain text in the bullets that define them. Tacchoan was not edited this window. |
| 58 | 2026-07-28 | structural | low | Talk:Family A, Talk:Family B, Talk:Family C, Talk:Family D, Talk:Family E | Five pages are now queued for deletion and only an administrator can clear them. Carrying out #46(a) this run placed {{delete}} on the five talk pages that outlived the language-family rename, so Category:Pages flagged for deletion has gone from empty to five members. Each carries the same stated reason: "Talk page of an article deleted in the language-family rename; its one open thread was settled when the family was named." The underlying facts were confirmed when #46 was filed — Family A through Family E were deleted by Yezur on 2026-07-19 and their talk pages were simply never moved with them. |
flag-only. The editing bots hold no delete right, so this is listed for the administrator to action, as the task list requires of the deletion queue. Delete the five and the row clears itself; the routine will keep listing them every run until then. Removing a tag is not something the routine will do — if any of the five should be kept after all, say so and the row becomes the instruction to untag. |
pending | New 2026-07-28, and the direct product of an approved fix rather than a fresh defect. The queue was empty on every previous run.
Re-listed 2026-07-30, unchanged: the same five pages, each carrying the same stated reason, are still the whole of Category:Pages flagged for deletion. Re-listed 2026-07-31, unchanged: the same five pages, each carrying the same stated reason, are still the whole of Category:Pages flagged for deletion. Third run this row has been listed; it clears itself the moment the five are deleted. |
| 60 | 2026-07-30 | structural | high | the Map: namespace (33 pages), Map:Features, Map:Main Page |
Thirty-three of the thirty-five pages in the Map: namespace can no longer be reached by name, and the index built last run to gather them is now almost entirely red. The namespace's title-casing rule has changed: Map: (namespace 3004) now reports case=first-letter, so a title is capitalised after the prefix. Thirty-three of its pages were created under lowercase titles — Map:place, Map:highway, Map:name, Map:natural=coastline and the rest — and that rule can no longer address them. The pages themselves are intact: addressed by page id, Map:place is still 2,062 bytes of wikitext, and all thirty-three still hold their content. Nothing can reach it. A reader who opens one is bounced: /wiki/Map:place answers 301 to /wiki/Map:Place, which answers 404 with the "no text in this page" notice. The API behaves the same way — action=raw returns an empty body, and a title query silently normalises Map:place to Map:Place and reports it missing. Map:Features now renders 34 of its 35 links red: every key and value page it was built to index, plus Map:Conventions, which was already wanted. Only two pages in the namespace still work, and only because their titles begin with a capital anyway — Map:Features and Map:Main Page, which means the map portal's own navigation now leads nowhere. When it happened: the last report recorded those same 33 links as resolving on 2026-07-28, and this page's five Map: links were re-recorded in capitalised form when it was saved on 2026-07-30, so the change falls between 2026-07-28 20:40 and 2026-07-30 14:09. What it was: the Dictionary: namespace still reports case=case-sensitive, which is what Map: must have held when these pages were created — a first-letter namespace will not accept a lowercase title at all, so they could not have been made under the present setting. |
(a) The recommended fix is one line of configuration, and only you can make it: restore the case override for namespace 3004 in LocalSettings.php — the same setting that still keeps Dictionary: case-sensitive — and, for consistency, 3005 (Map talk:, which holds no pages). That brings all thirty-three back at once, with every page name, every link and the whole Map:Features index correct as already written, and nothing on the wiki to edit afterwards. (b) The fallback, which the routine could carry out, is to move all thirty-three to capital-initial titles and rewrite Map:Features and the key pages' internal links to match; Alompan holds the move right and can address the pages by page id, which is the only handle that still works. It is the worse answer — it renames a documented tag set away from the lowercase form the tags themselves take — and it is offered only in case the configuration cannot be recovered. Do not do both. Until one of them happens, nothing new should be written into the namespace. |
pending | New 2026-07-30, and the first high-severity row since #26'. Read out of the wiki rather than inferred: the case setting was queried from siteinfo, the surviving content was fetched by page id, and the 301→404 was followed end to end. Filed as one row because it is one cause. Not a defect in anyone's editing' — no page content is wrong, and Map:Features was correct on the day it was written. #33 (dismissed) named two of the same value pages for a different reason and is not re-opened here. Note on this report: its own five links into the namespace were the sole cause of five wanted pages, so they are written as plain code from this revision on.
RESOLVED 2026-07-31, by fix (a). The namespace has been put back: |
| 61 | 2026-07-30 | factual | medium | Yezur Wiki:Main Page, Module:Languages | Two pages still describe Cargo as the engine behind the encyclopedia's infoboxes and lists, after it was retired from exactly that role. Yezur Wiki:Conventions now reads "Infoboxes are display only — they file nothing into a database. Lists, member rosters, and cross-references are written and maintained by hand"; the five encyclopedia infoboxes have had their #cargo_store and #cargo_declare calls removed; the family Members tables and the two category listings have been converted to hand-maintained text; and Special:CargoTables is down to the single Lexemes table. Two pages were not brought along. (a) Yezur Wiki:Main Page §How it runs still introduces the software as "extended with Cargo (the structured data behind the infoboxes and the self-building lists)", and its §Conventions still advises "Prefer templates, Lua, and Cargo over repetition." Neither holds for the encyclopedia any more, and the first contradicts the convention page a reader is sent to from the same screen. (b) Module:Languages's header comment ends "Keep this table in step with the Languages Cargo table" — the Languages table no longer exists, and the dependency now runs the other way: Template:Infobox language's documentation was rewritten on 2026-07-30 to say "keep it in step with Module:Languages". As written, the module points at nothing and the template points at the module. |
Mechanical, and asserts nothing new. (a) Narrow the §How it runs parenthetical to what Cargo still does — the Dictionary's Lexemes table — and drop Cargo from the §Conventions bullet, leaving "Prefer templates and Lua over repetition." The see-also link to Special:CargoTables is not proposed for removal: the page still exists and still lists a table. (b) Replace the module's closing comment with the direction that now holds — keep the table in step with the code field of Template:Infobox language — matching the wording that template's own documentation already carries. Two edits, neither touching behaviour. |
pending | New 2026-07-30, from reading every page outside the Dictionary namespace against the ruling; these two are the only survivals of it. Cross-reference: #47 also proposes edits to Yezur Wiki:Main Page (§Behind the scenes and §Conventions), so if both are approved they belong in one edit. Recorded as not a finding: Talk:English language's open thread asks whether the isolate's Cargo row should store a queryable value — a talk-page thread the ruling has simply answered, and a stale thread on a talk page is not a defect. Template:Head and Yezur Wiki:Dictionary structure still describe Cargo at length and are correct to: the Dictionary is the deliberate exception.
Re-checked 2026-07-31, unchanged and confirmed line by line: Yezur Wiki:Main Page still reads "extended with Cargo (the structured data behind the infoboxes and the self-building lists)" and still advises "Prefer templates, Lua, and Cargo over repetition"; Module:Languages line 9 still reads "Keep this table in step with the Languages Cargo table". Neither page has been edited since the row was filed. |
| 62 | 2026-07-30 | voice | low | 210 Dictionary: entries, Yezur Wiki:Dictionary structure |
The definition sweep of 2026-07-30 puts several senses on one numbered line, and quotes glosses with straight quote marks where the wiki asks for italics. Khurouan enriched the definition line of 210 entries — every Proto-Herta-Olaic lemma but one — turning a bare gloss into a described semantic range: "# blood" became "# blood; the life-fluid; by extension kinship and killing". The work is careful and the content is not in question; two points of form are. (a) Senses per line. Yezur Wiki:Dictionary structure states the rule twice — "Definitions are numbered wikitext list items (#), one sense per line", and "numbered senses" among the habits adopted as-is. All 210 lines carry two to four senses separated by semicolons, and 86 add an em-dashed comparative note. (b) Quoted glosses. 31 of the lines name other concepts inside straight single quotes — "overlaps 'see' and 'remember'", "not clearly separated from 'foot'" — 40 distinct terms in all. Yezur Wiki:Conventions §Text formatting gives that duty to italics: "Italics carry their usual duties: words as words, native-language forms, titles of works". (Two further lines contain an apostrophe only, in digit's and beast's, and are not affected.) |
(a) is a decision, not a defect to correct. A reconstructed lemma arguably has one sense whose range is being described, rather than several senses to number — and many of the lines say exactly that ("not clearly separated from 'foot'"). If that reading is right, the fix is to record the exception on Yezur Wiki:Dictionary structure — proto-language entries gloss a semantic range on a single line — rather than to split 210 entries; if it is not, the lines want splitting into numbered senses, which is a large authorial edit and belongs with Khurouan rather than with the routine. (b) is mechanical: italicise the 31 quoted spans in place of the straight quotes, changing no wording and no fact. The routine can do it in one pass on approval. | pending | New 2026-07-30, from reviewing the largest content change since the last run against the convention set in full. Two things recorded here rather than filed as rows of their own. (i) Two of the new lines use human in character for the first time on the wiki — "a human being; someone; one of us as against a beast" and "possibly 'human' at large". Every earlier use of the word anywhere on the wiki is out-of-frame, describing the human editor. Whether the peoples of Yezur are called human in the encyclopedia's own voice is a canon question, not a maintenance one; noted so it is not found again as a defect. (ii) One Proto-Herta-Olaic lemma was missed by the sweep and still carries its bare gloss: xiəltə "four", conspicuous because three and five were both enriched. Otherwise the sweep is clean: no Earth reference, no break of frame, every gloss= parameter left in step with its short sense, and Lexemes unchanged at 526 rows with no field lost.
Re-checked 2026-07-31. Part (a) has been half carried out, outside this routine. On 2026-07-30, between 20:31 and 20:34, Khurouan split packed senses onto separate numbered lines across 87 Proto-Herta-Olaic entries (revisions 1843–1929, summary "Enumerate senses as separate definitions"). The sweep is faithful — every one of the 87 was compared word for word against its previous revision, and nothing was lost beyond the connectives a split makes redundant. It is also incomplete: 124 of the 211 Proto-Herta-Olaic entries were not reached, and 118 of those still carry a packed first line, so the condition this row describes is now true of roughly three-fifths of the language rather than all of it. The two other languages were never affected — all 212 Ancient Hertic and all 102 Proto-Njeshan entries have exactly one definition line each. Part (b) has moved a little: straight-quoted glosses are down from 31 to 27 definition lines, four of them having become parenthetical labels in the sweep; the 27 are listed by the same method as before and 25 of them sit on entries the sweep did not touch. Two new rows come out of the sweep rather than being folded in here, because they are about how it was written rather than whether it should happen: #63 (the labels it introduced) and #64 (the separator it used). |
| 63 | 2026-07-31 | structural | medium | 87 Dictionary: entries (Proto-Herta-Olaic) |
Seventy-five sense labels were written as plain text, on a wiki that has a built template for exactly them. The definition sweep of 2026-07-30 introduced a leading parenthetical on 75 definition lines across 87 entries — (by extension) 71 times, plus (relative) twice and (indefinite) and (adjectivally) once each — all typed directly into the wikitext, as in # (by extension) the front, the chief, the beginning. Template:Lb exists and is built for this: its own documentation opens "Inline sense labels, placed at the very start of a definition line — the italic, parenthesised context/register/domain tags". Yezur Wiki:Dictionary structure names it twice, in §What the Yezur Dictionary adopts as {{lb|code|label…}}, "inline sense labels, italic and parenthesised before a sense (built)", and again in the passage describing definitions: "Context labels — {{lb|en|nautical|slang}} — prefix a sense". Module:Labels' own header names this very label among the ones that work without further setup: "semantic qualifiers (figurative, idiomatic, by extension, …) just work as plain text". The plain-text form renders upright, the template renders italic, so the wiki now shows two appearances for one thing. The template is barely used at all: 5 pages in a 527-page Dictionary call it, all of them Ancient Hertic, and all 75 plain-text labels date from this one sweep. |
Mechanical, one pass, no judgement. Rewrite each leading parenthetical as a label call: # (by extension) X → # {{lb|YAP-XX|by extension}} X, and likewise for relative, indefinite and adjectivally. The routine checked what this produces before proposing it: {{lb|YAP-XX|by extension}} renders (by extension) in italics and files the page into no category at all, because none of the four is in Module:Labels' categorising vocabulary — so the edit changes appearance and nothing else, and adds no wanted categories. Nothing else on the affected lines changes. |
pending | New 2026-07-31, from the only content change on the wiki this window. Not a criticism of the sweep, which did what #62(a) described and did it faithfully; this is the markup it reached for. Worth deciding once rather than per entry, because the Dictionary is the part of the wiki that will grow fastest and 71 of the 75 are the same label. If #62(a) is carried further across the remaining 124 entries, this row should be settled first so the same choice is made throughout — otherwise the split runs the other way and the newer entries are the plain-text ones. |
| 64 | 2026-07-31 | voice | low | 13 Dictionary: entries (Proto-Herta-Olaic) |
The same sweep separated near-synonyms two different ways, in the same pass, in the same language. Of the 87 entries it rewrote, 74 now join the terms of the first sense with commas — # bird, a flying creature, # fruit, the edible growth of a plant, # fear, be afraid, dread — while 13 kept the semicolon they had before: # nose; the smelling part, # head; the top of a person, # hand; the grasping part, # heart; the beating organ, # mouth; the opening, # tongue; the organ of taste and speech, # tooth; a biting part, # knee; the joint of the leg, # flesh; the edible substance of a body, # root; the underground part, # bite; seize with the teeth, # suck; draw in with the mouth, and # seed, grain; the sown thing, which uses both. The thirteen are not a distinguishable class — they are body-part nouns and their verbs, which the comma form covers elsewhere in the same sweep (# bone, the hard frame, # ear, hearing, # wing, the flying limb) — so the split reads as an artefact of the pass rather than a distinction being drawn. |
Pick one and apply it to the thirteen; either direction is a single mechanical pass and the routine holds no opinion on which. Comma matches the 74 and makes the whole sweep uniform. Semicolon is defensible if the intent was gloss; explanation — a short equivalent, then a fuller definition — in which case the 74 are the ones out of step and the fix is larger. A third answer is that the difference is deliberate and this row should be rejected. Whatever is chosen belongs in the same pass as #63 and, if it is carried further, #62(a). | pending | New 2026-07-31. Filed narrowly. The larger fact — that the sweep covered 87 of 211 entries — is recorded against #62 rather than here, because it is that row's condition partly resolved, not a new one. This row is only about the punctuation the 87 were left with, which is new this window and did not exist to be flagged before. Low, and genuinely low: nothing is wrong or unclear on any of the thirteen pages read on its own. |
Dismissed flags
Deferred or rejected findings, kept here so later runs do not re-flag them.
- #8 (deferred) — Wanted history-period pages Yezuri Age of Exploration / Yezuri Middle Ages. Operator: not canon names for these eras; will not create stubs under temporary names.
- #11 (deferred) — Andusian / Tacchoan / Shung-Worrehan member-language queries fall back to the default. A content gap, not a data error; operator: no member languages are in yet, add when ready.
- #12 (rejected) — Greek-letter native names on Hertia / Hertic language / Alompe etc. Operator: fully intentional in-world orthographic style.
- #14 (deferred) — Uncategorised portal front pages and the root Category:Yezur. Operator: accepted, but no decided approach for handling it yet.
- #21 (deferred) — The four wanted Ancient Hertic inflection templates (conj-IS, conj-OO, decl-N1, decl-N2). Operator: "will be fixed when the tables are created — already on my to-do." Confirmed present on the to-do list at User talk:Yezur.
- #30 (rejected) — The one-line User:Yezur page, read as an unfinished sentence. Operator: the line is not unfinished — the city name is written there as
, "using a script I have added to the wiki, with characters stored in the PUA … a temporary text intended to be used for testing the PUA font; it is working correctly." Answering the operator's condition for reflagging: the routine can see the characters and reads five PUA codepoints there (U+E067 U+E111 U+E179 U+E179 U+E0EB, the third and fourth identical, so a five-letter name with a doubled letter), which round-trip intact through the API. What it cannot do is read them: no mapping from those codepoints to sounds or letters exists anywhere on the wiki, so the glyphs are legible only to a reader with the font. Not reflagged. If a transliteration table for the script ever lands on-wiki, say so and later runs can check such names instead of skipping them. - #32 (rejected) — Airananwe and the code
name:yas-aiinMap:name's worked example matching no language and no registry code. Operator: "that language will land later. No need right now." Left as written; the routine will not re-open it when the language arrives. - #33 (deferred) — The two redlinked values
Map:place=hamletandMap:place=suburbinMap:place's settlement table. Real but not now; they remain the only redlinked values in any key page's value table, and both are listed in the new Map:Features index only through their parent key. - #43 (rejected) — Template:Infobox former country declared and stored into a FormerCountries Cargo table that was never created, so Hertia's structured data went nowhere. Operator: "Cargo tables no longer the go-to." Overtaken by the retirement of Cargo from the encyclopedia (2026-07-30): the declaration and the store have both been removed from the template, so there is no longer a table to create. Confirmed this run — of the six tables the wiki once declared, only Lexemes answers a query; Continents, Languages, LanguageFamilies, Polities and FormerCountries now all throw the same
MWExceptionthat once distinguished an absent table from an empty one, because all five are now absent. The administrative Create data click this row was waiting on is no longer wanted. - #59 (rejected) — Betonia, Unteria and Sea of Sihia categorised but reaching no Cargo table, with no infobox on the wiki fitting a subcontinent, an island or a sea. Operator: "No longer relevant since Cargo tables no longer the go-to. Not everything needs to be tabulized." The structured-data half of the finding has been removed by the same ruling, and the infobox question closes with it. Vetsihia's borrowed
{{Infobox continent}}is left as it stands: with Cargo gone it is display only, and itstype=Geographic region (colloquial)already says what the article is.
Latest run
2026-07-31 (scheduled run). Recent changes 1820–1907, 88 of them, by two editors — and 87 of the 88 are one sweep through the Dictionary. The wiki outside the Dictionary: namespace was not edited at all since the last run; the 88th change is this report being posted.
No verdicts were left, so nothing was applied and no article was touched. This page has not been edited since the routine posted it on 2026-07-30 (revision 1842), and the last triage remains that of 2026-07-30 ("out with cargo", revision 1629). All thirteen rows were still pending at the start of this run; all thirteen were re-checked and none was removed. The only page edited this run is this one.
Fixes applied
None, and none were due: an untriaged table has nothing to apply. Every row carries a dated re-check line instead.
#60 is fixed — the Map namespace is back
The high-severity row filed last run is resolved, by the configuration fix it recommended as (a). siteinfo now reports case=case-sensitive for namespace 3004 and for 3005 alongside it, and the thirty-three pages that spent the last window unreachable answer to their own names again. The routine confirmed it three ways rather than taking the setting's word for it: Map:place returns its full 2,062 bytes from action=raw, a title query resolves it without normalising the initial letter away, and Map:Features — the index that was 1 of 35 links blue when the row was filed — now parses 35 of 35 blue. No page was edited to achieve it and none needed to be; every page name, every internal link and the whole index were correct as already written, which is what made (a) the better of the two fixes offered.
Two things are worth recording. The repair is invisible in Recent changes: a LocalSettings.php change leaves no revision, so the row's re-check line and this paragraph are the only account of it the wiki holds. And wanted pages fell 36 → 31 exactly as predicted: the five capitalised Map: titles were the whole of the rise, they had a single source — this report's own links — and with both the namespace and the links restored to sanity the count is back to what it was on 2026-07-28. Every one of the 31 traces to an open row, a dismissed flag or a to-do note; none is new.
The row itself is left in the table, because the routine removes a row only on your verdict, never on its own reading that a finding has gone away. A one-word rejected or deferred clears it and there is nothing to apply.
The definition sweep, checked line by line
The window's one content change is Khurouan's pass through the Dictionary on 2026-07-30, 20:31–20:34 — 87 edits, revisions 1843–1929, all summarised "Enumerate senses as separate definitions", all on Proto-Herta-Olaic entries. It carries out part (a) of #62: senses that had been packed onto one numbered line are split onto separate ones, with the derived sense labelled.
It is faithful. Each of the 87 was fetched at both revisions and compared word for word across its definition lines. Ten pages differ by more than punctuation, and all ten differ in the direction a split makes necessary: six lost a single connective (and, or, to) that had joined two senses now standing apart, and four lost a pair of straight quotes that became a parenthetical label. Nothing was dropped, reworded or invented on any of the 87, and no headword line, gloss, etymology or descendant list was touched — the Lexemes table still holds exactly 526 rows and one row per page.
It is incomplete, and stopped mid-language. 87 of the 211 Proto-Herta-Olaic entries were reached; 124 were not, and 118 of those still carry the packed first line the sweep was undoing. The other two languages were never in question — all 212 Ancient Hertic and all 102 Proto-Njeshan entries have exactly one definition line apiece. So #62(a) is not resolved but reduced: it now describes about three-fifths of one language rather than all of it, and the entries on either side of the line are written in visibly different styles. That is recorded against #62 rather than filed as a new row, since it is the same condition partly cleared.
Two things about how it was written are new, and are filed: #63 and #64.
Hand-maintained lists
Run in full for the second time; everything still agrees, and nothing in this group was edited this window.
- List of languages — ten rows, checked cell by cell against the ten language articles. Family, era, region, code and native name match every infobox. English language, the one article with no
familyfield, is the one row the list calls a language isolate, and it is the sole member of Category:Language isolates. - Family Members tables — Njeshan lists seven and exactly seven articles carry
family=Njeshan; Herta-Olaic lists two and exactly two carryfamily=Herta-Olaic. Andusian, Shung-Worrehan and Tacchoan claim no members and none exists. Nothing has drifted and nothing is missing. - The five families — Category:Language families holds five, List of languages names the same five, and each family article opens by calling itself one of the world's five.
- Continents — as last run, the check as written has nothing to compare: Main Page carries no continent list, it links the category. The category holds seven articles; Vetsihia, which borrows
{{Infobox continent}}without being a continent, is correctly outside it in Category:Geographic regions. Said again so the line is not read as unchecked.
New flags
Two, both out of the definition sweep, both about its markup rather than its substance.
#63 (medium, mechanical) — the sweep introduced 75 leading sense labels as plain text, 71 of them (by extension), on a wiki where Template:Lb is built for exactly that and is named twice in Yezur Wiki:Dictionary structure as the way to do it. The plain form renders upright, the template italic, so one thing now has two appearances. The routine tested the replacement before proposing it: {{lb|YAP-XX|by extension}} renders (by extension) and files the page into no category, so the fix changes appearance and nothing else and adds no wanted categories.
#64 (low) — within the same 87 entries the first sense is punctuated two ways, 74 with commas and 13 with the semicolon they had before, across words of the same kind. Either direction is a one-pass fix and the routine has no preference; rejecting it is a reasonable third answer.
Deliberately not filed. The three {{lb}}-related things that are not defects: Template:Auphen/testcases and Template:Infobox polity showing as unused templates (a testcases page and a documented template awaiting its first use), Template:Infobox/styles.css as the one uncategorised template (a stylesheet subpage), and the 109 Dictionary entries that appear as both orphaned and dead-end pages, which is what a dictionary entry reached through its categories should look like. Everything red on the wiki traces to something already open: the four inflection templates to #21, the seven module /doc pages to #25, all 43 wanted categories to to-do flag #18, Yezuri Age of Exploration and Yezuri Middle Ages to #8, the two lowercase Map:place values to #33, Map:Conventions to #26, the five Tacchoan names to #57, and Dictionary:dog to the worked example on Template:D that has always produced it. The uncategorised front pages and the root Category:Yezur remain covered by #14 (deferred).
Clean
Linter errors 0. Broken redirects 0, double redirects 0. Category:Auphen errors 0 members and Category:Auphen test failures 0, both the good state. Unused images 0.
Lexemes audited row by row rather than counted, and identical to last run in every measure despite 87 of its pages being rewritten: 526 rows, no row missing word, lang, pos or gloss, no duplicate word–language–part-of-speech triple, no page holding two rows, and word equal to the page title in all 526. 210 carry an etymology (209 inherited, 1 compound); every etym_source value is one of the three registered codes YAP-XX, YAQ-HE, YBP-XX, and no row carries one of the pair etym_type/etym_source without the other. The 316 without an etymology are the 313 reconstructed proto-roots, which have no ancestor to record, plus the three {{etym-missing}} entries that are the whole of Category:Ancient Hertic entries needing etymology.
Wanted pages 36 → 31, the fall being #60 undone. Wanted categories 43, unchanged and unchanged in membership — the same 43, all lexical, none new. Wanted templates 4, unchanged. Site totals: pages 714, articles 452, edits 1,908, files 1, job queue empty.
Self-check on this report. Its own links were re-counted after last run's namespace lesson: the five Map: mentions stay written as plain code rather than links, and the two new rows name their 100 affected Dictionary pages by count and by quoted wikitext rather than linking them, so this page adds no incoming links to the pages it reports on and cannot inflate any count it publishes.
Pending
15 rows — thirteen carried forward (#47, #50, #51, #52, #53, #54, #55, #56, #57, #58, #60, #61, #62) and two new (#63, #64). #60 is carried forward only in the bookkeeping sense: it is fixed, and wants a one-word verdict to clear.
Five medium (#47, #53, #54, #57, #61, now #63 a sixth), the rest low; no high left. Eight need only a one-word verdict: #51(a), #52, #55, #56, #60, #62(b), #63 and part (c) of #53 are purely mechanical, and #55, #56, #53(c) and the first half of #57 still all touch the same six lines of Tacchoan and can go in one edit. One is yours rather than the routine's: #58, five deletions, now listed for the third run. The rest turn on a decision — #47 whether Meta: is retired, #50 and #51(b) on wording, #54 on file conventions, #62(a) on whether the sweep is carried through the remaining 124 entries, and #64 on a mark of punctuation.
The Dictionary rows go together. #62(a), #62(b), #63 and #64 all touch the same definition lines, and three of the four are one mechanical pass each. Settling them in one sitting means the Dictionary is written one way rather than four, and — because #62(a) would extend the sweep to 124 more entries — settling them before that happens rather than after.