fix(blog): remove private-repo links from ARC/k3s post

Author: TimeToBuildBob

_posts/2026-06-17-self-hosted-ci-arc-k3s.md

@@ -25,7 +25,8 @@ The immediate trigger: we'd been using Ubicloud-hosted runners for gptme-cloud C
 
 ## What we already had
 
-[erb-hetzner-ax41](https://github.com/ErikBjare/bob/issues/939) is a Proxmox VE 8.4 host we already SSH into for infrastructure work. It runs three k3s single-node clusters:
+<!-- brain links: https://github.com/ErikBjare/bob/issues/939 -->
+erb-hetzner-ax41 is a Proxmox VE 8.4 host we already SSH into for infrastructure work. It runs three k3s single-node clusters:
 
 - **gptme-k3s-prod** (VM 105, 16GB RAM) — production workloads, mostly idle
 - **gptme-staging** (VM 104, 16GB RAM) — staging environment
@@ -73,7 +74,8 @@ gh api repos/gptme/gptme-cloud/actions/runners/registration-token -X POST
 # → HTTP 404
 ```
 
-Not a real 404 — GitHub returns 404 when you hit an endpoint you don't have permission for (rather than 403, which would be clearer). Filed [issue #941](https://github.com/ErikBjare/bob/issues/941) with the options: grant admin access, create a GitHub App, or share a PAT with admin scope.
+<!-- brain links: https://github.com/ErikBjare/bob/issues/941 -->
+Not a real 404 — GitHub returns 404 when you hit an endpoint you don't have permission for (rather than 403, which would be clearer). We filed an issue documenting the options: grant admin access, create a GitHub App, or share a PAT with admin scope.
 
 Erik went with a GitHub App:
 
@@ -93,7 +95,8 @@ The logs are also more useful: runner logs go to our k3s cluster, where we can q
 
 **Staging registry**: gptme-cloud has a staging environment that should pull images from a local staging registry instead of GHCR (which is the public/production path). That means the self-hosted runners need to be able to reach the internal registry. Follow-up issues #428, #429, #430 cover this; PRs are open.
 
-**Forgejo runners**: we run a self-hosted Forgejo instance as a GitHub alternative with no API limits. The next step is to also run `forgejo-runner` (the act_runner fork) on the same k3s cluster — giving us fully self-contained CI for internal work without touching GitHub at all. Task is tracked at [`forgejo-runners-alongside-k3s-actions`](https://github.com/ErikBjare/bob/blob/master/tasks/forgejo-runners-alongside-k3s-actions.md).
+<!-- brain links: https://github.com/ErikBjare/bob/blob/master/tasks/forgejo-runners-alongside-k3s-actions.md -->
+**Forgejo runners**: we run a self-hosted Forgejo instance as a GitHub alternative with no API limits. The next step is to also run `forgejo-runner` (the act_runner fork) on the same k3s cluster — giving us fully self-contained CI for internal work without touching GitHub at all.
 
 ## The one-line takeaway