git phorge sounds right, amend / land as real verbs is exactly the mental model the docs are struggling to explain, and no PHP dependency removes the first thing I got stuck on. Curious what the September test with the 5 says.

(removed the tag good first issue as we switch from "deploy existing CSS" to design a dark language properly)

Taking this task in addition to my current work for our 2027 design in T2353.

Preview of the current theme (light starts to be more polished, dark mode is still a big WIP) on Agora, because I'll use that for color ratio tweaks: https://agora.nasqueron.org/User:Dereckson/timeless.css (from line 22).

What I'd also like to see if a button to add a <syntaxhighlight> block.

I confirm the workflow works well.

The workflow itself has never really been the problem. It's fine, and it maps closely enough to a GitHub PR loop. What's heavy I would say is how much arrives at once on the first contributions, it's equal to too much current for a wire.

GPT-5.6-Sol proposal: https://chatgpt.com/share/6a8a838d-4cbc-83eb-b59e-5d847a64b03e

Deployment wasn't up-to-date and families configuration for Agora was missing, that's why fallback was on testwiki.

Mail bien reçu : `
ARC-Authentication-Results: i=1; mx.google.com;

spf=pass (google.com: domain of mediawiki-saas-no-reply@nasqueron.org designates 2001:41d0:303:d971::517e:c0de as permitted sender) smtp.mailfrom=mediawiki-saas-no-reply@nasqueron.org

Return-Path: <mediawiki-saas-no-reply@nasqueron.org>
Received: from web-001.nasqueron.drake (www-alkane.nasqueron.org. [2001:41d0:303:d971::517e:c0de])

by mx.google.com with ESMTP id ffacd0b85a97d-42e1ca54633si1934360f8f.947.2025.11.28.03.09.59
for <doba.guimartinien@gmail.com>;
Fri, 28 Nov 2025 03:10:00 -0800 (PST)

Received-SPF: pass (google.com: domain of mediawiki-saas-no-reply@nasqueron.org designates 2001:41d0:303:d971::517e:c0de as permitted sender) client-ip=2001:41d0:303:d971::517e:c0de;
Authentication-Results: mx.google.com;

spf=pass (google.com: domain of mediawiki-saas-no-reply@nasqueron.org designates 2001:41d0:303:d971::517e:c0de as permitted sender) smtp.mailfrom=mediawiki-saas-no-reply@nasqueron.org

Received: from mediawiki (uid 3004) (envelope-from mediawiki-saas-no-reply@nasqueron.org) id 1fd73 by web-001.nasqueron.drake (DragonFly Mail Agent v0.13+ on web-001.nasqueron.drake); Fri, 28 Nov 2025 11:09:58 +0000

SPF updated for nasqueron.org domain to allow web-001:

DNS record for SPF, TXT version, didn't include the IPs of web-001, now it's the case with D3892 (propagation still pending to nsX.he.net)

Wiki documentation added to Devserver reference: https://agora.nasqueron.org/index.php?title=Devserver_reference&diff=2037&oldid=1966

Wurf is configured to use port 8080, most of the table can be added to PORTS file.

In T2124#32520, @dereckson wrote:

Next steps for full automation:

• allow to login with proper credentials
  • Vault via rOPS: Create a permission for access to relevant credentials (see first comment of this post, acquisitariat not needed)
  • Vault manually: Create an AppRole linked to that permission
  • Code: allow to login to Vault with AppRole when available in environment or when a file exists, TO IMPLEMENT FOR BOTH TOOLS (bot needs Agora, run-report needs db-B-001).
• deploy the bot on WindRiver
  • Vault via rOPS: credentials to query Vault (ie secret id and role id from the AppRole)
  • Salt: create rhyne-wyse user
  • Salt: create /var/db/rhyne-wyse, chown to rhyne-wyse:nasquenautes in 775, so everyone can run the bot too
  • Salt: provide /etc/periodic configuration to run the script daily

Just for information, log doesn't have any timestamp.

At this stage, we've an auto update working when running the helper script manually:

Releasing the task assignment.

Deployed on WindRiver. Anyone with a vault token valid for ops/secrets/dbserver/cluster-B/users/rhyne-wyse can run there:

Claiming temporarily for credentials and if time allows this evening write helpers script. Will release afterwards, so anyone can create the bot.

On Agora, an account name is required for the automated agent / bot.
The agent will be called Rhyne-Wyse [1].

The documentation is now more comprehensive and include the steps to contribute.

That workflow has been added to the main documentation page.

Mumble isn't currently in scope.

Plan is to temporarily increase $wgMaxImageArea from 12500000 to 15000000, so we can generate thumbnail for our files.

I moved my WikiMedia development environment from Ysul to WindRiver, so we can have a faster https://mediawiki.dereckson.be/ to test this.