Yezur Wiki:Daily routine - Revision history

Thiorosan: Report convention, per operator: link files with the colon form :File:..., never embed images in the report

2026-08-04T10:02:25Z

Report convention, per operator: link files with the colon form File:..., never embed images in the report

← Older revision		Revision as of 10:02, 4 August 2026
Line 28:		Line 28:
	* New findings become new rows in the flagged-items table with Status <code>pending</code>, 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).		* New findings become new rows in the flagged-items table with Status <code>pending</code>, 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.		* 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 <code><nowiki>[[:File:Name]]</nowiki></code> (with the leading colon), not <code><nowiki>[[File:Name]]</nowiki></code>: the plain form drops the full image into the table.
	* Update the scan-state comment at the bottom of [[/Report]].		* Update the scan-state comment at the bottom of [[/Report]].

Thiorosan: Survey: structured-data check now covers Lexemes only; add drift check for hand-maintained lists (Cargo retired from the encyclopedia)

2026-07-30T11:27:20Z

Survey: structured-data check now covers Lexemes only; add drift check for hand-maintained lists (Cargo retired from the encyclopedia)

← Older revision		Revision as of 11:27, 30 July 2026
Line 17:		Line 17:

	* '''Structural health''' — from the API (<code>list=querypage</code>): '''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.		* '''Structural health''' — from the API (<code>list=querypage</code>): '''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''' — ~~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. Propose a fix only where it is mechanical.		* '''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 <code>family</code> 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 (<code>list=linterrors</code>): name the page and propose the fix.		* '''Markup''' — linter errors (<code>list=linterrors</code>): name the page and propose the fix.
	* '''Auphen errors''' — pages in [[:Category:Auphen errors]]: an <code><nowiki>{{auphen}}</nowiki></code> 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 <code>Module:Auphen/<code></code> data page, or fix the call.		* '''Auphen errors''' — pages in [[:Category:Auphen errors]]: an <code><nowiki>{{auphen}}</nowiki></code> 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 <code>Module:Auphen/<code></code> data page, or fix the call.

Khurouan: Add deletion-queue check to the survey

2026-07-18T15:27:12Z

Add deletion-queue check to the survey

← Older revision		Revision as of 15:27, 18 July 2026
Line 20:		Line 20:
	* '''Markup''' — linter errors (<code>list=linterrors</code>): name the page and propose the fix.		* '''Markup''' — linter errors (<code>list=linterrors</code>): name the page and propose the fix.
	* '''Auphen errors''' — pages in [[:Category:Auphen errors]]: an <code><nowiki>{{auphen}}</nowiki></code> 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 <code>Module:Auphen/<code></code> data page, or fix the call.		* '''Auphen errors''' — pages in [[:Category:Auphen errors]]: an <code><nowiki>{{auphen}}</nowiki></code> 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 <code>Module:Auphen/<code></code> data page, or fix the call.
			* '''Deletion queue''' — pages in [[:Category:Pages flagged for deletion]] (tagged with <code><nowiki>{{delete}}</nowiki></code>): 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.		* '''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.

Khurouan: Add an Auphen-errors check to the survey

2026-07-18T01:08:34Z

Add an Auphen-errors check to the survey

← Older revision		Revision as of 01:08, 18 July 2026
Line 19:		Line 19:
	* '''Structured data''' — 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. Propose a fix only where it is mechanical.		* '''Structured data''' — 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. Propose a fix only where it is mechanical.
	* '''Markup''' — linter errors (<code>list=linterrors</code>): name the page and propose the fix.		* '''Markup''' — linter errors (<code>list=linterrors</code>): name the page and propose the fix.
			* '''Auphen errors''' — pages in [[:Category:Auphen errors]]: an <code><nowiki>{{auphen}}</nowiki></code> 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 <code>Module:Auphen/<code></code> data page, or fix the call.
	* '''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.		* '''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.

Thiorosan: Recent-changes check now reviews adherence to the conventions in full (voice, Earth test, formatting, naming, categorisation)

2026-07-17T10:28:05Z

Recent-changes check now reviews adherence to the conventions in full (voice, Earth test, formatting, naming, categorisation)

← Older revision		Revision as of 10:28, 17 July 2026
Line 19:		Line 19:
	* '''Structured data''' — 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. Propose a fix only where it is mechanical.		* '''Structured data''' — 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. Propose a fix only where it is mechanical.
	* '''Markup''' — linter errors (<code>list=linterrors</code>): name the page and propose the fix.		* '''Markup''' — linter errors (<code>list=linterrors</code>): name the page and propose the fix.
	* '''Recent changes''' — for articles changed since the last run (see the scan-state comment at the bottom of [[/Report]]): 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.		* '''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 ===		=== 3 · File and summarise ===

Thiorosan: Fold verdict-processing into each run: apply approved/amended fixes from the report table first, then survey; define the five statuses

2026-07-16T12:29:45Z

Fold verdict-processing into each run: apply approved/amended fixes from the report table first, then survey; define the five statuses

