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/replicating-blumeops.md

@@ -26,7 +26,7 @@ BluemeOps runs on modest hardware. At minimum:
 
 | Component | BlumeOps Uses | Minimum Alternative |
 |-----------|---------------|---------------------|
-| **Server** | Mac Mini M1 | Any machine with 16GB RAM |
+| **Server** | Mac Mini M1 | Any machine with sufficient RAM (16GB recommended) |
 | **NAS** | Synology DS920+ | USB drive or second machine |
 | **Workstation** | MacBook Air M4 | Whatever you use daily |
 
@@ -45,7 +45,18 @@ Before deploying services, establish secure connectivity.
 
 This replaces: traditional VPNs, port forwarding, dynamic DNS
 
-### Phase 2: Kubernetes Cluster
+### Phase 2: Core Services
+
+Bootstrap the essential services that everything else depends on.
+
+**[[tutorials/replication/core-services | Core Services Setup]]**
+- Set up [[forgejo]] for git hosting and CI/CD
+- Optionally set up [[zot]] container registry
+- Configure SSH access and deploy keys
+
+Forgejo is central to GitOps - it's where your infrastructure definitions live and where CI/CD workflows run.
+
+### Phase 3: Kubernetes Cluster
 
 A cluster for running containerized workloads.
 
@@ -56,7 +67,7 @@ A cluster for running containerized workloads.
 
 BlumeOps uses minikube for simplicity, but the patterns apply to any distribution.
 
-### Phase 3: GitOps with ArgoCD
+### Phase 4: GitOps with ArgoCD
 
 Declarative, git-driven deployments.
 
@@ -68,7 +79,7 @@ Declarative, git-driven deployments.
 
 This is the heart of GitOps - changes in git automatically sync to your cluster.
 
-### Phase 4: Observability Stack
+### Phase 5: Observability Stack
 
 Know what's happening in your infrastructure.
 
@@ -80,13 +91,14 @@ Know what's happening in your infrastructure.
 
 Without observability, you're flying blind.
 
-### Phase 5: Your First Services
+### Phase 6: Your First Services
 
 With the foundation in place, deploy actual workloads. BluemeOps runs:
 - [[miniflux]] - RSS reader
 - [[jellyfin]] - Media server
 - [[immich]] - Photo management
 - [[navidrome]] - Music streaming
+- [[docs]] - Documentation site (Quartz)
 
 Pick what matters to you. Each service follows similar patterns:
 1. Create Kubernetes manifests
@@ -94,7 +106,7 @@ Pick what matters to you. Each service follows similar patterns:
 3. Configure ingress routing
 4. Sync and verify
 
-### Phase 6: Backups and Resilience
+### Phase 7: Backups and Resilience
 
 Protect your data.
 
@@ -123,6 +135,5 @@ Begin with [[tutorials/replication/tailscale-setup]] - networking is the foundat
 
 ## Related
 
-- [[what-is-blumeops]] - Understand what you're replicating
 - [[reference/index]] - See BlumeOps' specific configurations
 - [[contributing]] - Help improve BlumeOps instead