Jump to content

Yezur Wiki:Daily routine/Report

From Yezur Wiki
< Yezur Wiki:Daily routine
Revision as of 20:10, 22 July 2026 by Alompan (talk | contribs) (Daily maintenance report 2026-07-22: 0 verdicts pending; 5 new flags (#31-#35) from the new Map pages; #26 raised to high)

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, and has 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
22 2026-07-19 structured data resolved Special:CargoTables — Lexemes Resolved — no action needed. The Lexemes Cargo table has finished draining and is fully in sync: 526 of 526 rows. The per-language split totals correctly — Ancient Hertic 212, Proto-Herta-Olaic 211, Proto-Njeshan 102, Pjany 1. No administrator intervention was needed at any point. none — the row is kept only so the resolution is recorded; clear it with fixed or rejected. pending Re-confirmed 2026-07-22: still 526 of 526. (The job queue reads 32 this run, but that is the Map import working through its links, not Cargo; it drains on its own.) Ran its full course over three runs: 177 → 521 → 526. Severity retired.
23 2026-07-19 structural medium Category:Dictionary templates Wanted category with 7 members. The Dictionary's template set categorises into it — including Template:Etym-missing — but the category page does not exist. Its two sibling template categories, Category:Link templates and Category:Infobox templates, both exist and both sit under Category:Templates. Create it on the sibling pattern: a one-line description (Templates used by the Yezur Dictionary.) plus [[Category:Templates]]. Mechanical; the parent is unambiguous. pending Still wanted (7 members) this run. Oldest unresolved mechanical fix in the table.
24 2026-07-19 structural low Category:Ancient Hertic entries needing etymology Uncategorised category. Created alongside Template:Etym-missing, which files entries into it as a review queue. It has no parent, so it hangs off the category tree entirely — and it is the first of a per-language series (Category:<Language> entries needing etymology) that the template will generate for every language it is used with. Give it a parent, and settle the pattern once for the whole series. Best guess: Category:Yezur Wiki, the existing project/maintenance container. Cleaner alternative, if you would rather keep housekeeping queues separate from project pages: create Category:Dictionary maintenance (or a broader Category:Tracking categories) under Category:Yezur Wiki and parent this and its future siblings there. Say which and it can be applied mechanically. pending Still uncategorised this run. See #27 — the same parent-container decision would settle two more maintenance categories at once.
25 2026-07-19 structural low Module:Auphen, Module:Auphen/frame, Module:Auphen/YAQ-HE, Module:Auphen/YBS-PJ, Module:Head, Module:Labels, Module:Languages Wanted documentation subpages. Seven modules carry a documentation transclusion whose /doc page does not exist, so each renders a redlinked doc box. This is the same gap as #9 last run, which was approved and filled by Module:Infobox/doc. Create each /doc on the Module:Infobox/doc pattern, restating only what the module source itself establishes — purpose, entry points, parameters — and inventing no behaviour. Module:Auphen/YAQ-HE and Module:Auphen/YBS-PJ are data pages and need only a short note on the ruleset each holds. Best done by Khurouan, who wrote the modules, but Alompan can do it from the source on approval. pending All seven still wanted this run.
26 2026-07-19 structural high Map:Conventions, Map:Features Wanted pages linked from a portal front page — and now the only route into 33 live pages. Map:Main Page is built around two navigation cards — "Map features" (the keys and values that describe things on the map) and "Conventions" (how features are tagged, named, and classified) — and both targets are redlinks. Those two links are the only links Map:Main Page carries, so with 33 key and value pages now in the namespace, the whole documented tag set is unreachable from the portal meant to index it. flag-only on the substance — how the map is actually tagged is your side of the work, and the routine will not invent map conventions. What is now mechanical, if you want it: Map:Features could be built as a plain index of the 33 pages that exist, grouped by key, making no new claims. Say the word and that much can be done. pending Severity raised medium → high this run. The import on 2026-07-22 turned a cosmetic dead link into a navigational dead end: 33 pages, none of them linked from the portal.
27 2026-07-20 structural low Category:Hidden categories, Category:Auphen test failures Two maintenance/tracking categories that are linked but do not exist. (a) Category:Hidden categories — the standard container into which any __HIDDENCAT__ category files itself; it currently holds one member, Category:Auphen errors, but the container page itself is missing. (b) Category:Auphen test failures — linked from Template:Auphen/testcases as the bin for failing test cases; empty right now (no tests are failing, which is the good state), so it shows only as a redlink in the test harness. Neither is content; both are housekeeping furniture, and both are homeless in the same way as #24. Settle the maintenance-container question once (see #24: Category:Yezur Wiki directly, or a new Category:Tracking categories beneath it) and create all three there. Category:Hidden categories should itself carry __HIDDENCAT__ and a one-line description; Category:Auphen test failures should mirror the existing Category:Auphen errors. Mechanical once the parent is chosen. pending Filed together with #24 deliberately: one parent decision resolves the etymology-queue series, the hidden-categories container, and the Auphen test-failure bin.
28 2026-07-21 naming medium High Nichana, Otjesi, Pises Three language articles are not at the conventional title. Conventions set the form "X language" for language articles, and every other language on the wiki follows it — Gaillean language, Hertic language, Lonish language, Nichana language, Pjany language, Uu language, English language. The three attested medieval stages of Njeshan are the only exceptions: they sit at the bare name. (The bare form is correct for the families — Njeshan, Herta-Olaic, Tacchoan — which is a separate case.) Move each to the conventional title, leaving the bare name behind as a redirect: High Nichana to High Nichana language, Otjesi to Otjesi language, Pises to Pises language. All three target titles are free, and each article has only two inbound links (its family page Njeshan and its descendant language), which can be repointed at the same time. Mechanical; the convention is explicit. pending Re-confirmed still open this run. Related to #29 — the same three pages; the two fixes are independent and can be approved separately.
29 2026-07-21 structured data medium High Nichana, Otjesi, Pises Three language articles carry no {{Infobox language}}, so they are absent from the Languages Cargo table. The table holds 7 rows; these three are not among them. The consequence is visible on Njeshan: its Members Cargo query lists only the four modern languages, and the three medieval stages have to be named in a prose sentence beneath the table instead. Every other language article on the wiki carries the infobox. Add {{Infobox language}} to each, filling only the fields the article itself already asserts — family=Njeshan and era=Medieval — and leaving native_name, region and code blank rather than inventing them. Each article states its family and its medieval status in its first sentence, so nothing new is asserted. Once the rows land, the prose sentence on Njeshan can be trimmed to whatever it still adds (the ancestor-of relationships, which the table does not carry). Note: era=Medieval is a value the table has not held before (Gaillean and Hertic are Ancient, the rest Modern); no schema change is involved. pending Re-confirmed still open this run — Languages still holds 7 rows. Distinct from dismissed #11, which concerns families with no member languages at all.
30 2026-07-21 open thread low User:Yezur An unfinished sentence, saved as the whole page. User:Yezur was created with a single line — "The name of a large Tacchoan city is ." — which breaks off where the name should be. No Tacchoan city is named anywhere on the wiki, and Taccho has no settlement articles, so nothing else supplies the missing word. Most likely an accidental save; possibly a note-to-self, or a naming prompt left for an author account. flag-only — the routine does not edit another editor's user page. Raised only so an unfinished line is not left standing. If it was meant as a naming prompt, say so and Khurouan can generate a spread of candidate Tacchoan city names to cull from; the routine will not invent one. pending Unchanged this run.
31 2026-07-22 structural medium Category:Map documentation Wanted category with 33 members — every page of the new Map tag set. All 33 key and value pages added to the Map: namespace on 2026-07-22 end with [[Category:Map documentation]], but the category page does not exist, so each shows a redlinked category and the set has no category-level index. It is by far the largest wanted category on the wiki outside the lexical backlog. Create it with a one-line description and a parent. Recommended parent: Category:Yezur, the root container, as a sixth top-level branch beside Geography, History, Languages and Templates — the Map: namespace is in-character per Conventions, so it should not hang under Category:Yezur Wiki, which its own page defines as "out-of-frame — about the wiki, not about the world." Alternative, if you would rather it sat a level down: create Category:Map under Category:Yezur and parent this beneath it, leaving room for other map categories later. Mechanical once you pick. pending New this run. Distinct from #24/#27, which concern maintenance containers; this one is content documentation and does not wait on that decision.
32 2026-07-22 open thread medium Map:name The worked example cites a language and a language code that exist nowhere on the wiki. Map:name says additional names go in name:<lang>=* "using Yezur's language codes (for example name:yas-ai for Airananwe)". There is no Airananwe on the wiki — no article, no redirect, no page title beginning "Air", and no such row in the Languages or LanguageFamilies Cargo tables (the five families are Andusian, Herta-Olaic, Njeshan, Shung-Worrehan, Tacchoan). Nor does yas-ai fit the code registry: every registered code is uppercase on a YAQ-/YBS-/YXS- stem (YAQ-HE, YBS-PJ, YXS-EN). The same sentence's other example, name:en, is likewise not the registered code for English, which the table holds as YXS-EN, YXS-NE. flag-only on the first half, mechanical on the second. (a) Say whether Airananwe is meant to be a Yezur language at all — the name reads as belonging to a neighbouring project rather than to this wiki, which is out of scope here. If it is not Yezuri, swap the example for an attested language and its registered code (name:YBS-PJ for Pjany, say). If it is Yezuri, it needs an article and a Languages row before the map documentation can lean on it. (b) Either way, reconcile the case: if the map really uses short lowercase codes rather than the wiki's registry codes, that mapping should be stated on Map:name itself, since the page currently claims the codes are Yezur's language codes. pending New this run. Flagged rather than fixed because only you can say where Airananwe belongs; the routine will not invent a language or a code.
33 2026-07-22 structural low Map:place=hamlet, Map:place=suburb Two of the five values in a value table have no page. Map:place tabulates the settlement hierarchy as city / town / village / hamlet / suburb and links each; the first three exist, the last two are redlinks. They are the only redlinked values in any of the key pages' value tables — every other tabulated value (highway ×4, natural ×4, waterway ×2, landuse ×2, boundary ×1, railway ×1) has its page. Create the two on the pattern of Map:place=village, restating only what Map:place already says — hamlet: a very small cluster of dwellings with few or no services; suburb: a named district within a larger city or town — plus the usual tagging line and See also. Nothing new is asserted; the definitions are lifted from the parent page. Mechanical. pending New this run. Narrower than #26: this completes a set that already defines itself, rather than writing map conventions.
34 2026-07-22 factual low Map:wiki The page's worked example is self-defeating and points at a page that does not exist. Map:wiki illustrates that spaces and underscores are interchangeable in a page title with: "so wiki=Khurouan and wiki=Khurouan reach the same page" — the two sides are identical, so the sentence demonstrates nothing; the underscore form was evidently lost. Separately, Khurouan is not an article: the ancient city is Khurou, and Khurouan is the name of an editing account (User:Khurouan), which makes it doubly ill-suited as the example of a map-to-article cross-reference. Rewrite the example around a real two-word title so the point survives — e.g. "so wiki=Sea of Sihia and wiki=Sea_of_Sihia reach the same page", using Sea of Sihia, which exists. Mechanical, one sentence. pending New this run. If you would rather the example used a city, Khurou exists but is a single word and so cannot carry the underscore point.
35 2026-07-22 convention low Map:boundary, Map:highway, Map:highway=motorway, Map:name, Map:place, Map:place=city Reflexive "on Yezur" in the new Map pages trips the Earth test. Conventions ask that every Yezur/Yezuri still read naturally with the real world's name swapped in, and warn specifically against a reflexive qualifier "in front of every other noun". Seven sentences in the new set do not survive the swap: "On Yezur the common case is the administrative hierarchy"; "Yezur's route network"; "the highest-capacity roads on Yezur"; "Almost everything named on Yezur takes a name=*"; "the points and areas that carry Yezur's place names"; "its standing on Yezur rather than a fixed population cut-off"; "the largest and most prominent settlements on Yezur". A tagging guide for the world's own map has no more need of the qualifier than a road atlas does. Delete the qualifier in those seven places, leaving the sentences otherwise untouched ("The common case is the administrative hierarchy", "the route network", "the highest-capacity roads", and so on). The other three Yezur mentions in the set are genuinely contrastive and should stay: "a Yezur convention" (Map:admin level), "Yezur's language codes" (Map:name) and "Yezur's own cross-reference; there is no link to any outside wiki" (Map:wiki). Mechanical, but it is a copyedit of your own new prose, so it wants your say-so. pending New this run. Low severity — style polish, not an error. Deliberately not flagged alongside it: the imperative "How to tag" voice throughout the set, which is proper to a tagging guide and not the article-namespace register the convention governs.

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.

Latest run

2026-07-22 (scheduled run) — no operator verdicts were waiting (all ten rows were pending), so nothing on the wiki was changed; the run was a read-only survey. It was the busiest survey so far: the Map namespace grew from 1 page to 34.

Fixes applied: none — no row carried a verdict.

Dismissed: none.

New findings: five, all arising from the new Map pages.

  • #31 (medium) — Category:Map documentation does not exist, yet all 33 new pages file into it.
  • #32 (medium) — Map:name gives name:yas-ai for Airananwe as its worked example; no such language and no such code exists anywhere on this wiki.
  • #33 (low) — Map:place=hamlet and Map:place=suburb are the only redlinked values in any value table.
  • #34 (low) — Map:wiki's underscore example gives the same string twice, and names a page that does not exist.
  • #35 (low) — seven sentences across six Map pages carry a reflexive "on Yezur" that fails the Earth test.

Row updates: #26 raised from medium to high. It was filed as two dead links on a portal front page; the new pages have made it the wiki's one real navigational failure. Map:Main Page carries exactly two links, Map:Features and Map:Conventions, and both are redlinks — so none of the 33 pages the namespace now documents can be reached from the namespace's own front door. #22 was re-confirmed resolved (Lexemes still 526 of 526). The remaining rows (#23, #24, #25, #27, #28, #29, #30) were each re-confirmed still open and left pending.

Recent changes reviewed: 34 entries since the last survey, all by Yezur but one (Alompan's own report post). Map:place was written directly; the other 32 Map pages arrived together as an import at 19:52. The whole set was read against Yezur Wiki:Conventions in full. It comes through well: the register is consistent, the cross-links between key and value pages are dense and correct, the wikitables are well-formed (no linter errors), every page is categorised, and nothing in it breaks frame or reaches for a real-world reference — church and motorway as building and road kinds are exactly the familiar-to-the-second-level analogy the conventions invite. What the review turned up is the five items above. No article outside the Map namespace was edited, so there was no other new text to check.

Clean: no linter errors, no broken redirects, no double redirects, Category:Auphen errors empty, deletion queue empty. Structured data holds no row missing a key field: every Lexemes row carries both a gloss and a part of speech, and the language, family and continent rows are complete but for deliberate blanks. The job queue stands at 32, working through the new pages' links; it needs no attention.

Not treated as findings: the orphaned Dictionary: entries (reached through the Dictionary index rather than by inbound links — inherent to a dictionary, not a defect); the lexical wanted-category backlog, 43 of the 46 wanted categories, recorded on the User talk:Yezur to-do list as report flag #18; the wanted pages Dictionary:dog and Template:He-decl, cited only as documentation examples; the empty tracking categories Category:Auphen errors and Category:Pages flagged for deletion, whose emptiness is the good state; Template:Infobox polity, which no article uses yet, and the Polities table's 0 rows that follow from it; the imperative "How to tag" voice across the Map set, which suits a tagging guide; and Vetsihia appearing in the Continents Cargo table — it is a colloquial landmass rather than a continent, and is deliberately kept out of Category:Continents, but Template:Infobox continent is documented as covering "a continent or major landmass" and its type field carries the distinction, so the row is correct as it stands. Recorded here so later runs do not re-open it.

Structured data this run — Polities 0, Lexemes 526 (of 526 — in sync), by language: Ancient Hertic 212, Proto-Herta-Olaic 211, Proto-Njeshan 102, Pjany 1. Languages 7 (see #29), LanguageFamilies 5, Continents 8 (7 continents + Vetsihia, above). The wiki now holds 696 pages, 450 of them articles.

Pending tally: the table holds 14 rows — #26 (high); #23, #28, #29, #31, #32 (medium); #24, #25, #27, #30, #33, #34, #35 (low); and #22 (resolved, awaiting only a verdict to clear) — plus 5 findings in Dismissed flags. No row was resolved by an operator verdict this run.

Retrieved from "https://yezur.xyz/w/index.php?title=Yezur_Wiki:Daily_routine/Report&oldid=1311"