Yezur Wiki:Daily routine: Difference between revisions

Revision as of 20:54, 15 July 2026

Task list for the automated daily maintenance routine (the Alompan project). It is report-first and read-only: each run surveys the wiki and prints a numbered report of issues and proposed fixes as its own output — it writes nothing to the wiki, and does not even log in. A human reviews the printed report and, on a separate run, has Alompan apply the chosen items.

On each run

Survey the wiki through the public API and print the report. No edits, no login. When unsure whether something qualifies, leave it out or mark it flag-only; a short, trustworthy report beats a noisy one.

1. Structural health

From the API (list=querypage):

Wanted categories (priority) — used but not created. 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 pages, uncategorised pages, double and broken redirects — list them, and propose the concrete fix where it is unambiguous.

2. Structured-data consistency

For each table in Special:CargoTables: rows missing a key field, duplicate values that should be unique, and references to pages that do not exist. Flag; propose a fix only where it is mechanical.

3. Markup

Linter errors (list=linterrors) — name the page and propose the fix.

4. Recent changes

There is no stored state, so use a rolling time window on list=recentchanges sized to the schedule (about a day for a daily run). For articles changed in that window: factual contradictions against linked or related canon; voice breaks (real-world references, out-of-frame intrusions, non-encyclopedic register — see Yezur Wiki:Conventions); and open threads (placeholders, dangling references) to propose as Talk-page notes.

The report

Print a dated, numbered list as the run's output, most severe first. Format each item as:

N. [category · severity] <page(s)> — the issue in a sentence. Fix: the concrete edit, or flag-only.

Close with a tally, e.g. "18 items — 3 high, 9 medium, 6 low".

Approving and applying

A human reads the printed report and picks the item numbers to apply. On a separate, human-triggered run, Alompan performs only those items — as ordinary encyclopedia edits, with in-character summaries. Items that need a genuine editorial or creative decision stay flag-only for a human.

@@ Line 1: / Line 1: @@
-Task list for the automated daily maintenance routine, carried out by the [[User:Alompan|Alompan]] account. The routine is '''report-first''': each run surveys the wiki and posts a numbered report to [[/Report]], and changes no article content on its own. A human reviews the report, approves items, and the approved fixes are applied on a separate, human-triggered run.
+Task list for the automated daily maintenance routine (the [[User:Alompan|Alompan]] project). It is '''report-first and read-only''': each run surveys the wiki and '''prints''' a numbered report of issues and proposed fixes as its own output — it writes '''nothing''' to the wiki, and does not even log in. A human reviews the printed report and, on a separate run, has [[User:Alompan|Alompan]] apply the chosen items.
 == On each run ==
-Acting as Alompan, work through the checks below, then overwrite [[/Report]] with the findings. '''Change no canon during a run''' — the only page written is [[/Report]]. When unsure whether something qualifies, leave it out or mark it flag-only; a short, trustworthy report beats a noisy one.
+Survey the wiki through the public API and print the report. '''No edits, no login.''' When unsure whether something qualifies, leave it out or mark it flag-only; a short, trustworthy report beats a noisy one.
 === 1. Structural health ===
@@ Line 17: / Line 17: @@
 === 4. Recent changes ===
-For articles changed since the last run: factual '''contradictions''' against linked or related canon; '''voice''' breaks (real-world references, out-of-frame intrusions, non-encyclopedic register — see [[Yezur Wiki:Conventions]]); and '''open threads''' (placeholders, dangling references) to propose as Talk-page notes.
+There is no stored state, so use a rolling '''time window''' on <code>list=recentchanges</code> sized to the schedule (about a day for a daily run). For articles changed in that window: factual '''contradictions''' against linked or related canon; '''voice''' breaks (real-world references, out-of-frame intrusions, non-encyclopedic register — see [[Yezur Wiki:Conventions]]); and '''open threads''' (placeholders, dangling references) to propose as Talk-page notes.
 == The report ==
-Overwrite [[/Report]] with a dated, numbered list, most severe first. Format each item as:
+'''Print''' a dated, numbered list as the run's output, most severe first. Format each item as:
-: '''N.''' <code>[category · severity]</code> <page(s)> — the issue in a sentence. '''Fix:''' the concrete edit, or ''flag-only''. '''Status:''' pending
+: '''N.''' <code>[category · severity]</code> <page(s)> — the issue in a sentence. '''Fix:''' the concrete edit, or ''flag-only''.
 Close with a tally, e.g. "18 items — 3 high, 9 medium, 6 low".
@@ Line 28: / Line 28: @@
 == Approving and applying ==
-A human reviews [[/Report]] and changes the <code>Status:</code> of each wanted item from <code>pending</code> to <code>approved</code> (leaving the rest). On a separate, human-triggered apply run, Alompan performs '''only''' the <code>approved</code> items — as ordinary encyclopedia edits, with in-character summaries — and sets each to <code>applied</code> with its revision id. Nothing is ever applied without an explicit <code>approved</code>. Items that need a genuine editorial or creative decision stay flag-only and are left for a human.
+A human reads the printed report and picks the item numbers to apply. On a separate, human-triggered run, [[User:Alompan|Alompan]] performs only those items — as ordinary encyclopedia edits, with in-character summaries. Items that need a genuine editorial or creative decision stay flag-only for a human.
 [[Category:Yezur Wiki]]