Address PR review feedback for Phase 3 tutorials

Tutorial changes:
- Replace what-is-blumeops with adding-a-service tutorial
- Update ai-assistance-guide with Mise Tasks table
- Update contributing with tooling setup, target revisions, DNS preview
- Remove AI-only sections from contributing and exploring-the-docs
- Add replicator explanation to exploring-the-docs
- Add pre-commit link validation note
- Add Core Services phase to replication roadmap
- Add docs service to services list in replicating-blumeops

New reference cards:
- docs.md - Quartz documentation service
- tailscale-operator.md - Kubernetes ingress operator
- ansible/roles.md - Available ansible roles

Other updates:
- Add mise to Brewfile
- Update docs/index.md to link to exploring-the-docs
- Add notes to update exploring-the-docs in future phases
- Link tailscale-operator from apps.md

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

docs/tutorials/replication/argocd-config.md

@@ -49,16 +49,13 @@ For Tailscale access:
 tailscale serve --bg --https 8443 https+insecure://localhost:$(kubectl -n argocd get svc argocd-server -o jsonpath='{.spec.ports[?(@.name=="https")].port}')
 ```
 
-Or create a Tailscale Ingress in Kubernetes.
+Or create a Tailscale Ingress in Kubernetes (see [[tailscale-operator]]).
 
 Access at `https://your-server.tailnet.ts.net:8443`
 
 ### Install the CLI
 
-```bash
-brew install argocd  # macOS
-# or download from GitHub releases
-```
+BlumeOps includes `argocd` in its Brewfile (`brew bundle`), or install it however you prefer.
 
 Login:
 ```bash

docs/tutorials/replication/core-services.md

@@ -0,0 +1,113 @@
+---
+title: core-services
+tags:
+  - tutorials
+  - replication
+  - forgejo
+---
+
+# Core Services Setup
+
+> **Audiences:** Replicator
+
+This tutorial walks through setting up the foundational services that your GitOps infrastructure depends on: a git forge and optionally a container registry.
+
+## Why Core Services First?
+
+Before Kubernetes and ArgoCD, you need somewhere to store your infrastructure definitions. [[forgejo]] provides:
+- Git hosting for your GitOps repository
+- CI/CD workflows for building and deploying
+- A web interface for code review and PRs
+
+The [[zot]] container registry is optional but useful for hosting your own container images.
+
+## Step 1: Install Forgejo
+
+Forgejo runs directly on your server (not in Kubernetes) because Kubernetes depends on it.
+
+### Using Ansible (BlumeOps Approach)
+
+BlumeOps manages Forgejo via an Ansible role. See [[reference/ansible/roles | Ansible Roles]].
+
+### Manual Installation
+
+1. Download Forgejo from [forgejo.org](https://forgejo.org/download/)
+2. Create a service user and directories
+3. Configure with `app.ini`
+4. Set up as a system service
+
+Key configuration points:
+- SSH on a non-standard port (e.g., 2222) to avoid conflicts
+- Database (SQLite works fine for personal use)
+- Domain and URL settings for your Tailscale hostname
+
+## Step 2: Configure SSH Access
+
+Set up SSH for git operations:
+
+```bash
+# Add your SSH key to Forgejo via the web UI
+# Then test access:
+ssh -T git@your-server.tailnet.ts.net -p 2222
+```
+
+## Step 3: Create Your GitOps Repository
+
+1. Create a new repository in Forgejo (e.g., `infrastructure` or `homelab`)
+2. Initialize the standard directory structure:
+
+```
+your-repo/
+├── ansible/           # Host configuration
+│   ├── playbooks/
+│   └── roles/
+├── argocd/            # Kubernetes GitOps
+│   ├── apps/          # ArgoCD Applications
+│   └── manifests/     # K8s manifests per service
+├── pulumi/            # IaC for Tailscale, DNS
+└── docs/              # Documentation
+```
+
+3. Push your initial commit
+
+## Step 4: Set Up CI/CD Runner (Optional)
+
+Forgejo Actions runs workflows defined in `.forgejo/workflows/`. To use it:
+
+1. Register a runner on your server
+2. Configure runner to access your build tools
+3. Create workflow files for builds and deployments
+
+BlumeOps runs a Forgejo runner in Kubernetes - see [[forgejo]] for details.
+
+## Step 5: Container Registry (Optional)
+
+If you'll build custom container images, set up [[zot]]:
+
+1. Install Zot on your server
+2. Configure authentication
+3. Set up TLS (via Caddy or similar)
+
+For getting started, you can skip this and use public registries.
+
+## What You Now Have
+
+- Git hosting for infrastructure code
+- SSH access for git operations
+- Foundation for CI/CD workflows
+- Optionally, a private container registry
+
+## Next Steps
+
+- [[tutorials/replication/kubernetes-bootstrap | Bootstrap Kubernetes]] - Now that you have a git repo, set up your cluster
+- Configure Forgejo webhooks for ArgoCD (after ArgoCD is running)
+
+## BlumeOps Specifics
+
+BlumeOps' Forgejo setup includes:
+- Ansible role for installation and updates
+- SSH on port 2222, proxied via Caddy
+- Integration with ArgoCD via deploy keys
+- Forgejo runner in Kubernetes for CI/CD
+
+See [[forgejo]] and [[zot]] for full details.

docs/tutorials/replication/observability-stack.md

@@ -177,7 +177,7 @@ spec:
     namespace: monitoring
 ```
 
-BluemeOps uses Alloy on both [[indri]] (for host metrics) and in the [[cluster]] (for pod logs and service probes).
+BluemeOps uses Alloy on both [[indri]] (for host metrics, via [[reference/ansible/roles | Ansible role]]) and in the [[cluster]] (for pod logs and service probes).
 
 ## What You Now Have