Enforce unique doc filenames and simple wiki-links (#109)

## Summary
- Rename section index files to match their titles (tutorials.md, reference.md, how-to.md, explanation.md) so all filenames are unique
- Convert all ~47 path-based wiki-links to simple filename format across 15 files
- Update doc-filenames task to no longer skip index.md files
- Update doc-links task to reject path-based links containing '/'

This ensures all wiki-links work correctly in obsidian.nvim by making links resolvable by filename alone.

## Testing
- `mise run doc-filenames` - all unique
- `mise run doc-links` - no broken or path-based links
- `mise run doc-titles` - no duplicates

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/109

docs/tutorials/replication/argocd-config.md

@@ -198,7 +198,7 @@ BlumeOps uses manual sync for workloads, auto sync only for the `apps` Applicati
 
 ## Next Steps
 
-- [[tutorials/replication/observability-stack | Build observability]] - Monitor your deployments
+- [[observability-stack|Build observability]] - Monitor your deployments
 - Add more applications to your repo
 - Set up notifications for sync failures
 

docs/tutorials/replication/core-services.md

@@ -10,7 +10,7 @@ tags:
 
 > **Audiences:** Replicator
 >
-> **Prerequisites:** [[tutorials/replication/tailscale-setup | Tailscale Setup]]
+> **Prerequisites:** [[tailscale-setup|Tailscale Setup]]
 
 This tutorial walks through setting up the foundational services that your GitOps infrastructure depends on: a git forge and optionally a container registry.
 
@@ -29,7 +29,7 @@ Forgejo runs directly on your server (not in Kubernetes) because Kubernetes depe
 
 ### Using Ansible (BlumeOps Approach)
 
-BlumeOps manages Forgejo via an Ansible role. See [[reference/ansible/roles | Ansible Roles]].
+BlumeOps manages Forgejo via an Ansible role. See [[roles|Ansible Roles]].
 
 ### Manual Installation
 
@@ -101,7 +101,7 @@ For getting started, you can skip this and use public registries.
 
 ## Next Steps
 
-- [[tutorials/replication/kubernetes-bootstrap | Bootstrap Kubernetes]] - Now that you have a git repo, set up your cluster
+- [[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

docs/tutorials/replication/kubernetes-bootstrap.md

@@ -148,7 +148,7 @@ spec:
 
 ## Next Steps
 
-- [[tutorials/replication/argocd-config | Configure ArgoCD]] - GitOps deployments
+- [[argocd-config|Configure ArgoCD]] - GitOps deployments
 - Install essential addons (ingress controller, cert-manager)
 
 ## BluemeOps Specifics

docs/tutorials/replication/observability-stack.md

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

docs/tutorials/replication/tailscale-setup.md

@@ -112,8 +112,8 @@ Tags must be defined in ACLs before use.
 ## Next Steps
 
 With networking established:
-- [[tutorials/replication/core-services | Set Up Core Services]] - Install Forgejo and optionally a container registry
-- [[tutorials/replication/kubernetes-bootstrap | Bootstrap Kubernetes]] - Your cluster will join the tailnet
+- [[core-services|Set Up Core Services]] - Install Forgejo and optionally a container registry
+- [[kubernetes-bootstrap|Bootstrap Kubernetes]] - Your cluster will join the tailnet
 
 ## BlumeOps Specifics