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
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. Re-confirmed 2026-07-30: Meta: and Help: still hold 0 pages each, and the sidebar's Project docs slot still points at Special:PrefixIndex/Meta: — MediaWiki:Sidebar has not been edited since 2026-07-14. Yezur Wiki:Conventions was edited on 2026-07-30 for the Cargo ruling, in §Categories and §Infoboxes and structured data only, so both halves of the mismatch stand exactly as described. New this run: #61(a) proposes other edits to Yezur Wiki:Main Page; if both are approved they belong in one edit.
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.
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.
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.
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.
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 File: category, and Yezur Wiki:Conventions still has no §Files — the 2026-07-30 edit to that page touched §Categories and §Infoboxes and structured data only.
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.
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.
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.
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.
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.
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.
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.

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.
• #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 MWException that 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 its type=Geographic region (colloquial) already says what the article is.

Latest run

2026-07-30 (scheduled run). There was no run on 2026-07-29 — the workstation's permission layer was unavailable for the whole of that attempt and refused every wiki call outside a small allowlist, so the routine aborted rather than widen its own permissions, edited nothing and moved no watermark. This run therefore covers the full window since the last one: recent changes 1585–1819, 234 of them, by three editors.

Both verdicts left in the table were carried out, and no article was touched. The triage of 2026-07-30 ("out with cargo", rev 1629) gave a verdict on two rows, #43 and #59 — the two remaining Cargo rows — and both were rejected, so the whole of the first phase was to move them to Dismissed flags. Ten rows were left pending and are untouched. The only page edited this run is this one.

Fixes applied

None, and none were due: a rejection has nothing to apply. Both dismissals are recorded in full under Dismissed flags, with the state of the wiki that confirms each.

The Cargo retirement, as the routine found it

Between the two runs the wiki's structured-data policy was reversed — by Thiorosan on 2026-07-30 in fifteen edits (revisions 1614–1628) and by you at the server. The routine's business is to report what it found, and what it found is that the change is all but complete. Every #cargo_query, #cargo_store and #cargo_declare outside the Dictionary is gone: the five encyclopedia infoboxes are display-only, Herta-Olaic and Njeshan carry their Members rosters as hand-written tables, Andusian, Shung-Worrehan and Tacchoan say plainly that no member languages are listed yet, and Category:Geography and Category:Languages let the category listing do its own work. Yezur Wiki:Conventions, Yezur Wiki:Dictionary structure and Yezur Wiki:Daily routine all record the ruling, and the survey below follows the task list as amended. Of the six tables the wiki once declared, only Lexemes survives, which is what §Infoboxes and structured data now says should survive.

Two pages were left behind by it, and are filed as #61. Nothing else outside the Dictionary still mentions Cargo except where it is correct to.

Hand-maintained lists

The task list gained this check on 2026-07-30, when the lists stopped maintaining themselves; it is run here for the first time, and everything agrees.

• List of languages — new this window, and checked cell by cell against all ten language articles rather than against itself. Family, era, region and code match the infobox of every one of the ten; the one language with no family field, English language, is the one the list calls a language isolate, and it is the sole member of Category:Language isolates.
• Family Members tables — Njeshan lists seven languages and exactly seven articles carry family=Njeshan; Herta-Olaic lists two and exactly two carry family=Herta-Olaic. Andusian, Shung-Worrehan and Tacchoan claim no members and none exists. Nothing has drifted and nothing is missing.
• The five families — all five family articles open by calling themselves one of "the world's five major language families", List of languages names the same five, and Category:Language families holds exactly five.
• Continents — the check as written compares Main Page's continent list against the continent articles, but Main Page carries no such list: it links the category instead, which needs no maintaining. The category holds seven articles, and Vetsihia — which borrows {{Infobox continent}} without being one — is correctly not among them but in Category:Geographic regions. Nothing to reconcile; worth saying so, since that line of the task list will otherwise be read as unchecked.

New flags

Three. #60' is the important one and the first high-severity row since #26: the Map: namespace now capitalises titles, and the thirty-three pages created under lowercase ones — the whole documented tag set — cannot be reached by name from anywhere, though their text is untouched in the database. Map:Features, built last run to index them, is 34 of 35 links red, and the map portal's own navigation now leads nowhere. It is not a defect in anyone's editing, and the likeliest single fix is one line of configuration. #61 is the residue of the Cargo retirement: Yezur Wiki:Main Page still calls Cargo "the structured data behind the infoboxes and the self-building lists" and still advises preferring it, and Module:Languages still asks to be kept in step with a table that no longer exists. Both mechanical. #62 covers the 210-entry definition sweep in the Dictionary: senses packed onto one numbered line where Yezur Wiki:Dictionary structure asks for one per line, and thirty-one glosses in straight quotes where §Text formatting asks for italics — the first a decision, the second a one-pass fix.

Deliberately not filed. The first in-character use of the word human on the wiki, and one Proto-Herta-Olaic lemma the sweep missed, are recorded inside #62 rather than as rows. Talk:English language's open thread about a Cargo field is now simply answered, and a stale thread on a talk page is not a defect. The 109 Dictionary entries that appear as both orphaned and dead-end pages are not flagged: a dictionary entry reached through its categories and its language section, with no term yet to link out to, is doing what it should. Everything else red 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, all forty-three 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 portal front pages and the root Category:Yezur remain covered by #14 (deferred); Special:UncategorizedTemplates' one entry is Template:Infobox/styles.css, a stylesheet subpage rather than a template, and is not a finding.

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 was audited row by row rather than counted: 526 rows, no row missing word, lang, pos or gloss, no duplicate word–language–part-of-speech triple, no page holding two rows, and the word value equal to the page title in all 526. 210 carry an etymology (209 inherited, 1 compound) and the 316 that do not 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 categories 44 → 43 — the tracking category this report was itself filling has emptied and disappeared, exactly as last run predicted — and all 43 remaining are lexical. Wanted templates 4, unchanged. Site totals: pages 714, articles 452, edits 1,820, files 1, job queue empty.

Wanted pages 31 → 36', and every one of the five new ones is #60 — Map:Name, Map:Place, Map:Wiki and two Map:Place= values, the capitalised forms the wiki now resolves those links to.

One thing this report was itself causing, now fixed. Those five wanted pages had exactly one source: this page. Its five links into the Map: namespace, written in the dismissed notes for #32 and #33 when they still resolved, are now the only links on the wiki pointing at the capitalised titles, so from this revision they are written as plain code instead. The wording of both notes is unchanged, and the count should fall to 31 on the next parse.

Pending

13 rows — ten carried forward (#47, #50, #51, #52, #53, #54, #55, #56, #57, #58) and three new (#60, #61, #62). One high (#60), four medium (#47, #53, #54, #61, with #57 a fifth), the rest low. Six need only a one-word verdict: #51(a), #52, #55, #56, #62(b) 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. Two are yours rather than the routine's: #60(a), one line of configuration, and #58, five deletions. The rest turn on a decision — #47 whether Meta: is retired, #50 and #51(b) on wording, #54 on file conventions, #62(a) on how a proto-language entry is glossed.