README.md

@@ -1188,13 +1188,19 @@ FORGEJO__actions__DEFAULT_ACTIONS_URL=https://code.forgejo.org
 > `runner-isolated`, `docs-sync`, and the release/labels callers) fails to
 > resolve the moment rig's CI actually runs on the forge.
 >
-> Forgejo accepts an absolute URL per step, so one side has to be explicit —
-> which one is a **decision this PR does not make**. Either set the default to
-> this instance and make the three `actions/*` references absolute
-> (`uses: https://code.forgejo.org/actions/checkout@v4`), or keep the value
-> above and make the eight ceremony references absolute. Until that lands,
-> **rig's CI is not expected to run on Forgejo** — `rig forgejo-runner` is for
-> running *your* repositories' workflows, and does not depend on this.
+> Forgejo accepts an absolute URL per step, so one side has to be explicit.
+> **The ruling is to keep the value above** — `actions/*` are exactly what
+> `DEFAULT_ACTIONS_URL` is designed to resolve, and `code.forgejo.org` mirrors
+> them — and to make the eight first-party references absolute:
+>
+> ```yaml
+> - uses: https://forgejo.heavyduty.builders/heavy-duty/ceremony/actions/docs-sync@0.3.0
+> ```
+>
+> That change is tracked in forgejo#112, not made here. Until it lands,
+> **rig's own CI is not expected to run on Forgejo**.
+> `rig forgejo-runner` exists to run *your repositories'* workflows and does not
+> depend on any of it — the value above is correct for those from the start.
 
 > **A registry served from Forgejo needs one more.** `RIG_TEMPLATES_HOST`
 > (below) lets the template registry live on any forge, but the mint-time fetch