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)
• approved or accepted — carry out the Suggested fix, as written
• amended — carry out the fix described in Notes instead
• deferred — real, but not now; moves to Dismissed flags and is not re-flagged
• rejected — not an issue; moves to Dismissed flags and is not re-flagged
• to to-do — real issue that should be marked on User talk:Yezur's to-do list instead for human intervention
• fixed — 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
43	2026-07-25	structured data	medium	Template:Infobox former country, Hertia, Special:CargoTables	A Cargo table is declared and written to, but was never created — so one article's structured data goes nowhere. Template:Infobox former country carries #cargo_declare:_table=FormerCountries with fourteen fields and #cargo_stores into it on every use, and it is in use: Hertia fills five of its fields (status, era, region, location, languages) and renders the infobox correctly. But Special:CargoTables lists only five tables — Continents, LanguageFamilies, Languages, Lexemes, Polities — and FormerCountries is not among them; a query against it returns an internal exception rather than an empty result. The comparison that settles it is Template:Infobox polity: also declared, used by no article, and its Polities table nonetheless exists and reports 0 rows. So this is not an empty table, it is an absent one — the declaration was saved but the one-time creation step never ran.	One administrative action, then nothing else: from Template:Infobox former country, run Create data (?action=recreatedata). That needs the recreatecargodata right, which an administrator holds and the editing bots do not, so the routine cannot do it. Neither the template nor Hertia needs any change — the row should appear as soon as the table exists. Worth doing before more former countries are written, since every one added meanwhile stores into nothing.	rejected	New 2026-07-25, and confirmed 2026-07-26 that the routine cannot do it: Alompan's own rights were queried directly, and recreatecargodata is false — the account sits in user / autoconfirmed only, holding move, upload and editcontentmodel but neither recreatecargodata nor delete. The comparison that settles absent-vs-empty also still holds: a query on FormerCountries throws MWException while Polities answers cleanly with 0 rows. Third of the three "facts that never reach a table" rows, with #29 and #41. Set back to pending 2026-07-28: the verdict could not be confirmed. Marked fixed in the triage of 2026-07-28, so this run re-tested it first — and FormerCountries still does not exist. A cargoquery against it returns internal_api_error_MWException verbatim, while Polities answers cleanly with 0 rows and the other four tables answer with 8 / 10 / 5 / 526; Special:CargoTables still lists five tables, not six. The one action that fixes it — Create data (?action=recreatedata) from Template:Infobox former country — needs recreatecargodata, which Alompan does not hold, so the routine cannot do it and cannot verify it any other way. Nothing is wrong with the template or with Hertia; the row is kept open only so the one administrative click is not lost. Mark it fixed again once the table answers and the next run will confirm and clear it. Human note: Cargo tables no longer the go-to.
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: Meta: and Help: still hold 0 pages and still have no revision, and the sidebar's Project docs slot still points at Special:PrefixIndex/Meta:. Yezur Wiki:Conventions was edited twice this run (#45(a), §Naming); neither edit touched §Namespaces or §Where out-of-frame content goes, so both halves of the mismatch stand exactly as described.
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.
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.
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.
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.
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.
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.
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.
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.
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.
59	2026-07-28	structured data	low	Betonia, Unteria, Sea of Sihia, Special:CargoTables	Three geography articles now have a category but still reach no Cargo table, and no infobox exists that would fit them. The amended fix to #41 settled the categories — Category:Subcontinents for Betonia and Unteria, Category:Seas for Sea of Sihia, Category:Geographic regions for Vetsihia — and ruled out the infobox half explicitly ("please do not add continent infoboxes to non-continents"), which the routine agrees with: Betonia is part of Andusia, and Andusia lists both it and Unteria under its own §Subcontinents. That leaves the structured-data half open rather than resolved. The wiki has four Infobox templates for places — continent, polity, former country, language — and none describes a subcontinent, an island, or a sea, so three of the four articles carry no structured data at all. Vetsihia is the exception only because it borrows {{Infobox continent}} with type=Geographic region (colloquial), which is the same mismatch seen from the other side.	flag-only. A new template is a design decision the convention set reserves to you, and the routine will not invent one. Three readings are open, and the cheapest may well be the last: (a) a single Infobox landform with a type field, covering subcontinents, islands and seas alike, which would also let Vetsihia stop borrowing the continent box; (b) broadening {{Infobox continent}}'s documented scope, which already reads "a continent or major landmass" and already carries a type field that defaults to Continent — the change would be to the name and the docs rather than the behaviour; or (c) deciding that these four articles do not need structured data, in which case dismiss this and Vetsihia's borrowed box is the only loose end. Note: any new Cargo table needs the same administrative Create data step that #43 is stuck on.	rejected	New 2026-07-28. Filed as the residue of #41, not a re-opening of it: the categorisation you asked for is done and is not in question here. Same family as #29 (since resolved — the three medieval languages now carry infoboxes and the Languages table has gone 7 → 10) and #43: facts that never reach a table. Category:Geography's own query filters on type='Continent', so it renders identically either way. Human note: No longer relevant since Cargo tables no longer the go-to. Not everything needs to be tabulized.

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-ai in Map: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=hamlet and Map:place=suburb in Map: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.

