Automatic translations update

i18n/translation-templates/docs/configuring-playbook-bot-meowlnir.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-08-13 05:03+0000\n"
+"POT-Creation-Date: 2026-08-17 08:17+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -441,141 +441,145 @@ msgid "Re-running is safe and idempotent, so adding a bot later is a matter of e
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bot-meowlnir.md:278
-msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgid "If the homeserver turns out to be running without Meowlnir's appservice registration (which is the normal state of affairs on the run that first enables Meowlnir), the playbook restarts the homeserver during bot provisioning, so that everything completes in a single run."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bot-meowlnir.md:280
-msgid "Usage"
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bot-meowlnir.md:282
-msgid "You can refer to the upstream [documentation](https://docs.mau.fi/meowlnir/) for a more detailed usage guide."
+msgid "Usage"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bot-meowlnir.md:284
-msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
+msgid "You can refer to the upstream [documentation](https://docs.mau.fi/meowlnir/) for a more detailed usage guide."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bot-meowlnir.md:286
-msgid "Inspecting and driving Meowlnir directly"
+msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bot-meowlnir.md:288
+msgid "Inspecting and driving Meowlnir directly"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:290
 msgid "The playbook drives Meowlnir's management API for you based on `matrix_bot_meowlnir_bots_custom`, which is the recommended way. For anything it does not cover, helper scripts are installed under `/matrix/meowlnir/bin`, which find the management secret and reach the API inside the container:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:301
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:307
 msgid "`meowlnir-create-management-room` prints the new room's ID, which you then register with `meowlnir-api PUT /_meowlnir/v1/management_room/<room ID>`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:303
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:309
 msgid "See the upstream [bot creation documentation](https://docs.mau.fi/meowlnir/bot-create.html) for the full set of endpoints. Bear in mind that bots you create this way are not declared in your `vars.yml` file, so the next playbook run will remove them again (see [Bots which are no longer declared](#bots-which-are-no-longer-declared))."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:305
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:311
 msgid "If you have enabled encryption, each bot also needs verifying once. That step is left manual because it returns a recovery key you need to store somewhere safe:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:311
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:317
 msgid "Protecting a room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:313
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:319
 msgid "Invite the bot to a room, give it a power level high enough to act (see below), and then tell it to protect the room by sending this command to its management room:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:319
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:325
 msgid "Meowlnir refuses to protect a room unless its power level reaches that room's own `ban` and `redact` levels (50 in a default room). That is only enough for user bans, though: writing `m.room.server_acl` usually requires 100, and without it the server rules in your watched lists have no effect — which is most of what a list like [CME](https://matrix.to/#/%23community-moderation-effort-bl:neko.dev) carries. **Give the bot power level 100** unless you only care about user bans."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:321
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:327
 msgid "Set the power level *before* protecting the room. Meowlnir re-sends server ACLs when it starts and when a watched list changes, but not when its own power level goes up subsequently, so raising it afterwards leaves the room without ACLs until you restart the bot (`systemctl restart matrix-bot-meowlnir` or via the playbook's Ansible `start` tag)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:323
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:329
 msgid "Subscribing to a policy list"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:325
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:331
 msgid "Policy lists are maintained in Matrix rooms. Popular public ones are:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:327
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:333
 msgid "`#community-moderation-effort-bl:neko.dev`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:328
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:334
 msgid "`#huginn-muninn-active-threats:feline.support`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:330
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:336
 msgid "Subscribe to one by sending the following command to the management room:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:336
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:342
 msgid "The last argument is a shortcode, which you use to refer to the list in later commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:338
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:344
 msgid "Overriding a policy from someone else's list"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:340
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:346
 msgid "This is the main capability Meowlnir has that Draupnir does not."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:342
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:348
 msgid "When several watched lists carry a policy for the same user, **the first match wins**, and \"first\" means the order in which the lists are watched. So to be able to override a community list's ban, your own list has to come before it."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:344
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:350
 msgid "`!lists subscribe` appends, which makes subscription order the precedence order. Subscribe to your own list first, and to community lists afterwards:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:352
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:358
 msgid "If you have already subscribed in the wrong order, fixing it means editing the `fi.mau.meowlnir.watched_lists` state event in the management room by hand. Newer Meowlnir releases (than `v0.2606.0`) add `!lists subscribe … --insert-before <shortcode>`, which will make reordering a single command."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:354
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:360
 msgid "You can then publish an unban policy into your own list, which takes precedence over the community list's ban:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:361
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:367
 msgid "Unlike `!ban`, the `!add-unban` command does not treat its reason as a trailing argument, so a reason containing spaces is discarded. Use a single word (or hyphenate) until that is fixed upstream."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:364
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:370
 msgid "An unban policy stops a ban from being **re-applied**; it does not undo one that is already in place unless Meowlnir applied it itself and still has it on record. A ban placed by a human moderator, or by the Draupnir or Mjolnir you are migrating away from, stays. Unban such a user once by hand — from then on the policy keeps them unbanned, while you remain subscribed to the list that banned them."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:366
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:372
 msgid "Use `!match @alice:example.com` to see which policies currently apply to a user and which list each came from."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:369
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:375
 msgid "Unban policies use a Meowlnir-specific recommendation (`fi.mau.meowlnir.unban`) which is not part of the Matrix specification. If you publish your policy list for other people to subscribe to, subscribers running Draupnir or Mjolnir will ignore your unban policies."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:371
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:377
 msgid "There is also a blunter, server-wide escape hatch for policies that are too wide to tolerate at all — `matrix_bot_meowlnir_config_meowlnir_hacky_rule_filter_custom`, which makes Meowlnir ignore any policy matching the listed entities."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:373
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:379
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:375
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:381
 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running a command like `journalctl -fu matrix-bot-meowlnir`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:377
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:383
 msgid "If bots appear to do nothing, check that they have an Administrator power level in the rooms they are meant to protect, and that the room has been added with `!rooms protect`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:379
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:385
 msgid "If commands in a management room get no reply at all, check the bot's power level *there* too — it needs at least 50 to record its own configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-meowlnir.md:381
+#: ../../../docs/configuring-playbook-bot-meowlnir.md:387
 msgid "A bare `!lists` returns nothing in a management room which has never had a policy list. That is an upstream bug and it clears as soon as you subscribe to one; `!lists subscribe` works from the start."
 msgstr ""