Yezur Wiki:Daily routine

Task list for the automated daily maintenance routine, carried out by the Alompan account. Each run does two things, in order: first it carries out the verdicts the operator has left in the /Report table, then it surveys the wiki and files new findings there. The survey itself changes nothing; the only canon edits in a run are fixes the operator has explicitly marked approved or amended. When unsure whether something qualifies as a finding, leave it out or file it flag-only — a short, trustworthy report beats a noisy one.

On each run

1 · Carry out the operator's verdicts

Read the flagged-items table on /Report and handle every row whose Status is not pending:

• approved — carry out the Suggested fix as written, as ordinary encyclopedia edits with in-character summaries. Remove the row.
• amended — carry out the fix described in the Notes cell (the notes override the suggested fix). Remove the row.
• deferred / rejected — remove the row and add one line to Dismissed flags on /Report: id, verdict, a one-sentence summary, and any operator note. Dismissed findings are not re-flagged by later runs.
• A row that cannot be carried out as instructed — the fix fails, or turns out to need a judgment call after all — stays in the table: set its Status back to pending and explain why in Notes.

A row whose fix is flag-only has nothing mechanical to apply: it is resolved either by an amended fix in Notes, or by dismissing it.

2 · Survey

• Structural health — from the API (list=querypage): wanted categories (priority — propose creating each with a best-guess parent and a one-line description; flag-only if the parent is unclear); wanted pages and templates; orphaned and uncategorised pages; double and broken redirects. Propose the concrete fix where it is unambiguous.
• Structured data — the wiki's one Cargo table, Lexemes (Special:CargoTables): rows missing a key field, duplicate values that should be unique, and references to pages that do not exist. Propose a fix only where it is mechanical.
• Hand-maintained lists — tables and rosters that summarise other articles (each family's Members table against the family field of its languages' infoboxes; Main Page's continent list against the continent articles): flag entries that have drifted from the articles they summarise, and members missing from a list. Propose the mechanical fix.
• Markup — linter errors (list=linterrors): name the page and propose the fix.
• Auphen errors — pages in Category:Auphen errors: an {{auphen}} call that could not resolve (unknown language code, unknown ruleset, or missing input). List each with the failing call and propose the fix — create or correct the Module:Auphen/<code> data page, or fix the call.
• Deletion queue — pages in Category:Pages flagged for deletion (tagged with {{delete}}): the editing bots hold no delete right, so list each with its stated reason for the administrator to action. Flag-only — never remove the tag or blank the page.
• Recent changes — for articles changed since the last run (see the scan-state comment at the bottom of /Report): adherence to Yezur Wiki:Conventions in full — voice and register, the Earth test, text formatting, naming, categorisation; factual contradictions against linked or related canon; and open threads (placeholders, dangling references) to propose as Talk-page notes.

3 · File and summarise

• New findings become new rows in the flagged-items table with Status pending, dated with the run. Skip anything already in the table or on the Dismissed-flags list — match on substance, not wording. Ids are never reused; continue from the highest id ever issued (check both the table and the dismissed list).
• Rewrite the Latest run section of /Report: the date; fixes applied (with revision ids); flags dismissed; new flags filed; the clean checks; and a tally of what is now pending.
• Files are linked, never embedded — anywhere on /Report, write [[:File:Name]] (with the leading colon), not [[File:Name]]: the plain form drops the full image into the table.
• Update the scan-state comment at the bottom of /Report.

Statuses

Status	Set by	Meaning	On the next run
pending	Alompan	awaiting the operator's review	stays in the table
approved	the operator	the suggested fix is wanted, as written	fix applied, row removed
amended	the operator	a different fix is wanted — described in Notes	Notes applied, row removed
deferred	the operator	real, but not worth acting on now	moved to Dismissed flags
rejected	the operator	not an issue	moved to Dismissed flags

Nothing is ever applied without an explicit approved or amended. Findings that need a genuine editorial or creative decision are filed flag-only and left to the operator.