Latest run

2026-07-28 (scheduled run) — the first run in which the routine has changed anything. The triage of 2026-07-28 ("bunch of triaging", rev 1319) gave a verdict on every row filed before this week: 20 accepted, one accepted with an amendment, two sent to the to-do list, two rejected, one deferred and two marked as already fixed. All of them were carried out — 292 edits, revisions 1320–1611 — and the flagged-items table has gone from 36 rows to 12. Nothing was applied that was not explicitly approved, and where an operator note contradicted a suggested fix, the note won.

Fixes applied

Maintenance categories — one decision, six pages (#23, #24, #27, #44). Your note on #24 chose the container, so Category:Dictionary maintenance was created first (1320) under Category:Yezur Wiki, and the rest followed it: Category:Dictionary templates created under Category:Templates (1321, its 7 members now resolve); Category:Hidden categories created with __HIDDENCAT__ (1324) and Category:Auphen test failures created on the Category:Auphen errors pattern (1325), both filed as your note on #27 directed; Category:Auphen errors reparented off Category:Templates (1326); and Category:Ancient Hertic entries needing etymology given its parent at last (1328), the oldest mechanical fix in the table, first filed nine runs ago. One judgement call inside an approved fix, flagged here rather than buried: the second half of #44, Category:Pages flagged for deletion, was not put under Dictionary maintenance (1327) — it collects any page on the wiki, so the routine used the other container #44 itself offered, Category:Yezur Wiki directly. Move it if you would rather it sat with the others.

The map documentation (#31, #26, #34, #35). Your note on #31 asked for the intermediate level, so Category:Map was created under Category:Yezur (1322) and Category:Map documentation beneath it (1323) — 33 members, the largest wanted category outside the lexical backlog, now resolved. Map:Features was then built as the plain index #26 proposed (1401): all 33 key and value pages, grouped by key, values nested under their key, making no claim of its own — every line is a link to a page that exists. That closes the only high-severity row in the table: Map:Main Page's two navigation cards are no longer both dead, and the documented tag set is reachable from the portal built to index it. The second card, Map:Conventions, is untouched and still wanted — how the map is actually tagged is your side of the work, exactly as #26 said. Alongside: Map:wiki's worked example now demonstrates the point it makes, using Sea of Sihia (1330), and the seven reflexive on Yezur qualifiers came out of six Map pages (1344–1349). The three contrastive uses #35 listed as keepers were left alone.

The Earth test in the article namespace (#38). All 21 instances across 18 articles (1350–1367). Deletion where deletion sufficed ("is a language of Njeshan", "the source language for scientific binomials"), and a recast where it would have cost the sense: the family formula became "one of the world's five major language families" and its variants, "where the majority of the world's history has unfolded", "where the tallest mountains on Yezur rise" — the form #38 recorded as passing — and "geographers treat them as separate continents". Everything #38 listed as explicitly not to be touched was not touched, and two proper nouns that merely contain the word survived intact: Yezuri Age of Exploration on Sihia and Yezuri Middle Ages on Taccho are era names, not the reflexive pattern, and both were checked byte-for-byte after each edit.

The three medieval Njeshan languages (#28, #29). Moved to the conventional title with redirects left behind — High Nichana language, Otjesi language, Pises language — talk pages moved with them, and all four inbound links repointed (1374–1380). Each then took {{Infobox language}} filled only from what its own first sentence asserts, family=Njeshan and era=Medieval, with native_name, region and code left blank. Verified after the fact rather than assumed: the Languages Cargo table has gone 7 rows to 10, and Njeshan's Members query — which listed four languages when #29 was filed — now renders all seven, the three medieval stages included. The prose sentence beneath it was kept, since the ancestor-of relationships it carries are still the one thing the table does not.

Ancient Hertic (#36). Your note settled it — "use Ancient Hertic for all references to this language on the wiki currently. Modern Hertic hasn't yet landed" — which is option (b), the registry keeping the name it already had. Since the note asks for all references, the article moved too: Ancient Hertic language, with Hertic language left as a redirect, the bare Ancient Hertic created as a redirect so the Dictionary's own ==Ancient Hertic== headings resolve for the first time, and the native-name redirect Χερτεχι retargeted. The infobox name and the lead now read Ancient Hertic (1385), and the five prose references were updated to match: Main Page, Dictionary:Main Page, Herta-Olaic, Alompe and Hertia's infobox (1387–1391). Module:Languages's worked example, which was wrong about its own table whichever name won, now returns what the table returns (1392). One consequence worth having in view: Hertic language is now a redirect rather than an article, so when Modern Hertic lands the title is free to be retargeted or overwritten — nothing has to be undone first.

The rest. Alompe no longer sits in both Category:Cities in Hertia and its own child (1329), leaving the chain intact (#39). Pandenica is a polar continent in its lead and its infobox, and Vetsia calls it one too (1331–1332) — the Continents table's location field followed automatically (#40). Two module header comments that said the opposite of what their pages do were corrected (1333–1334), and the Kept behaviours clause that contradicted divergence D15 was deleted from Module talk:Auphen (1335) (#48, #49). The retired Family A–E scheme is gone from all three project pages (1336–1338): the bullet deleted from Yezur Wiki:Conventions §Naming as your note directed, and the two worked examples now name a family and a proto-language that exist (#45). The five orphaned family talk pages were tagged for deletion (1339–1343) (#46(a)) — see the new #58.

Betonia, Unteria, Sea of Sihia, Vetsihia (#41, amended). Your note overrode the suggested fix on both halves: no continent infoboxes on non-continents, and new categories chosen by what each article says it is. Three were created under Category:Geography and the four articles moved out of the top-level bucket into them (1394–1400) — Category:Subcontinents for Betonia and Unteria, which Andusia's own §Subcontinents section names as exactly that; Category:Seas for Sea of Sihia; and Category:Geographic regions for Vetsihia, whose own infobox calls it a geographic region (colloquial). The structured-data half your note closed off is filed as the new #59, flag-only.

The Dictionary sweep (#42). 209 entries, 209 edits (1402–1610), the largest single fix the routine has made. Every value was taken from the entry's own etymology sentence and nothing was inferred: 208 entries reading "Inherited from Proto-Herta-Olaic …" took etym_type=inherited + etym_source=YAP-XX, and the one compound, νουζιφτι, took etym_type=compound + etym_source=YAQ-HE — plus the markup slip noted under #42, its second element φτι now linked like its first. The three {{etym-missing}} entries were identified and skipped, as intended: they remain the three members of Category:Ancient Hertic entries needing etymology. Verified through Cargo, not through the edit count: Lexemes now answers 209 inherited + 1 compound against 1 + 0 before, so the query Yezur Wiki:Dictionary structure names as the whole point of the table — "all words inherited from Proto-A" — returns 209 words this evening and returned one yesterday. Two working notes for next time: the wiki rate-limited the sweep at 87 edits and again at 200, so it was completed by a second pass that re-reads each page and skips any that already carries the fields; and the scan and the apply were kept as separate steps, so the 209 targets were confirmed before a single edit was made.

Routed to the to-do list (#25, #37). Both were marked to to-do and are now notes on User talk:Yezur (1611), with their rows cleared and no re-flagging: the seven module /doc pages, and the question of whether the two reconstructed proto-languages get articles. The second note was worth writing after the sweep rather than before it — with 209 rows now carrying etym_source=YAP-XX, Proto-Herta-Olaic is by a wide margin the most-cited language on the wiki and the only one with nowhere to link.

Verdicts that could not be carried out

#43 was marked fixed, and it is not. The routine re-tested it before writing anything else this run: a query against FormerCountries still returns internal_api_error_MWException, Special:CargoTables still lists five tables rather than six, and Polities still answers cleanly with 0 rows — the comparison that distinguishes an absent table from an empty one. Per the task list the row goes back to pending with the reason in its Notes rather than being cleared. It needs one administrative click, Create data from Template:Infobox former country; Alompan does not hold recreatecargodata and cannot verify it any other way.

Flags dismissed

Three moved to Dismissed flags and will not be re-flagged: #30 (rejected), #32 (rejected) and #33 (deferred). #30 carried a question the routine owes you an answer to, so the answer is recorded there in full: the PUA text is intact and the routine can see it — five codepoints, U+E067 U+E111 U+E179 U+E179 U+E0EB, third and fourth identical, so a five-letter name with a doubled letter, surviving the API round-trip unharmed. It cannot read them, because nothing on the wiki maps those codepoints to letters or sounds; that is a missing table, not a broken font, and by your own condition it is not grounds to reflag.

New flags

Only two, both low and both flag-only, and neither is a defect found in your work — one is the product of an approved fix and the other is what an amended fix left open. #58: the five talk pages tagged under #46(a) now sit in Category:Pages flagged for deletion, which the task list requires be listed every run for the administrator, since the editing bots hold no delete right. #59: with the infobox half of #41 ruled out, Betonia, Unteria and Sea of Sihia have a category but no structured data, and no infobox on the wiki fits a subcontinent, an island or a sea.

Deliberately not filed. The survey turned up nothing else that is not already accounted for. Every redlink on the wiki traces to an open row, a dismissed flag or a to-do note: the four inflection templates to #21, the seven module /doc pages to #25, the lexical categories to to-do flag #18, Yezuri Age of Exploration and Yezuri Middle Ages to #8, the two 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 portal front pages and the root Category:Yezur remain covered by #14 (deferred). Both unused categories are the Auphen tracking pair, for which empty is the good state.

Clean

Linter errors 0. Broken redirects 0, double redirects 0 — including after nine page moves and three new redirects this run, which is the check most likely to have been broken by it. Category:Auphen errors 0 members; Category:Auphen test failures 0, still the good state. Unused images 0. Cargo is consistent and every table was re-counted after the sweep rather than assumed: Continents 8, LanguageFamilies 5, Languages 7 → 10, Lexemes 526 rows holding steady with 210 now carrying an etymology, Polities 0, FormerCountries absent (see #43). Wanted categories 47 → 44, wanted pages 36 → 31, wanted templates 4, unchanged and all four accounted for by #21.

One error this report was itself causing, now fixed. The tracking category Category:Pages with syntax highlighting errors had exactly one member — this page. The <syntaxhighlight> block in the triage note on #30 carries no lang attribute, which the extension treats as an error. Moving that note to Dismissed flags this run, the PUA sample was re-rendered with <code> instead: the five characters are preserved exactly, the wording is yours unchanged, and the category should empty — and with it disappear, taking wanted categories to 43 — on the next parse. (Named unlinked here for the same reason the count is worth stating: linking it would make this page a cause of it again.)

Pending

12 rows — down from 36. Ten carried forward (#43, #47, #50, #51, #52, #53, #54, #55, #56, #57) and two new (#58, #59). By severity: no high-severity row remains — #26 was the only one and it was carried out. Four medium (#43, #47, #53, #54, with #57 a fifth) and the rest low. Five need only a one-word verdict: #51(a), #52, #55, #56 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 be carried out in one edit. #58 and #43 are the two that need you rather than the routine — one deletion and one administrative click. The rest turn on a decision: #47 whether Meta: is retired, #50 and #51(b) on wording, #54 on file conventions, #59 on whether these articles want structured data at all.