← Older revision		Revision as of 12:29, 16 July 2026
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, carried out by the [[User:Alompan\|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 <code>approved</code> or <code>amended</code>. 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 ==		== 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.~~		=== 1 · Carry out the operator's verdicts ===

	~~=== 1. Structural health ===~~		Read the flagged-items table on [[/Report]] and handle every row whose Status is not <code>pending</code>:
	~~From~~ the ~~API (~~<code>~~list=querypage~~</code>):
	* '''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 ===~~		* <code>approved</code> — carry out the '''Suggested fix''' as written, as ordinary encyclopedia edits with in-character summaries. Remove the row.
	~~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~~.		* <code>amended</code> — carry out the fix described in the '''Notes''' cell (the notes override the suggested fix). Remove the row.
			* <code>deferred</code> / <code>rejected</code> — 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 <code>pending</code> and explain why in Notes.

	~~=== 3. Markup ===~~		A row whose fix is ''flag-only'' has nothing mechanical to apply: it is resolved either by an <code>amended</code> fix in Notes, or by dismissing it.
	~~Linter errors (~~<code>~~list=linterrors~~</code>~~) — name the page and propose the~~ fix.

	=== ~~4. Recent changes~~ ===		=== 2 · Survey ===
	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.

	== ~~The report ==~~		* '''Structural health''' — from the API (<code>list=querypage</code>): '''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''' — 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. Propose a fix only where it is mechanical.
			* '''Markup''' — linter errors (<code>list=linterrors</code>): name the page and propose the fix.
			* '''Recent changes''' — for articles changed since the last run (see the scan-state comment at the bottom of [[/Report]]): 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.

	~~Overwrite [[/Report]] with a dated, numbered list, most severe first. Format each item as:~~		=== 3 · File and summarise ===
	~~: '''N.''' <code>[category~~ · ~~severity]</code> <page(s)> — the issue in a sentence. '''Fix:''' the concrete edit, or ''flag-only''. '''Status:''' pending~~

	~~Close~~ with ~~a tally~~, e.~~g. "18 items~~ — ~~3 high~~, ~~9 medium, 6 low"~~.		* New findings become new rows in the flagged-items table with Status <code>pending</code>, 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.
			* Update the scan-state comment at the bottom of [[/Report]].

	== ~~Approving and applying~~ ==		== Statuses ==

	~~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~~.		{\| class="wikitable"
			! Status !! Set by !! Meaning !! On the next run
			\|-
			\| <code>pending</code> \|\| Alompan \|\| awaiting the operator's review \|\| stays in the table
			\|-
			\| <code>approved</code> \|\| the operator \|\| the suggested fix is wanted, as written \|\| fix applied, row removed
			\|-
			\| <code>amended</code> \|\| the operator \|\| a different fix is wanted — described in Notes \|\| Notes applied, row removed
			\|-
			\| <code>deferred</code> \|\| the operator \|\| real, but not worth acting on now \|\| moved to Dismissed flags
			\|-
			\| <code>rejected</code> \|\| the operator \|\| not an issue \|\| moved to Dismissed flags
			\|}

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

	[[Category:Yezur Wiki]]		[[Category:Yezur Wiki]]

Khurouan: Restore the local routine that posts its report to the wiki

2026-07-15T21:08:53Z

Restore the local routine that posts its report to the wiki

← Older revision		Revision as of 21:08, 15 July 2026
Line 1:		Line 1:
	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~~.		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.

	== On each run ==		== 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.		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.

	=== 1. Structural health ===		=== 1. Structural health ===
Line 17:		Line 17:

	=== 4. Recent changes ===		=== 4. Recent changes ===
	~~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.		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.

	== The report ==		== The report ==

	~~'''Print'''~~ a dated, numbered list ~~as the run's output~~, most severe first. Format each item as:		Overwrite [[/Report]] with a dated, numbered list, 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''.		: '''N.''' <code>[category · severity]</code> <page(s)> — the issue in a sentence. '''Fix:''' the concrete edit, or ''flag-only''. '''Status:''' pending

	Close with a tally, e.g. "18 items — 3 high, 9 medium, 6 low".		Close with a tally, e.g. "18 items — 3 high, 9 medium, 6 low".
Line 28:		Line 28:
	== Approving and applying ==		== Approving and applying ==

	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.		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.

	[[Category:Yezur Wiki]]		[[Category:Yezur Wiki]]

Khurouan: Rewrite for a read-only cloud run that prints its report

2026-07-15T20:54:41Z

Rewrite for a read-only cloud run that prints its report

← Older revision		Revision as of 20:54, 15 July 2026
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 ==		== 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 ===		=== 1. Structural health ===
Line 17:		Line 17:

	=== 4. Recent changes ===		=== 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 ==		== 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".		Close with a tally, e.g. "18 items — 3 high, 9 medium, 6 low".
Line 28:		Line 28:
	== Approving and applying ==		== 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]]		[[Category:Yezur Wiki]]

Khurouan: Create the daily routine task list

2026-07-15T19:58:58Z

Create the daily routine task list

New page

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.

== 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.

=== 1. Structural health ===
From the API (<code>list=querypage</code>):
* '''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 (<code>list=linterrors</code>) — name the page and propose the fix.

=== 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.

== The report ==

Overwrite [[/Report]] with a dated, numbered list, 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

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

== 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.

[[Category:Yezur Wiki]]