Turn a Chat Into a How-To Guide

This conversation ended with something that worked. Turn it into a how-to guide that someone else could follow without reading the chat.

What the guide is for: {{task the guide achieves}}
Who will follow it and what they already know: {{reader}}
Where it will be stored (wiki, README, document) and any template: Markdown for a team wiki
Environment or versions it applies to, if known: as used in the chat

Work through these steps and show them in order:
1. Reconstruct the path to the working result. Identify which steps in the chat actually produced it, and which attempts were dead ends or were later replaced. List the dead ends separately with one line each on why they failed, because they may be worth a warning.
2. Write the guide with these sections: Goal, Before you start (requirements, access, versions, backups), Steps, How to check it worked, Common problems, and Rollback or undo if the steps change something.
3. Steps must be numbered, one action each, in the order that works. Use exact commands, settings and names as they appeared in the chat, in code blocks. Add the expected result after a step where it helps.
4. Replace anything specific to this one situation, such as names, ids and personal paths, with clearly marked placeholders, and list them. Never keep passwords, tokens, keys or private data.
5. Mark any step where the chat did not confirm the result, or where something was assumed, as [unverified].
6. End with "What I could not confirm from the chat": gaps a person would hit when following the guide.

Rules: do not add steps, commands or settings that were not in the conversation, even if you think they would help. If you know of a likely improvement, put it in a separate "Possible improvements, not tested" list. Do not claim the guide has been tested by anyone but me.

2 required fields are empty and will stay as a {{placeholder}} in the copied text.